Try the hardware compatibility list for the card on Redhat's website. Second
choice, the manufacturer's website. The issue is the driver.
My question (rhetorical), why do you want to use an OS that is recently
released and still bleeding for a backup server? I understand upgrade
headaches,
The client definition on the server.
Client {
Name = "myclient"
Address = "myclient.example.com"
AutoPrune = yes
Catalog = "MyCatalog"
FdPort = 9102
FileRetention = 33696000
HeartbeatInterval = 300
JobRetention = 33696000
MaximumConcurrentJobs = 4
Password = "mypassword"
}
While I don't think the merits of selinux should be the focus of this
community, both Redhat and CentOS have the selinux policies for bacula. If the
user is required to run in enforcing mode, then he should apply the policies
correctly. This should fix the AVC errors. SELinux is rather
I highly disagree with the RHEL 8 suggestion. You don't need to be fighting
new release problems with an OS on a backup server that will require frequent
patching and reboots.
As for Bacula community don't use the RHEL provided packages, they are way too
old.
Patti Clark
Sr. Linux System
Sometimes I’ve had a BLOCKED device it has been due to a race condition in
Bacula between 2 jobs requesting different media for the same drive. Usually
it can be corrected by canceling one of the jobs. Other times it is due to a
“failed” job that is not cleaned up completely leaving a
You don’t use "Maximum Volume Bytes" for tape volumes.
Patti Clark
Sr. Linux System Administrator
Oak Ridge National Laboratory
From: Olivier Delestre
Reply-To: "olivier.deles...@univ-rouen.fr"
Date: Thursday, June 20, 2019 at 9:25 AM
To: Jasen Lentz , bacula-users
Subject: [EXTERNAL] Re:
You provided the answer yourself. You have limited the director to 20
concurrent jobs. Modify the director setting to the 40 that you want.
>
I definitely have "Maximum Concurrent Jobs = 20" in the Storage sections
of both bacula-dir.conf, and bacula-sd.conf.
>
Patti Clark
; requested by DIR is disabled.
.
.
.
And it goes on for pages and pages until the job is assigned an available drive.
Patti
On 1/3/19, 1:30 PM, "Bill Arlofski" wrote:
On 01/02/2019 02:45 PM, Clark, Patti via Bacula-users wrote:
> Is there a way to put a
Is there a way to put a malfunctioning tape drive in an autochanger into a
service mode via commands without modifying bacula configuration files?
Patti Clark
Sr. Linux System Administrator
Oak Ridge National Laboratory
___
Bacula-users mailing list
Sorry about the /dev/sch0. I've written udev rules to use consistent names
regardless of what udev does - I do use the /dev/sgX for changer
identification. If you've rebooted your system, the output from lsscsi -g may
have changed. You still need the Drive Index line in your bacula-sd.conf .
Use /dev/sch0, not /dev/sg2. Bear in mind, udev is not your friend. If you
ever add another tape drive to your library or expand your device fabric, these
device references will/can change with every system boot. As is, the /dev/sgX
references can change with reboots, but if you only have
From the manual:
> You need to ensure that your Storage daemon (if not running as root) has
> access permissions to both the tape drive and the control device.
My bacula user is also a member of the disk group. The disk group has rw
access to bacula-sd.conf. It also completes the full group
12 matches
Mail list logo
