Summary
The file history entries provide a file by file record of every backed-up file. File history is also saved in the Catalog and used at Restore time.
Question
What effect does File history have on a job and the DPX catalog?
Answer
The file history entries provide a file by file record of every backed-up file. File history is also saved in the Catalog and used at Restore time. The file history needs to be present to allow the browsing of restore points in the Catalog to enable single file restore. File history can be generated at backup or restore time.
What are the benefits of not running file history during the backup time?
- Faster completion times of Block level backups. For large Block-level backup jobs with a large number of files the file history generation may take a very long time; if this is disabled the jobs run much faster.
- Less disk space used for the DPX Catalog. When file history is disabled for a job the file history is generated at Restore time and not stored in the catalog.
When file history is turned off a Block level backup job, if you wish to restore by browsing the catalog the file history data will need to be generated; please see What does the message: "There is no data present in the catalog for this backup instance. Please click "OK" to browse the data from actual data snapshot." mean?