We're currently using 27 backup jobs to backup the 27 various VMs/physical servers.
--- Can someone suggest a better way to backup our things?
We just switched our Hardware Deduper from S3 to Enhanced Data Mover.
We thought EDM would only let us run one backup at a time, we're unsure currently.
Q: You are saying "Some physical servers are far away", does that mean you run the backups from a central place via a WAN connection?
Our Veeam Server and Qorestor Deduper are local to city x. Some servers are across the country in city y. Some are in Azure.
about half of the servers are local to Qorestor/Veeam. Everything is connected with Bell MPLS. Azure servers are part of the company wide WAN(Bell MPLS) too.
It would be awesome if I could schedule the jobs so the 1 full backup (changes every day) ran first, and then all the sequential triggered, but I don't know if we can do that.
--- Can someone suggest a better way to backup our things?
We just switched our Hardware Deduper from S3 to Enhanced Data Mover.
We thought EDM would only let us run one backup at a time, we're unsure currently.
Q: You are saying "Some physical servers are far away", does that mean you run the backups from a central place via a WAN connection?
Our Veeam Server and Qorestor Deduper are local to city x. Some servers are across the country in city y. Some are in Azure.
about half of the servers are local to Qorestor/Veeam. Everything is connected with Bell MPLS. Azure servers are part of the company wide WAN(Bell MPLS) too.
It would be awesome if I could schedule the jobs so the 1 full backup (changes every day) ran first, and then all the sequential triggered, but I don't know if we can do that.
Statistics: Posted by tegroup — Jul 21, 2025 7:17 pm







