Thanks again in advance and look forward to being part of the veeam community. My question is that on all of these i'm not sure weather we should be using the synthetic full options or the active full option enabled and also what days those should run as to not overlap? Or a combination of both active and synthetic fulls? (Different run time as to not interfere with the daily and monthly Sunday job) Yearly Full-First Sunday of January-Retention is 5 years or 5 restore points. (different run time as to not interfere with the daily Sunday job) Monthly Full Sunday-first Sunday every month-retention time 12 months or 12 restore points. Tag123 is not a good example of a vSphere tag, but. Veeam is a great example of a category that you could use for tags to power Veeam jobs. Category 5 isn’t a good category name since you really don’t know what it’s going to do. Weekly Full Saturday-Retention time 5 weeks or 5 restore points. You want to use vSphere tags and categories that are descriptive and easy to understand. We have different retention time frames for jobs that would look something like this:ĭaily Job-S-M-T-W-T-F-Retention time 14 days or in veeam terms 14 restore points. I found a couple posts but not exactly my scenario so wanted to run this by the pros here in the forums and see what you thought. Hello everyone, rather new to veeam and have been searching for best practices as far as scheduling jobs goes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |