Re: 'Lock' retention on a media...

Mandi! Rob Gerber
  In chel di` si favelave...

Thanks for your previous message, full of invaluable info!

> However, I have an idea. If you have some pool like 'Archive pool' and you
> set in that pool File, Job, and Volume retention to some very long period,
> like 1000Y, then if you migrate jobs you want to archive to that pool, *I
> think the migrated jobs should inherit the new pool's retention period.* I
> believe it should work, because pool retention periods override retention
> periods from all other sources, and jobs migrated to a pool should
> certainly inherit the settings from that new pool. *You would have to test
> to confirm this does work as expected.*

Uh. Oh. But why not simply move the media to the archive pool?

My main pool is a 'normal' one:

 Pool {
        Name = FVG-SV-SVPVE3LTOPool
        Pool Type = Backup
        Volume Use Duration = 10 days
        Recycle = yes
        AutoPrune = yes
        Action On Purge = Truncate
        Volume Retention = 20 days
 }

I've setup an archive pool:

 Pool {
        Name = FVG-SV-SVPVE3ArchiveLTOPool
        Pool Type = Backup
        Volume Use Duration = 7 days
        Recycle = no
        AutoPrune = no
        Volume Retention = 10 years
        Job Retention = 10 years
        File Retention = 10 years
 }

documentation say me that i can set 'Job Retention' and 'File Retention' on
a pool, and effectivaly 'lock' job and file retention for the media of that
pool.


So i've done:

 *update volume=SVPVE3_0001 pool=FVG-SV-SVPVE3ArchiveLTOPool
 New Pool is: FVG-SV-SVPVE3ArchiveLTOPool

 *list media pool=FVG-SV-SVPVE3ArchiveLTOPool
 +---------+---------------------+-----------+---------+--------------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+-------------+
 | mediaid | volumename          | volstatus | enabled | volbytes           | volfiles | volretention | recycle | slot | inchanger | mediatype | voltype | volparts | lastwritten         | expiresin   |
 +---------+---------------------+-----------+---------+--------------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+-------------+
 |     775 | SVPVE3_0001         | Archive   |       1 | 10,554,477,517,824 |      156 |    1,728,000 |       1 |    0 |         0 | LTO       |       2 |        0 | 2025-03-14 06:16:49 |           0 |
 |   1,333 | SVPVE3_Archive_2025 | Append    |       1 | 10,146,988,299,264 |      149 |  315,360,000 |       0 |    0 |         0 | LTO       |       2 |        0 | 2025-06-12 09:53:51 | 315,247,842 |
 +---------+---------------------+-----------+---------+--------------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+-------------+

 *update volume allfrompool=FVG-SV-SVPVE3ArchiveLTOPool
 All Volume defaults updated from "FVG-SV-SVPVE3ArchiveLTOPool" Pool record.
 
 *list media pool=FVG-SV-SVPVE3ArchiveLTOPool
 +---------+---------------------+-----------+---------+--------------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+-------------+
 | mediaid | volumename          | volstatus | enabled | volbytes           | volfiles | volretention | recycle | slot | inchanger | mediatype | voltype | volparts | lastwritten         | expiresin   |
 +---------+---------------------+-----------+---------+--------------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+-------------+
 |     775 | SVPVE3_0001         | Archive   |       1 | 10,554,477,517,824 |      156 |  315,360,000 |       0 |    0 |         0 | LTO       |       2 |        0 | 2025-03-14 06:16:49 | 307,462,368 |
 |   1,333 | SVPVE3_Archive_2025 | Append    |       1 | 10,146,988,299,264 |      149 |  315,360,000 |       0 |    0 |         0 | LTO       |       2 |        0 | 2025-06-12 09:53:51 | 315,247,790 |
 +---------+---------------------+-----------+---------+--------------------+----------+--------------+---------+------+-----------+-----------+---------+----------+---------------------+-------------+

so, move the media to the new pool, and the reapply media parameter of the
new pool.


Unfortunately jobs and file are just expired for 'SVPVE3_0001', so i cannot
test anymore, but i think will suffices...

--