Thanks all,

Though keeping the orginal full around(to create other synthetics) does seem
a bit strange. Hopefully Netbackup will mature to elimnate the constraint.

Jim

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of cpreston
Sent: Tuesday, July 07, 2009 1:39 PM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] Synthetic Backups




> I've been testing it myself. I think you do need to keep that full 
> backup around. The "synthetic" part of a synthetic backup is the 
> consolidation of the full backup and the incrementals into a single 
> image. This is done via duplication.


What makes it synthetic is that it is created tape to tape instead of
transferring a bunch of non-changed data from the client again.  Once that
new (synthetic) full is created, there is no need for previous fulls (other
than for retention).  The new full DOES NOT rely on the old full once it's
created.

+----------------------------------------------------------------------
|This was sent by wcplists1 AT gmail DOT com via Backup Central. Forward SPAM 
|to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


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

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