Kobridge Forum  

Go Back   Kobridge Forum > Technical Solution Center [기술정보센터] - Korean, English Mixed Topics > Computer Center [컴퓨터]

Computer Center [컴퓨터] Computer related information is in this place [컴퓨터와 관련된 정보 저장소]

 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 10-05-2018, 03:23 PM
JJ's Avatar
JJ JJ is offline
Administrator
 
Join Date: Jan 2006
Posts: 285
JJ is on a distinguished road
Default Acronis backup & Recovery 11.5 - system does not boot after system recovered

Current date: 9/30/2018
Most Recent backup: 9/30/2018
Last good backup date using Acronis Backup & Recovery 11.5 - 7/29/2017

Using the current backup, I can start the system after the system recovered but this backup has some DC problem. So, lots of services were not working with current backup like IIS, Exchange, etc.

So, I had to go back to a backup made in last year.
But after the recovery, system did not boot with 0Xc00002e2 error message.
This error message is specially related to the DC database.

Solutions:
I spent many days to make the system bootable after the recovery.

1.Change the system date to the same date when the last backup created from BIOS.
2. Recover the system thru Acronis bootable recovery media.
3. Reboot system. If the system boot normally, you don't need the next step.
Just change the system date to current from Windows.
If system does not boot and show the blue screen with 0Xc00002e2 STOP error message, then restart the system while pressing F8 until you see the boot menu
4. Boot into Directory Services Repair Mode (DSRM). This mode only shows if you have the DC to interact with NTDS database.
5. Login with a local administrator account, since AD service will not be running so the domain user will not be available.
6. Open a Command Prompt (Win-R, CMD, Enter)
7. Navigate to C:\Windows\NTDS. Backup everything in this location. You can use the File Explorer for this step.
8. Type NTDSUTIL and press Enter from Command Prompt.
9. Type "activate instance ntds" and press Enter.
10. Type “Files” and press Enter.
11. Type “Info” and press Enter (this will shows you the logs location in case if you have more than one partition).
12. Navigate to logs Location and delete (or rename) the *.log. You can do this from File Explorer.
13. Reboot normally. Boot into Directory Services Repair Mode for second time
14. Now you should defrag the database, while in DSRM. Open a Command Prompt (Win-R, CMD, Enter). Type NTDSUTIL and press Enter.
15. Type “activate instance ntds” and press Enter.
16. Type “Files” and press Enter.
17. Type “Info” and press Enter. Verify the folder is C:\Windows\NTDS.
18 .Type Compact to ”C:\Windows\NTDS\Temp"
19. Copy the new file Ntds.dit in the temp folder over the old one in NTDS, and delete all the *.log files.
20. Exit from NTDSUTIL.
21. Type: esentutl /g c:\windows\ntds\ntds.dit
This will perform an integrity check, (the results indicate that the jet database is corrupt - ok)
22. Type: esentutl /p c:\windows\ntds\ntds.dit
Agree with the prompt
23. Reboot normally and change the date back to current date.
__________________
Thanks for reading,
J.J.
Reply With Quote
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump


All times are GMT -4. The time now is 06:53 AM.


Copyright ©2000 - 2018, Kobridge Co.
이곳의 모든 내용은 허락없이 사용, 복제를 금합니다.