I've been struggling a bit to get Bacula to work but almost have it, I think.

I'm running Debian Squeeze on the server and have it successfully backing up /home. Unfortunately I can't get it to back up a Windows 7/Pro-64 client. The only error in the log is the one quoted in the subject line.

Any ideas?

First of all: make sure that on the Windows machine the Volume Shadow Copy Service (VSS) is not disabled.
Go to Administration Tools > Services and check if the service is disabled and, in case it is, enable it.
If this will not solve the issue it's maybe a permission problem and you have to modify some registry keys on the Windows machine to grant access to the user used by Bacula.
Open regedit and navigate to the key HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/VSS and add the key VssAccessControl if it doesn't exist.
Then add a value that is the name of the user and set it to 1.
Its name have to be in the form domain\username.
If you keep on having this issue check the registry log on Windows machine and follow this ugly guide from Microsoft: http://technet.microsoft.com/en-us/l...35(WS.10).aspx

I upgraded to the newest Windows version of Bacula and that seems to have cured it.

I have the same problem.

Windows 2008 64bit
Bacula 5.2.10 x64
VSS Enabled and ready

JobId 7245: Fatal error: VSS was not initialized properly. ERR=�������� ������� ���������.
JobId 7245: Error: VSS API failure calling "BackupComplete". ERR=Object is not initialized; called during restore or not called in correct sequence.

I'm trying to solve the problem on their own for two weeks ...
How to get out of the situation?

I have the same problem, any solution? :?

The solution was not found. Error still exists.

Hi Guys,
I´m currently working with Bacula and got the same issue today.
Maybe there are any helpful ideas?

Regards,
David

David:

Welcome to LQ.
First order of business called "Necroposting". You don't want to reply to a thread that's older than 6 months.
Please note that this thread has not been replied to in over 6 months. Please ensure your reply is still relevant and timely.

Having said that, you should open your own thread, perhaps under
Linux Software or
Linux Server
since it could apply to either one.

If you choose to do that, then tell us the bacula version you are using and on what OS.Build.Platform
(Ubuntu xx.xx LTS/64 bit usually works)

and the Windows version you are having issue with.

is still good advice.

Good Luck!

I was suffering the same error. My issue was I had the wrong FileSet selected. I had configured the FileSet correctly, but selected the default "Full Set in the backup job.

Hello.
I was able to resolve this by editing the "Bacula File Backup Service" in services.msc "Proprierties" - "Login" - "This account" I put the local administrator's credentials and password. After that, just restart the service and have the job run on the server of the bacula.