Backup VBO Repositories?

[Stibo]

Hello fellow VBO users,

I've just finished my testing phase with VBO and we're planning to deploy it within our environment. I was wondering whether we should backup the backup repos themselves in case something was to happen to the system VBO is running on? Is this even supported? Does any of you guys do this already?

Thanks in advance for any reply!

[nielsengelen]

Hi and welcome to the forums!

This is fully supported by using Veeam Backup & Replication or Veeam Agent for Windows. You can find some more information in our best practices guide.

[Stibo]

Hi and thanks,

thanks for your reply, I will have a look into this!

[Stibo]

I've got one more question: I was asked whether it was possible to put the repositories on a SMB share. After reading some KBs and topics in this forum, I understand that it is experimental but fully supported.

How would I backup those shares? My idea is to backup the VBO VM with Veeam B&R and the files on the share as they are (e.g. any copy tool). Would the restored VM be able to mount that shares again?

[nielsengelen]

Keep in mind VBO uses a live database in the background. An option would be to use NAS backup introduced in v10 to back up the SMB share however I would do some testing with a test server to see if it gives the desired outcome.

[stevekarra]

The VBO docs https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=40 says "... To use SMB 3.0 ..." - does that imply that it's possible to use an SMB 2.x target for VBO?

I would like to use a PBBA appliance that supports SMB 2.1

[nielsengelen]

SMB3 is the minimum version required.

[stevekarra]

Cool, thanks.

[jveerd1]

any thoughts on how to backup the data stored in the object storage repository?

[Polina]

Native cross-region replication and geo-redundancy already make cloud platforms highly resilient; and along with access control, backup data in object storage is quite safe.
Even in the event of a VBO server/proxies loss, backups residing in an object storage repository stay undamaged and can be easily retrieved by adding the existing object storage repository to a fresh VBO installation.

[jveerd1]

I agree object storage is highly resilient, but I am thinking about protecting the object storage repository against human error like deletion of the object storage repository or the malicious admin.

[jimmyhurr]

What I do is this (after posting a similar question veeam-backup-for-microsoft-office-365-f ... 62930.html):

VBO backs up to local repo.
Machine on which VBO is running is entirely backed up using Veeam Agent for Windows - this backs up to a NAS SMB network share.
The NAS is backed up to rotated external USB drives and AWS S3.

I'm also experimenting with VBO object repos direct to AWS S3. Not got it right yet though.

[nielsengelen]

James, what exactly isn't working regarding AWS S3?

[jimmyhurr]

You've answered it Niels in the other thread : veeam-backup-for-microsoft-office-365-f ... 65739.html. Thank you!

[jveerd1]

What is your backup strategy of the object storage repositories when you move them to AWS? You do not take a backup anymore?

[Helferlein]

I am planning to use Veeam VBO as a VM on a HyperV Cluster and three repository disks attached by iSCSI to it.
To backup now the whole VBO Server with VBR this might not be possible as normal HyperV Snapshot since it does not see the iSCSI disks as read in other thread.
It would actually work with the Veeam Agent for Windows.

Is this recommended as well for Veeam VBO Server, backing it up with Veeam Agent?