Dear team,
We are planning to move our storage from one Rack to another.
it's a small storage total usable capacity is 3TB (EMC CX4-120). created one LUN size of 3TB and mapped the same to 14 ESXi host.
That LUN is selected as heartbeat datastore. we will follow below POA to perform said activity.
-> Select Home => datastore & datastore clusters => Select datastore => Virtual machine => take VMs export
=> gracefully shutdown all VMs which are hosted on this datastore (non production vms no need to migrate the same on other datastore)
=> select different datastore for datastore heart beat (Need ur help how to do that)
=> remove this datastore from datastore heartbeat (Need ur help how to do that)
=> Unregister all VMs (Please confirm do i need to unregister VMs ???)
=> unmount and detach then unmap the datastore from Storage end (if i remap the same on all esxi host will i able to see the data onit, I don;t want to loose data)
=> gracefully shutdown the SAN storage
=> Disconnect cables from storage.
=> Move the storage from rack1 to rack2
=> Connect cables and poweron the storage
=> attach and mount the datastore on all esxi host
or if i unmap the datastore before activity then map the same datastore on all 14 esxi host and rescan the HBA
=> mount the datastore on all esxi host and it will be visible on all esxi host
=> register all vms
=> Poweron & check all network connection.
=> Handover to application team.
point which are marked as bold need asisstance on the same , also add missing steps if any.
regards
Mr VMware
Please find the right steps
above POA is 100% okay and tested.
before activity take VM export which are stored on datastore
Home => datastore and datastore cluster => select the datastore => VMs => add all the columns => take VM export
take latest RVTool export.
shutdown all VMs => Unregister all VMs and Templates => RK on Cluster (edit setting => datastore hearbeating => here we have to select another datastore and click on OK)
to confirm new datastore is visible as datastore heartbeat select Cluster=> Sumamry => Custer Status => Heartbeat Datastore )
if we are able to see new datastore then now remove old datastore from datastore heartbeat
RK on Cluster (edit setting => datastore hearbeating => here we have to uncheck datastore and click on OK)
unmount => detach(need to perform this step on all esxi host) => san team will unmap => start storage movement activity (poweroff storage) => move the storage => poweron => san team will map the datastore =>attach((need to perform this step on all esxi host) => mount the datastore
Register all VMs
Poweron All VMs if get message (moved it or copied it ) select Moved it.
if above steps followed then it won't throw any error, will work seemlessly.
Yes we need to unregister all VMs and Templates before unmount a datastore.
regards
Mr VMware
Please find the right steps
above POA is 100% okay and tested.
before activity take VM export which are stored on datastore
Home => datastore and datastore cluster => select the datastore => VMs => add all the columns => take VM export
take latest RVTool export.
shutdown all VMs => Unregister all VMs and Templates => RK on Cluster (edit setting => datastore hearbeating => here we have to select another datastore and click on OK)
to confirm new datastore is visible as datastore heartbeat select Cluster=> Sumamry => Custer Status => Heartbeat Datastore )
if we are able to see new datastore then now remove old datastore from datastore heartbeat
RK on Cluster (edit setting => datastore hearbeating => here we have to uncheck datastore and click on OK)
unmount => detach(need to perform this step on all esxi host) => san team will unmap => start storage movement activity (poweroff storage) => move the storage => poweron => san team will map the datastore =>attach((need to perform this step on all esxi host) => mount the datastore
Register all VMs
Poweron All VMs if get message (moved it or copied it ) select Moved it.
if above steps followed then it won't throw any error, will work seemlessly.
Yes we need to unregister all VMs and Templates before unmount a datastore.
regards
Mr VMware