Treat the retention policy as a write protect tab - it helps.
If you - for whatever reason - need to go back to an earlier cycle (just let's 
assume that the current full is bad or lost), then you want to have a previous 
one, correct? - That's why customers - if they clone - usually choose a longer 
retention policy for the clones.

Sorry - i obviously got the numbers wrong. Whatever backup cycle you choose, 
retention must be at least cover the backup cycle period.

BTW - the de-facto retention policy is 2 backup cycles. This is due to 
depencies as it only make sense to delete a whole backup cycle.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER