Hi, consider following setup:
* Storage daemon configured with archive device: /mnt/backup with media
type: file
* Storage daemon connected via 10Gbps Ethernet
* Many jobs. For example: Backup server1, Backup server2, . Backup server70
* Each server has its own volume pool: server1-fd-Pool, server2-fd-Pool, .
server70-df-Pool
This configuration worked great but the problem was the jobs are running
consecutively and would run sometimes several days (in case of full backups).
Seeking for an option to run the backup jobs in parallel I created
4 Device definitions on the storage daemon and 4 storage definitions on the
director:
On Storage daemon:
* Device { Name = Backup_01; Archive device = /mnt/backup; media type = file;
[...]}
* Device { Name = Backup_02; Archive device = /mnt/backup; media type = file;
[...]}
* Device { Name = Backup_03; Archive device = /mnt/backup; media type = file;
[...]}
* Device { Name = Backup_04; Archive device = /mnt/backup; media type = file;
[...]} On Director:
* Storage { Name = Storage_01; Device = Backup_01; [...]} ...
* Storage { Name = Storage_04; Device = Backup_04; [...]}
The pools were randomly configured to use either Storage_01, Storage_02,
Storage_03 and Storage_04 --> Now 4 jobs are running in parallel which is
almost perfect.
The problem with this configuration is: Whenever a new server is being added to
be backed up, we manually must choose a storage (01-04) which is all but
perfect.
Is there a way to configure/modify the job scheduler in order it assigns one
storage after the other to the scheduled jobs? Could this be done using plugins?
Is there some other nicer way to more or less automatically balance the jobs to
the available storages?
Bruno
--
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 [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
