If your SnapManager backup fails, check the backup report to determine the cause of the failure.
Problem: cluster failover during backup
If a cluster failover or a Windows cluster move group happens during a backup operation, the backup fails, and you need to restart the backup operation.
Problem: Snapshot copy limit reached
You get an error message if you try to back up a LUN that contains more than 255 Snapshot copies. The backup operation fails irrespective of whether SnapManager created the Snapshot copies or not.
Problem: SnapInfo directory out of space
You get an error message if your SnapInfo directory runs out of space. Expand the LUN that contains the SnapInfo directory and ensure that enough space remains in the volume for Snapshot copy creation.
Problem: data does not match
You get an error message if you make changes to your Exchange Server storage groups and databases after SnapManager started and you did not refresh your view. You can refresh your view by pressing F5, or you can restart SnapManager.
Problem: busy Snapshot copy
You get an error message if you back up a LUN when a Snapshot copy of the LUN already exists and then you try to delete a Snapshot copy of the LUN. Event 249 is logged by SnapDrive and SnapManager backups fail.
Problem: Snapshot copy already exists
You get an error message either if the system clock on the SnapManager host is not synchronized with the storage system clock or if SnapMirror replication is running when you try to start a backup operation.
Problem: out of disk space
You get an error message when the database or the transaction logs use all of the available disk space in a volume. Resize the volume or expand the LUN.
Problem: SnapManager server initialization failed
You get an error message either if the SnapManager server account or the server account permissions have changed; or if you exit SnapManager when the smesrvr.exe process is running.
