Considerations before backing up a CCR replica database and production database

Before you back up a CCR replica database and production database, you need to make some considerations about the use of active and passive nodes in your CCR configuration.

When you perform an operation such as adding, reconnecting, or removing a CCR-enabled Exchange server, the operation applies to both the active and passive nodes together.
You can back up your Storage Group from either the active node or the passive node.
- You cannot connect to the active nodes and passive nodes at the same time and perform backup operations on both the nodes simultaneously.
- If you do not select the option Create a copy database on another CCR node along with current backup, then you only back up the CCR node that you are connected to, which is either an active node or a passive node.
- When you rename a Storage Group, you must unmount all of the databases in that Storage Group. After you unmount all of the databases, you can remount them.
  At this point Exchange recognizes the new Storage Group name, and you can create new SnapManager backups of this Storage Group.
When you back up a CCR configuration, SnapManager creates full database backups either on a CCR active node, using Exchange Store Writer, or on a CCR passive node, using Exchange Replication Writer.

Note: SnapManager does not perform any special operation to delete the log files on a replica database after the production database backup in a CCR environment. When a backup is created on a CCR replica database, Exchange Writer handles the truncation of the log files automatically, on both the production and the replica databases.