[V13] "High Availability functionality requires VSA 13.0.1 and VDP Premium edition"

[mkretzer]

Hello,

now that we migrated to VUL i was looking forward to using the VSA in HA mode - until i read the what's new document: "High Availability functionality requires VSA 13.0.1 and VDP Premium edition".

Does that really mean i need another license? What exactly does this mean?

Markus

[Gostev]

Hi, Markus.

It means exactly that: if you don't have VDP Premium edition license then you can't use VSA in HA mode.

From my memory of writing the What's New document, I believe this is actually the only new V13 feature that is not available in the core offering (which is VDP Foundation edition). I recall a few other new features were considered for VDP Advanced edition, but in the end it was decided to put everything into Foundation.

Thanks

[mkretzer]

How does the upgrade to VDP Premium work when you have the discount of a Socket to VUL Migration? Does that mean we no longer benefit from that?
The upgrade is per VUL license?

[Gostev]

Remember we're with R&D you should be discuss licensing with your Veeam sales rep as always.

[mkretzer]

To wrap up the topic: The discount you get with VUL migration carries over to the upgrade.
I find this extremely fair from Veeam!

[wuweijava]

If I need to enable the HA function, does the license file need to be the official version? I can't see the HA function with my test license.

[Mildur]

Hello,

HA will be released with version 13.0.1 and will require VDP Premium (as mentioned on page 8 of What's New in V13).

Trial licenses should be able to test all functionality in the product.
I recommend trying again once v13.0.1 is released.

Best,
Fabian

[NightBird]

Hello all,

I have a little question, Hight avaibility for VSA, just for management Veeam Server and enterprise manager I think.

But what about repository side ? imagine 2 DC (DC1 and DC2), with management high available VSA HA, but how to do a high available repository, so if DC1 is down, backups continues to work ?

Because one job point to one repository,if repository is VIA base, if I lost DC1, I lost VIA repository in DC1 and jobs pointing to them...
Or may be with an horizontal SOBR with "continue backup if I lost extent... checked" ? no idea of that.

Thx

[Gostev]

For highly available repository we recommend S3-compatible object storage with node loss protection. Which is literally every object storage available on the market except Object First and those SOHO NAS with S3 protocol bolted on just to check the box in the protocol support matrix.

One big reason of our push for object storage support as a backup repository was because of native checksumming, redundancy and high availability which together make the perfect combo as an Enterprise backup target. While surely we could build our own HA repository, it just does not worth the time with so many options readily available, from commercial to free. Best we focus on backup and let someone else do storage!

Plus we somehow got to 2B of annual revenue without this feature, which also shows that the need for HA backup target is not too common. This is likely because most of our customers are required to copy their backups for DR and compliance with 3-2-1 rule anyway, so the loss of primary backup repository is never a big issue.

Let's not hijack this discussion about HA for VSA though

[ftravinsky]

Still,

Is SOBR repository a redundant solution to a degree that backup job will continue if one repo is temporary down?

[Gostev]

Yes, you will see the corresponding option for that in the advanced SOBR settings.

[mkretzer]

What will this option do?