Sie sind auf Seite 1von 2

Move a destination Qtree SnapMirror or SnapVault from one volume to another without requiring a new baseline transfer between

primary and secondary


Symptoms
Traditional volume to flexible volume migration Maintain SnapVault relationship Maintain Qtree SnapMirror relationship Move a destination Qtree SnapMirror or SnapVault from one volume to another without requiring a new baseline transfer between primary and secondary

Solution
There are several techniques that can be used to move Qtree SnapMirror, SnapVault, and/or OSSV destination data from one volume to another while maintaining the replication relationship. Note: In Scenario 1, destination Snapshots are moved. In Scenarios 2 and 3, it is not possible to move destination Snapshots.

Scenario 1
Moving an entire replication destination volume within a storage system, or to another storage system. The replication destination volume may contain multiple qtrees. The volume type remains the same, for example, traditional to traditional or FlexVol volume to FlexVol volume.

The solution steps for Scenario 1 are described in the following documents:

1. 2.

Migrating between two volumes on one secondary storage system Migrating a relationship between two secondary storage systems Note: Although the steps above are found in the OSSV Installation and Administration Guide, they are also valid for volumes containing Qtree SnapMirror and SnapVault destination qtrees.

Scenario 2
If moving individual Qtree SnapMirror, SnapVault, or OSSV destination qtrees from one destination volume to another, and sufficient network bandwidth is available between the source and the new destination, NetApp recommends initializing a new relationship. The replication relationship with the original destination volume can then be broken or stopped in accordance with customer retention policies. Instructions on how to start a new replication relationship are found in the relevant administration guide.

Scenario 3
When moving individual Qtree SnapMirror or SnapVault qtrees from one destination volume to another, and network bandwidth between the source and the new destination is limited, the steps below can be used. A common use of this procedure would be to migrate a destination qtree from a traditional volume to a flexible volume, while maintaining its SnapVault or Qtree SnapMirror relationship. The recipe gives a Qtree SnapMirror example. For a SnapVault example, you must run the before and after commands as explained in the recipe. Due to the use of SnapMirror on the primary system, qtrees SnapVaulted from OSSV hosts are not supported.

CAUTION: The procedure described below is complex and contains steps that are prone to human error. It is intended for experienced administrators only and caution should be used.

Please note there is downtime required on the source for the duration of the local initialize on the destination.

A SnapMirror license is always required for the recipe, likewise a SnapVault license is required in a SnapVault scenario. Before executing this recipe, be sure the filer running a release that is not susceptible to BUG 151450. Environment Existing relationship: pri:/vol/tradvol/qtree > sec:/vol/tradvol/qtree Desired relationship: pri:/vol/tradvol/qtree > sec:/vol/flexvol/qtree Recipe If you are running SnapVault, please see the "Notes for SnapVault" section below. Stop client access to qtree data on pri. Failure to stop client access can result in data loss. sec> sec> sec> pri> sec> sec> pri> pri> pri> snapmirror update -w -S pri:/vol/tradvol/qtree /vol/tradvol/qtree snapmirror quiesce /vol/tradvol/qtree snapmirror break /vol/tradvol/qtree snapmirror resync -f -w -S sec:/vol/tradvol/qtree /vol/tradvol/qtree snap create tradvol common_snap snapmirror initialize -w -s common_snap -S /vol/tradvol/qtree /vol/flexvol/qtree snapmirror update -w -s common_snap -S sec:/vol/tradvol/qtree /vol/tradvol/qtree snapmirror quiesce /vol/tradvol/qtree snapmirror break /vol/tradvol/qtree

Allow client access to qtree data on pri sec> snapmirror quiesce /vol/flexvol/qtree sec> snapmirror break /vol/flexvol/qtree sec> snapmirror resync -f -w -S pri:/vol/tradvol/qtree /vol/flexvol/qtree Notes for SnapVault Before executing the recipe, enter the following commands: sec> options snapvault.enable off sec> options snapmirror.enable off sec> priv set diag sec*> snapmirror convert /vol/tradvol/qtree sec*> priv set sec> options snapvault.enable on sec> options snapmirror.enable on After recipe, enter the following commands: sec> options snapvault.enable off sec> options snapmirror.enable off sec> priv set diag sec*> snapvault convert /vol/flexvol/qtree sec*> priv set sec> options snapvault.enable on sec> options snapmirror.enable on sec> snapvault modify -S pri:/vol/tradvol/qtree sec:/vol/flexvol/qtree Note: The first SnapVault update may fail with the error, "destination qtree is not coalesced." If you encounter this error, try an update again and it will succeed

Das könnte Ihnen auch gefallen