When planning the configuration of SnapMirror, you need to consider the relevant restrictions.
- The source volume must be online.
For information about how to put a volume online, see the Data ONTAP Storage Management Guide for 7-Mode.
- For SnapMirror volume replication, the capacity of the destination volume must be greater than or equal to the capacity of the source volume.
For information about how to add disks to a volume, see the Data ONTAP Storage Management Guide for 7-Mode.
- For SnapMirror volume replication, if you create a large file after the last volume SnapMirror update, the file is deleted before the next update.
The time taken to delete the file depends on its size. Before all the blocks are freed, if you attempt volume SnapMirror update the blocks that are not freed are also transferred. This is because those blocks are captured in the volume SnapMirror created Snapshot copy.
- To support SnapMirror qtree replication, the destination volume must contain 5 percent more free space than the source qtree consumes.
- For SnapMirror qtree replication, the deleted file does not involve transferring of deleted block data to the destination.
- The SnapMirror destination volume cannot be the root volume of a storage system.
The SnapMirror source volume, however, can be the root volume.
- A destination qtree can be on the root volume, but the /etc qtree cannot be a destination qtree.
- A destination qtree name should not:
Note: When creating or specifying a qtree, you can use the space character in the qtree name. However, if you do so, you need to enclose the qtree name in double quotes. You can also use a double quote within a qtree name. The following example shows how to specify the qtree name, vol/vol1/x y"z, with both a space character and a double quote."systemA:/vol/vol1/x y""z"
- There must be a functional network to transfer data between two different storage systems.
- Each storage system model supports a specified number of snapmirror update command or vol copy command operations at a time.
- When you convert an aggregate that contains a volume SnapMirror destination into a Flash Pool, the destination volumes will not be cached.
Note: If you create a
Flash Pool with the same name as the
destination volume of a SnapMirror relation, the
subsequent SnapMirror updates fail.