everRun

Release Notes

NOTE: For the most recent documentation and updates, please log in to the Marathon
customer web portal and download the latest versions. The link is:
https://support.marathontechnologies.com/portallogin.asp

Product: everRun MX

Version Number V6.1 Release

Release Date May 2011

Document Edition 6.6.2011

Customer Support http://support.marathontechnologies.com

This document describes the everRun® 6.1 release and provides late-breaking or other
information that supplements the main documentation set.

Software Versions and Hardware Supported

The everRun 6.1 product download contains both the everRun software and the
Marathon OEM Edition of Citrix XenServer 5.6 Service Pack 2 required for this release.

When installing the XenServer software, please be sure to install the new version of
XenCenter, using the XenCenter.msi file (XenCenter version 5.6 Service Pack 2) on
the CD you create from the Citrix ISO downloaded from the Marathon website.

everRun also supports the advanced management editions of the Citrix software:
XenServer Advanced, Enterprise, and Platinum Editions, which are available from
Citrix. In this release, a XenServer Advanced Edition license is required if you include
XenServer HA (everRun Level 1) protected VMs in your pool. See the final bullet under
“What’s New in this Release” on page 2 for more information.

A list of the processors currently supported for everRun Level 3 and Level 2 protection
is available at
http://www.marathontechnologies.com/documents/Hardware_Qualifications.pdf

everRun Release Notes 1

CAUTION: Do not install any additional updates to this software without first
contacting your certified Marathon service provider. Installing
XenServer updates that are not supported by this everRun release
could require you to reinstall your entire software deployment.

What’s New in this Release

The following features are new in this everRun 6.1 release:
• Expanded operating system support. This release can be used to protect
virtual machines running the following operating systems: Windows Server 2003
Standard or Enterprise (32- or 64-bit, SP2); Windows Server 2008 Standard or
Enterprise (32- or 64-bit, SP1 and SP2); Windows Server 2008 R2 (64-bit,
including SP1); and Windows Small Business Server (SBS) 2003 R2 and 2008
(SP2, R2).
• Shared storage guidelines. New guidelines apply for configuring storage
subsystem data protection in everRun MX 6.1. See System Administration >
Configuring PVM Resources > Storage in the Online Help for information.
• Platform-specific management applications. Dell OpenManage, Fujitsu
ServerView, and HP Insight Manager are supported. If you plan to use one of
these applications, you may install it anytime after you install XenServer.

NOTE: For optimum performance, it is strongly recommended that you always apply
the latest BIOS version available for your platform before installing everRun.

• everRun supports the new XenServer CPU masking feature, which is available
in XenServer advanced management editions (Advanced, Enterprise, and
Platinum). This feature allows servers configured with different generations of
processors to join the same resource pool. However, the recommended best
practices for everRun CPU compatibility remain as outlined in the everRun
Configuration Planning Guide and the CPU Compatibility Checker.
• The Marathon-supplied XenServer license no longer includes XenServer High
Availability (HA); this feature requires Citrix XenServer Advanced Edition
software or greater. For information on purchasing and installing this license,
visit http://citrix.com. Also note that the Advanced Edition must be installed using
a Citrix license server, as described in “Licensing XenServer” in the Citrix
XenServer Installation Guide.
• XenServer Thin Provisioning Not Supported in everRun. Thin provisioning
of Storage Repositories (SRs), introduced in XenServer 5.6, is not supported for
use with everRun configurations. Do not implement either of the following options

2 everRun Release Notes

 in your everRun system:
- When adding an SR to a VM or protected VM, do not check the box to
select the "Optimize for thin provisioning" option.
- Never select any option that enables thin provisioning.

Important License Information

The everRun product includes a XenServer license to enable the XenServer hosts. This
license (as a *.xslic file) can be downloaded from the Marathon product web site, and
must be applied to each host during installation, using the process described in the
XenCenter online help. If you plan to use XenServer HA (Level 1 protection) in your
pool, contact your Marathon representative, or obtain the appropriate license from
Citrix, as described in the final item listed on page 2 of this document.

The everRun license is applied to the pool (not the individual servers), as described in
the everRun Online Help topic, “Installing an everRun License Key.”

Advisory: Incorrect Upgrade Sequence will cause Upgrade

Failure
Do not update to XenServer V5.6 SP2 until after a new Marathon OEM
XenServer license has been applied. Due to an incompatibility between the
existing Marathon OEM XenServer license (for XenServer V5.5 Update 2) and the
newer version of XenServer, the upgrade to everRun MX V6.1.0-RL will fail if you have
updated your XenServer installation to V5.6 SP2 prior to applying the latest Marathon
OEM XenServer license (.xslic) file. Please follow the revised procedure described in the
Upgrade Guide (Document Edition: 6.6.2011) included with this documentation set to
avoid any problems or issues during upgrade.

Version-Specific Online Help and Document Access

Starting with Release 6.1, the eAC allows you to access the version of Online Help and
documentation associated with the everRun software running in a selected pool. If you
launch eAC from a pool running v6.1, for example, then select a component from that
pool and open Online Help, the displayed help topic contains v6.1 information. If you
select a component from the pool running v6.0 and launch Online Help, the displayed
help topic contains v6.0 information.

This is important when you are managing multiple pools and need to view Release
Notes or other version-specific information. When managing multiple pools, it is
recommended that you launch the eAC from a pool that is running the newest version
of everRun.

A message is displayed in the status bar at the bottom of the eAC when you are
managing a multiple-pool environment and the Online Help or documentation you are

everRun Release Notes 3

currently viewing is associated with a different version of everRun software than the
version running in the launch pool.

The first part of the message identifies the IP address of the host providing the
currently displayed Help or document. The second part of the message identifies the IP
address of the host you can select to view help or documentation associated with the
software that launched the eAC.

NOTE: To locate the IP address of the pool you are currently accessing, look at the URL
for the Online Help you are viewing.

Advisory: Enable Multipathing on Fibre Channel Storage

If you are configuring fibre channel shared storage for your pool, Marathon strongly
recommends that you enable multipathing on the storage respository.
Without multipathing, guest VMs with a virtual disk image (VDI) configured on the
associated FC SAN will not recover storage access properly following repair of a FC
SAN until you restart the XenServer host. When multipathing is properly configured,
you will avoid this problem. For more information, search the Citrix website for articles
on multipathing, or contact Marathon Technical Support. The everRun Setup and
Installation Guide describes how to enable multipathing.
Issues and Limitations
The following tables list issues and suggested workarounds that apply to the everRun
6.1 release.

Installation Issues

Description Workaround/Comment ID

Running the Citrix XenServer Marathon recommends that you install 2079
console window by typing everRun from the XenCenter Console
xsconsole in the Console tab window before you open xsconsole.
window of XenCenter affects
the appearance of the everRun
installer screens.

4 everRun Release Notes

 Description Workaround/Comment ID

An iSCSI/FC everRun install Where possible, install everRun to a disk on a 2131

disk may be marked as read- local storage repository. If iSCSI or Fibre
only if the path is lost and Channel is used, be sure to use multipath
recovered. drivers. For best availability, do not assign
the same iSCSI/FC storage system for your
everRun storage device on two or more hosts.
If the disk becomes read-only, you may need
to reboot XenServer in order to recover.
Currently, 64-bit browsers do You can use a 32-bit browser on a 64-bit 2190
not support Adobe Flash operating system to run the eAC with Flash
Player, which is required to Player. Adobe is currently working to provide
connect to the everRun eAC. native support for 64-bit platforms in an
upcoming release of Flash Player.
After a XenServer upgrade or The message can safely be ignored. It is 3170
fresh install, the XenServer caused by a temporary condition that occurs
software generates a system during software installation, and the
alert for each upgraded host: condition is corrected after the everRun
“A storage repository could not installation completes.
be attached when <server
name> started.
After installing XenServer, a To avoid this, always update to the latest 4267
“time went backwards” version of BIOS available for the platform
message may appear in the before installing the XenServer software.
XenServer log file.

System Management Issues

Description Workaround/Comment ID

Although the eAC allows you Virtual machines that contain more than the 2874,
to add a fifth virtual NIC to a maximum number of redirected NICs can not 3228
PVM, an error code will be be protected with everRun. everRun supports
generated when this up to 4 virtual (redirected) NICs per
configuration is specified. protected Windows VM (PVM), and a total of
8 redirected devices (NICs and disks
combined) per PVM.

everRun Release Notes 5

 Description Workaround/Comment ID

After recovering from a power In XenCenter, disconnect from the pool and 3133,
failure on the primary host, close XenCenter; then restart XenCenter and 3535
XenCenter may lose access to reconnect to the pool.
the active CI in a protected
VM. XenCenter may also
become slow to respond after
it has been running for some
time — particularly under
heavy loads.
Resynchronization of Level 3 Marathon requires a minimum capacity of 155
PVMs or online migration of Mbps for all network components such as
Level 2 PVMs may fail when switches or uplinks. The best practice is to use
100 Mbps Ethernet is used for 1 GB Ethernet adapters for management
the management LAN. links, as described in the everRun
Configuration Planning Guide. Further, the
minimum requirement for a SplitSite
configuration that includes PVMs protected at
Level 3 SMP (FT-SMP) is two 1GB Ethernet
adapters for availability links. When
providing these minimum bandwidth
requirements, be certain no switch or uplinks
can reduce the effective bandwidth below
supported minimums.
If you attempt to start a PVM After the second host successfully exits from 3356
on a XenServer host and the maintenance mode, you will be able to restart
other host is in maintenance the PVM.
mode, a five-minute timeout
occurs and the PVM shuts
down.

6 everRun Release Notes

 Description Workaround/Comment ID

When a XenServer VMPR The VM Protection and Recovery (VMPR) 4208

policy is applied to a feature, available in the Citrix XenServer
XenServer VM, the VM is no Platinum Edition, provides a backup and
longer a candidate for restore utility for XenServer VMs. The feature
everRun protection. If you uses regularly scheduled XenServer
attempt to add everRun snapshots, and can be configured with archive
protection to a VMPR- and delete options in XenCenter.
protected VM, you receive a
"Not a Candidate" message in In order for the VM to qualify for everRun
the everRun eAC. Clicking protection, you must first remove its VMPR
Why Not? displays a brief policy using XenCenter or the xe command
explanation: "VM has line interface. The VM is then a candidate for
XenServer VMPR policy everRun protection. After protecting the VM
applied." with everRun, you can use the everRun
snapshot process to make backup copies of the
PVM.
Note: Do not apply a XenServer VM
Protection/Recovery (VMPR) policy to any VM
that is part of an everRun-protected VM. The
XenServer recovery policy will not work as
expected.
If multipathing is not enabled When you include FC-SAN storage in your 4248
in your storage configuration deployment, some form of multipath FC-
and all paths to a disk on a SANmust be configured to minimize the
Fibre Channel SAN (FC-SAN) likelihood of connectivity loss.
are lost, corrective action will
be required to reestablish
connectivity to the affected
everRun AM once physical
access to the disk is restored.
If you have PVMs that are A server shutdown normally takes only a few 4410
started but not in a fully minutes. Wait for the required redundancy, or
redundant state, an attempt make appropriate repairs and issue the
to shut down a XenServer host shutdown command again. When the
on which such PVMs reside remaining PVMs can evacuate successfully,
may stall unexpectedly. the XenServer shutdown proceeds as
requested.

Contact Marathon Technical Support if you

require assistance with this process.

everRun Release Notes 7

 Description Workaround/Comment ID

XenCenter allows you to If you have reset the MTU value for a 4458
change the properties of any network, you must reboot each PVM that is
network (except the using the network to restore functionality of
management LAN). However, the associated A-link or production network.
if you reset the Maximum
Transmission Unit (MTU) for Note: In this release, Marathon strongly
a network in use by a PVM, recommends using only the default value
the network is disabled. Use of (1500 MTU) on all networks used by a
the associated A-link or protected VM.
production NIC is lost until
the everRun AM is restarted.

Ongoing issues identified in earlier releases are now documented in the

Troubleshooting section of “System Administration” in the everRun Online Help.
Please check that section for help on resolving known issues.

8 everRun Release Notes

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

COPYRIGHT
© Marathon Technologies Corporation 2008, 2009-2011. All rights reserved. Printed in the U.S.A.
This document is copyrighted, and all rights are reserved. No part of the document or the products it
describes may be reproduced by any means or in any form, without prior consent in writing from
Marathon Technologies Corporation.
Marathon everRun products are protected by one or more of the following patents:
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; 6,279,119; 6,473,869; 6,728,898; 7,373,545; 7,877,552.
European Patent Numbers: EP0731945; EP0974912; EP0986784; EP0993633; EP1000397; EP1000404;
EP1029267; EP1496434; GB2392536; Japanese Patent Numbers: 3679412; 4166939; 4264136. Other
patents pending.
Marathon Assured Availability, The Application Availability Experts, ComputeThru, everRun,
SplitSite, and the Marathon logos are registered trademarks or trademarks of Marathon Technologies
Corporation. Copyright © 2008, 2009-2011, Marathon Technologies Corporation. All rights reserved.

SOFTWARE COPYRIGHT NOTICE

The software described in this document is covered by the following copyright:
© Marathon Technologies Corporation. 2008, 2009-2011.

GNU PUBLIC LICENSE AND LESSER GNU PUBLIC LICENSE

The product makes use of software covered under the GNU Public License (GPL) and the Lesser GNU
Public License (LGPL). For a written copy of these licenses, see /var/everRun/current_everRun/
licenses on any XenServer host on which everRun VM is installed. Marathon will make source
components available upon request, via email to [email protected], as required
under the terms of the GPL.

TRADEMARK NOTICE
Microsoft® and Windows® are registered trademarks of Microsoft Corporation in the United States and/
or other countries; Xen® and Citrix® are registered trademarks and XenServer™, XenCenter™, and
XenConvert™ are trademarks of Citrix Systems, Inc.; Java® is a registered trademark of Sun
Microsystems; Linux® is a registered trademark of Linus Torvalds. Intel® is a registered trademark of
Intel Corporation. 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 everRun MX 6.1.
Marathon Technologies Corporation
295 Foster Street, Littleton, MA 01460
(978) 489.1100 or (888) 682.1142
www.marathontechnologies.com

everRun Release Notes 9

10 everRun Release Notes