This is simply good brother. But it will be always good if you provide more information like what to do if snapmirror is scheduled and local snapshot policies are there? Anyways this is good.
Good afternoon, by your response then the vol move will not use the LIF data, but the vol moves between user nodes the intercluster network, or cluster mgmt? Great video.
I hope intercluster lif is used for cross cluster replication. But here we do vol movement within a single cluster. Then either cluster lif should serve this purpose right?
You can follow the below steps and command Start the volume move by entering the following command: vol move start srcvol dstaggr [-k] [-m | -r num_cutover_attempts] [-w cutover_window] [-o] [-d] srcvol specifies the source volume. dstaggr specifies the destination aggregate. -k retains the source volume after a successful move. The source volume remains offline. -m specifies that the volume move does not initiate automatic cutover. The system continuously runs updates and you can initiate manual cutover at any point during the volume move. num_cutover_attempts specifies the number of cutover attempts. The minimum number of cutover attempts is one and the default number of attempts is three. If cutover cannot be completed in the specified number of attempts, then the volume move is paused. cutover_window specifies the duration of the cutover window. The default and minimum value is 60 seconds. -o displays warning messages on the console and the operation continues. -d runs all the data copy phase checks. If any of the checks fail, error messages are displayed on the console and the operation is terminated.
Very knowledgeable chapter..thank you..
Bro, you're doing good. Keep up the good work. Post videos on CIFS, NFS and other common troubleshooting.
Sure Sakthivelu Will try to make videos related to troubleshotting
Very nice elaboration.
This is simply good brother. But it will be always good if you provide more information like what to do if snapmirror is scheduled and local snapshot policies are there? Anyways this is good.
Thanks Pavan for the suggestion will keep that in mind on coming videos
Good afternoon, by your response then the vol move will not use the LIF data, but the vol moves between user nodes the intercluster network, or cluster mgmt?
Great video.
Its intercluster network. cluster management is for administration purpose.
I hope intercluster lif is used for cross cluster replication. But here we do vol movement within a single cluster. Then either cluster lif should serve this purpose right?
very descriptive video
Glad to know that you liked it.
Would the move operation execute via the cluster network or via the data?
Hey Anderato
The volume move happens from node to node hence its happens via cluster network
May I know the procedure to move volume to other aggregate in 7 mode?
You can follow the below steps and command
Start the volume move by entering the following command:
vol move start srcvol dstaggr [-k] [-m | -r num_cutover_attempts] [-w cutover_window] [-o] [-d]
srcvol specifies the source volume.
dstaggr specifies the destination aggregate.
-k retains the source volume after a successful move. The source volume remains offline.
-m specifies that the volume move does not initiate automatic cutover. The system continuously runs updates and you can initiate manual cutover at any point during the volume move.
num_cutover_attempts specifies the number of cutover attempts. The minimum number of cutover attempts is one and the default number of attempts is three. If cutover cannot be completed in the specified number of attempts, then the volume move is paused.
cutover_window specifies the duration of the cutover window. The default and minimum value is 60 seconds.
-o displays warning messages on the console and the operation continues.
-d runs all the data copy phase checks. If any of the checks fail, error messages are displayed on the console and the operation is terminated.
Dear all,anybody knows how can move volume from Netapp Cluster ontap 9.5 to Netapp 8.2 7-ModeThank you