Hello Alex, 

Like everything else in this area, there good and bad things about both 
methods. 

The risky part is in the fact that Full backup does the data base and the logs, 
the Incremental only covers the logs. The Magic part of doing a full backup of 
the data base is that the exchange backup api does a checksum check of all the 
data base pages. A method to check for data base page corruption. 

Not a risky thing, but another point is that the after the last full data base 
is restored, all the existing and restored logs have to be applied by the api. 
If a exchange server is very active, then it can take a very long time to apply 
all the log pages. This can take more time then the restores. 

So it depends on how worried they are about exchange data base corruption, and 
the projected effect recovery of the logs will have on exchange server 
recovery. 
len 

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu [mailto:veritas-bu-admin 
AT mailman.eng.auburn DOT edu] On Behalf Of Wilkinson, Alex
Sent: Sunday, April 30, 2006 2:54 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Microsoft Exchange Backups ... [recommendations please]


Hi all,

Is there any reason whatsoever why Full+Incremental backups of Microsoft
Exchange are risky ? Our mail team is very dubious about moving to a
Full+Incremental backup paradigm for Exchange.

What do others do ? Is there a "best practices" way of doing it ?

 -aW
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu