Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Unable to backup System State on various Windows Servers

Created: 06 Feb 2013 • Updated: 02 Apr 2014 | 8 comments
This issue has been solved. See solution.

I get this error message on a few of my servers indicating that I'm unable to backup System State. 

OS:  Windows 2003 Standard 

Netbackup version:  7.0.1

Status code:1

Vss writers are ok and listed. 

Any ideas?

02/06/2013 2:06:16 PM - requesting resource B9_Staging_2_SVR720
02/06/2013 2:06:16 PM - requesting resource snnsvr720.NBU_CLIENT.MAXJOBS.snnsvr150
02/06/2013 2:06:16 PM - requesting resource snnsvr720.NBU_POLICY.MAXJOBS.C_B9_DiskStaging_SVR720_2
02/06/2013 2:06:19 PM - granted resource snnsvr720.NBU_CLIENT.MAXJOBS.snnsvr150
02/06/2013 2:06:19 PM - granted resource snnsvr720.NBU_POLICY.MAXJOBS.C_B9_DiskStaging_SVR720_2
02/06/2013 2:06:19 PM - granted resource MediaID=@aaaaB;DiskVolume=Y:\;DiskPool=STAG2_SVR720;Path=Y:\;StorageServer=snnsvr720;MediaServer=snnsvr720
02/06/2013 2:06:19 PM - granted resource STAG2_STU_SVR720
02/06/2013 2:06:19 PM - started
02/06/2013 2:06:20 PM - estimated 1295344 Kbytes needed
02/06/2013 2:06:21 PM - started process bpbrm (2704)
02/06/2013 2:06:29 PM - connecting
02/06/2013 2:06:32 PM - connected; connect time: 00:00:03
02/06/2013 2:06:50 PM - begin writing
02/06/2013 2:23:52 PM - Warning bpbrm(pid=2704) from client snnsvr150: WRN - can't open object: Shadow Copy Components:\System Service\Event Logs\Event Logs (BEDS 0xE0009421: No component files present on the snapshot.)
02/06/2013 2:23:52 PM - Warning bpbrm(pid=2704) from client snnsvr150: WRN - can't open object: Shadow Copy Components:\System Service\Windows Management Instrumentation\WMI (BEDS 0xE0009421: No component files present on the snapshot.)
02/06/2013 2:23:58 PM - Warning bpbrm(pid=2704) from client snnsvr150: WRN - can't open file: System State:\System Files\System Files (WIN32 -536832991: Unknown error)
02/06/2013 2:23:58 PM - Error bpbrm(pid=2704) from client snnsvr150: ERR - Error encountered while attempting to get additional files for System State:\
02/06/2013 2:23:58 PM - Warning bpbrm(pid=2704) from client snnsvr150: WRN - can't open file: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 -536832991: Unknown error)
02/06/2013 2:23:58 PM - Warning bpbrm(pid=2704) from client snnsvr150: WRN - can't open file: System State:\Registry\Registry (WIN32 -536832991: Unknown error)
02/06/2013 2:23:59 PM - Warning bpbrm(pid=2704) from client snnsvr150: WRN - can't open file: System State:\Internet Information Services\IISMETABASE (WIN32 -536832991: Unknown error)
02/06/2013 2:25:05 PM - end writing; write time: 00:18:15
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.

 

 

Comments 8 CommentsJump to latest comment

Will Restore's picture

BEDS 0xE0009421: No component files present on the snapshot

see this technote:

Article URL http://www.symantec.com/docs/TECH147574

 

Solution

 

1. Verify no backup jobs are active for the client, run vssadmin list writers on the affected client: confirm all writers are listed as State: [1] Stable

 

2. If any writers are not in a stable state, reboot the client to reset the writers

 

3. Check the Windows Open File Backup setting on the master server to ensure VSS is being used
Host Properties > Master Servers > (master) > Client Attributes > Windows Open File Backups tab
Ensure the client name is added to this list, then highlight client in the list, and select 'Use Microsoft Volume Shadow Service (VSS)'

 

4. This error can also happen if the snapshot size exceeds the snapshot maximum size 'Use limit' configured for the volume.  If this happens, Windows will automatically delete the snapshot, even though NetBackup still wants to use it

 

Will Restore -- where there is a Will there is a way

Will Restore's picture

or this one:

 

  Article URL http://www.symantec.com/docs/TECH177496

 

Cause

 

This issue has been observed when the installation path for NetBackup has been turned into a Junction Point pointing to another volume.

Example:

C:\Program Files>dir
 Volume in drive C has no label.
 Volume Serial Number is D428-983F
 Directory of C:\Program Files
08/11/2011  03:13 PM    <DIR>          .
08/11/2011  03:13 PM    <DIR>          ..
08/02/2011  12:07 PM    <DIR>          Common Files
06/23/2011  01:12 PM    <DIR>          ComPlus Applications
06/23/2011  01:12 PM    <DIR>          Internet Explorer
06/23/2011  01:12 PM    <DIR>          Outlook Express
08/11/2011  03:13 PM    <JUNCTION>     Veritas
06/23/2011  01:21 PM    <DIR>          VMware
06/23/2011  01:12 PM    <DIR>          Windows NT
               0 File(s)              0 bytes
               9 Dir(s)  12,952,461,312 bytes free

 

Will Restore -- where there is a Will there is a way

Dyneshia's picture

Please upload the bpbrm from the media server and bpfis and bpbkar from the client.

Also check the application event viewer for errors during the time of the backup.

If possible can you reboot the client ?

NBUIT's picture

How do you find  the snapshot maximum size 'Use limit' configured for the volume? 

Nagalla's picture

you would need to find that from Client ---> Drive properties -->Shadow copies tab.

recommended to keep "No limit"

Will Restore's picture

according to the link in my post above

 

To check the Maximum size 'Use limit':
A. Open My Computer > rt-click on the C:\ drive > select Properties
B. Select the 'Shadow Copies' tab
C. Select the C:\ drive and click 'Settings' to view the 'Use limit' values

* If 'No limit' is selected, then Windows will not delete the snapshot regardless of how much space it consumes.   However, if the snapshot is very large, and there is not much disk space left on C:\, then it might be failing to create the snapshot due to space restrictions.

* If 'Use limit' is specified, make sure the specified value is large enough to contain the snapshot with room to spare.  Symantec recommends no less then 1 GB.  Microsoft recommends the snapshot 'Use limit' be configured for roughly 10% of occupied space. For example, if the C:\ drive has 100GB of data on it, the 'Use limit' should be set to 10 GB.

Will Restore -- where there is a Will there is a way

Stumpr2's picture

 

TECH193539 NetBackup-related technotes for troubleshooting Microsoft Volume Shadow Copy service (VSS) issues
TECH126295 Frequently asked questions about VSS (Microsoft's Volume Shadow Copy Service) and VSP (VERITAS Snapshot provider)
TECH126922 DOCUMENTATION: Statement of change of support for Windows Open File Backup methods in NetBackup 7.0
TECH129082 "BEDS 0xE000FEDF: A failure occurred reading an object" when backing up DFSR data
TECH139365 How to configure the storage area for shadow copies to go to a different NTFS volume on a Windows 2003 server using BackupExec
TECH147574 Windows backup exit status 1 for Shadow Copy Components
TECH153955 How to configure the storage area for shadow copies to go to a different NTFS volume on a Windows 2008 server using BackupExec
TECH156750 Troubleshooting Status Code 156 "snapshot error encountered" occurs when using VSS for Open file backups or snapshots
TECH158127 NetBackup defaults to using VSS in NetBackup 7.0 and higher as the Open File Snapshot provider. In some cases, there are third party
VSS providers installed that are not configured properly
TECH38709 STATUS CODE: 156 "snapshot error encountered" occurs when utilizing VSP or VSS for open file backups.
TECH54530 DOCUMENTATION: VSS is the recommended snapshot method for Windows 2003 Clients.
TECH72112 NetBackup 6.5.4 changes the settings for Microsoft's Shadow Copies for Shared Folders option
TECH72361 After upgrading to NetBackup 6.5.4, adjustments may be made to Windows VSS settings that lead to individual snapshots being deleted
unexpectedly on a Windows client. This affects snapshots that are taken outside of NetBackup manually or with a third party application
TECH83223 How to purge the Microsoft Volume Shadow copy Service (VSS) snapshots if they do not get deleted automatically after the backup
of Shadow Copy Components: for BackupExec
TECH129884 Backup of Hyper-V Guest OS fails intermittently with Status 156

VERITAS ain't it the truth?

SOLUTION