Fatal error: CreateSGenerate VSS snapshots failed

Fatal error: CreateSGenerate VSS snapshots failed

When getting VSS Volume Shadow Copy Service error , it's usually due to NTFS drive not having enough space , VSS core services alone requires at least 500 mb for each volume to be shadow copied , Try to check the event viewer and look for VSS logs , Once you made sure there's enough space on disk and you're still getting the error , You can try to use Regsrv32 util tool to register and un-register vss OLE Controls and Dlls in windows registry . 

Try to create the following .bat and execute :

cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
net start swprv
net start vss

backups usually starts to run afterwards , If the issue still persist (possibly in windows 2k8) it might be due to bareos picking wrong mountpoint while taking snapshots  try checking the configs .

    • Related Articles

    • Windows VSS Snapshot Failures

      Phase One : If VSS snapshots are failing via ClusterLogics please check the following: There is at least 5% of disk space available on system drive the VSS plugin is installed To check this, look for Bacula VSS Plugin under Control Panel > Add/Remove ...

    • Fatal error: Network error with FD during Backup

      Related Errors: ERR=Connection reset by peer Fatal error: No Job status returned from FD. Problem: It is likely the server was restarted and/or the ClusterLogics service interrupted Solution: Check firewall, restart service (Linux: service baroes-fd ...

    • Fatal error: catreq.c:383 Invalid Catalog request

      Fatal error: catreq.c:383 Invalid Catalog request This error indicates an outdates director or SD in your environment. The best practice is to keep all FDs and SDs updated with the latest client versions. The FD and SD clients can be updated directly ...

    • Fatal error: catreq.c:383 Invalid Catalog request

      Fatal error: catreq.c:383 Invalid Catalog request This error indicates an outdates director or SD in your environment. The best practice is to keep all FDs and SDs updated with the latest client versions. The FD and SD clients can be updated directly ...

    • Backup Job Failure - ERR=ERROR: index row size exceeds maximum 2712 for index "path_name_idx

      Hello, if you receive a backup error similar to the below Fatal error: sql_create.c:831 Fill Path table Query failed: INSERT INTO Path (Path) SELECT a.Path FROM (SELECT DISTINCT Path FROM batch) AS a WHERE NOT EXISTS (SELECT Path FROM Path WHERE Path ...