Forum Discussion

Prajil's avatar
Prajil
Level 2
11 years ago

Bakup Exec 2010 R2 x64

Dear Team,

This is my first entry in Symantec forum so rquesting you to please provide any solution for this error,

In our organisation we are using Symantec Backup Exec 2010 R2 with windows Server 2003 R2 x64. few days before this error start to appear in my job list and failed my backup too. The destination server or failure is happening in Windows 2008 R2 Server (Installed in VM ware). I already restart VSS service in services . But i can see that in service list one service is stoped named as 'Backup exec VSS provider'. When i am trying to start that service i am getting a error and its not starting also. In cmd line i typed  'vssadmin list providers' but unfortunately i can not find any service running on it
.

here is the error when i am trying to start 'Backup exec VSS provider'

The Backup Exec VSS Provider service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Backup- XXXX.com
- AOFO: Initialization failure on: "XXXX.com\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11217 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.

 

 

any help highly appreciated

10.x and Earlier
Agents
Backing Up
Backup and Recovery
Backup Exec
Case Study
Error messages
Troubleshooting
Windows Server (2003-2008)
  • pkh's avatar
    pkh
    11 years ago
    Re-registering the VSS dll's on the media server is not going to help. It is the VSS on your Server 2008 server that matters, but do not re-register the dll's on this server as it will cause problems. Have you upgraded your BE as I have suggested earlier? If not, do so

7 Replies

Sort By
  • pkh's avatar
    pkh
    Moderator
    11 years ago
    Re-registering the VSS dll's on the media server is not going to help. It is the VSS on your Server 2008 server that matters, but do not re-register the dll's on this server as it will cause problems. Have you upgraded your BE as I have suggested earlier? If not, do so
  • pkh's avatar
    pkh
    Moderator
    11 years ago
    I would suggest that you upgrade to BE 2010 R3 which is the latest version and it solves quite a bit of VSS writer problems. Your existing licence keys will work.  You can download BE 2010 R3 from either the fileconnect site or
     
    http://trialware.norton.com/files/fc/Backup_Exec_2010_13.0.5204_MultiPlatforms_Multilingual_DVD.iso
     
    After your upgrade, do not forget to run LiveUpdate a couple of time to update it to SP3 and the latest hotfixes.
     
    After you have upgraded to R3 SP3, push out the remote agent again.
  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    11 years ago

    I am not sure you are meant to start that provider in that way.

     

    What happens if (inside the affacted VM) you run pre-freeze-script.bat form the windows folder and then refresh your services list, do you get a second BE VSS service listed that is then started. Note if this works makes sure you run post-thaw-script.bat afterwards to return the VSS services to the standby position.

    These two batch files are usually called by the VMWare Tools at the start of the snapshot request and during the removal and activate the BE VSS provider during backup operations.

  • CraigV's avatar
    CraigV
    Moderator
    11 years ago
    Server 2003 has a VSS Rollup Patch that can be installed if you continue to receive these errors after upgrading to BE 2010 R3...might be worth your while to download and install it. Thanks!
  • Prajil's avatar
    Prajil
    Level 2
    11 years ago

    Dear, PKH

    Is there any other way to fix this issue (without upgrade). Still now i am facing the same error.

  • Prajil's avatar
    Prajil
    Level 2
    11 years ago

    Hi all,

    I Re-install the Symantec backup agent on client server, restart the services, try without AOFO and with AOFO (from media server), Re-register the dll (below mentioned)

    cd /d %windir%\system32
     
    Net stop vss
     
    Net stop swprv
     
    regsvr32 ole32.dll
     
    regsvr32 oleaut32.dll
     
    regsvr32 vss_ps.dll
     
    vssvc /register
     
    regsvr32 /i swprv.dll
     
    regsvr32 /i eventcls.dll
     
    regsvr32 es.dll
     
    regsvr32 stdprov.dll
     
    regsvr32 vssui.dll
     
    regsvr32 msxml.dll
     
    regsvr32 msxml3.dll
     
    regsvr32 msxml4.dll
     
     
    But unfortunately error is still there.
     
  • Prajil's avatar
    Prajil
    Level 2
    11 years ago

    When i am starting Backu Exec VSS Provider in Service getting one error

    "Windows could not start the Backup Exec VSS Provider service on Local Computer.

    error 1053: The servvice did not respond to the Start or control request in a timely fasion"

     

    here is the list of my VSS provider list

    c:\Program Files\Symantec\Backup Exec\RAWS>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: {b0d03ddd-aefb-4114-a8c3-0836e9ddc47f}
       State: [7] Failed
       Last error: Timed out
     
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {68c68875-fa22-4a39-bd6d-d37a9eea9d26}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {9a49ad25-b3a5-4bb3-98d6-06b41f884209}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {1f751ae1-a97a-4883-8076-d72a9a38b9f8}
       State: [7] Failed
       Last error: Timed out
     
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {2aae6498-0be6-4bfe-b525-680f8d686b24}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {8bdaffce-1f05-441e-9a00-381639a5b2a6}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {cbccc07a-7358-41c4-9f50-9f88cb1ce64b}
       State: [7] Failed
       Last error: Timed out
     
    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {90832016-c4fe-4ca7-9103-df688be05f45}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {a899bbc3-577e-4102-8a0c-4efb3f1c9a44}
       State: [7] Failed
       Last error: Timed out
     
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {f5b325bc-1c21-483e-831a-43be23c97607}
       State: [7] Failed
       Last error: Timed out
     
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {458a1cdc-9871-4473-b18f-b55fce3dcca6}
       State: [1] Stable
       Last error: No error
     
    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {2aaab894-14f9-4d27-b376-370883c416ec}
       State: [7] Failed
       Last error: Timed out
     
     
    please give me a solution for this. Still now also i am getting the same error when i am running the same backup