Doesn’t work,
During the consolidation of a full, you have to read back from teh full pool
and write to the full pool. So you always need to have 2 working devices, one
to read, one to write to the AI-Consolidate pool.
That’s why in my setup tape is really a pool to ‘migrate to make space’
On Sat, Dec 23, 2023 at 17:21 Brock Palen wrote:
> Correct. Because when you run your consolidate with a full it has to read
> the old full likely from your tape drive. So it has to write to disk.
>
What if I flip things around: use disk for incrementals and tape for full?
Would I then just
Correct. Because when you run your consolidate with a full it has to read the old full likely from your tape drive. So it has to write to disk. Sent from my iPhoneBrock PalenOn Dec 23, 2023, at 3:43 PM, Russell Harmon wrote:On Sat, Dec 23, 2023 at 10:49 Brock Palen
On Sat, Dec 23, 2023 at 10:49 Brock Palen wrote:
> I do this and it works but it has some bugs that are reported but not had
> progress in few years.
>
> My setup is:
>
> Disk Pools:
> AI-Incremental
> AI-Consolidated
>
> Tape Pool:
> LTO
> Offsite
>
> I run the AI setup on the disk pools but I
I do this and it works but it has some bugs that are reported but not had
progress in few years.
My setup is:
Disk Pools:
AI-Incremental
AI-Consolidated
Tape Pool:
LTO
Offsite
I run the AI setup on the disk pools but I use a Migration Job to migrate
AI-Consolidated jobs to Offsite.
This is