Am 06.03.24 um 15:55 schrieb Phil Stracchino:
On 3/6/24 01:58, Stefan G. Weichinger wrote:
As I try to come up with an initial setup for weekly-daily-monthly I
found this:
https://www.bacula.org/13.0.x-manuals/en/main/Automatic_Volume_Recycling.html#SECTION003060
Shouldn't the
Rob
I changed the owner and permission to match yours, from
-rw-r--r-- 1 root root 190 Jul 11 2023 BackupCatalog.bsr
to
-rw-rwx--- 1 bacula bacula 190 Jul 11 2023 BackupCatalog.bsr
I don't know why it would need group execute, it just a text file:
11-Jul-2023 23:10:29 - BackupCatalog
Hello Ken,
In addition to what I previously wrote, i just noticed that your *.bsr files should not be in `/opt/bacula/working`, but
rather in `/opt/bacula/bsr`.
Check your Jobs and JobDefs resources and make sure that the `WriteBootstrap`
settings in these point to the bsr directory
This is
On 3/6/24 10:19, Ken Mandelberg wrote:
I I notice these two permission errors in my logs. I'm on Ubuntu. What do I
need to do to correct them.
The backups succeed but I guess they are missing info.
05-Mar 23:19 orac-dir JobId 7661: shell command: run BeforeJob
"/opt/bacula/scripts/make_catalog
Interesting. I can run that command as my non-root user and get output for
working from my rocky linux 9 system running bacula 13.x.
Your permissions seem similar to mine, though the groups lack write and my
groups do have write permissions. I imagine since these are user's groups
(root should pro
I had a similar issue in v9.x. I added
"cloud storage=cloud-sd allpools allfrompool upload"
as a run after Console command in the cloud job resource. This seems to do
the trick as I've not seen any orphaned volumes in the cache since.
Chris
On Wed, 6 Mar 2024, 18:53 K. M. Peterson,
wrote:
>
I had to run 'ls -lah /opt/bacula/ /opt/bacula/working/ as root to get
access to working:
/opt/bacula/:
total 44K
drwxr-xr-x 11 root root 4.0K Jul 11 2023 .
drwxr-xr-x 9 root root 4.0K Feb 12 12:33 ..
drwx-- 2 bacula root 4.0K May 3 2023 archive
drwxr-xr-x 2 root root 4.0
I am concerned that these backups might not be successful (in the sense
that they are quite probably not actually backing your catalog up). If the
catalog export via "/opt/bacula/scripts/make_catalog_backup.pl MyCatalog"
is not successful and if bacula cannot access the bacula.sql file written
to /
Hi all,
I've been using the S3 driver for some time now, and working around various
idiosyncrasies - the most lasting one being where occasionally due to
something being shut down there are backup parts in the cache that haven't
been uploaded for some reason.
I started using a job that ran at boo
I I notice these two permission errors in my logs. I'm on Ubuntu. What do I
need to do to correct them.
The backups succeed but I guess they are missing info.
05-Mar 23:19 orac-dir JobId 7661: shell command: run BeforeJob
"/opt/bacula/scripts/make_catalog_backup.pl MyCatalog"
05-Mar 23:19 orac-
On 3/6/24 01:58, Stefan G. Weichinger wrote:
As I try to come up with an initial setup for weekly-daily-monthly I
found this:
https://www.bacula.org/13.0.x-manuals/en/main/Automatic_Volume_Recycling.html#SECTION003060
Shouldn't there also be Jobs for Weekly and Monthly?
No, t
11 matches
Mail list logo
