[Bacula-users] Volume issues with 11.0.6 running in docker

2023-08-07 Thread Daniel Rich via Bacula-users
I recently migrated my bacula director and storage daemon to version 11 and am 
running them in docker. Ever since, I have started getting occasional volume 
errors that can only be resolved by restarting the bacula-sd container or in 
some cases deleting and relabeling a volume. Thinks will run fine for a week or 
two (or more) and then start throwing errors. Has anyone else seen anything 
like this? 

These volumes are file volumes that live on my Synology and are mounted over 
NFS.

Here’s a example of what I’m seeing:
07-Aug 06:10 morpheus-dir JobId 3671: shell command: run BeforeJob 
"/opt/bacula/etc/scripts/make_catalog_backup.pl MyCatalog" 
07-Aug 06:11 morpheus-dir JobId 3671: Start Backup JobId 3671, 
Job=BackupCatalog.2023-08-07_06.10.00_18 
07-Aug 06:11 morpheus-dir JobId 3671: Using Device "vDrive-03" to write. 
07-Aug 06:11 morpheus-sd JobId 3671: Fatal error: block_util.c:478 Volume data 
error at 0:0! Wanted ID: "BB02", got "". Buffer discarded. 
07-Aug 06:11 morpheus-fd JobId 3671: Fatal error: job.c:3012 Bad response from 
SD to Append Data command. Wanted 3000 OK data 
, got len=257 msg="3903 Error append data: Read label block failed: requested 
Volume "morpheus-0076" on File device "vDrive-03" (/srv/backup) is not a Bacula 
labeled Volume, because: ERR=block_util.c:478 Volume data error at 0:0! Wanted 
ID: "BB02", got "". Buffer discarded." 
07-Aug 06:11 morpheus-dir JobId 3671: Error: Bacula morpheus-dir 11.0.6 
(10Mar22): 
Build OS: x86_64-redhat-linux-gnu-bacula redhat (Core) 
JobId: 3671 
Job: BackupCatalog.2023-08-07_06.10.00_18 
Backup Level: Full 
Client: "morpheus-fd" 9.6.7 (10Dec20) x86_64-pc-linux-gnu,ubuntu,20.04 
FileSet: "Catalog" 2022-08-07 06:10:00 
Pool: "morpheus" (From Job resource) 
Catalog: "MyCatalog" (From Client resource) 
Storage: "File" (From Job resource) 
Scheduled time: 07-Aug-2023 06:10:00 
Start time: 07-Aug-2023 06:11:39 
End time: 07-Aug-2023 06:11:40 
Elapsed time: 1 sec 
Priority: 10 
FD Files Written: 0 
SD Files Written: 0 
FD Bytes Written: 0 (0 B) 
SD Bytes Written: 0 (0 B) 
Rate: 0.0 KB/s 
Software Compression: None 
Comm Line Compression: None 
Snapshot/VSS: no 
Encryption: no 
Accurate: no 
Volume name(s): 
Volume Session Id: 72 
Volume Session Time: 1690744006 
Last Volume Bytes: 1 (1 B) 
Non-fatal FD errors: 1 
SD Errors: 1 
FD termination status: Error 
SD termination status: Error 
Termination: *** Backup Error *** 

Dan Rich  |   http://www.employees.org/~drich/
                               |  "Step up to red alert!"  "Are you sure, sir?
                               |   It means changing the bulb in the sign..."
                               |          - Red Dwarf (BBC)

signature.asc
Description: Message signed with OpenPGP using AMPGpg
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] New bacula install

2023-04-05 Thread Daniel Rich via Bacula-users
Did you drop the database and recreate it after you tried to create the tables 
with the root user? That sounds like there were already tables there when you 
ran that command, and it couldn’t recreate them because of the constraints on 
the existing tables.

If you don’t have any data it in, I would drop and recrecreate the database; 
then run that script again.

Dan Rich  |   http://www.employees.org/~drich/
                               |  "Step up to red alert!"  "Are you sure, sir?
                               |   It means changing the bulb in the sign..."
                               |          - Red Dwarf (BBC)

On April 5, 2023 at 08:14:06, Andrew Meyer via Bacula-users 
(bacula-users@lists.sourceforge.net) wrote:

I'm trying to set up bacula on AlmaLinux 8.7 w/ MariaDB 10.11 and getting the 
following error:

$ sudo /usr/libexec/bacula/make_mysql_tables -u bacula -p  
Enter password:  
ERROR 1005 (HY000) at line 112: Can't create table `bacula`.`Job` (errno: 150 
"Foreign key constraint is incorrectly formed")
ERROR 1005 (HY000) at line 286: Can't create table `bacula`.`Pool` (errno: 150 
"Foreign key constraint is incorrectly formed")
Creation of Bacula MySQL tables succeeded.

The error was much worse when I tried to run this as mysql root user.   

Can someone point me in the right direction to resolve this?
___  
Bacula-users mailing list  
Bacula-users@lists.sourceforge.net  
https://lists.sourceforge.net/lists/listinfo/bacula-users  


signature.asc
Description: Message signed with OpenPGP using AMPGpg
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Cloud storage and bacula 11

2022-10-18 Thread Daniel Rich via Bacula-users
Has anyone been able to use cloud storage reliably with Bacula 11? I am trying 
to convert from using volumes on local disk to using minio as a cloud service 
without much luck.

The odd thing is, it will work for a time. But if bacula-sd or bacula-dir 
restarts, I end up in a state where the device status shows things like:
> Device Cloud (S3 Plugin): "cloudDrive-01" (/tmp/cloudDrive-01) is not open.
>    Device is BLOCKED waiting for mount of volume "rpi-0002",
>        Pool:        rpi
>        Media type:  CloudType
>    Drive 0 is not loaded.
and I don't see any obvious way to force it to mount the cloud storage into 
that device node -- short of running s3fs to mount the volume as if I was doing 
a restore. I would think that would not be needed since this mount request is 
from a backup.

Restores are another problem, as I have yet to get one to work reliably with 
cloud media. Maybe I just need to tune my settings a bit more, but doing a 
mount of a volume with lots of small files via. s3fs is painful at best, and 
doesn't work at all in the worst case. Having to mount that under a specifc 
directory when I'm running bacula-sd in a docker container is even more 
painful, since it requires reconfiguing and restarting bacula-sd any time I 
want to restore something.

Here's a sample of my config (with passwords/hostnames obsfucated of course):
> Device {
>   Name = cloudDrive-01
>   Device Type = Cloud
>   Media Type = CloudType
>   Archive Device = /tmp/cloudDrive-01
>   AutomaticMount = yes
>   AlwaysOpen = no
>   RemovableMedia = yes
>   Label Media = yes
>   Random Access = yes
>   Autochanger = yes
>   Maximum Part Size = 50MB
>   Maximum File Size = 50MB
>   Cloud = minio-nas
> }
> Autochanger {
>   Name = CloudAutoChangerS3
>   Changer Device = /dev/null
>   Changer Command = ""
>   Device = cloudDrive-01, cloudDrive-02, cloudDrive-03, cloudDrive-04
> }
> Cloud {
>   Name = "minio-nas"
>   Driver = S3
>   HostName = "nas.xxx.com:9000"
>   BucketName = "bacula"
>   AccessKey = "bacula"
>   SecretKey = "xx"
>   Protocol = HTTP
>   UriStyle = "Path"
>   Truncate Cache = "AfterUpload"
>   Upload = "EachPart"
>   Region = us-xxx-1
>   MaximumUploadBandwidth = 100MB/s
> }
>


Dan Rich 
http://www.employees.org/~drich/
"Step up to red alert!" "Are you sure, sir?
It means changing the bulb in the sign..."
- Red Dwarf (BBC)
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users