CloudConnect - Initial Backup

[mwirz]

Hello

is it possible to import existing backups to CloudConnect to not have to send all the data over WAN? by example: can i make a copy Job OnSite (to NAS) and take the NAS with me to the Datacenter, copy the Data over to the Customers CloudConnect Repsository and Change the copy Job OnSite to CloudConnect? Will that work?

best regards
Mike

[Vitaliy S.]

Hi Mike,

Yes, that's possible. Here is a response from Luca on how it should be performed:

- customer creates the seed and ship it to the service provider (SP)
- SP creates an empty cloud repository
- SP browse the backup repository and identifies the sub-folder related to the cloud repository
- SP uploads the seeds
- customer connects to the cloud repository
- customer scans the repository to identify the seed. Seed goes into the "imported" backup sets
- customer maps a backup copy job to the seed

Thanks!

[mwirz]

Hi Vitaliy

That's really great - i gonna try this out. Thank you very much for the fast response.

best regards
Mike

[hulbertmike]

Regarding step 1 "customer creates the seed and ship it to the service provider (SP)". Is this process defined? Should it be a backup copy job? Regular backup job? Replica job? I am assuming backup copy job would be most logical if customer already has Veeam infrastructure. If this is a good assumption, is this the correct KB? : http://www.veeam.com/kb1856

[foggy]

It can be either a regular forward incremental backup job or a backup copy job. The KB is correct.

[Bryanr]

Does this process change in any way if some data already resides on the cloud connect repository. We control both sides of the equation (Client B&R copying to our Cloud Connect Server). About half the VM's for a specific clients copy job have already completed but it has taken terribly long. Should I perform the steps below as is or remove the existing data from the clients cloud connect repository then proceed as described.

[veremin]

You can't seed just portion of backup copy job. Therefore, you will have to wait until it copies parts that are currently missing or make a brand new seed, replacing existing data. Thanks.

[rmehta]

Hi I was just wondering, what if the backup copy job is pretty big and creates an incremental job; can we still use it and would we be required to copy both incremental and full files

[veremin]

Full, incremental and metadata files (.vbm) would be required. Thanks.

[rmehta]

thanks I thought so just wanted to confirm...