Concurrent jobs on different clients and on different storage devices not running at the same time

[Ramil]

Why are concurrent jobs that run on different clients and on different storage devices not running at the same time?

Dir->Storage:
Storage {  
 Name = BareosStorage
 Address = 10.64.116.172        
 Password = "LhEbHl35nvQyUnYqcenMs/ECUpIDmtlW+NbECHorrITE"
 Maximum Concurrent Jobs = 100  
 Device = BareosStorage
 Media Type = File
 TLS Enable = no
 TLS Require = no
}
Storage {
  Name = TapeLibrary  
  Address  = 10.64.116.172
  Password = "LhEbHl35nvQyUnYqcenMs/ECUpIDmtlW+NbECHorrITE"  
  Maximum Concurrent Jobs = 100
  Device = autochanger-0  
  Media Type = LTO-8
  Auto Changer = yes  
  TLS Enable = no
  TLS Require = no}

Sd->Device:
Device {  
  Name = BareosStorage
  Media Type = File  
  Maximum Concurrent Jobs = 100
  Archive Device = /mnt/backups/bareos_backup
  LabelMedia = yes;                  
  Random Access = yes;    
AutomaticMount = yes;              
RemovableMedia = no;

Device {
    Name = "tapedrive-0"
   DeviceType = tape
    DriveIndex = 0
    ArchiveDevice = /dev/tape/by-id/scsi-350014380272e92b0-nst
    MediaType = LTO-8
    AutoChanger = yes                          
   AutomaticMount = yes
    Label Media = yes  # Check Labels = yes                  
    Maximum Concurrent Jobs = 100
    AlwaysOpen = yes
    Maximum Spool Size = 200G
  Spool Directory = /mnt/backups/spool

Autochanger {
  Name = "autochanger-0"
  Changer Device = /dev/tape/by-id/scsi-350014380272e92ac-changer
  Device = tapedrive-0

# Device = tapedrive-1

   Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
}
 

Dir->Job:

Job {
  Name = "Test_Tape-job"
  Type = Backup  
  Client = hl-bareos-sd01
  Level = Full  
  FileSet = "TapeTest"
#Schedule = "WeeklyCycleAfterBackup"  
  Storage = TapeLibrary
  Messages = Standard  
  Pool = ORA_DB
  SpoolData = yes
  Priority = 13  
  Maximum Concurrent Jobs = 100
  Full Backup Pool = ORA_DB
  Write Bootstrap = "/var/lib/bareos/%c.bsr"


Job {
  Name = "BackupCatalog"
  JobDefs = "DefaultJob"
  .........
}  
JobDefs {  

  Name = "DefaultJob"
  Type = Backup  
  Level = Full
  Client = bareos-fd
  FileSet = "SelfTest"                    
  Schedule = "WeeklyCycle"
  Storage = BareosStorage  
  Messages = Standard
  Pool = Incremental  
  Priority = 10
  Write Bootstrap = "/var/lib/bareos/%c.bsr"  
  Full Backup Pool = Full                  
  }

[Brock Palen]

Jobs with different priorities won’t run at the same time unless you update a setting (forget which) that allows it.

The stock config the catalog backup is set to run after other backups have ran.

I don’t use the web UI but is bconsole

status dir

Will often show “waiting on higher priority jobs to finish”


Brock Palen
bro...@mlds-networks.com
www.mlds-networks.com
Websites, Linux, Hosting, Joomla, Consulting

> On Jul 3, 2023, at 3:39 AM, Ramil <agishe...@gmail.com> wrote:
>
>
> Why are concurrent jobs that run on different clients and on different storage devices not running at the same time?
>

> --
> You received this message because you are subscribed to the Google Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/c3ce0bd5-8bcb-47dd-afc1-8ebc74ce44a6n%40googlegroups.com.
> <photo_5265031813976413692_w.jpg>

[Ramil]

You are right. It was a matter of priority. I started the task with lower priority first. After setting the same priority, everything worked. Thank you very much!

понедельник, 3 июля 2023 г. в 19:54:47 UTC+6, Brock Palen: