Oiles
asked on
Exchange Server Backup and Repair
Windows 2003 R2 running MS Exchange 6
Two questions really:
1.) What is typically backed up on MS Exchange and how do most folk do it?
2.) Our Exchange DB has become inconsistent and I need a tool to repair it but I don't want to take the DB offline to use ESEUTIL. What can I use to stabilize the database?
Two questions really:
1.) What is typically backed up on MS Exchange and how do most folk do it?
2.) Our Exchange DB has become inconsistent and I need a tool to repair it but I don't want to take the DB offline to use ESEUTIL. What can I use to stabilize the database?
Is the DB up (mounted\running) and is the Exchange enterprise version ?
ASKER
DB is up and running. To move the mailboxes, I would assume that the store would need to be dismounted (undesirable). Version: 6.5.7638.1 (from Exchange System Manager). I think I would be leary of setting up a new Exchange instance, migrating all mailboxes, then running diagnostics on that DB and then replacing the old one. Seems like a lot of work.
Is the Exchange Standard or Enterprise ?
For moving mailboxes the DB wont be dismounted anytime.
For moving mailboxes the DB wont be dismounted anytime.
It would require some time but not a lot of hard work and a clean DB in new place.
ASKER
We are running Exchange Standard. Ok, I'm asking for a lot, but you wouldn't happen to have a link to instructions on how to migrate mailboxes and a new Exchange Store would you?
In Standard we can have only one Mailbox and PF store so we cant have anyother store. But with Exchange 2003 you can use RSG.
ASKER
Is using a recovery storage group your recommendation? To create one and then migrate it into production as a clean store?
An RSG isn't going to help here, because that is for recovery only, used with a backup.
Your only option to minimise downtime is going to be to build another server with Exchange 2003 on it, then use move mailbox wizard to move all the mailboxes to it, drop the original and then recreate it and move everything back. That is fail safe and the downtime window is small.
Simon.
Your only option to minimise downtime is going to be to build another server with Exchange 2003 on it, then use move mailbox wizard to move all the mailboxes to it, drop the original and then recreate it and move everything back. That is fail safe and the downtime window is small.
Simon.
ASKER
This sounds like a plan. Last question: Once I've recreated the store on another server and migrated the users to it, I would assume I just unmount Store 1, move the new store over and mount it. Sound about right?
I realize there is probably more to it as I will be using a book/technet as a guide, but is this essentially correct?
I realize there is probably more to it as I will be using a book/technet as a guide, but is this essentially correct?
You drop the store within ESM, if there is a problem it will stop you from doing that.
Then you can recreate a new store. At that point I would suggest that you restart the information service so that the system mailboxes are recreated. Then move everything back.
If you can do it with no users around, so on a Saturday or something, then you shouldn't have any problems with Outlook redirecting. If you must do it with users around then the old server will need to alive long enough for Outlook to redirect on its own.
Remember that the temp system must be removed correctly, in just the same way as a full server. You cannot cut corners just because it is a temp system.
Simon.
Then you can recreate a new store. At that point I would suggest that you restart the information service so that the system mailboxes are recreated. Then move everything back.
If you can do it with no users around, so on a Saturday or something, then you shouldn't have any problems with Outlook redirecting. If you must do it with users around then the old server will need to alive long enough for Outlook to redirect on its own.
Remember that the temp system must be removed correctly, in just the same way as a full server. You cannot cut corners just because it is a temp system.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Any updates ?
That should put you in a clean DB.