General discussion


Can I do this to Exchange?

By rob ·
Is there anything wrong with this? Lets say I wanted to move an exchange database to a new computer. The computer has exchange setup on it, but it's not doing anything.

Can I unmount the mailbox store under the first storage group, and remove the default EBD and STM files- and then copy the ones I want to use there and re-mount the store?

I tried this on my text box. It seemed to work fine.

I am thinking of ways to perform the fastest recovery possible (in case I ever have to) as my production environment is not fancy: no redundant server, no backup server- just a SBS server with a tape backup.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -


by chaotic1 In reply to Can I do this to Exchange ...

Yes you can do it. that is actually the best and quickest way to restore exchange. Just remember run the integ. check to make sure the store is uncorrupted on the new box before mounting.

Collapse -


by risunantony In reply to yes

You may also be required to keep the exchange organization name, storage group name, mailbox store name all same on additional server too.

Collapse -


by lynton In reply to Also.......

...on Exchange 2000/2003, you'll also need to "reconnect" all the mail-enabled users to their mailboxes on the new server once the stores are mounted, so Active Directory knows which server each user's mailbox is on.

The recovery method you've suggested does seem to work fine. It's also possible to use disk volume replication (mirroring) software to continuously replicate the drive(s) holding Exchange databases & logs from one server to the other, in real time, so you always have an exact copy of the Exchange data on the second server. This would allow you to get the second server up and running even quicker, with no loss of data, as you wouldn't have to restore from your most recent tape backup first. You'd just need to move a few files around on the second server to get the databases to where Exchange is expecting them to be, then reconnect the mailboxes.

Collapse -

Directory Name Change

by Mail_man In reply to Can I do this to Exchange ...

Beware, however, that when you do this, the directory name on the existing mailboxes will be appended with a random sequence of numbers. This should only be an issue if you're usuing something like Exmerge that uses directory names, rather than aliases.

For example, running Exmerge on a mailbox would produce a file name of john.doe.pst. Now, the file name will be something like john.doe6015472.pst. This is by design from Microsoft and the appended numbers can not be removed.

Again, not a really big issue. But can come as a surpise if you're not prepared for it.

Collapse -

Yes and no

by MagicTom In reply to Can I do this to Exchange ...

You have to take care of an ID that is called SID (I think it is System identification). If you manage do give the SID of the old computer to the new computer then Exchange should work after the old computer and its Sid is out of circulation. There cannot be two computers with the same SID on the same network. The best way to transfer should be with a backup restore (from the old to the new) Before restoring to the new, The SID of the new computer would have to be change to the SID of the old computer.

Collapse -

This is the best for disaster recovery

by dannyt In reply to Yes and no

This is what I recommended:
1. Build a member server with a different name of course, partition the RAID same as your production Exchange server and most importantly, this member server must have the same hardware specs as the production one or else disaster recovery would be impossible.
2. Use Symantec system stage recovery to do drives image backup, this included your OS; IS databasee & transaction log partitions. Then replicate these images to a shared folder on your file server.
3. In a disaster situation, completely disconnect your production Exchange server and boot your standby member server with the Symantec CD and map to your shared folder on your network, first you need to recover the OS partition from the image file and follow by other partitions.
4. Once all done, connect your new Exchange to your production network and you will be on your way.

This is the best practice that I recommended because you don't need to worry about SID.

Related Discussions

Related Forums