Renaming a SnapVault or Open Systems SnapVault secondary volume
SnapVault or Open Systems SnapVault
updates do not work if a SnapVault or Open Systems SnapVault secondary (destination) volume is renamed.
Considerations
If the qtree is not configured in SnapVault, using the snapvault start command to configure the qtree gives the following error:
Error: Not a snapvaulted qtree, ignoring.
The qtree is not a SnapVault qtree replica.
Steps
Enter the following command:vol rename oldvolnamenewvolname
To verify the changes, enter the following commands:snapvault status
snapvault status displays the new path.
Enter the following commands to verify the changes: snapvault status -c
snapvault status -c does not show the new path yet.
Enter the following command:snapvault start -Spri_filer:pri_qtree sec_filer:sec_qtree
Snapvault configuration for the qtree has been set.
Qtree /vol/newvolname/sec_qtree is already a replica.
Enter the following command: snapvault status -c
Note:snapvault status -c now shows the new path.
Enter the following command to verify whether the change was successful: snapvault update sec_qtree
The output of snapvault status -c will contain entries referencing the old volume name in addition to the new volume name. Remove these entries using the snapvault stop command: snapvault stop /vol/oldvolname/sec_qtree
Snapvault configuration for the qtree has been deleted.
Could not delete qtree: destination qtree does not exist The output reflects that the configuration information is deleted and that the qtree did not exist on disk. This is normal because the volume name has changed.