It is deprecated to assign a single WAN Accelerator to multiple replication jobs. Is this because it consumes too much CPU and memory?
If a WAN accelerator has high spec, can it be assigned to multiple replication jobs?
Because if you need one WAN accelerator per replication job, you need a huge amount of WAN accelerators (= Windows Server). We're service provider, and would like to replicate thousands of VMs, so this is very troubling.
Also, for reference, how much CPU and memory would it consume?
Best Regards,
-
- Enthusiast
- Posts: 26
- Liked: 2 times
- Joined: Mar 17, 2023 12:25 pm
- Full Name: miyu masuda
- Contact:
-
- Product Manager
- Posts: 14690
- Liked: 1696 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: WAN Accelerator Limitations
Hello miyu.masuda,
It is possible, however, keep in mind that single WAN accelerator assigned to multiple replication jobs will sequentially process one replication task (machine) at a time from every job. Thank you!
It is possible, however, keep in mind that single WAN accelerator assigned to multiple replication jobs will sequentially process one replication task (machine) at a time from every job. Thank you!
Who is online
Users browsing this forum: Bing [Bot], Egor Yakovlev and 72 guests