Scale Out Repository

[storageguy]

Hi,

Can i convert a regular backup repository to a scale-out repository and how to do it?

Thanks

[Dima P.]

Hi storageguy,

You can add simple repository to a scale-out repository as one of the extents. Cheers!

[storageguy]

Hi Dima,

Will this procedure convert my regular backup repository to a scale-out repository? Right now I only have one regular backup repository that I want to convert to scale out repository for future scalability.

Regards,

[Gostev]

It is more correct to say that your backup repository will become an extent of the new scale-out repository. It will not be usable as a "regular" backup repository once that happens, if this is the question. But of course you can always create another "regular" repository pointing to a different folder on the same physical storage.

[storageguy]

Hi Gostev,

So if my current regular backup repository will become an extent of the new scale-out repository, what then will happen to my backed-up data stored in my regular repository? Will it become unusable?

[Gostev]

No, of course not.

[storageguy]

Hi Gostev,

Will it not change my backup mapping? Will my backup server still going to continue using that location for my backup data even-though that repository is now an extent of a scale-out repository?

What worries me is if after my regular repository becomes an extent of a scale-out repository, that my backup jobs can no longer finds it's target repository and I have to do remapping again of my backups.

[Gostev]

Yes, it goes without saying that you will need to update your backup jobs to use the new (scale-out) backup repository.

[storageguy]

So I'm trying to create a scale-out backup repository and adding my existing backup jobs target simple backup repository to it but an error window pops out saying
"Unable to add extent Backup Repository because it serves as the target for one or more job types which are not supported by a scale-out backup repository"

Any suggestions?

[Gostev]

Edit the incompatible jobs listed in the message box and have them use another simple repository?

[storageguy]

There is no incompatible jobs listed in the message box, just the error message.

[mkh]

sounds like you have the config backup targeted to that repository.
the config backup cannot be targeted to a scale-out backup repository, so you will have to target that somewhere else

Also when you add the normal repository to the scale out repository, it will remap the backups automaticly.

[Gostev]

Ha! Perhaps we found a bug then: the configuration backup job is not shown in the list of jobs in the error message details? And when it is the only "conflicting" job, there are no Show Details section on this message box at all? We will try to reproduce and fix this in v11.

[Gostev]

Actually, we can't seem to reproduce issue: configuration job is displayed even when alone.
@storageguy can you please share a screenshot of the error message box you get?

[storageguy]

Gostev, I may have overlooked that lists but after removing the backup configuration it went without errors

[crackocain]

Hello

I want to discuss Scale Out Backup Repository licensing. In Enterprise we have 3 + 1 maintenance extent. Enterprise Plus is unlimited.

If one customer use 5 extent in Enterprise license then they attach to disk Linux LVM and combine everything. (or Windows Dynamic volume) iSCSI, FC or FCoE. Or 6 storage device in 3 extent for maintenance.

Thats why like SureBackup, SOBR with unlimited extent should be in Enterprise and Enterprise Plus license.

The point I want to mention is that there is no reason for customers with Enterprise licenses to upgrade. (Considering SOBR)

[Gostev]

Hello! This will not change as we don't do editions any longer in principle, see my earlier response in another thread. Thanks!

[albertwt]

Hi,

Can we mixed several hardware types into SOBR like below:

Performance Tier: HPE Lefthand iSCSI
Capacity Tier: HPE MSA
Archive Tier: QNAP NAS and Synology NAS

As I cannot find it under https://helpcenter.veeam.com/docs/backu ... ml?ver=110

[Mildur]

No,
You can mix the different hardware types, but only in Performance Tier.
Capacity Tier needs to be an Object Storage.
Archive Tier is only supported/developed for Azure or AWS Archive Storage.

Capacity Tier:
- S3-compatible object storage repository
- Amazon S3
- Microsoft Azure Blob Storage
- Microsoft Azure Data Box
- IBM Cloud Object Storage
- Google Cloud Object Storage

Archive Tier:
- Amazon S3 Glacier
- Microsoft Azure Archive Storage