We do not have great governance instruction in terms of recovery point/time objectives or retention periods…so when we implemented Unitrends last year, we more or less set it up to do what we did with tape only disk to disk. We have daily jobs running on two Hyper-V hosts and all the VMs on them. We also have a backup copy job taking fulls to a NAS on top of that. We struggled with space and set our retention periods to be 1 or 2 weeks on both the internal storage and the NAS copy.<\/p>\n
Advertisement
Now I’m trying to understand the more sophisticated features, and I find the effect of retention settings to be a little confusing. Even though retention on the assets is set at 2 weeks max, the jobs are set to remove older backups, when I look at the sets on the backup copy target NAS, I see dates as far back as August 2018. In the backup catalog, with date filters removed, I see recovery options as far back as about 4 weeks.<\/p>\n
Advertisement
I wanted to do some planning for next year’s budget to increase capacity in order to increase retention, but I already see more backups being retained than I thought were configured and I’m struggling to sort out the capacity. I understand that the idea is probably that I have my business needs well defined, I have recovery objectives and retention policies set based on governance reality, and the system is very smart and I don’t have to think so much. However, in the absence of those definitions I think I have to think so much…and I’m having trouble trying to be smarter than the system.<\/p>\n
Can anyone enlighten me a little? Let me know if too confusing or vague. Thanks.<\/p>","upvoteCount":2,"answerCount":5,"datePublished":"2018-10-15T14:01:57.000Z","author":{"@type":"Person","name":"lisastratton3609","url":"https://community.spiceworks.com/u/lisastratton3609"},"acceptedAnswer":{"@type":"Answer","text":"