Topics | How To | Related Topics
How to Set Up and Run a Migration Archive Operation
Migration Archiving Considerations
This section discusses archive information that is specific to the SharePoint Archiver Agent. See Migration Archiving for a general overview.
During archive operations, the SharePoint Archiver Agent will archive versioned and non-versioned documents that meet the preset criteria specified in the Archiving Rules tab of the Subclient Properties dialog box. Information about each archived object is placed into a stub (when enabled) that can then be used as a link to recover the data.
The configuration of the archiving rules is central to customizing archive operations to meet the needs of your organization. Continue on to the following section for an in-depth discussion of the archiving rules for these agents.
The following section provides the steps to set up and run a Migrate Archive Operation:
By default, this option is disabled. When selected, all archiving rules will be enabled except for Stub Rules. |
Before performing any archive procedure, review the following information:
When SharePoint Archiver archives data, it creates a database file to track the stubs that will appear in the SharePoint user interface. Stubs contain information about the archived data for recovery purposes. This file, SPDAStubDatabase.db, resides in the Job_Results folder and is not backed up with the SharePoint Database iDataAgent. Therefore, you should back up this file with the Windows File System iDataAgent to ensure that stubs can be recovered.
For successful archiving and recovery, the user performing the operation must have write permissions to the SPDAStubDatabase.db file that resides in the Job_Results folder. Otherwise, you may receive the error Failed to update database with new version number.
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.
In a SharePoint environment with more than 500 site collections, it is recommended to increase the size and number of log files with the <logfile>_MaxLogFileSize and <logfile>_MaxLogFileBackups registry keys. Replace <logfile> with any desired name (e.g., SPDBBackup, SPDocBackup, SPDocArchive, etc.).