There is a backup server with Veeam B&R and a target machine (I will call it BD1) where files are stored, they need to be backed up. On the BD1 machine, a copy of the databases is created once a day, this copy should be taken by Veeam B&R and stored for at least a year, the database file on DB1 is deleted after a backup on VeeamB&R, and this should happen every day. How to configure the retention policy correctly?
Each file should be stored for at least a year, it turns out that a full backup with a retention of 365 days should be done every day? If you do an incremental (.vib), then if one element from the chain is accidentally lost, there will be problems with data recovery, as I understand it.
Another option: Make a synthetic backup for 7 days and the retention should be 8 days (on the 8th day, the old chain will be cleared). On the 7th day, a full copy will be created from increments. After that, "Backup Copy" will be launched and a weekly backup with a retention of 1 year will be saved.
I would be very grateful if you could help me understand how retention policies work.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jan 09, 2025 3:55 am
- Contact:
-
- Veeam Software
- Posts: 2597
- Liked: 606 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: File level backup
Hi Artem, welcome to the forums.
I would consider an Unstructured Data Backup Job and backup the DB dumps as files. Given the specificity of your retention needs, I think this does it better as the retention will be applied per file version. You can configure secondary copies for the Unstructured Data Backup as well, as well as tape-out if you will archive to tape.
I think this will handle your retention needs for the DB dumps a bit better without a lot of planning, and also allow for secondary copies.
I would consider an Unstructured Data Backup Job and backup the DB dumps as files. Given the specificity of your retention needs, I think this does it better as the retention will be applied per file version. You can configure secondary copies for the Unstructured Data Backup as well, as well as tape-out if you will archive to tape.
I think this will handle your retention needs for the DB dumps a bit better without a lot of planning, and also allow for secondary copies.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: No registered users and 8 guests