Convert snapvault to snapmirror

PRICLU2::> snapmirror break -destination-path PRICLU2V1:v_TEST01 Error: command failed: “snapmirror break” not supported for “XDP” relationships. PRICLU2::> snapmirror delete -destination-path PRICLU2V1:v_TEST01 PRICLU2::> snapmirror create -source-path PRICLU1V1:v_TEST01 -destination-path PRICLU2V1:v_TEST01 -type DP -schedule 1minutely -policy DPDefault PRICLU2::> snapmirror resync -destination-path PRICLU2V1:v_TEST01 Warning: All data newer than Snapshot copy 1minutely.2014-07-03_2031 on volume PRICLU2V1:v_TEST01 will be deleted. Do you want to continue? {y|n}: y PRICLU2::> snapshot show -volume v_TEST01 -snapmirror-label 1minutely —Blocks— Vserver Volume Snapshot State Size Total% Used% ——– ——- ——————————- ——– ——– —— —– PRICLU2V1 v_TEST01 1minutely.2014-07-03_1958 valid 68KB 0% 29% … 1minutely.2014-07-03_2051 valid 76KB 0% 31% 54 entries were displayed.

Migrate VSC to other server

Perform the following steps: Stop the NetApp SnapManager for Virtual Infrastructure service. Copy the C:\Program Files\NetApp\Virtual Storage Console\SMVI\server\repository directory to a safe location. Uninstall old instance of VSC. After the old instance of VSC has been removed, the new install of VSC on new server can be performed. On the new server, perform the new installation of Virtual Storage Console: Download the VSC installer from the NetApp Support Site. Right click the VSC installer file and select ‘Run as Administrator’ to start the installation wizard. Follow the instructions in the installation wizard to install the software. Note: If you want to install Backup and Recovery, select that option. Otherwise, the VSC installerRead More

Convert snapmirror to snapvault

Steps Break the data protection mirror relationship by using the snapmirror break command. The relationship is broken and the disaster protection volume becomes a read-write volume. Delete the existing data protection mirror relationship, if one exists, by using the snapmirror delete command. Remove the relationship information from the source SVM by using the snapmirror release command. (This also deletes the Data ONTAP created Snapshot copies from the source volume.) Create a SnapVault relationship between the primary volume and the read-write volume by using the snapmirror create command with the -type XDP parameter. Convert the destination volume from a read-write volume to a SnapVault volume and establish the SnapVault relationship byRead More

Can’t delete a volume as a SnapVault secondary volume

Symptoms When trying to delete a secondary volume from DataFabric Manager (DFM), the following error is reported: C:\>dfm volume delete 12345 Error: Can’t delete volume filername:/volname (12345) as a SnapVault secondary volume. Solution Because this is a secondary volume, use dfbm secondary volume delete against the offending volume, then use dfm volume delete against the offending volume: C:\>dfbm secondary volume delete 12345 C:\>dfm volume delete 12345 This should successfully remove the secondary volume from DFM.