cancel
Showing results for 
Search instead for 
Did you mean: 

Disaster Recovery of a Windows Client fails

Orangebud
Level 3
Hello,

here's the szenario:

  • BE Version 12.5 SP3
  • Full Backup of a Windows XP client exist
  • I have to restore the entire client
my procedure:

i have searched for a how-to and found this:

seer.entsupport.symantec.com/docs/236286.htm
I have followed the instructions:
  • Install a Windows XP with the same patch- and servicepack-level
  • I named the system like before, with the same ip
  • I installed the BE-remote client from the BE-Server with the credentials of a local administrator-account from the target system, and could access it
  • I can see the resources from the computer and can access it
  • I created the Restore-job, selected the last full backup, typed in the login-credentials from the local administrator and tested the resource login but it failed
When i run the restore it failes of course with the error 0xa000848c:seer.entsupport.symantec.com/docs/327019.htm

My question now:
  • why the authentication with the local account failes
  • when i relocate the source files i can authenticate and restore to the target system
  Thanks, for your attention!
1 ACCEPTED SOLUTION

Accepted Solutions

Orangebud
Level 3
This is what the Symantec-Support gave me:

seer.entsupport.symantec.com/docs/307395.htm 

After this, i could restore the client.

View solution in original post

3 REPLIES 3

Hemant_Jain
Level 6
Employee Accredited Certified
So, when you click on backup, expand the resource, it does allow you to get in? If it does, go to "resource credentials" tab in the backup job properties and check the credentials being used there. Use the same credentials for restore job.

Please mark it a solution, if this is useful.
Thanks

Orangebud
Level 3
Exactly this is my problem, in backup i can expand the resource with the credentials of the local administrator, but if i want to restore i get an access denied with the same credentials. I have built a test-environment and can reproduce the problem. Whats the problem?

Thanks

Orangebud
Level 3
This is what the Symantec-Support gave me:

seer.entsupport.symantec.com/docs/307395.htm 

After this, i could restore the client.