Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
VSS issues on AD/ Files Server

Answered VSS issues on AD/ Files Server

  • Saturday, June 16, 2012 4:04 AM
     
     
    Sign In to Vote
    0

    Hi

    I have a server is SAN boot,

    Windows 2008 R2, work as DC, File Services and FSRM, using netbackup 7.0 to backup this server.

    Recently encounter this problem when backup the shadow copy component it failed with backup partially successfully. Here are the backup logs.

    6/7/2012 5:11:11 AM - Warning bpbrm(pid=32240) from client adfl1: WRN - can't open object: Shadow Copy Components: (BEDS 0xE000FECB: A failure occurred accessing the backup component document.)
    6/7/2012 5:11:22 AM - Warning bpbrm(pid=32240) from client adfl1: WRN - can't open object: Shadow Copy Components:\System Service\File Server Resource Manager\FSRM Global Configuration (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
    6/7/2012 5:11:23 AM - Warning bpbrm(pid=32240) from client adfl1: WRN - can't open object: Shadow Copy Components:\System Service\File Server Resource Manager\FSRM Classification Module Configuration (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
    6/7/2012 5:11:23 AM - Warning bpbrm(pid=32240) from client adfl1: WRN - can't open object: Shadow Copy Components:\System Service\File Server Resource Manager\FSRM Configuration on Volume D:/ (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
    6/7/2012 5:11:24 AM - Warning bpbrm(pid=32240) from client adfl1: WRN - can't open object: Shadow Copy Components:\System Service\File Server Resource Manager\FSRM Configuration on Volume E:/ (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
    6/7/2012 5:11:24 AM - Warning bpbrm(pid=32240) from client adfl1: WRN - can't open object: Shadow Copy Components:\System Service\File Server Resource Manager\FSRM Reports (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
    6/7/2012 5:11:25 AM - Warning bpbrm(pid=32240) from client adfl1: WRN - can't open object: Shadow Copy Components:\System Service\Windows Management Instrumentation\WMI (BEDS 0xE000FEDD: A failure occurred accessing the object list.)
    6/7/2012 7:23:36 AM - end writing; write time: 03:22:43
    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.

    I have log a case with Netbackup support after they troubleshooting, it said it because of Netbackup is not able to access the File server objects has to checked, Whether there is permission issue or the objects got corrupted. Symantec request me check with the VSS vendors.

    I got check the share folder for permission, it gor remove "SYSTEM" group from the list. Will this affected the backup? Actually what this "SYSTEM" group for?

    Please find below of my vssadmin writer list

    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: {e0a23036-8645-4335-bdb1-51491ca3813b}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {7f96acfa-19e4-4df5-a60b-35087809ba84}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {eb9ef90b-f891-48fd-9de8-3366c192662d}
       State: [1] Stable
       Last error: No error

    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {ee52aab9-70ae-44ab-8f3b-5caba68b6a15}
       State: [7] Failed
       Last error: Timed out

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {35c9812c-3a16-4553-b998-4801c9f4bc84}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {df1088fc-32e4-44df-8099-b8152bcc1482}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {2cceb3f3-10f7-4074-adc4-c9a0bdccf4f5}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {ec239e2f-58ce-4719-b26b-c935ce360b15}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {77196b55-d204-4334-8bac-ef3ac94f3ba2}
       State: [1] Stable
       Last error: No error

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {d6bdaaa4-8894-44e6-9c49-de04b0df0af1}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {06e594c9-5925-4dc4-9811-b7ac6a168539}
       State: [7] Failed
       Last error: Timed out

    Writer name: 'DFS Replication service writer'
       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
       Writer Instance Id: {3fa6ad33-5106-4ddd-8650-385df582365d}
       State: [1] Stable
       Last error: No error

    Because Windows NT backup do not have shadow copy component to select for backup as i have run windows NT backup backup system state it complete successfully. This mean not related with windows?


     

All Replies

  • Saturday, June 16, 2012 7:56 AM
     
     Answered
    Sign In to Vote
    0

    Hello,

    Please take a look at following article

    Backup Fails with error message "WMI Writer Missing" in VSSADMIN 

    http://social.technet.microsoft.com/wiki/contents/articles/7309.backup-fails-with-error-message-wmi-writer-missing-in-vssadmin.aspx 

    If the suggestions mentioned in above article doesn't help, you might want to post your query in Backup sub forum for further assistance.

    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/threads

    Press any key... What the ... Where's any key ?

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    About Me ?

     
  • Monday, June 18, 2012 5:48 AM
     
     Answered
    Sign In to Vote
    0

    I got check the share folder for permission, it got remove "SYSTEM" group from the list. Will this affected the backup? Actually what this "SYSTEM" group for?

    • What do you mean about share folder? Do you backup the content of a share folder that is on a remote server? Or you are storing the backed up data to that share folder?
    • Did you remove the SYSTEM group from the share permissions section or from the NTFS permission section?
    • The SYSTEM account is used by most Windows services (via LocalSystem). Removing it won't prevent the Windows kernel from accessing the drive, but it might break some services that do it.

    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {ee52aab9-70ae-44ab-8f3b-5caba68b6a15}
       State: [7] Failed
       Last error: Timed out

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {06e594c9-5925-4dc4-9811-b7ac6a168539}
       State: [7] Failed
       Last error: Timed out

    Try to restart the server and run the vssadmin list writers command and report back the result...

    Because Windows NT backup do not have shadow copy component to select for backup as i have run windows NT backup backup system state it complete successfully. This mean not related with windows?

    As your post, you are using Windows Server 2008 R2 and this OS uses Windows Server Backup tool that replaces NTBackup in Windows Server 2003. What do you mean about the above bolded statement?

    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.