View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001284 | bareos-core | vmware plugin | public | 2020-12-09 16:35 | 2023-08-02 10:29 |
Reporter | SOKAKU | Assigned To | bruno-at-bareos | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | Linux | OS | Ubuntu | OS Version | 18.04 |
Product Version | 19.2.8 | ||||
Summary | 0001284: The message goes well but no Backup will be performed | ||||
Description | Good afternoon, First of all a greeting to all the members of this Bareos forum that I consider a very complete tool. I am new in this world of Bareos, I am using it more than everything for the Backup of files, but now I want to do the Backups of the VMware VMs, I have read the documentation and carry out the steps indicated; but when I run the backup the message goes all right but it doesn't make any backup. And CBT is enabled with vmware_cbt_tool.py I don't know if I am missing something in the configuration or did something wrong. This is the message: bareos-director-dir JobId 131: Start Backup JobId 131, Job=vm-prueba.2020-12-09_12.23.17_06 bareos-director-dir JobId 131: Connected Storage daemon at 10.1.14.151:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 bareos-director-dir JobId 131: Using Device "FileStorage" to write. bareos-director-dir JobId 131: Probing client protocol... (result will be saved until config reload) bareos-director-dir JobId 131: Connected Client: bareos-director-fd at localhost:9102, encryption: TLS_CHACHA20_POLY1305_SHA256 bareos-director-dir JobId 131: Handshake: Immediate TLS bareos-director-dir JobId 131: Encryption: TLS_CHACHA20_POLY1305_SHA256 bareos-director-fd JobId 131: Connected Storage daemon at 10.1.14.151:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 bareos-director-sd JobId 131: Volume "Incremental-0001" previously written, moving to end of data. bareos-director-fd JobId 131: Extended attribute support is enabled bareos-director-fd JobId 131: ACL support is enabled bareos-director-sd JobId 131: Ready to append to end of Volume "Incremental-0001" size=116995 bareos-director-sd JobId 131: Releasing device "FileStorage" (/mnt/backups). bareos-director-sd JobId 131: Elapsed time=00:00:01, Transfer rate=0 Bytes/second bareos-director-dir JobId 131: Bareos bareos-director-dir 19.2.7 (16Apr20): Build OS: Linux-3.10.0-1062.18.1.el7.x86_64 ubuntu Ubuntu 18.04.4 LTS JobId: 131 Job: vm-prueba.2020-12-09_12.23.17_06 Backup Level: Full Client: "bareos-director-fd" 19.2.7 (16Apr20) Linux-3.10.0-1062.18.1.el7.x86_64,ubuntu,Ubuntu 18.04.4 LTS FileSet: "File-vm-prueba" 2020-12-09 11:04:19 Pool: "Incremental" (From command line) Catalog: "MyCatalog" (From Client resource) Storage: "File" (From command line) Scheduled time: 09-Dec-2020 12:24:13 Start time: 09-Dec-2020 12:24:15 End time: 09-Dec-2020 12:24:15 Elapsed time: 0 secs Priority: 10 FD Files Written: 0 SD Files Written: 0 FD Bytes Written: 0 (0 B) SD Bytes Written: 0 (0 B) Rate: 0.0 KB/s Software Compression: None VSS: no Encryption: no Accurate: no Volume name(s): Volume Session Id: 1 Volume Session Time: 1607527379 Last Volume Bytes: 0 (0 B) Non-fatal FD errors: 0 SD Errors: 0 FD termination status: OK SD termination status: OK Bareos binary info: bareos.org build: Get official binaries and vendor support on bareos.com Termination: Backup OK | ||||
Steps To Reproduce | run the backup | ||||
Additional Information | This is my configuration, I followed the steps in the documentation: bareos-fd.d/client/myself.conf Client { Name = bareos-director-fd Maximum Concurrent Jobs = 20 Plugin Directory = /usr/lib/bareos/plugins Plugin Names = python } bareos-dir.d/job/vm-prueba-fd.conf Job { Name = "vm-prueba" JobDefs = "DefaultJob" Fileset = "File-vm-prueba" Level = Full Schedule = "WeeklyCycleAfterBackup" } bareos-dir.d/jobdefs/DefaultJob.conf JobDefs { Name = "DefaultJob" Type = Backup Level = Incremental Client = bareos-director-fd FileSet = "SelfTest" Schedule = "WeeklyCycle" Storage = File Messages = Standard Pool = Incremental Priority = 10 Write Bootstrap = "/var/lib/bareos/%c.bsr" Full Backup Pool = Full # write Full Backups into "Full" Pool (0000005) Differential Backup Pool = Differential # write Diff Backups into "Differential" Pool (0000008) Incremental Backup Pool = Incremental # write Incr Backups into "Incremental" Pool (0000011) } bareos-dir.d/fileset/File-vm-prueba.conf FileSet { Name = "File-vm-prueba" Include { Options { signature = MD5 Compression = LZ4 } Plugin = "python:\ module_path=/usr/lib/bareos/plugins:\ module_name=bareos-fd-vmware:\ dc=DATA:\ folder=/deployed:\ vmname=dev-heladeras:\ vcserver=prueba.ejem.local:\ vcuser=prueba@vsphere.local:\ vcpass=password" } } | ||||
Tags | No tags attached. | ||||
Is this really still the case with recent Bareos 22.1.0 version and python3 version of the plugin ? | |
Use version > 22.1.0 VMWare plugin got a lot of improvement with python3 | |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-12-09 16:35 | SOKAKU | New Issue | |
2023-07-19 10:45 | bruno-at-bareos | Assigned To | => bruno-at-bareos |
2023-07-19 10:45 | bruno-at-bareos | Status | new => feedback |
2023-07-19 10:45 | bruno-at-bareos | Note Added: 0005226 | |
2023-08-02 10:29 | bruno-at-bareos | Status | feedback => closed |
2023-08-02 10:29 | bruno-at-bareos | Resolution | open => no change required |
2023-08-02 10:29 | bruno-at-bareos | Note Added: 0005301 |