Table of ContentsView in Frames

SnapLock interaction with SyncMirror and MetroCluster configuration

As with any volume on a mirrored aggregate, a MetroCluster configuration enables SnapLock volumes to be mirrored from one site to another while retaining the SnapLock characteristics, assuming that the sites have been properly configured.

The primary node might have data that was not mirrored before using the cf forcetakeover –d command. For example, the data might have been written to the primary node while the link between the sites was inoperative. In such a case, you should back up the SnapLock volumes in the aggregate on the primary site before resynchronizing the two mirror aggregates. This step of creating an additional backup for the SnapLock volumes is required to ensure the availability of all data.

Splitting a mirrored aggregate removes the relationship between the two plexes and creates two independent unmirrored aggregates. After splitting, both the aggregates come online.

Attention: When you rejoin the split aggregates, Data ONTAP mirrors the data from one aggregate to another and destroys the data that existed on that aggregate before the rejoining.

For more information about split aggregates and rejoining the split aggregates, see the Data ONTAP Data Protection Online Backup and Recovery Guide for 7-Mode.

However, if you are planning to use both SnapLock and MetroCluster configuration together, see the Data ONTAP High Availability and MetroCluster Configuration Guide for 7-Mode.