Article ID: 555603 - View products that this article applies to.
In some cases you need to move/restore a database as soon as possible, if you don't have hardware you might use this article to restore your database on another Exchange Server.
The best way for disaster recovery is setup /disasterrecovery, but if you don't have a machine or time to do it you might use this article to help you to restore a database on another Exchange Server. This article explains changes in database location, attributes in user objects on Active Directory of affected users, and script on client machines.
For this article you need another Exchange Server 2003 with Service Pack 2 or higher, we'll use names to the differentiate to crashed and second Exchange Server as follow:
To restore your database on another server, follow these steps:
Restore the database
Modify Exchange User attributes localized at Server1
Modify the Microsoft Outlook Client
It's a optional step, you can change the name of the server manually in each client to access Server1 (crashed server), but if you want to make it in a centralized way, you can do the steps bellow.
To create a script to change the server name in Microsoft Outlook Clients you need to use the Exchange Profile Update Tool (exprofre.exe) utility. It can be found in this web site: http://support.microsoft.com/?kbid=873214, and follow this steps on a test machine with profile configured to a Server1 (old exchange server):
For this step to work it is necessary to have a correct X500 address for user objects. Ps: If you use a X500 address for some message systems then you must validate the implication of these changes in your environment.
Troubleshooting a correct X500 address for Exprofre
Follow this steps to do a correct troubleshoot in a X500 address generation/modification in your users:
You must have your users be able to migrate in your validate-exprofre.txt, if you won't validate the X500 address.
821829 How to move mailbox
873214 How to use Exprofre
271987 Overview of Exchange Server database architecture and database engine
867704 Disaster Recovery Guide of Exchange Server 2003
Article ID: 555603 - Last Review: April 24, 2006 - Revision: 1.0
COMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
Contact us for more help
Connect with Answer Desk for expert help.