Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Always failed to restore OS from tapes

Created: 14 Jul 2014 • Updated: 27 Jul 2014 | 26 comments
This issue has been solved. See solution.

Hi,

My server is 2008R2 64 bit with domain.

I always failed to restore OS from tape by NBU, which steps I was wrong, please help!!

1. Reinstall 2008R2, the hostname is a new one.

2. Join domain

3. Install NBU

4. Restore OS from tapes.

The broken one is called Test1, the new installed one is called Test2, I can restore OS from tapes(Test1 OS) to new OS(Test2)?

If the broken one is enterprise, I still can install standard then do restore?

Below is my error message:

18:23:53 (8922.001) (8922.001) INF - TAR EXITING WITH STATUS = 5
18:23:53 (8922.001) (8922.001) INF - TAR RESTORED 24860 OF 24881 FILES SUCCESSFULLY
18:23:53 (8922.001) (8922.001) INF - TAR KEPT 0 EXISTING FILES
18:23:53 (8922.001) (8922.001) INF - TAR PARTIALLY RESTORED 0 FILES

18:23:54 (8922.001) Status of restore from image created 07/14/2014 01:22:03 PM = tar did not find all the files to be restored

18:23:55 (8922.xxx) INF - Status = the restore failed to recover the requested files.

And then the Operation Status is showing Incomplete.

Operating Systems:

Comments 26 CommentsJump to latest comment

Riaan.Badenhorst's picture

Hello,

Please see this note http://www.symantec.com/docs/TECH56473 when trying to perform a disaster recovery (full) restore of a Windows System.

You can also look at BMR which will enable you to restore the entire system from tape without having to reinstall the operating system first.

http://www.symantec.com/docs/DOC6472

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

SOLUTION
Marianne's picture

In support of Riaan's excellent post - the steps in TECH56473 MUST be followed exactly.

The hostname cannot be a new one. You can only recover the same client to the same hardware.

You cannot use NBU restore to clone a machine.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

HowardYu's picture

Thanks all, so client name and IP must be the same. (I'm wrong, i used the difference because it's my production machine, maybe i need to find out a test one.)

BTW, must be without domain? or can join domain? It's always failed without domain beccause connection socket error, i found i can't ping the new sever(maybe it's another problem.)

Thanks.

Riaan.Badenhorst's picture

Hi,

Yes, you'd want to use the same name and IP (but you could get away with an IP address change as long as DNS reflects it).

Build test machine and then perform the backup and restore on it so you can get familiar with the process.

And please read the note. If you did you would have seen the following in step 1.

NOTE ABOUT DOMAINS DURING SETUP:
  • If the system was in a specific domain or workgroup, do not join the domain or workgroup at this time.
  • If you are recovering a domain controller, do not perform the domain controller installation process at this time.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Marianne's picture

You REALLY need to follow the TN exactly.

Please read this section under How to use this guide: carefully:

The guide is intended for restore back to the original machine.  If the machine is damaged and replaced with another machine (regardless of being 99.999% identical make/model) this is no longer considered the original machine.  You may attempt to treat it like an original restore (using w2koption), but there is a risk that restore will result in a non-bootable system (if this is the case, retry without w2koption).  For non-original system restore do not use w2koption.  If target is not the original, the larger the difference from the original machine, the lower the success rate of a bootable system.
 

It seems in your case you will be better off trying BMR.

See the link to BMR Admin guide in Riaan's post. 
But even BMR is not intended for 'cloning'. 
Restore to different hardware is supported.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

HowardYu's picture

Thanks guys, i tested and failed, i must follow the TN exactly.

I'm not clear at 5. Start the restore process.

A. Do not elect to restore the System State/Shadow Copy Components at
the same time.

B. By default, the System State/Shadow Copy Components assumes the restore is to different
hardware (and NOT the original machine) and does not restore the registry hive:

So I think i no need to do restore the System State/Shadow Copy Components because it's original, am I right?

Riaan.Badenhorst's picture

It is saying that you must first restore the system drives (usually C, but maybe C and others depending on your OS is installed). After restoring those drives, proceed to step D. In step D, depending on whether it is the original or not, you perform or skip certain steps.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

ChAmp35's picture

You have to restore the System State/Shadow Copy Component for full system recovery.

If I am correct then

"A" means first only restore the system drives like C: , D: only  (do not restore system state in this job, restore system state in another job once restore of these drives complete successfully.)

"B" while restoring system states/shadow copy compenents, it is assumed as restoring these compenents to some other system, so eleminate this assumption W2koption.exe utility is used to notify netbackup that restore of these compenents is attempting over same system.

HowardYu's picture

Thank you guys, I realize that not only C drive but maybe also System State/Shadow Copy Component. After C drive successfully by rebooting, it's still not my original system. I'll try it again.

ChAmp35's picture

restore all system drives in one job and then go for System state/shadow copy components in another job.

Marianne's picture

Again - steps in the TN must be followed precisely.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Riaan.Badenhorst's picture

Howard,

For your own and other forum user's benefit, why don't you document each step you're following with screenshot, copy and paste, or a video maybe. Then you'll have a reference and also a tutorial for others.

We might then also be able to see what you did and spot a mistake if one was made.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

HowardYu's picture

Thanks guys, I found C and Shadow Copy Components but not System State.

The erro is below: even i can't boot from F8

10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.879f
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 4176896
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 65536
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 0
10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a0
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 60416
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a1
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 7168
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 65536
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 0
10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a2
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 58880
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:33 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a4
10:28:33 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:33 (9029.001) (9029.001) WRN - desired byte count: 16896
10:28:33 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:34 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a5
10:28:34 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:34 (9029.001) (9029.001) WRN - desired byte count: 23040
10:28:34 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:34 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a6
10:28:34 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:34 (9029.001) (9029.001) WRN - desired byte count: 51200
10:28:34 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:34 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a7
10:28:34 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:34 (9029.001) (9029.001) WRN - desired byte count: 38400
10:28:34 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:35 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a8
10:28:35 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:35 (9029.001) (9029.001) WRN - desired byte count: 56320
10:28:35 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:35 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a9
10:28:35 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:35 (9029.001) (9029.001) WRN - desired byte count: 47104
10:28:35 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87be (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87bf (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c0 (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c1 (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c2 (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c3 (WIN32 -536836977: Unknown error)
10:28:45 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c4 (WIN32 -536836977: Unknown error)
10:28:45 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c5 (WIN32 -536836977: Unknown error)
10:28:45 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c6 (WIN32 -536836977: Unknown error)
10:28:46 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c7 (WIN32 -536836977: Unknown error)
10:30:12 (9029.001) (9029.001) INF - TAR EXITING WITH STATUS = 5
10:30:12 (9029.001) (9029.001) INF - TAR RESTORED 14597 OF 16464 FILES SUCCESSFULLY
10:30:12 (9029.001) (9029.001) INF - TAR KEPT 0 EXISTING FILES
10:30:12 (9029.001) (9029.001) INF - TAR PARTIALLY RESTORED 744 FILES
10:30:13 (9029.xxx) INF - Status = the restore failed to recover the requested files.

HowardYu's picture

Hi, I tried it again, I can restore C drive and Shadow Copy Components successfully, but not System State.

My is Win2008R2 64bit, as it said the w2koption command - No need to run below command for Win 2008
Clients-

My step is restore C then Shadow Copy Components then System State.

Error logs:

10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.879f
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 4176896
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 65536
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 0
10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a0
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 60416
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a1
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 7168
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 65536
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 0
10:28:32 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a2
10:28:32 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:32 (9029.001) (9029.001) WRN - desired byte count: 58880
10:28:32 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:33 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a4
10:28:33 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:33 (9029.001) (9029.001) WRN - desired byte count: 16896
10:28:33 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:34 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a5
10:28:34 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:34 (9029.001) (9029.001) WRN - desired byte count: 23040
10:28:34 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:34 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a6
10:28:34 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:34 (9029.001) (9029.001) WRN - desired byte count: 51200
10:28:34 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:34 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a7
10:28:34 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:34 (9029.001) (9029.001) WRN - desired byte count: 38400
10:28:34 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:35 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a8
10:28:35 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:35 (9029.001) (9029.001) WRN - desired byte count: 56320
10:28:35 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:35 (9029.001) (9029.001) WRN - error writing object: System State:\_SharedHardlinkData_\d89f2c5e.10000.87a9
10:28:35 (9029.001) (9029.001) WRN - error writing byte: 0
10:28:35 (9029.001) (9029.001) WRN - desired byte count: 47104
10:28:35 (9029.001) (9029.001) WRN - actual byte count: 256
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87be (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87bf (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c0 (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c1 (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c2 (WIN32 -536836977: Unknown error)
10:28:44 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c3 (WIN32 -536836977: Unknown error)
10:28:45 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c4 (WIN32 -536836977: Unknown error)
10:28:45 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c5 (WIN32 -536836977: Unknown error)
10:28:45 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c6 (WIN32 -536836977: Unknown error)
10:28:46 (9029.001) (9029.001) ERR - unable to create object for restore: System State:\_SharedHardlinkData_\d89f2c5e.10000.87c7 (WIN32 -536836977: Unknown error)
10:30:12 (9029.001) (9029.001) INF - TAR EXITING WITH STATUS = 5
10:30:12 (9029.001) (9029.001) INF - TAR RESTORED 14597 OF 16464 FILES SUCCESSFULLY
10:30:12 (9029.001) (9029.001) INF - TAR KEPT 0 EXISTING FILES
10:30:12 (9029.001) (9029.001) INF - TAR PARTIALLY RESTORED 744 FILES
10:30:13 (9029.xxx) INF - Status = the restore failed to recover the requested files.

HowardYu's picture

Thank you guys.

I can restore C and Shadow Copy Components but not System_State.

The client is win2008R2, so no need to run w2koption as the document said.

My steps are C -> Shadow Copy Components -> System_State

Even after failing on System_State restore, can't reboot 2008R2 successful(blue screen Status: 0xc000000e
)

Did I make something wrong?

Thanks.

Marianne's picture

I see in the TN that Shadow Copy Components or System_State must be restored, not both.

Shadow Copy Components actually includes System_State.

The TN also says:

E. Upon completion of the restore, check the tar log again for any problems.  Once again, DO NOT REBOOT.

Did you do that? 
The idea here is to check reason for failure in tar log and fix the problem before rebooting.
 

The TN then also says that you need to stop NBU services before rebooting. Did you do that?

8. Stop the service named "NetBackup Client Service" or "NetBackup Legacy Client Service".

NOTE: After the Restore job completes, the NetBackup process named bpinetd.exe has pending registry-merge responsibilities post-restore.  It will perform the queued registry-merge tasks upon graceful shutdown of the process.   Killing the process (bpinetd.exe) using Task Manager or other tools will prevent the registry merge from happening. This will cause a post-restore boot failure.

9. Transfer logs from restore before rebooting!

Transfer the client's NetBackup logs to an area where you can access them if the post-restore reboot fails.

Did you do this? 
Can you post the tar log here as File attachment?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

HowardYu's picture

Hi, thanks.

But i saw it said "Do not elect to restore the System State/Shadow Copy Components at
the same time."

The Stop the service named i think it means on client, so I did.

Even I restore Shadow Copy Components and C drive, but it doesn't restore to my original one, so I assume it should be restore System State as well.

Riaan.Badenhorst's picture

Howard,

I suggest you setup BMR, its free, and will probably work better if you're restoring to the same hardware.

Check out the BMR guide in my original post.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

HowardYu's picture

One more question, restore both System State/Shadow Copy Components is right step?

Riaan.Badenhorst's picture

System state is a component of the Shadow Copy Components. The note says to restore both, and if it fails you can try to restore ONLY the system state again.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

HowardYu's picture

Hi, let me clear it, I can restore Shadow Copy Components only, right because System state is a component of the Shadow. but I don't get it "if it fails you can try to restore ONLY the system state again." it means Shadow Copy Components failed?

Thanks.

Riaan.Badenhorst's picture

Hi Howard,

If its still not working use BMR, or open a support case so they can assist you.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Marianne's picture

I am repeating my previous question - have you copied the tar log off the client as per steps in the TN?

Please copy the log to tar.txt and post here as file attachment.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

HowardYu's picture

Dear all, finally it's successfully, i've to run the commands  -same_hardware while do system state and Shadow copy, not sure why but it's indeed.

Thanks all.