Topics | How To | Related Topics
Pruning Backup History Information
Content Indexing History Information
You can view the backup and restore history of iDataAgents, BackupSets/Instances, and subclients.
The Backup Job History Filter dialog box allows you view detailed, historical information about backup jobs. Once you have chosen your filter options, they are displayed in the Backup Job History window.
For information on Job Details displayed in the Job History, see Viewing Job Information.
From this window, you can right-click a backup job to:
The View backup file list option allows you to view a list of the files that were backed up during a backup job, along with the data sizes of each backed up file. The View backed up messages option allows you to view a list of messages that were backed up by using, along with the alias name, display name, email address, sender name, and recipient of each message.
From these windows you can conduct searches based on a particular string, allowing to find particular files quickly and easily.
|
|
It is not recommended that this option is used to view a very large list of items that were backed up (such as lists that total over 100,000 items). It is suggested that the Browse option is used to find a list of backed up items in such cases. |
See View the Items That Were Protected During a Data Protection Operation for step-by-step instructions.
The items that failed for a data protection operation include individual files that may fail the job even though a particular job completed successfully. You can determine the degree of success for these jobs using this window.
Filters can be used in conjunction with the "Items That Failed" list on the data protection Job History Report to eliminate backup or archive failures by excluding items which consistently fail that are not integral to the operation of the system or applications. Some items fail because they are locked by the operating system or application and cannot be opened at the time of the data protection operation. This often occurs with certain system-related files and database application files.
Also, keep in mind that you will need to run a full backup after adding failed files to the filter in order to remove them.
|
|
A listing of files and folders that failed is not available for the
Quick Recovery Agent, or the Image Level and Image Level ProxyHost
iDataAgents. These agents do not perform a file level
backup/copy. Certain application related files can never be backed up by the File System iDataAgent due to the nature of the data. For example, Microsoft SQL Server database files cannot be backed up by the File System iDataAgent. In this and other similar circumstances, consider entering files such as these as exclusions in the corresponding subclient filter. |
See View the Items That Failed For a Data Protection Operation for step-by-step instructions.
You can prune backup history information based on the number of days established in the Days to keep the backup job histories option from the Media Management Configuration (Service Configuration) dialog box available in the Control Panel.
|
|
If you have installed the SQL Server iDataAgent, do not use the stored procedure sp_delete_backuphistory, sp_delete_database_backuphistory and sp_delete_backup_and_restore_history provided by Microsoft clean up backup history. By default backup history is automatically pruned from the CommServe database and the Microsoft SQL Server, as necessary. |
Content Indexing history can also be viewed of iDataAgents, BackupSets/Instances, and subclients. The following information is displayed:
You can view the list of items that were successfully content indexed during a Content Indexing operation for a particular job. for step-by-step instructions, see View the Items that Were Successfully Content Indexed.
Content Indexing failures allows you to look at the messages, files and documents that could not be indexed during a content indexing operation. Content Indexing looks at each file (of the supported data types) and indexes its contents allowing advanced searches of backed up/archived/migrated data.
Files that were not indexed, (perhaps because the file’s content could not be read) are added to the Content Indexing Failures list, and are viewable from the View Content Index (Failed Items) option in the Job History window. For step-by-step instruction, see View the Items that Failed to Content Index.