[Bacula-users] Shadow Copy issue - Fatal error: VssOject is NULL
2015-04-20 21:07:32
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: Start Backup JobId 5546,
Job=Software_Share_Backup_-_Encrypted.2015-04-20_19.30.00_41
20-Apr 19:30 bacula-zha JobId 5546: Using Device "FileStorage-software" to
write.
20-Apr 19:30 bacula-zha JobId 5546: Sending Accurate information.
20-Apr 19:30 bacula-sd JobId 5546: Volume "zha-software-encrypted-vol0360"
previously written, moving to end of data.
20-Apr 19:30 bacula-sd JobId 5546: Ready to append to end of Volume
"zha-software-encrypted-vol0360" size=1775302040
20-Apr 19:30 fs01 JobId 5546: Fatal error: VSS API failure calling
"CoInitialize". ERR=Unexpected error. The error code is logged in the error log
file.
20-Apr 19:30 fs01 JobId 5546: Fatal error: VSS was not initialized properly.
ERR=Cannot create a file when that file already exists.
20-Apr 19:30 fs01 JobId 5546: Fatal error: VssOject is NULL.
20-Apr 19:30 bacula-sd JobId 5546: Elapsed time=00:00:06, Transfer rate=0
Bytes/second
20-Apr 19:30 bacula-zha JobId 5546: Error: Bacula bacula-zha 5.2.13 (19Jan13):
The only way to "fix" this is to reboot the client. Items I have tried:
* Restarted the Bacula service on the client - backups still failed
* Tested connection to client using the 'estimate' command, success. Issue
isolated to Windows server.
* List current VSS instances via cmd prompt (vssadmin list writers) - All
states reported as Stable / No writers reporting errors
* Manually create a shadow copy on the client (vssadmin create shadow /for=e: )
and then manually remove all shadow copies (vssadmin delete shadows /all) -
backup still fails
* Ran System File Checker (sfc /scannow) - No issues found, backups still fail
After rebooting the client, backups using VSS work fine for a few days and then
start failing with the same FATAL error. It is not always the same job that
fails first.
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
If anyone has any ideas on how to further troubleshoot this issue, or have
encountered this before, I'd greatly appreciate it.[/img]
+----------------------------------------------------------------------
|This was sent by bumbacod AT hotmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Bacula-users] Shadow Copy issue - Fatal error: VssOject is NULL,
global16 <=
|
|
|