Currently we've got 4 mailbox servers and 31 databases. We have one active and one passive copy of each database.
The servers themselves are set up using a variety of drive letters. i.e if DB1 needs to be active on Server1 then theres a G: drive on Server1 and a G: drive on Server2 (where its passive). There would be no G: drive mapped on the other servers (since we don't need a datbase on these).
Not the best idea since we used many drive letters. My understanding is if you build a new passive copy its got to be the same drive letter and path (i.e. G:) on the new server.
We're trying to tidy this up a bit, cutting down on drive letters, making all drive letters available on all mailbox servers. Basically, just using E, F, H.
Easy to do if we were starting from scratch BUT we have some DBs mapped to say, I: drive on two servers. I can't build a new passive copy on a new H: - it wont work I dont think.
I "could" physically copy the DB to the new drive - but don't like that idea at all. It seems like its going to be problematic.
Possibly export and import would do it too but thats never going to happen in this environment. DBs too big and no downtime allowed.