
14 Endurance FTvirtual Server Release Notes
routed in a manner that makes it impossible to sever all physical pathways between the
CoServers simultaneously. Failure to follow these guidelines may result in loss of data in some
failure scenarios.
Memory Synchronization Time and TCP/IP Time-out
Endurance software is designed to maintain client connections during resynchronization of the
Virtual Servers. Memory synchronization requires a blackout period when all transactions are
halted while the memory state is copied to the synchronizing Virtual Server. Typically, the
blackout period is shorter than the TCP/IP time-out and consequently, client connections are
maintained during resynchronization. When running Windows Server 2003 Enterprise Edition
on the FTvirtual Server, the default setting uses a two-phase background synchronization
technique. The first phase permits most of memory to be copied in the background with system
operations continuing. The second phase typically requires an extremely short blackout time to
complete memory synchronization.
Under Windows 2000 or when the foreground memory copy option is enabled, system
operations are halted while all of memory is copied. In some large memory configurations, the
blackout period may exceed the TCP/IP timeout value and
connections may be lost temporarily.
If this is a concern, you can use the Endurance Manager or the MTCCONS utility disable
automatic synchronization, and then use a script to schedule the resynchronization for a specific
time period. See the Endurance Manager’s online help and the Endurance FTvirtual Server
Commands manual for information on how to do this.
Virtual Disks
• When creating a Virtual Disk the Device Redirector will allow you to specify a currently
mounted Virtual Disk as the location for the new Virtual Disk file. This is not supported
and will not work.
• When attempting to dismount a Virtual Disk, you may see the error The device
"Marathon Virtual Disk n" cannot be stopped right now. Try stopping the device
again later. Make sure there are no open files on the Virtual Disk, including viewing it in
Windows Explorer, and retry the operation.
• When creating a Virtual Disk for use as the FTvirtual Server boot disk, Windows requires
that you use a boot partition that is at least 1536 MB in size.
Kommentare zu diesen Handbüchern