Its that day where you thought finally you got everything working perfectly with your Exchange infrastructure & your manager walk in and say our old storage where your Microsoft Exchange Server is installed is getting out of warranty and the good news we are replacing it with this new shiny storage box which should give us a better performance and durability. I need this done in a week time. Now you start scratching your head on how to move you Microsoft Exchange 2003 Cluster or Microsoft Exchange 2007 SCC(Single Copy Cluster) to the new SAN. While my article here can not do the work for you. It will show you how you can do it with ease, & without doing mailbox movement although that might be another good way to do it if you have extra hardware for it! Below is how to migrate your Microsoft Exchange Cluster to a new SAN. As well you can find my article on migrating SQL at: http://www.tsmguru.com/data-migration/microsoft-sql-cluster-data-migration-to-a-new-san.html
Steps to Migrate MS Exchange 2007/2003 to a new SAN Box
MS Exchange Storage Migration Preparation Steps:
1- Make sure there is an adequate back in place in case anything go wrong
2- Present both SAN boxes to your MS Exchange server. Check with your hardware vendor if there is any special requirement you need to do this.
3- Test the Current Exchange failover & failback
4- Create the new arrays, LUNs similar to what was used on your original storage. Though create two luns for the Quorum drive as one of extra Quorum drive will be required during the migration.
5- Add the new array and its LUNs to the same switch as the existing array (on the new switches).
6- Configure the LUN masking on the switch to expose the new LUNs to all cluster Nodes.
Moving MS Exchange Quorum drive to the new SAN
Collect all used drive letters in the cluster to avoid causing a conflict.
Use the disk management tools in Windows to rescan the drives
- Use the active node to partition and format the disks (Proper Labeling will easy identifying disks at later steps).
Use Cluster Administrtor to create the new physical disk resources and put them into their proper cluster groups
Create a temp Cluster Group.
Move the Quorum using the GUI to a temp location
In Cluster Administrator, right click the cluster name
Select the Quorum tab
Use the drop down box to select a temp location for the quorum
Delete the existing MSDTC folder (if any)
Stop the MSDTC resource
Copy the MSDTC folder from Q: to the final qurom disk target location
Stop the Q: resource (remember, the quorum isn’t there anymore)
Delete the MSDTC resource
Move the quorum to its final location
Go into disk management and change the Q: name to another letter
Use disk management and name the final quorum drive to Q:
- Repeat steps 6.1-6.4 to move the quorum to its final destination
Recreate the MSDTC resource
Create a new MSDTC resource with the clustername network name resource and the new Q: as dependencies
Bring the MSDTC resource online
8. Move the old Quorum & MSDTC drives to a temp cluster group
Moving Exchange 2003 Databases & Log Files to the New SAN
- Stop the cluster service and the Exchange cluster groups.
Move the data from the old disks to the new ones. Tools such as CloneDisk or SynchroFolder can be of a great help in here. For more info about them check out my earlier post: Microsoft SQL Cluster Data Migration to a new SAN
- Re-letter the old disks to something outside the current range, but do not remove them yet – we might need to use them in our back out plan
Re-letter the new disks to the same drive letter as the old ones
- Move the old drives to a temp cluster group
Verify that all dependent resources are pointing to the proper physical disk resource.
- Ensure the permissions on the drive and the registery key mentioned in MS Article #821915 are in place
Restart the cluster service
Make sure the new drive letters and disk resources are showing up properly in cluster administrator
- Bring everything back online.
Ensure the cluster is working with the new resources after getting the temp cluster group offline, if so it is safe then to remove the old drives.
steps 1 – 11 will have to be repeated for every Virtual server.
Decomissioning OLD SAN
Disconnect OLD SAN from the switch after all the drivers has been removed from the Exchange servers.
Upgrade the Firmware & Drivers of the HBAs as required.
- Carry out any changes to your multipathing drivers and so on that was not possible when the two storages were connected to the system.
- One day shall be reserved for testing after the migration has finished.
- Don’t delete the LUNs from the old storage as soon the migration is completed, but rather just remove their mapping and leave them to be recalled on in case if something to go wrong.
I hope this help. Please leave your feedback & questions in the comments area below.
2 Responses to 'Migrating Exchange 2007/2003 Cluster to a new SAN'
Leave a Reply
Eiad Al-Aqqad, VCDX#89
VMware Canada PSO
- Backup Solutions (3)
- Blades (2)
- IBM Blades (2)
- Data Migration (2)
- EMC (1)
- VPLEX (1)
- How to (1)
- Management Software (5)
- Problem resolutions (0)
- Storage (21)
- Tips & Tricks (7)
- Tivoli (22)
- Tutorials (11)
- VMware (6)
- Iwan: hi… I can not re-install smi-s agent on server windows 2003, I`ve been search the registry but still...
- sindhu: hello sir,i am doing my b.tech 3rd year (e.c.e) i am intrested in doing this tsm course .is this course will...
- CR7: Hi EIAD, I couldnt figure out where to post this doubt of mine, so im just posting it here.Please help out if...
- Errol: I’m using a clean install of windows 7 Ultimate 64 bit with the latest build of Thinapp 5.1.0-2079447....
- arun: Is that tsm is growing and good field
- TSM – IBM Tivoli Storage Manager Guru Blog: Should Virtual Tape Library have a place in your backup strategy?
- Tivoli TSM guide to securing VMware: IBM Tivoli Storage Manager & VMware Consiledated Backup (VCB) I hope these...
- TSM – IBM Tivoli Storage Manager Guru Blog: Microsoft SQL Cluster Data Migration to a new SAN
- TSM – IBM Tivoli Storage Manager Guru Blog: Migrating Exchange 2007/2003 Cluster to a new SAN
- IBM Tivoli Storage Manager Guru Blog: TSM
- Should Virtual Tape Library have a place in your backup strategy?
- Symantec Backup Exec StarWind Virtual Tape Library Integration
- Comparing Online Backup Services
- Veeam & PHD Virtual comparison
- IBM Tivoli Storage Manager support for VADP
- StarWind is Named a Finalist in The Storage Awards 2012
- PHD Virtual Monitor Review
- vSphere manual Disaster Recovery failback when using VMware SRM
- Migrating Exchange 2007/2003 Cluster to a new SAN
- Microsoft SQL Cluster Data Migration to a new SAN