Hi
I feel like this question should be answered in at least ten knowledgebase articles and other documentations, yet i seem to be unable to find any of them ...
I have BackupExec 2010 and vSphere 4.0 Enterprise Plus (3 ESX 4 servers). So far, I've been testing the nbd transport mode, which works, but gets slow sometimes on VMs with disks >100GB (i read that this is a problem with the service console of vmware esx 4 - not sure though).
Anyhow, since I have all the necessary hardware on site, i thought i could as well connect the server running backupexec (and vsphere server) to the san directly using FC...
... but i can't find a guide, neither from vmware nor from backupexec nor EMC, on what i should pay attention while doing this. Those questions came up before I've even touched the FC-Controller:
- vsphere 4.0 has this storage API thingy ... backupexec 2010 apparently supports it. does that mean that i don't have to install vmware VCB?
- I'm running backupexec 2010 and vSphere Server on the same box...any problems with that?
- i feel really uncomfortable that windows might write something to my vmfs luns, and destroying them with it... (like auto-signing or auto-initializing of new disks). how do i prevent windows from doing so?
- i read about a problem with multi-pathing and san backup mode ... i could just install EMC powerpath, which would handle the multipathing. does that work with vsphere storage api?
any answers (or links to documents i'm apparently unable to find) are very much appreciated.
best regards,