SnapManager Backup uses Snapshot copy functionality to create online, read-only copies of databases. After the selected databases are backed up, the transaction logs that are already committed to the databases captured in the backup are deleted.
SnapManager Backup performs backups at the volume level:
Volume-wide backup When a Snapshot copy is made of a LUN, SMB share, or VMDK for a SnapManager backup, the entire volume is captured in that Snapshot copy. However, that backup is valid only for that server. If data from other servers resides on the same volume, it is not restorable from that Snapshot copy.
Multiple-volume backups SnapManager performs backups in parallel on all LUNs, SMB shares, or VMDKs that belong to the same server and share a single storage system volume. When a database set spans multiple volumes, the resulting backup set contains multiple database Snapshot copies but is still restorable as a single entity.
Partial backups If the backup of some of the databases in the database set fails, the databases in the set that were backed up successfully can still be restored. Because each database constitutes its own backup, or file, it is restored discretely, independent of backups of the others in its backup set, even though the backup of all databases in the set was performed by the backup job.
SnapManager performs the following tasks when creating a backup:
Creates a new directory in the SnapInfo directory for this backup
Be aware of the requirements and limitations of SnapManager Backup:
HKEY_LOCAL_MACHINE\SOFTWARE\Network Appliance\SnapManager for SQL Server\Server\HaveDBWithTrailingSpaces