getting started with endurance ftvirtual server · 1-2 getting started with endurance ftvirtual...

Getting Started with Endurance FTvirtual Server

Marathon Technologies CorporationFault and Disaster Tolerant™ Solutions for Windows Environments

Release 6.1.1June 2005

NOTICEMarathon Technologies Corporation reserves the right to make improvements to this guide and the product it describes at any time and without further notice.

COPYRIGHT© Marathon Technologies Corporation. 1996-2005. All rights reserved.

This guide is copyrighted, and all rights are reserved. No part of this guide or the products it describes may be reproduced by any means or in any form, without prior consent in writing from Marathon Technologies Corporation.

Printed in the U.S.A.

U.S. Patent Numbers: 5,600,784; 5,615,403; 5,787,485; 5,790,397; 5,896,523; 5,956,474; 5,983,371; 6,038,685; 6,205,565; and 6,728,898.

European Patent Numbers: EP0974912; EP0731945; EP0993633; and EP0986784, and EP1000397.

Other patents pending.

SOFTWARE COPYRIGHT NOTICEThe software described in this document is covered by the following copyright:

© Marathon Technologies Corporation. 1996-2005.

TRADEMARK NOTICE

Endurance, Marathon Assured Availability, SplitSite, Marathon FTvirtual Server, and the Marathon logo are either registered trademarks or trademarks of Marathon Technologies Corporation in the United States and/or other coun-tries.Microsoft, MS-DOS, and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. All other brands and product names are trademarks of their respective companies or organizations.

SOFTWARE REVISION

The revision of the software that this document supports is Revision 6.1.1.

Marathon Technologies Corporation, Inc.295 Foster Street, Littleton, MA 01460

(978) 489.1100 or (888) 682.1142www.marathontechnologies.com

ii

Contents

Chapter 1 — Welcome to Endurance FTvirtual Server

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Comparing Endurance Fault Tolerance to Other High Availability Systems . . . . . 1-2

Failover Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Endurance Fault Tolerance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Endurance Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

The Fault Tolerant Virtual Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Endurance FTvirtual Server Devices. . . . . . . . . . . . . . . . . . . . . . . . 1-9Endurance Disk Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Endurance Delta Copy Disk Mirroring . . . . . . . . . . . . . . . . . . . . . . 1-14Endurance Boot Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Endurance Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Creating FTvirtual Server Devices . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Chapter 2 — Endurance FTvirtual Server Administration

Endurance Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2FTvirtual Server Taskbar Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Endurance Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5MTCCONS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Endurance MIB and SNMP Agents . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Performing CoServer Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . 2-10

Chapter 3 — Endurance FTvirtual Server Start Up and Shut Down

Order of the Endurance Configuration Start Up Process . . . . . . . . . . . . . . . . 3-1

Contents iii

Non-Redundant Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Shutting Down Endurance Configurations . . . . . . . . . . . . . . . . . . . . . . . 3-3

Shutting Down All Components and Powering Off the CoServers. . . . . . . . . 3-4Shutting Down an Individual CoServer . . . . . . . . . . . . . . . . . . . . . . . 3-4Shutting Down the FTvirtual Server . . . . . . . . . . . . . . . . . . . . . . . . 3-5Restarting the FTvirtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Chapter 4 — Learn More about Endurance Software

Where Can I Learn More? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Additional Information on the Support Web Site . . . . . . . . . . . . . . . . . . . . 4-3

iv Getting Started with Endurance FTvirtual Server

Endurance®software ensures the industry’s highest level of system availability for business-critical Microsoft® Windows ® applications. Endurance FTvirtual Server prevents loss of application data and eliminates application downtime related to server hardware, disk, or network failures. Endurance protects any Windows application to provide continuous computing, mirrored data storage, uninterrupted network access, and service through hardware faults and network failures. These benefits are achieved without requiring any application modification or custom scripts. Servers enabled by Endurance software are especially suited for business environments requiring 24x7 system availability and unattended operations.

This chapter introduces the concepts and unique features of Endurance software that allow you to attain the highest levels of Windows server availability in the industry. It contains the following sections:

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Comparing Endurance Fault Tolerance to Other High Availability Systems 1-2

The Fault Tolerant Virtual Server . . . . . . . . . . . . . . . . . 1-8

Welcome to EnduranceFTvirtual Server 1

Welcome to Endurance FTvirtual Server 1-1

OverviewEndurance software works with the Microsoft Windows operating system and industry-standard Intel®-based server hardware to create a virtual server that provides a fully fault tolerant operating environment for Windows applications. Users of applications running in this fault tolerant environment experience seamless operation and continuous availability even in the event of hardware failures. This level of availability is commonly called “Five-Nines Availability,” which indicates that the operating system, application, and data are protected from hardware failures so that system operations are available more than 99.999% of the time. This represents less than 5 minutes of unscheduled downtime per year.

The Endurance FTvirtual Server ensures that applications survive the leading causes of downtime, continuously operating through hardware and other failures, such as those associated with:

• Power interruptions and power supplies

• Disk drives

• I/O controllers

• Memory, motherboards, and CPUs

• Network connectivity loss

• Faults caused by defective device drivers

Comparing Endurance Fault Tolerance to Other High Availability SystemsHigh availability server technologies use hardware redundancy to ensure system and application availability. What distinguishes the different high availability technologies from each other is the way each manages redundant hardware, as well as the level of availability and ease of operations they provide.

Failover Technologies

Technologies such as clusters and data replication comprise a class of high availability systems known as failover technology. Failover technologies use redundant servers in an active-passive design in which one server actively executes the application while the redundant (passive) server is inactive. The passive server is accessible and ready to assume operations should the active system fail. Using replication technology, data are periodically copied from the active

1-2 Getting Started with Endurance FTvirtual Server

server to a passive, replication server.When a hardware failure occurs on the active system, application operations cease on the failed system and must be restarted on the replication system.

In a cluster, two redundant servers operating in an active-passive configuration access common shared disk storage. When a failure occurs in a cluster, the application is moved from the active server to the passive server, as shown in Figure 1-1.

Figure 1-1 Cluster Failover – Applications Are Restarted on the Passive Server

In some failover implementations, the failover event is initiated by an administrator; in other implementations, the failover is automatically handled. Automated failover technology requires scripting and/or application modification to manage the migration of the application from the failed server to the redundant server.

A significant drawback of failover designs is that service is interrupted during the failover process. This can result in the loss of in-process transactions; the loss of some application data is also possible. Furthermore, if the failover event requires manual intervention to reestablish

Application Restarted on Passive Cluster Node

Active Server Passive Server Active Server (now failed)

Active Server (now activated)

Failure Occurs

Shared Disk Shared Disk


service, considerable delays in operations may occur. Additionally, when the failed system is repaired, service may need to be interrupted a second time to return processing to the repaired server.

Endurance Fault Tolerance

In contrast to failover technologies, Endurance eliminates the failover process by providing a fully fault tolerant virtual server, called the Endurance FTvirtual Server. The FTvirtual Server is a virtual Windows server, operating redundantly and synchronized across two identical servers. If one server fails, application execution continues uninterrupted within the FTvirtual Server environment without loss of transactions, data, or network connectivity. Application data are protected by mirroring disk data on redundant drives associated with each server. In the presence of a failure, Endurance automatically removes the failed hardware and reconfigures system operations without operator intervention. The reconfiguration process is not detectable by the user, application, or operating system. See Figure 1-2.

Figure 1-2 Endurance FTvirtual Server Survives Hardware Failures

Both Physical Servers Operating Redundantly and Synchronized

Operational Server

Failed Server

Failure Occurs

Fault Tolerant Virtual Server Virtual Server


Endurance software accomplishes fault tolerance by synchronizing data, memory, and program execution in the FTvirtual Server environment so that every operation executed under the control of one server is executed simultaneously on the second server. This design, known as lockstepping, ensures that operations are redundantly processed, synchronized, and executed in such a way that when a hardware failure occurs on one server, application operations within the FTvirtual Server continue under the control of the surviving server.

Endurance Software Automatically Handles Hardware Faults

Endurance software continually monitors all system devices to determine which are operable and which are inoperable. Endurance software automatically discovers failing or faulted hardware and reconfigures hardware resources to maintain system operations. Errors detected in server memory, motherboards, or CPUs result in the automatic removal of the faulty server. Errors detected in disk or network adapters result in device reconfiguration in the manner needed to continue ongoing operations.

Endurance Software Permits Application Operations During Repair

Endurance software allows you to perform repairs without interrupting service to network clients. You can shut down one server to repair, replace, or upgrade hardware components and install software patches while application operations continue on the remaining server. After a failed component is repaired and reinstalled, the repaired server is simply booted and returned to service. Endurance software then automatically reconfigures and resynchronizes application operations and data between the two servers, returning the FTvirtual Server to full redundancy.


Endurance Configurations

An Endurance Configuration is comprised of two standard dual-processor Intel-based servers running the Microsoft Windows operating system and connected through gigabit Ethernet links. In this configuration, the servers are called CoServers, and the gigabit Ethernet links connecting the CoServers are known as CoServer Links. CoServer Links are used for Endurance synchronization, device management, and remirroring processes.

The Endurance software installation process creates the FTvirtual Server, a virtual server hosted by the two CoServers. The FTvirtual Server is a fault tolerant Windows operating environment where application execution is protected from hardware failures.

During the Endurance software installation, a disk is designated for use as the FTvirtual Server boot disk. The disk selected may be a second physical disk, separate from the CoServer boot disk, or it may be created as a virtual disk derived from an Endurance-managed file resident on the CoServer boot disk. When a virtual disk is used, only one physical disk is needed to support both CoServer and FTvirtual server operations.

In an Endurance configuration, one or more additional Ethernet adapters (up to four) can be configured as Redirected Links on each CoServer. Ethernet adapters used as Redirected Links provide client network access only to the FTvirtual Server environment. To access and manage the CoServer environment, a network path to the CoServer must be established. While a number of network configurations are possible, a separate Ethernet adapter is typically configured on each CoServer and dedicated to administrative access for the CoServer environment. An Ethernet adapter used for this purpose is known as a CoServer Management Link (CS Management Link). Figure 1-3 illustrates the optimal hardware configuration to support fault tolerant operations.

Figure 1-3 Optimal Configuration Including Fault Tolerant Environment

CoServer Links

Public LAN

Redirected LinkRedirected Link

CS Management LinkCS Management Link


Endurance FTvirtual Server permits highly flexible configuration of networks and physical placement of CoServers to accommodate support for both Fault Tolerant operations and Disaster Tolerant operations:

Fault Tolerant Configurations

In a fault tolerant Endurance configuration, the CoServers are physically located adjacent to each other. In the optimal configuration, the CoServer Link adapters are redundant and physically interconnected with no intervening switches, hubs, or other active components. This is the simplest configuration to install, administer, and maintain. It supports continuous application availability and provides the highest level of performance and serviceability. The standard Endurance software license supports fault tolerant operations.

Disaster Tolerant Configurations

In a disaster tolerant Endurance configuration, the CoServers are physically separated in different rooms, buildings, or geographical locations. The gigabit CoServer Links may be interconnected directly or through a switched network. This configuration, known as Splitsite, provides continuous application availability even if a site failure occurs. If a fire or disaster occurs at one site, operations at the remaining site continue uninterrupted. The Quorum Service, an additional software component, is required for Splitsite operation. The Quorum Service is installed on one or more servers resident on the CoServer Management network. It arbitrates connectivity loss between the two CoServers and manages the appropriate response when failures occur. Endurance Splitsite is purchased as an option and requires a Splitsite license key.


The Fault Tolerant Virtual ServerThe Endurance installation process creates a virtual Windows server on each CoServer, hosted by the CoServer operating system. After a CoServer boots, its Virtual Server starts. When first started, these Virtual Servers are neither redundant nor fault tolerant. However, when both CoServers have completed the boot process, the two Virtual Servers synchronize to form the FTvirtual Server, a single fault tolerant Virtual Server supported by and accessible through both CoServers, as shown in Figure 1-4.

Figure 1-4 Endurance FTvirtual Server: Two Virtual Servers Join to Form a Single Fault Tolerant Virtual Server

The FTvirtual Server has all the characteristics of a physical Windows-based server. As a fault tolerant server, it provides an error-free operational platform for applications, protected from hardware failures. You can allocate disk storage, and install, configure, and execute applications within the FTvirtual Server, just as you normally would on any Windows system. Like any standard Windows server, the FTvirtual Server has a single network identity and is accessible on the LAN.

Virtual Servers Start the Joining and Synchronization Process

Once the Virtual Servers Synchronize, the FTvirtual Server Is Redundant and Fault Tolerant


To access the FTvirtual Server, you log into either CoServer and:

• Right click on the Taskbar icon

• Launch the FTvirtual Server Desktop

• Click on the FTvirtual Server Desktop

See Figure 1-5. The Windows operating system login screen displays, allowing you to log into the FTvirtual Server, just as if you are accessing a physical server.

Figure 1-5 The FTvirtual Server Available from Either CoServer Desktop

Endurance FTvirtual Server Devices

While no physical devices are directly attached to the FTvirtual Server, applications operating within it have access to redirected devices such as disks, tapes drives, CD-ROMs, medium changers, and network adapters. From the perspective of applications executing in the FTvirtual Server, redirected devices operate and act like physical devices.

Devices attached to the CoServers are made available to the FTvirtual Server through a process known as redirection. Using the Endurance Device Redirector utility, you can choose which of the devices attached to the CoServers you want to redirect, making them accessible by

FTvirtual Server Desktop


applications executing in the FTvirtual Server. Once devices are redirected, they are no longer accessible to programs running on the CoServer.

Figure 1-6 Fault Tolerant Network Access with Paired and Redundant Ethernet Adapters

Devices such as disks and network adapters that are available on both CoServers are paired and redirected to provide fault tolerance. See Figure 1-6. Consequently, if a device on one CoServer fails, the redundant device on the surviving CoServer maintains service to the virtual server.

Non-redundant devices attached to and available from only one CoServer also can be redirected, as shown in Figure 1-7.

FTvirtual Server

Public Network Redundant Network


Figure 1-7 Non-Redundant Devices Are Accessed Through Only One CoServer

The process of redirecting non-redundant devices is implemented for accessing devices that cannot operate redundantly, such as compact disks or tapes drives.When redirected in this manner, these devices are not fault tolerant. If the device fails or the CoServer servicing the device should fail, the device is no longer available to applications operating in the FTvirtual Server.

Endurance Disk Mirroring

Endurance software protects data by maintaining identical copies of data on a pair of redundant disks, one disk associated with each CoServer. These disk pairs are called mirror sets. To create a disk mirror set, you use the Device Redirector to select an available disk on each CoServer and bind the pair as a mirror set. Once configured, the mirror set is presented to the FTvirtual Server as a single redirected disk. Applications operating in the FTvirtual Server use the mirrored disk just as they would any physical disk device. See Figure 1-8.

Fault Tolerant Virtual Server


Figure 1-8 A Mirror Set Appears as a Single Device to the FTvirtual Server

FTvirtual Server

Virtual Device

CoServer 2 CoServer 1


When the mirror set is first created, Endurance software synchronizes the data in the mirror set by completely copying data from the mirror disk member on one CoServer to the mirror disk member on the second CoServer, as shown in Figure 1-9.

Figure 1-9 Synchronizing the Mirror Set: Data Are Copied From the Source Disk to the Target Disk

During normal operations, application data written to the mirror disk are synchronously and transparently written on each member of the mirror set. Should a member in the mirror set fail or an entire CoServer fail, Endurance software manages access to the surviving disk in the mirror set in such a way that the application continues disk operations uninterrupted. See Figure 1-10.


Source Target


Figure 1-10 Redundant Mirrored Disks Provide Online, Up-to-Date Copies of Data

Endurance Delta Copy Disk Mirroring

In many cases, Endurance software accomplishes remirroring of disk data without having to copy the entire contents of one disk to its redundant mirrored disk. Endurance software includes a delta copy mirroring feature that tracks which data have changed on an active CoServer while a redundant CoServer is out of service. When the repaired CoServer is returned to service, Endurance software updates and synchronizes the disk mirror set by copying only the changed data. This portion of data typically is a small fraction of the entire mirror set and permits highly efficient operation with rapid restoration of full redundancy and data protection.

Mirrored Writes Maintain Physical Disk Copies

Failure Occurs

Mirror Set Mirror Set

When Controller or Disk Fails, Surviving Disk Continues Service

FTvirtual Server FTvirtual Server


Endurance Boot Devices

Just as in a standard Windows server, each CoServer in a Endurance Configuration has a boot disk used to store its Windows operating system and associated files. The boot disk is designated and initialized as part of the installation of the Windows operating system on the CoServer. The CoServer boot disk is accessible only from the local CoServer; it can not be redirected for access from the FTvirtual Server.

As part of the Endurance installation process, a second disk drive on each CoServer is allocated and reserved for exclusive use by Endurance software. This disk is used as the FTvirtual Server boot disk and serves a similar purpose as a standard Windows boot disk. The FTvirtual Server boot disk is created as a mirror set comprised of two disk drives, each associated with a separate CoServer. The Windows operating system of the FTvirtual Server, along with Windows system directories and files, are stored and managed within the FTvirtual Server boot disk. Like all other FTvirtual Server devices, the boot disk can only be accessed from within the FTvirtual Server; it is not accessible from either CoServer.

Endurance Networking

Network adapters on each CoServer provide redundant network paths to the FTvirtual Server. In normal operations, one of the two redundant network adapters is active and responsible for communication while the redundant path is on standby. Should the active network path experience an adapter, network, or CoServer failure, the standby adapter is activated automatically. The result is that in-process network communications are maintained, and users never experience a loss of network data or server connectivity during failures. See Figure 1-11.


Figure 1-11 Redundant Network Adapters Ensure Network Connectivity

Endurance Virtual Network

The Endurance FTvirtual Server also includes a virtual network that provides LAN-style connectivity between the FTvirtual Server environment and both CoServer operating system environments.

Within this virtual network, the CoServers and FTvirtual Server appear as three interconnected nodes, as shown in Figure 1-12.

FTvirtual Server

Active

Network Failure Occurs

Standby Offline Active

FTvirtual Server


Figure 1-12 The Virtual Network

Each virtual network between the CoServer and FTvirtual Server is a separate LAN. However, there is no direct virtual LAN between the two CoServers. The virtual network requires no additional hardware.

The virtual network can be configured to provide:

• CoServer access to redirected CD-ROMs

• FTvirtual Server access to CoServer event logs, memory dumps, and other files

• FTvirtual Server access to floppy drives or CD-ROMs that have not been redirected from the CoServers

FTvirtual Server

Virtual LAN Virtual LAN


Creating FTvirtual Server Devices

Endurance software includes the Device Redirector, a utility used to redirect physical devices attached to the CoServers and make them available for access as redirected devices in the FTvirtual Server environment.

The Device Redirector provides two views of devices in the Endurance Configuration. The CoServer view presents a tree view, showing each CoServer and the full list of attached physical devices, regardless of whether the device has been redirected for use by the FTvirtual Server. The default view is the FTvirtual Server view. In this view the Device Redirector presents two lists of devices:

• The CoServer Devices

• The FTvirtual Server Devices

See Figure 1-13.

Figure 1-13 Endurance Device Redirector’s Lists of Devices


In this view, the list of devices in the CoServer Devices tree includes those physical devices attached to the CoServer that are accessible to the CoServer and are eligible to be redirected. These devices are not accessible from the FTvirtual Server. The list of devices shown under the FTvirtual Server tree includes the devices that are redirected and accessible from the FTvirtual Server.

Using the utility’s graphical user interface, you select devices from the tree and redirect them for use from within the FTvirtual Server. Once devices are redirected, they are fully accessible from, and can be used by, the FTvirtual Server. Redirected devices are dedicated for exclusive use by the FTvirtual Server and are not visible or accessible to the CoServer operating systems. Consequently, when you redirect a CoServer device, it is removed from the CoServer Devices list and added to the FTvirtual Server Devices list.

To create mirror sets, you select two disks, one attached to each CoServer, and bind them as a mirror set. To create redundant network connections, you select the NICs, one attached to each CoServer, and bind them as a redundant network pair.

Refer to the Endurance FTvirtual Server Administrator’s Guide for complete documentation of the Endurance Device Redirector.


This chapter introduces you to the concepts needed to understand the administration and management of the Endurance FTvirtual Server. It contains the following sections:

Endurance Administration Overview . . . . . . . . . . . . . . . . 2-2

Performing CoServer Maintenance Tasks . . . . . . . . . . . . .2-10

Endurance FTvirtualServer Administration 2

Endurance FTvirtual Server Administration 2-1

Endurance Administration OverviewFrom the system administration perspective, management of a Endurance Configuration involves monitoring and administration of the two CoServers and the FTvirtual Server as separate entities, as shown in Figure 2-1. Each entity presents itself to the network and the administrator as a distinct server that can be accessed and managed using standard Windows utilities and tools.

Figure 2-1 CoServers and the FTvirtual Server – Accessed and Managed as Three Separate Entities

In addition to the standard Windows management tools, Endurance software provides the Endurance Manager, a utility with a graphical user interface, and MTCCONS, a command line utility. Both utilities are used for monitoring and controlling configuration component states. Endurance also includes an SNMP MIB, which enables you to use industry-standard management frameworks for monitoring Endurance Configurations.


FTvirtual Server


FTvirtual Server Taskbar Icon

Endurance software includes a Taskbar icon through which you can quickly determine the status of the Endurance Configuration. Because the icon enables you to know at a glance if the FTvirtual Server is operating in a Good state, you know immediately if you need to perform any analysis or take any corrective actions.

Table 2-1 describes the Endurance Configuration states indicated by the Taskbar icons.

Table 2-1 Taskbar Icons Indicating Endurance Configuration Operating State

Icon Description

Good • The FTvirtual Server, local, and remote CoServers are all operating in a Good state. The FTvirtual Server is fully redundant and fault tolerant.

• No operator intervention is needed.

Informational • Transitioning is an example of a state for which an informational icon might be displayed.

• Operator intervention typically is not needed because this temporary state usually resolves itself automatically to a Good state.

Unknown • The state of the FTvirtual Server is not known. The Taskbar icon does not have access to state information, perhaps because, for example, the system management software is not running, or one CoServer is not able to communicate with the other CoServer.

• Operator intervention is recommended in order to determine the status of the Endurance Configuration components and the state of the FTvirtual Server.

Warning • The Endurance Configuration is experiencing some type of failure and is not fully redundant at this time.

• The FTvirtual Server is running on at least one CoServer.

• Operator intervention is required to perform the steps needed to return the FTvirtual Server to full redundancy and fault tolerance.

Failed • The Endurance Configuration is not functioning as a fault-tolerant, redundant system because of one or more failures.

• Operator intervention is required to perform the steps needed to return the FTvirtual Server availability.


You can double-click on the icon to launch the Endurance Manager directly. You can then use the Endurance Manager to obtain more detailed information about the various components’ states, and can take corrective action necessary to return the FTvirtual Server to its normal Good operating state.

The Taskbar icon also uses tool-tip text to display summary information about the state of the Endurance Configuration whenever the cursor passes over or comes to rest on the icon. The tool-tip text indicates the states of the local and remote Coservers as well as the FTvirtual Server, as shown in the example of a Good Configuration state in Figure 2-2.

Figure 2-2 Tool-tip Text Example

Alternatively, you can right-click on the Taskbar icon to raise menus through which you can perform various management tasks directly from the Taskbar. See Figure 2-3 for an example of management tasks you might perform from a remote CoServer.

Figure 2-3 CoServer Taskbar Icon Menus

As shown in Figure 2-3, you can manage the Endurance Configuration, the Local CoServer, the Remote CoServer, and the FTvirtual Server directly from the Taskbar, disabling, enabling, restarting, or shutting down the components you select.


Endurance Manager

The Endurance Manager is a Windows application used to monitor and control the Endurance Configuration. It uses color-coded component icons, state icons, and fly-over text to display operational states as well as redirected device information. If a component changes, the icons and the fly-over text change to reflect the current state.

You can run the Endurance Manager locally from either of the CoServers or from the FTvirtual Server as well as from a remote client PC. Start the utility from the Windows Start menu by selecting Start Programs Marathon Endurance Manager. On the FTvirtual Server Desktop or on a CoServer, you can also start the utility by double clicking on the Taskbar icon.

When the utility starts, it displays the operational state of the local Endurance Configuration with a graphical representation of its components. If you are running the Endurance Manager from a remote client, use the dialog box that is displayed and connect to the FTvirtual Server, CoServer 1, or CoServer 2 of the Endurance Configuration you want to manage.

The Endurance Manager offers two views of the Endurance Configuration: the FTvirtual Server View and the CoServer View. Both views display component state information and can be used to make changes to the states of components.


The FTvirtual Server View displays the Endurance Configuration from the perspective of a redundant, fault-tolerant server. The FTvirtual Server is displayed with an icon representing the entire Endurance Configuration and with icons for the FTvirtual Server and each class of redirected device accessible from the FTvirtual Server. When fully operational and redundant, the FTvirtual Server is displayed as green, and each component displays without state icons. SeeFigure 2-4.

Figure 2-4 Endurance FTvirtual Server View


The CoServer View is displayed from the perspective of separate physical entities with icons for each component organized to show the relationship of the physical devices redirected to the FTvirtual Server from each of the CoServers. When fully operational and redundant, each Virtual Server and CoServer is displayed as green, and each component is displayed without state icons. See Figure 2-5.

Figure 2-5 Endurance CoServer View


The FTvirtual Server survives component failures and also state changes to individual components with no noticeable affect on the end user. When operating in a state with failed components, or when one Virtual Server icon appears red, it continues to function and process applications, even though it is not fully redundant. Only when both Virtual Server icons appear red has its ability to continue operating failed. When complete redundancy is restored, it resumes operation as the fault tolerant FTvirtual Server, indicated by green icons.

The Endurance Manager’s menus help you monitor and manage the Endurance Configuration. You can right-click on an individual component to get more detailed information regarding the component and change its operating state, such as starting, stopping, or disabling it. You can also access information and management options using the View and Manage drop-down menus from the Menu bar and the pop-up menus on the component list in the Component Status window. The following table summarizes common tasks and their related menus.

The Component Status window displays operational data and can be displayed in either the FTvirtual Server or CoServer view, and component information is available through the Properties page. The Mirror Copy Status Window shows you detailed information about mirror copy status and progress by continuously updating a graphical display. See Figure 2-6.

Table 2-2 Quick Guide to Endurance Manager Menu Options

To Do This: Use This Menu

Connect to a host of a Endurance Configuration

File Connect

Set defaults for the Endurance Manager

File Options

Change the GUI display of the Endurance Configuration

View FTvirtual Server View or CoServer View

Display the list of the Endurance Configuration components and their states

View Component Status

Display the status and graphical representation of the most recent or the next scheduled mirror copy for each redirected mirrored disk

View Mirror Copy Status

Display the list of the Endurance Configuration components and their properties

View Component Properties

Disable, enable, shut down restart, and other operational tasks for individual components

ManageSelect the component, and then the option you want.


Figure 2-6 Mirror Copy Status Window

Refer to the Endurance FTvirtual Server Administrator’s Guide for complete documentation of the Endurance Manager.

MTCCONS Utility

Endurance software includes MTCCONS, a command line interface used for scripting. Using the MTCCONS utility, you can construct automated procedures to display or control the state of the Endurance Configuration and its components. Refer to the Endurance FTvirtual Server Administrator’s Guide for complete documentation of the MTCCONS utility.

Endurance MIB and SNMP Agents

Endurance software also includes an industry-standard SNMP interface for monitoring server operations using SNMP-based browsers and frameworks commonly available from server vendors. Should a server or device change state, SNMP traps signal the state change to the framework, making it easy for system administrators to take appropriate corrective action. Refer to the Endurance FTvirtual Server Administrator’s Guide for complete documentation of the Endurance MIB and use of SNMP agents.


Performing CoServer Maintenance TasksFor most management and administration tasks, you manage CoServers in the same way as any standard Windows operating environments. However, when CoServers are booted into the Endurance Configuration, redirected devices are not visible to the FTvirtual Server. Consequently, to perform certain repair and maintenance tasks on physical devices, you must sometimes remove the CoServer from the Endurance Configuration. Even though a CoServer is removed from the full configuration, application operations continue uninterrupted on the surviving CoServer. Typical maintenance tasks that require CoServer removal include device driver updates, Endurance software updates, and new device installations and repairs.

In cases in which you must remove a CoServer from the Endurance Configuration, you disable the CoServer, shut it down, and then boot it into a special mode of operation called Offline Endurance CoServer Mode. When a CoServer is booted into this mode, it operates as a standard Windows server with all attached physical devices visible and accessible for maintenance and repair.

To boot into this mode, you select Offline Endurance CoServer Mode from the Endurance boot options on the flexible boot menu. The Endurance boot options are:

• Online Endurance CoServer Mode – the server’s usual mode of operation

• Offline Endurance CoServer Mode – the mode used on occasions when you need to perform certain maintenance and repair tasks on physical devices or the CoServer operating system.

When you complete the maintenance task or repairs, you boot the CoServer back into Online Endurance CoServer Mode and then enable it, causing the CoServer to rejoin the Endurance Configuration. When a CoServer is returned to Online Endurance CoServer Mode, Endurance software re-establishes configured devices as redirected devices for the FTvirtual Server and resynchronizes disk mirror sets.

Note: When the CoServer is operating in Offline Endurance CoServer Mode, data modifications you make to the virtual servers’ boot drives and any application disks normally redirected to the FTvirtual Server are lost when the CoServer is rebooted into the Endurance Configuration. The reason for this loss is that when booted, Endurance software must restore the integrity of all data on all redirected mirrored disks. The online data is copied to the repaired CoServer disks until both mirror set members are identical. In the process, it overwrites changes you may have made while the CoServer was operating in Offline Endurance CoServer Mode. Modifications you make to the CoServer boot drive while in Offline Endurance CoServer Mode are retained.


This chapter introduces you to the procedures for starting up and shutting down the Endurance FTvirtual Server. It contains the following sections:

Order of the Endurance Configuration Start Up Process . . . . . 3-1

Shutting Down Endurance Configurations . . . . . . . . . . . . . 3-3

Order of the Endurance Configuration Start Up ProcessFor a Endurance Configuration to start, both the CoServers boot as standard Windows servers in the following order.

1. The CoServers are powered on and join:

- The first CoServer is powered on, boots the CoServer Windows operating system, and pauses, waiting to join with the second CoServer.

- The second CoServer is powered on and joins with the first CoServer.

2. The first CoServer starts a virtual server.

3. The virtual server context is copied from the first CoServer to the second CoServer.

4. The virtual servers on each CoServer synchronize and begin fault tolerant operations as a unified and redundant FTvirtual Server environment. See Figure 3-1.

Endurance FTvirtual ServerStart Up and Shut Down 3

Endurance FTvirtual Server Start Up and Shut Down 3-1

Figure 3-1 Endurance Configuration Boot Process

CoServer 1 CoServer 2 CoServer 1

CoServer 1 and CoServer 2 boot and join. The first CoServer starts a Virtual Server.

The Virtual Server context is copied from the first CoServer to the second CoServer.

CoServer 1 CoServer 2 CoServer 2

CoServer 2

CoServer 1

The Virtual Servers on each CoServer synchronize and begin fault tolerant operations as a unified and redundant FTvirtual Server environment.

Step 1. Step 2.

Step 3. Step 4.

Initialized Virtual Server

Uninitialized Virtual Server

Virtual Server 1 Virtual Server 2 FTvirtual Server


Non-Redundant Operation

To perform certain repair procedures, it is may be necessary to operate a single CoServer and the associated virtual server in a non-redundant configuration. This is accomplished by disabling the CoServer to be repaired, using either the Windows Start menu, the Taskbar icon, or the Endurance Manager. To use the Windows Start menu, select Start Programs Marathon Endurance Management Tasks Local CoServer Disable. If you prefer to use the Endurance Manager or the Taskbar icon, use the appropriate means to invoke the Disable option.

Disabling a CoServer removes it from the Endurance Configuration while server functions continue on the remaining CoServer. This is especially useful if you need to reboot the surviving CoServer. Ordinarily, during boot, one CoServer waits to join with the second CoServer before starting the FTvirtual Server. In a non-redundant environment, disabling one CoServer allows you to reboot and operate the surviving CoServer without having it wait for the second CoServer to boot.

Once you have completed the repair operations on a CoServer, you must return it to the Endurance Configuration to reestablish redundancy and fault tolerant operations. To restore redundant operations, enable the repaired CoServer. To do so:

• To use the Windows Start menu, select Start Programs Marathon Endurance Management Tasks Local CoServer Enable.

• To use the Taskbar icon, right click on the icon and select Manage Local CoServer Enable.

• To use the Endurance Manager, in the CoServer View, right click on the CoServer you want to enable and select the Enable option.

Shutting Down Endurance ConfigurationsYou can shut down parts of the Endurance Configuration or the entire Configuration in any of the following ways:

• Shut down all components and power off the CoServers

• Shut down an individual CoServer

• Shut down the FTvirtual Server


Shutting Down All Components and Powering Off the CoServers

You can use either the Windows Start menu or the Endurance Manager to shut down all components of the Endurance Configuration and power off the CoServers, as follows.

• To use the Windows Start menu, select Start Programs Marathon Endurance Management Tasks Endurance Configuration Shutdown.

• To use the Taskbar icon, right click on the icon and select Manage Endurance Configuration Shutdown.

• To use the Endurance Manager, from the tool bar menu, select Manage Endurance Configuration Shutdown

When the shutdown completes, all operations terminate in an orderly fashion, mirror sets are closed, and most servers display a pop-up message indicating it is safe to power off the server. Because the mirror sets close in an orderly fashion during this procedure, when you restart the configuration, mirror copy operations are not necessary.

Shutting Down an Individual CoServer

To shut down an individual CoServer, you log into the CoServer you want to shut down, and then shut down its Windows operating system using the Windows Start menu, the Taskbar icon, or the Endurance Manager, as follows:

• To use the Windows Start menu, select Start Programs Marathon Endurance Management Tasks Local CoServer Shutdown.

• To use the Taskbar icon, right click on the icon and select Manage Local CoServer Shutdown.

• To use the Endurance Manager, in the CoServer View, right click on the icon representing the CoServer you want to shut down and select the Shutdown option.

When the shutdown completes, the remaining CoServer and Virtual Server provide non-redundant processing. This enables you to continue operating on the surviving CoServer, although it is not fully fault tolerant: mirror sets are broken, and the local CoServer shuts down and does not reboot.


To return to full fault tolerance, you must power on the CoServer.

• To use the Windows Start menu, select Start Programs Marathon Endurance Management Tasks Local CoServer Restart.

• To use the Taskbar icon, right click on the icon and select Manage Local CoServer Restart.

• To use the Endurance Manager, right-click on the icon representing the CoServer you want to shut down and select the Restart option.

When the shut down completes, the CoServer restarts automatically. Endurance software uses the Delta Copy feature to update the mirror set rapidly and return the server to its fully redundant fault tolerant configuration.

Shutting Down the FTvirtual Server

You can also use either the Windows Start menu, the Taskbar icon, or the Endurance Manager to shut down FTvirtual Server, as follows.

• To use the Windows Start menu, select Start Programs Marathon Endurance Management Tasks FTvirtual Server Shutdown.

• To use the Taskbar icon, right click on the icon and select Manage Endurance Configuration Shutdown.

• To use the Endurance Manager, from the tool bar menu, select Manage FTvirtual Server Shutdown.

When the FTvirtual Server completes shutdown, the two CoServers remain operational with access to the FTvirtual Server and its devices, but they are not running as the FTvirtual Server. The CoServers continue to run as two servers that are networked together.


Restarting the FTvirtual Server

You can also use either the Windows Start menu, the Taskbar icon, or the Endurance Manager to restart the FTvirtual Server. To restart the FTvirtual Server from a running CoServer:

• To use the Windows Start menu, select Start Programs Marathon Endurance Management Tasks FTvirtual Server Restart.

• To use the Taskbar icon, right click on the icon and select Manage Endurance Configuration Restart.

• To use the Endurance Manager, from the tool bar menu, select Manage FTvirtual Server Restart.


This chapter contains the following sections:

Where Can I Learn More? . . . . . . . . . . . . . . . . . . . . . 4-2

Additional Information on the Support Web Site . . . . . . . . . . 4-3

Learn More aboutEndurance Software 4

Learn More about Endurance Software 4-1

Where Can I Learn More?Endurance provides you with a variety of documentation and online help to give you the information you need to implement a Endurance Configuration quickly and efficiently. See Table 4-1 for details.

Table 4-1 Endurance Component and Feature Documentation

Documentation Contents

readme.txt file on the Endurance CD

The version of Endurance software you are installing or have installed

Online Help Screens

Instructions, tips, and guidance for a range of topics.

Endurance FTvirtual Server Administrator’s Guide

Tools, utilities, and procedures, located in the \Docs directory on the Endurance CD.• Using the various administration tools and utilities• Using the Endurance Manager to monitor and manage the server• Using the Endurance Device Redirector to configure the server• Using Endurance MIBs and setting up SNMP capabilities

Endurance FTvirtual Server Commands

Endurance FTvirtual Server commands used with the MTCCONS utility within scripts you write.

Endurance FTvirtual Server Configuration and Installation Guide

Explains how to install the software and configure the Endurance FTvirtual Server.

Endurance FTvirtual Server Messages

Understanding and responding to Endurance FTvirtual Server messages• How messages are reported during the text phase of the

boot process, in the event log, and in pop-up screens within applications• Complete index of event messages• Possible causes of event• Recommended steps for remediation

Endurance FTvirtual Server Release Notes

Describes release-specific information, installation requirements, release considerations and limitations, and information that is not documented in the Endurance documentation set.

Glossary Lists and defines the Endurance terminology


Additional Information on the Support Web SiteVisit the Support web site at http://support.marathontechnologies.com to obtain the most recent updates to information about the release, including:

• Tested Server List

• Supported Windows Service Packs

• Supported operating systems on which you can run the Endurance Manager remotely

• Qualified language variations

• Tools and utilities available for problem diagnosis and resolution

• Packaging of event logs and .hrl files for transmission to Endurance for analysis and problem resolution

• Technical Information Knowledgebase

• Documentation of other versions of Endurance software

Learn More about Endurance Software 4-3

http://support.marathontechnologies.com

getting started with endurance ftvirtual server · 1-2 getting started with endurance ftvirtual...

Documents