You can migrate a volume that contains SnapVault destination qtrees from one secondary system to a tertiary system without having to perform a baseline transfer.
Before you begin
Ensure that you have Open Systems SnapVault baselines. For example, in the following procedure, consider a baseline of the
bno:C:\500MB directory was backed up to
system-old:/vol/old_vol/bno_C_500MB.
Steps
- Using SnapMirror, replicate the volume from the present secondary system to a volume on the new secondary system.
Example
To replicate the old_vol volume from the system-old secondary system to the new_vol volume on the system-new secondary system, complete the following steps on the new secondary system (system-new).
- Create the new_vol volume.system-new> vol create new_vol 3
- Mark the new_vol volume restricted.system-new> vol restrict new_vol
- Transfer the old_vol volume to the new_vol volume.system-new> snapmirror initialize -S system-old:old_vol new_vol
- Quiesce and break the SnapMirror relationship between the old secondary system and the new secondary system.
Example
To quiesce and break the SnapMirror relationship between system-old and system-new, complete the following steps on system-new.
- snapmirror quiesce new_vol
- snapmirror break new_vol
- Check the SnapMirror status and SnapVault status on the new secondary system. SnapMirror status should be Broken-off. SnapVault status should be Snapvaulted to the new volume on the new secondary system.
Example
Perform the following steps from system-new.
- snapmirror status
Source Destination State
system-old:old_vol system-new:new_vol Broken-off
- snapvault status
Source Destination State
bno:C:\500MB system-new:/vol/new_vol/bno_C_500MB Snapvaulted
- Confirm that SnapVault configuration information is not present on the new secondary system by using the snapvault status -c command.
Example
Perform the following step from
system-new.
snapvault status -cSnapvault is ON.
- Enable access to the new SnapVault secondary system from the SnapVault primary system using the options snapvault.access command.
Example
Perform the following step from system-new. options snapvault.access host=system-old
Note: When using SnapVault, access needs to be specified on both the primary and secondary systems.
- Add SnapVault configuration information to the registry on the new secondary system using the snapvault start command.
Note: This does not start a new baseline, it updates the registry.
Example
Perform the following step from
system-new.
snapvault start -S bno:C:\500MB system-new:/vol/new_vol/bno_C_500MBSnapVault configuration for the qtree has been set.
Qtree /vol/new_vol/bno_C_500MB is already a replica.
- Confirm that SnapVault configuration information is present on the new secondary system using the snapvault status -c command.
Example
Perform the following step from
system-new.
snapvault status -cSnapvault is ON.
/vol/new_vol/bno_C_500MB source=bno:C:\500MB
- Test the new SnapVault relationship by manually updating system-new.
If you are using the CLI to manage your environment, continue to the next step; otherwise, you have completed the task.
Example
Perform the following step from
system-new.
snapvault update system-new:/vol/new_vol/bno_C_500MBTransfer started.
Monitor progress with ‘snapvault status’ or the snapmirror log.
- Re-create any schedules used on the old secondary system to the new secondary system and ensure access permissions are in place.