Archiver Appliance on MSP Side instead of Customer's side.

[iamloki]

Hi Guys, we are backing up customer data to our S3-compatible Storage (Quantum-ActiveScale) over the internet using the VBR server on the customer site (SOBR). We plan to run archive jobs to write backups from Capacity-Tier to DEEP-ARCHIVE using Archiver Appliance. If we install an archiver appliance at the customer's site next to VBR, the data has to travel twice over the internet before it is written to DEEP-ARCHIVE. (Once to reach and another time to write to Deep-Archive). So, I was planning to install Archiver Appliance next to S3 Storage and make network changes for VBR (customer-side) to talk to Archiver Appliance



What are the best strategies to archive this?
Should I use a VPN so that VBR can talk to Archiver-Appliance?
or
Should I add Archiver-Appliance to the on-prem VBR using a public IP from the MSP side (refer to image)

[veremin]

The archiver appliance should be located closer to the capacity and archive tier, and it should be deployed on your end.

It should be added as a managed server on the user’s end.

The choice between VPN or public IP does not matter much—you can set up connectivity in whichever way you prefer.

Thanks!