Upgraded to v4 and Added S3 Bucket

[kha]

I upgraded to v4 of VB for Microsoft Office 365. I upgraded the Backup Disk. Everything is fine.
Today I'm adding an Object Storage Repo. I got it connected to an S3 Bucket and it looks like it's happy. It created the folder structure so it's communicating and read/write is there.

Now, I have a couple questions:

1. When I try and create a new backup job and go to select a Backup repository, the S3 bucket is not listed. I only have my local disk listed. I've rebooted and rescanned and still the same. Is there a trick I need to do to see the online repo? I'm following the official guide here: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=40

2. Is there a way to "move" my existing backup repo from local disk to this S3 bucket? I don't want to delete and re-create the job. The reason, is that I have old objects backed up in the backups and they are deleted from Office 365. So if I lose my local disk repo those backups are gone. How do I "move" the existing repo to online?

Thanks!
Kevin

[kha]

Ok, looks like I have to create a brand new backup repository and extend it with the online repository. So I think that answers question #1.

How about question #2?

[Mike Resseler]

Hi Kevin,

Yes, it is possible through PowerShell (Since this is normally a one-time operation only. In fact, we are finalizing a KB that will give you step-by-step instructions on how to do this.

Brgds,
Mike

[Polina]

The KB is now finalized and available at https://www.veeam.com/kb3067

[kha]

Great! Thanks for the information.

I think I understand, but there could be some clarifications in the KB article.
For example, it says: $target = Get-VBORepository -Name "Object Storage Repository Name"
Shouldn't the $target be the new backup repository I created that was extended with Object Storage? Not the Object Storage Repository directly?

When creating a new backup repository with an Object Storage extension, only metadata is stored locally? The bulk of data is stored in the object store? This means the local cache won't be that large, correct?

[nielsengelen]

Correct, the target is the new backup repository which will offload the data.

Local cache will indeed be small and just contain metadata.

[kha]

Awesome. Thank you for the info.