Table of ContentsLibraryView in Frames

Configuring SnapManager in a CCR-enabled Storage Group

You can configure SnapManager in a Storage Group that has Cluster Continuous Replication (CCR) enabled.

Before you begin

Keep the name of the verification server ready.

About this task

SnapManager migrates a Storage Group or database from one location to another on both CCR nodes, because both nodes use the same database path.

SnapManager migrates transaction logs from one location to another on both CCR nodes. The transaction log path is same for both the active and the passive nodes.

The SnapInfo directory path is similar for both active and passive nodes.

You should configure your Microsoft iSCSI service as a dependency for the Microsoft Exchange System Attendant so that Microsoft Exchange cannot start before the Microsoft iSCSI service is ready to accept connections.

After you complete the Configuration wizard, you can also view or change the Notification settings using the Auto Notification Settings in the Actions pane. You should enable all of the automatic event notification options. When you enable automatic event notification, if any problems occur with the SnapManager backups, you are alerted and can take immediate corrective action.

If you are moving the location of Exchange databases, it could take some time to complete.

Steps

  1. In the Scope pane, double-click SnapManager for Exchange.
  2. Click the Exchange server that is CCR-enabled, and for which the database seeding is complete.
  3. In the Actions pane, click Configuration Wizard.
  4. In the Database Verification Server window, specify the Exchange server to be used to perform Exchange database verification.
    1. If you want to specify the database verification server now, type the name of the Exchange server or browse to an Exchange server in the Verification Server window, or select Select a verification server later.
  5. In the Select a Storage Group/Database to move to a LUN window, associate your CCR-enabled Exchange Storage Groups or databases with the correct LUNs, according to your SnapManager data configuration plan.
  6. In the Select a set of logs from one or more Storage Groups/Databases to move to a LUN window, associate your transaction logs with the correct LUNs, according to your SnapManager data configuration plan.
  7. In the Configure the SnapInfo directory to store the backup information window, select the SnapInfo files, and the LUN to which you want to move them and click <=>.
  8. If you are installing SnapManager on a system that has the Microsoft iSCSI initiator installed, select whether you want to configure your Microsoft iSCSI service as a dependency for the Microsoft Exchange System Attendant.
  9. In the Configure Automatic Event Notification (Recommended) window, configure the automatic Simple Mail Transfer Protocol (SMTP) e-mail notification for event notification, enable Syslog (storage system event log) support, enable AutoSupport for SnapManager, and limit event logging to failure events.
  10. Review the configuration summary in the Completing the Configuration Wizard window, and click Finish.
  11. To migrate your databases, and their transaction logs and SnapInfo files to the LUNs you specified, click Start Now.
  12. Click OK.

After you finish

Create a SnapManager Backup immediately.

Related concepts
Considerations for selecting the database verification server
Why SnapManager uses NTFS hard links for transaction log archiving
Support for multiple SnapInfo directories
Database backup using SnapManager
Related tasks
Configuring automatic event notification settings
Related reference
Windows host system requirements