Replies posted by magnusvr
Thanks Link State,since the customer has a brand new Veeam setup with a 300TB LHR, that’s what we want to use, to get the benefit och immutability and XFS pointers.. Also, the Agents will be server managed.I will move forward with suggesting to run the traffic through the firewall after all, and work with speed limits, distributed schedules, and possibly QoS in the FW./Magnus
Thank you Daniel,And as Veeam has the LHR registered with an IP in LAN1, it won’t help if I assign an IP in LAN2 on the VBR, since Veeam server won’t know that IP?I would have to add the LHR two times in Veeam (?), one for each IP, and control which agents from which network, that stores in what Repo instance.
Thank you all for your thoughts. The background is that they are running a lot of VMs in Proxmox, which means Agent backups. Only a few Agents are actually Physical servers. They have a new AHV cluster and are migrating to it, but it will be some time before they are all migrated. Once in AHV, the problem is gone.A Backup Network is hard to suggest now, and I feel that security wise, that would also connect all the servers together in one LAN, perhaps even more so that putting an IP on the backup server.I’m kind of assuming that I can’t get the Agent to connect directly to the LHR without segmenting it up into many, which sounds like a hassle.Can I put an extra IP/LAN on the B&R server and have the traffic go from the Agent to the B&R, and the B&R will then ship the traffic to the LHR? Or do I always need a connection from the Agent to the LHR?Complicated to explain my thoughts...thanks!
Hi JM,I’m not sure actually, the Agent servers are varying, 1 or 10Gbit, and I’m guessing they are around 10-20TB of Frontend data, and it will decrease to a large degree in the next 1-12 months.I don’t think there is much of change rate, these are application, sql and webhosting servers, no users.The Firewall is probably 1 Gbit but I’m not sure it can actually throughput 1 Gbit, and it will probably affect the 24/7 webhosting traffic.