Simulate low bandwidth using throttling

[dbr]

Hi,

I have a large Windows repository to which we copy our primary backups using backup copy jobs through 10g ethernet. We want to simulate a second copy job that copies through a limited link (100Mbit). Because I don't have a large enough repository yet, I wanted to use the free space of the first repository. For this simulation I configured a second ip address on the destination, a separate Veeam managed server (with second ip directly, not name) and new Veeam Windows repository based on newly created managemed server. Additionally I set a network traffic rule between the primary backup respository and the second ip of the destination repository. But throttling also affects the backup copy job copying to a repository via name and not throttled ip. Does throttling even work with separate ip addresses on the same windows repository? If not, any other ideas to achieve my simulation without buying a new repository now?

Daniel

[JoshuaPostSAMC]

In the properties of the second repository you can set a read/write limit. That is how I'm simulating ours being offsite while we fine tune things.

Would that work for you?

[dbr]

Yes, that could be an option. I'll give it a try.

[dbr]

For anyone who's interested:

I got this working although I used open source wanem rather than using built-in throttling functionality:

Veeam-Server
IP: 10.1.1.10/24 -> Primary
IP: 10.254.98.10/24 -> to be able to add second repoistory as an additonal managed server / repository by ip

Rep 01
IP: 10.1.1.11/24
IP: 10.254.97.11/24

Rep 02
IP: 10.1.1.12/24
IP: 10.254.98.12/24

Wanem:
eth0 IP: 10.254.97.30
eth1 IP: 10.254.98.30

Primary Backup Copy Job:
10.1.1.11 ------------ 10g -----------> 10.1.1.12

WAN Backup Copy Job:
10.254.97.11 -----> 10.254.97.30 wanem-throttling 10.254.98.30 -----> 10.254.98.12

Addtional configuration:
- On Rep 01: route add 10.254.98.12 mask 255.255.255.255 10.254.97.30
- On Rep 02: route add 10.254.97.11 mask 255.255.255.255 10.254.98.30
- Be sure that the second IPs are not registered in DNS if you access the repositories with primary Backup Copy Job by name.
- Boot wanem iso in a newly created vm with two nics.
- Open root shell: ifconfig eth0 10.254.97.30 netmask 255.255.255.0
- Open root shell: ifconfig eth1 10.254.98.30 netmask 255.255.255.0
- Start wanem with appropriate bandwidth template