Using extended queries to operate on many SnapMirror relationships
You can use extended queries to perform SnapMirror operations on many SnapMirror relationships at one time. For example, you might have many uninitialized SnapMirror relationships that you want to initialize using one command.
What tape seeding is Tape seeding is an SMTape functionality that helps you initialize a destination FlexVol volume in a data protection mirror relationship.
Performing tape seeding using SMTape
Using SMTape, cluster administrators can perform tape seeding to initialize a destination FlexVol volume in a data protection mirror relationship. The time taken to initialize this destination volume over a low bandwidth connection using SMTape is faster when compared to using the snapmirror initialize command.
Scalability limits for SMTape backup and restore sessions
While performing SMTape backup and restore operations through NDMP or CLI (tape seeding), you must be aware of the maximum number of SMTape backup and restore sessions that can be performed simultaneously on storage systems with different system memory capacities. This maximum number depends on the system memory of a storage system.
Scheduling SnapMirror transfers
If you want scheduled SnapMirror transfers, you can add a schedule to a mirror relationship after you initially create the relationship.
Changing mirror relationship schedules
You can change a schedule that updates mirror relationships for FlexVol volumes and Infinite Volumes if the schedule impacts other backups or updates.
Manually updating data protection mirror copies on destination volumes
You can schedule updates to data protection mirror copies for destination FlexVol volumes or Infinite Volumes, or you can manually update a data protection mirror copy to transfer Snapshot copies between the source and destination volume. However, for Infinite Volumes, you cannot choose which Snapshot copies to transfer.
Deleting a mirror copy
You can delete a mirror relationship and the destination FlexVol volume or Infinite Volume if you no longer want the mirror copy.
Considerations when breaking SnapMirror relationships
You might break a SnapMirror relationship when a disaster impacts the source volume so that you can temporarily serve data from the destination volume. There are some considerations you should understand before breaking a SnapMirror relationship so that you can avoid issues.
Reversing the data protection mirror relationship when disaster occurs
When disaster disables the source FlexVol volume of a data protection mirror relationship, you can use the destination FlexVol volume to serve data while you repair or replace the source, update the source, and reestablish the original configuration of the systems.
Reversing the version-flexible SnapMirror relationship when disaster occurs
When disaster disables the source FlexVol volume of a version-flexible SnapMirror relationship, you can use the destination FlexVol volume to serve data while you repair or replace the source, update the source, and reestablish the original configuration of the systems.
Converting a data protection mirror destination to a writeable volume
You can convert the destination volume of a data protection mirror relationship to a writable volume if you want to use that volume to serve data. For example, you might do this if you want to migrate a volume.
Testing database applications
You can use data protection mirror relationships to create a copy of database data on which to test software applications that run on a database, to avoid the possibility of changing or corrupting the database.
