VMware backups - HotAdd vs SAN Transport
Hi,
We have the VRAY licences for VMware and was wondering what others are doing with regards for backups?
We have 150 VM machines on 5 hosts on fibre storage...
Our Backup Exec server is a physical server with fibre connectivity.
From my testing I can see that on an individual VM, SAN Transport is taking about half the time than using HotAdd for both initial backup to an empty dedupe folder, and the second backup (Where the majority of the source has already been captured).
However what I am wondering is (Particuarly using dedupe), do people use SAN Transport with multiple jobs running in parallel (Up to the concurrent usage limit of the dedupe folder) or do they use HotAdd and utilize multiple HotAdd backup proxies to the dedupe device?
I am trying to work out what would be best?
Thanks
I think this in effect boils down to for any given environment one option may work faster or slower than the other.
You are not really comparing like for like as Deduplication inside a VM can be affacted by how Vmware is managing performance related hardware access between systems (and Dedup is very resource intensive) Other components of the environemnt will also have affacts on performance. (i.e. speed of network link between the virtual MMS and the shared dedupl folder on the CASO etc)
With regards the multiple jobs running at same time - you probably needs some real world comments from forum members that are not Symantec support staff to get some idea of their experiences - it will work ( at least for SAN mode)
Note: I am not sure we get many customers using Hot-Add (we certainly don't see many support cases for it)