Storage clustering for B&R

[BUUKInfrastructure]

Really just a thought but i'll be damned if i can find an answer.

We have a number of ubuntu boxes which are just storage for veeam, we are seeing the estate grown and managing data across them is becoming painful. I'm wondering if anyone has clustered their storage and how it performed?

[Mildur]

Hi,

Why not using them as linux hardened repos in a SOBR?
Veeam will distribute the backups across all ubuntu boxes.

[BUUKInfrastructure]

Sorry for not coming back sooner, the world descended upon me and this took a back seat lol.

The problem with SOBR is that the business has a requirement of backing up the backups which if i'm right SOBR doesn't support, currently it looks like this: -

VM1 >Hardened Job> DC1 Repo 1 >Copy Hardened Job> DC2 Repo 1

So currently i have 5 Repos at the local DC and another 5 at a remote DC, depending on VM local depends on where it gets backed up to first as part of a BC/DR tool.

[Mildur]

Sorry for not coming back sooner, the world descended upon me and this took a back seat lol.
No issue Hopefully everything is back at it was.

backing up the backups

You can create two SOBRS (with 10 extends, I think you must use veeam enterprise Plus edition).

SOBR1 with 5 extends in primary datacenter.
SOBR2 with 5 extends in remote datacenter.
- Backup Job targets SOBR 1.
- Backup Copy Job targets SOBR 2.

SOBR as a backup copy source should not be an issue. I will check in 60 minutes when I‘m back at my work place.

Or use a veeam capacity tier to offload (copy policy) the backups to a s3 storage.

[BUUKInfrastructure]

Oooo just looking and i misread about the copy it called it a limitation but i guess that means if i have a job going to SOBR1 consisting of HBR1-5 then i can't do a copy job specifically to HBR3 for example.

I need to build a lab for this but looks like it's what i'm after, need to see if i can switch the HBR to SOBR without data loss and if the immutability will live on (then have it all Pen Tested *sigh*)

[Mildur]

I will check for you in my lab 10-15 min away.
I‘m not sure either, never done a backup copy job from a SOBR.

[Mildur]

I can confirm, Backup Copy Job works. Tested with VMs Backup Copy Job:
- SOBR to SOBR
- SOBR to Simple Backup Repo

Can you show me the link, where do you have read about such limitation?

[BUUKInfrastructure]

Thats brilliant!!!

To be fair it was a while ago i read the documentation (this time last year actually) more than likely i misread something

[Mildur]

Could be, that you read about VM copy jobs.

If you want to go forward to using SOBRs, make sure you have a veeam enterprise plus license.
Either Sockets or VUL. VUL always have the entire feature set available.
Starting at July, VUL is the only license you can get if you need to buy new licenses. For socket based licensing, only maintenance renewal will be available.

Enterprise edition users can create 2 SOBRs with three active extends. With Enterprise Plus, you don't have this limitation.
Feature Comparison

[BUUKInfrastructure]

I have Ent plus.

Does the immutable storage policy still apply to the SOBR?

Ignore me. Should have read https://helpcenter.veeam.com/docs/backu ... ml?ver=110

As the retention policy is applied to the underlying HBR it is on the SOBR

[Mildur]

Cool.
Yes, Immutability works as normal. Only exception if you use S3 Object Storage with the move policy as a caapcity tier behind the SOBR.

If you don‘t use a capacity tier, Immutability works as normal.
Short Term Retention is immutable for the configured value.
Long Term Retention (GFS) backup files are immutable for their entire retention period.