![]() ![]() Shows you the recommended RAM, cores, proxies, repositories, jobs and so on. This tool help you to calculate the hardware resources you need, according you environment. I'd be interested to hear in how others have setup their job and retention or best practice. Are you planning a Veeam Backup deployment Do you want to improve jobs’s settings Keep in mind these sizing tools: Virtual Architect. vrb files containing content deleted for up to 90 days? Would I be correct in saying with forever we'd end up using the initial full backup + data churn over the 90 days at a block level so we shouldn't expect that much use? Would reverse incremental be a safer way of doing this having a newer full backup file then 90 days retention set to clear out. Having not used reverse incremental or forever incremental before these sound like possible solutions. We have around 25TB when compressed currently on weekly backups.ĭue to the 90 day minimum retention period I'm debating the best way to set this up? If we did weekly full backups and daily incremental with SOBR using onsite storage as the performance tier and a Wasabi Immutability for Capacity Tier would end up paying for each weekly backup worth of data on Wasabi for the full 90 days, potentially 12x25TB? Veeam® Backup for Microsoft 365, the leader in Microsoft 365 backup with over 11M users protected, eliminates the risk of losing your Microsoft 365 data, including Exchange Online, SharePoint Online, OneDrive for Business and Microsoft Teams - so that your data is always protected and accessible. The only question remaining is calculating the correct amount of storage for costing. ![]() I'm looking at switching our current on prem backup exec and tapes to Veeam with use of Wasabi immutable storage.
0 Comments
Leave a Reply. |