Typical config for a HyperIP Lab test

[LMT13]

Can you help me with a typical config to test a couple of apps over HyperIP? I've got the ability to source two or three 1u servers I have sitting around and I'd like to possibly test Veeam, Avamar, and maybe Netbackup over the WAN. I've got a copy of DummyCloud to use as a WAN emulator. I see it like this:

Windows Server/VMware/Veeam/HyperIP on one box.
DummyCloud/WAN Emulator on a second server.
Windows Server VMware/Veeam/HyperIP on a third server.

Is this about right?

[petephil]

That is correct and once installed test different distances (RTT) and packet loss from .01% up the maximum of 1%. Bandwidth setting will be controlled by your WAN emulator but a small, mid range, and large link would be enough. Remember to run with and without HyperIP over the same tests so that you have a good comparison between native and accelerated throughput.

[LMT13]

Ok, testing has been going well and I've noticed something quite surprising, the vm I built doesn't change its resource size no matter what bandwidth key I select. I've been monitoring my resources on the virtual appliance and even at 800Mbs (running multiple streams of FTP and Veeam Replication) that there is plenty of memory and processor left over. Do you really need the whole Gig of memory and a dedicated NIC for slower speed links? I understand the 9GB of disk, but wondered if a link is under 10Mbs, would I need the larger memory and dedicated GigE NIC?

[huhned]

There is no difference in the configured HyperIP resources for links from 2 Mb/s to 800 Mb/s. The required resources are: 9GB disk, 1GB RAM, 2GHz CPU. A dedicated NIC is suggested but not required. We have many installations running on shared NICs.