In an environment with one or more clusters with virtual machines protected by SRM, What is the most appropriate configuration of Storage I/O control?
1. SRM solution must not be impacted
1. vSphere Version 4.1 or later
2. FC (Block) Based Storage OR NFS (File) based Storage
3. Number of datastores is fairly static
1. Storage I/O control can prevent unmounting of datastore during a Recovery which can lead to errors being reported by SRM
1. Where possible ensure consistent storage performance for all virtual machines
Enable and Configure Storage I/O control for all datastores.
Set the congestion threshold to 20ms
Leave the shares value default
Add a Step to each SRM recovery Plan as Step 1 and Select the Step Placement of “Before selected step”.
Configure step type as “Command of SRM Server” and execute the Scheduled Task which will disable SIOC prior to executing a SRM recovery
1. The benefits of Storage I/O control can still be achieved without impact to the SRM solution
2. SIOC will not impact SRM failover as it will be disabled automatically as part of the SRM recovery plan
3. In the event the Protected site or is lost, SIOC will not prevent failover
1. Increased complexity for the SRM solution
2. An additional step to excecute a “Command of SRM Server” is required
3. A Scheduled Task will need to be setup and configured with setting “Allow task to be ran on demand”
4. A script to disable SIOC will need to be prepared and configured with all datastores
1. Enable Storage I/O control and leave default settings
2. Enable storage I/O control and set share values on virtual machines
3. Enable Storage I/O control and set a lower “congestion threshold”
4. Enable Storage I/O control and set a higher “congestion threshold”
5. Disable Storage I/O control