Ok will read up on SyncBackPro profile Groups and will await the first profile to finish up in a few days, thus as you refer to it, "frontloading" the container in Azure will be complete.
I assume that this would be as easy as creating the profiles Group and "dropping" my now 2 separate Azure profiles into it. (will read up)
I also assume I should do this with my 2 local profiles taht back up the primary server to a secondary server inside same LAN nitely also.
OR probably even better, bcs as you say it's better to have ALL profiles run sequentially (vs parallel) drop all 4 profiles (2 Azure and 2 local backup inside LAN) to same group and let "group" run them sequentially each weekday night.
Should i remove scheduling from each profile then before adding them to the created GROUP, and have the GROUP itself say start executing at say 9pm each weekday nite..?
I assume that this would be as easy as creating the profiles Group and "dropping" my now 2 separate Azure profiles into it. (will read up)
I also assume I should do this with my 2 local profiles taht back up the primary server to a secondary server inside same LAN nitely also.
OR probably even better, bcs as you say it's better to have ALL profiles run sequentially (vs parallel) drop all 4 profiles (2 Azure and 2 local backup inside LAN) to same group and let "group" run them sequentially each weekday night.
Should i remove scheduling from each profile then before adding them to the created GROUP, and have the GROUP itself say start executing at say 9pm each weekday nite..?