View Issue Details

IDProjectCategoryView StatusLast Update
0001086bareos-core[All Projects] vmware pluginpublic2019-06-05 16:37
ReporterbarstefAssigned Tostephand 
PriorityhighSeveritycrashReproducibilitysometimes
Status feedbackResolutionopen 
PlatformLinuxOSUbuntuOS Version18.04
Product Version18.2.5 
Fixed in Version 
Summary0001086: vmdk files of VMware VMs to be backed up are not unmounted from Bareos VM
DescriptionMy Bareos server runs on a VMware VM. I'm using the VMware plugin to execute backups of Virtual Machines. The Bareos VMs apparently mounts the vDisks of the VM to be backed up and unmounts them after backup has been completed.

Unfortunately, it happens pretty often, that the VMDK is not being unmounted, which seems to cause problem in subsequent backup attempts on the same VM.

Please find attached a snapshot showing the hard disk config on the Bareos VM (called bareos46-1) in regular state (4 hard disks) and if the releasing of the target VMs' disks failed. In the shown example the disks of two VMs called msitedocker46-4 and msitedocker46-2 are still attached to the Bareos VM.

In addition, snapshots of the target VMs are not being deleted after the failed backups.
Steps To ReproduceRun a couple of VMware backups. After a while, VMDK files of such VMs are not being removed anymore from the Bareos VM's config.
Also, snapshots of the VM are not being deleted anymore.
Additional Information[root@bareos46-1:/etc/bareos/bareos-dir.d]# dpkg -l | grep bareos
ii bareos 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - metapackage
ii bareos-bconsole 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - text console
ii bareos-client 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - client metapackage
ii bareos-common 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - common files
ii bareos-database-common 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - common catalog files
ii bareos-database-mysql 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - MySQL backend
ii bareos-database-tools 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - database tools
ii bareos-director 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - director daemon
ii bareos-filedaemon 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - file daemon
ii bareos-filedaemon-python-plugin 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - file daemon Python plugin
ii bareos-storage 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - storage daemon
ii bareos-tools 18.2.5-144.1 amd64 Backup Archiving Recovery Open Sourced - common tools
ii bareos-vadp-dumper 18.2.5-124.1 amd64 vStorage APIs for Data Protection Dumper program
ii bareos-vmware-plugin 18.2.5-124.1 amd64 Bareos VMware plugin
ii bareos-vmware-vix-disklib 6.5.2-6195444 amd64 VMware vix disklib distributable libraries
ii bareos-webui 18.2.5-131.1 all Backup Archiving Recovery Open Sourced - webui




VMware vCenter 6.7
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

barstef

barstef

2019-05-21 09:45

reporter  

Bareos VM OK.png (313,148 bytes)
Bareos VM other VMDKs mounted.png (315,378 bytes)
stephand

stephand

2019-06-05 16:37

developer   ~0003390

Thanks for reporting this issue.
Did the backup fail before getting the state with the snapshot disks still attached to the backup VM?
If so, please report the job log here, to get it you can use
echo "list joblog jobid=nnnnn" | bconsole

The root cause of this problem is a VMware problem, but may be it's possible to modify the bareos code
so that a cleanup of this state if enforced if such a problem occurs.

When it is a VM that runs the backup, VDDK will use the so-called hotadd transport. It's possible to
override the transport mode, you could add "transport=nbdssl" to the plugin options, the nbdssl transport
does not attach disks to the backing up VM, and it must not necesarily be slower on current VMware versions,
so you could try it as a workaround to prevent from the issue.
See https://docs.bareos.org/TasksAndConcepts/Plugins.html#vmware-plugin

Issue History

Date Modified Username Field Change
2019-05-21 09:45 barstef New Issue
2019-05-21 09:45 barstef File Added: Bareos VM OK.png
2019-05-21 09:45 barstef File Added: Bareos VM other VMDKs mounted.png
2019-05-21 09:45 barstef File Added: Snapshot not being removed.png
2019-06-05 16:37 stephand Assigned To => stephand
2019-06-05 16:37 stephand Status new => feedback
2019-06-05 16:37 stephand Note Added: 0003390