New to Bare OS. Have the following setup, RHEL 7 server running bareos 14.2.2 I set up a gluster file system as a storage device for backups.
I consulted the BARE OS documentation as well as the following thread from this user group: https://www.mail-archive.com/[email protected]/msg00845.html It was helpful, but I have the following problem. If I manually run a backup job from bconsole pointed to the Gluster file system, the job just runs (until I cancel it) and no data is ever written, and any other subsequent jobs (pointed to other storage devices) also just queue and never kick off. The logs don't show any errors or give any indications as to whats wrong. I stopped the bareos-sd service/daemon, and ran in manually from the command line to watch the debug output in real time, and my test gluster backup job ran, along with any other job I kicked off. The only difference I noticed was I happened to run it in the foreground as root, and it normally runs as bareos. I assumed it was a simple permissions issue, but I switched user to bareos and mounted the gluster volume on bareos server and backup client machines via fuse gluster client, and verified as bareos I could write to the gluster file system. Again, no errors in the log file even with debug set to 200. Here are the relevant bareos configs, I setup the gluster storage with intention of backing up mysql databases, thus the Name MySQL. Device { Name = MySQL Archive Device = gluster://infarchive01/archives/mysqlbackup/bareos Device Type = gfapi Media Type = GlusterFile LabelMedia = yes # lets Bacula label unlabeled media Random Access = yes AutomaticMount = yes # when device opened, read it RemovableMedia = no AlwaysOpen = no } Storage { Name = MySQL Address = itbackup01.fdqn #N.B. Use a fully qualified name here SDPort = 9103 Password = "****" Device = MySQL Media Type = GlusterFile } Any help troubleshooting this would be appreciated. Relevenat bareos log showing bareos identified the volume for test-client01, and its trying to open the gluster device and then thats the last entry, just stops. Apr 23 10:55:21 pkc-itbackup01 bareos-dir: pkc-backup01-dir: catreq.c:97-5727 Vol Info for test-client01.2015-04-23_10.55.18_04: 1000 OK VolName=MySQL-INC-0158 VolJobs=3 VolFiles=0 VolBlocks=23 VolBytes=1409358 VolMounts=3 VolErrors=0 VolWrites=24 MaxVolBytes=100000000000 VolCapacityBytes=0 VolStatus=Append Slot=0 MaxVolJobs=0 MaxVolFiles=0 InChanger=0 VolReadTime=0 VolWriteTime=4545 EndFile=0 EndBlock=1409357 LabelType=0 MediaId=158 EncryptionKey= MinBlocksize=0 MaxBlocksize=0 Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: askdir.c:175-0 <dird 1000 OK VolName=MySQL-INC-0158 VolJobs=3 VolFiles=0 VolBlocks=23 VolBytes=1409358 VolMounts=3 VolErrors=0 VolWrites=24 MaxVolBytes=100000000000 VolCapacityBytes=0 VolStatus=Append Slot=0 MaxVolJobs=0 MaxVolFiles=0 InChanger=0 VolReadTime=0 VolWriteTime=4545 EndFile=0 EndBlock=1409357 LabelType=0 MediaId=158 EncryptionKey= MinBlocksize=0 MaxBlocksize=0 Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: askdir.c:211-0 do_get_volume_info return true slot=0 Volume=MySQL-INC-0158, VolminBlocksize=0 VolMaxBlocksize=0 Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: askdir.c:213-0 setting dcr->VolMinBlocksize(0) to vol.VolMinBlocksize(0) Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: askdir.c:215-0 setting dcr->VolMaxBlocksize(0) to vol.VolMaxBlocksize(0) Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: mount.c:122-0 After find_next_append. Vol=MySQL-INC-0158 Slot=0 Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: autochanger.c:99-0 Device "MySQL" (gluster://pkc-infarchive01/archives/mysqlbackup/bareos) is not an autochanger Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: mount.c:144-0 autoload_dev returns 0 Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: mount.c:175-0 want vol=MySQL-INC-0158 devvol= dev="MySQL" (gluster://pkc-infarchive01/archives/mysqlbackup/bareos) Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: dev.c:536-0 open dev: type=5 dev_name="MySQL" (gluster://pkc-infarchive01/archives/mysqlbackup/bareos) vol=MySQL-INC-0158 mode=OPEN_READ_WRITE Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: dev.c:540-0 call open_device mode=OPEN_READ_WRITE Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: dev.c:941-0 Enter mount Apr 23 10:55:21 pkc-itbackup01 bareos-sd: pkc-backup01-sd: dev.c:610-0 open disk: mode=OPEN_READ_WRITE open(gluster://pkc-infarchive01/archives/mysqlbackup/bareos/MySQL-INC-0158, 0x2, 0640) -- 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.
