Re: [Bacula-users] Bacula community repo SHA1 pubkey
Hello Rob, There’s already an issue open since a year Bacula bug tracker https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues/2681 Up to now, I haven’t seen any progress or plan to fix this issue, this is why I’ve built my own binaries. If nobody from Bacula side provide a “fix”, I will simply share the rpm I have built on my own. Let’s wait a couple days of days to see how f something happen. I’ll keep you posted. Best regards Davide On Thu, May 9, 2024 at 17:37 Rob Gerber wrote: > Hello, > > The bacula community repo currently signs their packages with a SHA1 key. > SHA1 is deprecated in EL9 onwards, and poses a security risk that only > increases over time. > > Do the community package maintainers have any plans to update the package > signing process to use a SHA256 or greater SHA cipher? This would be a good > move for a project which positions itself in the enterprise software space. > > I appreciate that this change would entail change and difficulty, and that > there might be some downsides for users of older bacula distributions, or > for those who have previously installed bacula using an older key. I do not > know if it is possible to sign a package with both the old SHA1 key and a > newer SHA256+ key (I suspect not, but this isn't my field of expertise). > > Given that bacula 15.x is in beta, this might be a good time to sign the > next 15.x release with a new SHA256+ key, so at least packages 15.x onwards > are signed with a more secure cipher standard. > > Here is a brief writeup on the subject. I hope it is useful. > > https://www.redhat.com/en/blog/rhel-security-sha-1-package-signatures-distrusted-rhel-9 > > Regards, > Robert Gerber > 402-237-8692 > r...@craeon.net > ___ > 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-fd appearing to use wrong storage server
Thanks man You nailed it down. I did comment out this setting and it worked immediately. I did completely overlooked this before. I have now removed it form all my client files and also the template that is used by my client auto-install script. Many thanks, Gaston -Original Message- From: Bill Arlofski via Bacula-users Sent: Friday, 26 April, 2024 00:24 To: bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] bacula-fd appearing to use wrong storage server On 4/25/24 3:55 PM, gaston.gloesener--- via Bacula-users wrote: > Thanks for the rplies, > > I include here some of the requested informations. > > First abouth the "bconsole reload", yes I did not do, but I did restart the > director, the storage and file deamons several times after the config change. > Also because I did run them in forground with debug. Hello Gaston, I am re-sending this since the last one I sent I had included a screenshot which will not translate well for search engines, etc... The problem had pointed out in the screenshot was that it looks like you are using the `FDStorageAddress` setting in this client. I believe this is causing your issue.: 8<> *show job=Backup-james1 > Job: name=Backup-james1 JobType=66 level=Incremental Priority=10 Enabled=1 > MaxJobs=1 NumJobs=0 Resched=0 Times=0 Interval=1,800 Spool=0 > WritePartAfterJob=1 > Accurate=1 >--> Client: Name=james1-fd Enabled=1 Address=james1.home > FDport=9102 MaxJobs= 1 NumJobs=0 > JobRetention=6 months FileRetention=2 months AutoPrune=1 > FDStorageAddress=bacula.home > <--- HERE >--> Catalog: name=MyCatalog address=*None* DBport=0 db_name=bacula >db_driver=PostgreSQL db_user=bacula MutliDBConn=0 >--> FileSet: name=Full Set IgnoreFileSetChanges=0 8< If this is not it, we will look a little deeper. :) Hope this helps, Bill -- Bill Arlofski w...@protonmail.com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-fd appearing to use wrong storage server
On 4/25/24 3:55 PM, gaston.gloesener--- via Bacula-users wrote: Thanks for the rplies, I include here some of the requested informations. First abouth the "bconsole reload", yes I did not do, but I did restart the director, the storage and file deamons several times after the config change. Also because I did run them in forground with debug. Hello Gaston, I am re-sending this since the last one I sent I had included a screenshot which will not translate well for search engines, etc... The problem had pointed out in the screenshot was that it looks like you are using the `FDStorageAddress` setting in this client. I believe this is causing your issue.: 8<> *show job=Backup-james1 Job: name=Backup-james1 JobType=66 level=Incremental Priority=10 Enabled=1 MaxJobs=1 NumJobs=0 Resched=0 Times=0 Interval=1,800 Spool=0 WritePartAfterJob=1 Accurate=1 --> Client: Name=james1-fd Enabled=1 Address=james1.home FDport=9102 MaxJobs= 1 NumJobs=0 JobRetention=6 months FileRetention=2 months AutoPrune=1 FDStorageAddress=bacula.home <--- HERE --> Catalog: name=MyCatalog address=*None* DBport=0 db_name=bacula db_driver=PostgreSQL db_user=bacula MutliDBConn=0 --> FileSet: name=Full Set IgnoreFileSetChanges=0 8< If this is not it, we will look a little deeper. :) Hope this helps, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-fd appearing to use wrong storage server
efix=*None* LabelType=0
RecyleOldest=0 PurgeOldest=0 ActionOnPurge=0
MaxVolJobs=1 MaxVolFiles=0 MaxVolBytes=200
MaxPoolBytes=0
MigTime=0 secs MigHiBytes=0 MigLoBytes=0
CacheRetention=0 secs
JobRetention=0 secs FileRetention=0 secs
Catalog=MyCatalog
--> Autochanger: name=vTape2 address=nas1.home SDport=9103 MaxJobs=2 NumJobs=0
DeviceName=vChanger2 MediaType=vtape2 StorageId=5 Autochanger=1
AC group=5 ShareStore=*none*
--> Messages: name=Standard
mailcmd=/opt/bacula/bin/bsmtp -h smtp.pt.lu -f "(Bacula) <%r>" -s
"Bacula: %t %e of %c %l" %r
opcmd=/opt/bacula/bin/bsmtp -h smtp.pt.lu -f "(Bacula) <%r>" -s "Bacula:
Intervention needed for %j" %r
For me thsio all look slike expected.
In the client definition file (below) I did basically only change vTape1 to
vTape2 storage in the pools.
#
# Specification:
#
# ? : Only include if VAR is not empty
# %{}: reüplace by contents of var
# : ^ : capitalize
# : ^^ : upper case
Client {
Name = "james1-fd"
Address = "james1.home"
FdStorageAddress = "bacula.home"
FdPort = 9102
Password = "xxx"
Catalog = "MyCatalog"
FileRetention = 5184000
JobRetention = 15552000
AutoPrune = yes
}
Job {
Name = "Backup-james1"
Type = "Backup"
Client = "james1-fd"
JobDefs = "DefaultJob"
ReRunFailedLevels = yes
Accurate = yes
FullBackupPool = "james1-Full-Pool"
IncrementalBackupPool = "james1-Incr-Pool"
DifferentialBackupPool = "james1-Diff-Pool"
}
Pool {
Name = "james1-Full-Pool"
Description = "Pool for client james1 full backups"
PoolType = "Backup"
LabelFormat = "james1-full-"
MaximumVolumeJobs = 1
MaximumVolumeBytes = 200
VolumeRetention = 8726400
Storage = "vTape2"
Catalog = "MyCatalog"
}
Pool {
Name = "james1-Diff-Pool"
Description = "Pool for client james1 diff backups"
PoolType = "Backup"
LabelFormat = "james1-diff-"
MaximumVolumeJobs = 1
MaximumVolumeBytes = 200
VolumeRetention = 8726400
Storage = "vTape2"
Catalog = "MyCatalog"
}
Pool {
Name = "james1-Incr-Pool"
Description = "Pool for client james1 incremental backups"
PoolType = "Backup"
LabelFormat = "james1-incr-"
MaximumVolumeJobs = 5
MaximumVolumeBytes = 200
VolumeRetention = 3369600
Storage = "vTape2"
Catalog = "MyCatalog"
}
-Original Message-
From: Bill Arlofski via Bacula-users
Sent: Thursday, 25 April, 2024 20:40
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] bacula-fd appearing to use wrong storage server
On 4/25/24 3:17 AM, gaston.gloesener--- via Bacula-users wrote:
>
> Until now I did run bacula in a virtual machine running the director
> and storage deamon. The storage daemon was stroing data to files on a shared
> directory as the storage is on a NAS.
>
> Now I have build bacula-sd for the NAS to avoid this duplicate
> transfer. I have configured one client to use the new storage but while it
> uses it, it claims to still contact the “old” storage daemon on the bacula
> node.
Hello Gaston,
A bconsole `show job=` will show what the Director knows about this job.
It is quite possible, and my guess that one of two possible things has happened:
#1: You forgot to issue the bconsole reload command
#2: The Director has reached its default configuration reload limit of 32 and
is no longer reloading
You can check with:
* status director
...and look at the header line:
`Daemon started 24-Apr-24 18:55, conf reloaded 24-Apr-2024 18:55:27`
If the `conf reloaded` time is not recent, then you have hit #2 above and
simply need to restart the Director.
Hope this helps,
Bill
--
Bill Arlofski
w...@protonmail.com
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-fd appearing to use wrong storage server
On 4/25/24 3:17 AM, gaston.gloesener--- via Bacula-users wrote: > Until now I did run bacula in a virtual machine running the director and storage deamon. The storage daemon was stroing data to files on a shared directory as the storage is on a NAS. Now I have build bacula-sd for the NAS to avoid this duplicate transfer. I have configured one client to use the new storage but while it uses it, it claims to still contact the “old” storage daemon on the bacula node. Hello Gaston, A bconsole `show job=` will show what the Director knows about this job. It is quite possible, and my guess that one of two possible things has happened: #1: You forgot to issue the bconsole reload command #2: The Director has reached its default configuration reload limit of 32 and is no longer reloading You can check with: * status director ...and look at the header line: `Daemon started 24-Apr-24 18:55, conf reloaded 24-Apr-2024 18:55:27` If the `conf reloaded` time is not recent, then you have hit #2 above and simply need to restart the Director. Hope this helps, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-fd appearing to use wrong storage server
It would be useful to see the bacula-dir.conf Job and Client resources for
this job and also the full job log.
__Martin
> On Thu, 25 Apr 2024 11:17:18 +0200, gaston gloesener--- via Bacula-users
> said:
>
> Until now I did run bacula in a virtual machine running the director and
> storage deamon. The storage daemon was stroing data to files on a shared
> directory as the storage is on a NAS.
>
> Now I have build bacula-sd for the NAS to avoid this duplicate transfer. I
> have configured one client to use the new storage but while it uses it, it
> claims to still contact the “old” storage daemon on the bacula node.
>
> Using bacula 13.0.4
>
> Here is the storage definition in bacula-dir.conf (vTape1 is the original 1,
> vTape2 the new one):
> Storage {
> Name = "vTape1"
> SdPort = 9103
> Address = "bacula.home "
> Password = "…deleted…"
> Device = "vChanger1"
> MediaType = "vtape1"
> Autochanger = "vTape1"
> MaximumConcurrentJobs = 2
> }
> Storage {
> Name = "vTape2"
> SdPort = 9103
> Address = "nas1.home "
> Password = "…deleted…"
> Device = "vChanger2"
> MediaType = "vtape2"
> Autochanger = "vTape2"
> MaximumConcurrentJobs = 2
> }
>
> The client pool definition looks now like:
>
> Pool {
> Name = "james1-Full-Pool"
> Description = "Pool for client james1 full backups"
> PoolType = "Backup"
> LabelFormat = "james1-full-"
> MaximumVolumeJobs = 1
> MaximumVolumeBytes = 200
> VolumeRetention = 8726400
> Storage = "vTape2"
> Catalog = "MyCatalog"
> }
>
> I have tried a manual and the scheduled job with same result:
>
> *(James1-fd says:
>
> 25-Apr-2024 01:00:00 james1-fd: bsockcore.c:472-7062 OK connected to server
> Storage daemon bacula.home:9103. socket=10.1.10.111.60144:10.1.200.12.9103
> s=0x7fa01c01ac88
> 2
>
> The full log:
>
> 25-Apr-2024 01:00:00 james1-fd: bnet_server.c:235-0 Accept
> socket=10.1.10.111.9102:10.1.200.12.45200 s=0x563bfba72728
> 25-Apr-2024 01:00:00 james1-fd: authenticate.c:67-0 authenticate dir: Hello
> Director bacula-dir calling 10002 tlspsk=100
> 25-Apr-2024 01:00:00 james1-fd: authenticatebase.cc:365-0 TLSPSK Remote need
> 100
> 25-Apr-2024 01:00:00 james1-fd: authenticate.c:90-0 *** No FD compression to
> DIR
> 25-Apr-2024 01:00:00 james1-fd: authenticatebase.cc:335-0 TLSPSK Local need
> 100
> 25-Apr-2024 01:00:00 james1-fd: authenticatebase.cc:563-0 TLSPSK Start PSK
> 25-Apr-2024 01:00:00 james1-fd: bnet.c:96-0 TLS server negotiation
> established.
> 25-Apr-2024 01:00:00 james1-fd: cram-md5.c:68-0 send: auth cram-md5 challenge
> <2032624038.1713999600@james1-fd> ssl=0
> 25-Apr-2024 01:00:00 james1-fd: cram-md5.c:156-0 sending resp to challenge:
> L6/ZMB/xti+re9kmB4sR+D
> 25-Apr-2024 01:00:00 james1-fd: events.c:48-0 Events: code=FC0002
> daemon=james1-fd ref=0x7fa01c00b0a8 type=connection source=bacula-dir
> text=Director connection
> 25-Apr-2024 01:00:00 james1-fd: fd_plugins.c:1714-7062 Instantiate
> plugin_ctx=563bfbb34378 JobId=7062
> 25-Apr-2024 01:00:00 james1-fd: fd_plugins.c:254-7062 plugin_ctx=563bfbb34378
> JobId=7062
> 25-Apr-2024 01:00:00 james1-fd: fd_plugins.c:147-7062 name= len=0
> plugin=bpipe-fd.so plen=5
> 25-Apr-2024 01:00:00 james1-fd: job.c:2499-7062 level_cmd: level = full
> mtime_only=0
> 25-Apr-2024 01:00:00 james1-fd: fd_plugins.c:254-7062 plugin_ctx=563bfbb34378
> JobId=7062
> 25-Apr-2024 01:00:00 james1-fd: fd_plugins.c:147-7062 name= len=0
> plugin=bpipe-fd.so plen=5
> 25-Apr-2024 01:00:00 james1-fd: fd_plugins.c:254-7062 plugin_ctx=563bfbb34378
> JobId=7062
> 25-Apr-2024 01:00:00 james1-fd: fd_plugins.c:147-7062 name= len=0
> plugin=bpipe-fd.so plen=5
> 25-Apr-2024 01:00:00 james1-fd: bsockcore.c:472-7062 OK connected to server
> Storage daemon bacula.home:9103. socket=10.1.10.111.60144:10.1.200.12.9103
> s=0x7fa01c01ac88
> 25-Apr-2024 01:00:00 james1-fd: authenticatebase.cc:335-7062 TLSPSK Local
> need 100
> 25-Apr-2024 01:00:05 james1-fd: hello.c:183-7062 Recv caps from SD failed.
> ERR=Success
> 25-Apr-2024 01:00:05 james1-fd: hello.c:185-7062 Recv caps from SD failed.
> ERR=Success
> 25-Apr-2024 01:00:05 james1-fd: events.c:48-7062 Events: code=FC0001
> daemon=james1-fd ref=0x7fa01c00b0a8 type=connection source=bacula-dir
> text=Director disconnection
> 25-Apr-2024 01:00:05 james1-fd: fd_plugins.c:1749-7062 Free instance
> plugin_ctx=563bfbb34378 JobId=7062
>
> The job log on the director confirms:
>
> 2024-04-25 01:00:00 bacula-dir JobId 7062: Connected to Storage "vTape2" at
> bacula.home:9103 with TLS
>
> So correct storage but bad server. Note that vTape 2 has always been pointing
> to nas1 (not bacula) and the director (as well as james1-fd and both storage
> deamons) was restarted several times
>
> The storage daemon on nas1 reports only a connection from the director, the
> ip address of the client (10.1.10.111) is never seen:
>
> 25-Apr-2024 01:00:00 nas1-sd: bnet_server.c:235-0 Accept
>
Re: [Bacula-users] Bacula and german special chars "umlauts"
I think those special chars are already in the filesystem like this. It's no big deal as long as they are in the backups ;-) Choosing files in the GUI is still possible, it just looks ugly or incorrect somehow. I will check if that relates to the way samba was set up there etc (the relevant files are hosted by Samba) ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and german special chars "umlauts"
Am 09.04.24 um 08:38 schrieb Marcin Haba:
Hello Stefan,
Yes, filenames displayed in the restore process.
Also it might be good to check how the names are stored in the database
in the File table if everything is fine there.
will try that in an hour or so.
currently editing Jobs and doing initial Full runs to test them
Let me ask something not related to umlauts here:
In Amanda I had "disk list entries" defined, one per Samba-share to
backup ... and one for each virtual machine dump located on a samba
share: Veeam dumps to a samba share, I let amanda and now bacula read
that and push to tape.
The idea there is to have many DLEs (=disk list entries) to make use of
the scheduler there: it creates a dynamic schedule every run and
combines fulls and incrementals of the DLEs to meet the overall goals
("create one full backup of this DLE within N days").
I still tend to define more Jobs in Bacula and not do huge Jobs
containing hundreds of Gigs and multiple VMs in one Job.
That leads to more manual editing ;-) but OK; that's done now at
migration time.
Is it recommended to use more Jobs? I assume it's quicker and easier to
handle, for example at restore time etc
Any problems I create by doing so?
Thanks for any pointers here
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and german special chars "umlauts"
Hello Stefan, Yes, filenames displayed in the restore process. Also it might be good to check how the names are stored in the database in the File table if everything is fine there. Best regards, Marcin Haba (gani) On Tue, 9 Apr 2024 at 08:20, Stefan G. Weichinger wrote: > Am 09.04.24 um 08:04 schrieb Marcin Haba: > > Hello Stefan, > > > > I agree with Anders' advice to check Bacula first. Bacula stores file > > names in the database as they are, without interpreting them, no > > encoding conversion. It means that something is wrong on the input when > > names are stored, it will also be wrong on the output when names are get > > from the database. > > And would do I check in Bacula? > > The display of filenames in the Restore-process? > > -- "Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and german special chars "umlauts"
Am 09.04.24 um 08:04 schrieb Marcin Haba: Hello Stefan, I agree with Anders' advice to check Bacula first. Bacula stores file names in the database as they are, without interpreting them, no encoding conversion. It means that something is wrong on the input when names are stored, it will also be wrong on the output when names are get from the database. And would do I check in Bacula? The display of filenames in the Restore-process? ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and german special chars "umlauts"
Hello Stefan, I agree with Anders' advice to check Bacula first. Bacula stores file names in the database as they are, without interpreting them, no encoding conversion. It means that something is wrong on the input when names are stored, it will also be wrong on the output when names are get from the database. Best regards, Marcin Haba (gani) On Tue, 9 Apr 2024 at 07:15, Anders Gustafsson wrote: > Not using bacularis, but accented characters, used in all languages, > except English and some odd language > spoken by about 1000 people on an island in the Pacific, work for us. Try > restoring from bconsole to rule out > that it is a bacula issue and not just a bacularis one. > > -- > Med vänlig hälsning > > Anders Gustafsson, ingenjör > anders.gustafs...@pedago.fi | Support +358 18 12060 | Direkt +358 9 > 315 45 121 | Mobil +358 40506 7099 > > Pedago interaktiv ab, Nygatan 7 B , AX-22100 MARIEHAMN, ÅLAND, FINLAND > > > > >>> "Stefan G. Weichinger" 2024-04-09 08:06 >>> > > I am in the process of installing and configuring Bacula-13.0.4 and > Bacularis-2.7.0 on a Debian-12.5 server. > > (moving over from using Amanda, I might ask a few questions around that > soon) > > What I noticed: when I access "Restore" in Bacularis, there are files > displayed with strange chars instead of the correct german special chars > or "Umlauts". > > That's something I would like to get correct from the start. > > I installed from the deb-packages and use postgresql as database. > > Didn't notice any specific choice of charsets or so. > > Does that maybe come from the language I chose for Bacularis? > > Right now I have it in english ... > > pls advise, thanks, Stefan > > > ___ > 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 > -- "Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and german special chars "umlauts"
Not using bacularis, but accented characters, used in all languages, except English and some odd language spoken by about 1000 people on an island in the Pacific, work for us. Try restoring from bconsole to rule out that it is a bacula issue and not just a bacularis one. -- Med vänlig hälsning Anders Gustafsson, ingenjör anders.gustafs...@pedago.fi | Support +358 18 12060 | Direkt +358 9 315 45 121 | Mobil +358 40506 7099 Pedago interaktiv ab, Nygatan 7 B , AX-22100 MARIEHAMN, ÅLAND, FINLAND >>> "Stefan G. Weichinger" 2024-04-09 08:06 >>> I am in the process of installing and configuring Bacula-13.0.4 and Bacularis-2.7.0 on a Debian-12.5 server. (moving over from using Amanda, I might ask a few questions around that soon) What I noticed: when I access "Restore" in Bacularis, there are files displayed with strange chars instead of the correct german special chars or "Umlauts". That's something I would like to get correct from the start. I installed from the deb-packages and use postgresql as database. Didn't notice any specific choice of charsets or so. Does that maybe come from the language I chose for Bacularis? Right now I have it in english ... pls advise, thanks, Stefan ___ 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 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 support LTO9?
Thank you for your answers. On Tue, Apr 2, 2024 at 7:10 PM Bill Arlofski via Bacula-users < bacula-users@lists.sourceforge.net> wrote: > On 4/2/24 3:52 PM, Jose Alberto wrote: > > Hi. > > > > I work with Bacula (11 and 13) with lto8, all fine. > > > > with bacula 13 or 15 work LTO9 ? > > Yes. ;) > > You may want to run some tests using btape to find the right > `MaximumFileSize` and `MaximumBlockSize` for your tape drive(s), > but I can assure you (personally working in Quantum's lab testing Bacula > with their latest Scalar i6000 library and LTO9 > drives), Bacula absolutely works fine with them. > > The settings I found that work quite well with LTO9 drives (with 10+ > concurrent backup streams) are: > 8< > MaximumFileSize = 32GB > MaximumBlockSize = 2097152 > 8< > > I have also attached a script I wrote to automate the testing of several > file and block size combinations using btape. > > Please have a look and be sure to read the btape documentation to > understand what is going on before running the script - > also there are variable settings at the top you will need to edit to fit > your environment. > > > Hope this helps, > Bill > > -- > Bill Arlofski > w...@protonmail.com > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- # # Sistema Operativo: Debian # #Caracas, Venezuela # # ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula support LTO9?
On 4/2/24 3:52 PM, Jose Alberto wrote: Hi. I work with Bacula (11 and 13) with lto8, all fine. with bacula 13 or 15 work LTO9 ? Yes. ;) You may want to run some tests using btape to find the right `MaximumFileSize` and `MaximumBlockSize` for your tape drive(s), but I can assure you (personally working in Quantum's lab testing Bacula with their latest Scalar i6000 library and LTO9 drives), Bacula absolutely works fine with them. The settings I found that work quite well with LTO9 drives (with 10+ concurrent backup streams) are: 8< MaximumFileSize = 32GB MaximumBlockSize = 2097152 8< I have also attached a script I wrote to automate the testing of several file and block size combinations using btape. Please have a look and be sure to read the btape documentation to understand what is going on before running the script - also there are variable settings at the top you will need to edit to fit your environment. Hope this helps, Bill -- Bill Arlofski w...@protonmail.com tape_speed_tests.sh Description: application/shellscript signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula support LTO9?
Bacula should work with LTO 9 just fine. I would be very surprised if it had issues with LTO 9. Some users on the mailing list have mentioned that they use LTO 9. Robert Gerber 402-237-8692 r...@craeon.net On Tue, Apr 2, 2024, 4:53 PM Jose Alberto wrote: > Hi. > > I work with Bacula (11 and 13) with lto8, all fine. > > with bacula 13 or 15 work LTO9 ? > > > -- > # > # Sistema Operativo: Debian # > #Caracas, Venezuela # > # > ___ > 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
Re: [Bacula-users] Bacula 15.02 upgrade on Centos 7 -- Storage Daemon not starting
Hello, Glad we got this working. :) Regarding any possible user:group changes, I guess you would have to contact the person who maintains the package for the CentOS 7 Linux distribution - And quite frankly, I am surprised that 15.0.2 is already available as it was *just* release some days ago. Kudos to the maintainer for being "Johnny on the Spot"™ :) To fix everything, just figure out what user:group the Bacula SD is currently running as, make sure this combination has read/write access to all of the file volumes, and any directories/files (eg: /opt/bacula/working) and you should be all set. P.S. I think it is time to upgrade/migrate from CentOS 7 ;) Best regards, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ 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 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 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. Hope this helps, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Release 15.0.2
Hello Eric & team, thanks for the update & your continuing support of the bacula community edition. I just upgraded my first bacula install from 13.0.2 to 15.0.2 without any issues whatsoever (Ubuntu 22.04, bacula compiled from source). All the best, Uwe -- Uwe Schürkamp // email: ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula BPIPE help
Hello,
czw., 7 mar 2024 o 22:58 Ismael Matos napisał(a):
> Hello all,
>
> After a while and investing a little time, I've managed to run
> successfully the Postgres database backups using the BPIPE plugin. At least
> I think it worked.
>
> I've got 2 questions:
>
> 1 - The BPIPE Plugin is at the start of the "include" list in the
> "fileset" definition, but it runs at the end of the backup job., after all
> other regular file backups So, the log files from the pg_dump for each
> database are not backed up with the database backup files. Is there a way
> to get the BPIPE Plugin to run first?
>
Have you tried something like this?
FileSet {
Include {
Plugin ="bpipe: ..."
}
Include {
File = "/..."
}
}
2 - I've checked the log from the pg_dumps and they seem to run OK, BUT the
> there is no information about the size of the files in the bacula backup
> (-1 is the file length, when checking with Bacularis). Is this expected?
>
Yes, unfortunately the way how Bacula handles backup requires a plugin to
prepare a metadata for the file it wants to backup (save) before it could
save real data. It is not a problem for regular file data you can get from
any standard filesystem, as you can simply execute a stat(2) function to
get all standard metadata in advance. It won't work with the bpipe plugin
as the size of the data is unknown until all data is read. This is why
bpipe generated backup files got '-1' as a size.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-fd hangs in pipe during backup
Ah, so it is bug that happens when "honor nodump flag=yes" on Linux. I
couldn't repeat it because FreeBSD implements nodump differently.
You could work around it either by not using that option or by having another
options clause that sets "honor nodump flag=no" for the specific places where
you have pipes or sockets.
__Martin
> On Thu, 15 Feb 2024 09:14:18 -0500, Peter Sjoberg said:
>
> Sorry for late reply, had to let my normal backups finish up first.
>
> I did ask google how to run gdb and managed to get something out that I=20
> now attached.
> No symbols since I'm running the distro version insead of github.
> Did see that a new version is released - 13.0.4. Running some more=20
> backups now (copy to external drive) but after that I will update and=20
> see if anything changed.
>
> /ps
>
>
> On 2024-02-13 10:55, Martin Simmons wrote:
> > It works for me on FreeBSD with Bacula 15 from git.
> >
> > Can you attach gdb to the bacula-fd while it is running and issue the g=
> db
> > command:
> >
> > thread apply all bt
> >
> > Also, try running bacula-fd with -d 150 -dt -v -fP which will make it p=
> rint
> > the debug info to the terminal. Level 150 should show what it is doing=
> for
> > the fifo.
> >
> > __Martin
> >
> >
> >> On Tue, 13 Feb 2024 09:07:43 -0500, Peter Sjoberg said:
> >> On 2024-02-13 02:49, Eric Bollengier wrote:
> >>> Hello Peter,
> >>>
> >>> Without the ReadFifo directive, it's unlikely to cause a problem,
> >> Unlikely maybe but that is the problem and I can even reproduce it!
> >> My setup is based on ubuntu 22.04 LTS (was trying debian but align is
> >> broken there) using the community repo
> >>
> >> =C2=A0 debhttps://www.bacula.org/packages//debs/13.0.3 jam=
> my main
> >>
> >>> and the file daemon output is pretty clear, we are not at this file.
> >> The file daemon output shows last file that worked, not the file it is
> >> trying to backup.
> >>
> >> To reproduce I did
> >>
> >> *1 - create a fileset that backups just /tmp/debug*
> >>
> >> FileSet {
> >> Name =3D "debugfs2"
> >> Ignore FileSet Changes =3D yes
> >> Include {
> >> Options {
> >> signature=3DMD5
> >> honor nodump flag=3Dyes
> >> noatime=3Dyes
> >> keepatime =3D no
> >> sparse=3Dyes
> >> exclude =3D yes
> >> wild =3D *~
> >> wild =3D *.tmp
> >> }
> >> File =3D "/tmp/debug"
> >> }
> >> }
> >>
> >> *2 - create a pipe ("mkfifo random_pipe") and a plane file ("date
> >> >a_red_herring") in /tmp/debug*
> >>
> >> peters@quark:/tmp/debug$ find /tmp/debug/ -ls
> >> 11017 0 drwxr-xr-x 2 peters peters 80 Feb 13 08=
> :47 /tmp/debug/
> >> 11031 4 -rw-r--r-- 1 peters peters 32 Feb 13 08=
> :47 /tmp/debug/a_red_herring
> >> 11029 0 prw-r--r-- 1 peters peters 0 Feb 13 08=
> :46 /tmp/debug/random_pipe
> >> peters@quark:/tmp/debug$
> >>
> >> *3 - start a backup;
> >> *
> >>
> >> root@quark:~#echo run BackupQ_quark FileSet=3D"debugfs2" Level=3DFull =
> yes|bconsole
> >>
> >> *4 - confirm it hangs*
> >>
> >> root@quark:~# echo stat client=3Dquark-fd|bconsole #CLIENTSTAT
> >> Connecting to Director quark:9101
> >> 1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
> >> Enter a period to cancel a command.
> >> stat client=3Dquark-fd
> >> Connecting to Client quark-fd at quark:9102
> >>
> >> quark-fd Version: 13.0.3 (02 May 2023) x86_64-pc-linux-gnu-bacula-ent=
> erprise ubuntu 22.04
> >> Daemon started 12-Feb-24 23:55. Jobs: run=3D5 running=3D1.
> >>Heap: heap=3D856,064 smbytes=3D603,907 max_bytes=3D1,219,047 bufs=3D=
> 178 max_bufs=3D429
> >>Sizes: boffset_t=3D8 size_t=3D8 debug=3D0 trace=3D0 mode=3D0,0 bwli=
> mit=3D0kB/s
> >>Crypto: fips=3DN/A crypto=3DOpenSSL 3.0.2 15 Mar 2022
> >>Plugin: bpipe-fd.so(2)
> >>
> >> Running Jobs:
> >> JobId 315 Job BackupQ_quark.2024-02-13_08.48.07_46 is running.
> >> Full Backup Job started: 13-Feb-24 08:48
> >> Files=3D1 Bytes=3D40 AveBytes/sec=3D0 LastBytes/sec=3D2 Errors=3D=
> 0
> >> Bwlimit=3D0 ReadBytes=3D32
> >> Files: Examined=3D1 Backed up=3D1
> >> Processing file: /tmp/debug/a_red_herring
> >> SDReadSeqNo=3D8 fd=3D5 SDtls=3D1
> >> Director connected using TLS at: 13-Feb-24 08:55
> >> =3D=3D=3D=3D
> >>
> >> *5 - release the job by sending something to the pipe; *
> >>
> >> root@quark:~# echo >/tmp/debug/random_pipe
> >>
> >> *6 - confirm the job finished*
> >>
> >> root@quark:~# echo 'llist jobid=3D315'|bconsole
> >> Connecting to Director quark:9101
> >> 1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
> >> Enter a period to cancel a command.
> >> llist jobid=3D315
> >> Automatically selected Catalog: MyCatalog
> >> Using Catalog "MyCatalog"
> >> JobId: 315
> >>Job: BackupQ_quark.2024-02-13_08.48.07_46
> >> Name: BackupQ_quark
> >>PurgedFiles: 0
Re: [Bacula-users] bacula-fd hangs during backup
It works for me on FreeBSD with Bacula 15 from git.
Can you attach gdb to the bacula-fd while it is running and issue the gdb
command:
thread apply all bt
Also, try running bacula-fd with -d 150 -dt -v -fP which will make it print
the debug info to the terminal. Level 150 should show what it is doing for
the fifo.
__Martin
> On Tue, 13 Feb 2024 09:07:43 -0500, Peter Sjoberg said:
>
> On 2024-02-13 02:49, Eric Bollengier wrote:
> > Hello Peter,
> >
> > Without the ReadFifo directive, it's unlikely to cause a problem,
> Unlikely maybe but that is the problem and I can even reproduce it!
> My setup is based on ubuntu 22.04 LTS (was trying debian but align is
> broken there) using the community repo
>
> debhttps://www.bacula.org/packages//debs/13.0.3 jammy main
>
> > and the file daemon output is pretty clear, we are not at this file.
>
> The file daemon output shows last file that worked, not the file it is
> trying to backup.
>
> To reproduce I did
>
> *1 - create a fileset that backups just /tmp/debug*
>
> FileSet {
> Name = "debugfs2"
> Ignore FileSet Changes = yes
> Include {
>Options {
> signature=MD5
> honor nodump flag=yes
> noatime=yes
> keepatime = no
> sparse=yes
> exclude = yes
> wild = *~
> wild = *.tmp
> }
>File = "/tmp/debug"
>}
> }
>
> *2 - create a pipe ("mkfifo random_pipe") and a plane file ("date
> >a_red_herring") in /tmp/debug*
>
> peters@quark:/tmp/debug$ find /tmp/debug/ -ls
> 11017 0 drwxr-xr-x 2 peters peters 80 Feb 13 08:47
> /tmp/debug/
> 11031 4 -rw-r--r-- 1 peters peters 32 Feb 13 08:47
> /tmp/debug/a_red_herring
> 11029 0 prw-r--r-- 1 peters peters 0 Feb 13 08:46
> /tmp/debug/random_pipe
> peters@quark:/tmp/debug$
>
> *3 - start a backup;
> *
>
> root@quark:~#echo run BackupQ_quark FileSet="debugfs2" Level=Full yes|bconsole
>
> *4 - confirm it hangs*
>
> root@quark:~# echo stat client=quark-fd|bconsole #CLIENTSTAT
> Connecting to Director quark:9101
> 1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
> Enter a period to cancel a command.
> stat client=quark-fd
> Connecting to Client quark-fd at quark:9102
>
> quark-fd Version: 13.0.3 (02 May 2023) x86_64-pc-linux-gnu-bacula-enterprise
> ubuntu 22.04
> Daemon started 12-Feb-24 23:55. Jobs: run=5 running=1.
> Heap: heap=856,064 smbytes=603,907 max_bytes=1,219,047 bufs=178 max_bufs=429
> Sizes: boffset_t=8 size_t=8 debug=0 trace=0 mode=0,0 bwlimit=0kB/s
> Crypto: fips=N/A crypto=OpenSSL 3.0.2 15 Mar 2022
> Plugin: bpipe-fd.so(2)
>
> Running Jobs:
> JobId 315 Job BackupQ_quark.2024-02-13_08.48.07_46 is running.
> Full Backup Job started: 13-Feb-24 08:48
> Files=1 Bytes=40 AveBytes/sec=0 LastBytes/sec=2 Errors=0
> Bwlimit=0 ReadBytes=32
> Files: Examined=1 Backed up=1
> Processing file: /tmp/debug/a_red_herring
> SDReadSeqNo=8 fd=5 SDtls=1
> Director connected using TLS at: 13-Feb-24 08:55
>
>
> *5 - release the job by sending something to the pipe; *
>
> root@quark:~# echo >/tmp/debug/random_pipe
>
> *6 - confirm the job finished*
>
> root@quark:~# echo 'llist jobid=315'|bconsole
> Connecting to Director quark:9101
> 1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
> Enter a period to cancel a command.
> llist jobid=315
> Automatically selected Catalog: MyCatalog
> Using Catalog "MyCatalog"
> JobId: 315
> Job: BackupQ_quark.2024-02-13_08.48.07_46
> Name: BackupQ_quark
> PurgedFiles: 0
> Type: B
> Level: F
> ClientId: 32
>ClientName: quark-fd
> JobStatus: T
> SchedTime: 2024-02-13 08:48:07
> StartTime: 2024-02-13 08:48:09
> EndTime: 2024-02-13 08:56:40
> RealEndTime: 2024-02-13 08:56:40
> JobTDate: 1,707,832,600
> VolSessionId: 66
>VolSessionTime: 1,707,779,559
> JobFiles: 3
> JobBytes: 40
> ReadBytes: 32
> JobErrors: 0
> JobMissingFiles: 0
>PoolId: 2
> PoolName: File-Full
>PriorJobId: 0
> PriorJob:
> FileSetId: 7
> FileSet: debugfs2
> HasCache: 0
> Comment:
> Reviewed: 0
>
> You have messages.
> root@quark:~#
>
> /ps
>
> >
> > The problem can be somewhere else, and a good start is a "status dir"
> > and "status storage".
> >
> > Best Regards,
> > Eric
> >
> > On 2/13/24 06:23, Peter Sjoberg wrote:
> >>
> >> Actually, I think I found the root cause - a pipe!
> >>
> >> The file listed in the client status is not the problem but close to
> >> it is a pipe (maybe next file) and that is what causing the issue in
> >> all cases.
> >> I striped down the directory to just one file and it still fails
> >>
> >> root@defiant1:/home/debug# find .zoom -ls
> >> 23855106 4 drwx-- 4
Re: [Bacula-users] bacula-fd hangs during backup
> On Tue, 13 Feb 2024 12:03:50 +1100, Gary R Schmidt said: > > On 13/02/2024 11:08, Phil Stracchino wrote: > > On 2/12/24 18:35, Peter Sjoberg wrote: > >> Hi all > >> > >> I have a strange problem and (on my system) reproducible problem. When > >> I do backup of some directories then bacula-fd just hangs and never > >> complete. > >> The directories in question are not very strange and backup of them > >> works find with older versions of -fd > > > > > > Silly question: Do the problem directories contain named pipes or sockets? > > > Another possibly silly question: Are there any soft links that may cause > a loop? Soft links can't cause a loop because Bacula doesn't follow them. __Martin ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-fd hangs during backup
On 2024-02-13 02:49, Eric Bollengier wrote:
Hello Peter,
Without the ReadFifo directive, it's unlikely to cause a problem,
Unlikely maybe but that is the problem and I can even reproduce it!
My setup is based on ubuntu 22.04 LTS (was trying debian but align is
broken there) using the community repo
debhttps://www.bacula.org/packages//debs/13.0.3 jammy main
and the file daemon output is pretty clear, we are not at this file.
The file daemon output shows last file that worked, not the file it is
trying to backup.
To reproduce I did
*1 - create a fileset that backups just /tmp/debug*
FileSet {
Name = "debugfs2"
Ignore FileSet Changes = yes
Include {
Options {
signature=MD5
honor nodump flag=yes
noatime=yes
keepatime = no
sparse=yes
exclude = yes
wild = *~
wild = *.tmp
}
File = "/tmp/debug"
}
}
*2 - create a pipe ("mkfifo random_pipe") and a plane file ("date
>a_red_herring") in /tmp/debug*
peters@quark:/tmp/debug$ find /tmp/debug/ -ls
11017 0 drwxr-xr-x 2 peters peters 80 Feb 13 08:47
/tmp/debug/
11031 4 -rw-r--r-- 1 peters peters 32 Feb 13 08:47
/tmp/debug/a_red_herring
11029 0 prw-r--r-- 1 peters peters 0 Feb 13 08:46
/tmp/debug/random_pipe
peters@quark:/tmp/debug$
*3 - start a backup;
*
root@quark:~#echo run BackupQ_quark FileSet="debugfs2" Level=Full yes|bconsole
*4 - confirm it hangs*
root@quark:~# echo stat client=quark-fd|bconsole #CLIENTSTAT
Connecting to Director quark:9101
1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
Enter a period to cancel a command.
stat client=quark-fd
Connecting to Client quark-fd at quark:9102
quark-fd Version: 13.0.3 (02 May 2023) x86_64-pc-linux-gnu-bacula-enterprise
ubuntu 22.04
Daemon started 12-Feb-24 23:55. Jobs: run=5 running=1.
Heap: heap=856,064 smbytes=603,907 max_bytes=1,219,047 bufs=178 max_bufs=429
Sizes: boffset_t=8 size_t=8 debug=0 trace=0 mode=0,0 bwlimit=0kB/s
Crypto: fips=N/A crypto=OpenSSL 3.0.2 15 Mar 2022
Plugin: bpipe-fd.so(2)
Running Jobs:
JobId 315 Job BackupQ_quark.2024-02-13_08.48.07_46 is running.
Full Backup Job started: 13-Feb-24 08:48
Files=1 Bytes=40 AveBytes/sec=0 LastBytes/sec=2 Errors=0
Bwlimit=0 ReadBytes=32
Files: Examined=1 Backed up=1
Processing file: /tmp/debug/a_red_herring
SDReadSeqNo=8 fd=5 SDtls=1
Director connected using TLS at: 13-Feb-24 08:55
*5 - release the job by sending something to the pipe; *
root@quark:~# echo >/tmp/debug/random_pipe
*6 - confirm the job finished*
root@quark:~# echo 'llist jobid=315'|bconsole
Connecting to Director quark:9101
1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
Enter a period to cancel a command.
llist jobid=315
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
JobId: 315
Job: BackupQ_quark.2024-02-13_08.48.07_46
Name: BackupQ_quark
PurgedFiles: 0
Type: B
Level: F
ClientId: 32
ClientName: quark-fd
JobStatus: T
SchedTime: 2024-02-13 08:48:07
StartTime: 2024-02-13 08:48:09
EndTime: 2024-02-13 08:56:40
RealEndTime: 2024-02-13 08:56:40
JobTDate: 1,707,832,600
VolSessionId: 66
VolSessionTime: 1,707,779,559
JobFiles: 3
JobBytes: 40
ReadBytes: 32
JobErrors: 0
JobMissingFiles: 0
PoolId: 2
PoolName: File-Full
PriorJobId: 0
PriorJob:
FileSetId: 7
FileSet: debugfs2
HasCache: 0
Comment:
Reviewed: 0
You have messages.
root@quark:~#
/ps
The problem can be somewhere else, and a good start is a "status dir"
and "status storage".
Best Regards,
Eric
On 2/13/24 06:23, Peter Sjoberg wrote:
Actually, I think I found the root cause - a pipe!
The file listed in the client status is not the problem but close to
it is a pipe (maybe next file) and that is what causing the issue in
all cases.
I striped down the directory to just one file and it still fails
root@defiant1:/home/debug# find .zoom -ls
23855106 4 drwx-- 4 sys adm 4096 Feb 13
00:11 .zoom
23855107 4 drwxrwxr-x 2 ba ba 4096 Feb 13
00:11 .zoom/data
23855116 0 prw-r--r-- 1 ba ba 0 Mar 12
2021 .zoom/data/com.zoom.ipc.confapp__res
23855110 4 drwxrwxr-x 2 sys adm 4096 May 5
2020 .zoom/reports
root@defiant1:/home/debug#
and if I send something to the pipe the job finish ok and restoring
the job did include the pipe.
/ps
On 2024-02-12 23:36, Peter Sjoberg wrote:
In short - no and no, no special files
Also, while I haven't waited forever I have left it for several
hours so it's not like it's just some house cleaning left.
It does happen on different servers, sample below is my laptop.
=== My fileset:
FileSet {
Name =
Re: [Bacula-users] bacula-fd hangs during backup
Hello Peter,
Without the ReadFifo directive, it's unlikely to cause a problem,
and the file daemon output is pretty clear, we are not at this file.
The problem can be somewhere else, and a good start is a "status dir"
and "status storage".
Best Regards,
Eric
On 2/13/24 06:23, Peter Sjoberg wrote:
Actually, I think I found the root cause - a pipe!
The file listed in the client status is not the problem but close to it is a
pipe (maybe next file) and that is what causing the issue in all cases.
I striped down the directory to just one file and it still fails
root@defiant1:/home/debug# find .zoom -ls
23855106 4 drwx-- 4 sys adm 4096 Feb 13 00:11 .zoom
23855107 4 drwxrwxr-x 2 ba ba 4096 Feb 13 00:11
.zoom/data
23855116 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
.zoom/data/com.zoom.ipc.confapp__res
23855110 4 drwxrwxr-x 2 sys adm 4096 May 5 2020
.zoom/reports
root@defiant1:/home/debug#
and if I send something to the pipe the job finish ok and restoring the job did
include the pipe.
/ps
On 2024-02-12 23:36, Peter Sjoberg wrote:
In short - no and no, no special files
Also, while I haven't waited forever I have left it for several hours so it's
not like it's just some house cleaning left.
It does happen on different servers, sample below is my laptop.
=== My fileset:
FileSet {
Name = "debugfs2"
Ignore FileSet Changes = yes
Include {
Options {
signature=MD5
honor nodump flag=yes
noatime=yes
keepatime = no
sparse=yes
exclude = yes
wild = *~
wild = *.tmp
}
File = "/home/ba/.zoom"
}
}
= run command
echo run BackupQ_defiant1 FileSet="debugfs2" Level=Full yes|bconsole
= client status when hung
root@quark:~# echo stat client=defiant1-fd|bconsole #CLIENTSTAT
Connecting to Director quark:9101
1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
Enter a period to cancel a command.
stat client=defiant1-fd
Connecting to Client defiant1-fd at defiant1:9102
defiant1-fd Version: 13.0.3 (02 May 2023)
x86_64-pc-linux-gnu-bacula-enterprise ubuntu 22.04
Daemon started 12-Feb-24 23:22. Jobs: run=2 running=1.
Heap: heap=856,064 smbytes=606,583 max_bytes=794,675 bufs=188 max_bufs=203
Sizes: boffset_t=8 size_t=8 debug=0 trace=0 mode=0,0 bwlimit=0kB/s
Crypto: fips=N/A crypto=OpenSSL 3.0.2 15 Mar 2022
Plugin: bpipe-fd.so(2)
Running Jobs:
JobId 255 Job BackupQ_defiant1.2024-02-12_23.29.48_18 is running.
Full Backup Job started: 12-Feb-24 23:29
Files=2 Bytes=0 AveBytes/sec=0 LastBytes/sec=0 Errors=0
Bwlimit=0 ReadBytes=0
Files: Examined=2 Backed up=2
Processing file: /home/ba/.zoom/logs
SDReadSeqNo=8 fd=5 SDtls=1
Director connected using TLS at: 12-Feb-24 23:30
Content of that directory
root@defiant1:~# find /home/ba/.zoom -ls
15728688 4 drwx-- 7 ba ba 4096 Apr 28 2021
/home/ba/.zoom
16130303 4 drwx-- 2 ba ba 4096 Apr 28 2021
/home/ba/.zoom/screenCapture
16130301 4 drwxrwxr-x 2 ba ba 4096 Feb 12 18:47
/home/ba/.zoom/logs
16023538 4 drwxrwxr-x 4 ba ba 4096 Apr 28 2021
/home/ba/.zoom/data
16023540 0 prw-r--r-- 1 ba ba 0 May 5 2020
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__res
16023541 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
/home/ba/.zoom/data/com.zoom.ipc.confapp__req
16023539 0 prw-r--r-- 1 ba ba 0 Apr 28 2021
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__req
16130305 4 drwx-- 2 ba ba 4096 Mar 23 2021
/home/ba/.zoom/data/VirtualBkgnd_Custom
16131475 1564 -rw--- 1 ba ba 1597940 Mar 23 2021
/home/ba/.zoom/data/VirtualBkgnd_Custom/{ff6d8a57-d810-4dd2-bf1b-8366c063728f}
16023542 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
/home/ba/.zoom/data/com.zoom.ipc.confapp__res
16023545 52 -rw--- 1 ba ba 53248 Apr 28 2021
/home/ba/.zoom/data/zoomus.enc.db
16130304 4 drwx-- 2 ba ba 4096 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar
16131472 36 -rw--- 1 ba ba 36397 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_6c72761c1ad5cc6f485dce3966cbb705_100
16131473 4 -rw--- 1 ba ba 1020 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_9e6b3f01c5d33a2052c2681a42b4e659_100
16131474 4 -rw--- 1 ba ba 1020 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_e977cbed2632f5b11882e92e31f32516_100
16023544 8 -rw--- 1 ba ba 5120 Mar 23 2021
/home/ba/.zoom/data/zoommeeting.enc.db
16130302 4 drwxrwxr-x 2 ba ba 4096 May 5 2020
Re: [Bacula-users] bacula-fd hangs during backup
Actually, I think I found the root cause - a pipe!
The file listed in the client status is not the problem but close to it
is a pipe (maybe next file) and that is what causing the issue in all cases.
I striped down the directory to just one file and it still fails
root@defiant1:/home/debug# find .zoom -ls
23855106 4 drwx-- 4 sys adm 4096 Feb 13 00:11 .zoom
23855107 4 drwxrwxr-x 2 ba ba 4096 Feb 13 00:11
.zoom/data
23855116 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
.zoom/data/com.zoom.ipc.confapp__res
23855110 4 drwxrwxr-x 2 sys adm 4096 May 5 2020
.zoom/reports
root@defiant1:/home/debug#
and if I send something to the pipe the job finish ok and restoring the
job did include the pipe.
/ps
On 2024-02-12 23:36, Peter Sjoberg wrote:
In short - no and no, no special files
Also, while I haven't waited forever I have left it for several hours
so it's not like it's just some house cleaning left.
It does happen on different servers, sample below is my laptop.
=== My fileset:
FileSet {
Name = "debugfs2"
Ignore FileSet Changes = yes
Include {
Options {
signature=MD5
honor nodump flag=yes
noatime=yes
keepatime = no
sparse=yes
exclude = yes
wild = *~
wild = *.tmp
}
File = "/home/ba/.zoom"
}
}
= run command
echo run BackupQ_defiant1 FileSet="debugfs2" Level=Full yes|bconsole
= client status when hung
root@quark:~# echo stat client=defiant1-fd|bconsole #CLIENTSTAT
Connecting to Director quark:9101
1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
Enter a period to cancel a command.
stat client=defiant1-fd
Connecting to Client defiant1-fd at defiant1:9102
defiant1-fd Version: 13.0.3 (02 May 2023)
x86_64-pc-linux-gnu-bacula-enterprise ubuntu 22.04
Daemon started 12-Feb-24 23:22. Jobs: run=2 running=1.
Heap: heap=856,064 smbytes=606,583 max_bytes=794,675 bufs=188
max_bufs=203
Sizes: boffset_t=8 size_t=8 debug=0 trace=0 mode=0,0 bwlimit=0kB/s
Crypto: fips=N/A crypto=OpenSSL 3.0.2 15 Mar 2022
Plugin: bpipe-fd.so(2)
Running Jobs:
JobId 255 Job BackupQ_defiant1.2024-02-12_23.29.48_18 is running.
Full Backup Job started: 12-Feb-24 23:29
Files=2 Bytes=0 AveBytes/sec=0 LastBytes/sec=0 Errors=0
Bwlimit=0 ReadBytes=0
Files: Examined=2 Backed up=2
Processing file: /home/ba/.zoom/logs
SDReadSeqNo=8 fd=5 SDtls=1
Director connected using TLS at: 12-Feb-24 23:30
Content of that directory
root@defiant1:~# find /home/ba/.zoom -ls
15728688 4 drwx-- 7 ba ba 4096 Apr 28 2021
/home/ba/.zoom
16130303 4 drwx-- 2 ba ba 4096 Apr 28 2021
/home/ba/.zoom/screenCapture
16130301 4 drwxrwxr-x 2 ba ba 4096 Feb 12 18:47
/home/ba/.zoom/logs
16023538 4 drwxrwxr-x 4 ba ba 4096 Apr 28 2021
/home/ba/.zoom/data
16023540 0 prw-r--r-- 1 ba ba 0 May 5 2020
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__res
16023541 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
/home/ba/.zoom/data/com.zoom.ipc.confapp__req
16023539 0 prw-r--r-- 1 ba ba 0 Apr 28 2021
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__req
16130305 4 drwx-- 2 ba ba 4096 Mar 23 2021
/home/ba/.zoom/data/VirtualBkgnd_Custom
16131475 1564 -rw--- 1 ba ba1597940 Mar 23 2021
/home/ba/.zoom/data/VirtualBkgnd_Custom/{ff6d8a57-d810-4dd2-bf1b-8366c063728f}
16023542 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
/home/ba/.zoom/data/com.zoom.ipc.confapp__res
16023545 52 -rw--- 1 ba ba 53248 Apr 28 2021
/home/ba/.zoom/data/zoomus.enc.db
16130304 4 drwx-- 2 ba ba 4096 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar
16131472 36 -rw--- 1 ba ba 36397 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_6c72761c1ad5cc6f485dce3966cbb705_100
16131473 4 -rw--- 1 ba ba 1020 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_9e6b3f01c5d33a2052c2681a42b4e659_100
16131474 4 -rw--- 1 ba ba 1020 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_e977cbed2632f5b11882e92e31f32516_100
16023544 8 -rw--- 1 ba ba 5120 Mar 23 2021
/home/ba/.zoom/data/zoommeeting.enc.db
16130302 4 drwxrwxr-x 2 ba ba 4096 May 5 2020
/home/ba/.zoom/reports
16130300 4 drwx-- 2 ba ba 4096 Apr 28 2021
/home/ba/.zoom/im
root@defiant1:~#
/ps
On 2024-02-12 20:03, Gary R. Schmidt wrote:
On 13/02/2024 11:08, Phil Stracchino wrote:
On 2/12/24 18:35, Peter Sjoberg wrote:
Hi all
I have a strange problem and (on my
Re: [Bacula-users] bacula-fd hangs during backup
In short - no and no, no special files
Also, while I haven't waited forever I have left it for several hours so
it's not like it's just some house cleaning left.
It does happen on different servers, sample below is my laptop.
=== My fileset:
FileSet {
Name = "debugfs2"
Ignore FileSet Changes = yes
Include {
Options {
signature=MD5
honor nodump flag=yes
noatime=yes
keepatime = no
sparse=yes
exclude = yes
wild = *~
wild = *.tmp
}
File = "/home/ba/.zoom"
}
}
= run command
echo run BackupQ_defiant1 FileSet="debugfs2" Level=Full yes|bconsole
= client status when hung
root@quark:~# echo stat client=defiant1-fd|bconsole #CLIENTSTAT
Connecting to Director quark:9101
1000 OK: 10002 techwiz-dir Version: 13.0.3 (02 May 2023)
Enter a period to cancel a command.
stat client=defiant1-fd
Connecting to Client defiant1-fd at defiant1:9102
defiant1-fd Version: 13.0.3 (02 May 2023)
x86_64-pc-linux-gnu-bacula-enterprise ubuntu 22.04
Daemon started 12-Feb-24 23:22. Jobs: run=2 running=1.
Heap: heap=856,064 smbytes=606,583 max_bytes=794,675 bufs=188 max_bufs=203
Sizes: boffset_t=8 size_t=8 debug=0 trace=0 mode=0,0 bwlimit=0kB/s
Crypto: fips=N/A crypto=OpenSSL 3.0.2 15 Mar 2022
Plugin: bpipe-fd.so(2)
Running Jobs:
JobId 255 Job BackupQ_defiant1.2024-02-12_23.29.48_18 is running.
Full Backup Job started: 12-Feb-24 23:29
Files=2 Bytes=0 AveBytes/sec=0 LastBytes/sec=0 Errors=0
Bwlimit=0 ReadBytes=0
Files: Examined=2 Backed up=2
Processing file: /home/ba/.zoom/logs
SDReadSeqNo=8 fd=5 SDtls=1
Director connected using TLS at: 12-Feb-24 23:30
Content of that directory
root@defiant1:~# find /home/ba/.zoom -ls
15728688 4 drwx-- 7 ba ba 4096 Apr 28 2021
/home/ba/.zoom
16130303 4 drwx-- 2 ba ba 4096 Apr 28 2021
/home/ba/.zoom/screenCapture
16130301 4 drwxrwxr-x 2 ba ba 4096 Feb 12 18:47
/home/ba/.zoom/logs
16023538 4 drwxrwxr-x 4 ba ba 4096 Apr 28 2021
/home/ba/.zoom/data
16023540 0 prw-r--r-- 1 ba ba 0 May 5 2020
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__res
16023541 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
/home/ba/.zoom/data/com.zoom.ipc.confapp__req
16023539 0 prw-r--r-- 1 ba ba 0 Apr 28 2021
/home/ba/.zoom/data/com.zoom.ipc.assistantapp__req
16130305 4 drwx-- 2 ba ba 4096 Mar 23 2021
/home/ba/.zoom/data/VirtualBkgnd_Custom
16131475 1564 -rw--- 1 ba ba1597940 Mar 23 2021
/home/ba/.zoom/data/VirtualBkgnd_Custom/{ff6d8a57-d810-4dd2-bf1b-8366c063728f}
16023542 0 prw-r--r-- 1 ba ba 0 Mar 12 2021
/home/ba/.zoom/data/com.zoom.ipc.confapp__res
16023545 52 -rw--- 1 ba ba 53248 Apr 28 2021
/home/ba/.zoom/data/zoomus.enc.db
16130304 4 drwx-- 2 ba ba 4096 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar
16131472 36 -rw--- 1 ba ba 36397 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_6c72761c1ad5cc6f485dce3966cbb705_100
16131473 4 -rw--- 1 ba ba 1020 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_9e6b3f01c5d33a2052c2681a42b4e659_100
16131474 4 -rw--- 1 ba ba 1020 Mar 23 2021
/home/ba/.zoom/data/ConfAvatar/conf_avatar_e977cbed2632f5b11882e92e31f32516_100
16023544 8 -rw--- 1 ba ba 5120 Mar 23 2021
/home/ba/.zoom/data/zoommeeting.enc.db
16130302 4 drwxrwxr-x 2 ba ba 4096 May 5 2020
/home/ba/.zoom/reports
16130300 4 drwx-- 2 ba ba 4096 Apr 28 2021
/home/ba/.zoom/im
root@defiant1:~#
/ps
On 2024-02-12 20:03, Gary R. Schmidt wrote:
On 13/02/2024 11:08, Phil Stracchino wrote:
On 2/12/24 18:35, Peter Sjoberg wrote:
Hi all
I have a strange problem and (on my system) reproducible problem.
When I do backup of some directories then bacula-fd just hangs and
never complete.
The directories in question are not very strange and backup of them
works find with older versions of -fd
Silly question: Do the problem directories contain named pipes or
sockets?
Another possibly silly question: Are there any soft links that may
cause a loop?
Cheers,
Gary B-)
___
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-fd hangs during backup
On 13/02/2024 11:08, Phil Stracchino wrote: On 2/12/24 18:35, Peter Sjoberg wrote: Hi all I have a strange problem and (on my system) reproducible problem. When I do backup of some directories then bacula-fd just hangs and never complete. The directories in question are not very strange and backup of them works find with older versions of -fd Silly question: Do the problem directories contain named pipes or sockets? Another possibly silly question: Are there any soft links that may cause a loop? Cheers, GaryB-) ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-fd hangs during backup
On 2/12/24 18:35, Peter Sjoberg wrote: Hi all I have a strange problem and (on my system) reproducible problem. When I do backup of some directories then bacula-fd just hangs and never complete. The directories in question are not very strange and backup of them works find with older versions of -fd Silly question: Do the problem directories contain named pipes or sockets? -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula BPIPE help
Hi Eric, thanks for the reply. I've put BPIPE tests on hold, as I'm working with other priorities. I think I've followed the instructions, but the BPIBE plugin is not activated during the backup job - the few lines generated by the script are simply ignored and the pg_dump is not even started. Actually, I've just left all there, as the lines are ignored anyway - no errors, nothing happens. I'll try again later in March or April. In the meantime, running pg_dump to /tmp/ files (with the extra lines for the BPIPE) is working and I still can afford all the extra disk space used. Thanks again... I'll be back Cheers Ismael ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula BPIPE help
Hello Ismael, On 2/2/24 16:57, Ismael Matos wrote: Hello everyone, I've been spending time trying to make BPIPE work for me to take backup of a few postgres databases. So far, it seems, not enough time, so success is still away from me. I've already tried the FIFO file approach and gave up. Backup works perfectly when I use pg_dump to a /tmp/ directory, but I'd rather skip creating those intermediate files, as the databases are growing faster than expected. Normally, you can send the pg_dump into the bpipe plugin using more or less the same command. I believe some of you out there have been using the BPIPE approach with the postgres databases. May I ask you to send the relevant snippets of shell script and bacula-dir/bacula-fd config files? I think it's the right place to share experience and get help. Best Regards, Eric ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula GUI projects
Hello Alexey, Thank you for letting us know that it started working. Great to hear. For Baculum, it is important to have disabled E_DEPRECATED and E_STRICT errors. Rest of the error types can stay enabled and they are even desirable to keep enabled for seeing when something is going wrong. On Tue, 6 Feb 2024 at 16:30, Alexey Chistyakov wrote: > Hello Marcin > > I didn’t have a php.ini file for the baculum api. > I created a php.ini file for the api with the correct error_reporting and > it was fixed. > Thank you! > But perhaps I may have new questions. > Yes, I encourage you to do so. We are here to help :-) Best regards, Marcin Haba (gani) > пт, 2 февр. 2024 г. в 04:05, Marcin Haba : > >> Hello Alexey, >> >> Thanks for your tests and new tries. >> >> I think it is technically impossible that disabled E_DEPRECATED error >> reporting in PHP config works well on the Baculum level. Theoretically It >> could happen when error_reporting is enabled back in PHP code but this type >> of function does not exist in Baculum nor in any Baculum dependency. >> >> On the screenshot that you sent in the previous message we can see that >> these errors are displayed in the window on the main page which means it >> happens on the remote side. So maybe you are looking at the wrong host? In >> this case you need to disable E_DEPRECATED on the Baculum API host. The >> current API host is displayed on the top right side of the Baculum Web >> interface in a combobox. >> >> Good luck. >> >> Best regards, >> Marcin Haba (gani) >> >> On Thu, 1 Feb 2024 at 12:54, Alexey Chistyakov >> wrote: >> >>> Hello! >>> >>> My php.ini file for Bacula is the same as for the interpreter: >>> [image: Untitled.png] >>> >>> Addition, I checked the error_reporting var, this var is equal to 22527 >>> (E_ALL >>> & ~E_DEPRECATED & ~E_STRICT). >>> Settings in the php.ini file work, but Baculum shows deprecated errors. >>> >>> чт, 1 февр. 2024 г. в 03:59, Marcin Haba : >>> Hello Alexey, Running php --ini displays php.ini file used by PHP command line interpreter, not by PHP that executes Baculum scripts. In FreeBSD by default PHP is used as Apache module (mod_php). To see what php.ini file is used with Baculum, you can put to /usr/local/www/baculum/htdocs/index.php calling phpinfo() function and exit() one line after starting the PHP block. Something like: >>> phpinfo(); exit(); After that please load the Baculum page. You will be able to see all PHP settings used by the PHP Apache module. Best regards, Marcin Haba (gani) On Wed, 31 Jan 2024 at 16:29, Alexey Chistyakov wrote: > > Error_reporting option doesn't work. Same output. > I checked my php.ini file with "php --ini" comand and saw this output: >> >> Configuration File (php.ini) Path: /usr/local/etc >> Loaded Configuration File: /usr/local/etc/php.ini >> Scan for additional .ini files in: /usr/local/etc/php >> Additional .ini files parsed: /usr/local/etc/php/ext-18-session.ini, >> /usr/local/etc/php/ext-20-ctype.ini, >> /usr/local/etc/php/ext-20-curl.ini, >> /usr/local/etc/php/ext-20-dom.ini, >> /usr/local/etc/php/ext-20-ldap.ini, >> /usr/local/etc/php/ext-20-xml.ini > > > After adding the "error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT" line to the "/usr/local/etc/php.ini " file, nothing happened. > Apache restart command shows this output: >> >> [Wed Jan 31 18:16:04.065362 2024] [so:warn] [pid 2016] AH01574: module dir_module is already loaded, skipping >> [Wed Jan 31 18:16:04.083540 2024] [ssl:warn] [pid 2017] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache] >> [Wed Jan 31 18:16:04.087244 2024] [mpm_prefork:notice] [pid 2017] AH00163: Apache/2.4.58 (FreeBSD) PHP/8.1.27 OpenSSL/1.1.1t-freebsd mod_auth_kerb/5.4 configured -- resuming normal operations >> [Wed Jan 31 18:16:04.087707 2024] [core:notice] [pid 2017] AH00094: Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' > > > ср, 31 янв. 2024 г. в 15:59, Marcin Haba : >> >> Hello Alexey, >> >> Maybe you are looking in the wrong php.ini file. Sometimes there are >> few php.ini files that are used depending on how PHP is used. >> >> The messages that you showed us on screenshots are E_DEPRECATED type >> errors, so E_DEPRECATED works for PHP in your environment. >> >> For the lines from php.ini file, they are comment lines. Could you >> make sure that below you don't have error_reporting = XXX defined? >> >> Also please note that restart the web server in environments with >> PHP-FPM is not the same as restart PHP. >> >> I hope these tips will help in making it working. Good luck. >> >> Best regards, >> Marcin Haba (gani) >> >> On Wed,
Re: [Bacula-users] Bacula GUI projects
Hello Marcin I didn’t have a php.ini file for the baculum api. I created a php.ini file for the api with the correct error_reporting and it was fixed. Thank you! But perhaps I may have new questions. пт, 2 февр. 2024 г. в 04:05, Marcin Haba : > Hello Alexey, > > Thanks for your tests and new tries. > > I think it is technically impossible that disabled E_DEPRECATED error > reporting in PHP config works well on the Baculum level. Theoretically It > could happen when error_reporting is enabled back in PHP code but this type > of function does not exist in Baculum nor in any Baculum dependency. > > On the screenshot that you sent in the previous message we can see that > these errors are displayed in the window on the main page which means it > happens on the remote side. So maybe you are looking at the wrong host? In > this case you need to disable E_DEPRECATED on the Baculum API host. The > current API host is displayed on the top right side of the Baculum Web > interface in a combobox. > > Good luck. > > Best regards, > Marcin Haba (gani) > > On Thu, 1 Feb 2024 at 12:54, Alexey Chistyakov > wrote: > >> Hello! >> >> My php.ini file for Bacula is the same as for the interpreter: >> [image: Untitled.png] >> >> Addition, I checked the error_reporting var, this var is equal to 22527 >> (E_ALL >> & ~E_DEPRECATED & ~E_STRICT). >> Settings in the php.ini file work, but Baculum shows deprecated errors. >> >> чт, 1 февр. 2024 г. в 03:59, Marcin Haba : >> >>> Hello Alexey, >>> >>> Running php --ini displays php.ini file used by PHP command line >>> interpreter, not by PHP that executes Baculum scripts. In FreeBSD by >>> default PHP is used as Apache module (mod_php). >>> >>> To see what php.ini file is used with Baculum, you can put to >>> /usr/local/www/baculum/htdocs/index.php calling phpinfo() function and >>> exit() one line after starting the PHP block. Something like: >>> >>> >> phpinfo(); >>> exit(); >>> >>> After that please load the Baculum page. You will be able to see all >>> PHP settings used by the PHP Apache module. >>> >>> Best regards, >>> Marcin Haba (gani) >>> >>> On Wed, 31 Jan 2024 at 16:29, Alexey Chistyakov >>> wrote: >>> > >>> > Error_reporting option doesn't work. Same output. >>> > I checked my php.ini file with "php --ini" comand and saw this output: >>> >> >>> >> Configuration File (php.ini) Path: /usr/local/etc >>> >> Loaded Configuration File: /usr/local/etc/php.ini >>> >> Scan for additional .ini files in: /usr/local/etc/php >>> >> Additional .ini files parsed: >>> /usr/local/etc/php/ext-18-session.ini, >>> >> /usr/local/etc/php/ext-20-ctype.ini, >>> >> /usr/local/etc/php/ext-20-curl.ini, >>> >> /usr/local/etc/php/ext-20-dom.ini, >>> >> /usr/local/etc/php/ext-20-ldap.ini, >>> >> /usr/local/etc/php/ext-20-xml.ini >>> > >>> > >>> > After adding the "error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT" >>> line to the "/usr/local/etc/php.ini " file, nothing happened. >>> > Apache restart command shows this output: >>> >> >>> >> [Wed Jan 31 18:16:04.065362 2024] [so:warn] [pid 2016] AH01574: >>> module dir_module is already loaded, skipping >>> >> [Wed Jan 31 18:16:04.083540 2024] [ssl:warn] [pid 2017] AH01873: >>> Init: Session Cache is not configured [hint: SSLSessionCache] >>> >> [Wed Jan 31 18:16:04.087244 2024] [mpm_prefork:notice] [pid 2017] >>> AH00163: Apache/2.4.58 (FreeBSD) PHP/8.1.27 OpenSSL/1.1.1t-freebsd >>> mod_auth_kerb/5.4 configured -- resuming normal operations >>> >> [Wed Jan 31 18:16:04.087707 2024] [core:notice] [pid 2017] AH00094: >>> Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' >>> > >>> > >>> > ср, 31 янв. 2024 г. в 15:59, Marcin Haba : >>> >> >>> >> Hello Alexey, >>> >> >>> >> Maybe you are looking in the wrong php.ini file. Sometimes there are >>> >> few php.ini files that are used depending on how PHP is used. >>> >> >>> >> The messages that you showed us on screenshots are E_DEPRECATED type >>> >> errors, so E_DEPRECATED works for PHP in your environment. >>> >> >>> >> For the lines from php.ini file, they are comment lines. Could you >>> >> make sure that below you don't have error_reporting = XXX defined? >>> >> >>> >> Also please note that restart the web server in environments with >>> >> PHP-FPM is not the same as restart PHP. >>> >> >>> >> I hope these tips will help in making it working. Good luck. >>> >> >>> >> Best regards, >>> >> Marcin Haba (gani) >>> >> >>> >> On Wed, 31 Jan 2024 at 13:45, Alexey Chistyakov >>> >> wrote: >>> >> > >>> >> > Hello! >>> >> > >>> >> > I had the following options enabled by default: >>> >> > ; error_reporting >>> >> > ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED >>> >> > >>> >> > Enabling your options didn't change anything in the output. >>> >> > >>> >> > ср, 31 янв. 2024 г. в 04:52, Marcin Haba : >>> >> >> >>> >> >> Hello Alexey, >>> >> >> >>> >> >> It looks that you need to tune a bit the error reporting option in >>> your PHP configuration. Could you please try with this
Re: [Bacula-users] Bacula GUI projects
Hello Alexey, Thanks for your tests and new tries. I think it is technically impossible that disabled E_DEPRECATED error reporting in PHP config works well on the Baculum level. Theoretically It could happen when error_reporting is enabled back in PHP code but this type of function does not exist in Baculum nor in any Baculum dependency. On the screenshot that you sent in the previous message we can see that these errors are displayed in the window on the main page which means it happens on the remote side. So maybe you are looking at the wrong host? In this case you need to disable E_DEPRECATED on the Baculum API host. The current API host is displayed on the top right side of the Baculum Web interface in a combobox. Good luck. Best regards, Marcin Haba (gani) On Thu, 1 Feb 2024 at 12:54, Alexey Chistyakov wrote: > Hello! > > My php.ini file for Bacula is the same as for the interpreter: > [image: Untitled.png] > > Addition, I checked the error_reporting var, this var is equal to 22527 (E_ALL > & ~E_DEPRECATED & ~E_STRICT). > Settings in the php.ini file work, but Baculum shows deprecated errors. > > чт, 1 февр. 2024 г. в 03:59, Marcin Haba : > >> Hello Alexey, >> >> Running php --ini displays php.ini file used by PHP command line >> interpreter, not by PHP that executes Baculum scripts. In FreeBSD by >> default PHP is used as Apache module (mod_php). >> >> To see what php.ini file is used with Baculum, you can put to >> /usr/local/www/baculum/htdocs/index.php calling phpinfo() function and >> exit() one line after starting the PHP block. Something like: >> >> > phpinfo(); >> exit(); >> >> After that please load the Baculum page. You will be able to see all >> PHP settings used by the PHP Apache module. >> >> Best regards, >> Marcin Haba (gani) >> >> On Wed, 31 Jan 2024 at 16:29, Alexey Chistyakov >> wrote: >> > >> > Error_reporting option doesn't work. Same output. >> > I checked my php.ini file with "php --ini" comand and saw this output: >> >> >> >> Configuration File (php.ini) Path: /usr/local/etc >> >> Loaded Configuration File: /usr/local/etc/php.ini >> >> Scan for additional .ini files in: /usr/local/etc/php >> >> Additional .ini files parsed: >> /usr/local/etc/php/ext-18-session.ini, >> >> /usr/local/etc/php/ext-20-ctype.ini, >> >> /usr/local/etc/php/ext-20-curl.ini, >> >> /usr/local/etc/php/ext-20-dom.ini, >> >> /usr/local/etc/php/ext-20-ldap.ini, >> >> /usr/local/etc/php/ext-20-xml.ini >> > >> > >> > After adding the "error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT" >> line to the "/usr/local/etc/php.ini " file, nothing happened. >> > Apache restart command shows this output: >> >> >> >> [Wed Jan 31 18:16:04.065362 2024] [so:warn] [pid 2016] AH01574: module >> dir_module is already loaded, skipping >> >> [Wed Jan 31 18:16:04.083540 2024] [ssl:warn] [pid 2017] AH01873: Init: >> Session Cache is not configured [hint: SSLSessionCache] >> >> [Wed Jan 31 18:16:04.087244 2024] [mpm_prefork:notice] [pid 2017] >> AH00163: Apache/2.4.58 (FreeBSD) PHP/8.1.27 OpenSSL/1.1.1t-freebsd >> mod_auth_kerb/5.4 configured -- resuming normal operations >> >> [Wed Jan 31 18:16:04.087707 2024] [core:notice] [pid 2017] AH00094: >> Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' >> > >> > >> > ср, 31 янв. 2024 г. в 15:59, Marcin Haba : >> >> >> >> Hello Alexey, >> >> >> >> Maybe you are looking in the wrong php.ini file. Sometimes there are >> >> few php.ini files that are used depending on how PHP is used. >> >> >> >> The messages that you showed us on screenshots are E_DEPRECATED type >> >> errors, so E_DEPRECATED works for PHP in your environment. >> >> >> >> For the lines from php.ini file, they are comment lines. Could you >> >> make sure that below you don't have error_reporting = XXX defined? >> >> >> >> Also please note that restart the web server in environments with >> >> PHP-FPM is not the same as restart PHP. >> >> >> >> I hope these tips will help in making it working. Good luck. >> >> >> >> Best regards, >> >> Marcin Haba (gani) >> >> >> >> On Wed, 31 Jan 2024 at 13:45, Alexey Chistyakov >> >> wrote: >> >> > >> >> > Hello! >> >> > >> >> > I had the following options enabled by default: >> >> > ; error_reporting >> >> > ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED >> >> > >> >> > Enabling your options didn't change anything in the output. >> >> > >> >> > ср, 31 янв. 2024 г. в 04:52, Marcin Haba : >> >> >> >> >> >> Hello Alexey, >> >> >> >> >> >> It looks that you need to tune a bit the error reporting option in >> your PHP configuration. Could you please try with this settings in your >> php.ini file: >> >> >> >> >> >> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >> >> >> >> >> >> Good luck. >> >> >> >> >> >> Best regards, >> >> >> Marcin Haba (gani) >> >> >> >> >> >> On Tue, 30 Jan 2024 at 14:18, Alexey Chistyakov < >> typa.lesskee...@gmail.com> wrote: >> >> >>> >> >> >>> Hello! >> >> >>> >> >> >>> This is screens of my error: >> >> >>> >> >> >>> пт,
Re: [Bacula-users] Bacula GUI projects
Hello! My php.ini file for Bacula is the same as for the interpreter: [image: Untitled.png] Addition, I checked the error_reporting var, this var is equal to 22527 (E_ALL & ~E_DEPRECATED & ~E_STRICT). Settings in the php.ini file work, but Baculum shows deprecated errors. чт, 1 февр. 2024 г. в 03:59, Marcin Haba : > Hello Alexey, > > Running php --ini displays php.ini file used by PHP command line > interpreter, not by PHP that executes Baculum scripts. In FreeBSD by > default PHP is used as Apache module (mod_php). > > To see what php.ini file is used with Baculum, you can put to > /usr/local/www/baculum/htdocs/index.php calling phpinfo() function and > exit() one line after starting the PHP block. Something like: > > phpinfo(); > exit(); > > After that please load the Baculum page. You will be able to see all > PHP settings used by the PHP Apache module. > > Best regards, > Marcin Haba (gani) > > On Wed, 31 Jan 2024 at 16:29, Alexey Chistyakov > wrote: > > > > Error_reporting option doesn't work. Same output. > > I checked my php.ini file with "php --ini" comand and saw this output: > >> > >> Configuration File (php.ini) Path: /usr/local/etc > >> Loaded Configuration File: /usr/local/etc/php.ini > >> Scan for additional .ini files in: /usr/local/etc/php > >> Additional .ini files parsed: > /usr/local/etc/php/ext-18-session.ini, > >> /usr/local/etc/php/ext-20-ctype.ini, > >> /usr/local/etc/php/ext-20-curl.ini, > >> /usr/local/etc/php/ext-20-dom.ini, > >> /usr/local/etc/php/ext-20-ldap.ini, > >> /usr/local/etc/php/ext-20-xml.ini > > > > > > After adding the "error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT" > line to the "/usr/local/etc/php.ini " file, nothing happened. > > Apache restart command shows this output: > >> > >> [Wed Jan 31 18:16:04.065362 2024] [so:warn] [pid 2016] AH01574: module > dir_module is already loaded, skipping > >> [Wed Jan 31 18:16:04.083540 2024] [ssl:warn] [pid 2017] AH01873: Init: > Session Cache is not configured [hint: SSLSessionCache] > >> [Wed Jan 31 18:16:04.087244 2024] [mpm_prefork:notice] [pid 2017] > AH00163: Apache/2.4.58 (FreeBSD) PHP/8.1.27 OpenSSL/1.1.1t-freebsd > mod_auth_kerb/5.4 configured -- resuming normal operations > >> [Wed Jan 31 18:16:04.087707 2024] [core:notice] [pid 2017] AH00094: > Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' > > > > > > ср, 31 янв. 2024 г. в 15:59, Marcin Haba : > >> > >> Hello Alexey, > >> > >> Maybe you are looking in the wrong php.ini file. Sometimes there are > >> few php.ini files that are used depending on how PHP is used. > >> > >> The messages that you showed us on screenshots are E_DEPRECATED type > >> errors, so E_DEPRECATED works for PHP in your environment. > >> > >> For the lines from php.ini file, they are comment lines. Could you > >> make sure that below you don't have error_reporting = XXX defined? > >> > >> Also please note that restart the web server in environments with > >> PHP-FPM is not the same as restart PHP. > >> > >> I hope these tips will help in making it working. Good luck. > >> > >> Best regards, > >> Marcin Haba (gani) > >> > >> On Wed, 31 Jan 2024 at 13:45, Alexey Chistyakov > >> wrote: > >> > > >> > Hello! > >> > > >> > I had the following options enabled by default: > >> > ; error_reporting > >> > ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED > >> > > >> > Enabling your options didn't change anything in the output. > >> > > >> > ср, 31 янв. 2024 г. в 04:52, Marcin Haba : > >> >> > >> >> Hello Alexey, > >> >> > >> >> It looks that you need to tune a bit the error reporting option in > your PHP configuration. Could you please try with this settings in your > php.ini file: > >> >> > >> >> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT > >> >> > >> >> Good luck. > >> >> > >> >> Best regards, > >> >> Marcin Haba (gani) > >> >> > >> >> On Tue, 30 Jan 2024 at 14:18, Alexey Chistyakov < > typa.lesskee...@gmail.com> wrote: > >> >>> > >> >>> Hello! > >> >>> > >> >>> This is screens of my error: > >> >>> > >> >>> пт, 26 янв. 2024 г. в 22:44, Marcin Haba : > >> > >> Hello Alexey, > >> > >> Yes, I confirm that Baculum supports PHP 8 (8.0, 8.1 and 8.2). You > >> wrote that after switching to PHP 8.1 Baculum stopped building > >> correctly. Could I ask you about describing what it means, what > >> commands you type and what error you see? It will help us to > diagnose > >> where the problem that you experience is. > >> > >> For Bacularis, it is a more modern project than Baculum. Here you > can > >> see comparison between both web interfaces: > >> > >> > https://bacularis.app/news/3/36/Why-Bacularis/d,Bacularis%20news%20details > >> > >> For Bacula-Web, I always recommend this project. Davide does great > >> work providing this tool. > >> > >> Best regards, > >> Marcin Haba (gani) > >> > >> On Fri, 26 Jan 2024 at 13:33, Alexey Chistyakov > >> wrote: > >>
Re: [Bacula-users] Bacula GUI projects
Hello Alexey, Running php --ini displays php.ini file used by PHP command line interpreter, not by PHP that executes Baculum scripts. In FreeBSD by default PHP is used as Apache module (mod_php). To see what php.ini file is used with Baculum, you can put to /usr/local/www/baculum/htdocs/index.php calling phpinfo() function and exit() one line after starting the PHP block. Something like: wrote: > > Error_reporting option doesn't work. Same output. > I checked my php.ini file with "php --ini" comand and saw this output: >> >> Configuration File (php.ini) Path: /usr/local/etc >> Loaded Configuration File: /usr/local/etc/php.ini >> Scan for additional .ini files in: /usr/local/etc/php >> Additional .ini files parsed: /usr/local/etc/php/ext-18-session.ini, >> /usr/local/etc/php/ext-20-ctype.ini, >> /usr/local/etc/php/ext-20-curl.ini, >> /usr/local/etc/php/ext-20-dom.ini, >> /usr/local/etc/php/ext-20-ldap.ini, >> /usr/local/etc/php/ext-20-xml.ini > > > After adding the "error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT" line > to the "/usr/local/etc/php.ini " file, nothing happened. > Apache restart command shows this output: >> >> [Wed Jan 31 18:16:04.065362 2024] [so:warn] [pid 2016] AH01574: module >> dir_module is already loaded, skipping >> [Wed Jan 31 18:16:04.083540 2024] [ssl:warn] [pid 2017] AH01873: Init: >> Session Cache is not configured [hint: SSLSessionCache] >> [Wed Jan 31 18:16:04.087244 2024] [mpm_prefork:notice] [pid 2017] AH00163: >> Apache/2.4.58 (FreeBSD) PHP/8.1.27 OpenSSL/1.1.1t-freebsd mod_auth_kerb/5.4 >> configured -- resuming normal operations >> [Wed Jan 31 18:16:04.087707 2024] [core:notice] [pid 2017] AH00094: Command >> line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' > > > ср, 31 янв. 2024 г. в 15:59, Marcin Haba : >> >> Hello Alexey, >> >> Maybe you are looking in the wrong php.ini file. Sometimes there are >> few php.ini files that are used depending on how PHP is used. >> >> The messages that you showed us on screenshots are E_DEPRECATED type >> errors, so E_DEPRECATED works for PHP in your environment. >> >> For the lines from php.ini file, they are comment lines. Could you >> make sure that below you don't have error_reporting = XXX defined? >> >> Also please note that restart the web server in environments with >> PHP-FPM is not the same as restart PHP. >> >> I hope these tips will help in making it working. Good luck. >> >> Best regards, >> Marcin Haba (gani) >> >> On Wed, 31 Jan 2024 at 13:45, Alexey Chistyakov >> wrote: >> > >> > Hello! >> > >> > I had the following options enabled by default: >> > ; error_reporting >> > ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED >> > >> > Enabling your options didn't change anything in the output. >> > >> > ср, 31 янв. 2024 г. в 04:52, Marcin Haba : >> >> >> >> Hello Alexey, >> >> >> >> It looks that you need to tune a bit the error reporting option in your >> >> PHP configuration. Could you please try with this settings in your >> >> php.ini file: >> >> >> >> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >> >> >> >> Good luck. >> >> >> >> Best regards, >> >> Marcin Haba (gani) >> >> >> >> On Tue, 30 Jan 2024 at 14:18, Alexey Chistyakov >> >> wrote: >> >>> >> >>> Hello! >> >>> >> >>> This is screens of my error: >> >>> >> >>> пт, 26 янв. 2024 г. в 22:44, Marcin Haba : >> >> Hello Alexey, >> >> Yes, I confirm that Baculum supports PHP 8 (8.0, 8.1 and 8.2). You >> wrote that after switching to PHP 8.1 Baculum stopped building >> correctly. Could I ask you about describing what it means, what >> commands you type and what error you see? It will help us to diagnose >> where the problem that you experience is. >> >> For Bacularis, it is a more modern project than Baculum. Here you can >> see comparison between both web interfaces: >> >> https://bacularis.app/news/3/36/Why-Bacularis/d,Bacularis%20news%20details >> >> For Bacula-Web, I always recommend this project. Davide does great >> work providing this tool. >> >> Best regards, >> Marcin Haba (gani) >> >> On Fri, 26 Jan 2024 at 13:33, Alexey Chistyakov >> wrote: >> > >> > Hello everyone! >> > >> > I need help with baculum. >> > When I switched the php version from 80 to 81, the baculum package >> > from bacula 11.0.6 stopped building correctly. I wanted to update the >> > baculum version, but when I went to bacula sourceforge, I discovered >> > that the baculum version in makefale in all versions of the >> > bacula-gui archive is 9.6.0. But on the other hand, the patchnotes >> > for each bacula-gui version are supplemented, and at the moment the >> > latest version indicated in the patchnotes for baculum is equal to >> > the latest version of bacula (13.0.3). >> > Help me understand the baculum project is still alive, can it support >> > the latest
Re: [Bacula-users] Bacula: Backup OK -- with warnings - what warning?
On Tue, Jan 23, 2024, at 12:05 PM, Dan Langille wrote: > On Tue, Jan 23, 2024, at 11:16 AM, Martin Simmons wrote: >>> On Wed, 17 Jan 2024 09:54:23 -0500, Dan Langille said: >>> >>> On Fri, Dec 29, 2023, at 6:26 PM, Martin Simmons wrote: >>> >> On Fri, 29 Dec 2023 12:35:59 -0500, Dan Langille said: >>> >> >>> >> On Fri, Dec 29, 2023, at 12:10 PM, Martin Simmons wrote: >>> >> > 9.6.6 certainly displayed them for me, so I suspect a config issue. >>> >> > >>> >> > The messages would be omitted if !notsaved is in the Messages resource >>> >> > (but >>> >> > they would still be counted as "Non-fatal FD errors" which makes it >>> >> > add "with >>> >> > warnings" to the status). >>> >> > >>> >> > Maybe that changed in the client's bacula-fd.conf when you upgraded it? >>> >> >>> >> That's a good idea. >>> >> >>> >> [17:29 r730-01 dvl ~] % sudo ls -l /usr/local/etc/bacula/bacula-fd.conf >>> >> -rw-r- 1 root bacula 1497 Feb 25 2023 >>> >> /usr/local/etc/bacula/bacula-fd.conf >>> >> >>> >> [17:31 r730-01 dvl ~] % sudo md5 /usr/local/etc/bacula/bacula-fd.conf >>> >> MD5 (/usr/local/etc/bacula/bacula-fd.conf) = >>> >> e41a7d835766f563253c0a93418a1c61 >>> >> >>> >> >>> >> No change since February. >>> >> >>> >> Let's look at snapshots taken before Dec 25, the date of the job in >>> >> question. >>> >> >>> >> [17:32 r730-01 dvl /.zfs/snapshot] % cd >>> >> autosnap_2023-12-20_00:00:09_daily >>> >> [17:32 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % >>> >> sudo md5 usr/local/etc/bacula/bacula-fd.conf >>> >> MD5 (usr/local/etc/bacula/bacula-fd.conf) = >>> >> e41a7d835766f563253c0a93418a1c61 >>> >> >>> >> >>> >> I'm confident this file has not changed. >>> > >>> > Hmm, looking at src/lib/message.h, I suspect this change broke version >>> > compatibility in the message filtering infrastructure: >>> > >>> > commit fd926fc4671b054234fd3d5957bc05d303d87763 >>> > Author: Eric Bollengier >>> > Date: Fri Nov 6 21:27:05 2020 +0100 >>> > >>> > Fix unexpected connection event sent by the FD when the Message >>> > resource is not configured >>> > >>> > The problem is that the message types have been renumbered by moving >>> > M_EVENTS >>> > higher up, but messages sent to the Director from other daemons use the >>> > numeric value of the type so this is an incompatible change in the wire >>> > protocol. >>> > >>> > Dispite the date of this change, it looks like it first appeared in >>> > Bacula 13, >>> > so will cause problems if a Client < 13 sends a message to a Director >= >>> > 13 as >>> > in your case. >>> >>> That is concerning. It means backups may be incomplete and you don't know >>> it. >>> >>> This has happened at home, and today I noticed it at $WORK. >>> >>> It is no longer the case that versions can follow the rule: >>> >>> bacula-dir=bacula-sd>bacula-fd >>> >>> That rule has been in effect as long as I've been associated with the >>> project (about 20 years). Is there any possibility of this being fixed? Or >>> is this change irrevocable? >> >> The change to the numbering is probably irrevocable (changing it back would >> create a new set of incompatibilities), but some hack might be possible using >> the jcr->FDVersion. >> >> >>> If irrevocable, the users really need to be notified via an announcement. >>> Clients must be upgraded or the risk of data loss is present. In my case, >>> things I expected to be backed up were not being backed up. I could not >>> tell because the warnings were not presented to me. >> >> I suggest you create a bug report about it at >> https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues >> so it can tracked. > > And there we go: > https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues/2704 A fix has been committed. Expect a new release for 13.x and the fix will be in 15.x I have patched the FreeBSD port: https://cgit.freebsd.org/ports/commit/?id=3c57e9fa97a073c2911a6b3c76161376d3d185f6 -- Dan Langille d...@langille.org ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula GUI projects
Error_reporting option doesn't work. Same output. I checked my php.ini file with "php --ini" comand and saw this output: > > *Configuration File (php.ini) Path: /usr/local/etc* > *Loaded Configuration File: /usr/local/etc/php.ini* > *Scan for additional .ini files in: /usr/local/etc/php* > *Additional .ini files parsed: /usr/local/etc/php/ext-18-session.ini,* > */usr/local/etc/php/ext-20-ctype.ini,* > */usr/local/etc/php/ext-20-curl.ini,* > */usr/local/etc/php/ext-20-dom.ini,* > */usr/local/etc/php/ext-20-ldap.ini,**/usr/local/etc/php/ext-20-xml.ini* After adding the "error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT" line to the "*/usr/local/etc/php.ini* " file, nothing happened. Apache restart command shows this output: > [Wed Jan 31 18:16:04.065362 2024] [so:warn] [pid 2016] AH01574: module > dir_module is already loaded, skipping > [Wed Jan 31 18:16:04.083540 2024] [ssl:warn] [pid 2017] AH01873: Init: > Session Cache is not configured [hint: SSLSessionCache] > [Wed Jan 31 18:16:04.087244 2024] [mpm_prefork:notice] [pid 2017] AH00163: > Apache/2.4.58 (FreeBSD) PHP/8.1.27 OpenSSL/1.1.1t-freebsd mod_auth_kerb/5.4 > configured -- resuming normal operations > [Wed Jan 31 18:16:04.087707 2024] [core:notice] [pid 2017] AH00094: > Command line: '/usr/local/sbin/httpd -D NOHTTPACCEPT' > ср, 31 янв. 2024 г. в 15:59, Marcin Haba : > Hello Alexey, > > Maybe you are looking in the wrong php.ini file. Sometimes there are > few php.ini files that are used depending on how PHP is used. > > The messages that you showed us on screenshots are E_DEPRECATED type > errors, so E_DEPRECATED works for PHP in your environment. > > For the lines from php.ini file, they are comment lines. Could you > make sure that below you don't have error_reporting = XXX defined? > > Also please note that restart the web server in environments with > PHP-FPM is not the same as restart PHP. > > I hope these tips will help in making it working. Good luck. > > Best regards, > Marcin Haba (gani) > > On Wed, 31 Jan 2024 at 13:45, Alexey Chistyakov > wrote: > > > > Hello! > > > > I had the following options enabled by default: > > ; error_reporting > > ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED > > > > Enabling your options didn't change anything in the output. > > > > ср, 31 янв. 2024 г. в 04:52, Marcin Haba : > >> > >> Hello Alexey, > >> > >> It looks that you need to tune a bit the error reporting option in your > PHP configuration. Could you please try with this settings in your php.ini > file: > >> > >> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT > >> > >> Good luck. > >> > >> Best regards, > >> Marcin Haba (gani) > >> > >> On Tue, 30 Jan 2024 at 14:18, Alexey Chistyakov < > typa.lesskee...@gmail.com> wrote: > >>> > >>> Hello! > >>> > >>> This is screens of my error: > >>> > >>> пт, 26 янв. 2024 г. в 22:44, Marcin Haba : > > Hello Alexey, > > Yes, I confirm that Baculum supports PHP 8 (8.0, 8.1 and 8.2). You > wrote that after switching to PHP 8.1 Baculum stopped building > correctly. Could I ask you about describing what it means, what > commands you type and what error you see? It will help us to diagnose > where the problem that you experience is. > > For Bacularis, it is a more modern project than Baculum. Here you can > see comparison between both web interfaces: > > > https://bacularis.app/news/3/36/Why-Bacularis/d,Bacularis%20news%20details > > For Bacula-Web, I always recommend this project. Davide does great > work providing this tool. > > Best regards, > Marcin Haba (gani) > > On Fri, 26 Jan 2024 at 13:33, Alexey Chistyakov > wrote: > > > > Hello everyone! > > > > I need help with baculum. > > When I switched the php version from 80 to 81, the baculum package > from bacula 11.0.6 stopped building correctly. I wanted to update the > baculum version, but when I went to bacula sourceforge, I discovered that > the baculum version in makefale in all versions of the bacula-gui archive > is 9.6.0. But on the other hand, the patchnotes for each bacula-gui version > are supplemented, and at the moment the latest version indicated in the > patchnotes for baculum is equal to the latest version of bacula (13.0.3). > > Help me understand the baculum project is still alive, can it > support the latest versions of php? Or is it better to change it to > analogues baculum-web or bacularis? > > > > > > ___ > > Bacula-users mailing list > > Bacula-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > -- > "Greater love hath no man than this, that a man lay down his life for > his friends." Jesus Christ > > "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie > za przyjaciół swoich."
Re: [Bacula-users] Bacula GUI projects
Hello Alexey, Maybe you are looking in the wrong php.ini file. Sometimes there are few php.ini files that are used depending on how PHP is used. The messages that you showed us on screenshots are E_DEPRECATED type errors, so E_DEPRECATED works for PHP in your environment. For the lines from php.ini file, they are comment lines. Could you make sure that below you don't have error_reporting = XXX defined? Also please note that restart the web server in environments with PHP-FPM is not the same as restart PHP. I hope these tips will help in making it working. Good luck. Best regards, Marcin Haba (gani) On Wed, 31 Jan 2024 at 13:45, Alexey Chistyakov wrote: > > Hello! > > I had the following options enabled by default: > ; error_reporting > ; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED > > Enabling your options didn't change anything in the output. > > ср, 31 янв. 2024 г. в 04:52, Marcin Haba : >> >> Hello Alexey, >> >> It looks that you need to tune a bit the error reporting option in your PHP >> configuration. Could you please try with this settings in your php.ini file: >> >> error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT >> >> Good luck. >> >> Best regards, >> Marcin Haba (gani) >> >> On Tue, 30 Jan 2024 at 14:18, Alexey Chistyakov >> wrote: >>> >>> Hello! >>> >>> This is screens of my error: >>> >>> пт, 26 янв. 2024 г. в 22:44, Marcin Haba : Hello Alexey, Yes, I confirm that Baculum supports PHP 8 (8.0, 8.1 and 8.2). You wrote that after switching to PHP 8.1 Baculum stopped building correctly. Could I ask you about describing what it means, what commands you type and what error you see? It will help us to diagnose where the problem that you experience is. For Bacularis, it is a more modern project than Baculum. Here you can see comparison between both web interfaces: https://bacularis.app/news/3/36/Why-Bacularis/d,Bacularis%20news%20details For Bacula-Web, I always recommend this project. Davide does great work providing this tool. Best regards, Marcin Haba (gani) On Fri, 26 Jan 2024 at 13:33, Alexey Chistyakov wrote: > > Hello everyone! > > I need help with baculum. > When I switched the php version from 80 to 81, the baculum package from > bacula 11.0.6 stopped building correctly. I wanted to update the baculum > version, but when I went to bacula sourceforge, I discovered that the > baculum version in makefale in all versions of the bacula-gui archive is > 9.6.0. But on the other hand, the patchnotes for each bacula-gui version > are supplemented, and at the moment the latest version indicated in the > patchnotes for baculum is equal to the latest version of bacula (13.0.3). > Help me understand the baculum project is still alive, can it support > the latest versions of php? Or is it better to change it to analogues > baculum-web or bacularis? > > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- "Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus >> >> >> >> -- >> "Greater love hath no man than this, that a man lay down his life for his >> friends." Jesus Christ >> >> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za >> przyjaciół swoich." Jezus Chrystus -- "Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula GUI projects
Hello! I had the following options enabled by default: *; error_reporting* *; Default Value: E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED* Enabling your options didn't change anything in the output. ср, 31 янв. 2024 г. в 04:52, Marcin Haba : > Hello Alexey, > > It looks that you need to tune a bit the error reporting option in your > PHP configuration. Could you please try with this settings in your php.ini > file: > > error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT > > Good luck. > > Best regards, > Marcin Haba (gani) > > On Tue, 30 Jan 2024 at 14:18, Alexey Chistyakov > wrote: > >> Hello! >> >> This is screens of my error: >> >> пт, 26 янв. 2024 г. в 22:44, Marcin Haba : >> >>> Hello Alexey, >>> >>> Yes, I confirm that Baculum supports PHP 8 (8.0, 8.1 and 8.2). You >>> wrote that after switching to PHP 8.1 Baculum stopped building >>> correctly. Could I ask you about describing what it means, what >>> commands you type and what error you see? It will help us to diagnose >>> where the problem that you experience is. >>> >>> For Bacularis, it is a more modern project than Baculum. Here you can >>> see comparison between both web interfaces: >>> >>> >>> https://bacularis.app/news/3/36/Why-Bacularis/d,Bacularis%20news%20details >>> >>> For Bacula-Web, I always recommend this project. Davide does great >>> work providing this tool. >>> >>> Best regards, >>> Marcin Haba (gani) >>> >>> On Fri, 26 Jan 2024 at 13:33, Alexey Chistyakov >>> wrote: >>> > >>> > Hello everyone! >>> > >>> > I need help with baculum. >>> > When I switched the php version from 80 to 81, the baculum package >>> from bacula 11.0.6 stopped building correctly. I wanted to update the >>> baculum version, but when I went to bacula sourceforge, I discovered that >>> the baculum version in makefale in all versions of the bacula-gui archive >>> is 9.6.0. But on the other hand, the patchnotes for each bacula-gui version >>> are supplemented, and at the moment the latest version indicated in the >>> patchnotes for baculum is equal to the latest version of bacula (13.0.3). >>> > Help me understand the baculum project is still alive, can it support >>> the latest versions of php? Or is it better to change it to analogues >>> baculum-web or bacularis? >>> > >>> > >>> > ___ >>> > Bacula-users mailing list >>> > Bacula-users@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/bacula-users >>> >>> >>> >>> -- >>> "Greater love hath no man than this, that a man lay down his life for >>> his friends." Jesus Christ >>> >>> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie >>> za przyjaciół swoich." Jezus Chrystus >>> >> > > -- > "Greater love hath no man than this, that a man lay down his life for his > friends." Jesus Christ > > "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za > przyjaciół swoich." Jezus Chrystus > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula GUI projects
Hello Alexey, It looks that you need to tune a bit the error reporting option in your PHP configuration. Could you please try with this settings in your php.ini file: error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT Good luck. Best regards, Marcin Haba (gani) On Tue, 30 Jan 2024 at 14:18, Alexey Chistyakov wrote: > Hello! > > This is screens of my error: > > пт, 26 янв. 2024 г. в 22:44, Marcin Haba : > >> Hello Alexey, >> >> Yes, I confirm that Baculum supports PHP 8 (8.0, 8.1 and 8.2). You >> wrote that after switching to PHP 8.1 Baculum stopped building >> correctly. Could I ask you about describing what it means, what >> commands you type and what error you see? It will help us to diagnose >> where the problem that you experience is. >> >> For Bacularis, it is a more modern project than Baculum. Here you can >> see comparison between both web interfaces: >> >> https://bacularis.app/news/3/36/Why-Bacularis/d,Bacularis%20news%20details >> >> For Bacula-Web, I always recommend this project. Davide does great >> work providing this tool. >> >> Best regards, >> Marcin Haba (gani) >> >> On Fri, 26 Jan 2024 at 13:33, Alexey Chistyakov >> wrote: >> > >> > Hello everyone! >> > >> > I need help with baculum. >> > When I switched the php version from 80 to 81, the baculum package from >> bacula 11.0.6 stopped building correctly. I wanted to update the baculum >> version, but when I went to bacula sourceforge, I discovered that the >> baculum version in makefale in all versions of the bacula-gui archive is >> 9.6.0. But on the other hand, the patchnotes for each bacula-gui version >> are supplemented, and at the moment the latest version indicated in the >> patchnotes for baculum is equal to the latest version of bacula (13.0.3). >> > Help me understand the baculum project is still alive, can it support >> the latest versions of php? Or is it better to change it to analogues >> baculum-web or bacularis? >> > >> > >> > ___ >> > Bacula-users mailing list >> > Bacula-users@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/bacula-users >> >> >> >> -- >> "Greater love hath no man than this, that a man lay down his life for >> his friends." Jesus Christ >> >> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie >> za przyjaciół swoich." Jezus Chrystus >> > -- "Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula purges old jobs and I don't want it to do that
Hello, pon., 29 sty 2024 o 05:38 Rob Gerber napisał(a): > Radosław, thank you for your reply! Useful information. > > Regarding virtual full backups, because I am backing up via my single SAS > LTO8 drive, and because making a copy job requires an input device and an > output device, the information you shared leads me to expect that I am > unable to do virtual full backups with my Bacula community edition unless I > either upgrade to bacula enterprise edition > Bacula Enterprise Edition behaves the same for Tape devices. It does references with deduplication storage only. > or purchase another LTO8 drive. > In this case this is the only solution. > My tape changer does have room for such a drive, but the expense would > have to be justified to my client. > > I agree with you about manually purging volumes being dangerous and really > not advisable at all. The problem I'm facing is that I don't see a better > way to meet my client's needs otherwise. > > For reference, a full backup of this dataset takes 2-3 weeks at the > average tape write rate of about 170MB/s. > My very brief calculation (3 weeks with 170MB/s) shows 308448000 MB of backup storage, so about 300PB. Well in this case you should split your backups to multiple Tape drives to simply increase a throughput. Q: What tape library are you using? > For further reference, acquisition of the raw files is expensive, > requiring that professionals be paid to go to location and capture footage. > This places a value on the data, not counting the cost if we disappoint my > client's customer by losing the data for the shoots they arranged. > If part of your data never changes then you should backup it a limited number of times and use it as a long-term archive. So, I would go for defining multiple backup sets and not for virtual full or something. YMMV. best regards -- Radosław Korzeniewski rados...@korzeniewski.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula purges old jobs and I don't want it to do that
Radosław, thank you for your reply! Useful information. Regarding virtual full backups, because I am backing up via my single SAS LTO8 drive, and because making a copy job requires an input device and an output device, the information you shared leads me to expect that I am unable to do virtual full backups with my Bacula community edition unless I either upgrade to bacula enterprise edition or purchase another LTO8 drive. My tape changer does have room for such a drive, but the expense would have to be justified to my client. I agree with you about manually purging volumes being dangerous and really not advisable at all. The problem I'm facing is that I don't see a better way to meet my client's needs otherwise. Basically, I have two classes of data. The first (and easiest to handle) consists of project files and minor media files that the video editors use in their day to day work. These files are created, changed, and deleted all the time, and the total dataset is around 2TB. So, very manageable. I have a nightly backup of these files running on an automated schedule. I think I will discuss with the client and set a retention period around one year. The second dataset is the root of my issues here. This dataset consists of the video files captured by film crews on location. These files are filmed in 8k, and are very large. Dataset size is around 130TB, and is only expected to grow. The raw video files should be expected to NEVER change. Any edits are not applied to the original raws. Effectively, if bit rot or any edit has changed these files, then this is to be regarded as corruption. There are smaller downscaled versions of these files (called "proxies") that do change periodically. The proxies aren't as valuable or important as the original raw files, as they can always be regenerated from the raws. My goal regarding the media share is to back it up manually only, as media is added. Media will only be added when film crews have gone onsite and filmed new media, or when an editor has generated or regenerated proxies for that media. Because system performance is so important to the video editors, they don't want any backup action to impact their access speeds when working on the raws. Additionally, none of us want a partially completed file to be saved to LTO. As such, backups to this media share will be manually ran, as and when media is added or changes made. Because the proxies are stored right next to the raws, in the same share and folder tree, I don't have a good idea so far for detecting comparatively small changes and backing those up automatically. This leaves me with manual backup for this large dataset. My largest concern is that I don't want to lose the original backup of these essential raw files. I presume that the original backup was correct, and any subsequent re-backup of that original could include damage from bit rot or an unwanted change. My incremental backups will capture any wanted changes, but I don't want the original backup to be eliminated as I reuse tape. So, I plan to re-use tape very infrequently. I have been thinking about this problem and I think I might be able to confirm that data on the media share is valid and not corrupt by a combination of querying the bacula catalog for any file in the media share which has been backed up twice (modification date/size changed, so this was a valid filesystem operation), and then using a catalog to disk verify operation to hash files presently on disk and determine if any of them have changed due to bit rot. The only problem is that some raw files may have been deleted by video editors for valid reasons, but tracking such would be very difficult for purposes of validating if a deleted file was really unwanted or is missing. Reusing my tapes would then eliminate backups of the missing file. My client's stated goal for data retention of this media is 7 years. I think I could set the retention period for volumes to be around 7 years. I don't know if this period is doable between full backups. I imagine I'm going to have to adjust my expectations as I encounter more situations and learn. Meeting my customer's goals with bacula might involve buying a lot of tape, or mixing analysis of data on disk with analysis of catalog data to verify if discarding the old full backup would be safe. For reference, a full backup of this dataset takes 2-3 weeks at the average tape write rate of about 170MB/s. For further reference, acquisition of the raw files is expensive, requiring that professionals be paid to go to location and capture footage. This places a value on the data, not counting the cost if we disappoint my client's customer by losing the data for the shoots they arranged. Regards, Robert Gerber 402-237-8692 r...@craeon.net On Sat, Jan 27, 2024 at 7:45 AM Radosław Korzeniewski < rados...@korzeniewski.net> wrote: > Hello, > > wt., 7 lis 2023 o 21:57 Rob Gerber napisał(a): > >> To update this thread, I ultimately was able to
Re: [Bacula-users] Bacula purges old jobs and I don't want it to do that
Hello, wt., 7 lis 2023 o 21:57 Rob Gerber napisał(a): > To update this thread, I ultimately was able to avoid a bscan of all my > backed up media by restoring a backup of my catalog database. I have set > file, job, and volume retention to 1000 years. > Volume retention for 1000Y means you will never recycle your backups, so it will occupy all your available storage in the long term and you will be forced to manually delete oldest unused backups. IMVHO, doing manual backup recycle on will, is the last clever idea anyone can get. It is always better to set a real and usable volume retention and let the Bacula (enterprise class backup software) do this job for you. > Does a virtual full job strategy eliminate information about changed > files? ie, if the full backup captured fileA in one state, and if a later > incremental backup captured fileA in a different state, would the virtual > full consolidation process eliminate reference to the first backup of fileA? > Bacula Community does not maintain backups as data references, but always does a data copy on virtual full. You have to use Bacula Enterprise GED feature to get data references on virtual full. So, in your question virtual full consolidation process will use fileA state from incremental backup level and will copy it to the new virtual full backup job. > Lets assume that once a tape is full it, nor its associated files or jobs > will never be recycled, at least not for a 7 year period or so. > It doesn't matter. Virtual full will be a fully independent backup copy from all its ingredients. It will occupy a new backup space. > Incrementals forever could scale very badly in a larger enterprise, > Did you check BackupsToKeep functionality in Bacula? I have a different opinion on this matter. > but my objective is to protect a single set of files on a single system. > My largest concern is tapes going missing in an incremental chain, and for > that reason I'm probably going to need to do differential backups > periodically. > If you want to maintain a few hundred thousand incrementals chain because you've made a single full a 1000Y ago and did incrementals only, then this policy won't work by design. Incrementals forever means your backup client won't need to execute full backup (despite a first one) any more. It doesn't mean your backup chain only grows. It means backup software consolidates automatically full+incrementals chain for oldest backups or creates a full level from data already saved. Bacula uses a virtual full backup level for this. In this case you can set up a time base consolidation, i.e. once a week or number based consolidation, i.e. number of remaining incrementals. or I totally misunderstood your concerns here. R. -- Radosław Korzeniewski rados...@korzeniewski.net ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula GUI projects
Hello Alexey, Yes, I confirm that Baculum supports PHP 8 (8.0, 8.1 and 8.2). You wrote that after switching to PHP 8.1 Baculum stopped building correctly. Could I ask you about describing what it means, what commands you type and what error you see? It will help us to diagnose where the problem that you experience is. For Bacularis, it is a more modern project than Baculum. Here you can see comparison between both web interfaces: https://bacularis.app/news/3/36/Why-Bacularis/d,Bacularis%20news%20details For Bacula-Web, I always recommend this project. Davide does great work providing this tool. Best regards, Marcin Haba (gani) On Fri, 26 Jan 2024 at 13:33, Alexey Chistyakov wrote: > > Hello everyone! > > I need help with baculum. > When I switched the php version from 80 to 81, the baculum package from > bacula 11.0.6 stopped building correctly. I wanted to update the baculum > version, but when I went to bacula sourceforge, I discovered that the baculum > version in makefale in all versions of the bacula-gui archive is 9.6.0. But > on the other hand, the patchnotes for each bacula-gui version are > supplemented, and at the moment the latest version indicated in the > patchnotes for baculum is equal to the latest version of bacula (13.0.3). > Help me understand the baculum project is still alive, can it support the > latest versions of php? Or is it better to change it to analogues baculum-web > or bacularis? > > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- "Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula GUI projects
Hello Alexey, Probably by baculum-web you meant bacula-web right ? I know 3 main Bacuia GUI (web based) projects - Baculum - Bacularis - Bacula-Web (maintained by me) 2nd and 3rd projects does support recent versions of PHP (Bacula-Web for sure) I don't know if Baculum does support PHP 8.0 version or above. Then it depends ... If you're looking for a tool to manage and configure Bacula from a web UI, go to Bacularis or wait for an answer from the maintainer of Baculum. For the moment, Bacula-Web does only reporting and monitoring and does not allow you to restart job, run restore, etc. These features will come in a future release. Hope it helps Davide On Fri, Jan 26, 2024 at 1:32 PM Alexey Chistyakov wrote: > Hello everyone! > > I need help with baculum. > When I switched the php version from 80 to 81, the baculum package from > bacula 11.0.6 stopped building correctly. I wanted to update the baculum > version, but when I went to bacula sourceforge, I discovered that the > baculum version in makefale in all versions of the bacula-gui archive is > 9.6.0. But on the other hand, the patchnotes for each bacula-gui version > are supplemented, and at the moment the latest version indicated in the > patchnotes for baculum is equal to the latest version of bacula (13.0.3). > Help me understand the baculum project is still alive, can it support the > latest versions of php? Or is it better to change it to analogues > baculum-web or bacularis? > > > ___ > 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: Backup OK -- with warnings - what warning?
On Tue, Jan 23, 2024, at 11:16 AM, Martin Simmons wrote: >> On Wed, 17 Jan 2024 09:54:23 -0500, Dan Langille said: >> >> On Fri, Dec 29, 2023, at 6:26 PM, Martin Simmons wrote: >> >> On Fri, 29 Dec 2023 12:35:59 -0500, Dan Langille said: >> >> >> >> On Fri, Dec 29, 2023, at 12:10 PM, Martin Simmons wrote: >> >> > 9.6.6 certainly displayed them for me, so I suspect a config issue. >> >> > >> >> > The messages would be omitted if !notsaved is in the Messages resource >> >> > (but >> >> > they would still be counted as "Non-fatal FD errors" which makes it add >> >> > "with >> >> > warnings" to the status). >> >> > >> >> > Maybe that changed in the client's bacula-fd.conf when you upgraded it? >> >> >> >> That's a good idea. >> >> >> >> [17:29 r730-01 dvl ~] % sudo ls -l /usr/local/etc/bacula/bacula-fd.conf >> >> -rw-r- 1 root bacula 1497 Feb 25 2023 >> >> /usr/local/etc/bacula/bacula-fd.conf >> >> >> >> [17:31 r730-01 dvl ~] % sudo md5 /usr/local/etc/bacula/bacula-fd.conf >> >> MD5 (/usr/local/etc/bacula/bacula-fd.conf) = >> >> e41a7d835766f563253c0a93418a1c61 >> >> >> >> >> >> No change since February. >> >> >> >> Let's look at snapshots taken before Dec 25, the date of the job in >> >> question. >> >> >> >> [17:32 r730-01 dvl /.zfs/snapshot] % cd autosnap_2023-12-20_00:00:09_daily >> >> [17:32 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % >> >> sudo md5 usr/local/etc/bacula/bacula-fd.conf >> >> MD5 (usr/local/etc/bacula/bacula-fd.conf) = >> >> e41a7d835766f563253c0a93418a1c61 >> >> >> >> >> >> I'm confident this file has not changed. >> > >> > Hmm, looking at src/lib/message.h, I suspect this change broke version >> > compatibility in the message filtering infrastructure: >> > >> > commit fd926fc4671b054234fd3d5957bc05d303d87763 >> > Author: Eric Bollengier >> > Date: Fri Nov 6 21:27:05 2020 +0100 >> > >> > Fix unexpected connection event sent by the FD when the Message >> > resource is not configured >> > >> > The problem is that the message types have been renumbered by moving >> > M_EVENTS >> > higher up, but messages sent to the Director from other daemons use the >> > numeric value of the type so this is an incompatible change in the wire >> > protocol. >> > >> > Dispite the date of this change, it looks like it first appeared in Bacula >> > 13, >> > so will cause problems if a Client < 13 sends a message to a Director >= >> > 13 as >> > in your case. >> >> That is concerning. It means backups may be incomplete and you don't know it. >> >> This has happened at home, and today I noticed it at $WORK. >> >> It is no longer the case that versions can follow the rule: >> >> bacula-dir=bacula-sd>bacula-fd >> >> That rule has been in effect as long as I've been associated with the >> project (about 20 years). Is there any possibility of this being fixed? Or >> is this change irrevocable? > > The change to the numbering is probably irrevocable (changing it back would > create a new set of incompatibilities), but some hack might be possible using > the jcr->FDVersion. > > >> If irrevocable, the users really need to be notified via an announcement. >> Clients must be upgraded or the risk of data loss is present. In my case, >> things I expected to be backed up were not being backed up. I could not tell >> because the warnings were not presented to me. > > I suggest you create a bug report about it at > https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues > so it can tracked. And there we go: https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues/2704 -- Dan Langille d...@langille.org ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula: Backup OK -- with warnings - what warning?
> On Wed, 17 Jan 2024 09:54:23 -0500, Dan Langille said: > > On Fri, Dec 29, 2023, at 6:26 PM, Martin Simmons wrote: > >> On Fri, 29 Dec 2023 12:35:59 -0500, Dan Langille said: > >> > >> On Fri, Dec 29, 2023, at 12:10 PM, Martin Simmons wrote: > >> > 9.6.6 certainly displayed them for me, so I suspect a config issue. > >> > > >> > The messages would be omitted if !notsaved is in the Messages resource > >> > (but > >> > they would still be counted as "Non-fatal FD errors" which makes it add > >> > "with > >> > warnings" to the status). > >> > > >> > Maybe that changed in the client's bacula-fd.conf when you upgraded it? > >> > >> That's a good idea. > >> > >> [17:29 r730-01 dvl ~] % sudo ls -l /usr/local/etc/bacula/bacula-fd.conf > >> -rw-r- 1 root bacula 1497 Feb 25 2023 > >> /usr/local/etc/bacula/bacula-fd.conf > >> > >> [17:31 r730-01 dvl ~] % sudo md5 /usr/local/etc/bacula/bacula-fd.conf > >> MD5 (/usr/local/etc/bacula/bacula-fd.conf) = > >> e41a7d835766f563253c0a93418a1c61 > >> > >> > >> No change since February. > >> > >> Let's look at snapshots taken before Dec 25, the date of the job in > >> question. > >> > >> [17:32 r730-01 dvl /.zfs/snapshot] % cd autosnap_2023-12-20_00:00:09_daily > >> [17:32 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % > >> sudo md5 usr/local/etc/bacula/bacula-fd.conf > >> MD5 (usr/local/etc/bacula/bacula-fd.conf) = > >> e41a7d835766f563253c0a93418a1c61 > >> > >> > >> I'm confident this file has not changed. > > > > Hmm, looking at src/lib/message.h, I suspect this change broke version > > compatibility in the message filtering infrastructure: > > > > commit fd926fc4671b054234fd3d5957bc05d303d87763 > > Author: Eric Bollengier > > Date: Fri Nov 6 21:27:05 2020 +0100 > > > > Fix unexpected connection event sent by the FD when the Message > > resource is not configured > > > > The problem is that the message types have been renumbered by moving > > M_EVENTS > > higher up, but messages sent to the Director from other daemons use the > > numeric value of the type so this is an incompatible change in the wire > > protocol. > > > > Dispite the date of this change, it looks like it first appeared in Bacula > > 13, > > so will cause problems if a Client < 13 sends a message to a Director >= 13 > > as > > in your case. > > That is concerning. It means backups may be incomplete and you don't know it. > > This has happened at home, and today I noticed it at $WORK. > > It is no longer the case that versions can follow the rule: > > bacula-dir=bacula-sd>bacula-fd > > That rule has been in effect as long as I've been associated with the project > (about 20 years). Is there any possibility of this being fixed? Or is this > change irrevocable? The change to the numbering is probably irrevocable (changing it back would create a new set of incompatibilities), but some hack might be possible using the jcr->FDVersion. > If irrevocable, the users really need to be notified via an announcement. > Clients must be upgraded or the risk of data loss is present. In my case, > things I expected to be backed up were not being backed up. I could not tell > because the warnings were not presented to me. I suggest you create a bug report about it at https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues so it can tracked. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula: Backup OK -- with warnings - what warning?
On 18/01/2024 01:54, Dan Langille wrote: On Fri, Dec 29, 2023, at 6:26 PM, Martin Simmons wrote: On Fri, 29 Dec 2023 12:35:59 -0500, Dan Langille said: On Fri, Dec 29, 2023, at 12:10 PM, Martin Simmons wrote: 9.6.6 certainly displayed them for me, so I suspect a config issue. The messages would be omitted if !notsaved is in the Messages resource (but they would still be counted as "Non-fatal FD errors" which makes it add "with warnings" to the status). Maybe that changed in the client's bacula-fd.conf when you upgraded it? That's a good idea. [17:29 r730-01 dvl ~] % sudo ls -l /usr/local/etc/bacula/bacula-fd.conf -rw-r- 1 root bacula 1497 Feb 25 2023 /usr/local/etc/bacula/bacula-fd.conf [17:31 r730-01 dvl ~] % sudo md5 /usr/local/etc/bacula/bacula-fd.conf MD5 (/usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61 No change since February. Let's look at snapshots taken before Dec 25, the date of the job in question. [17:32 r730-01 dvl /.zfs/snapshot] % cd autosnap_2023-12-20_00:00:09_daily [17:32 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % sudo md5 usr/local/etc/bacula/bacula-fd.conf MD5 (usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61 I'm confident this file has not changed. Hmm, looking at src/lib/message.h, I suspect this change broke version compatibility in the message filtering infrastructure: commit fd926fc4671b054234fd3d5957bc05d303d87763 Author: Eric Bollengier Date: Fri Nov 6 21:27:05 2020 +0100 Fix unexpected connection event sent by the FD when the Message resource is not configured The problem is that the message types have been renumbered by moving M_EVENTS higher up, but messages sent to the Director from other daemons use the numeric value of the type so this is an incompatible change in the wire protocol. Dispite the date of this change, it looks like it first appeared in Bacula 13, so will cause problems if a Client < 13 sends a message to a Director >= 13 as in your case. That is concerning. It means backups may be incomplete and you don't know it. This has happened at home, and today I noticed it at $WORK. It is no longer the case that versions can follow the rule: bacula-dir=bacula-sd>bacula-fd That rule has been in effect as long as I've been associated with the project (about 20 years). Is there any possibility of this being fixed? Or is this change irrevocable? If irrevocable, the users really need to be notified via an announcement. Clients must be upgraded or the risk of data loss is present. In my case, things I expected to be backed up were not being backed up. I could not tell because the warnings were not presented to me. If true, this is a major WTF and Not Upgrading level screw-up. That ancient clients Just Worked has been one of the major strength of Bacula. Sigh. Cheers, GaryB-) ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula: Backup OK -- with warnings - what warning?
On Fri, Dec 29, 2023, at 6:26 PM, Martin Simmons wrote: >> On Fri, 29 Dec 2023 12:35:59 -0500, Dan Langille said: >> >> On Fri, Dec 29, 2023, at 12:10 PM, Martin Simmons wrote: >> > 9.6.6 certainly displayed them for me, so I suspect a config issue. >> > >> > The messages would be omitted if !notsaved is in the Messages resource (but >> > they would still be counted as "Non-fatal FD errors" which makes it add >> > "with >> > warnings" to the status). >> > >> > Maybe that changed in the client's bacula-fd.conf when you upgraded it? >> >> That's a good idea. >> >> [17:29 r730-01 dvl ~] % sudo ls -l /usr/local/etc/bacula/bacula-fd.conf >> -rw-r- 1 root bacula 1497 Feb 25 2023 >> /usr/local/etc/bacula/bacula-fd.conf >> >> [17:31 r730-01 dvl ~] % sudo md5 /usr/local/etc/bacula/bacula-fd.conf >> MD5 (/usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61 >> >> >> No change since February. >> >> Let's look at snapshots taken before Dec 25, the date of the job in question. >> >> [17:32 r730-01 dvl /.zfs/snapshot] % cd autosnap_2023-12-20_00:00:09_daily >> [17:32 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % sudo >> md5 usr/local/etc/bacula/bacula-fd.conf >> MD5 (usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61 >> >> >> I'm confident this file has not changed. > > Hmm, looking at src/lib/message.h, I suspect this change broke version > compatibility in the message filtering infrastructure: > > commit fd926fc4671b054234fd3d5957bc05d303d87763 > Author: Eric Bollengier > Date: Fri Nov 6 21:27:05 2020 +0100 > > Fix unexpected connection event sent by the FD when the Message > resource is not configured > > The problem is that the message types have been renumbered by moving M_EVENTS > higher up, but messages sent to the Director from other daemons use the > numeric value of the type so this is an incompatible change in the wire > protocol. > > Dispite the date of this change, it looks like it first appeared in Bacula 13, > so will cause problems if a Client < 13 sends a message to a Director >= 13 as > in your case. That is concerning. It means backups may be incomplete and you don't know it. This has happened at home, and today I noticed it at $WORK. It is no longer the case that versions can follow the rule: bacula-dir=bacula-sd>bacula-fd That rule has been in effect as long as I've been associated with the project (about 20 years). Is there any possibility of this being fixed? Or is this change irrevocable? If irrevocable, the users really need to be notified via an announcement. Clients must be upgraded or the risk of data loss is present. In my case, things I expected to be backed up were not being backed up. I could not tell because the warnings were not presented to me. -- Dan Langille d...@langille.org ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula S3 Cloud Folders?
Bump,
Anybody have an idea of using keys in the Bacula Cloud bucket name?
Levi Wilbert
HPC & Linux Systems Administrator
ARCC - Division of Research and Economic Development
Information Technology Ctr 226
1000 E. University Avenue, Laramie, WY 82071-200
From: Levi Wilbert
Sent: Thursday, December 21, 2023 5:06 PM
To: bacula-users@lists.sourceforge.net
Subject: [Bacula-users] Bacula S3 Cloud Folders?
◆ This message was sent from a non-UWYO address. Please exercise caution when
clicking links or opening attachments from external sources.
I'm using Bacula 13.0.3 w/ the libs3 driver. I have it working well, uploading
backups to a bucket on Ceph storage.
However, when Bacula uploads the backups from the local cache ("archive
directory") to Ceph, it uploads the volume w/ the part files inside directly in
the root of the bucket.
For example, say I have a backup I've just taken which is stored locally in the
cache in /backups/HOST001, which corresponds to this host's volume. In this
folder, I then have several cloud part files, "part.1", "part.2", "part.3", etc.
When Bacula uploads this particular backup to the cloud, it puts them directly
into :/HOST001.
Is there any way to specify an object prefix when uploading to the Cloud? So in
that way, I could do something like:
:/HOST_BACKUPS/HOST001/part.[1-n]
In the device definition, the "archive device" only specifies the local folder
to use as a cache, which doesn't impact where the backups go on the cloud.
I've tried specifying the prefix w/ the bucket name in the Cloud object
definition, like so:
Cloud {
Name = CEPH
Driver = "S3"
Host Name = "CEPH.MYDOMAIN.COM"
Bucket Name = "/"
<...>
}
...but this leads to the SD crashing after the director connects to it:
21-Dec 17:01 bacula-dev-dir JobId 359: Sending Accurate information to the FD.
21-Dec 17:01 bacula-dev-fd JobId 359: Error: openssl.c:81 TLS read/write
failure.: ERR=error:0A000126:SSL routines::unexpected eof while reading
21-Dec 17:01 bacula-dev-fd JobId 359: Fatal error: job.c:3492 Comm error with
SD. bad response to Append Data. ERR=Bad file descriptor
I really don't want to use a separate bucket for each and every host I backup,
but I would like to keep the host volumes organized in Ceph.
Anyone know how to accomplish this?
Levi Wilbert
HPC & Linux Systems Administrator
ARCC - Division of Research and Economic Development
Information Technology Ctr 226
1000 E. University Avenue, Laramie, WY 82071-200
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula: Backup OK -- with warnings - what warning?
> On Fri, 29 Dec 2023 12:35:59 -0500, Dan Langille said:
>
> On Fri, Dec 29, 2023, at 12:10 PM, Martin Simmons wrote:
> > 9.6.6 certainly displayed them for me, so I suspect a config issue.
> >
> > The messages would be omitted if !notsaved is in the Messages resource (but
> > they would still be counted as "Non-fatal FD errors" which makes it add
> > "with
> > warnings" to the status).
> >
> > Maybe that changed in the client's bacula-fd.conf when you upgraded it?
>
> That's a good idea.
>
> [17:29 r730-01 dvl ~] % sudo ls -l /usr/local/etc/bacula/bacula-fd.conf
> -rw-r- 1 root bacula 1497 Feb 25 2023
> /usr/local/etc/bacula/bacula-fd.conf
>
> [17:31 r730-01 dvl ~] % sudo md5 /usr/local/etc/bacula/bacula-fd.conf
> MD5 (/usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61
>
>
> No change since February.
>
> Let's look at snapshots taken before Dec 25, the date of the job in question.
>
> [17:32 r730-01 dvl /.zfs/snapshot] % cd autosnap_2023-12-20_00:00:09_daily
> [17:32 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % sudo
> md5 usr/local/etc/bacula/bacula-fd.conf
> MD5 (usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61
>
>
> I'm confident this file has not changed.
Hmm, looking at src/lib/message.h, I suspect this change broke version
compatibility in the message filtering infrastructure:
commit fd926fc4671b054234fd3d5957bc05d303d87763
Author: Eric Bollengier
Date: Fri Nov 6 21:27:05 2020 +0100
Fix unexpected connection event sent by the FD when the Message resource is
not configured
The problem is that the message types have been renumbered by moving M_EVENTS
higher up, but messages sent to the Director from other daemons use the
numeric value of the type so this is an incompatible change in the wire
protocol.
Dispite the date of this change, it looks like it first appeared in Bacula 13,
so will cause problems if a Client < 13 sends a message to a Director >= 13 as
in your case.
>
> Here is it, with some redactions:
>
> [17:33 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % sudo
> cat usr/local/etc/bacula/bacula-fd.conf
> Director {
> Name = bacula-dir
> Password = "[redacted]"
>
> TLS Enable = yes
> TLS Require = yes
> TLS Verify Peer = yes
>
> # Allow only the Director to connect
> TLS Allowed CN = "bacula.example.org"
> TLS CA Certificate File = /usr/local/etc/ssl/MyBigCA.crt
>
> TLS Certificate = /usr/local/etc/ssl/r730-01.int.unixathome.org.crt
> TLS Key =
> /usr/local/etc/ssl/r730-01.int.unixathome.org.nopassword.key
> }
>
> Director {
> Name = nagios-mon
> Password = "[redacted]"
> Monitor = yes
> }
>
> FileDaemon {
> Name= r730-01-fd
> FDAddress = 10.55.0.141
> FDport = 9102
> WorkingDirectory= /var/db/bacula
> Pid Directory = /var/run
> Maximum Concurrent Jobs = 20
>
> TLS Enable = yes
> TLS Require = yes
>
> TLS CA Certificate File = /usr/local/etc/ssl/MyBigCA.crt
>
> TLS Certificate = /usr/local/etc/ssl/r730-01.int.unixathome.org.crt
> TLS Key =
> /usr/local/etc/ssl/r730-01.int.unixathome.org.nopassword.key
> }
>
> # Send all messages except skipped files back to Director
> Messages {
> Name = Standard
> director = bacula-dir = all, !skipped, !restored
> }
>
>
> >
> > __Martin
> >
> >
> >> On Mon, 25 Dec 2023 07:06:58 -0500, Dan Langille said:
> >>
> >> Hello,
> >>
> >> This is more for advising others than looking for a fix.
> >>
> >> bacula9 client mentions warnings and does not list them.
> >> bacula13 client mentions the warnings.
> >>
> >> It turns out, the missing warnings are rather important to know. The ZFS
> >> datasets in question are jailed, and need a different path to the mount
> >> point. Checking the log file, the warnings do not appear there either.
> >>
> >> Here are examples of the problem.
> >>
> >> The following email is from bacula9-client: 9.6.7_3 on FreeBSD 14. The
> >> subject of this message from Bacula mentions warnings.
> >>
> >> No warnings are supplied.
> >>
> >> From: (Bacula) d...@langille.org
> >> Subject: Bacula: Backup OK -- with warnings of r730-01-fd Incremental
> >> Sender: bac...@bacula.int.unixathome.org
> >> To: [redacted]
> >> Date: Mon, 25 Dec 2023 03:09:16 + (UTC)
> >>
> >> 25-Dec 03:09 bacula-dir JobId 362083: Start Backup JobId 362083,
> >> Job=r730-01_snapshots.2023-12-25_03.05.00_24
> >> 25-Dec 03:09 bacula-dir JobId 362083: Connected to Storage
> >> "bacula-sd-04-IncrFile" at bacula-sd-04.int.unixathome.org:9103 with TLS
> >> 25-Dec 03:09 bacula-dir JobId 362083: There are no more Jobs associated
> >> with Volume "IncrAuto-04-14761". Marking it purged.
> >> 25-Dec 03:09 bacula-dir JobId 362083: All records pruned from Volume
> >> "IncrAuto-04-14761"; marking it "Purged"
> >> 25-Dec 03:09 bacula-dir JobId 362083: Recycled
Re: [Bacula-users] Bacula: Backup OK -- with warnings - what warning?
On Fri, Dec 29, 2023, at 12:10 PM, Martin Simmons wrote:
> 9.6.6 certainly displayed them for me, so I suspect a config issue.
>
> The messages would be omitted if !notsaved is in the Messages resource (but
> they would still be counted as "Non-fatal FD errors" which makes it add "with
> warnings" to the status).
>
> Maybe that changed in the client's bacula-fd.conf when you upgraded it?
That's a good idea.
[17:29 r730-01 dvl ~] % sudo ls -l /usr/local/etc/bacula/bacula-fd.conf
-rw-r- 1 root bacula 1497 Feb 25 2023 /usr/local/etc/bacula/bacula-fd.conf
[17:31 r730-01 dvl ~] % sudo md5 /usr/local/etc/bacula/bacula-fd.conf
MD5 (/usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61
No change since February.
Let's look at snapshots taken before Dec 25, the date of the job in question.
[17:32 r730-01 dvl /.zfs/snapshot] % cd autosnap_2023-12-20_00:00:09_daily
[17:32 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % sudo
md5 usr/local/etc/bacula/bacula-fd.conf
MD5 (usr/local/etc/bacula/bacula-fd.conf) = e41a7d835766f563253c0a93418a1c61
I'm confident this file has not changed.
Here is it, with some redactions:
[17:33 r730-01 dvl /.zfs/snapshot/autosnap_2023-12-20_00:00:09_daily] % sudo
cat usr/local/etc/bacula/bacula-fd.conf
Director {
Name = bacula-dir
Password = "[redacted]"
TLS Enable = yes
TLS Require = yes
TLS Verify Peer = yes
# Allow only the Director to connect
TLS Allowed CN = "bacula.example.org"
TLS CA Certificate File = /usr/local/etc/ssl/MyBigCA.crt
TLS Certificate = /usr/local/etc/ssl/r730-01.int.unixathome.org.crt
TLS Key = /usr/local/etc/ssl/r730-01.int.unixathome.org.nopassword.key
}
Director {
Name = nagios-mon
Password = "[redacted]"
Monitor = yes
}
FileDaemon {
Name= r730-01-fd
FDAddress = 10.55.0.141
FDport = 9102
WorkingDirectory= /var/db/bacula
Pid Directory = /var/run
Maximum Concurrent Jobs = 20
TLS Enable = yes
TLS Require = yes
TLS CA Certificate File = /usr/local/etc/ssl/MyBigCA.crt
TLS Certificate = /usr/local/etc/ssl/r730-01.int.unixathome.org.crt
TLS Key = /usr/local/etc/ssl/r730-01.int.unixathome.org.nopassword.key
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = bacula-dir = all, !skipped, !restored
}
>
> __Martin
>
>
>> On Mon, 25 Dec 2023 07:06:58 -0500, Dan Langille said:
>>
>> Hello,
>>
>> This is more for advising others than looking for a fix.
>>
>> bacula9 client mentions warnings and does not list them.
>> bacula13 client mentions the warnings.
>>
>> It turns out, the missing warnings are rather important to know. The ZFS
>> datasets in question are jailed, and need a different path to the mount
>> point. Checking the log file, the warnings do not appear there either.
>>
>> Here are examples of the problem.
>>
>> The following email is from bacula9-client: 9.6.7_3 on FreeBSD 14. The
>> subject of this message from Bacula mentions warnings.
>>
>> No warnings are supplied.
>>
>> From: (Bacula) d...@langille.org
>> Subject: Bacula: Backup OK -- with warnings of r730-01-fd Incremental
>> Sender: bac...@bacula.int.unixathome.org
>> To: [redacted]
>> Date: Mon, 25 Dec 2023 03:09:16 + (UTC)
>>
>> 25-Dec 03:09 bacula-dir JobId 362083: Start Backup JobId 362083,
>> Job=r730-01_snapshots.2023-12-25_03.05.00_24
>> 25-Dec 03:09 bacula-dir JobId 362083: Connected to Storage
>> "bacula-sd-04-IncrFile" at bacula-sd-04.int.unixathome.org:9103 with TLS
>> 25-Dec 03:09 bacula-dir JobId 362083: There are no more Jobs associated with
>> Volume "IncrAuto-04-14761". Marking it purged.
>> 25-Dec 03:09 bacula-dir JobId 362083: All records pruned from Volume
>> "IncrAuto-04-14761"; marking it "Purged"
>> 25-Dec 03:09 bacula-dir JobId 362083: Recycled volume "IncrAuto-04-14761"
>> 25-Dec 03:09 bacula-dir JobId 362083: Using Device "vDrive-IncrFile-5" to
>> write.
>> 25-Dec 03:09 bacula-dir JobId 362083: Connected to Client "r730-01-fd" at
>> r730-01.int.unixathome.org:9102 with TLS
>> 25-Dec 03:09 r730-01-fd JobId 362083: shell command: run ClientBeforeJob
>> "/usr/local/sbin/snapshots-for-backup.sh create"
>> 25-Dec 03:09 bacula-sd-04 JobId 362083: Recycled volume "IncrAuto-04-14761"
>> on File device "vDrive-IncrFile-5" (/usr/local/bacula/volumes/IncrFile), all
>> previous data lost.
>> 25-Dec 03:09 bacula-dir JobId 362083: Max Volume jobs=1 exceeded. Marking
>> Volume "IncrAuto-04-14761" as Used.
>> 25-Dec 03:09 r730-01-fd JobId 362083: shell command: run ClientAfterJob
>> "/usr/local/sbin/snapshots-for-backup.sh destroy"
>> 25-Dec 03:09 bacula-sd-04 JobId 362083: Elapsed time=00:00:14, Transfer
>> rate=32.35 K Bytes/second
>> 25-Dec 03:09 bacula-sd-04 JobId 362083: Sending spooled attrs to the
>> Director. Despooling 10,154 bytes ...
>> 25-Dec 03:09 bacula-dir JobId 362083: Bacula
Re: [Bacula-users] Bacula: Backup OK -- with warnings - what warning?
9.6.6 certainly displayed them for me, so I suspect a config issue. The messages would be omitted if !notsaved is in the Messages resource (but they would still be counted as "Non-fatal FD errors" which makes it add "with warnings" to the status). Maybe that changed in the client's bacula-fd.conf when you upgraded it? __Martin > On Mon, 25 Dec 2023 07:06:58 -0500, Dan Langille said: > > Hello, > > This is more for advising others than looking for a fix. > > bacula9 client mentions warnings and does not list them. > bacula13 client mentions the warnings. > > It turns out, the missing warnings are rather important to know. The ZFS > datasets in question are jailed, and need a different path to the mount > point. Checking the log file, the warnings do not appear there either. > > Here are examples of the problem. > > The following email is from bacula9-client: 9.6.7_3 on FreeBSD 14. The > subject of this message from Bacula mentions warnings. > > No warnings are supplied. > > From: (Bacula) d...@langille.org > Subject: Bacula: Backup OK -- with warnings of r730-01-fd Incremental > Sender: bac...@bacula.int.unixathome.org > To: [redacted] > Date: Mon, 25 Dec 2023 03:09:16 + (UTC) > > 25-Dec 03:09 bacula-dir JobId 362083: Start Backup JobId 362083, > Job=r730-01_snapshots.2023-12-25_03.05.00_24 > 25-Dec 03:09 bacula-dir JobId 362083: Connected to Storage > "bacula-sd-04-IncrFile" at bacula-sd-04.int.unixathome.org:9103 with TLS > 25-Dec 03:09 bacula-dir JobId 362083: There are no more Jobs associated with > Volume "IncrAuto-04-14761". Marking it purged. > 25-Dec 03:09 bacula-dir JobId 362083: All records pruned from Volume > "IncrAuto-04-14761"; marking it "Purged" > 25-Dec 03:09 bacula-dir JobId 362083: Recycled volume "IncrAuto-04-14761" > 25-Dec 03:09 bacula-dir JobId 362083: Using Device "vDrive-IncrFile-5" to > write. > 25-Dec 03:09 bacula-dir JobId 362083: Connected to Client "r730-01-fd" at > r730-01.int.unixathome.org:9102 with TLS > 25-Dec 03:09 r730-01-fd JobId 362083: shell command: run ClientBeforeJob > "/usr/local/sbin/snapshots-for-backup.sh create" > 25-Dec 03:09 bacula-sd-04 JobId 362083: Recycled volume "IncrAuto-04-14761" > on File device "vDrive-IncrFile-5" (/usr/local/bacula/volumes/IncrFile), all > previous data lost. > 25-Dec 03:09 bacula-dir JobId 362083: Max Volume jobs=1 exceeded. Marking > Volume "IncrAuto-04-14761" as Used. > 25-Dec 03:09 r730-01-fd JobId 362083: shell command: run ClientAfterJob > "/usr/local/sbin/snapshots-for-backup.sh destroy" > 25-Dec 03:09 bacula-sd-04 JobId 362083: Elapsed time=00:00:14, Transfer > rate=32.35 K Bytes/second > 25-Dec 03:09 bacula-sd-04 JobId 362083: Sending spooled attrs to the > Director. Despooling 10,154 bytes ... > 25-Dec 03:09 bacula-dir JobId 362083: Bacula bacula-dir 13.0.3 (02May23): > Build OS: amd64-portbld-freebsd14.0 freebsd 14.0-RELEASE-p1 > JobId: 362083 > Job:r730-01_snapshots.2023-12-25_03.05.00_24 > Backup Level: Incremental, since=2023-12-25 01:51:02 > Client: "r730-01-fd" 9.6.7 (10Dec20) > amd64-portbld-freebsd14.0,freebsd,14.0-RELEASE-p1 > FileSet:"r730-01 snapshots" 2023-12-25 01:30:49 > Pool: "IncrFile-04" (From Job IncPool override) > Catalog:"MyCatalog" (From Client resource) > Storage:"bacula-sd-04-IncrFile" (From Pool resource) > Scheduled time: 25-Dec-2023 03:05:00 > Start time: 25-Dec-2023 03:09:01 > End time: 25-Dec-2023 03:09:16 > Elapsed time: 15 secs > Priority: 10 > FD Files Written: 34 > SD Files Written: 34 > FD Bytes Written: 446,284 (446.2 KB) > SD Bytes Written: 453,016 (453.0 KB) > Rate: 29.8 KB/s > Software Compression: None > Comm Line Compression: 56.7% 2.3:1 > Snapshot/VSS: no > Encryption: no > Accurate: no > Volume name(s): IncrAuto-04-14761 > Volume Session Id: 52 > Volume Session Time:1703358455 > Last Volume Bytes: 455,013 (455.0 KB) > Non-fatal FD errors:3 > SD Errors: 0 > FD termination status: OK > SD termination status: OK > Termination:Backup OK -- with warnings > > 25-Dec 03:09 bacula-dir JobId 362083: Begin pruning Jobs older than 3 years . > 25-Dec 03:09 bacula-dir JobId 362083: No Jobs found to prune. > 25-Dec 03:09 bacula-dir JobId 362083: Begin pruning Files. > 25-Dec 03:09 bacula-dir JobId 362083: No Files found to prune. > 25-Dec 03:09 bacula-dir JobId 362083: End auto prune. > > > I replaced that bacula9-client: 9.6.7_3 with bacula13-client: 13.0.3 and > reran the job. > > The warnings are now listed. > > 25-Dec 11:53 bacula-dir JobId 362099: Start Backup JobId 362099, > Job=r730-01_snapshots.2023-12-25_11.52.58_26 > 25-Dec 11:53 bacula-dir
Re: [Bacula-users] Bacula-Web 9.2.0 release available
Hello, Thanks a lot for testing latest version. I’ll have a look as soon as possible and answer you directly in the bug report. Best regards Davide On Tue, 5 Dec 2023 at 22:42 wrote: > 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 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 copy from tape to tape
On 11/7/23 15:09, Rob Gerber wrote: > Well, now I know that whole thing is impossible. Simpler, that way. Thank you for letting me know! :) Welcome. could we have disk based backups managed by bacula on this larger NAS, with copies made to tape for onsite AND offsite storage? With the large NAS you have described, that is exactly what I would do. :) Just make sure it is mounted to the SD server via iSCSI, FC, or NFS and *not* CIFS. ;) Best regards, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula copy from tape to tape
On 11/7/23 17:09, Rob Gerber wrote: Technically I do have a huge NAS that dwarfs the production NAS in size (TrueNAS box). It was intended to store one movie, but the movie IT people massively over-estimated the amount of space we needed, so it never got used. It has occurred to me to use this TrueNAS device as a disk based volume storage solution. Can one make multiple copies of a reference volume? Ie, could we have disk based backups managed by bacula on this larger NAS, with copies made to tape for onsite AND offsite storage? You can absolutely to disk-to-disk-to-tape. It's not conceptually difficult to set up. (I'm doing disk to disk to removable ZFS disk pool, but ... same principle.) Maybe at that point we wouldn't need an onsite tape backup set. Disk based backup could speed up our initial backups substantially since both of these systems can operate at 10gbe speeds. Yeah, I love my disk-to-disk setup. Small restores are almost instant. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula copy from tape to tape
Well, now I know that whole thing is impossible. Simpler, that way. Thank you for letting me know! Technically I do have a huge NAS that dwarfs the production NAS in size (TrueNAS box). It was intended to store one movie, but the movie IT people massively over-estimated the amount of space we needed, so it never got used. It has occurred to me to use this TrueNAS device as a disk based volume storage solution. Can one make multiple copies of a reference volume? Ie, could we have disk based backups managed by bacula on this larger NAS, with copies made to tape for onsite AND offsite storage? Maybe at that point we wouldn't need an onsite tape backup set. Disk based backup could speed up our initial backups substantially since both of these systems can operate at 10gbe speeds. I have it set up with LTO as the primary backup solution because LTO infrastructure was the only backup plan until management suddenly demanded I build a massive NAS for housing this movie (then failed to use said NAS). Regards, Robert Gerber 402-237-8692 r...@craeon.net On Tue, Nov 7, 2023 at 3:28 PM Bill Arlofski via Bacula-users < bacula-users@lists.sourceforge.net> wrote: > On 11/7/23 13:04, Rob Gerber wrote: > > > > How difficult will it be to run copy jobs with only 1 LTO8 tape drive? > > Hello Rob, > > Sorry to be the bringer of bad news, but "difficult" is not the correct > word. > > The word you are looking for is "impossible" > > Bacula needs one read device and one write device for copy or migration > jobs. > > > Best regards, > Bill > > -- > Bill Arlofski > w...@protonmail.com > > ___ > 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 copy from tape to tape
On 11/7/23 13:04, Rob Gerber wrote: > How difficult will it be to run copy jobs with only 1 LTO8 tape drive? Hello Rob, Sorry to be the bringer of bad news, but "difficult" is not the correct word. The word you are looking for is "impossible" Bacula needs one read device and one write device for copy or migration jobs. Best regards, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula purges old jobs and I don't want it to do that
To update this thread, I ultimately was able to avoid a bscan of all my backed up media by restoring a backup of my catalog database. I have set file, job, and volume retention to 1000 years. Does a virtual full job strategy eliminate information about changed files? ie, if the full backup captured fileA in one state, and if a later incremental backup captured fileA in a different state, would the virtual full consolidation process eliminate reference to the first backup of fileA? Lets assume that once a tape is full it, nor its associated files or jobs will never be recycled, at least not for a 7 year period or so. Incrementals forever could scale very badly in a larger enterprise, but my objective is to protect a single set of files on a single system. My largest concern is tapes going missing in an incremental chain, and for that reason I'm probably going to need to do differential backups periodically. Regards, Robert Gerber 402-237-8692 r...@craeon.net On Fri, Aug 18, 2023 at 6:25 PM Phil Stracchino wrote: > On 8/18/23 17:24, Rob Gerber wrote: > > verification jobs. My guess is that bacula purged job records for some > > reason, possibly because they were older than 6 months. I have volume > > retention set to 1000 years, but maybe I need to add something for job > > retention? > > There are three retention periods you need to consider: > — Volume retention > — Job retention > — File retention > I suggest reading up on these in the documentation so that you > understand what each of them does. You can then adjust your pools, and > update all of your volumes, as necessary. > > > > Background info: I am backing up some large video files with LTO8 tape. > > My goal is to back these files up once, and do incremental backups to > > capture any new or changed files in the fileset. I do not expect > > the large media files to be changed once placed on the disk. Basically, > > I am using an "incrementals forever" strategy. > > > You might want to consider virtual-full jobs as a part of that strategy. > > > I am using bacula 13.x. We have a qualstar q24 autochanger. We use LTO 8 > > media. The fileset in question is around 70TiB. I welcome any assistance > > the list could provide. I'm sure it has to be something simple. > > > You could fix your retention and then scan the pruned volumes back in > using bscan. By the sound of it, that would take a while, but it's doable. > > What you need to keep in mind is that an "incrementals forever" strategy > is also a "Bacula database grows forever" strategy. That will > eventually become a problem. > > > -- >Phil Stracchino >Babylon Communications >ph...@caerllewys.net >p...@co.ordinate.org >Landline: +1.603.293.8485 >Mobile: +1.603.998.6958 > > > ___ > 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 recycling volumes it should not recycle
On 9/8/23 17:45, Rob Gerber wrote: Don't know if this helps, but file and job retention entries you put in the pool will override any such entries on the client resource. So afaik the last word on whether a job will be retained is the job retention entry on a pool resource. Maybe define job and file retention on the pool and see what happens, as part of troubleshooting. Thanks. I added "job retention" to each pool and this seems to work. Strangely I had never needed this in any other setup. I looked in the docs and it doesn't indicate any default. Actually, in the section titled "Client Resource", when talking about Job retention, it says: The Job retention period can actually be less than the value you specify here if you set the Volume Retention directive in the Pool resource to a smaller duration. Since I hadn't set it, I thought "Job retention" from client resource should have been authoritative. bye & Thanks av. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula packages repo for debian 12
I'm wondering that myself. I was able to install the 13.0.3 client on a debian 12 machine by downloading and installing the libssl1.1_1.1.1w-0+deb11u1_amd64.deb package and then the 13.0.3 debian 11 binaries run. Bob On 10/31/23 12:45 PM, Elias Pereira wrote: hello, Any idea when bacula 13 will be compatible with debian 12? -- Elias Pereira ___ 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 and BBR Protocol for Internet Backups, Packet Losses, Disconnections, etc.
On 10/2/23 09:47, hei...@bacula.com.br wrote: > I've enabled this now on all of my hosts, but I'm honestly not seeing a > clear improvement in network throughput so far. The improvements are more notiable if you introduce packet losses or networ interruptions. Ah, so, all the things I've done my best to eliminate from my network :) Well maybe it'll show up in other usages. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and BBR Protocol for Internet Backups, Packet Losses, Disconnections, etc.
Hello Phil, >> I would like to share this finding regarding the Linux BBR TCP >> congestion protocol and Bacula. >> I've tested in a few production environments, but I would like to have a >> broather population of >> results: >> https://www.bacula.lat/bacula-e-prototoclo-bbr-para-backups-via-internet-perdas-de-pacote-desconecoes-etc/?lang=en > I've enabled this now on all of my hosts, but I'm honestly not seeing a > clear improvement in network throughput so far. The improvements are more notiable if you introduce packet losses or networ interruptions. Rgds. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and BBR Protocol for Internet Backups, Packet Losses, Disconnections, etc.
On 9/14/23 18:08, hei...@bacula.com.br wrote: Hello Bacula Users, I would like to share this finding regarding the Linux BBR TCP congestion protocol and Bacula. I've tested in a few production environments, but I would like to have a broather population of results: https://www.bacula.lat/bacula-e-prototoclo-bbr-para-backups-via-internet-perdas-de-pacote-desconecoes-etc/?lang=en I've enabled this now on all of my hosts, but I'm honestly not seeing a clear improvement in network throughput so far. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula recycling volumes it should not recycle
Don't know if this helps, but file and job retention entries you put in the pool will override any such entries on the client resource. So afaik the last word on whether a job will be retained is the job retention entry on a pool resource. Maybe define job and file retention on the pool and see what happens, as part of troubleshooting. Robert Gerber 402-237-8692 r...@craeon.net On Fri, Sep 8, 2023, 3:16 AM Andrea Venturoli wrote: > On 9/7/23 21:33, Ana Emília M. Arruda wrote: > > Hello Andrea, > > Hello. > > > > > You have 1 job per volume and automatic pruning and recycling enabled. > > Correct. > > > > > If the only job in the volume is deleted from the Catalog, the recycling > > algorithm will detect it and the volume will be marked as Purged and > > reused. > > Again, I would expect so if the job was deleted, but why would it? > > > > > Is it happening with all volumes or only a few cases? > > Not sure about "all", but certainly for a lot of volumes. > > > > > Are you manually deleting jobs from the Catalog? > > No. > > The only unusual thing I'm doing is: > > echo "cloud prune AllFromPool Pool=Full" | /usr/local/sbin/bconsole > > echo "cloud prune AllFromPool Pool=Diff" | /usr/local/sbin/bconsole > > echo "cloud prune AllFromPool Pool=Inc" | /usr/local/sbin/bconsole > > echo "cloud prune AllFromPool Pool=Cat" | /usr/local/sbin/bconsole > > This was done after each catalog backup jobs (now I disabled it to see > if it was the culprit). > AFAICT, this should prune the "cache" not recycle the volume in the cloud. > > > Bye & Thanks > av. > > > ___ > 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 recycling volumes it should not recycle
On 9/7/23 21:33, Ana Emília M. Arruda wrote: Hello Andrea, Hello. You have 1 job per volume and automatic pruning and recycling enabled. Correct. If the only job in the volume is deleted from the Catalog, the recycling algorithm will detect it and the volume will be marked as Purged and reused. Again, I would expect so if the job was deleted, but why would it? Is it happening with all volumes or only a few cases? Not sure about "all", but certainly for a lot of volumes. Are you manually deleting jobs from the Catalog? No. The only unusual thing I'm doing is: echo "cloud prune AllFromPool Pool=Full" | /usr/local/sbin/bconsole echo "cloud prune AllFromPool Pool=Diff" | /usr/local/sbin/bconsole echo "cloud prune AllFromPool Pool=Inc" | /usr/local/sbin/bconsole echo "cloud prune AllFromPool Pool=Cat" | /usr/local/sbin/bconsole This was done after each catalog backup jobs (now I disabled it to see if it was the culprit). AFAICT, this should prune the "cache" not recycle the volume in the cloud. Bye & Thanks av. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula recycling volumes it should not recycle
Hello Andrea,
You have 1 job per volume and automatic pruning and recycling enabled. If
the only job in the volume is deleted from the Catalog, the recycling
algorithm will detect it and the volume will be marked as Purged and
reused. Is it happening with all volumes or only a few cases? Are you
manually deleting jobs from the Catalog?
Best,
Ana
El sáb., 2 sept. 2023 17:04, Andrea Venturoli escribió:
> On 9/2/23 12:30, Andrea Venturoli wrote:
> > Hello.
> >
> > I've been using bacula for a long long time, but I can't seem to
> > understand why, in a specific installation, volumes are recycled before
> > I think they should.
> > The only difference from several other installation, is the use of S3
> > cloud plugin.
> >
> > So:
> >
> > _ Bacula version is 11.0.6;
> >
> > _ excerpts from bacula-dir.conf:
> >> Client {
> >> Name=...
> >> Address=...
> >> FDPort = 9102
> >> Catalog = MyCatalog
> >> Password="..."
> >> File Retention=3 months
> >> Job Retention=3 months
> >> AutoPrune = yes
> >> }
> >> Pool {
> >> Name = Full
> >> Pool Type = Backup
> >> Recycle = yes
> >> AutoPrune = yes
> >> Maximum Volume Bytes = 50G
> >> Maximum Volume Jobs=1
> >> Label Format = "Full"
> >> Volume Retention=3 months
> >> Cache retention=31 days
> >> Action On Purge=Truncate
> >> }
> >
> > _ from the DB:
> >> select volumename,volretention/60/60/24 from media where volumename
> >> like 'Full%';
> >> volumename | ?column? +--
> >> Full0021 | 90
> >> Full0025 | 90
> >> Full0026 | 90
> >> Full0117 | 90
> >> Full0112 | 90
> >> Full0152 | 90
> >> Full0111 | 90
> >> Full0116 | 90
> >
> > _ yesterday I had:
> >> ls -lt|grep Full
> >> drwxr- 2 bacula bacula 512 Aug 30 22:45 Full0111
> >> drwxr- 2 bacula bacula 25600 Aug 8 22:45 Full0026
> >> drwxr- 2 bacula bacula 512 Aug 7 22:45 Full0025
> >> drwxr- 2 bacula bacula 21504 Aug 4 23:53 Full0116
> >> drwxr- 2 bacula bacula 512 Aug 4 22:33 Full0112
> >> drwxr- 2 bacula bacula 512 Jul 9 22:45 Full0021
> >> drwxr- 2 bacula bacula 25088 Jul 4 22:45 Full0152
> >> drwxr- 2 bacula bacula 512 Jul 3 22:45 Full0117
> >
> > _ today the volumes from July were recycled:
> >> ls -lt | grep Full
> >> drwxr- 2 bacula bacula 21504 Sep 1 23:55 Full0152
> >> drwxr- 2 bacula bacula 512 Sep 1 22:33 Full0117
> >> drwxr- 2 bacula bacula 512 Aug 30 22:45 Full0111
> >> drwxr- 2 bacula bacula 25600 Aug 8 22:45 Full0026
> >> drwxr- 2 bacula bacula 512 Aug 7 22:45 Full0025
> >> drwxr- 2 bacula bacula 21504 Aug 4 23:53 Full0116
> >> drwxr- 2 bacula bacula 512 Aug 4 22:33 Full0112
> >> drwxr- 2 bacula bacula 512 Jul 9 22:45 Full0021
> >
> >
> > Any idea why this happens?
>
> P.S.
> In the last job's mail I see:
> > There are no more Jobs associated with Volume "Full0117". Marking it
> purged.
>
> So it seems job retention is the problem, not volume retention.
>
>
>
> ___
> 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 recycling volumes it should not recycle
On 9/2/23 12:30, Andrea Venturoli wrote:
Hello.
I've been using bacula for a long long time, but I can't seem to
understand why, in a specific installation, volumes are recycled before
I think they should.
The only difference from several other installation, is the use of S3
cloud plugin.
So:
_ Bacula version is 11.0.6;
_ excerpts from bacula-dir.conf:
Client {
Name=...
Address=...
FDPort = 9102
Catalog = MyCatalog
Password="..."
File Retention=3 months
Job Retention=3 months
AutoPrune = yes
}
Pool {
Name = Full
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Maximum Volume Bytes = 50G
Maximum Volume Jobs=1
Label Format = "Full"
Volume Retention=3 months
Cache retention=31 days
Action On Purge=Truncate
}
_ from the DB:
select volumename,volretention/60/60/24 from media where volumename
like 'Full%';
volumename | ?column? +--
Full0021 | 90
Full0025 | 90
Full0026 | 90
Full0117 | 90
Full0112 | 90
Full0152 | 90
Full0111 | 90
Full0116 | 90
_ yesterday I had:
ls -lt|grep Full
drwxr- 2 bacula bacula 512 Aug 30 22:45 Full0111
drwxr- 2 bacula bacula 25600 Aug 8 22:45 Full0026
drwxr- 2 bacula bacula 512 Aug 7 22:45 Full0025
drwxr- 2 bacula bacula 21504 Aug 4 23:53 Full0116
drwxr- 2 bacula bacula 512 Aug 4 22:33 Full0112
drwxr- 2 bacula bacula 512 Jul 9 22:45 Full0021
drwxr- 2 bacula bacula 25088 Jul 4 22:45 Full0152
drwxr- 2 bacula bacula 512 Jul 3 22:45 Full0117
_ today the volumes from July were recycled:
ls -lt | grep Full
drwxr- 2 bacula bacula 21504 Sep 1 23:55 Full0152
drwxr- 2 bacula bacula 512 Sep 1 22:33 Full0117
drwxr- 2 bacula bacula 512 Aug 30 22:45 Full0111
drwxr- 2 bacula bacula 25600 Aug 8 22:45 Full0026
drwxr- 2 bacula bacula 512 Aug 7 22:45 Full0025
drwxr- 2 bacula bacula 21504 Aug 4 23:53 Full0116
drwxr- 2 bacula bacula 512 Aug 4 22:33 Full0112
drwxr- 2 bacula bacula 512 Jul 9 22:45 Full0021
Any idea why this happens?
P.S.
In the last job's mail I see:
There are no more Jobs associated with Volume "Full0117". Marking it purged.
So it seems job retention is the problem, not volume retention.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula backup snapshots from ZFS.
Hi Sergio, It’s possible to backup ZFS snapshots with Bacula community using the bpipe plugin. You can find an example set of wrapper scripts and fileset definition for this here: https://gist.github.com/optiz0r/68cb93172d72d2f8db48f7ab7b67c28e The bpipe plugin should be included with your community Bacula distribution. -- Regards, Ben Roberts From: Sergio Sa Sent: 29 August 2023 16:04 To: bacula-users@lists.sourceforge.net Subject: [Bacula-users] Bacula backup snapshots from ZFS. ** This is an external e-mail. Please treat attachments and links as potentially dangerous. ** hello Folks. I am working for a company which is interested to start using bacula in its environment. The company computer environment uses only Linux servers, and all secundary system is based on LXD/LXC virtualization under ZFS file sistem. My Main question is: Is possible to run ZFS snapshots backup using Bacula COMUNITY? I alreade read that there is a plugin for ZFS SNapshtos but where can I get a Documentation about it and download the respective plugin? Thanks. Sergio Sa. For details of how GSA uses your personal information, please see our Privacy Notice here: https://www.gsacapital.com/privacy-notice This email and any files transmitted with it contain confidential and proprietary information and is solely for the use of the intended recipient. If you are not the intended recipient please return the email to the sender and delete it from your computer and you must not use, disclose, distribute, copy, print or rely on this email or its contents. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. Any comments or statements made herein do not necessarily reflect those of GSA Capital. GSA Capital Partners LLP is authorised and regulated by the Financial Conduct Authority and is registered in England and Wales at Stratton House, 5 Stratton Street, London W1J 8LA, number OC309261. GSA Capital Services Limited is registered in England and Wales at the same address, number 5320529. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula purges old jobs and I don't want it to do that
On 8/18/23 17:24, Rob Gerber wrote: verification jobs. My guess is that bacula purged job records for some reason, possibly because they were older than 6 months. I have volume retention set to 1000 years, but maybe I need to add something for job retention? There are three retention periods you need to consider: — Volume retention — Job retention — File retention I suggest reading up on these in the documentation so that you understand what each of them does. You can then adjust your pools, and update all of your volumes, as necessary. Background info: I am backing up some large video files with LTO8 tape. My goal is to back these files up once, and do incremental backups to capture any new or changed files in the fileset. I do not expect the large media files to be changed once placed on the disk. Basically, I am using an "incrementals forever" strategy. You might want to consider virtual-full jobs as a part of that strategy. I am using bacula 13.x. We have a qualstar q24 autochanger. We use LTO 8 media. The fileset in question is around 70TiB. I welcome any assistance the list could provide. I'm sure it has to be something simple. You could fix your retention and then scan the pruned volumes back in using bscan. By the sound of it, that would take a while, but it's doable. What you need to keep in mind is that an "incrementals forever" strategy is also a "Bacula database grows forever" strategy. That will eventually become a problem. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
On 7/7/23 19:35, Phil Stracchino wrote: Then re-update it again, but BEFORE you rerun the updater, find update_mysql_tables_1021_to_1022 and change every instance of CREATE TABLE to CREATE TABLE IF NOT EXISTS. That will make sure that if something else is happening along the way that is creating those tables before they're expected, then the CREATE TABLE will be skipped, instead of the script failing. The *other* way you could do this is to insert a 'DROP TABLE IF EXISTS ;' before each 'CREATE TABLE (...' statement. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
On 7/7/23 19:26, Phil Stracchino wrote: On 7/7/23 18:59, Ken Mandelberg wrote: The suggestion below which is essentially to run "update_mysql_tables" manually instead of within the "apt-get install bacula-mysql" runs into the same issue. Specifically Update of Bacula MySQL tables from 16 to 1017 succeeded. Update of Bacula MySQL tables from 1017 to 1018 succeeded. Update of Bacula MySQL tables 1018 to 1019 succeeded. (From 16) Update of Bacula MySQL tables 1019 to 1020 succeeded. Update of Bacula MySQL tables 1020 to 1021 succeeded. ERROR 1050 (42S01) at line 3: Table 'TagJob' already exists Update of Bacula MySQL tables 1021 to 1022 failed. I also tried deleting TagJob and starting again, and then it just moves on to the next table that already exists. In fact I deleted all the Tag* tables, and that it complains about the Object table. I suspect it won't like any. Any ideas? OK, the short version is none of those TAG tables are SUPPOSED to exist before database version 1022. That PROBABLY means that you didn't fully clean from a prior update attempt. So what you can do is drop your bacula DB, *make sure it's empty*, restore it again from your backup copy, connect to mysql, do a SHOW TABLES FROM bacula; and check that the Tag... and Event tables are not in that list. Then re-update it again, but BEFORE you rerun the updater, find update_mysql_tables_1021_to_1022 and change every instance of CREATE TABLE to CREATE TABLE IF NOT EXISTS. That will make sure that if something else is happening along the way that is creating those tables before they're expected, then the CREATE TABLE will be skipped, instead of the script failing. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
On 7/7/23 18:59, Ken Mandelberg wrote: The suggestion below which is essentially to run "update_mysql_tables" manually instead of within the "apt-get install bacula-mysql" runs into the same issue. Specifically Update of Bacula MySQL tables from 16 to 1017 succeeded. Update of Bacula MySQL tables from 1017 to 1018 succeeded. Update of Bacula MySQL tables 1018 to 1019 succeeded. (From 16) Update of Bacula MySQL tables 1019 to 1020 succeeded. Update of Bacula MySQL tables 1020 to 1021 succeeded. ERROR 1050 (42S01) at line 3: Table 'TagJob' already exists Update of Bacula MySQL tables 1021 to 1022 failed. I also tried deleting TagJob and starting again, and then it just moves on to the next table that already exists. In fact I deleted all the Tag* tables, and that it complains about the Object table. I suspect it won't like any. Any ideas? Let me take a look at the current update_mysql_tables script and get back to you. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
The suggestion below which is essentially to run "update_mysql_tables" manually instead of within the "apt-get install bacula-mysql" runs into the same issue. Specifically Update of Bacula MySQL tables from 16 to 1017 succeeded. Update of Bacula MySQL tables from 1017 to 1018 succeeded. Update of Bacula MySQL tables 1018 to 1019 succeeded. (From 16) Update of Bacula MySQL tables 1019 to 1020 succeeded. Update of Bacula MySQL tables 1020 to 1021 succeeded. ERROR 1050 (42S01) at line 3: Table 'TagJob' already exists Update of Bacula MySQL tables 1021 to 1022 failed. I also tried deleting TagJob and starting again, and then it just moves on to the next table that already exists. In fact I deleted all the Tag* tables, and that it complains about the Object table. I suspect it won't like any. Any ideas? On 7/4/23 19:48, Ken Mandelberg wrote: > Another followup. One thing I learned, I need to remove all the Ubuntu > bundled bacula 9 packages before doing? the apt-get install bacula-mysql > for the Community 13 release, otherwise there are package conflicts. > > So after removing the old packages, apt-get install bacula-mysql tires > to install the mysql bacula database. It gets caught at > > mysql said: ERROR 1050 (42S01) at line 9: Table 'TagJob' already exists > > I imagine if I removed that table it would just get caught at the next one. > > Its not really clear on how to proceed preserving the current database 9 > info and letting 13 do the update job. OK, try this. - DUMP the bacula schema using mysqldump or your database dump tool of choice. (Personally I prefer mydumper.) - Then DROP the bacula DB. - Then run apt-get install bacula-mysql. - You MIGHT need to drop the bacula schema *again* at this point. to be safe. - Then RESTORE the bacula schema from your dump. - Then run update_mysql_tables to update your v9 Bacula DB to v13. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
On 7/4/23 19:48, Ken Mandelberg wrote: Another followup. One thing I learned, I need to remove all the Ubuntu bundled bacula 9 packages before doing the apt-get install bacula-mysql for the Community 13 release, otherwise there are package conflicts. So after removing the old packages, apt-get install bacula-mysql tires to install the mysql bacula database. It gets caught at mysql said: ERROR 1050 (42S01) at line 9: Table 'TagJob' already exists I imagine if I removed that table it would just get caught at the next one. Its not really clear on how to proceed preserving the current database 9 info and letting 13 do the update job. OK, try this. - DUMP the bacula schema using mysqldump or your database dump tool of choice. (Personally I prefer mydumper.) - Then DROP the bacula DB. - Then run apt-get install bacula-mysql. - You MIGHT need to drop the bacula schema *again* at this point. to be safe. - Then RESTORE the bacula schema from your dump. - Then run update_mysql_tables to update your v9 Bacula DB to v13. That should put you where you need to be, and in the worst case, you have a dump of your bacula DB in the event you have to roll back. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
Was the mysql database for bacula 9 used in production, and/or is there anything important in there? If not, remove the bacula 9 packages and dependencies with the apt purge command (look up syntax). This will remove configuration files and things created by the removed packages. Might have to reinstall the bacula 9 packages then do a purge, can't recall from when I encountered this. If you have production data in the bacula 9 catalog, or need to retain an unrelated mysql database better double check with the people here on this list. Robert Gerber 402-237-8692 r...@craeon.net On Tue, Jul 4, 2023, 6:49 PM Ken Mandelberg wrote: > Another followup. One thing I learned, I need to remove all the Ubuntu > bundled bacula 9 packages before doing the apt-get install bacula-mysql > for the Community 13 release, otherwise there are package conflicts. > > So after removing the old packages, apt-get install bacula-mysql tires > to install the mysql bacula database. It gets caught at > > mysql said: ERROR 1050 (42S01) at line 9: Table 'TagJob' already exists > > I imagine if I removed that table it would just get caught at the next one. > > Its not really clear on how to proceed preserving the current database 9 > info and letting 13 do the update job. > > > Ken Mandelberg wrote on 7/1/23 18:30: > > This is a followup of my previous posts. I'm doing an upgrade from > > Bacula 9 to 13 on Ubuntu 23.04. I realize there is no specific support > > for 23.04 so I'm making believe I'm on Jammy. > > > > I've gotten past the apt-key issue and sources are set up, and apt-get > > update has succeeded. Now my question is about the next step dealing > > with the fact that this is an upgrade of a working Bacula 9 > > installation. (Don't worry, its really on a test machine before I try > > it on a production machine). > > > > So I know I need to copy /etc/bacula to a safe place. Should I also > > delete it? > > > > I will also stop director , sd, and fd. and move those binaries out of > > the way. > > > > I'm running mysql. Should I do anything there to the existing bacula > > data base? > > > > Assuming the answers to those the next stop is > > > > apt-get install bacula-mysql > > > > I would assume I then copy back the saved /etc/bacula back in place > > and then start the new binaries. > > > > What about updating the mysql tables from 9 to 13? Where does that > > happen. > > > > Sorry for all the needy questions. This is my first time not using the > > bundled Ubuntu package support for Bacula which handles updates > > transparently. Debian/Ubuntu has no Bacula maintainer now. > > > > --- > > > > Side issue about the Documentation, what is the "concatenate" note > > about. It makes no sense, deb would just be an ignored comment. > > > > Complete example: > > > > #Bacula Community > > deb [arch=amd64] > > https://www.bacula.org/packages/abc123defxxxyyy/debs/13.0.1 xenial main > > > > Note 1: please concatenate the last 2 lines into 1 line. > > > > > > ___ > 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 Community Installation UPGRADE
Another followup. One thing I learned, I need to remove all the Ubuntu bundled bacula 9 packages before doing the apt-get install bacula-mysql for the Community 13 release, otherwise there are package conflicts. So after removing the old packages, apt-get install bacula-mysql tires to install the mysql bacula database. It gets caught at mysql said: ERROR 1050 (42S01) at line 9: Table 'TagJob' already exists I imagine if I removed that table it would just get caught at the next one. Its not really clear on how to proceed preserving the current database 9 info and letting 13 do the update job. Ken Mandelberg wrote on 7/1/23 18:30: This is a followup of my previous posts. I'm doing an upgrade from Bacula 9 to 13 on Ubuntu 23.04. I realize there is no specific support for 23.04 so I'm making believe I'm on Jammy. I've gotten past the apt-key issue and sources are set up, and apt-get update has succeeded. Now my question is about the next step dealing with the fact that this is an upgrade of a working Bacula 9 installation. (Don't worry, its really on a test machine before I try it on a production machine). So I know I need to copy /etc/bacula to a safe place. Should I also delete it? I will also stop director , sd, and fd. and move those binaries out of the way. I'm running mysql. Should I do anything there to the existing bacula data base? Assuming the answers to those the next stop is apt-get install bacula-mysql I would assume I then copy back the saved /etc/bacula back in place and then start the new binaries. What about updating the mysql tables from 9 to 13? Where does that happen. Sorry for all the needy questions. This is my first time not using the bundled Ubuntu package support for Bacula which handles updates transparently. Debian/Ubuntu has no Bacula maintainer now. --- Side issue about the Documentation, what is the "concatenate" note about. It makes no sense, deb would just be an ignored comment. Complete example: #Bacula Community deb [arch=amd64] https://www.bacula.org/packages/abc123defxxxyyy/debs/13.0.1 xenial main Note 1: please concatenate the last 2 lines into 1 line. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 13.0.x compatibility with 9.4 FD
Thank you Rob … From: Rob Gerber Sent: Friday, June 30, 2023 9:38 PM To: Yateen Shaligram Bhagat (Nokia) Cc: bacula-users Subject: Re: [Bacula-users] Bacula 13.0.x compatibility with 9.4 FD CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. This information is in the release notes. :) https://www.bacula.org/bacula-release-13-0-3/ "Compatibility: As always, both the Director and Storage daemon(s) must be upgraded at the same time. Any File daemon running on the same machine as a Director or Storage daemon must be of the same version. Older File Daemons should be compatible with the 13.0 Director and Storage daemons. There should be no need to upgrade older File Daemons." Robert Gerber 402-237-8692 r...@craeon.net<mailto:r...@craeon.net> On Fri, Jun 30, 2023, 6:28 AM Yateen Shaligram Bhagat (Nokia) mailto:yateen.shaligram_bha...@nokia.com>> wrote: Hi all, Can someone tell if Bacula 13.0.3 Dir & SD are compatible to Bacula 9.4 FD. Could not get this info from the the documentation. Thanks Yateen Bhagat ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net<mailto: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 Community Installation UPGRADE
Just as an FYI, bacula 13.x drops Ubuntu 18.04 support. If you still have some servers running that stick with 11. On July 1, 2023 6:30:59 PM EDT, Ken Mandelberg wrote: >This is a followup of my previous posts. I'm doing an upgrade from Bacula 9 to >13 on Ubuntu 23.04. I realize there is no specific support for 23.04 so I'm >making believe I'm on Jammy. > >I've gotten past the apt-key issue and sources are set up, and apt-get update >has succeeded. Now my question is about the next step dealing with the fact >that this is an upgrade of a working Bacula 9 installation. (Don't worry, its >really on a test machine before I try it on a production machine). > >So I know I need to copy /etc/bacula to a safe place. Should I also delete it? > >I will also stop director , sd, and fd. and move those binaries out of the way. > >I'm running mysql. Should I do anything there to the existing bacula data base? > >Assuming the answers to those the next stop is > >apt-get install bacula-mysql > >I would assume I then copy back the saved /etc/bacula back in place and then >start the new binaries. > >What about updating the mysql tables from 9 to 13? Where does that happen. > >Sorry for all the needy questions. This is my first time not using the bundled >Ubuntu package support for Bacula which handles updates transparently. >Debian/Ubuntu has no Bacula maintainer now. > >--- > >Side issue about the Documentation, what is the "concatenate" note about. It >makes no sense, deb would just be an ignored comment. > >Complete example: > >#Bacula Community >deb [arch=amd64] https://www.bacula.org/packages/abc123defxxxyyy/debs/13.0.1 >xenial main > >Note 1: please concatenate the last 2 lines into 1 line. > > > >___ >Bacula-users mailing list >Bacula-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/bacula-users -- Sent from my Android device with K-9 Mail. Please excuse my brevity.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
On 7/1/23 18:30, Ken Mandelberg wrote: So I know I need to copy /etc/bacula to a safe place. Should I also delete it? No, don't do that, you want to keep your configuration. If you delete those files you'll lose it. I will also stop director , sd, and fd. and move those binaries out of the way. You shouldn't need to do that. Let the package system handle it. I'm running mysql. Should I do anything there to the existing bacula data base? See below. Assuming the answers to those the next stop is apt-get install bacula-mysql I would assume I then copy back the saved /etc/bacula back in place and then start the new binaries. What about updating the mysql tables from 9 to 13? Where does that happen. The update-mysql-tables script will take care of that for you. Run it BEFORE you start the new Director. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation UPGRADE
Ken, No worries. I don't have them in front of me, but I'd bet the release notes for bacula 13.x (whatever your version will be, prob 13.0.3) will have info on any needed upgrade steps. I suspect it'll handle the database transparently based on my limited recollection from when I browsed said notes earlier this week. Find the relevant release notes on the bacula website. Regarding the concatenate note, I suspect they mean to make sure the text in brackets is all on one line with the URL. Robert Gerber 402-237-8692 r...@craeon.net On Sat, Jul 1, 2023, 5:53 PM Ken Mandelberg wrote: > This is a followup of my previous posts. I'm doing an upgrade from > Bacula 9 to 13 on Ubuntu 23.04. I realize there is no specific support > for 23.04 so I'm making believe I'm on Jammy. > > I've gotten past the apt-key issue and sources are set up, and apt-get > update has succeeded. Now my question is about the next step dealing > with the fact that this is an upgrade of a working Bacula 9 > installation. (Don't worry, its really on a test machine before I try it > on a production machine). > > So I know I need to copy /etc/bacula to a safe place. Should I also > delete it? > > I will also stop director , sd, and fd. and move those binaries out of > the way. > > I'm running mysql. Should I do anything there to the existing bacula > data base? > > Assuming the answers to those the next stop is > > apt-get install bacula-mysql > > I would assume I then copy back the saved /etc/bacula back in place and > then start the new binaries. > > What about updating the mysql tables from 9 to 13? Where does that happen. > > Sorry for all the needy questions. This is my first time not using the > bundled Ubuntu package support for Bacula which handles updates > transparently. Debian/Ubuntu has no Bacula maintainer now. > > --- > > Side issue about the Documentation, what is the "concatenate" note > about. It makes no sense, deb would just be an ignored comment. > > Complete example: > > #Bacula Community > deb [arch=amd64] > https://www.bacula.org/packages/abc123defxxxyyy/debs/13.0.1 xenial main > > Note 1: please concatenate the last 2 lines into 1 line. > > > > ___ > 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 Community Installation Guide
When I installed bacula 13.0.1 a year or two ago, they only had support for 20.x focal, not the more modern 22.x "whatever the name was". I selected the most modern available distro in the repo, which was focal. It worked ok. I believe you should be able to paste the provided repo link into a browser and see the available os versions as folders. I used the apt-key option in 22.x. not the best practice, but it's what I did. I'll have to fix it later. There isn't a super simple replacement for apt-key at this time. The general issue is that using apt-key grants global unmitigated trust to anyone publishing repos with that key, even if they push their code via someone else's repo servers. Bad guy could steal signing keys from repo A, subvert repo B servers or domain, then push malicious code to anyone who trusted repo B. The most upvoted answer in below stack exchange link gives some information on how to import a key using better practices that will limit the scope of your trust to the one repository the key is associated with. https://askubuntu.com/questions/1286545/what-commands-exactly-should-replace-the-deprecated-apt-key The most upvoted Unix stack exchange answer here talks about WHY this matters. https://unix.stackexchange.com/questions/463072/why-does-the-apt-key-man-page-advise-against-using-its-add-command/463140#463140 Robert Gerber 402-237-8692 r...@craeon.net On Fri, Jun 30, 2023, 1:12 PM Ken Mandelberg wrote: > Ben > > Thanks! I now have the access key. But going forward another obstacle. > I'm running Ubuntu 23.04 Lunar Lobster. apt-key is no longer available > in 23.04, so the instructions for importing the GPG key won't work. Is > there a simple replacement, and maybe more to the point if I get as far > as "deb" for sources, will the repository have Lunar? > > Ken > > Ben Tyger wrote on 6/30/23 12:12: > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bacula.org%2Fbacula-binary-package-download%2F=05%7C01%7Ckm%40mathcs.emory.edu%7Ccf20eaabdd404567f8b408db7984dc88%7Ce004fb9cb0a4424fbcd0322606d5df38%7C0%7C0%7C638237383887165100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=b2k4q2Gw622smLbaKpbvlZxcoxkF6eHlaCqk%2BsJgdag%3D=0 > > is the registration page. You'll get the specialized link in your e-mail > > > > > > On 6/30/23 11:27, Ken Mandelberg wrote: > >> I'm trying to use the instructions for installing the community > >> version binaries for Bacula 13 on Ubuntu. > >> > >> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bacula.org%2Fwhitepapers%2FCommunityInstallationGuide.pdf=05%7C01%7Ckm%40mathcs.emory.edu%7Ccf20eaabdd404567f8b408db7984dc88%7Ce004fb9cb0a4424fbcd0322606d5df38%7C0%7C0%7C638237383887165100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=Q5lKyN1XZJHNI%2BjCJJU66hC6uSC7qSRzqOQsf4661hM%3D=0 > >> > >> > >> To get started setting up sources for apt it needs an access key > >> which it says "This is the trailing path component sent in the > >> registration email". > >> > >> I can't find any place to register for the community version which > >> should be free. > >> > >> Any ideas? > >> > >> > >> > >> ___ > >> Bacula-users mailing list > >> Bacula-users@lists.sourceforge.net > >> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fbacula-users=05%7C01%7Ckm%40mathcs.emory.edu%7Ccf20eaabdd404567f8b408db7984dc88%7Ce004fb9cb0a4424fbcd0322606d5df38%7C0%7C0%7C638237383887165100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=6UXvNFZgmFnVZcDJGG4QQB5iLXmrEhCHyO24kcMxr4E%3D=0 > >> > >> > > > > ___ > 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 Community Installation Guide
Ben Thanks! I now have the access key. But going forward another obstacle. I'm running Ubuntu 23.04 Lunar Lobster. apt-key is no longer available in 23.04, so the instructions for importing the GPG key won't work. Is there a simple replacement, and maybe more to the point if I get as far as "deb" for sources, will the repository have Lunar? Ken Ben Tyger wrote on 6/30/23 12:12: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bacula.org%2Fbacula-binary-package-download%2F=05%7C01%7Ckm%40mathcs.emory.edu%7Ccf20eaabdd404567f8b408db7984dc88%7Ce004fb9cb0a4424fbcd0322606d5df38%7C0%7C0%7C638237383887165100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=b2k4q2Gw622smLbaKpbvlZxcoxkF6eHlaCqk%2BsJgdag%3D=0 is the registration page. You'll get the specialized link in your e-mail On 6/30/23 11:27, Ken Mandelberg wrote: I'm trying to use the instructions for installing the community version binaries for Bacula 13 on Ubuntu. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.bacula.org%2Fwhitepapers%2FCommunityInstallationGuide.pdf=05%7C01%7Ckm%40mathcs.emory.edu%7Ccf20eaabdd404567f8b408db7984dc88%7Ce004fb9cb0a4424fbcd0322606d5df38%7C0%7C0%7C638237383887165100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=Q5lKyN1XZJHNI%2BjCJJU66hC6uSC7qSRzqOQsf4661hM%3D=0 To get started setting up sources for apt it needs an access key which it says "This is the trailing path component sent in the registration email". I can't find any place to register for the community version which should be free. Any ideas? ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fbacula-users=05%7C01%7Ckm%40mathcs.emory.edu%7Ccf20eaabdd404567f8b408db7984dc88%7Ce004fb9cb0a4424fbcd0322606d5df38%7C0%7C0%7C638237383887165100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C=6UXvNFZgmFnVZcDJGG4QQB5iLXmrEhCHyO24kcMxr4E%3D=0 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Community Installation Guide
Don't feel bad. I've gotten this access key for my installations before and I struggled to find it. Go to the link below. It looks like a "contact us" form is at the bottom of the page, but that's actually the registration form. Give name and a valid email, and your access key will be emailed to you. It'll be the alphanumeric portion of the url they send you. Don't lose that, as you'll need it in your configuration now and again. https://www.bacula.org/bacula-binary-package-download/ Robert Gerber 402-237-8692 r...@craeon.net On Fri, Jun 30, 2023, 10:28 AM Ken Mandelberg wrote: > I'm trying to use the instructions for installing the community version > binaries for Bacula 13 on Ubuntu. > > https://www.bacula.org/whitepapers/CommunityInstallationGuide.pdf > > To get started setting up sources for apt it needs an access key which > it says "This is the trailing path component sent in the registration > email". > > I can't find any place to register for the community version which > should be free. > > Any ideas? > > > > ___ > 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 13.0.x compatibility with 9.4 FD
This information is in the release notes. :) https://www.bacula.org/bacula-release-13-0-3/ "Compatibility: As always, both the Director and Storage daemon(s) must be upgraded at the same time. Any File daemon running on the same machine as a Director or Storage daemon must be of the same version. Older File Daemons should be compatible with the 13.0 Director and Storage daemons. There should be no need to upgrade older File Daemons." Robert Gerber 402-237-8692 r...@craeon.net On Fri, Jun 30, 2023, 6:28 AM Yateen Shaligram Bhagat (Nokia) < yateen.shaligram_bha...@nokia.com> wrote: > Hi all, > > > > Can someone tell if Bacula 13.0.3 Dir & SD are compatible to Bacula 9.4 FD. > > > > Could not get this info from the the documentation. > > > > Thanks > > Yateen Bhagat > ___ > 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, Autochangers, insist on loading 'not in changer' media...
> Someone have some clue? Thanks. No feedback here, i've created: https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues/2683 FYI. -- Quante persone che non contano, e invece contano e si stanno contando gia` Stanno solo aspettando un segno, Capata`z (F. De Gregori) ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula, Autochangers, insist on loading 'not in changer' media...
I would add that this problem appears to occur when all in-changer tapes
are unavailable due to volume status AND the job's pool does contain
available tapes, but those tapes are not in-changer. Bacula will attempt
to load a tape that is not in-changer, where it should send an operator
intervention notice.
On 5/12/23 06:22, Marco Gaiarin wrote:
We have some setups using bacula (debian buster, 9.4.2-2+deb10u1) and RDX
media, by the way of the 'vchanger' (Virtual Changer) script.
All works as expected, until the current mounted media exaust the 'in
changer' media (because exausted it; or because simply users load the
incorrect media...).
After that, bacula try to mount expired (purge them) or generically
avaliable volumes from other media, that are 'not in changer', putting them
on error.
We have extensivaly debugged vchanger script, that seems behave correctly.
Bacula seems have a current and correct state of 'in changer' volumes, and
anyway a 'update volumes' on console does not solve the trouble.
On director we have:
Autochanger {
Name = SDPVE2RDX
Address = sdpve2.sd.lnf.it
SDPort = 9103
Password = "unknown"
Maximum Concurrent Jobs = 5
Device = RDXAutochanger
Media Type = RDX
}
Pool {
Name = VEN-SD-SDPVE2RDXPool
Pool Type = Backup
Volume Use Duration = 1 days
Maximum Volume Jobs = 1
Recycle = yes
AutoPrune = yes
Action On Purge = Truncate
Volume Retention = 20 days
}
On SD we have:
Autochanger {
Name = RDXAutochanger
Device = RDXStorage0
Device = RDXStorage1
Device = RDXStorage2
Changer Command = "/usr/bin/vchanger %c %o %S %a %d"
Changer Device = "/etc/vchanger/SDPVE2RDX.conf"
}
Device {
Name = RDXStorage0
Drive Index = 0
Device Type = File
Media Type = RDX
RemovableMedia = no
RandomAccess = yes
Maximum Concurrent Jobs = 1
Archive Device = "/var/spool/vchanger/SDPVE2RDX/0"
}
Device {
Name = RDXStorage1
Drive Index = 1
Device Type = File
Media Type = RDX
RemovableMedia = no
RandomAccess = yes
Maximum Concurrent Jobs = 1
Archive Device = "/var/spool/vchanger/SDPVE2RDX/1"
}
Device {
Name = RDXStorage2
Drive Index = 2
Device Type = File
Media Type = RDX
RemovableMedia = no
RandomAccess = yes
Maximum Concurrent Jobs = 1
Archive Device = "/var/spool/vchanger/SDPVE2RDX/2"
}
Someone have some clue? Thanks.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula Release 13.0.3
Nice! Will docker and cloud s3 plugins also be available for 13.0.3? Em qua., 3 de mai. de 2023 05:58, Eric Bollengier escreveu: > Hello Elias, > > On 5/3/23 00:49, Elias Pereira wrote: > > hello Eric, > > > > Do you have a release date for Bacula Community Binaries 10.0.3? > > I think that they are now all uploaded. We will run smoke tests to ensure > that > everything can be installed properly, so they should be ok by Friday or > early > next week. > > Best Regards, > Eric > > > On Tue, May 2, 2023 at 4:47 PM Eric Bollengier via Bacula-devel < > > bacula-de...@lists.sourceforge.net> wrote: > > > >> Hello, > >> > >> We are pleased to announce the release of Bacula version 13.0.3 This is > a > >> minor bugfix release of the new stable version. We recommend to upgrade > to > >> this > >> version. > >> > >> The new release 13.0 has many new features and a number of changes. > >> Please take care to test this code carefully before putting it > >> into production. The version 13.0.3 has some interesting new features > >> around the restricted console. > >> > >> This release of Bacula uses a new catalog format. We provide a set of > >> scripts that permit to convert a 11.x and earlier versions to the new > >> 13.0 format (1024). Normally, it is fast and automatic. > >> > >> Note that converting from 9.x is a big change that takes longer than > usual. > >> Beetween 9.x and 11.x, the upgrade process will require more or less > twice > >> the size of the actual database on disk. > >> > >> Please see the ReleaseNotes for how to build Bacula 13.0.3 with the > >> correct libs3 for use with the Amazon Cloud. > >> > >> Most of the binaries (rpm, deb) are already ready, more should come > >> this week. > >> > >> Thank you for using Bacula, > >> Eric > >> > >> 13.0.3 is a minor bug fix release with several new features and a number > >> of bug > >> fixes. > >> > >>- Fix #10030 About small issue while canceling the restore command > >> > >>- Fix #9968 Enhance restricted Console support > >>- Fix #10032 Allow restore menu 1 to users without sqlquery command > ACL > >>- Fix #10033 Add extra Client and FileSet ACL checks to the estimate > >> command > >>- Fix #9907 About Director crash with Runscript Console > >>- Fix #9968 Adapt restore menu and add RBCLIENT/BCLIENT in some ACL > SQL > >> checking > >>- Fix small memory leak with setbandwidth command > >>- Adapt delete, prune, purge commands to work with restricted > consoles > >>- Check ClientACL in acl_access_jobid_ok() > >>- Check Pool specific ACL in select_media_dbr() > >>- Disable Bootstrap manual selection in restore for Restricted > Console > >>- Do not display specific SQL errors to restricted consoles > >>- Include BackupClient in list jobs, list jobmedia, list joblog > >>- Restrict the use of local files during the restore file selection > >> process > >> when using a Restricted Console > >>- Take the first valid FileSet for the restore Job with restricted > >> consoles > >> > >>- baculum: Add checking errors in output from vsphere plugin servers, > >> hosts > >> and datastores commands > >>- baculum: Add new m365 plugin mailbox list endpoint > >>- baculum: Add VMware vSphere datastore list endpoint > >>- baculum: Add VMware vSphere host list endpoint > >>- baculum: Add VMware vSphere restore host list endpoint > >>- baculum: Add VMware vSphere server list endpoint > >>- baculum: Add a new endpoint to list jobs together with objects > >>- baculum: Add client filter to objects endpoint > >>- baculum: Add client property to object and objects endpoint > >>- baculum: Add client resnames endpoint > >>- baculum: Add client, pool, fileset and fileset content properties > to > >> jobs > >> objects endpoint > >>- baculum: Add displaying bconsole command output if command is > multiline > >>- baculum: Add enabled flag filter to volumes endpoint > >>- baculum: Add endpoint to list m365 jobs by email > >>- baculum: Add endtime property and filters to source list endpoint > >>- baculum: Add estimated job values endpoint that uses job historical > >> data for > >> estimation > >>- baculum: Add fileindex parameter to bvfs restore endpoint > >>- baculum: Add fileset and filesetid filters to jobs objects endpoint > >>- baculum: Add fileset content property to sources endpoint output > >>- baculum: Add job errors property to objects endpoint > >>- baculum: Add job errors property to sources endpoint > >>- baculum: Add job status property to objects endpoint > >>- baculum: Add job type to sources endpoint > >>- baculum: Add joberrors filter to jobs objects endpoint > >>- baculum: Add joberrors filter to objects endpoint > >>- baculum: Add mediaid to volume overview endpoint > >>- baculum: Add method to execute SQL queries > >>- baculum: Add more detailed output to restore endpoint > >>- baculum: Add
Re: [Bacula-users] [Bacula-devel] Bacula Release 13.0.3
Hello Elias, On 5/3/23 00:49, Elias Pereira wrote: hello Eric, Do you have a release date for Bacula Community Binaries 10.0.3? I think that they are now all uploaded. We will run smoke tests to ensure that everything can be installed properly, so they should be ok by Friday or early next week. Best Regards, Eric On Tue, May 2, 2023 at 4:47 PM Eric Bollengier via Bacula-devel < bacula-de...@lists.sourceforge.net> wrote: Hello, We are pleased to announce the release of Bacula version 13.0.3 This is a minor bugfix release of the new stable version. We recommend to upgrade to this version. The new release 13.0 has many new features and a number of changes. Please take care to test this code carefully before putting it into production. The version 13.0.3 has some interesting new features around the restricted console. This release of Bacula uses a new catalog format. We provide a set of scripts that permit to convert a 11.x and earlier versions to the new 13.0 format (1024). Normally, it is fast and automatic. Note that converting from 9.x is a big change that takes longer than usual. Beetween 9.x and 11.x, the upgrade process will require more or less twice the size of the actual database on disk. Please see the ReleaseNotes for how to build Bacula 13.0.3 with the correct libs3 for use with the Amazon Cloud. Most of the binaries (rpm, deb) are already ready, more should come this week. Thank you for using Bacula, Eric 13.0.3 is a minor bug fix release with several new features and a number of bug fixes. - Fix #10030 About small issue while canceling the restore command - Fix #9968 Enhance restricted Console support - Fix #10032 Allow restore menu 1 to users without sqlquery command ACL - Fix #10033 Add extra Client and FileSet ACL checks to the estimate command - Fix #9907 About Director crash with Runscript Console - Fix #9968 Adapt restore menu and add RBCLIENT/BCLIENT in some ACL SQL checking - Fix small memory leak with setbandwidth command - Adapt delete, prune, purge commands to work with restricted consoles - Check ClientACL in acl_access_jobid_ok() - Check Pool specific ACL in select_media_dbr() - Disable Bootstrap manual selection in restore for Restricted Console - Do not display specific SQL errors to restricted consoles - Include BackupClient in list jobs, list jobmedia, list joblog - Restrict the use of local files during the restore file selection process when using a Restricted Console - Take the first valid FileSet for the restore Job with restricted consoles - baculum: Add checking errors in output from vsphere plugin servers, hosts and datastores commands - baculum: Add new m365 plugin mailbox list endpoint - baculum: Add VMware vSphere datastore list endpoint - baculum: Add VMware vSphere host list endpoint - baculum: Add VMware vSphere restore host list endpoint - baculum: Add VMware vSphere server list endpoint - baculum: Add a new endpoint to list jobs together with objects - baculum: Add client filter to objects endpoint - baculum: Add client property to object and objects endpoint - baculum: Add client resnames endpoint - baculum: Add client, pool, fileset and fileset content properties to jobs objects endpoint - baculum: Add displaying bconsole command output if command is multiline - baculum: Add enabled flag filter to volumes endpoint - baculum: Add endpoint to list m365 jobs by email - baculum: Add endtime property and filters to source list endpoint - baculum: Add estimated job values endpoint that uses job historical data for estimation - baculum: Add fileindex parameter to bvfs restore endpoint - baculum: Add fileset and filesetid filters to jobs objects endpoint - baculum: Add fileset content property to sources endpoint output - baculum: Add job errors property to objects endpoint - baculum: Add job errors property to sources endpoint - baculum: Add job status property to objects endpoint - baculum: Add job type to sources endpoint - baculum: Add joberrors filter to jobs objects endpoint - baculum: Add joberrors filter to objects endpoint - baculum: Add mediaid to volume overview endpoint - baculum: Add method to execute SQL queries - baculum: Add more detailed output to restore endpoint - baculum: Add objectid parameter to Bvfs restore endpoint - baculum: Add objecttype parameter to jobs objects endpoint - baculum: Add offset and limit parameters to bvfs versions endpoint - baculum: Add offset parameter to filesets endpoint - baculum: Add offset parameter to m365 plugin email list endpoint - baculum: Add offset parameter to sources endpoint - baculum: Add options to configure preserving table settings - baculum: Add order_by and order_direction parameters to sources endpoint - baculum: Add order_by and order_direction parameters to volumes endpoint - baculum: Add order_by and order_direction
Re: [Bacula-users] [Bacula-devel] Bacula Release 13.0.3
hello Eric, Do you have a release date for Bacula Community Binaries 10.0.3? On Tue, May 2, 2023 at 4:47 PM Eric Bollengier via Bacula-devel < bacula-de...@lists.sourceforge.net> wrote: > Hello, > > We are pleased to announce the release of Bacula version 13.0.3 This is a > minor bugfix release of the new stable version. We recommend to upgrade to > this > version. > > The new release 13.0 has many new features and a number of changes. > Please take care to test this code carefully before putting it > into production. The version 13.0.3 has some interesting new features > around the restricted console. > > This release of Bacula uses a new catalog format. We provide a set of > scripts that permit to convert a 11.x and earlier versions to the new > 13.0 format (1024). Normally, it is fast and automatic. > > Note that converting from 9.x is a big change that takes longer than usual. > Beetween 9.x and 11.x, the upgrade process will require more or less twice > the size of the actual database on disk. > > Please see the ReleaseNotes for how to build Bacula 13.0.3 with the > correct libs3 for use with the Amazon Cloud. > > Most of the binaries (rpm, deb) are already ready, more should come > this week. > > Thank you for using Bacula, > Eric > > 13.0.3 is a minor bug fix release with several new features and a number > of bug > fixes. > > - Fix #10030 About small issue while canceling the restore command > > - Fix #9968 Enhance restricted Console support > - Fix #10032 Allow restore menu 1 to users without sqlquery command ACL > - Fix #10033 Add extra Client and FileSet ACL checks to the estimate > command > - Fix #9907 About Director crash with Runscript Console > - Fix #9968 Adapt restore menu and add RBCLIENT/BCLIENT in some ACL SQL > checking > - Fix small memory leak with setbandwidth command > - Adapt delete, prune, purge commands to work with restricted consoles > - Check ClientACL in acl_access_jobid_ok() > - Check Pool specific ACL in select_media_dbr() > - Disable Bootstrap manual selection in restore for Restricted Console > - Do not display specific SQL errors to restricted consoles > - Include BackupClient in list jobs, list jobmedia, list joblog > - Restrict the use of local files during the restore file selection > process > when using a Restricted Console > - Take the first valid FileSet for the restore Job with restricted > consoles > > - baculum: Add checking errors in output from vsphere plugin servers, > hosts > and datastores commands > - baculum: Add new m365 plugin mailbox list endpoint > - baculum: Add VMware vSphere datastore list endpoint > - baculum: Add VMware vSphere host list endpoint > - baculum: Add VMware vSphere restore host list endpoint > - baculum: Add VMware vSphere server list endpoint > - baculum: Add a new endpoint to list jobs together with objects > - baculum: Add client filter to objects endpoint > - baculum: Add client property to object and objects endpoint > - baculum: Add client resnames endpoint > - baculum: Add client, pool, fileset and fileset content properties to > jobs > objects endpoint > - baculum: Add displaying bconsole command output if command is multiline > - baculum: Add enabled flag filter to volumes endpoint > - baculum: Add endpoint to list m365 jobs by email > - baculum: Add endtime property and filters to source list endpoint > - baculum: Add estimated job values endpoint that uses job historical > data for > estimation > - baculum: Add fileindex parameter to bvfs restore endpoint > - baculum: Add fileset and filesetid filters to jobs objects endpoint > - baculum: Add fileset content property to sources endpoint output > - baculum: Add job errors property to objects endpoint > - baculum: Add job errors property to sources endpoint > - baculum: Add job status property to objects endpoint > - baculum: Add job type to sources endpoint > - baculum: Add joberrors filter to jobs objects endpoint > - baculum: Add joberrors filter to objects endpoint > - baculum: Add mediaid to volume overview endpoint > - baculum: Add method to execute SQL queries > - baculum: Add more detailed output to restore endpoint > - baculum: Add objectid parameter to Bvfs restore endpoint > - baculum: Add objecttype parameter to jobs objects endpoint > - baculum: Add offset and limit parameters to bvfs versions endpoint > - baculum: Add offset parameter to filesets endpoint > - baculum: Add offset parameter to m365 plugin email list endpoint > - baculum: Add offset parameter to sources endpoint > - baculum: Add options to configure preserving table settings > - baculum: Add order_by and order_direction parameters to sources > endpoint > - baculum: Add order_by and order_direction parameters to volumes > endpoint > - baculum: Add order_by and order_direction params to jobs objects > endpoint > - baculum: Add output parameter to run job endpoint > - baculum: Add
Re: [Bacula-users] Bacula Differential and Incremental Backup not working
Bill Arlofski via Bacula-users schrieb am 21.04.23 um 16:52: On 4/21/23 04:39, Dr. Thorsten Brandau wrote: Hi yes, I commented the incremential out because it also makes a full backup and therefore I only try to do differential per weekend. I want to have incrementals daily, but it does not work (always does full). The last log is: 07-Apr 23:05 -dir JobId 136: Start Backup JobId 136, Job=FileServer_Full.2023-04-07_23.05.00_04 Hello Dr. Thorsten, Please show us the Job and Fileset configurations. Then, please run: * run job=FileServer_Full level=Incremental * run job=FileServer_Full level=Differential and show us those complete Job logs too - including the Summary information at the end. Some things to note: - If there is no Full job in the Catalog, then Bacula can't run an Incremental, nor a Differential. These would be automatically upgraded to a Full level - you will be notified in the job log in the very first line. - If you edit a Fileset, Bacula will notice this and will automatical ly upgrade the next Inc or Diff to a Full - you will be notified in the job log in the very first line. - To prevent the second case, you can add `IgnoreFileSetChanges = yes` to the Fileset - but this has its own ramifications and is not recommended to use unless you are fully aware - See the docs about this feature for more information. Okay. Starting the jobs manually gave the desired result. Maybe because I have set "mtimeonly=yes" previously. Also the scheduled jobs work well. So probably "mtimeonly=yes" was the correct setting. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Differential and Incremental Backup not working
Chris Wilkinson schrieb am 21.04.23 um 17:00: One thing i’ve always found useful is to install Webmin and the Bacula module. It gives a quick overview of the config in GUI form and helps to spot config errors. One caveat is not to save any configs from it as it doesn’t respect the time units that are in the pool configs for retention times etc. Unfortunately I am running SuSe Tumbleweed on that sever and it does not work well with Webmin since many years... Back to the command line for me. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Differential and Incremental Backup not working
One thing i’ve always found useful is to install Webmin and the Bacula module. It gives a quick overview of the config in GUI form and helps to spot config errors. One caveat is not to save any configs from it as it doesn’t respect the time units that are in the pool configs for retention times etc. Webmin is handy for all sorts of tasks too. Best -Chris- > On 21 Apr 2023, at 15:52, Bill Arlofski via Bacula-users > wrote: > > On 4/21/23 04:39, Dr. Thorsten Brandau wrote: >> Hi >> >> yes, I commented the incremential out because it also makes a full backup >> and therefore I only try to do differential per >> weekend. I want to have incrementals daily, but it does not work (always >> does full). >> >> The last log is: >> >> 07-Apr 23:05 -dir JobId 136: Start Backup JobId 136, >> Job=FileServer_Full.2023-04-07_23.05.00_04 > > Hello Dr. Thorsten, > > Please show us the Job and Fileset configurations. > > Then, please run: > > * run job=FileServer_Full level=Incremental > > * run job=FileServer_Full level=Differential > > and show us those complete Job logs too - including the Summary information > at the end. > > > Some things to note: > > - If there is no Full job in the Catalog, then Bacula can't run an > Incremental, nor a Differential. These would be > automatically upgraded to a Full level - you will be notified in the job log > in the very first line. > > - If you edit a Fileset, Bacula will notice this and will automatical > ly upgrade the next Inc or Diff to a Full - you will be > notified in the job log in the very first line. > > - To prevent the second case, you can add `IgnoreFileSetChanges = yes` to the > Fileset - but this has its own ramifications > and is not recommended to use unless you are fully aware - See the docs about > this feature for more information. > > > Best regards, > Bill > > -- > Bill Arlofski > w...@protonmail.com > > ___ > 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 Differential and Incremental Backup not working
PS: Despooling seems unusually slow to me. PPS: Please do not top-post. I have noticed that both, spooling and despooling is very slow. I have no idea why, the disc makes easily 300 MB/s and there is nothing else going on on that raid. I have no idea where to even look. When I start parallel other processes, they can use the full power. iotop goes up to 300 MB/s from time to time to drop then again to zero. On another server where I go directly disc to tape it is faster (LTO-6). ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Differential and Incremental Backup not working
On 4/21/23 04:39, Dr. Thorsten Brandau wrote: Hi yes, I commented the incremential out because it also makes a full backup and therefore I only try to do differential per weekend. I want to have incrementals daily, but it does not work (always does full). The last log is: 07-Apr 23:05 -dir JobId 136: Start Backup JobId 136, Job=FileServer_Full.2023-04-07_23.05.00_04 Hello Dr. Thorsten, Please show us the Job and Fileset configurations. Then, please run: * run job=FileServer_Full level=Incremental * run job=FileServer_Full level=Differential and show us those complete Job logs too - including the Summary information at the end. Some things to note: - If there is no Full job in the Catalog, then Bacula can't run an Incremental, nor a Differential. These would be automatically upgraded to a Full level - you will be notified in the job log in the very first line. - If you edit a Fileset, Bacula will notice this and will automatical ly upgrade the next Inc or Diff to a Full - you will be notified in the job log in the very first line. - To prevent the second case, you can add `IgnoreFileSetChanges = yes` to the Fileset - but this has its own ramifications and is not recommended to use unless you are fully aware - See the docs about this feature for more information. Best regards, Bill -- Bill Arlofski w...@protonmail.com signature.asc Description: OpenPGP digital signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula Differential and Incremental Backup not working
Udo Kaune schrieb am 21.04.23 um 16:24: How does the protocol of one of these Differential (and then allegedly unnecessary Full) Backups start? Are there any hints e.g. "No Full Backup Found!"? Please always include the list in your postings for other readers to learn from the issue. Am 21.04.23 um 15:16 schrieb Dr. Thorsten Brandau: > > As seen below: > > Here is the full log (it is WY to much data for a differential backup): > > ->->-> > > 7-Apr 23:05 -dir JobId 136: Start Backup JobId 136, Job=FileServer_Full.2023-04-07_23.05.00_04 > 07-Apr 23:05 -dir JobId 136: Using Device "LTO9-1" to write. > 07-Apr 23:05 -sd JobId 136: Error: 07-Apr 23:05 -sd JobId 136: Volume "20L9" previously written, moving to end of data. > 07-Apr 23:06 -sd JobId 136: Ready to append to end of Volume "20L9" at file=2789. > 07-Apr 23:06 -sd JobId 136: Spooling data ... > 08-Apr 02:37 -sd JobId 136: User specified Job spool size reached: JobSpoolSize=3,000,000,026,157 MaxJobSpoolSize=3,000,000,000,000 > 08-Apr 02:37 -sd JobId 136: Writing spooled data to Volume. Despooling 3,000,000,026,157 bytes ... > 08-Apr 08:14 -sd JobId 136: Despooling elapsed time = 05:36:38, Transfer rate = 148.5 M Bytes/second > 08-Apr 08:14 -sd JobId 136: Spooling data again ... > 08-Apr 11:40 -sd JobId 136: User specified Job spool size reached: JobSpoolSize=3,000,000,008,520 MaxJobSpoolSize=3,000,000,000,000 > 08-Apr 11:40 -sd JobId 136: Writing spooled data to Volume. Despooling 3,000,000,008,520 bytes ... > 08-Apr 17:59 -sd JobId 136: Despooling elapsed time = 06:18:52, Transfer rate = 131.9 M Bytes/second > 08-Apr 17:59 -sd JobId 136: Spooling data again ... > 08-Apr 22:57 -sd JobId 136: User specified Job spool size reached: JobSpoolSize=3,000,000,059,190 MaxJobSpoolSize=3,000,000,000,000 > 08-Apr 22:57 -sd JobId 136: Writing spooled data to Volume. Despooling 3,000,000,059,190 bytes ... > 09-Apr 05:47 -sd JobId 136: Despooling elapsed time = 06:49:38, Transfer rate = 122.0 M Bytes/second > 09-Apr 05:47 -sd JobId 136: Spooling data again ... > 09-Apr 10:35 -sd JobId 136: Error: Error writing header to spool file. Disk probably full. Attempting recovery. Wanted to write=64512 got=692 > 09-Apr 10:35 -sd JobId 136: Writing spooled data to Volume. Despooling 2,999,394,019,676 bytes ... > 09-Apr 17:35 -sd JobId 136: Despooling elapsed time = 06:59:31, Transfer rate = 119.1 M Bytes/second > 09-Apr 20:28 -sd JobId 136: Error: Error writing header to spool file. Disk probably full. Attempting recovery. Wanted to write=64512 got=3793 > 09-Apr 20:28 -sd JobId 136: Writing spooled data to Volume. Despooling 2,999,392,366,895 bytes ... > 10-Apr 03:33 -sd JobId 136: Despooling elapsed time = 07:04:44, Transfer rate = 117.6 M Bytes/second > 10-Apr 06:22 -sd JobId 136: Committing spooled data to Volume "20L9". Despooling 1,510,003,913,646 bytes ... > 10-Apr 09:38 -sd JobId 136: Despooling elapsed time = 03:16:01, Transfer rate = 128.3 M Bytes/second > 10-Apr 09:38 -sd JobId 136: Elapsed time=58:31:43, Transfer rate=78.27 M Bytes/second > 10-Apr 09:38 -sd JobId 136: Sending spooled attrs to the Director. Despooling 1,885,573,459 bytes ... > 10-Apr 09:43 -dir JobId 136: Bacula -dir 11.0.6 (10Mar22): > Build OS: x86_64-suse-linux-gnu openSUSE Tumbleweed > JobId: 136 > Job: FileServer_Full.2023-04-07_23.05.00_04 > Backup Level: Full > Client: "-fd" 11.0.6 (10Mar22) x86_64-suse-linux-gnu,openSUSE,Tumbleweed > FileSet: "Full Set" 2023-03-18 23:05:00 > Pool: "Tape" (From Job resource) > Catalog: "MyCatalog" (From Client resource) > Storage: "AutoChangerLTO" (From Job resource) > Scheduled time: 07-Apr-2023 23:05:00 > Start time: 07-Apr-2023 23:05:03 > End time: 10-Apr-2023 09:43:52 > Elapsed time: 2 days 10 hours 38 mins 49 secs > Priority: 10 > FD Files Written: 6,600,638 > SD Files Written: 6,600,638 > FD Bytes Written: 16,491,080,239,221 (16.49 TB) > SD Bytes Written: 16,492,258,152,160 (16.49 TB) > Rate: 78109.0 KB/s > Software Compression: None > Comm Line Compression: 64.5% 2.8:1 > Snapshot/VSS: no > Encryption: no > Accurate: no > Volume name(s): 20L9 > Volume Session Id: 2 > Volume Session Time: 1680860753 > Last Volume Bytes: 19,288,951,428,096 (19.28 TB) > Non-fatal FD errors: 0 > SD Errors: 3 > FD termination status: OK > SD termination status: OK > Termination: Backup OK -- with warnings > > 10-Apr 09:43 -dir JobId 136: Begin pruning Jobs older than 6 months . > 10-Apr 09:43 -dir JobId 136: No Jobs found to prune. > 10-Apr 09:43 -dir JobId 136: Begin pruning Files. > 10-Apr 09:43 -dir JobId 136: No Files found to prune. > 10-Apr
Re: [Bacula-users] Bacula Differential and Incremental Backup not working
How does the protocol of one of these Differential (and then allegedly unnecessary Full) Backups start? Are there any hints e.g. "No Full Backup Found!"? Please always include the list in your postings for other readers to learn from the issue. Am 21.04.23 um 15:16 schrieb Dr. Thorsten Brandau: > > As seen below: > > Here is the full log (it is WY to much data for a differential backup): > > ->->-> > > 7-Apr 23:05 -dir JobId 136: Start Backup JobId 136, Job=FileServer_Full.2023-04-07_23.05.00_04 > 07-Apr 23:05 -dir JobId 136: Using Device "LTO9-1" to write. > 07-Apr 23:05 -sd JobId 136: Error: 07-Apr 23:05 -sd JobId 136: Volume "20L9" previously written, moving to end of data. > 07-Apr 23:06 -sd JobId 136: Ready to append to end of Volume "20L9" at file=2789. > 07-Apr 23:06 -sd JobId 136: Spooling data ... > 08-Apr 02:37 -sd JobId 136: User specified Job spool size reached: JobSpoolSize=3,000,000,026,157 MaxJobSpoolSize=3,000,000,000,000 > 08-Apr 02:37 -sd JobId 136: Writing spooled data to Volume. Despooling 3,000,000,026,157 bytes ... > 08-Apr 08:14 -sd JobId 136: Despooling elapsed time = 05:36:38, Transfer rate = 148.5 M Bytes/second > 08-Apr 08:14 -sd JobId 136: Spooling data again ... > 08-Apr 11:40 -sd JobId 136: User specified Job spool size reached: JobSpoolSize=3,000,000,008,520 MaxJobSpoolSize=3,000,000,000,000 > 08-Apr 11:40 -sd JobId 136: Writing spooled data to Volume. Despooling 3,000,000,008,520 bytes ... > 08-Apr 17:59 -sd JobId 136: Despooling elapsed time = 06:18:52, Transfer rate = 131.9 M Bytes/second > 08-Apr 17:59 -sd JobId 136: Spooling data again ... > 08-Apr 22:57 -sd JobId 136: User specified Job spool size reached: JobSpoolSize=3,000,000,059,190 MaxJobSpoolSize=3,000,000,000,000 > 08-Apr 22:57 -sd JobId 136: Writing spooled data to Volume. Despooling 3,000,000,059,190 bytes ... > 09-Apr 05:47 -sd JobId 136: Despooling elapsed time = 06:49:38, Transfer rate = 122.0 M Bytes/second > 09-Apr 05:47 -sd JobId 136: Spooling data again ... > 09-Apr 10:35 -sd JobId 136: Error: Error writing header to spool file. Disk probably full. Attempting recovery. Wanted to write=64512 got=692 > 09-Apr 10:35 -sd JobId 136: Writing spooled data to Volume. Despooling 2,999,394,019,676 bytes ... > 09-Apr 17:35 -sd JobId 136: Despooling elapsed time = 06:59:31, Transfer rate = 119.1 M Bytes/second > 09-Apr 20:28 -sd JobId 136: Error: Error writing header to spool file. Disk probably full. Attempting recovery. Wanted to write=64512 got=3793 > 09-Apr 20:28 -sd JobId 136: Writing spooled data to Volume. Despooling 2,999,392,366,895 bytes ... > 10-Apr 03:33 -sd JobId 136: Despooling elapsed time = 07:04:44, Transfer rate = 117.6 M Bytes/second > 10-Apr 06:22 -sd JobId 136: Committing spooled data to Volume "20L9". Despooling 1,510,003,913,646 bytes ... > 10-Apr 09:38 -sd JobId 136: Despooling elapsed time = 03:16:01, Transfer rate = 128.3 M Bytes/second > 10-Apr 09:38 -sd JobId 136: Elapsed time=58:31:43, Transfer rate=78.27 M Bytes/second > 10-Apr 09:38 -sd JobId 136: Sending spooled attrs to the Director. Despooling 1,885,573,459 bytes ... > 10-Apr 09:43 -dir JobId 136: Bacula -dir 11.0.6 (10Mar22): > Build OS: x86_64-suse-linux-gnu openSUSE Tumbleweed > JobId: 136 > Job: FileServer_Full.2023-04-07_23.05.00_04 > Backup Level: Full > Client: "-fd" 11.0.6 (10Mar22) x86_64-suse-linux-gnu,openSUSE,Tumbleweed > FileSet: "Full Set" 2023-03-18 23:05:00 > Pool: "Tape" (From Job resource) > Catalog: "MyCatalog" (From Client resource) > Storage: "AutoChangerLTO" (From Job resource) > Scheduled time: 07-Apr-2023 23:05:00 > Start time: 07-Apr-2023 23:05:03 > End time: 10-Apr-2023 09:43:52 > Elapsed time: 2 days 10 hours 38 mins 49 secs > Priority: 10 > FD Files Written: 6,600,638 > SD Files Written: 6,600,638 > FD Bytes Written: 16,491,080,239,221 (16.49 TB) > SD Bytes Written: 16,492,258,152,160 (16.49 TB) > Rate: 78109.0 KB/s > Software Compression: None > Comm Line Compression: 64.5% 2.8:1 > Snapshot/VSS: no > Encryption: no > Accurate: no > Volume name(s): 20L9 > Volume Session Id: 2 > Volume Session Time: 1680860753 > Last Volume Bytes: 19,288,951,428,096 (19.28 TB) > Non-fatal FD errors: 0 > SD Errors: 3 > FD termination status: OK > SD termination status: OK > Termination: Backup OK -- with warnings > > 10-Apr 09:43 -dir JobId 136: Begin pruning Jobs older than 6 months . > 10-Apr 09:43 -dir JobId 136: No Jobs found to prune. > 10-Apr 09:43 -dir JobId 136: Begin pruning Files. > 10-Apr 09:43 -dir JobId 136: No Files found to prune. > 10-Apr 09:43 -dir JobId 136: End auto prune. > >
