System State Backup for Windows Server 2008 Fails

[avijitc]

Hi

I am using BE2010 R2 as my backup software. I am currently configured to take system state backup for my Application Server. The job fails with error. Please find below the error : 

Job Log: BEX_SURBACKUP_00104.xmlJob Log for AOS3 System State 

      Completed status: Failed    See error(s) 

      Expand AllCollapse All 

      Job Information

Job server: SURBACKUP

Job name: AOS3 System State

Job started: Saturday, March 10, 2012 at 11:58:53 AM

Job type: Backup

Job Log: BEX_SURBACKUP_00104.xml

Drive and media mount requested: 3/10/2012 11:58:53 AM

Device and Media Information

Drive and media information from media mount: 3/10/2012 11:58:54 AM

Drive Name: AOS3 System State

Media Label: B2D000031

Media GUID: {c33b7ffd-6a3c-4c92-b66d-ad26bd4c4953}

Overwrite Protected Until: 1/1/1900 5:30:00 AM

Appendable Until: 3/16/2012 11:58:54 AM

Targeted Media Set Name: SDP DAILY OVERWRITE POLICY

All Media Used

 B2D000031

      Job Operation - Backup 

            Backup Options

Media operation - Overwrite media.

Compression Type: Hardware [if available, otherwise none]

Encryption Type: None

            Server - AOS3.surakshanet.com

AOFO: Started for resource: "\\AOS3.surakshanet.com\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

The following volumes are dependent on resource: "C:" "D:" "\\?\VOLUME{12556081-2C6F-11E0-8201-806E6F6E6963}" .

The snapshot provider used by VSS for volume C: - Symantec Software VSS Provider (Version 1.0).

The snapshot provider used by VSS for volume D: - Symantec Software VSS Provider (Version 1.0).

The snapshot provider used by VSS for volume \\?\VOLUME{12556081-2C6F-11E0-8201-806E6F6E6963} - Symantec Software VSS Provider (Version 1.0).

Network control connection is established between 192.168.8.110:64158 <--> 192.168.8.105:10000

Network data connection is established between    192.168.8.110:64178 <--> 192.168.8.105:53389

Set Information - \\AOS3.surakshanet.com\System?State

                        Backup Set Information

Family Name: "Media created 3/10/2012 11:58:53 AM"

Backup of "\\AOS3.surakshanet.com\System?State"

Backup set #1 on storage media #1

Backup set description: "AOS3 System State"

Backup Method: Full - Back Up Files - Reset Archive Bit

Backup started on 3/10/2012 at 11:59:19 AM.

Backup Set Detail Information

V-79-57344-65245 - A failure occurred accessing the object list.

The item \\AOS3.surakshanet.com\System?State\System Files\System Files in use - skipped.

Backup completed on 3/10/2012 at 12:22:57 PM.

Backup Set Summary

Backed up 16 System State components

1 item was skipped.

Processed 11,148,977,181 bytes in  23 minutes and  38 seconds.

Throughput rate: 450 MB/min

Compression Type: None

      Job Operation - Verify 

            Server - AOS3.surakshanet.com

                  Set Information - \\AOS3.surakshanet.com\System?State 

                  \\AOS3.surakshanet.com\System?State

                        Verify Set Information

Verify of "\\AOS3.surakshanet.com\System?State \\AOS3.surakshanet.com\System?State"

Backup set #1 on storage media #1

Backup set description: "AOS3 System State"

Verify started on 3/10/2012 at 12:23:02 PM.

Verify Set Detail Information

Verify completed on 3/10/2012 at 12:28:05 PM.

Verify Set Summary

Contents verified.

Processed 11,148,977,181 bytes in  5 minutes and  3 seconds.

Throughput rate: 2105 MB/min

      Job Completion Status

Job ended: Saturday, March 10, 2012 at 12:28:06 PM

Completed status: Failed

Final error: 0xe000fedd - A failure occurred accessing the object list.

Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-65245

      Errors

      Click an error below to locate it in the job log

Backup- \\AOS3.surakshanet.com\System?StateV-79-57344-65245 - A failure occurred accessing the object list.

      Exceptions

      Click an exception below to locate it in the job log

Backup- \\AOS3.surakshanet.com\System?StateThe item \\AOS3.surakshanet.com\System?State\System Files\System Files in use - skipped.

Please let me know the solution as this is a vital server in my environment. Please let me know if you need any more information for the solution.

Thanks

Avijit Chakraborty

[pkh]

Try the solutions in these documents

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

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

Also, you should turn on AOFO and select VSS is the technology to be used.

[avijitc]

Hi

I am already taking the backup with AOFO on and VSS selected as Microsoft Volume Shadow Copy Service. I am not using BE over apache and it is configured to run on IIS. I am not facing any problem with other servers running on Windows Server 2008. But this server is having problem. 

[CraigV]

Hi,

You can sometimes get this error if an AV is either actively scanning the BE services, or the AV blocks BE from accessing the System State.

Check and make sure that this isnt the case, and if need be, put in an exclusion in the AV for the BE services.

Thanks!

[avijitc]

Can anyone help me out???

[CraigV]

...if you don't respond to what's advised/suggested/pointed out to you, then nobody knows if what was suggested has worked or not. Therefore people are waiting for feedback.

[ltjimster]

Have you tried maybe changing the AOFO option on the Microsoft Volume Shadow Copy service to "System" instead of "Automatic"

James

[avijitc]

Hi

I have changed the option to System. Please find attached the screen shot. Still I am facing the same error. Just for a quick information I checked with my Application and found some of the VSS writers in Timed Out State. 

C:\Users\administrator.SURAKSHANET>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'

   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

   State: [1] Stable

   Last error: No error

Writer name: 'VSS Metadata Store Writer'

   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

   State: [1] Stable

   Last error: No error

Writer name: 'Performance Counters Writer'

   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

   State: [1] Stable

   Last error: No error

Writer name: 'System Writer'

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Instance Id: {81dee129-d531-4f5d-80a4-818954a63800}

   State: [7] Failed

   Last error: Timed out

Writer name: 'ASR Writer'

   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   Writer Instance Id: {e723329e-cbd8-4458-ac50-c1187f478c4d}

   State: [1] Stable

   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

   Writer Instance Id: {74c6a0d4-9e43-4173-bb51-4344a044d7f5}

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Writer Instance Id: {2cec7e3a-14e0-4ea8-9585-4b4627c03114}

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Writer Instance Id: {71309112-19d0-4d2f-ba26-a918ebed4568}

   State: [1] Stable

   Last error: No error

Writer name: 'SqlServerWriter'

   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

   Writer Instance Id: {4cc52f8d-ea45-40bb-8c3a-bce7f7698cbb}

   State: [1] Stable

   Last error: No error

Writer name: 'IIS Config Writer'

   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

   Writer Instance Id: {ab7a7f81-423a-43a1-b629-a6847effa3b0}

   State: [7] Failed

   Last error: Timed out

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {d73553b4-65e1-4479-bbdf-4283765157e3}

   State: [1] Stable

   Last error: No error

Writer name: 'IIS Metabase Writer'

   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

   Writer Instance Id: {6be60181-f174-4112-8e30-d6b2b28999af}

   State: [7] Failed

   Last error: Timed out

C:\Users\administrator.SURAKSHANET>

Can you just put light that if this can be problem factor. 

[CraigV · Accepted solution]

THis can be the cause of the issue, and you have 1 of 2 options:

1. Restart the server which will fix the VSS wirters.

2. Check the TN below and then reregister the VSS *.DLLs. This is nonintrusive and doesn't require a restart:

http://www.symantec.com/business/support/index?page=content&id=TECH70486

Thanks!