We have been running Bacula on Windows with VSS disabled, but would like to turn it on for disaster recovery purposes. In our tests on a fully patched version of Windows Server 2003, we are running into a problem where files that can be backed up without VSS are being reported as "corrupted or unreadable" when VSS is enabled. I posted a sample log to http://pastebin.com/NRYgmRQy
This does appear to be a Windows VSS problem rather than an issue with the Bacula client, as the system logs report an ntfs error when it occurs. A chkdsk did not help. Has anybody seen this issue before? Any suggestions on how to resolve it? Client OS: Microsoft Windows Server 2003, Standard Edition (32 bit) Bacula version: 5.0.3 -- Regards, Avery Ceo Systems Administrator Enterprise Hosting ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users