Cloud Connect with WAN Accelerator - single job or multiple?

[gwntc]

We are experimenting with Cloud Connect.
Source site has 10mb symmetrical connection
Target site has 40down/10up connection
Both have WAN Acceleration

I am about to do the initial seed to NAS at source and bring it back to target site. My question is.... Is it better to add all VM's to one Backup Copy job or should I create multiple Backup Copy jobs?

The only reason why I am thinking about the multiple backup copy jobs is for retries in the event that the job fails.

[dellock6]

Paul, are you talking as a user or as a service provider? If the latter, you should apply for the VCP dedicated forum and move the discussion there.

[Gostev]

On the source side, sending is limited to 1 task at a time per WAN accelerator. On the target side, a single WAN accelerator will process multiple tasks.

All of this is not specific to Cloud Connect though, this is how regular jobs in B&R work. In fact, jobs running over Cloud Connect ARE regular jobs - Cloud Connect simply allows these jobs to run over internet securely, and adds multi-tenancy on backup repository side.

[gwntc]

From a user standpoint from the source end.

My concern is if this backup copy job takes too long (over 24 hours to process) won't it fail when the regular job starts up again?

[Gostev]

No, in v8 it will suspend without failing.

[gwntc]

Thanks!