LCR-enabled database backups

SnapManager allows you to back up and schedule a database from either its Local Continuous Replication (LCR) copy location or its original location. Ensure that you do not create a backup on the replica database and its production database at the same time.

Using either the SnapManager Backup and Verify window or the Backup wizard, you can view the replica Storage Group simultaneously with its production Storage Group. The replica Storage Group is represented as an LCR Storage Group on the SnapManager graphical user interface.

Note: You must use different volumes to store the database files, the transaction log files of the replica Storage Group, and the production Storage Group.

When SnapManager creates a backup on the production database and its replica database at the same time, SnapManager creates two successive sets of timestamps, one for each backup operation. Only one of the backups has the recent backup name, if you select the generic naming convention in Backup Settings. Two copies of the backup set are created that consume extra storage space in the LUN.

Note: SnapManager does not perform any special operation to delete the transaction log files on a replica database after making the backup on the production database. When you create a backup on an LCR-enabled database, Exchange Writer handles the truncation of the log files automatically, on both the production and the replica databases.