I haven’t found an answer to this, so asking here.
I was asked if we can change the retention on an existing backup to keep it longer than the original retention time.
For example, we are running forward incrementals daily with a synthetic full every Saturday. The retention is set to 30 days. We are using Veeam 12.1 with immutable Linux repository.
If someone comes to me and asks for us to keep last Wednesday’s backup for 90 days due to an ongoing project they have, can I retroactively change the retention on that backup to 90 days? (I understand that the prior Saturday-Wednesday files would/should also be retained to keep the chain intact).
Otherwise just change the retention number to the new setting. Keep in mind that this will also change the immutable repo retention as well for eventual retention.
also it would be an option to export this specific restore point, with an defined retention.
Otherwise just change the retention number to the new setting. Keep in mind that this will also change the immutable repo retention as well for eventual retention.
In that documentation, I don’t see anything that refers to setting a new GFS policy on a previously created backup point. I could understand that new backups created with that policy would get the GFS setting, but my understanding of how Veeam works, it does not go back and reset the retention on prior backups in a chain. Maybe my understanding is incorrect.
also it would be an option to export this specific restore point, with an defined retention.
This is the option we used since we couldn’t find a way to do it within Veeam. The downside is that we have to remember to manually delete the backup file(s) when they are no longer needed. Not an insurmountable problem, but it just adds to our to-do list.
Otherwise just change the retention number to the new setting. Keep in mind that this will also change the immutable repo retention as well for eventual retention.
In that documentation, I don’t see anything that refers to setting a new GFS policy on a previously created backup point. I could understand that new backups created with that policy would get the GFS setting, but my understanding of how Veeam works, it does not go back and reset the retention on prior backups in a chain. Maybe my understanding is incorrect.
No you are correct on that as it would do it on a go forward basis. So you would need to start it from this point onward.
also it would be an option to export this specific restore point, with an defined retention.
This is the option we used since we couldn’t find a way to do it within Veeam. The downside is that we have to remember to manually delete the backup file(s) when they are no longer needed. Not an insurmountable problem, but it just adds to our to-do list.
What if you did this and created a scheduled task that runs a PowerShell script to remove the files once they are not needed? That might help with automation and save some time.
Is similar to use a full backup based on a specific point in time.
Perfect example of using the Export feature.
I use this often, as well as VeeamZIP, but in your original post you mentioned “existing backup” and things like “last Wednesday’s backup”
If someone asks for 1 time backup of a system due to the fact it’s being decommissioned, or maybe didn’t have backups required in the first place, VeeamZIP will do a full 1 time backup of that VM.
For a system that is already being backed up, or if someone wants to keep one of the already existing backups, this is an ideal solution for Exporting it. This is especially true if it’s from a backup created a few days ago as you can’t VeeamZIP something from the past.
Below I have created a test job and ran 4 incremental backups to simulate 4 days.
To export the job, right click the VM in the Backup or copy job and select Export Backup
Make sure to open the twisty so you can see the actual VM and not the job itself.
When the Export Backup window comes up, choose “Point” to select the restore point you plan to keep. Multiple can be added with the Add button if you want, along with other VM’s.
Select “Last Wednesday's backup” or any other restore point you want to export and click OK
Choose the Backup Repository or local or shared folder you want to keep it in.
At the bottom you can select the retention for how long you want to keep it.
You can even run a File-To-Tape job at this point to get it off your storage if you desire. I often do this when I’m told to delete a VM. I put them in a pool that is kept for a few years. It’s amazing how often people ask about a VM 3 years after it has been removed from production When dealing with many TB’s, tape is a lot cheaper than our Backup Storage.
I’ll add, using the export feature means you won’t have to change your retention to 90 days, or add a bunch of space to EVERY backup job you have as you don’t know which VM they will ask you to do this, or how frequently. You can also keep a backup significantly longer. In the photo above, I could export something for 7 years, and keep my retention of the job low.
When dealing with many TB’s, tape is a lot cheaper than our Backup Storage.