What is the preferred methodology for seeding a Cloud Connect repository for a Backup Copy job? Would this be a case of copying over a full and rescanning the repository? The documentation was not 100% clear
I have a customer whose Internet connectivity is less than optimal (OK for incrementals) and has a contract for a trial with a locally based provider.
Thanks in advance
Roger
-
- Expert
- Posts: 148
- Liked: 11 times
- Joined: Aug 20, 2013 1:16 pm
- Full Name: Roger Dufour
- Contact:
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Cloud Connect Seeding
Create a cloud repository for a tenant, let a tenant make an initial seed, move the seed to the cloud repository, let a tenant rescan it. After that, tenant will be able to map a job to the moved backups.
Moreover, there is a dedicated SP' Cloud Connect section of these forums. And this discussion will be moved to it soon. To request an access to it, go to the User Control Panel of this forum, select User Groups in the tabs, select "Veeam Cloud Provider" and finally the "Join selected" option.
Thanks.
Moreover, there is a dedicated SP' Cloud Connect section of these forums. And this discussion will be moved to it soon. To request an access to it, go to the User Control Panel of this forum, select User Groups in the tabs, select "Veeam Cloud Provider" and finally the "Join selected" option.
Thanks.
Who is online
Users browsing this forum: No registered users and 86 guests