Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Retension period + Incremental is good or not

Status
Not open for further replies.

vksm

IS-IT--Management
Oct 3, 2006
21
0
0
US
when we have two fulls in month like 1st and 15th full and other days incremental and browse/rentension policy set to say 30 days.

Say if the second full failed for some reason
1.what will be the retension period for the incrementals which follows the failed full can some one explain
also
2.whether these incrementals will be refering to the previous full and will it continue or this incremental is of no use ?
Thanks in advance
 
Browse and retention policies always refer to the real backup time. They will not change.

All differentials & incrementals of course refer to the last full, whenever this was created.

If you are afraid that NW might delete backups to early - do not worry. Due to the fact, that incrementals & differentials depend on the last full, NW will of course only delete a full backup cycle (all since the last full).
 
Thanks for your reply still I have doubt
what will be the status of todays incremental backup, when yesterday's full backup was stopped or aborted for some reason, whether todays incremental will refer to yesterdays bad full backup or will it refer to the previous good full back up?
 
As 605 explained, future backups only refer back to successful backups.

In the case of an incremental backup, it will refer to the last successful backup (of any level). A differential backup will refer to the last successful full backup. To prove this, run the following command:

savegrp -p -vvv -c <client> -l incr <group>

Look at the bottom of the output. It should say something like:

backup_server:/ pool=xxxx save as of ...

That date should be that of the last successful backup.

Then, run the same command, but replace the "-l incr" with "-l 1"

Assuming the last good backup wasn't a full, the save as of date should change from the last successful backup to match that of the last successful full backup (for all file systems, except for the index).

-ag100
 
Thank you ag100 that answers my question.

vksm
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top