Cloud connect initial seed (v8)

[ckent]

Hi.

Just had the new line installed so have a lot more bandwidth to play with.
Just curious on how to kick off the first backup copy to the cloud.

Id like to have the backup copy to run daily.
But what i am seeinging is that the initial seed takes longer than a day and gives the error.

19/01/2016 23:00:19 :: Some VMs were not processed during the copy interval

Is it ok just to let the job repeate daily until it has completed.
or should i change the backup interval to longer say a week for it to complete the once and then reduce the interval to a day ?

Cheers
Colin.

[veremin]

If this is just an initial cycle that taking longer, it's ok to wait and let job to copy previously uncopied blocks during today's run. If this happens always, consider increasing sync interval. Thanks.

[ckent]

Ok i will increase the interval and kick it off again Friday night.

[veremin]

Makes sense. During this interval a backup copy job will copy the blocks that has not been copied during previous cycle as well as the new blocks. Thanks.

[Jackf]

Hi Colin,

We are a cloud connect service provider. If your having to push up a lot of data. There's always the option of seeding the data to a local device and shipping it off to the SP

Jack

[veremin]

Yep, seeding procedure works great for such scenarios, especially if your WAN link leaves much to be desired. Thanks.