Moving SAN BOOT Volume from one storage to another
Hello,
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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 ?
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 ?
ASKER
Hancock,
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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,
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,
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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