Cloud Connect Replication initial seeding best practice

[dxb]

Hi All, I wonder what is the most efficient way to seed a VM replica into cloud connect.

I set the tenant side to use local backup repository as Seed source.
Is it possible to use a backup copy from (e.g. an USB drive, nas) from our customers to seed the Service Provider side ?

Thanks in advance, DB

[dxb]

Got it working with Veeam Support Today, the solution is not coming out the box

Prerequisites:
- veeam cloud connect connected and working
- cloud connect replication environment configured for new tenant

Phase 1: @tenant
- take a backup copy of the VMs onsite (any support: e.g. nas, usb, ... )

Phase 2: @SP (service provider side)
- Temporary assign cloud connect backup licence to the tenant (you will remove it later) and assign tenant storage space
- Copy customer veeam backup into the customer backup repository folder (if you add the nas as repository you need to move backups into the new folder)
- Scan the folder in order to import backups

Phase 3: @Tenant
- Add new Repository from cloud provider
- Create new replication job: enable low replication seeding
- Set Seeding to Initial seeding from backup repository > select the cloud storage backup repository

Phase 4: @tenant
- Run the replication job

Phase 5: (not yet tested)
- @Tenant side:
- remove cloud repository
- clean backup copy job and disk details,
@SP:
- disable Cloud Connect Backup licence,
- Remove temporary backups

Notes: The backup copies were not encrypted

[veremin]

That was something I was going to suggest - create a backup, place in cloud repository, use the repository as a source for cloud replication job. That's typical seeding approach.

Good to know you're up and running now.

Should you have other questions, don't hesitate to let us know.

[dxb]

Let's hope to have Veeam developers making this a simple single step process, currently is quite time consuming.

@Eremin would be nice if you share the how to into the online manual, cheers.

[veremin]

Typically we create a KB article or blog post, based on number of open support tickets or requests coming from forums; and so far there have been only few of them.

Anyway, thank you for the feedback; appreciated.