Howdy, The director is Debian Stretch running v7.4.4. The client is Windows 10 Professional also with v7.4.4. I am guessing the PC was doing some update or other and VSS started for bacula but then was claimed by something else. Some data was backed up but it would be useless for a restore and make a nonsense of incrementals.
Example error: 01-Sep 12:36 xx-fd JobId 60403: Could not stat "C:/YY/ZZ.pdf": ERR=A device which does not exist was specified. Summary: Build OS: x86_64-pc-linux-gnu debian 9.0 JobId: 60403 Job: Backup-xx-pc.2019-09-01_12.30.00_13 Backup Level: Full Client: "xx-pc-fd" 7.4.4 (28Sep16) Microsoft Professional (build 9200), 64-bit,Cross-compile,Win64 FileSet: "xx-pc" 2019-08-29 16:51:42 Pool: "xx-pc" (From Job resource) Catalog: "MyCatalog" (From Client resource) Storage: "xx-pc" (From Job resource) Scheduled time: 01-Sep-2019 12:30:00 Start time: 01-Sep-2019 12:30:05 End time: 01-Sep-2019 12:37:02 Elapsed time: 6 mins 57 secs Priority: 10 FD Files Written: 21,315 SD Files Written: 21,315 FD Bytes Written: 1,162,695,590 (1.162 GB) SD Bytes Written: 1,167,011,405 (1.167 GB) Rate: 2788.2 KB/s Software Compression: 59.7% 2.5:1 Snapshot/VSS: yes Encryption: no Accurate: no Volume name(s): xx-pc-1084 Volume Session Id: 123 Volume Session Time: 1567102076 Last Volume Bytes: 3,187,356,080 (3.187 GB) Non-fatal FD errors: 44 SD Errors: 0 FD termination status: OK SD termination status: OK I re-ran the full backup later in the evening and there are no errors with 100000+ file and 70Gb backed up. Is there some magic configuration option to make the director backup interpret VSS failures as an error? This would be useful as the director can re-run full/diff backup on error. Huge thanks, Bernie
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users