Hi All,
Traditionally we have been using guest attached iSCSI in our VM's. We are are preparing to deploy SRM for DR and need to look at changing this configuration. I know there has been lots of discussion on similar topics in the past but I am looking for something more recent. The following scenario's highlight those options I see as viable.
1) Create a VMFS volume for each of those volumes that were traditionally a guest attached iSCSI volume on the SAN.
Pro's
- Easy to identify within vCenter
- The most preferred solution with SRM
Con's
- Data is backed up via third Symantec, volume exclusions necessary per VM
- Data will need to be migrated from existing iSCSI volume to VMFS volume
- Additional connections against volumes eating up pool count on Equallogic arrays
- More volumes listed under vCenter, could become confusing
- Space expansion needs to happen on SAN first then extended in vCenter
2) Create a couple large VMFS volumes to contain numerous file server data drives
Pro's
- Most management can take place within vCenter
Con's
- Less flexibility
- More difficult to troubleshoot contention issues (specifically what data volume within that vmfs volume is causing the issues)
3) Map iSCSI volume as pass-through RAW LUN
Pro's
- Data does not need to be migrated to a VMFS volume
- Is a more preferred solution with SRM
Con's
- Still eats up connection count on SAN
- Lack of visibility of volumes within vCenter
4) Guest iSCSI
Pro's
- No changes necessary
- Easy to view metrics from SAN side
- Easy to control connection count against volume and increase at the guest level (Equallogic MPIO driver)
Con's
- Not preferred solution with SRM (work arounds required to ensure appropriate fail over and operation)
Looking for some advice and opinions.
Thanks