atguilmette
Posts: 401
Joined: 4.Mar.2003
From: Southfield, MI
Status: offline
|
A few tidbits that some of you may find helpful in this thread:
- If you want to just add more disk space to your server (such as a RAID tower) and want the Exchange databases to be on it, you don't have to reinstall anything. Simply install the hardware, and move the mail stores through ESM. Open ESM | Administrative Groups | <Administrative Group Name> | Servers | <Server Name> | <Storage Group Name>. Right-click | Properties on the mail store you wish to relocate, select the database tab, and change the locations of the database (.edb) and the streaming file (.stm). It will take a bit (and this particular mail store will be unavailable), but this is the recommended way.
- If you don't have a 3rd-party utility to do brick-level backups of Exchange, you need to have a disaster recovery forest in place. New forest, but the server MUST have the same NetBIOS name, Administrative Group/Storage Group (includes mailstores) structure, same Organization Name and logical partition setup so you can restore the IS. You can restore the database, exmerge the PST out, and re-import it back into production.
- If you didn't have good backups of Active Directory (but you did have good Exchange backups) and your environment gets hosed, you can create a new forest, name your Exchange server the same NetBIOS name, install Exchange using the same Organization Name, recreate the same Administrative and Storage Group structures (including mailstore names), and restore the IS. Then, you can use mbconn (on the Exchange 2000 CD) to export an LDIF of all of the user names in the IS, and import that into Active Director. Doesn't do much for your groups, but at least you have a starting point.
- Instead of just replacing your server with a faster one, consider adding another one to the site. You can create new mailstores and balance the users between the two servers. It's one more thing to manage, but you can also migrate users to this box in the event that your firt server starts acting up.
- If you really do want to replace your server, you can follow one of two main paths. You can run setup /disasterrecovery or restore to a recovery forest (depends on what your need is). See the list of Q artciles and recommended reading at the end. Recommended reading for anyone interested is the "Disaster Recovery for Microsoft Exchange 2000 Server" whitepaper and the "Exchange 2000 Server Database Recovery Whitepaper," both available at microsoft.com.
The basic process is for replacing the hardware while maintaining the server name:
1. Make a backup of Exchange 2000 server (including Storage Groups and SRS information) 2. Take existing server offline. 3. Reset machine account in AD Users and Computers (so you don't have SID problems). 4. Build new server w/ same NetBIOS name; install same Win2K SP's and patches as other server. 5. Using an Exchange 2000 Full Administrator account, run setup: setup /disasterrecovery. Ensure the Action-Disaster recovery items are set for Messaging and Collaboration services and the ESM tools. 6. Upgrade to same E2K SP as the previous server. 7. Add the following registry string: HKLM\Software\Microsoft\Exchange\Setup DWORD_NAME: ServicePackBuild For SP1, use HEX Value 1268 For SP2, use HEX Value 1682 For SP3, use HEX Value 1869 8. Install post-SP hotfixes that were installed on the existing server. 9. Restore Storage Groups and SRS from the Exchange 2000 server backup (separate restore jobs). 10. Mount stores.
----- Recommended reading and downloads http://support.microsoft.com/default.aspx?scid=kb;en-us;297289 - XADM: How to Move Exchange 2000 to New Hardware and Keep the Same Server Name http://download.microsoft.com/download/0/1/e/01eeb9c2-3803-4da7-9ef1-e579886d9a42/exchange2000wp.exe - All Exchange 2000 Whitepapers published through 02/2003. Includes Disaster Recovery whitepapers, OWA configuration, the works. It's about 19mb. -----
Hope some of this helps.
--Aaron
|