Customer wants control of repository

[frankive]

Hi.
A company want to buy our Veeam 365 service, but they also have a policy to own their data in terms of being able to own the repository and f.ex map it to another veeam 365 installation in future if they desire.
Is the solution here just to create a new aws account for them and create a separate s3 bucket for the customer and add it as their repository?
There should be no problem to remove the repository from our solutions, and add it to their own future veeam365? they should also be able to restore all data from it?
as default we offload directly to the object storage and are not using the local repository (perhaps some indexing are stored their..?)

[nielsengelen]

This should indeed be a working solution for them. If they do their own installation, they can just use the same AWS account and 'import' the data there. They will have to rebuild the local metadata which will happen on the first backup job.