Jump to content
Sign in to follow this  

Exchange system folders and public folder store?

Recommended Posts

I am little mess. Why many instructions and helps suggests in Internet, about Exchange migration to new server, all talk about replication needs of Exchange system folders to the new server. Are those Exchange system-folders part of "public folder store" or they are not part of it? If they are part on "public folder store", then why not just backup-restore this storage (or just simple copy it) to the new server?


Share this post

Link to post
Share on other sites

Moving exchange data to a new server is a very complicated process, that may require the help of MS tech support.


You could try doing a restore to a recovery storage group on a new server if the storage group does not contain public folders.

Share this post

Link to post
Share on other sites
Moving exchange data to a new server is a very complicated process, that may require the help of MS tech support.


You could try doing a restore to a recovery storage group on a new server if the storage group does not contain public folders.


But why not just install Exchange into new server and restore FirstStorageGroup with Retrospect.

(as I know Retrospect don't need Exchange "recovery storage group")


Share this post

Link to post
Share on other sites

Exchange is very limited when it comes to copying data to a new server.


You can read the KB article below, which details the steps:




As you can see it ISN'T easy.


TITLE: Restoring Exchange 2000 to a new server









Procedure for restoring MS Exchange in a Windows 2000 test environment, where the Exchange server is running on a different server than the domain controller.



1. Servers and Backup Media

Domain Controller server (to be configured)

MS Exchange server (to be configured)

Backup set catalog and backup set media


2. Exchange database backups should have an identical number of stores, and the names should be identical to those which are currently in Active Directory. Database changes in Exchange such as addition or removal of additional mailbox or public folder stores *may* have an adverse affect on restore.


3. Access to both the production network and a test network (isolated from your production network)



Part 1: The Domain Controller (access to both the production and test networks required)


1. Install Windows 2000 Server on the new Domain Controller (DC) server (to be referred to as NEWDC)


2. Install the same service packs and patches that are installed on existing DC(s).


3. Go to Start > Programs > Administrative Tools > Configure Your Server > Active Directory


4. Scroll to bottom and select Start the Active Directory Wizard


5. Click Next > Additional domain controller for an existing domain


6. Enter in the account information of a user with authorization to add domain controllers to the domain (usually a Domain Administrator)


7. Allow Active Directory to sync all objects to the new DC's. (Do not interrupt this process)


8. Once Active Directory objects are synced, go to:

Active Directory Sites and Services > Sites > Sitename > Servers > NEWDC. Right-click NTDS Settings > Properties. Check the box next to Global Catalog (allow for time to sync, could take 10-60 minutes or more. May be noted in the Directory Services event log as Event 1119 when complete)


9. Return to Configure Your Server and install DNS on NEWDC. Allow 5-15 minutes to sync, depending upon size of your existing network.


10. Once complete, remove NEWDC from production network and isolate into a private testing network. (WARNING: insure NEWDC and the Exchange Server are not connected to the production environment)


11. Assign a static IP address to NEWDC. For the DNS server entry use the IP address of NEWDC.


12. In Administrative Tools, DNS, find the entry for your production Exchange server and change the IP address to the IP you previously assigned it.


13. Now you must seize the FSMO roles of Schema Master, RID Master, PDC Emulator, and Domain Naming Master (Infrastructure Master cannot exist on same server as the Global Catalog). These roles are typically handled by the first DC that was created in the network; however Exchange cannot be installed without these roles present in the network.


A description of the roles seizure procedure can be found in Microsoft Knowledge Base article 255504.


1. Start ntdsutil.exe

2. type 'roles'

3. type 'connections'

4. type 'connect to server (where is the name of your new domain controller, NEWDC in this case.)

5. type 'q' , and then follow the steps to seize the four roles:

6. type 'seize schema master'

7. type 'seize rid master'

8. type 'seize pdc'

9. type 'seize domain naming master'

10. type 'q' to exit

11. Reboot. The new Domain Controller is ready.



Part 2: The Exchange Server (access to the test network required).


1. Install Windows and any current service packs so that the installation matches what was running on the old Exchange server. During the installation, the server should be given the exact same name as the original Exchange Server. For our example, we'll call it MAIL. Ensure that the drives are partitioned the same as they were on the original Exchange server. The sizes do not need to match exactly, but you should ensure that there is enough room on the appropriate partitions for the Exchange databases.


2. Ensure the server is only connected to the test network environment. Assign a static IP address on the same subnet as NEWDC, and for the DNS server entry, use NEWDC's IP address. Update NEWDC's DNS records so that MAIL points to the new static IP address.


3. Ensure that DNS is functioning correctly by pinging MAIL from NEWDC and NEWDC from MAIL by name.


4. Now that things are functioning correctly, join MAIL to the domain. When prompted, enter the credentials of a user that has permission to add servers to the domain (typically a Domain Administrator). Reboot when this is complete.


5. Install Exchange in Disaster Recovery mode. To do so, from the run menu, type the path to setup.exe on the Exchange CD, and suffix it with the "DisasterRecovery" switch. For example:


D:\i386\setup\setup.exe /DisasterRecovery.


On the component selection screen, you will have to manually select the components that were installed on the original Exchange server. The only installation option should be "Disaster Recovery"


This will cause Exchange to be installed very minimally, while at the same time pulling the original store configurations from Active Directory. During the installation, you may see a few dialog boxes. This is normal.


6. Install the same Exchange service pack version you were running on the old Exchange server. You must install the service pack with the /DisasterRecovery switch as well, using the path to the update.exe file instead of setup.exe.


After the service pack install is complete, install any required hotfixes that were installed on the original Exchange server.


7. Before restoring, you need to ensure that the databases are ready for restore. Open Exchange System Manager, and navigate to the storage groups for the server. For each store, get Properties and go to the Database tab to ensure that the boxes "This database can be overwritten by a restore", and "Do not mount this store at startup" are checked. This will allow the restore to complete successfully. The stores should not be mounted at this point, if they are, then something has gone wrong. Now is also a good time to verify that the database/store names and locations match those of the original (production) Exchange server.


8. If you had your stores and logfiles stored in a custom location, you may need to create the directory structure for that location before starting the restore. For example, if your stores were located on S:\Exchsrvr\MDBDATA, you may need to create that path if it doesn't already exist before starting the restore. If the paths to the stores and the logfiles do not exist, the restore will fail.


9. Install Retrospect. If you are installing Retrospect on another machine to restore the Exchange server as a client, ensure that the other machine is connected only to the isolated network, and that you have the latest Retrospect client running on the Exchange server. Open Retrospect, and ensure that your Exchange server is licensed and accessible. Go to Restore > Database, and choose the appropriate database snapshot. Choose the new Exchange server as the destination, and start the restore. When the restore completes, the databases should be mounted and functioning, and your restored Exchange server is now ready to use.






Share this post

Link to post
Share on other sites

You can not restore a Windows Registry to another computer, the computer would probably fail to boot.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this