Date: Mar 10
Product & Version: NVBU 8.5
OS Version: ALL
Module & Version: N/A
Application version:N/a
Symptoms:
Incrmental backup savesets are not visible within restore GUI when log lists the backup as completing sucessfully.
If the full backup related to the antecedent incremental is retired
Until the full backup index is present in the database then the incremental is not going to be listed
even if you rescan the tape the incremental wrote to.
to identify this condition-
1 - establish which backup job wrote the incremental save set - job id and instance number (from the binary log)
2 - establish which full backup using the same selection set wrote full save set - job id and instance number (again from the binary log)
3 - check the binary log for any retirements for the period since the incremental backup completed - use the text filter and enter Retiring
i.e.
Information 2010/03/05 08:51:51 0 Media Main_Office_Backup_Server Retiring Backup 'FULL - 01FPR Clustered Data Backup' Job 131, Instance 102 - Retirement
date reached
Information 2010/03/05 08:51:51 0 Media Main_Office_Backup_Server Retiring Backup 'INC - 01FPR Cluster Data Backup' Job 132, Instance 355 - Backup no
longer complete
Information 2010/03/05 08:51:51 0 Media Main_Office_Backup_Server Retiring Backup 'INC - 01FPR Cluster Data Backup' Job 132, Instance 356 - Backup no
longer complete
Information 2010/03/05 08:51:51 0 Media Main_Office_Backup_Server Retiring Backup 'INC - 01FPR Cluster Data Backup' Job 132, Instance 357 - Backup no
longer complete
Information 2010/03/05 08:51:51 0 Media Main_Office_Backup_Server Retiring Backup 'INC - 01FPR Cluster Data Backup' Job 132, Instance 358 - Backup no
longer complete
Retirement date reached
if the full has retired and marked the subsequent incrementals incomplete the then all tapes used by the full *then* the incrementals will need to scanned
before the tapes used by the full are re-used
** Note if the full backup tapes have been overwritten then you will not be able to scan the indices back into the database
and the incrementals will be unusable -
to establish this check the content of these tapes within media management and cross reference the tape's activity within the binary log
since the required backup was written
1 - identify all tapes used in the full and incremental backups
ensure the tapes are offline - e.g. open the library or VTL door
2 - within media manager remove the individual tapes (this will cause the medis record to be removed from the database)
3 - close the library VTL door
4 - Perform a Scan of the full tapes
5 - Perform a scan of the incremental tapes
6 - check the restore GUI for the results
Going forward to prevent this situation re-occurring a copy of the full backup that is used as the baseline index for incrementals needs to be present
(e.g. minimum of one current, one of the previous full) on the system to keep the incrementals active
This can be achieved by extending the expiry date of the Full copy on the VTL or increasing the lifespan on the copy held on physical tape via phase2 duplication
This lifespan needs to incorporate the duration for which you wish to be able to restore from the last incremental taken before the next full backup in the series.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center