arseable and loadable; If any copy fails you'd want to re-create it from
> other existing copies).
> On 07.08.2020 09:49, a.br...@mail.de wrote:
>
> Thanks a lot, Brock, for your comprehensive post and also to the others. I
> haven't fully worked through your example cases yet, but it
; Client = myth-fd
> Type = Migrate
> Purge Migration Job = yes
> Pool = AI-Consolidated
> Level = Full
> Next Pool = Offsite
> Schedule = WeeklyCycleAfterBackup
> Allow Duplicate Jobs = no
> Priority = 4 #before catalog dump
> Messages = Standard
> Selection Type = Poo
Hello everybody,
I'm in the process of developing a regular backup-strategy and found that I
need some assistance. Here are the parameters in short:
- 35TB of medical imaging data
- daily increment of 50-60GB
- one site, 10Gb/s Backbone
- Overland NEOs LTO7 Storageloader, 8-bay.
attached to
-
