Hello and welcome back. This is part two of my short series of posts about tuning backups.
I want to show you the performance, Backup Exec can reach.
Of course, this is neither an agreement that these performance values can be reached in every environment on the globe, nor that faster environments are not possible. It’s just a glimpse into what we do in our day-to-day business.
In the first part of this series we did some backups of test data to get a baseline of the performance Backup Exec can reach, if the environment is configured appropriately.
Of course I know that backing up test files is not “real testing”. Therefore, we do now want to see, what results we can get when backing up a virtual machine. As already announced in the first part, we want to do several tests with backing up the same VM via different paths and then see afterwards, what tuning of Backup Exec might help to get even better results.
Our “test candidate” is a virtual machine running Windows 7 including Office 2013 and is doing some background tasks that produce load and files on the machine.
It is virtualized on a VMware vSphere 6 ESXi cluster (2 nodes) that uses a HPE MSA 2040 SAS as its shared storage. It’s the same storage, we also used in part one of this series.
Backup via LAN
So our first run will be done via LAN, using the backup server’s 20 Gigabit Ethernet (GBE) team consisting of two 10 GBE network links.
The ESXi servers do also have two teamed 10 GBE network links, all connected to the same stack of switches.
You can watch the video recorded for this post on YouTube:
Please continue reading about this performance tests in part three of this series.