Best practices for the Archiving Option

Following are best practices when you use the Archiving Option:

  • Use the default full recovery model for the SQL Server instance that hosts the Backup Exec Database and the Archiving Option databases. All Archiving Option databases that are created on the SQL Server are then also created with the full recovery model.

  • Create only one archive job for each server from which you want to archive the data that has been backed up.

  • Do not use different media servers to archive files or mailboxes from the same file server or Exchange server.

  • Configure backup jobs so that full backups and their associated incremental and differential backups use the same selection list.

  • Run archive jobs outside the backup window. That is, don’t run archive jobs at the same time that you run backup jobs.

  • Consider archiving a smaller amount of data at first, such as a mailbox or a folder. All backup data may be eligible when you run the first archive job. Over a period of time, the amount of eligible archive data lessens, and it becomes a predictable amount.

  • Select the file system shares to archive that end users have access to rather than administrative shares. End users can then retrieve their own data by using Backup Exec Retrieve.

  • Ensure that a selection is included in only one archive job. Unlike backup jobs, archive jobs cannot share the same selections.

  • Ensure that all subdirectories in a selection are included in only one archive job.

  • Do not archive the system drive. The Archiving Option does not archive system files.

  • If you restore multiple Archiving Option components that include the Directory database, use a separate job to restore the Directory database first. Then, create one job for all of the remaining Archiving Option components that you want to restore.

  • If you restore multiple backup sets to restore a database, use a single restore job and leave the database ready to use.

  • If you redirect the restore of Archiving Option components to a new server because of hardware failure, redirect the restore of the Directory database first. Create a separate job to redirect the restore of the database. After the redirected restore of the Directory database is complete, you must run some additional tasks in a separate program called Backup Exec Utility. The tasks in the Backup Exec Utility update the Directory database with the new locations of the components. You should run the Backup Exec Utility tasks before you redirect the restore of any other Archiving Option components.

Best practices for the Archiving Option