Catalog protection
What is catalog protection?
Data Protector saves information about backed up data in the IDB. Since the information about the backed up data is written to the IDB each time a backup is done, the IDB grows with the number and the size of backups. Catalog protection tells Data Protector how long the information about backed up data is available to users browsing data during restore. Once catalog protection has expired, Data Protector will overwrite this information in the IDB (not on the media) in one of the subsequent backups.
You can specify the protection using absolute or relative dates.
If you do not change the Catalog Protection backup option when configuring your backup, information about backed up data has the same protection duration as data protection. Note that if you do not change this, the IDB grows constantly as new information is added with each backup.
For more information on how catalog protection settings influence the IDB growth and performance, see “Catalog protection as an IDB key tunable
The protection model used by Data Protector can be mapped to the concept of backup generations, which is elaborated in Appendix B on page 331
Logging level
What is logging level?
Logging level determines the amount of details on files and directories written to the IDB during backup. You can always restore your data, regardless of the logging level used during the backup.
Data Protector provides four logging levels that control the amount of details on files and directories written to the IDB. For more information, see “Logging level as an IDB key tunable parameter” on page 199.
Browsing files for restore
The IDB keeps information about the backed up data. This information allows you to browse, select and start the restore of files using the Data Protector user interface. You can also restore data without this information as long as the media are still
100 | Planning your backup strategy |