Hi David,
thanks a lot.
I was just looking at the second solution, and I think it is the most functional and practical to use.
I've already created a CopyJob by duplicating one, and implementing the Monthly in the GFS instead of the Weekly that I had before. I set it as LAST, which should be what I need.
So if I understood correctly, both from what you wrote to me, but also from what is written on the Veeam site (your link), I will have a FULL with a large chain of incrementals until the next FULL generated by the GFS Monthly. The old chain will then be deleted when the new chain has enough saves corresponding to the value of the Retention.
This will allow me to have less FULL and improve the management of the S3.
correct?
Thanks again
thanks a lot.
I was just looking at the second solution, and I think it is the most functional and practical to use.
I've already created a CopyJob by duplicating one, and implementing the Monthly in the GFS instead of the Weekly that I had before. I set it as LAST, which should be what I need.
So if I understood correctly, both from what you wrote to me, but also from what is written on the Veeam site (your link), I will have a FULL with a large chain of incrementals until the next FULL generated by the GFS Monthly. The old chain will then be deleted when the new chain has enough saves corresponding to the value of the Retention.
This will allow me to have less FULL and improve the management of the S3.
correct?
Thanks again
Statistics: Posted by GianlucaCroci — Jun 30, 2025 10:16 am







