This will give us a foundation from which to begin our retention discussion in subsequent posts.įrom the Veeam User Guide, a Backup Copy Job allows you the ability to create several instances of your backup data in different locations, whether onsite or offsite, for long-term storage, to help you meet the 3-2-1 Rule In this Part I post, I thought it would be best to share explicitly what Veeam states Copy Jobs are, then move on to their requirements, as well as some considerations and limitations. I will tackle this topic in a “3-part” series of posts – Part I Intro, Part II Short-Term Retention, and Part III Long-Term (GFS) Retention. And with the changes brought to Copy Jobs with the release of Veeam v11, I believe things got worse instead of better. As such, I thought it would be beneficial to the Veeam Community for me to go through the Backup Copy process from a deep-dive perspective, and see if I can make a bit more clearer sense, for myself and the Community, of how Backup Copy Jobs retention works.
The most difficult to understand about Copy Jobs in my opinion is how the retention algorithm works when using the GFS (grandfather-father-son) archive option. Easy, right? Well, when you look under the hood of the technology behind the retention, scheduling, interval, etc. things start to get murky pretty quick, at least for me. On the surface, they’re easy to understand – you create a Copy Job, use some supported backup source, and copy this source VM data to a designated target to implement part of the 3-2-1(-1-0) Rule – have multiple copies of your data and/or at least 1 offsite copy of your data. One of the biggest mysteries of Veeam’s list of features in my opinion is the Backup Copy Job.
0 kommentar(er)
