12/27/2023 0 Comments Veeam 12 releaseVmware pointed VDDK, ok, but they also advised to use VDDK 7.0U3 or 8.0. Veritas is experiencing same problem with NBD but gave a fix for theirĬustomers, being configuring NFC (Network File Copy) AIO (Asynchronous I/O) A call as P1 at veeam support without even a call back from support !!!! (Veeam Proxy, Veeam File repoistory, 10Gb Lan, Networking Swithces, Forti Firewall, Cisco Hardware powering ESX. Next, explain me such recovery time difference recoverying SAME VM recover point using SAME infrastructure Vmware 6.7 is not supported anymore, that's first point. I completely disagree with your latest post : It seems other vendors have documented steps to do it (reference - ) Question for Veeam - can we modify these 4 settings that VMware mentions? Software providers can assist their customers doing so." On Linux, various socket buffer sizes have minimal performance impact, but on Windows changing them might yield good benefits. "Customers do not need to change the defaults, but if they encounter NBD performance issues, they can change change four buffer settings under in the VDDK configuration file. Notes.html, there's mention of tweaks that can be done: Based on the file details of:Ĭ:\Program Files (x86)\Veeam\Backup Transport\圆4\vddk_7_0\vmxDiskLib.dll, Veeam 12 is likely using VMware's VDDK 7.0.3.2. So, as others have indicated, it seems like there's still issues in Veeam 12 with vSphere 7.0 hosts. Results: 1 hour, 28 mins at a processing rate of 32 MB/s (Load Source 0% > Proxy 11% > Network 0% > Target 96%)įor reference, we were getting 50-80 MB/s on ESXi 6.7 hosts. Path: HKLM\SOFTWARE\VeeaM\Veeam Backup and Replication Then, I added this value and rebooted again: Rebooted Windows a few times, verified pvscsi driver was in use. Third attempt - Wanting to make sure I didn't have any resource constraints on my Veeam server, I increased the CPUs from 4 to 8, increased RAM from 8G to 16G, converted my SCSI controller from LSI Logic to VMware paravirtual SCSI. Results: 2 hours, 5 mins at a processing rate of 22 MB/s - very little improvement (rebooted the ESXi host after changing them) Second attempt - same test vcsa server (deleted all files from the datastore), but I changed 2 ESXi settings I found online:Įsxcfg-advcfg -s 32768 /BufferCache/MaxCapacityĮsxcfg-advcfg -s 20000 /BufferCache/FlushInterval Load: Source 0% > Proxy 25% > Network 0% > Target 99% Both hosts use a local SAS array (RAID10, SSDs).įirst replication attempt - Replicating our test vcsa server (~160 GB of used disk space), it took 2 hrs, 12 mins at a processing rate of 21 MB/s. The source ESXi host is 7.0 U2e (build 19290878) with 2 VMs on it (both are vCenter Server Appliances) and the destination is a freshly installed ESXi 7.0 U3f (build 20036589) with 0 VMs. I am attempting to replicate a single VM - our vCenter Server Appliance.Ģ. It's my backup repository, proxy, console, etc. All Veeam components are on this single VM. I installed Veeam 12 on a new Windows VM (fresh install to hopefully prevent any legacy settings/limitations). Today was the day, and here's what I found - overall, slight speed improvement, but not much and not near the speeds we are seeing with vSphere 6.7 hosts. I posted in this forum back in June, and I've been waiting for Veeam 12 to test this again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |