Guidelines for archiving SnapManager backups

Before you start archiving your data, consider the guidelines for choosing the type of data to be archived, naming, and using the appropriate protocols.

Archive only verified backups.
If you are not sure whether a backup copy is verified, use the SnapManager Restore window to check.
Archive a complete backup set.
Archive the most recent backup copy.
Archive all Storage Groups together.
Do not archive individual Storage Groups or databases unless you know which Snapshot copies contain the appropriate Storage Groups and transaction logs for a specific time.
Keep in mind that single backup version is used during backup archiving when multiple storage groups or databases are selected to create a backup. This means that a backup version in Protection Manager includes backups from multiple storage groups or databases. When deleting a remote backup, all backups in that backup version will be deleted.
If you use the unique naming convention, look for the Snapshot copy with the most recent date and time.
If you did not use the unique name option when you created the backup, look for the most recent Snapshot copy in the storage system’s LUN drive volume named
/exchsnap_servername_recent

or

/exchsnap_servername_recent_backupmgmtgroup.

This is for backward compatibility with earlier versions of SnapManager, which did not include the Run Command After Operation feature.
Do not use the CIFS or NFS protocols to archive LUNs.
Use the storage system’s dump command or an NDMP backup application to archive LUNs.

Note: If the system is busy, the network is slow, or the load is primarily on the DataFabric Manager server or the storage system, there is a time lag between the creation of a backup and the appearance of the archive in the Restore view.
Consider the following factors:
- The archive method you use
- Service Level Agreements for disaster recovery
- The number of SnapManager backups performed per day
- Exchange client activity schedules
- Backup verification time