Re: filestorage :: some misconfiguration

"Stefan G. Weichinger via Bacula-users" <[email protected]>
Newsgroups gmane.comp.bacula.user
Message-ID <[email protected]>
Am 18.08.25 um 19:34 schrieb Rob Gerber:
> Stefan,
> 
> Did you restart the SD? bconsole 'reload' only reloads the dir.
> 
> in shell, try 'sudo systemctl restart bacula-dir.service bacula- 
> sd.service bacula-fd.service;/opt/bacula/bin/bacula status'
> 
> (you can restart all more simply using 'bacula restart' but this breaks 
> systemctl service monitoring until you reboot, iirc).

Yes, I restarted all the daemons. 3x  ;-)
> 'file_changer' is the name of your autochanger in the bacula-sd.conf file.
I show again what I have now. It seems I still don't get all the 
concepts, sorry. I think I have that mess for the n-th time.

# dir

Storage {
   Name = "filestorage"
   Description = "local storage on tx100:/mnt/tera/bacula"
   SdPort = 9103
   Address = "tx100.loc.oops.co.at"
   Password = "_swXHSgGz6DhqHOxS2PlmbAJks_LY6Gg0"
   Device = "file_changer"
   MediaType = "File1"
   Autochanger = "yes"
   MaximumConcurrentJobs = 50
}

# sd

Autochanger {
   Name = "file_changer"
   Device = "filestorage"
   ChangerDevice = "/dev/null"
   ChangerCommand = "/dev/null"
}

Device {
   Name = "filestorage"
   Description = "local storage on tx100:/mnt/tera/bacula"
   MediaType = "File1"
   DeviceType = "File"
   ArchiveDevice = "/mnt/tera/bacula/file"
   RemovableMedia = no
   RandomAccess = yes
   AutomaticMount = yes
   LabelMedia = yes
   Autochanger = yes
   ReadOnly = yes
   MaximumConcurrentJobs = 5
   MaximumSpoolSize = 8000000000
   MaximumJobSpoolSize = 8000000000
   DriveIndex = 5
   VolumeEncryption = "Yes"
}

Storage {
   Name = "tx100-sd"
   WorkingDirectory = "/opt/bacula/working"
   PidDirectory = "/opt/bacula/working"
   MaximumConcurrentJobs = 20
   EncryptionCommand = "/etc/bacula/scripts/key-manager.py getkey"
}

thank you!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.