03-26-2012 02:21 PM
We are currently using Enterprise Vault Version: 9.0.1.1073, and I would like to bring it up to date. We Would actually like to bring this server up to date, and then migrate all the data(~4TB) to a new server. The reason for this is the luns were old 2003 luns which were reattached to my 2008R2 9.0 server when we switched the server from 2003 to 2008R2 without copying the data. I an thinking a fresh start will be a good idea as opposed to re-aligning the luns.
Do you think it is necessary to bring the original server up to date before migrating the data?
Have you ever seen some one realign netapp luns so they can avoid migrating all the data? I suppose I could create new luns after upgrading> drop the services> migrate the data> shut off the old luns> change the letters of the new luns to match the old> then turn on the services.
Any thoughts?
Thank you
Solved! Go to Solution.
03-26-2012 03:00 PM
the plan sounds fine to me, just make sure that EV is offline for the entire time the copy is going, which may take some time, or at the very least, make sure that EV is in backup mode so no new data is being added or removed etc.
Make sure that you hve good backups as well just in case anything does go wrong, but usually RoboCopy is a fairly safe bet.
Obviously for the migrations wizard, you will have to have the EV servers stopped, and they ask you to do things such as turn off all the schedules so that it doesnt kick off an archiving run during a testing phase and what not
03-26-2012 02:46 PM
So you could set up your new server to have the correct configuration that you want and then use the EV Server Settings Migration Wizard to go from EV9 to EV10
More can be read about the Migration Wizard here:
http://www.symantec.com/business/support/index?page=content&id=HOWTO42445
However if you have the NetApp attached to the EV Server using drive letters and you are looking to change those drive letters, you are going to have to update the PartitionEntry table in the EnterpriseVaultDirectory database through SQL in order to have the parition root paths point at the correct drive letters, otherwise you will generate tons of errors.
03-26-2012 02:54 PM
Well.. In the past we have done the following with other servers.
Migration wizard may be the cleaner way to go, and if I am copying the data it might as well be done the cleanest way.
03-26-2012 03:00 PM
the plan sounds fine to me, just make sure that EV is offline for the entire time the copy is going, which may take some time, or at the very least, make sure that EV is in backup mode so no new data is being added or removed etc.
Make sure that you hve good backups as well just in case anything does go wrong, but usually RoboCopy is a fairly safe bet.
Obviously for the migrations wizard, you will have to have the EV servers stopped, and they ask you to do things such as turn off all the schedules so that it doesnt kick off an archiving run during a testing phase and what not