Solved

Cannot mount store after offline restore on dissimilar hardware

Posted on 2004-09-28
16
987 Views
Last Modified: 2009-11-14
I tried restoring a Windows 2000 Server SP4 Active Directory system state and an Exchange Server 2000 SP3 database backup on a standalone server with dissimilar hardware with an offline restore.  I have used this restore procedure many times, and it has always worked.  Recently there were problems with our Active Directory replications, and we repaired this problem by demoting the secondary domain controller and re-promoting it, and then restoring the SYSVOL folder.  This fixed our replication problem, but I think that this may be the cause for our unsuccessful restores.  Our restore procedure is the following, the errors are written in capital letters and are present only in our recent and unsuccessful restore attempts:

1. Try to assemble a hardware configuration as similar as possible to the original.  The harddrive sizes are identical.
2. Install Win2K as a standalone server, with identical IP address, Windows Components (DNS etc), Computer Name, Service Packs, Hotfixes, etc.
3. Restore System State (with default NTBackup settings, ex. Do Not Overwrite Existing Files)
4. Restart.

ERRORS:
-AFTER RESTART, SOME SERVICES COULD NOT BE START ERROR MESSAGE AT LOGIN
-IN MMC SNAPIN, FOLLOWING OBJECTS ARE MISSING: SYSTEM
                                                                                MICROSOFT EXCHANGE SYSTEM OBJECTS
                                                                                LOST AND FOUND

5. Reinstall Exchange 2000 in disaster recovery mode.
6. Reinstall all drivers removed from System State restore (ex. NIC, VGA, INF etc.)
7. Reconfigure static IP Address
8. Ensure all Exchange services are started, unmount mailbox store and public store, and unselect 'Do not mount this store at startup', and select 'This database can
   be overwritten by a restore' (for both stores)

ERRORS:
-ALL SERVICES START, EXCEPT MICROSOFT EXCHANGE MANAGEMENT SERVICE ERROR 2: SYSTEM CANNOT FIND THE FILE

9. Restore Exchange database backup.  In NTBackup I configure to 'Always replace existing files', select 'last backup set', select 'mount database after restore'

ERRORS:
-AFTER RESTORE, EXCHANGE STORES CANNOT BE MOUNTED, NEITHER AUTOMATICALLY, NOR MANUALLY.
-FOLLOWING ERROR MESSAGE AFTER MANUAL MOUNT: c104724

Note: The event log is filled with application and system errors regarding exchange and active directory.  
Errors codes range from applications log: 9175, 8197, 101, 103, 9518, 9519, 619, 102, 903, 904, 411
                          directory services log: 1311, 1566
                          systems log: 8035, 7000, 8015, 8033, 1007, 1006, 101

Any help would be greatly appreciated.

Thankx

GP
0
Comment
Question by:Navigatorkft
  • 7
  • 6
16 Comments
 
LVL 13

Expert Comment

by:rhinoceros
ID: 12167430
In case Exchange servers restored logging (.STM) is not consistent with “Priv1.edb” and “Pub1.edb” during restoring, these two stores may not be mounted.

State checking
INPUT: “Drive:\program files\exchsrvr\bin eseutil /mh Drive:\program files\exchsrvr\mdbdata\priv1.edb”
RESULT:
            (“state = clean shutdown”) = good status of databases in running.
            (“state = dirty shutdown”) = databases & log files are not consistent.

If (“state = dirty shutdown”), we should run “Drive:\program files\exchsrvr\bin eseutil /cc” ) to synchronous the restored database & log in consistent.


I hope it can help.
0
 

Author Comment

by:Navigatorkft
ID: 12167535
rhinoceros!

The state is inconsistent, i.e. dirty shutdown, but I cannot synchronize the restore database and log  using eseutil /cc
I receive the following error:

Restore log files: D:\log\First Storage Group
      Target instance: First Storage Group
Error returned from an ESE function call (-514).
Operation terminated with error -107 <JET_errInternalError, Fatal internal  error> after 0.79 seconds
0
 
LVL 13

Expert Comment

by:rhinoceros
ID: 12171192
During Exchange Restore Wizard, did you enter "Temporary location for log and patch files:"  as c:\temp ?


Overall, you should follow those steps again

(if drive on C:)

1. On Exchange Restore Wizard,
Restore To: Old server name
Temporary location for log and patch files: c:\temp
LastBackup Set (checked)
Mount Database After Restore (unchecked)

(Because it's failed, so no need to start it immediately)

2. Then do it on command promp
> C:
C:> cd\temp\First Storage Group
C:\temp\First Storage Group>C:\progra~1\exchsrvr\bin eseutil /cc

So it will take back all logs and patch files during synchornize.

3. You can mount the database using the Exchange System Manager now


I hope it can help.



The microsoft official documentation as following

CAUSE
The Last Backup Set check box was not selected during the restore, so hard recovery was not run.
RESOLUTION
Before the database can be mounted, hard recovery must be completed. You can run hard recovery manually with the following command:
eseutil /cc [path to directory containing Restore.env]
For example, if the path specified for the "Temporary location for log and patch files" during the restore process is C:\TempRest, the command to run hard recovery is:
eseutil /cc c:\temprest
Note You need to run eseutil.exe from the Exchsrvr\Bin directory.

After hard recovery completes, mount the database using the Exchange System Manager.
0
 

Author Comment

by:Navigatorkft
ID: 12177091
Rhinoceros!

I have read this article, and I have tried the above method, it does not work.  I think the problem with my System State restore.  Is the System State enough, or do I need to restore the system partition as well?  Or if not the whole partition, then things like Inetpub, Winnt, Program Files etc.?

GP
0
 
LVL 13

Expert Comment

by:rhinoceros
ID: 12187443
"I tried restoring a Windows 2000 Server SP4 Active Directory system state and an Exchange Server 2000 SP3 database backup on a standalone server with dissimilar hardware with an offline restore. "

"we repaired this problem by demoting the secondary domain controller and re-promoting it, and then restoring the SYSVOL folder.  This fixed our replication problem"


Friend, I don't understand what's your domain infrastructure? If Do you have more than one server into domain ? It’s impossible to depromo a server from domain, which has installed Exchange server.... Because Exchange server must be running on Active Directory...


Anyway if your domain is really more than one and the Exchange server is not RootDC, you can try it to restore your old Exchange server to a new one... I would like to share my experience.

- Install new 2000 server with old exchange server name, IP, Hot fixes etc.
- Directly promo new server to join to your domain again. (It will be accepted). Then waiting the full synchronize successful
- Reinstall new Exchange with “setup /disasterrecovery” to new server

(After Exchange server reinstalled)
- Dismount Store. (Mailbox Store & Public Folder Store),
- select the “This database can be overwritten by a restore” check box
- Stop all Exchange services except Microsoft Exchange Information Store
- Now restore "Microsoft Information Store", you should only restore "Microsoft Information Store" (it contains "Log Files", Mailbox Store, and Public Folder Store). Not for whole NTBackup file (e.g. no need to restore system state again).
- select the Last Backup Set check box & In the Temporary location for log and patch files box, specify a directory to store log and patch files during the restore process.
- If mounting failed, “run eseutil /cc” for mailbox consistent


I hope it can help.
0
 

Author Comment

by:Navigatorkft
ID: 12187498
Yes we have a Primary Domain Controller (Navi-DC3) which is also the Exchange Server, and a secondary Domain Controller (Navi-DC2) which is the replication partner.  The Exchange server IS the rootDC.
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 13

Expert Comment

by:rhinoceros
ID: 12188146
I got it...

I believe the problem is come from AD, so why you have a replication problem after RootDC had restored.

Because when you restore the only domain controller in the domain, or you restore all the domain controllers in the domain. The Sysvol and Netlogon shares are missing after you restore a domain controller. And you will find a folder “C:\WINNT\SYSVOL\Sysvol\Domain.com\PreExisting_See_EventLog\policies”
Normal case: c:\winnt\Sysvol\Domain\policies\ & \winnt\Sysvol\Domain\script

NOTE: If you run Dcdiag.exe, the FsmoCheck fails with:
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355.

Because you restore a domain controller, the FRS database is NOT restored, because a current replica is assumed to have the most current database. FRS tries to locate a replica to synchronize with and until it complete replication, it can NOT share the Sysvol and Netlogon shares. If you restore all the domain controllers, no replica can be found because they are all searching.


So you can try it to normally restore RootDC in domain.


Step A:
You still new install win2000 server, and then restore from NTbackup (Original location).

Step B:
To restore system state to an alternate location
1 Click the Restore tab
2. Select SystemState. (You need not restore the system disk to an alternate location.)
3.Ensure that Alternate Location is selected in the Restore Files to drop-down list box and designate the alternate location.
4.When the restore process is finished, close the backup utility.
5.Restart the computer to normal mode.

Step C:
You must designate a domain controller to be authoritative for the Sysvol replica set:
1.Stop the File Replication service on the PDC emulator FSMO role holder.
2.Use the Registry Editor to navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Paramaters\Backup/Restore\Process at Startup.
3.Double-click the BurFlags Value Name, a REG_DWORD data type, and set the data value to D4, using the Hex radix.
4.Exit the Registry Editor.
5.Start the File Replication service.
NOTE: If the BurFlags Value Name is set to D4 (authoritative) on more that one replica, conflicts and collisions will occur.

Step D:
You should try to restore applicable portion of SYSVOL from alternate location

The following example shows how to copy SYSVOL from the alternate location to the original location. Depending on your system, your drive and folder information can vary.
1.Copy the contents of the scripts directory from:
c:\<Alternate Sysvol Location>\sysvol\c_\winnt\Sysvol\Domain\scripts\
2.Add the contents to:
c:\Winnt\SYSVOL\Sysvol\domain\scripts\
3.Copy the contents of the policies directory from:
c:\<Alternate Sysvol Location>\sysvol\c_\winnt\Sysvol\Domain\policies\
4.Add the contents to:
c:\Winnt\SYSVOL\Sysvol\domain\policies\
By restoring the SYSVOL authoritatively, the files on the restored domain controller are authoritative for the domain and replicate to other domain controllers. Changes made to any policy after the backup will be lost.


I hope it can help.
0
 

Author Comment

by:Navigatorkft
ID: 12188193
Rhinoceros!

So I should first restore the system state only to original location, then restore the system state to a different location, and copy the SYSVOL content???

GP
0
 

Author Comment

by:Navigatorkft
ID: 12188398
Rhinoceros!!!!!!!!!!!

Guess what!  I restore the system state to the normal location.  Then i restarted the computer in Directory Service Repair mode, and restore the system state to a new location.  I wanted to copy the contents of c_\winnt\sysvol\domain
is EMPTY!  I checked both online DCs and the contents of sysvol\domain is ONLY:

DO_NOT_REMOVE_NtFrs_PreInstall_Directory

could this be the cause of all of our problems???
0
 
LVL 13

Expert Comment

by:rhinoceros
ID: 12191015
I think so...

Yes, you should go to Directory Service Restore mode, restore system state to to an alternate location  at first. After finished, you restore “System State” to the normal location. Then reboot server to normal mode.

Now do above step C, and then copy the SYSVOL content.

I hope it can help
0
 

Author Comment

by:Navigatorkft
ID: 12197551
rhinoceros, I don't understand!  which SYSVOL folder are you talking about?  the inner sysvol, or the outer sysvol?
And also, the sysvol\domain folder is empty on the existing servers as well!  so how is this going to fix my problem?

GP
0
 
LVL 13

Accepted Solution

by:
rhinoceros earned 50 total points
ID: 12205666
Friend, you must do all steps on new ROOTDC only

1. you should go to Directory Service Restore mode, restore system state to to an alternate location  at first. After finished, you restore “System State” to the normal location. Then reboot server to normal mode.

2. Then you must designate a domain controller to be authoritative for the Sysvol replica set as above Step C.

3. You should try to restore applicable portion of SYSVOL from alternate location as above Step D. (c:\Winnt\SYSVOL\Sysvol\domain\ -->  both policies  and scripts folders)

4. Reboot Server

(P.S. you do it all on RootDC only. If done, this new server will auto replicate SYSVOL again with existing server)




0
 
LVL 13

Expert Comment

by:rhinoceros
ID: 14321225
Navigatorkft

I had got the same job as before, so I believe you should solve it with my comments.
0

Featured Post

Do email signature updates give you a headache?

Do you feel like you are constantly making changes to email signatures? Are the images not formatting how you want them to? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now