I would venture a guess that MS is always working on the next version even 
before RTM.

----- Original Message -----
From: HELP_PC <g...@enter.it>
To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com>
Sent: Sat Mar 13 13:43:33 2010
Subject: R: Backup Software for Exchange 2007

This is not true.MS started with Exchange 2k10  less than 1 year after Exch 2k7


GuidoElia
HELPPC

-----Messaggio originale-----
Da: Michael B. Smith [mailto:mich...@smithcons.com]
Inviato: sabato 13 marzo 2010 12.37
A: MS-Exchange Admin Issues
Oggetto: RE: Backup Software for Exchange 2007

Where on earth does that comment come from and what relevance does it have to 
the topic?

Exchange 4.0, 5.0, and 5.5 were all released within a span of 3 years. Exchange 
2000 was less than 4 years later. Exchange 2003 was 3 years later. Exchange 
2007 was 4 years later...Exchange 2010 was 3 years later...

Exchange is on a 3 to 4 year release cycle. That's what all Microsoft products 
attempt to do.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: HELP_PC [mailto:g...@enter.it]
Sent: Saturday, March 13, 2010 4:11 AM
To: MS-Exchange Admin Issues
Subject: R: Backup Software for Exchange 2007

Exch 2k3 is old but Exch2k7 was old on borning.Its short life demonstrates it


GuidoElia
HELPPC

-----Messaggio originale-----
Da: Michael B. Smith [mailto:mich...@smithcons.com]
Inviato: venerdì 12 marzo 2010 22.46
A: MS-Exchange Admin Issues
Oggetto: RE: Backup Software for Exchange 2007

Exchange 2003 support is sub-par because DPM was designed to work with VSS 
providers and writers. The Exchange 2003 VSS support was sub-par.

DPM shines with Exchange 2007 and Exchange 2010, especially with block-level 
and real-time restores. It's a great product.

I agree with your comments - about ANY piece of software - that you should 
fully evaluate it and not purchase it just from a sales demo.

But Exchange 2003 is old. Very old in computer terms. It was designed and 
written in 2000-2001. Windows, Exchange, and backup solutions have come very 
far since then.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: Jason Gurtz [mailto:jasongu...@npumail.com]
Sent: Friday, March 12, 2010 4:32 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup Software for Exchange 2007

We are looking to replace Backup Exec (generally) and did not find our full 
replacement in DPM (we had really hoped).  We are now using a combination of 
Acronis and native ntbackup to take care of our Exchange 2003SP2.  We'll be 
evaluating the NetApp snap manager for exchange real soon now.

Here is a dose of DPM reality.

What I highly recommend to anyone not experienced with DPM (and looking at 
getting it) is to be sure to implement a full lab environment to assure that 
what the product actually does will meet your expectations before dropping the 
$$$.  I cannot stress enough that this is NOT a product to buy based on a sales 
demo or even after a cursory test install/restore.
Make sure it works on the exact configuration you have in production at the 
limits you need, particularly if you will AT ALL be using it with Exchange 2003.

The truth of what dpm appears to be:

-Cute wrapper around exutil, ntbackup, (etc... for other products); cute 
because the interface crashes sometimes.
-Tight integration with Windows VSS
-Some reporting/monitoring and client management tools (rough, some parts 
better than others)

That's it I'm afraid; you could probably emulate 90%+ of the backup and restore 
functionality with some .cmd/powershell scripts against WMI/WinRM and the task 
scheduler.  That's not meant to be a low blow, but more to say there's 
certainly no magic here regardless of the slick marketing the DPM team has put 
together.

There are high points:
- The PSS team for this product is great which is awesome since it's such a 
fragile product.
- It seems to work better with SQL
- I can say it's nearly seamless with Windows file backups

BUT, its Exchange integration, particularly with 2003 is amazingly sub-par. The 
respective management of the Exchange and DPM dev teams don't and won't get 
along with each other resulting in the customer being the loser!

The DPM 2010 story is a bit better, adding some nice functionality for 
client/laptop backups and getting rid of several interface annoyances.
Client backup may be its sweet spot.  DPM 2010 has not really addressed any 
Exchange concerns in 2010 and won't be from the communication I can see.

If DPM only cost a few hundred bucks there's no way I would've said all this. 
It's a lot more than that, so the lipstick-on-a-pig deserved it.
Think of WinNT circa 3.1...

Sorry for the rant, but I just can't believe anyone could recommend this 
product after having it in use here going on a year.

Jason

> -----Original Message-----
> From: Barsodi.John [mailto:john.bars...@igt.com]
> Sent: Friday, March 12, 2010 12:49
> To: MS-Exchange Admin Issues
> Subject: [MARKETING] RE: Backup Software for Exchange 2007
>
>
>
> Depending on all those factors, what about RTO? RPO? Backup hardware
> tech? Tape? D2D? Budget? Using an Exchange replication tech?
>
>
>
> Just about all current solutions cover most scenarios.
>
>
>
> I would recommend DPM 2007, use it to back up my Geo-dispersed CCR
boxes.
> Love it. We use Backup Exec 12.5 at all my single mailbox server
> International sites.
>
>
>
> Thanks,
>
> JB
>
>
>
> From: John Cook [mailto:john.c...@pfsf.org]
> Sent: Thursday, March 11, 2010 12:15 PM
> To: MS-Exchange Admin Issues
> Subject: RE: Backup Software for Exchange 2007
>
>
>
> That's a pretty broad request. Is there a budget for this? What level
> of SLA are you trying to attain? What is the impact of losing email in
> your org for an hour/day/week ?
>
>
>
> John W. Cook
>
> Systems Administrator
>
> Partnership For Strong Families
>
> 315 SE 2nd Ave
>
> Gainesville, Fl 32601
>
> Office (352) 393-2741 x320
>
> Cell     (352) 215-6944
>
> Fax     (352) 393-2746
>
> MCSE, MCTS, MCP, A, N, VSP4, VTSP4
>
>
>
> From: Sasan Oghlidos [mailto:sa...@ndia.org]
> Sent: Thursday, March 11, 2010 3:07 PM
> To: MS-Exchange Admin Issues
> Subject: Backup Software for Exchange 2007
>
>
>
> Hi,
>
>
>
> We are moving to Exchange 2007, looking for backup software/disaster
> recovery recommendations.
>
>
>
> Thanks,
>
>
>
>
>
> Sasan Oghlidos
> Director, Network & Systems
> National Defense Industrial Association V. 703.247.2557 F.
> 703.522.1885 WWW.NDIA.ORG <http://www.ndia.org/>
>
>
>
>
>
>
>
> ________________________________
>
> CONFIDENTIALITY STATEMENT: The information transmitted, or contained
> or attached to or with this Notice is intended only for the person or
entity
> to which it is addressed and may contain Protected Health Information
> (PHI), confidential and/or privileged material. Any review,
transmission,
> dissemination, or other use of, and taking any action in reliance upon
> this information by persons or entities other than the intended
recipient
> without the express written consent of the sender are prohibited. This
> information may be protected by the Health Insurance Portability and
> Accountability Act of 1996 (HIPAA), and other Federal and Florida laws.
> Improper or unauthorized use or disclosure of this information could
> result in civil and/or criminal penalties.
> Consider the environment. Please don't print this e-mail unless you
> really need to.
>
>
>
> This email and any attached files are confidential and intended solely
> for the intended recipient(s). If you are not the named recipient you
> should not read, distribute, copy or alter this email. Any views or
> opinions expressed in this email are those of the author and do not
> represent those of the company. Warning: Although precautions have
> been taken to make sure no viruses are present in this email, the
> company cannot accept responsibility for any loss or damage that arise
> from the use of this email or attachments.










CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
 Consider the environment. Please don't print this e-mail unless you really 
need to.

Reply via email to