CONFIGURATION object backup fails with VSS Snapshot creation failed

Dear All,

Could you please advise on the below. For one of our servers the backup of CONFIGURATION object fails with

[81:1009] It was not possible to create volume snapshot for 'C:\ProgramData\OmniBack\tmp\config'. System error: 'VSS Snapshot creation failed'.

in the debugs I can see error 8004230D:

[ 99] 2024-02-26 10:07:05.504 ("/da/bda/win32.c $Rev$ $Date:: $:":1495)
[ 99] <<=== (1) } /* Win32CheckForVolumeGUID */
[ 99] RetVal: (int) 0
[ 99]
[ 81] Problem during adding to snapshotset. 8004230D
[ 81] Volume 1277617008 added. snap id is 000000BD4C26E450
[ 81] gathering status for 'Task Scheduler Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'VSS Metadata Store Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'Performance Counters Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'System Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'SqlServerWriter'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'ASR Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'Registry Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'COM+ REGDB Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'MSMQ Writer (MSMQ)'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'Shadow Copy Optimization Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'IIS Config Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'BITS Writer'. status is 0. enum = 1, operation code =0
[ 81] gathering status for 'WMI Writer'. status is 0. enum = 1, operation code =0
[ 81] Failed to create snapshot

which if I get it right means Object already exists.

There are no other backups running concurrently with this one. We have enough disk space. On VSS side we can not see any errors in the OS logs.

Any ideas what else to check?

Thank you!

Parents
  • Suggested Answer

    0  

    Can we see the session report or at least the start up to where the error is seen? I assume you are backing up the C: volume in parallel with the CONFIGURATION object? Maybe you could try to exclude the directory mentioned in the error message 'C:\ProgramData\OmniBack\tmp\config' from the C: volume backup. I'm just assuming that may resolve the issue. Possibly it may complain about other directories again. In that case you may want to check what other directories are included in both objects and exclude them from the C: object.


    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

Reply
  • Suggested Answer

    0  

    Can we see the session report or at least the start up to where the error is seen? I assume you are backing up the C: volume in parallel with the CONFIGURATION object? Maybe you could try to exclude the directory mentioned in the error message 'C:\ProgramData\OmniBack\tmp\config' from the C: volume backup. I'm just assuming that may resolve the issue. Possibly it may complain about other directories again. In that case you may want to check what other directories are included in both objects and exclude them from the C: object.


    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

Children
No Data