Skip to main content

Object First storage is used in our main data center.

Regional backups are first stored locally, then copied to Object First at the main site using a forever incremental job (using Scale Out repo and Object First configured as capacity tier)

Now If full backup data needs to be sent to AWS (e.g., when decommissioning a regional application server), it can be done from the main site through a secondary copy—without using the regional office’s primary copy.

The answer is it depends based on your configuration but you should be able to accomplish this.  Is there a VBR server in the primary office or just the regional office?  You could use AWS as archive tier as well.


@dlinfrastructureteam If I understood your needs well, I thonk you can use the BCJ for that.

BCJ allows to copy content from Jobs or Reposotories as a source, so you can select one specific repo to create your secondary copy.

see the screensht below.

from Repo

Let me know it fits for you.


@dlinfrastructureteam If I understood your needs well, I thonk you can use the BCJ for that.

BCJ allows to copy content from Jobs or Reposotories as a source, so you can select one specific repo to create your secondary copy.

see the screensht below.

from Repo

Let me know it fits for you.

If they are using the object storage in a scale-out repository as a capacity tier, only the scale-out will show as an option to select as a source, and it would almost definitely pull from the performance tier when doing a backup copy job.

 

If their object storage at the main office was added to regional veeam server as a direct-to-object repository and had backup copies being sent to it, then yes it could be used as a source for another backup-copy job.