Data Protector A06.11 Volume Shadow Copy Copy functionality could not be initialized.

[Critical] From: VBDA@nts10.twcoffee.com "D:" Time: 5/7/2010 2:32:27 PM
Volume Shadow Copy functionality could not be initialized.

[Critical] From: VBDA@nts10.twcoffee.com "D:" Time: 5/7/2010 2:32:27 PM
Fallback to legacy filesystem backup was not allowed. Aborting the backup.

[Critical] From: VBDA@nts10.twcoffee.com "D:" Time: 5/7/2010 2:32:27 PM
[81:52] /D
Not a valid mount point => aborting.
Parents
  • Exchange filesystem backup(just c:\drive and CONFIGURATION) fails with the following:

    [Critical] From: VBDA@ "CONFIGURATION:" Time: 9/29/2010 12:22:22 AM
    Volume Shadow Copy functionality could not be initialized.

    [Major] From: BSM@" Time: 9/29/2010 12:29:22 AM
    [61:3003] Lost connection to VBDA named "CONFIGURATION:"
    on host .
    Ipc subsystem reports: "IPC Read Error
    System error: [10054] Connection reset by peer


    [Major] From: BSM@" Time: 9/29/2010 5:29:43 AM
    [61:1002] The VBDA named "CONFIGURATION:" on host reached its inactivity timeout of 18000 seconds.
    The agent on host will be shutdown.
Reply
  • Exchange filesystem backup(just c:\drive and CONFIGURATION) fails with the following:

    [Critical] From: VBDA@ "CONFIGURATION:" Time: 9/29/2010 12:22:22 AM
    Volume Shadow Copy functionality could not be initialized.

    [Major] From: BSM@" Time: 9/29/2010 12:29:22 AM
    [61:3003] Lost connection to VBDA named "CONFIGURATION:"
    on host .
    Ipc subsystem reports: "IPC Read Error
    System error: [10054] Connection reset by peer


    [Major] From: BSM@" Time: 9/29/2010 5:29:43 AM
    [61:1002] The VBDA named "CONFIGURATION:" on host reached its inactivity timeout of 18000 seconds.
    The agent on host will be shutdown.
Children
  • This is an old post but might still be usable. Here are some ways to troubleshoot;

    OPTION 1: Create separate object in Backup specification for the failing object affected by Volume Shadow Copy. If it is "CONFIGURATION", re-add the object manually in the backup specificaiton.

    OPTION 2: Disable “Shadow Copy” option in FS backup configuration under "Options" section

    OPTION 3: Restart “Volume Shadow Copy” service of the affected client and test to Enable/Disable, Stop/Start/Restart the service. Normally, setting it to "Manual" works.

    OPTION 4: Modify omnirc file (client side only) and activate the parameter OB2_ENABLE_VSS_WRITERS=0 and ensure it is set to 0. Usually, in omnirc it is commented out and it set to default value of 1 which is enabled.

    OPTION 5: Reboot affected client (if needed)