ONTAP Hardware

Volume Move same one cluster

DhonaAgungP
3,343 Views

Hello Guys,

Maybe somebody any experience for same this case?
15.jpg21.jpg16.jpg

Please give me step for troubleshoot.

1 ACCEPTED SOLUTION

paul_stejskal
3,283 Views

How is performance on the source/destination node? That first one will need to finish first. The other possibility could be BRE throttling, which is expected if latency is higher.

 

Lastly, how much i/o is going on with that volume? It might be so busy it can't finish a cutover.

View solution in original post

8 REPLIES 8

paul_stejskal
3,284 Views

How is performance on the source/destination node? That first one will need to finish first. The other possibility could be BRE throttling, which is expected if latency is higher.

 

Lastly, how much i/o is going on with that volume? It might be so busy it can't finish a cutover.

DhonaAgungP
3,195 Views

Hello Paul,
after we check performance source destination node 

DhonaAgungP_0-1725340270583.png

 

JonathanGaudette
3,268 Views

Run 
::> vol move show -instance
to see the actual "warning" state

DhonaAgungP
3,195 Views

hello Jonathan,

Fyi

DhonaAgungP_1-1725340496991.png

 

DhonaAgungP
3,195 Views

DhonaAgungP_2-1725340623388.png

where can i check snapshot capacity in node aggr_SASInternal

?

paul_stejskal
3,120 Views

There may be room on disks but it could be reserved. Why are you moving to an already full aggregate? ONTAP won't perform well with being full.

DhonaAgungP
3,095 Views

because i do volume move for replace node/aggr_SAS1800G_1. If I provide allocations in Aggr_SASInternal, the running process will continue?

paul_stejskal
3,014 Views

That or free space up. If you're upgrading nodes the account team/Professional Services should be able to fix that.

Public