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

Windows 2003 complete client restore

Created: 05 Jul 2012 • Updated: 17 Jul 2012 | 11 comments
This issue has been solved. See solution.

Hi All,

I am restoring complete windows 2003 client(vm) on another virtual machine.

-backup taken as standard client 

-restore is also standard not vmdk file restore

-hostname is same

-OS installed on new machine is also same

-nbu client is 6.5.6 as it was on earlier machine

-Master server 6.5.6 on HP-UX 11.23

I am firing restore from client server, there is no communication issue, as bpclntcmd runs fine from client server

============================================================================================================

restore gets active but fails in between with sattus 5. Below are the job logs from activity monitor:

Jul 5, 2012 3:23:27 PM - begin Restore
Jul 5, 2012 3:23:42 PM - restoring from image
oceanus_1338223432
Jul 5, 2012 3:23:46 PM - connecting
Jul 5, 2012 3:23:42 PM - requesting resource TRANSPORT Jul 5, 2012 3:23:42 PM - Info nbjm (pid=11061) NBU status: 2075, EMM
status: Fibre Transport resources are not available Jul 5, 2012 3:23:42 PM - Info nbjm (pid=11061) NBU status: 2075, EMM
status: Fibre Transport resources are not available Jul 5, 2012 3:23:50 PM - connected; connect time: 0:00:00 Jul 5, 2012 3:23:50 PM - started process bptm (pid=6323) Jul 5, 2012 3:23:54 PM - begin reading Jul 5, 2012 3:25:31 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for registry file to take effect: C:\Documents and Settings\LocalService\NTUSER.DAT Jul 5, 2012 3:25:32 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for registry file to take effect: C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat
Jul 5, 2012 3:25:33 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for registry file to take effect: C:\Documents and Settings\NetworkService\NTUSER.DAT
Jul 5, 2012 3:25:34 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for registry file to take effect: C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat
Jul 5, 2012 3:29:10 PM - end reading; read time: 0:05:16 Jul 5, 2012 3:29:12 PM - begin reading Jul 5, 2012 3:30:19 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\glib-2.0.dll (temp=C:\Program Files\VMware\VMware Tools\QQYCQ3J2.NBU) Jul 5, 2012 3:30:20 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\gmodule-2.0.dll (temp=C:\Program Files\VMware\VMware Tools\QQQ4R3J2.NBU) Jul 5, 2012 3:30:21 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\gobject-2.0.dll (temp=C:\Program Files\VMware\VMware Tools\QQIWR3J2.NBU) Jul 5, 2012 3:30:22 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\gthread-2.0.dll (temp=C:\Program Files\VMware\VMware Tools\QQAOS3J2.NBU) Jul 5, 2012 3:30:23 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\iconv.dll (temp=C:\Program Files\VMware\VMware Tools\QQ2GT3J2.NBU) Jul 5, 2012 3:30:24 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\icudt38l.dat (temp=C:\Program Files\VMware\VMware Tools\QQU7U3J2.NBU) Jul 5, 2012 3:30:25 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\intl.dll (temp=C:\Program Files\VMware\VMware Tools\QQMZU3J2.NBU) Jul 5, 2012 3:30:26 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\vmacthlp.exe (temp=C:\Program Files\VMware\VMware Tools\QQERV3J2.NBU) Jul 5, 2012 3:30:27 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\VMControlPanel.cpl (temp=C:\Program Files\VMware\VMware Tools\QQ6JW3J2.NBU) Jul 5, 2012 3:30:28 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - System needs to be rebooted for file to take effect: C:\Program Files\VMware\VMware Tools\vmtools.dll (temp=C:\Program Files\VMware\VMware Tools\QQYAX3J2.NBU) Jul 5, 2012 3:35:18 PM - end reading; read time: 0:06:06 Jul 5, 2012 3:35:21 PM - begin reading Jul 5, 2012 3:42:21 PM - end reading; read time: 0:07:00 Jul 5, 2012 3:42:23 PM - begin reading Jul 5, 2012 3:48:16 PM - end reading; read time: 0:05:53 Jul 5, 2012 3:48:18 PM - begin reading Jul 5, 2012 3:54:29 PM - end reading; read time: 0:06:11 Jul 5, 2012 3:54:33 PM - begin reading Jul 5, 2012 3:56:04 PM - end reading; read time: 0:01:31 Jul 5, 2012 3:56:04 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - Removable Storage Management: unable to import database (WIN32 21: The device is not ready. ) Jul 5, 2012 3:56:05 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - Removable Storage Management: may not be fully functional at the moment Jul 5, 2012 3:56:05 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - Removable Storage Management: please attempt to reimport the database after rebooting Jul 5, 2012 3:56:06 PM - Warning bpbrm (pid=6321) from client
oceanus: WRN - Removable Storage Management: to reimport, execute 'W2KUtil -rsm -restore' from a Command Prompt Jul 5, 2012 3:56:06 PM - Error bpbrm (pid=6321) client restore EXIT STATUS 5: the restore failed to recover the requested files
===========================================================================================================
 
Please help guys

Comments 11 CommentsJump to latest comment

Andy Welburn's picture

HOWTO: Use NetBackup to perform a restore for a total and complete recovery of Windows XP, 2000, 2003, or 2008 client(s) that includes C: (and other system) drive(s), Shadow Copy Component, and/or System_State from a reliable full Windows-NT backup without IDR or BMR in the event of a Disaster (or need to fall back to a known working state).
http://www.symantec.com/business/support/index?pag...

By the statement "backup taken as standard client" I presume you just meant it was backed up as a 'normal' client & not dealt with as a VM client, as opposed to policy being "Standard" & not "MS_Windows-NT" type?

Pinku's picture

yes, that is the same technote i am following.

And yes, it was backed up as normal client. VM has nothing to do here. Policy type was MS-windows-NT type.

I have 2 concerns in the above job log, hope you have anything over that

1) Removable Storage Management: unable to import database (WIN32 21: The device is not ready. )

2) Removable Storage Management: to reimport, execute 'W2KUtil -rsm -restore' from a Command Prompt

Pinku's picture

I blv RSM service is causing issue, I'll try performing restore by disabling it. 

Any inputs?

Andy Welburn's picture

We always disabled RSM for backups as it's known to cause 'issues' there (partially complete backups etc), you've nothing to lose by disabling RSM when you try the restore procedure again.

We only ever had to do a handful of similar restore operations as this & if i have to be brutally honest only a third of them were successful......

Pinku's picture

It failed again with this error:

Jul 6, 2012 2:01:41 PM - Warning bpbrm (pid=24296) from client oceanus: WRN - Removable Storage Management: unable to import database (WIN32 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. )

Jul 6, 2012 2:01:42 PM - Error bpbrm (pid=24296) client restore EXIT STATUS 185: tar did not find all the files to be restored

I just want to be sure if the msg at Jul 6, 2012 2:01:41 PM a warning can cause this issue. Can I ignore this warning?

Marianne's picture

Please share more info about which restore step is producing these errors?
Did the System drives restore complete successfully or this the one producing the errors?

Have you checked the tar log as suggested in the TN?

Please upload your tar log as attachment.

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

Pinku's picture

I am stuck on first step only

-i am trying to restore system drives at first

-initially i tried restoring c and d drive simultaneously, but it failed
-then i tried restoring only c drive, it failed again

-attaching tar logs when i restored c drive only

AttachmentSize
tar_log.zip 940.03 KB
Marianne's picture

It failed again? With what status code? Still 185?

tar log shows 100% successful restore:

3:27:46.250 PM: [3888.3892] <2> tar_base::V_vTarMsgM: TAR - C:\wmpub\wmiislog\
3:27:46.250 PM: [3888.3892] <4> UnpackerTAR::getData(): INF - Complete data processed.
3:27:46.250 PM: [3888.3892] <4> file_system_restore::tfs_writeclose_start: INF - Set times successful.
3:27:46.921 PM: [3888.3892] <2> tar_base::V_vTarMsgW: INF - Removable Storage Management: successfully imported database
3:27:46.921 PM: [3888.3892] <2> tar_base::backup_finish: TAR - restore:                     66232 files
3:27:46.921 PM: [3888.3892] <2> tar_base::backup_finish: TAR - restore:          file data:  135296109 bytes  9 gigabytes
3:27:46.921 PM: [3888.3892] <2> tar_base::backup_finish: TAR - restore:         image data:  280182784 bytes  9 gigabytes
3:27:46.921 PM: [3888.3892] <2> tar_base::backup_finish: TAR - restore:       elapsed time:        800 secs     12429824 bps
3:27:46.921 PM: [3888.3892] <2> tar_base::V_vTarMsgW: INF - TAR EXITING WITH STATUS = 0
3:27:46.921 PM: [3888.3892] <2> tar_base::V_vTarMsgW: INF - TAR RESTORED 66229 OF 66232 FILES SUCCESSFULLY
3:27:46.921 PM: [3888.3892] <2> tar_base::V_vTarMsgW: INF - TAR KEPT 0 EXISTING FILES
3:27:46.921 PM: [3888.3892] <2> tar_base::V_vTarMsgW: INF - TAR PARTIALLY RESTORED 0 FILES
3:27:46.921 PM: [3888.3892] <2> tar_base::V_vTarMsgW: INF - A REBOOT OF THE MACHINE IS REQUIRED FOR ALL FILES TO TAKE EFFECT.

It seems to me you should be able to carry on with point B (not reboot, restore rest of system drives (e.g D if it is also a system drive)) followed by steps C and D....

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

SOLUTION
Pinku's picture

on activity monitor the job failed with status 5, 

-i was planning to restore shadow copy components after c drive, is that fine?

i will reboot then and den start d drive restore...

below is my next plan, any inputs plz share

1) restore c drive

2) restore shadow copy components

3) reboot

4) if system comes up then restore d drive

HEMANPR's picture

Need to create a new VM and Install Windows 2003 (Same SP, Windows Updates and bits) 

Named with a different name (Example: "Restore VM")

Install the NBU Client on "Restore VM"

Restore From Original Client To This New Named Client "Restore VM" - Remember give access for write on the New Named Client Properties (Master Server - Clients Tab - "Restore VM")

1. submit a job fo restore the System State (Remember Target = "Restore VM")

2. submit a job fo restore the Shadow Copy (Remember Target = "Restore VM")

3. submit a job fo restore the entire C:\ with Overwrite option (Remember Target = "Restore VM") 

On finish Restart "Restore VM" and then change the Computer name and IP to the original client.

Please let us know Thanks

Please MARK AS SOLUTION If my Post Help You. I use the following Symantec Products: Veritas Netbackup 7.5 On Windows Enterprise 2003 SP2 - / - Symantec EndPoint 12.1.100.157 RU1 On Windows Standard 2003 SP2 - / - Symantec&nb

Pinku's picture

Hi,

As per Marianne I proceeded after witnessing the successful restore of C drive in tar logs. But WHen I started with shadow copy restore it failed and below were the tar logs then:

nable to create object for restore: Shadow Copy Components:\System State\ (BEDS 0xE000FEDE: A failure occurred opening an object.
 
)
14:48:21 (1290194.001) TAR - Shadow Copy Components:\System State\System Files\
14:48:21 (1290194.001) ERR - unable to create object for restore: Shadow Copy Components:\System State\System Files\ (BEDS 0xE000FEDE: A failure occurred opening an object.
 
)
14:48:21 (1290194.001) TAR - Shadow Copy Components:\System State\System Files\System Files
14:48:21 (1290194.001) ERR - unable to create object for restore: Shadow Copy Components:\System State\System Files\System Files (BEDS 0xE000FEDE: A failure occurred opening an object.
 
)
14:48:41 (1290194.001) TAR - Shadow Copy Components:\System State\Registry\
14:48:41 (1290194.001) ERR - unable to create object for restore: Shadow Copy Components:\System State\Registry\ (BEDS 0xE000FEDE: A failure occurred opening an object.
 
)
14:48:41 (1290194.001) TAR - Shadow Copy Components:\System State\Registry\Registry
14:48:41 (1290194.001) ERR - unable to create object for restore: Shadow Copy Components:\System State\Registry\Registry (BEDS 0xE000FEDE: A failure occurred opening an object.
 
)
14:48:43 (1290194.001) TAR - Shadow Copy Components:\System State\COM+ Class Registration Database\
14:48:43 (1290194.001) ERR - unable to create object for restore: Shadow Copy Components:\System State\COM+ Class Registration Database\ (BEDS 0xE000FEDE: A failure occurred opening an object.
 
)
14:48:43 (1290194.001) TAR - Shadow Copy Components:\System State\COM+ Class Registration Database\COM+ REGDB
14:48:43 (1290194.001) ERR - unable to create object for restore: Shadow Copy Components:\System State\COM+ Class Registration Database\COM+ REGDB (BEDS 0xE000FEDE: A failure occurred opening an object.
 
)
 
Found a technote and apply the hotfix for VSS. That resolved the issue.
 
Thanks Everyone, I'll mark Marianne reply as solution as she suggested to move on even the job was failing in activity monitor.