On 10/1/18 7:09 PM, Stieneke, Dan wrote:
> My reason for setting "Max Volume jobs=1" is that migrations will not occur
> unless a tape is marked full, used, or error. To shorten the backup window, I
> back up to striped SSDs, and from there migrate onto tape. Setting max jobs
> to 1 ensures that last disk volume is marked "used", rather than "append". I
> couldn't think of an easier way to do this than setting max jobs to 1; what
> is the preferred way to do it?
>
> My pool definition is:
>
> Pool {
> Name = tempDisk-pool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 5 days # We want to recycle this thing next
> week
> Maximum Volume Bytes = 100G
> Maximum Volumes = 20 # not all of them have to be full
> sized??
> Maximum Volume Jobs = 1 # migrations will not occur unless
> volume marked full,used,error.
> # append won't migrate to prevent
> attempts to read & write simultaneously
> # last volume in set will be
> 'append', unless it's only allowed one job
> Volume Use Duration = 23 hours
> Recycle Oldest Volume = yes # This one respects retention times
> Label Format = "tempDisk-"
> Action on Purge = Truncate
> Storage = File1
> Next Pool = weeklyMain-LTO5-pool
> }
So, let me see if I understand this right.
You're backing up to fixed-maximum-size 100GB volumes on striped SSDs,
with one job allowed per volume (this only one job can run at a time to
that storage), after which you're migrating the jobs one at a time to
tape, and then ... what, recycling the disk volumes? So you're
basically using your SSD pool as a giant spool buffer?
--
Phil Stracchino
Babylon Communications
[email protected]
[email protected]
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
