StorTrends Timeouts

Hypervisors

Any - Always install client tools for the VM’s if available.

VMWare - For software iSCSI Adapter set Recovery Timeout to 120 seconds.

NOTE: After modifying the iSCSI Adapter RecoveryTimeout value, the ESX iSCSI Initiator must disconnect and reconnect all StorTrends targets, or simply reboot the ESX server for the change to take effect.

HyperV - Follow the Windows recommendations below.

Citrix - Follow the Linux recommendations below.

Windows (all versions)

Any system which uses a StorTrends drive either directly or indirectly should set the timeout value to 190 seconds. If it is not present, create the DWORD entry.

NOTE: After changing settings in the registry the Windows server must be rebooted for the changes to take effect.

Additional settings when connecting via Microsoft iSCSI Initiator

Additional settings should be configured for systems connecting to StorTrends targets via Microsoft iSCSI Initiator. These include LinkDownTime, MaxRequestHoldTime, SrbTimeoutDelta, and ErrorRecoveryLevel (on Windows 8/2012).

NOTE: After changing settings in the registry the Windows server must be rebooted for the changes to take effect.

SMB / NAS Timeouts

For NAS volumes, set SessTimeout to 200 seconds.

If you encounter error 0x8007003B while copying to NAS, increase the timeout setting to 600.

NOTE: After changing settings in the registry the Windows server must be rebooted for the changes to take effect.

Linux

Any system which uses a StorTrends drive either directly or indirectly should configure the block device timeout to 190 seconds.

Persistent changes can be applied with udev rules. Examples include Citrix VDisk and RedHat/Fedora/SuSE StorTrends iSCSI devices.

Additional settings for Open-iSCSI

Edit the Open-iSCSI configuration file and set the replacement timeout to 180 seconds.