by ANI » Thu Sep 15, 2016 9:31 am people like this post
I am working on Backup architecture and administration and i have a new project. I am studying the possibility to backup remote site with physical servers in centralized in our DataCenter.
I am trying Veeam Endpoint and it seems to work fine. This backup is used to backup only specific and important folders so we are in "File Level Restore" backup mode. For my test i have only 15 days retention but according to last meeting on the project, the retention could be one year. I have a doubt on the capability of Veeam Endpoint to make merge successfully after one year of backup.
by PTide » Thu Sep 15, 2016 11:45 am people like this post
Merging will affect only .vbk and the subsequent .vib, that is not a problem. The real problem with 365 days retention is that if any .vib gets corrupted you'll not be able to restore anything past that .vib. I suggest you to start a new backup chain (will require you to reconfigure the job) once in two or three weeks to lower the risk.
by Mike Resseler » Thu Sep 15, 2016 1:25 pm people like this post
If your project has a bit more time, you might want to learn about version 2.0 (which will rename VEB to Veeam Agents for Windows) which will give you more scheduling capabilities and application aware processing. More information can be found here: https://go.veeam.com/launch-event
by Vitaliy S. » Thu Sep 15, 2016 3:46 pm people like this post
Not sure if you have Veeam B&R or not, but if you do, just point your VEB jobs to a backup repository, continue using 14 days of retention policy and configure a backup copy job in Veeam B&R with GFS retention policy. This will allow you to have 1 year of retention policy and store data in the archival repository.