Skip to main content
  • EN

Hi all, 
 

i’d like to clarify a best practice scenario for SOBR with Azure Blob storage.


Environment (short)

  • Veeam B&R v12.x — SOBR: Perf = Data Domain, Capacity = Azure Blob Cool (immutability 25 d + 10 d block generation), Archive = Azure Archive.

  • GFS: Weekly 5 weeks, Monthly 7 months (~210 d).

  • Goal: 30 d in Cool, then ≥ 180 d in Archive (Azure minimum).

Candidate options (please advise which is best practice)

  • Option A (simple & compliant, slight extra Cool cost):

    • Keep Monthly = 7 months and Archive-after = 30 d.

    • Keep immutability 25 + 10 = 35 d (Capacity cleanup deferred until D+35; ~5 extra Cool days).

  • Option B (cost-optimized, if security allows):

    • Set immutability = 20 + 10 = 30 d to align with Archive-after = 30 d,

    • keep Monthly = 7 months.

  • Option C (if keeping immutability 35 d and/or Archive-after 35 d):

    • Increase Monthly = 8 months (~240 d) to stay ≥ 180 d in Archive in all cases.

Question: Which option would you recommend as best practice (compliance + cost) for this use case, and why?

Thank you 

Check these posts on the community - https://community.veeam.com/blogs-and-podcasts-57/sobr-archive-tier-explained-and-configured-part-2-of-4-3502

 

i would suggest to use option B - this is what i provide as well

95% of restore are from last 3 days

GFS is immutable automatically

30 days of immutable backup is ok

35 days was used from another backup product, where each restore point was expiring based on date was made. In Veeam is different, until last restore point from last chain will not expire, entire chain is there. So you are able to restore from 30th day as well

Hi ​@abdelali.elkouri I think it's important to consider the repository consumption into your equation. You can use the Veeam calculator with the parameters for each option to determine the exact size of your repositories. The calculator is quite simple to use.

Here is the calculator’s link:
https://www.veeam.com/calculators/simple/vbr/machines



And also, the block size for your repo is important, as big as the block size is, less I/O you have and more space you spend. as smaller as the block size, more I/O you have and less space you spend.

 

The Veeam Calculator works great, but base it on your  environment. 

For myself, I’m often restoring stuff a few weeks old, but after that it’s rare. I backup to a SOBR, then copy job to immutable disk. the immutable storage keeps weekly and monthly jobs for much longer.  

From your storage, you can offload to Azure, or Tape, or any other type of long term retention as well to mee your own policies. 

If you find yourself restoring files often, try and keep more backups on hand. Pulling things back from slower disk or archive tiers my end up taking long, or costing more than having the data on hand for a longer retention. 

Comment


Terms & Conditions