Hello again,
i have tried it as you mentioned it. I have updated my Bareos packages
on my Debian 9 machine now with the official 17.2.4 packages from the
Bareos website and the experimental VMware-plugin packages also from the
site.
I don´t get the same error as before now, but something seems still not
to be working.
Here comes the log:
https://pastebin.com/5ee4i7h1
I can see how the snapshots are created and get deleted in the
VSphere-Manager before he wants to start the backup. This happens
without any error in Vsphere.
So i can not explain why he says: Failed to Prepare For Access: One of
the parameters was invalid [3].
What am i doing wrong here?
Greetings
Am 06.02.2018 um 13:18 schrieb Jörg Steffens:
On 05.02.2018 at 13:34 wrote tklassen:
Hello Jörg,
well i can revert back to Debian 9 from 10, but not to 8 sadly. I
thought it would be better to be more recent (as it is mostly with
Debian related problems ;)).
Do you see any other chance to get this up and running again?
You can try to remove following file:
/usr/lib/vmware-vix-disklib/lib64/libstdc++.so.6
It should work then.
The bareos-vmware-vix...version is at 6.5.2 as you mentioned.
Greetings
Am 05.02.2018 um 13:20 schrieb Jörg Steffens:
The vmware plugin is available for Debian 8, but not for Debian 9.
If you are on Debian 8, make sure the correct version of
bareos-vmware-vix-disklib is installed. If should be
bareos-vmware-vix-disklib_6.5.2
On 05.02.2018 at 12:34 wrote tklassen:
Hello again,
i have made some updates on my new Bareos test machine to see a bit
clearer here. I have updated Bareos now with the packages provided
directly from the Bareos team. So now im running here with Bareos
17.2.4, everything on the same version now.
The error message im getting now is slightly different then before:
https://pastebin.com/LdUGpgQM
Hopefully someone can help me out with that.
Greetings
Am 05.02.2018 um 10:53 schrieb tklassen:
Hello list,
im quite new with backing up VMWARE with Bareos and i ran into some
problems after our service company did the last updates on our ESX
hosts last week. We are still on version 6.0, but it´s the most recent
one of this series and i guess that causes some trouble. Before those
updates everything went fine, no problems at all-
Im running Bareos here on a Debian 9 server, for testing pruposes i
have made a clone of it and pushed it to Debian testing (same
results). I have downloaded the VMWARE plugin from here
http://download.bareos.org/bareos/release/16.2/Debian_8.0/amd64/ and
with the "new" Debian testing machine i tried the packages from here
http://download.bareos.org/bareos/experimental/nightly/Debian_9.0/
If i wanna backup any VM now i get an error like that:
https://pastebin.com/wpch3Yh0
That´s the content of the plugins directory. Im not sure why there is
a vmware-plugin folder, maybe there are some things messed up?
/usr/lib/bareos/plugins# tree
.
├── autoxflate-sd.so
├── bareos_fd_consts.py
├── bareos_fd_consts.pyc
├── bareos-fd-local-fileset.py
├── bareos-fd-mock-test.py
├── BareosFdPluginBaseclass.py
├── BareosFdPluginBaseclass.pyc
├── BareosFdPluginLocalFileset.py
├── BareosFdPluginVMware.py
├── BareosFdPluginVMware.pyc
├── bareos-fd.py.template
├── bareos-fd-vmware.py
├── bareos-fd-vmware.pyc
├── BareosFdWrapper.py
├── BareosFdWrapper.pyc
├── bpipe-fd.so
├── python-fd.so
└── vmware_plugin
├── BareosFdPluginVMware.py
├── BareosFdPluginVMware.pyc
├── bareos-fd-vmware.py
└── bareos-fd-vmware.pyc
Here we´ve got a sample configuration file:
FileSet {
Name = "MYVM-VM"
Include {
Options {
Signature = MD5
Compression = GZIP6
}
Plugin =
"python:module_path=/usr/lib/bareos/plugins/vmware_plugin/:module_name=bareos-fd-vmware:dc=Lhe:folder=/:vmname=MYVM:vcserver=vcenter.lhe.de:[email protected]:vcpass="PASS"
}
}
I hope that someone could give me a tip on how to get this up and
running again.
Thanks for your support!
Greetings
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
