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

NetBackup 7.0.1 and Windows 2008 R2 system state not included

Created: 05 Oct 2012 • Updated: 10 Oct 2012 | 5 comments

I have a ticket open with Symantec about this same issue, however is taking some time.

We use NetBackup 7.0.1 Build 20100707.  We are currently trying to use the *:\ directive or Shadow Copy Components:\ and even the System State:\ directive.  The backups show successful however when we attempt to do a restore the only things we see are the Shadow Copy Components > System Service.  The System State does not show up.  Our 2003 R2 servers seem to be doing fine.

Edit: 10/10/2012
------------------------

We've created a test policy with the server that was failing.  The Backup Selections use just Shadow Copy Components:\

When we run a vssadmin list writers we see that several writers have failed.  And we're actually getting warnings now. (See below)

Any suggestions?

Comments 5 CommentsJump to latest comment

captain jack sparrow's picture

shadow copy components include systemstate. simply select it and do backup. while restoration you would be able to see

 Cheers !!!

CJS

 

juliank's picture

Right I understand that, as I stated that was one of the directives we've tried.  The same result occured.

juliank's picture

Here is the Job Details:

10/10/2012 1:16:32 PM - estimated 28204 Kbytes needed
10/10/2012 1:16:32 PM - started process bpbrm (10084)
10/10/2012 1:16:34 PM - connecting
10/10/2012 1:16:37 PM - connected; connect time: 00:00:03
10/10/2012 1:16:43 PM - begin writing
10/10/2012 1:17:31 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open object: System State: (WIN32 -536805685: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\Task Scheduler\TasksStore (WIN32 -536805667: Unknown error)
10/10/2012 1:17:32 PM - Error bpbrm(pid=10084) from client mgmt22.us.local: ERR - Error encountered while attempting to get additional files for System State:\
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\VSS Express Writer Store\WriterMetadataStore (WIN32 -536805667: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\Performance Counter\PerformanceCounters (WIN32 -536805667: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\Automated System Recovery\BCD\BCD (WIN32 -536805679: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\Registry\Registry (WIN32 -536805679: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\Internet Information Services\IISCONFIG (WIN32 -536805679: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\Internet Information Services\IISMETABASE (WIN32 -536805679: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\System Files\System Files (WIN32 -536805679: Unknown error)
10/10/2012 1:17:32 PM - Warning bpbrm(pid=10084) from client mgmt22.us.local: WRN - can't open file: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536805679: Unknown error)
10/10/2012 1:17:36 PM - end writing; write time: 00:00:53
the requested operation was partially successful(1)
 
The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.
juliank's picture

 

10/10/2012 1:16:20 PM - requesting resource Disk_Staging_Group_2
10/10/2012 1:16:20 PM - requesting resource bup01.us.local.NBU_CLIENT.MAXJOBS.mgmt22.us.local
10/10/2012 1:16:20 PM - requesting resource bup01.us.local.NBU_POLICY.MAXJOBS.LTO4_SET02B
10/10/2012 1:16:20 PM - granted resource bup01.us.local.NBU_CLIENT.MAXJOBS.mgmt22.us.local
10/10/2012 1:16:20 PM - granted resource bup01.us.local.NBU_POLICY.MAXJOBS.LTO4_SET02B
10/10/2012 1:16:20 PM - granted resource MediaID=@aaaae;Path=T:\DiskStaging02;MediaServer=bup01.us.local
10/10/2012 1:16:20 PM - granted resource DiskStaging2
10/10/2012 1:16:20 PM - estimated 28204 Kbytes needed
10/10/2012 1:16:20 PM - begin Parent Job
10/10/2012 1:16:20 PM - begin Snapshot, Start Notify Script
10/10/2012 1:16:20 PM - started process RUNCMD (21776)
10/10/2012 1:16:20 PM - ended process 0 (21776)
Status 0
10/10/2012 1:16:20 PM - end Snapshot, Start Notify Script; elapsed time: 00:00:00
10/10/2012 1:16:20 PM - begin Snapshot, Step By Condition
Status 0
10/10/2012 1:16:20 PM - end Snapshot, Step By Condition; elapsed time: 00:00:00
10/10/2012 1:16:20 PM - begin Snapshot, Stream Discovery
Status 0
10/10/2012 1:16:20 PM - end Snapshot, Stream Discovery; elapsed time: 00:00:00
10/10/2012 1:16:20 PM - begin Snapshot, Read File List
Status 0
10/10/2012 1:16:20 PM - end Snapshot, Read File List; elapsed time: 00:00:00
10/10/2012 1:16:20 PM - begin Snapshot, Create Snapshot
10/10/2012 1:16:20 PM - started process bpbrm (15196)
10/10/2012 1:16:20 PM - started
10/10/2012 1:16:25 PM - begin Create Snapshot
10/10/2012 1:16:28 PM - Critical bpbrm(pid=15196) from client mgmt22.us.local: FTL - process_fs_list() failed, status 71    
10/10/2012 1:16:30 PM - end Create Snapshot; elapsed time: 00:00:05
10/10/2012 1:16:32 PM - end writing
Status 0
10/10/2012 1:16:32 PM - end Snapshot, Create Snapshot; elapsed time: 00:00:12
10/10/2012 1:16:32 PM - begin Snapshot, Policy Execution Manager Preprocessed
Status 1
10/10/2012 1:17:36 PM - end Snapshot, Policy Execution Manager Preprocessed; elapsed time: 00:01:04
10/10/2012 1:17:36 PM - begin Snapshot, Validate Image
Status 0
10/10/2012 1:17:36 PM - end Snapshot, Validate Image; elapsed time: 00:00:00
10/10/2012 1:17:36 PM - begin Snapshot, Delete Snapshot
10/10/2012 1:17:36 PM - started process bpbrm (22636)
10/10/2012 1:17:43 PM - end writing
Status 0
10/10/2012 1:17:43 PM - end Snapshot, Delete Snapshot; elapsed time: 00:00:07
10/10/2012 1:17:43 PM - begin Snapshot, Delete Snapshot On Exit
Status 0
10/10/2012 1:17:43 PM - end Snapshot, Delete Snapshot On Exit; elapsed time: 00:00:00
10/10/2012 1:17:43 PM - begin Snapshot, End Notify Script
10/10/2012 1:17:43 PM - started process RUNCMD (21600)
10/10/2012 1:17:43 PM - ended process 0 (21600)
Status 0
10/10/2012 1:17:43 PM - end Snapshot, End Notify Script; elapsed time: 00:00:00
Status 1
10/10/2012 1:17:43 PM - end Parent Job; elapsed time: 00:01:23
the requested operation was partially successful(1)
 
The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.
juliank's picture

Also what would the best solution be if we set a policy to include ALL_LOCAL_DRIVES and Shadow Copy Components:\  

Then for a host that was a part of that policy we would exclude ALL_LOCAL_DRIVES but then put in an exception for several various folders on D:\.

Would this work?  Sorry this is sort of related and sort of not.