Re: [Bacula-users] Bacula 15.02 upgrade on Centos 7 -- Storage Daemon not starting
On 2024-04-02 14:43, Bill Arlofski via Bacula-users wrote: Hello, Glad we got this working. :) P.S. I think it is time to upgrade/migrate from CentOS 7 ;) Absolutely agree. Thank you for the help. Best regards, Bill ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 15.02 upgrade on Centos 7 -- Storage Daemon not starting
On 2024-04-02 10:17, Bill Arlofski via Bacula-users wrote: On 4/2/24 9:54 AM, sruckh--- via Bacula-users wrote: I have upgraded from 13.x to 15.02 on a CentOS 7 server by changing yum repository and running yum update. After RPMs were upgraded, I ran the scripts to upgrade the MySQL database. When I try to start bacula-sd using systemctl no errors are returned, but the storage daemon is not starting (as seen by running 'ps -ef | grep bacula' ). Running journalctl for bacula-sd does not show that bacula-sd is failing. The systemctl status for bacula-sd is returning the following: hostname removed to protect the innocent ● bacula-sd.service - Bacula Storage Daemon service Loaded: loaded (/usr/lib/systemd/system/bacula-sd.service; enabled; vendor preset: disabled) Active: inactive (dead) since Tue 2024-04-02 08:18:13 MST; 18min ago Process: 4066 ExecStart=/opt/bacula/bin/bacula-sd -dt -c /opt/bacula/etc/bacula-sd.conf (code=exited, status=0/SUCCESS) Main PID: 19946 (code=exited, status=1/FAILURE) Apr 02 08:18:13 xxx.xxx.xxx systemd[1]: Starting Bacula Storage Daemon service... Apr 02 08:18:13 xxx.xxx.xxx systemd[1]: Started Bacula Storage Daemon service. There is nothing in the system logs that would help narrow down the problem. There is also nothing logged in /opt/bacula/log/bacula.log that mentions problems with the storage daemon. If the storage daemon is instead started manually from the command line (as root user) using the following command the storage daemon starts and does not terminate: sudo /opt/bacula/bin/bacula-sd -d 200 -c /opt/bacula/etc/bacula-sd.conf Hello, More than likely, the above command is/was the initial cause of your problem. The Bacula SD typically runs as the user 'bacula'. Starting the SD as root (as shown above with the sudo command), will cause the SD to open its PID and state files (and any file volumes) as the root user. Later, when you try to start it with systemd - which will run it as the bacula user - it will not have access to these files and will just silently fail to start. Try testing the config file syntax first with this: # sudo -u bacula /opt/bacula/bin/bacula-sd -t This showed that there were permissions problems with the bacula-sd.conf file. My bacula-sd.conf file was owned by root:disk, the bacula-sd.conf.rpmnew file is owned by root:tape. The groups for id bacula are: (bacula) (tape). All of my previous volumes are owned by bacula:disk. Did group membership of the bacula user change in the 15.02 upgrade? I am now wondering if the correct thing to do is add bacula user to group disk, or to change group on all the files to tape?? I don't know what the group membership of the bacula user was before the upgrade. That might/should fail with some read and/or write permissions on one or more files. If it does not fail, then start the SD in foreground more like: # sudo -u bacula /opt/bacula/bin/bacula-sd -d100 -f Then, `chown bacula:bacula` any files it complains about, and try again until it starts up and remains running. Next, find any file volumes the SD may have written to when run from the command line previously and chown them too. Then, ctrl-c the running bacula-sd, and try to start with systemd, it should work now. Thank you for providing debugging commands. As this is the first time I have run into this issue through various upgrades, I am wondering what changed in this particular upgrade.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula 15.02 upgrade on Centos 7 -- Storage Daemon not starting
I have upgraded from 13.x to 15.02 on a CentOS 7 server by changing yum repository and running yum update. After RPMs were upgraded, I ran the scripts to upgrade the MySQL database. When I try to start bacula-sd using systemctl no errors are returned, but the storage daemon is not starting (as seen by running 'ps -ef | grep bacula' ). Running journalctl for bacula-sd does not show that bacula-sd is failing. The systemctl status for bacula-sd is returning the following: hostname removed to protect the innocent ● bacula-sd.service - Bacula Storage Daemon service Loaded: loaded (/usr/lib/systemd/system/bacula-sd.service; enabled; vendor preset: disabled) Active: inactive (dead) since Tue 2024-04-02 08:18:13 MST; 18min ago Process: 4066 ExecStart=/opt/bacula/bin/bacula-sd -dt -c /opt/bacula/etc/bacula-sd.conf (code=exited, status=0/SUCCESS) Main PID: 19946 (code=exited, status=1/FAILURE) Apr 02 08:18:13 xxx.xxx.xxx systemd[1]: Starting Bacula Storage Daemon service... Apr 02 08:18:13 xxx.xxx.xxx systemd[1]: Started Bacula Storage Daemon service. There is nothing in the system logs that would help narrow down the problem. There is also nothing logged in /opt/bacula/log/bacula.log that mentions problems with the storage daemon. If the storage daemon is instead started manually from the command line (as root user) using the following command the storage daemon starts and does not terminate: sudo /opt/bacula/bin/bacula-sd -d 200 -c /opt/bacula/etc/bacula-sd.conf After running the above command and then starting Bacula director I was able to successfully run a job without errors. When looking at the bacula-sd.service file it appears to be using a similar command (the one listed above in the status output) to start the storage daemon. I see in the docs that cloud storage appears to be changing but is currently in beta. It sounds like the S3 driver still works. I have not made any changes to the bacula-sd.conf file at this time. What other things can I look at to troubleshoot why the storage daemon does not stay running when started with the systemctl command? Thank You.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 9.2.0 release available
On 2023-12-05 10:18, Davide F. via Bacula-users wrote: Hello everyone, I'm pleased to inform you that Bacula-Web 9.2.0 is now available. You can find more details on the blog using the link below https://www.bacula-web.org/blog/bacula-web-9.2.0/ Release notes on GitHub project https://github.com/bacula-web/bacula-web/releases/tag/v9.2.0 Best regards Davide I have opened a bug report on the git page, as the upgrade process from 8.9.0 to 9.2.0 did not work for me. All the details have been included in the git bug tracker incident report. Thank You.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 8.9.0 release
On 2023-04-12 00:24, Davide F. wrote: Hello everyone, I'm pleased to inform you that Bacula-Web 8.9.0 has been released. Please note that this release address a security issue with Smarty PHP template engine. Upgrading to latest version is highly recommended ! https://github.com/bacula-web/bacula-web/releases/tag/v8.9.0 I hope you'll enjoy it as much as I do Best regards ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users Looks good so far. Every previous issue I have reported appears to have been resolved. Good work. Thank You.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 8.6.3 release
On 2022-11-15 00:22, Davide F. wrote: Hello everyone, I'm pleased to inform you that Bacula-Web 8.6.3 is now available. This new release mainly focus on improving support for PHP version >= 8.0, and to update documentation by adding Instructions for Lighttpd web server. (https://docs.bacula-web.org). You'll find more details on the blog using the link below https://www.bacula-web.org/blog/bacula-web-8.6.3/ Release notes on GitHub project https://github.com/bacula-web/bacula-web/releases/tag/v8.6.3 This is working in my environment with lighttpd. Also, I see that the "Test Page" now recognizes other accounts besides apache as being the web user account. I submitted request to add permissions of application/views/cache/ to the "Update" documentation, if write access for the web user is necessary. Thank you for your work!!___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 8.6.1 release
On 2022-11-02 10:29, Davide F. wrote: Hello, Did you manage to make it work ? Best, I set up a virtual host configuration using SSL. I set up document root to the bacula-web/public directory. This did not work. I get http 500 error. This page is not working. Can't currently handle request type error. I next modified the index.php (in the bacula-web/public directory ) to be the php info page: I refreshed browser and the phpinfo page was displayed. As the phpinfo page works, I am guessing that the lighttpd configuration file I made for bacula-web works. I am unable to get get bacula-web-8.6.2 working with lighttpd using SSL and a configuration that points to bacula-web/public at the Document root.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 8.6.1 release
On 2022-11-02 10:29, Davide F. wrote: Hello, Did you manage to make it work ? Best, On Thu, 27 Oct 2022 at 17:54 sruckh--- via Bacula-users wrote: On 2022-10-26 23:11, Davide F. wrote: Hello, Thanks for your feedback First of all, I have two questions * Just curious, why are you not using built-in authentication but HTTP Basic authentication instead ? * Which OS are you running Debian, Ubuntu, etc ? Regarding the issue you're facing (403 permission denied). As mentioned in latest documentation, please make sure Lighttpd configuration is using Bacula-Web public sub-folder as a "root folder" Assuming you've installed Bacula-Web in /var/www/html/bacula-web, configure it like below server.document-root = "/var/www/html/bacula-web/public/" This is where I see a difference in the older version (v 8.4.4) I was running and the current version (thanks for pointing that out). There is no "public" sub-directory with the 8.4.4 version. As mentioned, I do not have a virtual host configuration for bacula-web and would not set my document root as suggested above, because I have several web apps in my document-root directory. So, I access all my apps using https://top.level.domain/some-directory, including the working 8.4.4 version of bacula-web. I would use https://top.level.domain/bacula-web/ . I did not notice you have changed the directory structure until you pointed it out. I can try making a virtual host configuration to see if that makes a difference, but this change, which I am not even sure I entirely understand, since you are putting files outside of document root, is most likely the reason for my error. ___ Sorry, I have not had time to mess around with it. I will certainly post here if I get it to work by setting up a custom configuration. As far as authentication goes, I think I just assumed the current setting I am using was for no authentication, meaning any user with the URL could access the page. Which is desired. I assumed the other authentication meant there would have to be some type of username/password to access the page.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 8.6.1 release
On 2022-10-26 23:11, Davide F. wrote: Hello, Thanks for your feedback First of all, I have two questions * Just curious, why are you not using built-in authentication but HTTP Basic authentication instead ? * Which OS are you running Debian, Ubuntu, etc ? Regarding the issue you're facing (403 permission denied). As mentioned in latest documentation, please make sure Lighttpd configuration is using Bacula-Web public sub-folder as a "root folder" _ _ Assuming you've installed Bacula-Web in /var/www/html/bacula-web, configure it like below server.document-root = "/var/www/html/bacula-web/public/" This is where I see a difference in the older version (v 8.4.4) I was running and the current version (thanks for pointing that out). There is no "public" sub-directory with the 8.4.4 version. As mentioned, I do not have a virtual host configuration for bacula-web and would not set my document root as suggested above, because I have several web apps in my document-root directory. So, I access all my apps using https://top.level.domain/some-directory, including the working 8.4.4 version of bacula-web. I would use https://top.level.domain/bacula-web/ . I did not notice you have changed the directory structure until you pointed it out. I can try making a virtual host configuration to see if that makes a difference, but this change, which I am not even sure I entirely understand, since you are putting files outside of document root, is most likely the reason for my error.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 8.6.1 release
On 2022-10-21 21:32, Davide F. wrote: Hello, Let me try to help you here Can you share your lighttpd config ? Could you also try to run the check from a shell please ? https://docs.bacula-web.org/en/latest/02_install/test.html#using-bacula-web-console Please note that there's a regression for users who setup Bacula-Web for the first time using the bwc script but I'm already working on a fix. Best regards === Checking requirements === PHP version Ok PHP timezone Ok Protected assets folder is writable Ok Smarty cache folder write permission Ok PHP Posix support Ok PHP PDO support Ok PHP SQLite support Ok PDO drivers (available): driver: mysql driver: pgsql driver: sqlite PHP Gettext support Ok PHP Session support Ok The lighttpd config is pretty generic. No virtual host is configured for bacula-web. It is using the main configuration where the base folder is defined, and web apps are put in that directory. I also have the SSLEngine turned on. I still get the 403 forbidden error message. BTW -- the first time I ran bwc check I got Error. I changed the permissions of the application/views/cache/ (which I did not see on the upgrade page) directory to be owned by lighttpd: and of course, gave write write permissions. I am also using 8.6.2 now.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula-Web 8.6.1 release
On 2022-10-19 10:02, Davide F. wrote: I'm pleased to inform you that Bacula-Web 8.6.1 is now available. This new release contains bug fixes and two minor features. More details are available on the blog using the link below https://www.bacula-web.org/blog/bacula-web-8.6.1/ Best regards Davide Web site - https://www.bacula-web.org [1] Follow the project on GitHub - https://github.com/bacula-web/bacula-web ___ I tried an upgrade. I downloaded tar file. Extracted contents. Renamed extracted folder to match old folder name (bacula-web). Copied over old config file. Set permissions on the "protected" folder to web user (lighttpd). No files in that directory (same as with older version). I get a 403 forbidden error. Using lighttpd 1.4.54 with php 7.4.32. I have set config['enable_users_auth'] = false in config.php. I have not done a whole lot a debugging or trying to figure out what is going on, but that was my initial experience. Links: -- [1] https://www.bacula-web.org/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Community Cloud Backup on B2
On 2022-07-06 03:02, Chris Wilkinson wrote: Hello Radoslaw B2 does claim to be S3 compatible with a few exceptions. https://www.backblaze.com/b2/docs/s3_compatible_api.html I'm not sure if any of these are a Bacula show stopper so I guess the only way to find out is to try it. Bacula 11 was compiled from source without the S3 driver so I'll need to rebuild it. There seems to have been some issues with this for some people but I haven't been following this topic much. Best Chris I am currently using the 11.06 community RPM packages on CentOS 7 to backup to backblaze (using the S3 cloud driver). Below are the packages I have installed: bacula-libs-11.0.6-22062217.el7.x86_64 bacula-aligned-11.0.6-22062217.el7.x86_64 bacula-mysql-11.0.6-22062217.el7.x86_64 bacula-cloud-storage-11.0.6-22062217.el7.x86_64 -Scott___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: fileset "magic" - still weird
On 2022-06-16 04:56, Martin Simmons wrote:
On Wed, 15 Jun 2022 22:07:06 +, Bill Arlofski via Bacula-users
said:
On 6/15/22 15:23, sruckh--- via Bacula-users wrote:> Below is an
example Fileset I use which has includes and excludes.
>
> Fileset {
> Name = "Firewall Full"
> Include {
> File = "/"
> File = "/boot"
> File = "/home"
> File = "/var"
> Options {
> Compression = "Gzip"
> Signature = "Md5"
> Exclude = "Yes"
> WildDir = "/ISO"
> WildFile = "/.journal"
> WildFile = "/.fsck"
> }
> }
> }
Hello,
I don't think yout fileset is working the way you think/want.
This fileset will not compress, nor create md5 signature for any files
in /, /boot /home, or /var. I'd expect you to see "No
signature found for file " during restores. (or some similar
message)
Are you sure about that? The doc says "However, one additional point
is that
in the case that no match was found, Bacula will use the options found
in the
last Options resource." so I think that will make it work.
In words, your example fileset says to backup those included
directories and below, but exclude those two wild files, and one
wilddir, but only if they are found in the root directory.
But, I am not even sure th
ose wilddir and wildfiles will correctly work because you have not
included any wildcards in them.
The lack of any wildcards will not cause a problem.
I would re-write this fileset as follows:
8<
FileSet {
Name = FirewallFull
Include {
Options {
compression = gzip
signature = md5
}
File = "/"
File = "/boot"
File = "/home"
File = "/var"
}
Exclude {
File = ISO
File = .fsck
File = .journal
}
}
8<
This example will compress and create an md5 signature for everything
under /, /boot /home, or /var, and then will exclude
any files or directories called ISO, .fsck, and .journal wherever they
are found.
If you want to anchor them to the root directory only, then set them
to /ISO, /.fsck, and /.journal
This Exclude clause looks wrong to me, because the File items will
match
nothing. Don't you need
File = "*/.fsck"
to match .fsck anywhere?
__Martin
I apologize for unintentionally hijacking thread and not paying enough
attention to the original poster's issue. This came from a policy I
have had for over 10 years, so have not revisited it for quite some
time.
I appreciate the feedback and will now have to consider what was stated
here and do some further testing. I thought this worked as expected a
long time ago, but apparently it could use some refreshing and some
retesting.
Thank You.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: fileset "magic" - still weird
On 2022-06-15 13:47, Justin Case wrote:
I re-read the chapter about filesets and fileset options.
In order to better understand what is happening I simplified the
fileset as follows:
Fileset {
Name = “cadat"
EnableVss = no
EnableSnapshot = no
Include {
Options {
OneFS = no
#RegexDir = "/mnt/cdat-.*"
}
# Options {
#OneFS = no
# Exclude = yes
#RegexDir = ".*”
# }
File = "/mnt"
}
}
I was hoping it would then backup everything in /mnt (yes they are all
different filesystems, but OneFS is set to no).
Again, nothing was backed up.
I do not understand this result. I thought I had understood what is in
the manual about filesets, but obviously I did not.
On 15. Jun 2022, at 19:55, Justin Case wrote:
Hi all,
I am somewhat struggling with the fileset algorithm, noob birth pains
I guess.
I have a bunch of VMs that have mounted(!!) docker container appdata
in /mnt/cdat-.
So I wish to backup /mnt/cdat-* on each of these VMs, meaning I wish
that the content of each subdirectory in /mnt where the name starts
with "cdat-“ gets backed up.
So I looked into the main manual for fileset directive syntax. And I
found this example:
FileSet {
Name = "Full Set”
Include {
Options {
wilddir = "/home/a*”
wilddir = "/home/b*"
}
Options {
RegexDir = ".*”
exclude = yes
}
File = /home
}
}
So what I did is this (and it does not work, just returns 1 file, and
that is wrong):
Fileset {
Name = “cadat"
EnableVss = no
EnableSnapshot = no
Include {
Options {
OneFS = no
RegexDir = "/mnt/cdat-.*"
}
Options {
OneFS = no
Exclude = yes
RegexDir = ".*"
}
File = "/mnt"
}
}
I know it must seem kinda obvious where the problem is for those who
have been around with bacula for a while. For me it is kinda “magic”.
Where is my mistake?
Thanks for helping out!
J/C
Below is an example Fileset I use which has includes and excludes.
Fileset {
Name = "Firewall Full"
Include {
File = "/"
File = "/boot"
File = "/home"
File = "/var"
Options {
Compression = "Gzip"
Signature = "Md5"
Exclude = "Yes"
WildDir = "/ISO"
WildFile = "/.journal"
WildFile = "/.fsck"
}
}
}
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula 11.06 RPMs (Cloud Storage)
Are the additional RPMs (for cloud-storage) that are in the 11.05 directory going to be added to the 11.06 directory? Thank You. Scott ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] YUM repository errors
I see the certificate for bacula.org was recently updated (05/17). I am not getting this error from yum: [Errno 14] curl#60 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate." When I put the URL in a web browser and check the certificate it looks valid, but yet YUM complains for both bacula, and baculum, which both are configured for repos using bacula.org. Thank You. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2
On 2021-05-03 10:01, r0...@nxlplyx.com wrote: Hi Struckh, I have tried for weeks to get the S3 module to work on the Community edition of Bacula, to no avail. Are you working with the community edition, or the paid edition? Regards, Al I am using the freely downloadable version from the link I put in my post. I used yum to download from the repository. Name : bacula-mysql Version : 9.6.7 Release : 1.el7 Architecture: x86_64 Install Date: Mon 04 Jan 2021 09:18:01 AM MST Group : System Environment/Daemons Size : 12099705 License : AGPLv3 Signature : RSA/SHA512, Tue 22 Dec 2020 07:14:33 AM MST, Key ID c0be2a5fe9df3643 Source RPM : bacula-9.6.7-1.el7.src.rpm Build Date : Tue 22 Dec 2020 07:00:04 AM MST Build Host : rhel7-64.local.lan Relocations : /opt/bacula Packager : Bacula Systems SA Vendor : The Bacula Team URL : http://www.bacula.org/ Summary : Bacula - The Network Backup Solution Description :___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2
On 2021-05-03 14:25, Heitor Faria wrote: Hello r0002, Despite of the not-working testimonials in this thread, until now I see no related bug reports in the Bacula bug tracker: https://bugs.bacula.org/view_all_bug_page.php IMHO it would be of great help if you could make the bug reports with the maximum details, such as: - bacula.org package versions you are trying to install. - libs3 version and installation commands - operating system exact version - bacula-sd -d 200 loading debug output - steps to reproduce the error. I believe this is the fastest way of the bacula.org team to address this problem properly. Regards, Problem has been reported. Thank You.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2
On 2021-04-30 09:23, Heitor Faria wrote: Hello, If you read the email thread, I was not asking for technical help. I was simply asking if anyone has had success with the S3 plugin. With the lack of responses, I can only assume nobody has got it working. Of course. After less than 20 hours from the original post that was the only possible assumption. I guess everyone have to, voluntarily and promptly, provide the answers that you need. Which means the plugin does not work, so it should be removed from the repo. I personally know at least 10 administrators that use the CBacula 9/11 version Cloud driver in different sectors. It also works in one of my lab machines: I am running bacula 9.6.7 on CentOS 7 where the packages came from https://bacula.org/packages/x/rpms/9.6.7/el7/x86_64/ . In my case the S3 drivers seemed to stop working after 9.6.5 (if I remember correctly. It was a couple of versions ago when it stopped working). With the current packages, bacula-mysql-9.6.7-1.el7.x86_64, bacula-aligned-9.6.7-1.el7.x86_64, bacula-cloud-storage-9.6.7-1.el7.x86_64, and bacula-libs-9.6.7-1.el7.x86_64, the S3LIB files (discussed in this thread earlier) are provided by package bacula-cloud-storage. The libs3.so.4 file gets installed in /opt/bacula/lib64/. The problem being that if you do a ldd on /opt/bacula/plugins/bacula-sd-cloud-driver-9.6.7.so it shows it uses, libs3.so.4, but that it is missing. So I tried to create the file /etc/ld.so.conf.d/bacula.conf and added /opt/bacula/lib64 path to the file and ran ldconfig to rebuild the cache. By doing this, running ldd on bacula-sd-cloud-driver-9.6.7.so now shows libs3.so.4 coming from /opt/bacula/lib64. Unfortunately, even with this change, a configuration that used to work fine in older versions of bacula, no longer work in the current version installed. The S3 drivers seems to load, but I ultimately end up with this error: 3999 Error with the upload: ERR=RequestTorrentOfBucketError . On a hunch, I went ahead and built an RPM package from the link provided earlier in the thread for the libs3 library. I went ahead and installed this RPM after building it and the libs3.so.4 file is now in /usr/lib/ . I went ahead and removed the /etc/ld.so.conf.d/bacula.conf, and again rebuilt the cache with ldconfig. Now when running ldd on bacula-sd-cloud-driver-9.6.7.so the libs3.so.4 now shows to be coming from /usr/lib/ . Unfortunately, I get the same error as before. This time, I just went into bconsole, and tried to use the cloud command to upload the volume. After a few minutes the bconsole command times out with the exact error mentioned above that is received when trying to perform a backup. This exact configuration used to work going straight to S3 cloud bucket, and also when using minio as a middle-man to go to Backblaze storage before they supported native S3 commands. So, in my experience, the S3 cloud plugin has not worked for me after something changed from an older version.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Cloud Driver Bacula 9.6.7 -- is it broken?
On 2021-01-06 09:31, sruckh--- via Bacula-users wrote: After upgrading to Bacula 9.6.7 (upgrading below packages from repo -- CentOS 7 server), my S3 cloud backups are no longer working. bacula-mysql-9.6.7-1.el7.x86_64 bacula-aligned-9.6.7-1.el7.x86_64 bacula-cloud-storage-9.6.7-1.el7.x86_64 bacula-libs-9.6.7-1.el7.x86_64 The following errors are in the job's log: bacula-dir JobId 727: Fatal error: No Job status returned from FD. bacula-dir JobId 727: Error: Director's connection to SD for this Job was lost. bacula-dir JobId 727: Fatal error: Network error with FD during Backup: ERR=No data available bacula-dir JobId 727: Using Device "B2-AWS" to write. bacula-dir JobId 727: Start Backup JobId 727, Job=BackBlazeNextcloudPi.2021-01-06_09.11.11_11 No changes were made to the .conf files? With the upgrade, is it necessary to make changes for S3 cloud backups, or is something broken in the S3 driver? Thank You Looks like more than just cloud-driver as I could not use other configured Storage resources either. Maybe the 9.4.2-2 bacula-fd client from debian buster does not work with the CentOS 9.6.7-1 Storage-Daemon/Director? ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Cloud Driver Bacula 9.6.7 -- is it broken?
After upgrading to Bacula 9.6.7 (upgrading below packages from repo -- CentOS 7 server), my S3 cloud backups are no longer working. bacula-mysql-9.6.7-1.el7.x86_64 bacula-aligned-9.6.7-1.el7.x86_64 bacula-cloud-storage-9.6.7-1.el7.x86_64 bacula-libs-9.6.7-1.el7.x86_64 The following errors are in the job's log: bacula-dir JobId 727: Fatal error: No Job status returned from FD. bacula-dir JobId 727: Error: Director's connection to SD for this Job was lost. bacula-dir JobId 727: Fatal error: Network error with FD during Backup: ERR=No data available bacula-dir JobId 727: Using Device "B2-AWS" to write. bacula-dir JobId 727: Start Backup JobId 727, Job=BackBlazeNextcloudPi.2021-01-06_09.11.11_11 No changes were made to the .conf files? With the upgrade, is it necessary to make changes for S3 cloud backups, or is something broken in the S3 driver? Thank You ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Red Hat / CentOS community RPM packages v9.6.5
The logrotate script, /etc/logrotate.d/bacula, that gets installed from the RPM packages (Bacula Community Repo), has mode 0755. It should be 0644. Thank You ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] S3 Configuration for Bacula 9.6.5 on Debian 10
On 2020-07-02 15:53, r0...@nxlplyx.com wrote:
> I have compiled Bacula 9.6.5 on Debian 10, with a lot of help from the folks
> here.
>
> Now I cannot get S3 to work, probably my own lack of knowledge.
>
> I can back up and restore to local directories, that is no problem.
>
> However I am unable to get th S3 module to backup to an S3 server. I can use
> Fuse S3 to mount the S3 storage and move files back and forth.
>
> ===
>
> From ./bconsole
>
> The defined Storage resources are:
> 1: storage_dev_S3_nd1
> 2: File1
> 3: File2
> Select Storage resource (1-3): 1
> Connecting to Storage daemon storage_dev_S3_nd1 at debian:9103 ...
>
> (hangs and no log is produced)
>
> I can't figure out what else to do. Can anyone help?
>
> =
>
> bacula_sd.conf
>
> Device {
> Name = dev_S3_nd1
> Device Type = Cloud
> Cloud = S3Cloud
> Archive Device = /home/user1/dirNFS/bu/bacula_cloudstorage_test
> Maximum Part Size = 1000
> Media Type = CloudType
> LabelMedia = yes;
> Random Access = Yes;
> AutomaticMount = yes
> RemovableMedia = no
> AlwaysOpen = no
> }
>
> Cloud {
> Name = S3Cloud
> Driver = "S3"
> HostName = with Fuse S3)
> BucketName = "test_bucket"
> Access Key =
> Secret Key =
> Protocol = HTTPS
> UriStyle = VirtualHost
> Truncate Cache = No
> Upload = EachPart
> Region = "us-central-1"
> MaximumUploadBandwidth = 5MB/s
> }
>
> ==
>
> bacula_dir.conf
>
> Storage {
> Name = storage_dev_S3_nd1
> Address = debian
> SD Port = 9103
> Password =
> Device = dev_S3_nd1
> Media Type = CloudType
> }
>
> Job {
> Name = "BackupClient1-to-Cloud"
> JobDefs = "DefaultJob"
> Storage = storage_dev_S3_nd1
> Client = debian-fd
> }
Here is what I have configured --
baculda-sd-conf
Cloud {
Name = BackBlaze-AWS
Driver = "S3"
HostName = "somehost.com"
BucketName = "somebucket"
AccessKey = "AccessKey"
SecretKey = "SecretKey"
Protocol = HTTPS
Region = "someregion"
Upload = EachPart
}
Device {
Name = B2-AWS
Device Type = Cloud
Cloud = BackBlaze-AWS
Archive Device = /path/to/local/backup/directory
Maximum Part Size = 10485760
Media Type = B2-AWS-Type
LabelMedia = yes
Random Access = Yes;
AutomaticMount = yes
RemovableMedia = no
AlwaysOpen = no
}
bacula-dir.conf
Autochanger {
Name = B2-AWS
Address = fqdn.directory
SDPort = 9103
Password = "mypassword"
Device = B2-AWS
Media Type = B2-AWS-Type
Maximum Concurrent Jobs = 10
Autochanger = B2-AWS
}
Pool {
Name = B2-AWS-Pool
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 365 days
Maximum Volume Bytes = 268435456
Maximum Volumes = 8192
Storage = B2-AWS
CacheRetention = 30 days
LabelFormat = "B2-AWS-Vol-"
}___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Baculum w/Lighttpd (CentOS)
On 2020-05-23 01:04, Marcin Haba wrote: Hello Sruckh, Thanks for reporting this problem. It is a packaging issue. New packages will be available at the beginning new week. Best regards, Marcin Haba (gani) Thank You! ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Baculum w/Lighttpd (CentOS)
From this page, https://bit.ly/2TqMV5t, it has instruction for installing RPMs for Baculum on CentOS after setting up a repo. In on section there are specific instructions for installing if you are using Lighttpd: Installation for Lighttpd Installation on system with access via Lighttpd is as follows: yum install baculum-common baculum-api baculum-api-lighttpd Please note that in case CentOS distribution the Lighttpd web server is available in the distribution packages after enabling the EPEL repository. Start Baculum API as application using the Lighttpd web server: service baculum-api-lighttpd start Why is there still a dependency on installing http (apache) if using lighttpd? I thought I would give the repo a try as I am running lighttpd by not apache, but cancelled the install when I saw the dependency list. I was wondering if anyone else running Lighttpd has tried this? Thank You. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Minio Backblaze
On 2019-09-02 10:53, sruckh--- via Bacula-users wrote: I am using bacula v9.4.4 community edition on CentOS 7 server. I am trying to use minio to send backup to backblaze storage. From the logs it looks like quite a few hiccups occur with messages similar to this: msg=S3_put_object ERR=ConnectionFailed At the very end of the backup log file there is a message like this: Termination: Backup OK -- Upload to Cloud failed When looking at the smaller "part" files that make up a volume on the backblaze server, the parts that had errors in the log message appear to have 2 revisions of the file and the total file size of that part to be roughly double of the designated size of the part. I assume this not to be horribly abnormal as I assume the part is uploaded twice. Although the bacula log file does not really say that the volume was re-uploaded, I am just guessing that is what happens. Anyway, to be safe, I thought it might make sense to use the "cloud" functions from bconsole to sync the volume to the cloud. When I choose the "cloud" option and choose the appropriate storage, pool, and volume, it looks like the upload is unsuccessful and the following error is given: 3999 Error with the upload: ERR=SignatureDoesNotMatch As far as I can tell, that may be a minio/aws error, and I can't find anything necessarily related to bacula with the error. Is anyone here familiar with this error, and know the resolution? Thank You. Not sure if this is helpful, but this is what shows up in the minio trace log when trying to perform upload function from bacula: 21:48:51.145 [200 OK] s3.ListObjectsV1 localhost:9000/BucketName/?prefix=B2-Vol-1101 127.0.0.1 21:48:51.543 [403 Forbidden] s3.ListObjectsV1 localhost:9000/BucketName/?prefix=B2-Vol-1101=B2-Vol-1101/part.1901%20 127.0.0.1 So I do not know why the [403 Forbidden] message. That "part" file in question, part.1901, appears to be present on the remote B2 storage and is the correct file size [2019-09-02 02:08:40 MST] 10MiB part.1901 I notice the %20 [space] at the end of the filename in the trace message. I am wondering if that has anything to do with the issue, or if that is normal. Also, the part.1901 file is not one of the files that had one of the "connectionfailed" errors mentioned in earlier post, so not entirely sure if the 1901 file is relevant to the actual problem or not or just coincidental. If I run the same bacula upload test but on a different volume, this is the result from the trace log: 22:05:52.176 [200 OK] s3.ListObjectsV1 localhost:9000/BucketName/?prefix=B2-Vol-1100 127.0.0.1 22:05:52.691 [403 Forbidden] s3.ListObjectsV1 localhost:9000/BucketName/?prefix=B2-Vol-1100=B2-Vol-1100/part.1907%20 127.0.0.1 So the same [403 Forbidden] error message, with the same %20 at the end of the file name, but the part file is 1907 as opposed to 1901. The MD5SUM of the local file and the remote file on the B2 storage calculate to the same value. I don't know if this is a bug between bacula<-->minio or if this is an admin issue. Any assistance appreciated. Thank You. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Backup to USB Drive
On 2019-09-03 09:33, mau...@gmx.ch wrote: > Dear Bacula > > Please i need to Backup any Linux System to any USB Drive, please exist here > any possibilites to make this > > Job running to any USB Drive. > > I know i need to read the Manuall but please can you send me here any Topic > so that i can run trought. > > Regards > > Mauri > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users Check Out vchanger. It has specific documentation about using removable USB storage and how one my rotate removable storage. It has specific bacula configurations.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Minio Backblaze
I am using bacula v9.4.4 community edition on CentOS 7 server. I am trying to use minio to send backup to backblaze storage. From the logs it looks like quite a few hiccups occur with messages similar to this: msg=S3_put_object ERR=ConnectionFailed At the very end of the backup log file there is a message like this: Termination: Backup OK -- Upload to Cloud failed When looking at the smaller "part" files that make up a volume on the backblaze server, the parts that had errors in the log message appear to have 2 revisions of the file and the total file size of that part to be roughly double of the designated size of the part. I assume this not to be horribly abnormal as I assume the part is uploaded twice. Although the bacula log file does not really say that the volume was re-uploaded, I am just guessing that is what happens. Anyway, to be safe, I thought it might make sense to use the "cloud" functions from bconsole to sync the volume to the cloud. When I choose the "cloud" option and choose the appropriate storage, pool, and volume, it looks like the upload is unsuccessful and the following error is given: 3999 Error with the upload: ERR=SignatureDoesNotMatch As far as I can tell, that may be a minio/aws error, and I can't find anything necessarily related to bacula with the error. Is anyone here familiar with this error, and know the resolution? Thank You. -Scott ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula with Cloud Storage B2 Backblaze
I have used bacula off and on again for many years. Recently in this list I was asking for help trying to integrate Bacula with back-end cloud storage. Namely, I was trying to integrate with Backblaze cloud storage. I went around trying different solutions, and thought I would share here. My first attempt was to use rclone-changer (http://bit.ly/2DdvEEL). As I had used both rclone and duplicity using various scripts, this seemed like a natural place to start. Unfortunately, I could not get any farther than what it looked like other users experienced. It would work with a single virtual volume, but when you would try to label tapes with barcode command, it could not load and unload virtual tapes and label them correctly (outside the first volume). It looked like other people had had the same experience (based on bug reports). I was never able to get the solution working outside of using the one single virtual volume. Next I went for using, bacula's native, bacula-cloud-storage module. When I first starting down this path I was unaware that it was designed for S3/AWS. As I was wanting a Backblaze solution, I searched for a solution from the interwebs. This is where I found minio (http://bit.ly/2EW0ulV). It is basically a proxy between S3 command set and Backblaze that allows for backing up files in this fashion bacula->bacula-cloud-storage->minio->B2-cloud-engine. Although I did get this working, and it could certainly be a solution, I just was not comfortable with the configuration (don't have a real technical reason why I did not stick with solution). Next up I went with vchanger ( http://bit.ly/2E297eg ) and OpenDedup ( http://bit.ly/2ETFaxF ). In this solution I use OpenDedup to mount my Backblaze bucket to my local file-system, and use the vchanger script to act as my autochanger for my virtual volumes. Again, I am not 100% I completely have a handle of the mounted SDFS (backblaze volume). For example, it uses your local file system for speed. So I have not tested the scenario if my local volume disappeared. I am not 100% certain if I would be able to 100% recover using only the files (virtual tape volumes) that are in the cloud. On a side note I use the vchanger script outside of just for use with Backblaze storage. I don't have enough testing or experience with any of the configurations to recommend a good solution, but I thought it might be worth sharing some of the various configurations I tried with the goal of being able to integrate bacula with a back-end cloud storage engine. Thank You. Scott ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula w/Cloud_Storage (Backblaze)
On 2019-04-17 16:17, Heitor Faria wrote: I can see the necessary package (bacula-cloud-storage-9.4.2-1.el7.x86_64.rpm) on the bacula.org 9.4.2 repo rpms/9.4.2/el7/x86_64/: Parent Directory - [DIR] repodata/ 2019-02-14 19:20- [ ] bacula-aligned-9.4.2-1.el7.x86_64.rpm 2019-02-14 19:09 77K Red Hat Enterprise Linux / Centos version 7 [ ] bacula-bat-9.4.2-1.el7.x86_64.rpm 2019-02-14 19:09 7.2M Red Hat Enterprise Linux / Centos version 7 [ ] bacula-client-9.4.2-1.el7.x86_64.rpm2019-02-14 19:09 519K Red Hat Enterprise Linux / Centos version 7 [ ] bacula-cloud-storage-9.4.2-1.el7.x86_64.rpm 2019-02-14 19:09 186K Red Hat Enterprise Linux / Centos version 7 [ ] bacula-libs-9.4.2-1.el7.x86_64.rpm 2019-02-14 19:09 752K Red Hat Enterprise Linux / Centos version 7 [ ] bacula-mysql-9.4.2-1.el7.x86_64.rpm 2019-02-14 19:09 2.9M Red Hat Enterprise Linux / Centos version 7 [ ] bacula-postgresql-9.4.2-1.el7.x86_64.rpm2019-02-14 19:09 2.9M Red Hat Enterprise Linux / Centos version 7 [ ] bacula-updatedb-9.4.2-1.el7.rpm 2019-02-14 19:09 23K Red Hat Enterprise Linux / Centos version 7 [TXT] ChangeLog 2019-02-04 16:47 224K [TXT] Release_Notes-9.4.2-1.el7.txt Regards, Thank you for pointing out user error! I had apparently disabled the repository after installing bacula originally. After enabling the repo, as you pointed out, the necessary package, bacula-cloud-storage, was able to be installed. After installation, the storage director was able to be started without error using the proposed configuration from the web article. At this time I have not been able to test full functionality. I can report back later. Sorry for the noise. Thank you much for the help, as without this response it would have taken much longer to get this portion working. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula w/Cloud_Storage (Backblaze)
I have been working on trying to use bacula to backup to Backblaze cloud storage. I have tried to work through this article: http://bit.ly/2VFukBx which uses rclone-changer wrapper. I tried this version of rclone-changer: http://bit.ly/2VQjxov and as suggested from this list, this version too: http://bit.ly/2DdvEEL I was unable to get either solution totally working (The best I could do is get 1 Volume labeled and working correctly with backup going to cloud). It does not look like rclone-changer is under active development, nor is there any active support (other than what has been provided through this list). Based on the git page for rclone-changer, it looks like multiple people are having the exact same experience with rclone-chager as I am. In looking for alternative solutions, I also came across this article, http://bit.ly/2VREW0q, that uses minio as a gateway from your localhost to your cloud back-end. I am able to get minio working, but it does not look like the community edition of bacula that I am using includes the necessary plugins to support the configuration listed in the web article. I have the following bacula community edition packages installed: bacula-mysql-9.4.2-1.el7.x86_64 and bacula-libs-9.4.2-1.el7.x86_64. It looks like I need the file, bacula-sd-cloud-driver-9.4.2.so, which does not seem to be included with any of the packages I have configured from the yum repository. I tried running repoquery and yum with 'whatprovides', and I did not get any matching hits. Is this plug-in only available for bacula enterprise customers? I am currently using a myriad of solutions (duplicacy, duplicity, rclone, etc) for backing up files to Backblaze, but ultimately I would like to use Bacula and get rid of some of the other unorganized processes I am using. If you have a working solution for using Bacula with Backblaze or similar Cloud storage, can you please point me in the right direction? Thank You. Scott ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] rclone / Autochanger / BackBlaze [SOLVED -- Maybe NOT]
On 2019-04-12 15:18, sruckh--- via Bacula-users wrote: > After deleting all the files and starting over, the label process, with the > new script was able to complete without error. > > Thank You. Wanderlei, I maybe have been premature on stating this was solved, or I am not understanding how this is supposed to work (which is entirely possible). As mentioned previously, made it all the way through the "label" command without error. As a test I started with setting slots to 25 in the rclone-changer script. After the label command completed without error, my b2 bucket was populated with 25 directories with each directory populated with a single file. This seems reasonable. I kicked off a backup job, using the above configured storage, and it appears to complete without error. The file that is configured as the "Archive Device" in the storage daemon configuration file appears to get written to and its size looks roughly to be the same size as the backup job reported for number of bytes written. My "Maximum Spool Size" was set to 400MB and the backup job was about 850MB. My expectation is that I would see something in my b2 bucket for this backup, but unfortunately it does not look like any data was written to the b2 storage. It still only has the 25 directories with the single file in each directory. I am not completely following the rclone-changer code, but I am looking at the config.archivedevice parameter. I looks like archive device is something that gets passed in from the configuration in the bacula storage daemon configuration, but I don't entirely see how config.archivedevice actually gets set using the passed in value (but again I have never written a python program before). Anyway, it is assumed some data should have been written to the b2 bucket and it is not. If I can do anything the help debug, please let me know. Thank You.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] rclone / Autochanger / BackBlaze [SOLVED]
On 2019-04-12 12:52, sruckh--- via Bacula-users wrote: > On 2019-04-12 12:03, Wanderlei Huttel wrote: > >> Hello Sruckh >> >> Try to use the rclone from this repository >> https://github.com/wanderleihuttel/rclone-changer >> >> Best regards >> WANDERLEI HÜTTEL >> http://www.bacula.com.br [1] > > Thank you for the suggestion. > I was using script from this repository > https://github.com/travisgroth/rclone-changer > I have now downloaded the version from > https://github.com/wanderleihuttel/rclone-changer > I changed the shebang to match my environment for python 3.6. I updated the > variable section with the same details as before. I connected to bconsole > and re-ran the label command (label barcodes storage=Cloud_b2 pool=Offsite); > same as before. > The new script seemed to take the variables as configured in the > configuration section, which is good. > Both scripts caused similar results from bconsole: > > Sending label command for Volume "VTAPE-0500" Slot 500 ... > 3307 Issuing autochanger "unload Volume VTAPE-0499, Slot 499, Drive 0" > command. > 3304 Issuing autochanger "load Volume VTAPE-0500, Slot 500, Drive 0" command. > 3305 Autochanger "load Volume VTAPE-0500, Slot 500, Drive 0", status is OK. > Too many tries: Wrong Volume mounted on Vtape device "BaculaVTL" > (/zfsstore/backups/bacula/vtape/tape): Wanted VTAPE-0500 have VTAPE-1 > 3920 Cannot label Volume because it is already labeled: "VTAPE-1" > Label command failed for Volume VTAPE-0500. > > A bunch of directories did get created in the backblaze bucket along with a > single file in each directory. Which seem similar to the experiences posted > here ( http://bit.ly/2DdCXvY ). > I will have to go back and verify the configuration again, and possibly start > over with a clean slate just in case something got messed up with the older > script. > Thank You. After deleting all the files and starting over, the label process, with the new script was able to complete without error. Thank You. Links: -- [1] http://www.bacula.com.br/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] rclone / Autochanger / BackBlaze
On 2019-04-12 12:03, Wanderlei Huttel wrote: > Hello Sruckh > > Try to use the rclone from this repository > https://github.com/wanderleihuttel/rclone-changer > > Best regards > > WANDERLEI HÜTTEL > http://www.bacula.com.br [1] Thank you for the suggestion. I was using script from this repository https://github.com/travisgroth/rclone-changer I have now downloaded the version from https://github.com/wanderleihuttel/rclone-changer I changed the shebang to match my environment for python 3.6. I updated the variable section with the same details as before. I connected to bconsole and re-ran the label command (label barcodes storage=Cloud_b2 pool=Offsite); same as before. The new script seemed to take the variables as configured in the configuration section, which is good. Both scripts caused similar results from bconsole: Sending label command for Volume "VTAPE-0500" Slot 500 ... 3307 Issuing autochanger "unload Volume VTAPE-0499, Slot 499, Drive 0" command. 3304 Issuing autochanger "load Volume VTAPE-0500, Slot 500, Drive 0" command. 3305 Autochanger "load Volume VTAPE-0500, Slot 500, Drive 0", status is OK. Too many tries: Wrong Volume mounted on Vtape device "BaculaVTL" (/zfsstore/backups/bacula/vtape/tape): Wanted VTAPE-0500 have VTAPE-1 3920 Cannot label Volume because it is already labeled: "VTAPE-1" Label command failed for Volume VTAPE-0500. A bunch of directories did get created in the backblaze bucket along with a single file in each directory. Which seem similar to the experiences posted here ( http://bit.ly/2DdCXvY ). I will have to go back and verify the configuration again, and possibly start over with a clean slate just in case something got messed up with the older script. Thank You. Links: -- [1] http://www.bacula.com.br/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] rclone / Autochanger / BackBlaze
On 2019-04-12 05:45, Martin Simmons wrote: I suggest running the rclone-changer in a shell to see what it prints. You could also try replacing /usr/local/bin/rclone-changer in the Changer Command with a shell script that logs its arguments and output like this (untested): #!/bin/sh echo "Arguments: $@" > /tmp/test.log /usr/local/bin/rclone-changer "$@" 2>&1 | tee -a /tmp/test.log __Martin Good idea! That has gotten me further. It looks like the script was not taking the defined variables (inserted at the top of the script) as described in the on-line documentation. It was instead using the values that were hard coded later down in the script. I set the "default" values later down in the script to match those that were defined at the top of the script. This has got the Virtual Tape files created and labeled. Thank You. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] rclone / Autochanger / BackBlaze
I am not sure this is the correct forum for this question, but as the
article I am referring to is on the bacula.us website I thought I would
try this mailing list.
I am running CentOS 7.6 server and Bacula v9.4.2 (from RPMs)
I am trying to get the functionality in this documentation (
http://bit.ly/2VFukBx ) modified to work with my configuration.
I am trying to use Backblaze as my backend as opposed to AWS which is
used in the documentation.
I have rclone set up and working (I was able to copy files to Backblaze
bucket).
I have downloaded both rclone-changer and rclone, and put them in
/usr/local/bin (mode:0755 owned by root:root).
I have copied the rclone.conf file to /opt/bacula/etc/ (mode:0600 owned
by bacula:root)
The following modifications have been made to bacula-sd.conf
Autochanger {
Name = "rclone_b2"
Device = BaculaVTL
Changer Device = 'BaculaVTL:BaculaVTL'
Changer Command = "/usr/local/bin/rclone-changer %c %o %S %a"
}
Device {
Name = BaculaVTL
Media Type = BaculaVTL
Maximum Changer Wait = 18000
Archive Device = /zfsstore/backups/bacula/vtape/tape
Autochanger = yes
LabelMedia = yes;
Random Access = Yes;
AutomaticMount = no;
RemovableMedia = no;
AlwaysOpen = no;
Spool Directory = /zfsstore/backups/bacula/bacula-spool
Maximum Spool Size = 419430400
}
These modifications have been made to bacula-dir.conf
Autochanger {
Name = Cloud_b2
Address = firewall
SDPort = 9103
Password = "secret"
Device = rclone_b2
Media Type = BaculaVTL
Autochanger = Cloud_b2
Maximum Concurrent Jobs = 10
}
Pool {
Name = Offsite
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Storage = Cloud_b2
Maximum Volume Bytes = 1073741824
AutoPrune = yes
Volume Retention = 4 weeks
}
In the rclone-changer script I have inserted the following:
class Rclone(object):
"""
Rclone contains logic to convert simple commands to full rclone
command line
calls with error handling
"""
#=
# Default params config
#=
rclone = '/usr/local/bin/rclone'
config = '/opt/bacula/etc/rclone.conf'
logFile= '/opt/bacula/working/rclone.log'
logChanger = '/opt/bacula/working/rclone-changer.log'
lockFile = '/opt/bacula/working/.rclonelock'
stateFile = '/opt/bacula/working/rclone-changer.state'
slots = 100
#=
options = []
@staticmethod
Towards the end of the article it states to go into bconsole and run the
following command:
label barcodes storage=Cloud_b2 pool=Offsite
When doing this I get the following output:
Connecting to Storage daemon Cloud_b2 at firewall:9103 ...
Connecting to Storage daemon Cloud_b2 at firewall:9103 ...
3306 Issuing autochanger "slots" command.
Device "rclone_b2" has 0 slots.
No slots in changer to scan.
I would expect the results to do something with the 100 slots configured
in the rclone-changer script. I am not even sure that the
rclone-changer script is getting called. I added some code to write to
a file as a test, and that file was not created or written to disk.
I am not sure if anyone has tried to do this with CentOS, bacula 9.4.2,
and the bacula-changer script, but I could use some help from someone
who has done something similar. I have never configured an auto-changer
let alone a virtual auto-changer.
Thank you for your assistance.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
