[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1605
  • Last Modified:

Moving SAN BOOT Volume from one storage to another

We are planning to replace our netapp FAS6200 to new one FAS6200 storage (same model but bigger capacity). Question is our Vmware host bootvolume is kept on the old Storage, and that will also get moved or migrated to the new storage server.
Netapp suggested to use Vol move command for all the luns and Datastore cluster. As they said it will not affect anything on our production host and it does not required any down time. is anybody has done this kind of migration ?
what precaution we should take or any problem we may see during this activity ?
Thanks in advance.
haresh n
Haresh Nikumbh
Haresh Nikumbh
3 Solutions
vcenter DHCP accomodates the change. Just dont start new ESXis when move is in progress.
Haresh NikumbhAuthor Commented:
Sorry didnt get you can you please explain me in brief ?

as per netappp this migration will be happen in live .. so we do not have to shutdown our host.. after migration we do not have to make any changes on the host as vol move command will work on netapp level
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, we've done this migration.

I would test this first using a test volume which contains the iSCSI LUNs.

Also make sure, that there are no changes required for the initator groups.

I assume this is the same SAN, and IP Address, you are just moving the volume to a new Aggregate ?
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

Haresh NikumbhAuthor Commented:

that's what we are planning, first we will move less utilized volume (Datastore volume ) on the new san, and see how they perform on the new storage.

after that we will take boot volume, but the question is do we have to make any changes on vcenter or vmware side? can this  task done in live mode? do we need to have plan B if anything goes wrong during this movement ?

I believe IP address will be changed as both SAN will be live at a same time.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It's ALL SAN related, there is nothing to change on vCenter Server or the host.

It's all SAN volume move related.

Personally, we would do the following:-

1. Create new volumes on new SAN storage.
2. Create new LUNs in new volumes.
3. Add new datastores to ESXi hosts.
4. Test new datastores
5. Once tests have confirmed new storage is good, performs well etc
6. Migrate VMs using Storage vMotion LIVE
(that's what Storage vMotion is designed to do, move between storage)

I have no idea what the configuration of your new storage is, so have no idea, if is the same, faster, slower, SAS, SATA, SSD etc

The above gives you a test plan, role back.....

if you just MOVED the vol, there is no role back.....

So this is going from SAN1 to SAN2 ?

you will need to add IP Address to each ESXi host, add the IQN groups, and initiators to new SAN2.

then you will need to accept and possible re signature the LUNs.

Are you or NetApp Support doing the Project and implementation?
Haresh NikumbhAuthor Commented:
the plan 1 to 6 which you have mention is the same which we are going to follow..

but i still have question for VMWARE host (which are booting from SAN), that will also get moved to new storage using vol move command from NETAPP. do you have any suggestion for that?

about storage its netapp FAS6200 , same model, only change is old storage was having 450GB SAS drive, and new one came with 600 GB SAS drive

Our old storage was having some faulty disk which was causing performance issue,
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Again, the same, the ESXi hosts will have to be re-configured to point to the new IP Address, and the IQN copied across and mapped to LUN 0 for each ESXi host, if iSCSI

if FC, you will need to map new WWNN hbas to the LUNs.

You cannot do Storage vMotion here, so you will need to move the volumes, containing the LUNs.
As I know that you can move vol non-disruptively between two aggregate only  if they are in same filer and vol move is not going to work if it is NFS datastore.
Your case you have two filer and two separate aggregate. The lun is going to be in new ip once you moved then you have to map this lun to your esxi.
I will go for Andrew's step1-6 with shared storage and migrate the VMs from one filer to another

 Other lenthy method is  snapmirror the volume and , break the mirror, map the lun and add the vm to inventory here you will have downtime.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now