Mike Resseler wrote:Hi,
At this moment it is not possible out of the box. There is a workaround (see http://www.virtualtothecore.com/en/send ... d-connect/ for more details).
This request seems to pop up more and more so our PM and engineers are aware of it and will take this as a count for the feature request
Hope it helps
Thank you for the site suggestion Mike.
I followed the steps outlined and had partial success. I am able to create, export and load multiple profiles. One profile is a local backup job, scheduled for 12:00AM launch, the other is a Cloud Connect remote backup , left unscheduled in the VAW 2.0 configuration. The local backup runs as expected, the batch file process SEEMS to work correctly (scheduled using windows scheduler, loads the Cloud Connect enabled profile, runs a backup, then reloads the Local backup profile). When I check the Cloud Connect repository, I can see the VAW 2.0 job ran. It shows a status of success; however it displays 0 bytes sent and received.
When I manually load the Cloud Connect enabled profile on the VAW 2.0 client, I can see that the jobs ran but failed with a login error. The baffling part is the credentials used in the batch file match exactly the credentials used to initially setup the job. When I manually run the job it also fails with an invalid credentials error, yet the configuration of the job is successful using the same exact credentials.