 |
Hi there, same problem here OS: CentOS 7 bareos version : 17.2.4-6 We actually can backup a vm and restore it with the bareos-vmware-plugin. But once a vm has been restored with bareos, the next backup will fail, with this error: 06-déc. 17:12 bareos-sd JobId 179: Ready to append to end of Volume "VMS_StorageWeekend0005" size=37785999243 *m 06-déc. 17:12 bareos-fd JobId 179: Fatal error: python-fd: Traceback (most recent call last): File "/usr/lib64/bareos/plugins/BareosFdWrapper.py", line 42, in start_backup_file return bareos_fd_plugin_object.start_backup_file(context, savepkt) File "/usr/lib64/bareos/plugins/BareosFdPluginVMware.py", line 202, in start_backup_file if not self.vadp.get_vm_disk_cbt(context): File "/usr/lib64/bareos/plugins/BareosFdPluginVMware.py", line 1003, in get_vm_disk_cbt changeId=cbt_changeId) File "/usr/lib/python2.7/site-packages/pyVmomi/VmomiSupport.py", line 580, in <lambda> self.f(*(self.args + (obj,) + args), **kwargs) File "/usr/lib/python2.7/site-packages/pyVmomi/VmomiSupport.py", line 386, in _InvokeMethod return self._stub.InvokeMethod(self, info, args) File "/usr/lib/python2.7/site-packages/pyVmomi/SoapAdapter.py", line 1374, in InvokeMethod raise obj # pylint: disable-msg=E0702 vim.fault.FileFault: (vim.fault.FileFault) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = 'Error caused by file /vmfs/volumes/vsan:529e79064efc1e89-e36758101e043745/c142095c-a822-9d22-3a7e-0cc47a9389aa/test-restore3.vmdk', faultCause = <unset>, faultMessage = (vmodl.LocalizableMessage) [], file = '/vmfs/volumes/vsan:529e79064efc1e89-e36758101e043745/c142095c-a822-9d22-3a7e-0cc47a9389aa/test-restore3.vmdk' } 06-déc. 17:12 bareos-fd JobId 179: Fatal error: fd_plugins.c:2519 Command plugin: no fname in bareosCheckChanges packet. My vm has only one vmdk and this error occurs in this precise scenario. We tried many things as disable CBT before restoring vm, put the vm out vmware's inventory et put it back again, without success. Any idea about that? |
|
|
Could you please try if it gets fixed removing all eventually existing snapshots an then running vmware_cbt_tool.py ... --resetcbt I've seen this kind of error message and resetting CBT did help. |
|
|
Hi stephand! vmware_cbt_tool.py ... --resetcbt Doesn't help. I've tried --disablecbt then --enablecbt. Error is the same. Centos7, bareos-dir Version: 18.2.5 (30 January 2019) |
|
|
Is this still reproducible with Bareos 22.1.0 and recent OS? |
|
|
closing after no answer. no report with recent code. |
- Anonymous
