If either or all the nodes are started before restoring the nodes, stop RMS. Perform the restoration procedure on either node that is started.
# hvshut -aIf all nodes are running before the restoration, select the latest disk. For all classes of GDS, execute the following command on either node.
# /etc/opt/FJSVsdx/bin/sdxnetdisk -S -c <class name>
Restore the virtual machine. To restore the snapshot or attach the Azure managed disk volumes, refer to the official Azure documentation.
Note
Instead of creating a new virtual machine, replace the system volume of the restoration target virtual machine with the restored volume.
After starting the node, execute the following on the restored node.
Delete the information of the iSCSI device.
# rm -f /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db
# rm -f /var/opt/FJSVsdx/log/.sdxnetmirror_timestamp
Stop RMS.
# hvshut -lRestore the other node if necessary.
Note
Instead of creating a new virtual machine, replace the system volume of the restoration target virtual machine with the restored volume.
When restoring the node in step 5, delete the iSCSI device information on the restored node.
# rm -f /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db # rm -f /var/opt/FJSVsdx/log/.sdxnetmirror_timestamp
If all nodes have stopped before the restoration, check the status of the slice that is the copy source of the synchronization copy. If the source slice for the synchronization copying is INVALID, restore the status of the slice. For the "-d" option of the "sdxfix " command, specify the source disk of the synchronization copying. Perform this procedure on either node.
# sdxfix -V -c <class name> -v <volume name> -d <disk name> -x NoRdchk
If the virtual machine name is changed in step 3 or step 5, perform step 2 to 4 described in "27.8.1.2 Setting up the Shutdown Facility" on all nodes, and modify the ResourceID of the hvazurenicconfig file created in "27.9.1.1 Creating the Definition File."
If 2 of step 4 is performed, start RMS on the node where RMS is stopped.
# hvcm