Zew wrote:I need suggestions on how I can get decent latency on my test enviro, cause lets face it... its damn slow even after 4 VM's +
Im at my wits end on getting a fast enough dedicated disc to simply spin up around 6 VM's in a test enviro and keep my latency under 50 ms at most.
Could you please tell what VBR version are you currently at? VBR server is a VM running inside one of your hosts, is that correct? Also please describe you repository configuration and location. Another question is related to latency - is it that bad on both writes and read, or on just one of the mentioned?
So the Veeam backup server is a VM sitting on one of these hypervisors. Each hypervisor also has local discs and storage (that used to be used for VM's before the SAN came into play for HA purposes) there are 7 x 10k SAS discs on each hypervisor also in a RAID 5 config with a total capacity of around 1 TB. Now the Veeam servers primary VMDK that Windows and the Veeam software resides on (C:\windows, Program files, program data, etc) are on the VNXe SAN. I then attached a 200 gig VMDK to this VM that is on the localstorage of my hypervisor the VMFS based disc storage. I created a folder on this disc (I made it thin provision by the way, probably not teh best choice for this application hahah, my bad) and its this storage location and folder (the local RAID 5 VMFS datastore), this is where I installed vPower NFS.
Now for the last piece, the backup data. As I had mentioned the Veeam VM has a leg in the SAN vSwitch, as well as its primary connection to everything in the DataCenter vSwitch. All backups are being stored on a iOmega px12-350r SAN, connected in the same SAN subnet as the hypervisors and the other VNXe. However its done via a SMB shared folder, as I managed to put FreeNAS on that backup SAN. Again 2 x 1gig Nics connects that SAN to the SAN subnet. (Everything is connected to our Core layer 3 switch (3750's), Yes ACL's are in place )
foggy wrote:vPowerNFS might be the bottleneck in case of parallel restores, it is single-threaded and was not designed to be a high performance NFS server, but rather an acceptable solution to restore a VM or few quickly when a system is down (not the entire production DR).
Users browsing this forum: No registered users and 17 guests