Hello,
I would be careful about assuming that VSS is reporting errors on the E
drive. It could well be some other drive, so it would be a good idea to
check them all.
Generally, VSS has a number of bugs, and you may be triggering one,
which can explain why it works after a reboot and then fails
-users@lists.sourceforge.net
Subject: [Bacula-users] Shadow Copy issue - Fatal error: VssOject is NULL
(From: global16 [mailto:bacula-forum < at > backupcentral.com] )
On the client, these entries are logged in C:\Program
Files\Bacula\working\zhfs01.trace
fs01: vss_generic.cpp:366-0 VSSClientGen
e the error originated, and
the sort of message (first digit 8 or C = error), but there's no such way to
quickly decode it at a command prompt.
Luc> -Original Message-
Luc> From: global16 [mailto:bacula-fo...@backupcentral.com]
Luc> Sent: 21 April 2015 2:03
Luc> To: bacula-u
(From: global16 [mailto:bacula-forum < at > backupcentral.com] )
On the client, these entries are logged in C:\Program
Files\Bacula\working\zhfs01.trace
fs01: vss_generic.cpp:366-0 VSSClientGeneric::Initialize: CoInitialize returned
0x80070008
Is one of the server's disks full or nearing its cap
it 8 or C = error), but there's no such way to
quickly decode it at a command prompt.
-Original Message-
From: global16 [mailto:bacula-fo...@backupcentral.com]
Sent: 21 April 2015 2:03
To: bacula-users@lists.sourceforge.net
Subject: [Bacula-users] Shadow Copy issue - Fatal er
I have been running the same version of Bacula on a Windows 2k12 server for
over a year (5.2.10). A few weeks ago, we started getting all our jobs failing
over the weekend due to an apparent issue with VSS. Has anyone encountered the
following fatal error:
20-Apr 19:30 bacula-zha JobId 5546:
