You must not create a container file larger than 4 Gbytes on a Spiralog volume. This is because of a problem with the Spiralog file system that causes it to corrupt data in any file that is larger than 4 Gbytes. This applies to all current versions of Spiralog.
DIGITAL OpenVMS Disk Services for Windows NT issues no warning messages about the size of a container file, because it has no knowledge of the underlying file system.
A TIMA kit that solves this Spiralog problem should be available soon. For more information, contact your DIGITAL representative or visit our World Wide Web site at:
http://www.openvms.digital.com/openvms/products/ntds/index.html
If you lose cluster quorum when the OpenVMS Alpha node providing a disk service fails, you may find that I/O requests issued by users connected to shares on the virtual disk may time out before the disk service fails over to a standby node in your OpenVMS Cluster.
If you encounter this problem, reconfigure your OpenVMS Cluster so that it does not lose quorum when the node providing the disk service fails.
Alternatively, if you are unable to reconfigure your OpenVMS Cluster, you can increase the parameter that controls the SMB timeout period on the user workstation. For example, if you find that I/Os are timing out on a Windows NT workstation, increase the value of the SessTimeout parameter in the NT registry:
This value specifies the timeout in seconds; by default, it is 45.
To estimate the required value, use the Windows NT Event Viewer to find out the average length of time between the connection being lost and the connection being regained during OpenVMS Cluster failover.
Copyright © Digital Equipment Corporation 1997. All Rights Reserved.