• Solutions
  • By Industry
    • Distribution
    • Security
    • Gaming
    • Government
    • Healthcare
    • Manufacturing
    • Media & Entertainment
    • Travel, Transportation & Logistics
  • By IT Need
    • Proactively Prevent Downtime
    • Protect Data for Compliance
    • Achieve Disaster Resilience
    • Reduce CAPEX & OPEX
    • Provide HA in Remote Locations
  • Small & Medium Business Solutions
  • Windows Business Application Availability
    • BlackBerry HA
    • Exchange HA
    • SharePoint HA
    • SQL HA
    • XenApp HA
    • BlackBerry DR
    • Exchange DR
    • SharePoint DR
    • SQL DR
    • Virtual Server DR
• Products
  • Overview
  • everRun MX
  • everRun MX Express
  • everRun MX Extend FT+DR
  • everRun SplitSite
  • everRun HA & FT
  • everRun Advantage
  • Product FAQs
• Services
  • everRun Services Overview
  • Consulting Services
  • Training Services
    • Authorized Training Centers
  • Assurance Program
  • Customer Portal
  • Requesting Technical Support
  • Technical Community Login
  • everRun Assist Web Support
• Partners
  • Partners Overview
  • Citrix Alliance
  • Microsoft Alliance
  • ISV Partners
  • Why Resell Marathon
  • Partner Program FAQs
  • Find A Reseller
  • Partner Login
• Resources
  • Resource Center
  • White Papers
  • Webinar Recordings
  • ROI Calculator
  • Collateral
  • Flash Demos
  • Glossary
    • Symmetric Multi-Processing
    • Continuous Application Availability
    • Application Availability
    • Disaster Recovery
    • Failover
    • Fault Tolerance
    • High Availability
    • High Availability Cluster
    • Server Redundancy
  • Customer Endorsements
  • Success Stories
  • Product Reviews
  • Analyst Opinions
  • Exporting everRun Products
• News & Events
  • Latest News
  • Press Releases
  • In The News
  • Events & Webinars
• About Us
  • Overview
  • Announcement
  • Why Marathon
  • Executive Team
  • Board of Directors
  • Awards
  • Careers
    • Current Openings
    • Benefits
  • Corporate Offices
  • Contact Us

Blog

LAN Magazine, a leading IT publication in the Netherlands, recently published an in-depth review of everRun 2G titled, “High Availability for the Masses.” You can read the review (in English) here. Bram Dons, the reviewer and author of the article, had this to say about everRun 2G:

"Although recovery certainly plays a role in high availability, it is much more about preventing downtime and data loss. Marathon Technologies shows this with the new everRun 2G."

“In all evaluation tests we have conducted to date, Marathon’s everRun 2G is the only software product that manages to provide complete continuity in all circumstances. Failure of system components, power interruptions—the product does not fail."

To read additional reviews of everRun from leading IT publications like eWeek, Network Computing UK, and IX Magazine, check out our product reviews page.

Earlier this week, we had a great webinar featuring guest speaker Greg Cullen, Sr. Director of Technology at Marathon. Greg provided tips and advice that government agencies can use to ensure optimal availability for their critical applications at minimal cost. He also reviewed  three different government agencies that protected their data and applications from downtime with Marathon’s everRun software.

These included the Brookline Police Department, which kept their 911 system available – even during a hardware failure on Christmas day when no IT staff were on duty; the City of Santa Rosa utilities department, that protects its water treatment facility against outages from earthquakes, power outages and other natural disasters; and a county court system in California that protects its virtualized Exchange server and other paperwork processing applications from downtime.

The transcript of the Q&A session with Greg from the live webinar is below.
 

Q: Can you deploy the two everRun servers in different locations or do they have to be in the same location?
You absolutely can. You can deploy the two servers in the same room, or different rooms in the same building and even in two separate buildings. We call that configuration SplitSite. That’s one way to get disaster tolerance in the event that you have a site-wide outage, rather than having them in the same room or building.

Q: Is there a limit to how far apart the servers can be?
In general, they can be separated by as much as 100 miles, although it really depends on your bandwidth and latency on the connection between the two sites.

Q: What are the hardware requirements for everRun?
You’ll need Intel-based servers that have a moderate amount of memory, or as much as the application requires. And you’ll need enough networks to do the production side of it as well as maintaining the redundancy between the severs. Generally speaking, having four network adaptors in each server and somewhere in the order of 100GB of disk drive is sufficient.

Q: How does the everRun software compare with a clustering solution?
One of the biggest difference between everRun and clustering is that everRun is a single image for the application. Instead of installing and managing two instances of your application like you do with clustering, everRun is just a single image to install and manage. Changes happen on both servers simultaneously through that single image.

Also, everRun software does not require cluster-aware applications. everRun is application agnostic, and can support almost any Windows application. And one more thing, with most clustering solutions, you also need to have a shared storage container that both servers are connected to. everRun can support that model as well, but doesn’t require it like clusters do. In fact, to remove single points of failure, it’s much better to have local storage connected to each of the servers and everRun will manage that storage as a mirrored device.

Q: I’m confused by your use of DR. Can you define what you mean by disaster recovery?
We’ve found that everyone has a different definition of what they mean by disaster recovery. At a very high-level, we see disaster recovery as the need to protect your data. By comparison, we see high availability as the need to protect your application, data and network connectivity. DR means you’re trying to copy your changed data off site to protect it in the event of a true disaster. After the “disaster” is over, you then need to bring that data back to the primary site, or configure an alternate server to use the data in the DR site.

Q: Does everRun work with Siemens building security systems?
Yes, we have been working for several years with building automation and security companies including Johnson Controls, Tyco, Andover Controls, Siemens and many others. As long as the building system runs in Windows Server 2003 or 2008, we can provide availability for it with no custom scripts or custom coding. We have many deployments of everRun protecting these building security systems around the world.

Q: Does everRun work with e911 systems?
Yes – absolutely. Generally speaking, everRun is application agnostic and can work with almost any Windows application. We have many solutions out there where these emergency 911 centers are protected by everRun so that if there is some type of disaster, these systems continue to run.

Q: Is everRun available on a GSA schedule?
Yes, through our channel partners. Contact your Marathon account representative or call 978.489.1100 for specific partner information.

Q: How does everRun differ from data replication solutions?
A lot of times when people look at availability, they simply try to replicate the data. There’s a big issue with that though. That’s only one part of what you need to recover in the event of a failure. everRun not only replicates the data, but also keeps a redundant set of your application environment and network connectivity, and everything else that is required for the application to not see any failures at all, or to recover very quickly in the advent of certain types of failures.
 

We’re very excited to announce our partnership with NEC Philips Unified Solutions today. Through this partnership, Marathon’s everRun software will provide high availability and fault tolerant capabilities for several of NEC Philips’ business communication systems, including the SIP@Net server and Business ConneCT and MA4000 applications. These new combined offerings will be available to channel partners and customers throughout EMEA.

From left to right:
Gerard Wubben, General Manager, Raxco Software; Nick Turnbull, VP International Sales, Marathon Technologies; Rafael Costa, VP Worldwide Sales Marathon Technologies; Yoshihiko Katsura, Senior VP Portfolio, Applications & Operations NEC Philips Unified Solutions; Paul Kievit, President NEC Philips Unified Solutions; Jim Welch, President & CEO Marathon Technologies; Benne van der Lugt, Director Enterprise solutions portfolio NEC Philips Unified Solutions; and Marco Koenen, Enterprise Business Manager NEC Philips Unified Solutions
 

Signing the agreement: Paul Kievit, President NEC Philips Unified Solutions and Jim Welch, President & CEO Marathon Technologies

Tom Reed, Marathon’s Senior Systems Engineer and MCSE, hosted our most recent webinar on SharePoint High Availability. We’ve summarized the Q&A portion of the webinar below. A recording of the webinar is also available for on-demand viewing.

Q: Do I have to have identical servers to use everRun?

The servers don’t have to be exactly the same; however, the CPUs should be identical as a best practice. For what we call our Level 2 protection (for component level protection of the network and disk), you can use different RAM and spindle speeds on storage. Level 3 protected workloads require the servers to be alike. You can view a complete list of supported processors on our website. 

Q: What kind of storage do I need to use everRun?

One of the great things about everRun is that it is storage agnostic. It doesn’t matter what type of storage you are running. You can work with SAS drives, and iSCSi, local or fibre SAN, pretty much any type of storage and it doesn’t have to be the same on both sides. Some customers using everRun SplitSite are using SAN at the primary data center and local disk at the secondary data center, which can save storage costs.

 Q: Does everRun DR integrate with SRM from VMware and how does this work with VMs as a second server?

VMware SRM, or site recovery manager, is designed to asynchronously replicate the actual virtual machines to a secondary site. It does this by using replication software at the SAN level. So once you purchase SRM you have to purchase SAN replication software as well. If you didn’t want to replicate the actual virtual machines over, what you could do is use everRun DR, the difference being that we do not bring over the current virtual machine. We have a separate vm built and we have the capability to start and stop service, recover from a single point in time, and drag and drop recover files on a replicated data drive. If you are looking for an in-depth comparison of VMware SRM vs. everRun DR, you can contact us at 800.884.6425 or via email for more info.

 Q: How much overhead does everRun place on the protected server?

General use cases today are 3-10%. We have application performance documentation for Exchange 2007 and XenApp that you can download from our website. We will have a similar document for SharePoint in early 2010.

 Q: How does everRun differ from a backup solution?

We have found that there is a lot of confusion in the industry around the difference between backup vs. high availability. Backup solutions are designed to provide a disk-to-disk or disk-to-tape scenario for recovery of data. Backup is a recovery option, not a prevention option. It lets you recover to your last point in time, last snapshot, or last tape. Again, this will not prevent downtime or provide availability for users. It is a means of recovery. everRun DR can provide this type of solution if this is what your business needs. If your goal is to prevent outages and data loss (rather than recover from them), what you really want is a local high availability solution. 

Q: What version of Windows does everRun support?

everRun supports Windows Server 2003 SP2 Standard and Enterprise Editions, 32-bit and 64-bit, as well as Windows Server 2008 Standard and Enterprise Editions, 64-bit.

 Q: Does everRun work with SQL 2008?

Yes. everRun supports any Windows application without requiring changes or customization. Because everRun resides below the operating environment, we are protected underneath that. We have a number of ISVs that use our software with their applications and they use us because they don’t have to make any changes to their software. It’s not tied into the application, and doesn’t need to be “cluster aware” or anything similar to that.

 Q: Can I use everRun between two VMs? Meaning two VMs instead of two physical servers?

We build out the virtual machines when you install our software, so if you’re using our VMs to build out your machines, then we can do that.

 Q: Do you have experience using everRun in education environments?

Yes, a couple of examples of everRun being used in education environments include Michigan State University in the US, and Wellcome Trust Sanger Institute in the UK. We have several additional education customer examples and references that we can provide to you. Give us a call at 800.884.6425 for more information.

Q: How do you determine when to use everRun HA vs. everRun DR solution?

A good method for determining which solution is most appropriate for your situation is to take a closer look at your Recovery Point Objective (RPO) and your Recovery Time Objective (RTO). How long can you be down and how much data can you lose? If you can be down for several days, then you want to look at a DR solution. Just take into consideration that while DR failover is sometimes necessary, it can be a lengthy, complex process and is sometimes invasive to your environment. First you have to failover to the DR site and then failback when the primary site is restored, which can be very time consuming. 

The majority of failures are not catastrophic. Most are pretty common like network issues or hardware failures. For this scenario what you should really look at is local high availability protection. For the most complete protection overall, best practices are to have local high availability protection and then DR as a back-up for a major disaster. Then at the DR site you should also have an HA solution because if you do have that major catastrophe and failover, you want to make sure that secondary environment is protected while you are re-building the primary site.

 Q: What are some large county government examples using everRun software?

everRun has been deployed by many different government agencies. You can read about deployments at the Brookline Police Department, the County of Chester (Pennsylvania), and the City of Santa Rosa, California Utilities Department on our website. We also have many more government customer examples and references that we can provide to you. Give us a call at 800.884.6425 for more information.

 Q: When using everRun, can I use the secondary server to backup the data to avoid impact on the primary production server, or will both servers feel the impact during the backup window?

You should run your backup on the active server. On the secondary server, the workloads are in paused mode, so you can’t run a backup agent there. If you run it on the primary server, then it’s cloned over to the secondary server automatically.

 Q: Does everRun guarantee no downtime, or 99.999?

Yes,we provide 99.999% (5 9’s) protection with our Level 3 system fault tolerant protection.

The 2010 Winter Olympics may still be a few months away, but everRun has recently added a couple of medals to the trophy case, including the 2009 Windows IT Pro Magazine Editors Gold Award in the “Best High Availability/Disaster Recovery Product” category, and the Bronze award in the "Best Mid-range Software" category from TechAwards Circle.

Marathon has received 16 industry awards in the last two years. Congratulations to the everRun team for producing such an outstanding product worthy of industry recognition 16 times over!

Thanks again to those who joined us for the everRun 2G live demo. An on-demand recording is now available to watch at your convenience.

We had quite a few questions and couldn’t get to all of them during the webinar, so we’ve put together a recap of all of the questions and answers below, including the ones we weren’t able to get to during the live event.

Q: You said that everRun supports any Windows application. Does that include Oracle DB too?
Yes. Any application that runs on Windows is supported by everRun. Custom applications that run in Windows are supported as well.

Q: Does workload mean a virtual machine that is running inside of everRun 2G?
Yes, that’s correct. A workload is a virtual machine that has its own Windows environment, its own application environment, and its own identity.

Q: Can you upgrade to everRun 2G from 7.1 or is it a new installation?
everRun 7.1 is the previous version of our product, and sits on a Windows base. everRun 2G is based on XenServer. As such it requires a new installation. We have a process to help you migrate your virtual machine from everRun HA or FT to everRun 2G. We also offer services to perform this migration.

Q: In everRun FT we need 3 windows licenses, 2 for co-servers and 1 for FT... how many Windows licenses do we need for 2G?
We always recommend that your check with your software vendors and license agreements on this question. For Windows, you do need a valid licensed copy of Windows on both hosts. If you have the Enterprise version of Windows, you can have multiple workloads there using the same enterprise license. Be sure to check with your Microsoft representative or other vendors for specific licensing questions.

Q: What is the base operating system running on Xen Hosts?
XenServer is the base operating system. everRun runs on top of XenServer.

Q: In an environment such as the one shown on your slide, would you be paying for two licenses of MS Exchange?
You should always check with your vendor and/or license agreement to ensure you have your applications licensed correctly.

Q: Can everRun be deployed on an existing server without a rebuild of the OS or server?
It can be if the existing server is running Citrix XenServer. In this case you would simply layer on everRun. If you have a Windows server with Windows on the bare metal, you would have to reconstruct that environment.

Q: What are the benefits of moving to everRun 2G for customers who are currently running everRun HA or FT?
everRun 2G is the next generation of everRun HA and FT, enabling multiple levels of protection within a single solution. While there are a number of new capabilities within everRun 2G, one of the most significant enhancements is the ability to protect multiple Windows workloads on a single pair of servers. With everRun HA and FT, only a single Windows workload can be protected on a pair of servers. everRun 2G allows multiple workloads to be protected on the same pair of servers to help reduce hardware costs and take advantage of more powerful servers. From a supported platform standpoint, everRun HA and FT support Windows Server 2003 32-bit Standard and Enterprise. everRun 2G supports Windows Server 2003 32- bit and 64-bit Standard and Enterprise as well as Windows Server 2008 64-bit Standard and Enterprise.

Q: How would you plug the NICs from each server to your network so that a faulty switch would not mess up the redundancy?
As a best practice to remove any single point of failure, redundant switches would be deployed.

Q: What is the maximum distance/geographic location for two physical servers to work using everRun?
The answer to this question is based on latency and bandwidth. It depends on the network connection. We have a latency requirement of 5ms roundtrip between the two servers to maintain the synchronous state that we provide. We have customers that separate servers campus-wide, and customers that run up to 50-100 miles with a dedicated fiber connection between the two servers. It depends on what your needs and requirements are and the network that runs between the two locations.

Q: At what intervals does everRun monitor the standby server?
It checks constantly. One of the things everRun does that is unique is active validation. We are constantly utilizing and validating the secondary server and all its devices. We’re doing disk I/O, we’re doing network reads, taking packets in from the network so that we know the network is good and the CPU is good. We’re actively validating all of the components. With a back-up site, it could be weeks or months since anything has run on the secondary server. So if there’s a failure that goes unnoticed on the backup server, and then there’s a failure on the primary, it has nowhere to go. With everRun, the secondary system is being actively validated at all times so that you know it will work in the event of a failure.

Q: Does Level 3 protection require shared storage?
It does not. everRun offers two storage configuration options; mirrored storage and a shared storage model. When using mirrored storage, everRun will synchronously mirror all data between paired hosts; this includes the OS, the application, data, etc. This does not require similar storage vendors or types. One host can have SAN-attached storage while the other has local SCSI storage. In a shared-storage configuration, the everRun paired hosts must be connected to the same storage device with access to the shared LUN’s. In this configuration, everRun does not mirror the data or protect against failures within the storage subsystem. Because of this, it is critical that you ensure proper configuration of the storage devices to protect against failures.

Q: How much hardware similarity do you need between the hosts in a pool?
It’s really tied to similarities in processors, not servers or disks. For a complete list of hardware that is supported, view our Supported Processor List.

Q: Does everRun having rolling upgrade support?
There are capabilities to assist with applying updates and performing maintenance. To be clear, everRun does not allow applying a service pack without having to reboot the server, if the service pack requires it. Contact Marathon for more information on this capability.

Q: Do you have plans to support Hyper-V?
We plan to support Hyper-V in a future release.

 Q: Do you have some experience about Oracle Applications in that (virtual) environment - are there any references?
We do have customers running Oracle. Please contact our sales department for references.

Q: Is the Xen server running over Windows, Linux, Unix?
XenServer runs on the bare metal. It does not run ‘over’ any other OS.

Q: If you have an Exchange server that is separated by a WAN, how does the client connect to the 2nd server when we lose network connection on primary?
Each of the everRun-protected hosts must be in a common subnet or vLAN.

Q: Will the system still run in this scenario: disk is not working / has fault on host 1 while host 2 has a problem on the NIC both at the same time?
Absolutely. everRun will handle each of these failures simultaneously without any disruption or interruption to the application.

Q: Can a workload be running on Linux?
Linux workloads are not currently supported for protection by everRun. Unprotected Linux workloads can be created, however.

Q: How do you remotely monitor the system and get automatic notification of hardware failures – e.g. SNMP?
SNMP will be available in the near future.

Q: Will everRun work over WAN and if so what is required?
5ms latency and 155Mb bandwidth per protected workload.
 

We had a fantastic presentation last week from IT expert and author Niel Nickolaisen. Niel shared his proven methods for reducing downtime and improving the alignment of IT resources to better support business goals. If you weren’t able to attend the live event, you can watch the recorded version here.

If you prefer a white paper format, Niel’s strategies and best practices have also been summarized in a brand-new 8-page white paper, “Reduce Downtime by 70% - Without Spending a Dime” which you can download here.

The Q&A session from the live webinar with Niel Nickolaisen and Michael Bilancieri of Marathon has been summarized below:

Q: Can you give some tips on how I can educate my branch offices about my business continuity plan?
Niel Nickolaisen, CIO: At Headwaters, Inc., we have 120 remote sites. We approached this from an SLA perspective. We translated how the SLAs affected the operations at our branch locations. Then we communicated it and got them to buy into the SLAs and the things we were doing and suggested that they followed our lead.

Q: How often should you update your disaster recovery plans?
Niel Nickolaisen, CIO: In our case at Headwaters, Inc., we have Sarbanes-Oxley regulatory requirements. We do an annual formal risk assessment both for our business and for IT. When we’re done with that assessment we update our disaster recovery plans, which are based on the risks. Our disaster plan is designed to mitigate or recover from the risks that we’ve identified.

Q: How does everRun work?
At a high-level, everRun takes your entire Windows environment and protects it as a whole. Most protect from within the OS but we protect from underneath the OS. We clone to a second system for redundancy in a synchronous fashion. A good way to understand how everRun works is to watch our product demos videos and flash demos available on our website.

Q: How does everRun fit into a virtual environment?
everRun allows the ability to create multiple workloads on a single server. Our technology is based on virtualization technology – we’re virtualizing two instances to appear as one. You can create multiple workloads and put them on the same server and protect them. It’s based on Citrix XenServer.

Q: Will this work in conjunction with SAN offhost backups using Vertias Netbackup and FlashSnap option?
We are agnostic to the storage. If you’re using back-up right from the SAN, that’s fine. You can also use a mirrored option, where we can mirror the entire system in a synchronous fashion. That allows you to have SAN on one side and NAS on the other, or direct-attached, or both. It’s your choice, which gives you greater flexibility. You can separate the servers as well between buildings. The other option is a single copy of storage, not mirrored and both systems can connect to that storage, but the SAN device will then have to protect the data.

Q: How can Marathon contribute to companies considering a move to SAP?
everRun can provide availability and fault tolerant protection to that SAP environment. If you’re considering a move to SAP, I would assume you have had some discussions about how to protect that—the SLA, the data, availability and disaster recovery. everRun can protect and provide disaster tolerance disaster recovery, and high availability for that application, as well as data protection. We don’t cause any changes to the application.

Q: Should Marathon be brought in as a consultant before SAP is contracted?
Sometimes it’s a good idea to have a joint discussion with vendors. A lot of times when you look at availability and redundancy or data replication, it’s doing things to the applications and data and can cause interaction issues. Sometimes the application has to be configured in a certain way, so you want to know up front how your high availability solution could affect the data and application. We can certainly do a call with any other software vendors to have that conversation up front.

Q: What version of Windows does everRun support?
everRun supports Windows Server 2003 32-bit and 64-bit and Windows Server 2008 64-bit.

Q: What kind of performance impact does the synchronous lock-step have on the system?
That varies by application, users, data, I/O, and other factors. In general, it can range from 10-20% on your application – we’ve seen less than that and more than that, depending on the system.

Q: Do you recommend WAN optimization to be used?
Our requirements are around bandwidth between the two systems if you want to separate the systems. WAN optimization tools don’t always help. It’s really a latency requirement to maintain good performance.

If you'd like to learn more about Niel's best practices for aligning business and IT resources, be sure to check out his new book, Stand Back and Deliver: Accelerating Business Agility.

Congratulations are in order (again!) for the Marathon team. everRun 2G has been selected as a finalist by Tech Awards Circle in the Best Mid-Range Software category. Tech Awards Circle recognizes the products, services, vendors and individuals making a difference in the industry today. Entries are judged by an independent circle of publication reviewers/journalists, each with at least a decade of experience covering technology from consumer electronics to enterprise-class computing. Winners will be announced at the end of October.

Nov. 10 update: Marathon's everRun 2G has been selected as the Bronze award winner in the "Best Mid-range Software" category. Congratulations once again to the everRun product team for another great award win!

Congratulations to Thomas Burgdorf of Mii Management Group, the winner of a $100 American Express gift card from our recent everRun 2G demo webinar. If you weren’t able to attend the live event, a recording the everRun 2G demo webinar is now available for on-demand viewing here.

Be sure to join us for our next webinar on Oct. 8th, featuring IT process expert and author Niel Nickolaisen. We're really excited to have Niel as our guest speaker for this webinar. In addition to his 25+ years of IT experience, Niel is the CIO and Director of Strategic Planning at Headwaters, Inc. and also writes regular columns for the CIO Leadership Network and TechTarget's Search CIO. Niel is going to share his proven methods for reducing downtime, including:

* Conducting a gap analysis of your current IT processes
* Identifying weaknesses that can lead to downtime
* Simplifying IT processes so that your entire staff can understand and follow them

We're expecting a large group for this webinar, so be sure to register today to reserve your spot.

Thanks again to those who joined us for last week’s webinar, "Windows Server 2008 High Availability: Technology Comparison." The on-demand recording of last week's webinar is now available to watch at your convenience (here).

We had a lot of good questions from our attendees during the Q&A portion of the webinar, which are summarized below.

Q: How do you determine when to use an HA solution vs. a DR solution?
When it comes to availability vs. recovery, the most important question to ask is what are your recovery time objectives (RTO)? What is the amount of time your application can afford to be down? If the applications have strict requirements, then you want an availability solution. Disaster recovery is data replication often times with a failover capability, not availability. For critical applications, this may not be sufficient.

Q: If I have an HA solution in place, do I still need a solution for backup?
Availability and backup are two different things. That question comes up a lot, along with the need for disaster recovery. Backup will never likely go away completely. You still need to backup your data to ensure recovery in the future should that be necessary.

Q: Is everRun available for Linux applications?
Yes. We can provide basic failover capabilities for Linux applications today.

Q: How does everRun differ from replication solutions?
everRun 2G is used for availability, both locally and for short-distance geographic separation as well. We have a replication and recovery solution as well that can be used for disaster recovery for long distances. You should determine what your objectives are: do I have to keep my applications up and running or do I just need to recover it if something fails? What’s the recovery time objective for each application? It’s up to your individual applications and what level of protection you need for each. Often times availability is a priority as downtime is not desirable, with DR also a requirement on top of that to ensure recovery in the event of a major outage.

Q: Can everRun be used for planned downtime (i.e. to keep one host running for end-users while the application on the other host is being upgraded)?
Yes, everRun can be used to help facilitate certain system updates to reduce interruptions and mitigate risk.

Q: Can it work between two virtual machines and on x64 based systems?
Yes, we support XenServer and 64-bit hardware and Windows Server environments.

Q: What is the performance impact of using everRun 2G?
That’s variable depending on your application. It can be anywhere from 3-15%. We’ve done some performance testing specifically on XenApp and Exchange. You can download those white papers here:
• Understanding and Characterizing Performance Implications for Running Exchange 2007 with everRun
• XenApp 5.0 High Availability Performance

Q: Does Marathon offer backup solutions for everRun users?
We have methods to backup your systems and we’re working improving on our current offerings to make them quicker, easier and more granular.

Q: Can everRun work with dissimilar hardware? Can everRun work with more than two servers?
From a server standpoint, you just need similar processors; storage does not need to be similar. You can have SAN on one side and NAS on the other or any other combination. On the second question, yes, everRun will work with more than two servers. You can build a pool of servers and protect within that pool.

Q: Does everRun have backward compatibility with older OS?
Yes. It will work with Windows Server 2003, and also Windows Server 2008.

Q: Can everRun run on the Foundation Server Edition of Windows 2008?
It does not. everRun supports the full implementation of Windows Server 2008. everRun runs underneath Windows, it does not install into Windows.

Q: How does everRun handle data stored on NAS?
Storage is transparent to everRun. We look at storage as just a LUN.

Q: What is difference between everRun HA and everRun 2G in Windos Server 2003?
The differences are the ability to create multiple workloads. HA can protect one workload. everRun 2G can protect multiple workloads. There is also a new and improved graphical interface with better reporting and management capabilities.

Q: Does everRun work with XenServer 5.5?
Yes, everRun works with XenServer 5.5.

Q: Are there any changes in WS 2008 & WS 2008 R2 in the way that HA improves?
Yes. You can find an overview of those changes directly from David Hanna of Microsoft in our recent webinar and white paper “The Top 10 Reasons to Upgrade to Windows Server 2008.” You can also read the Q&A with Microsoft from that webinar here.

Q: Is everRun 2G available for Microsoft Hyper-v?
We will provide support for Hyper-v in a future release.

Q: With applications using various DNS names, how does this solution integrate with DNS changes? (failover to remote office for true DR-different IP/network)
everRun availability solutions pairs systems within the same subnet of vLAN, eliminating the need to make any DNS changes.

Q: Question is tied to what permissions are needed to do a recovery. For recovery in active Directory most items need to replicate around that there was a change and we do not want to hand out Admin control over the domain(separation of access)
everRun is designed to not require any changes to Active Directory during or after a failure or recovery.

How many times do you check your email each hour? Recent studies have shown that the average worker checks email once every 15 minutes, with some users checking email as often as 40 times per hour. In addition, growing use of iPhones, BlackBerrys and similar email-enabled mobile devices means that employees have become attached to their email at all times, with some checking their device as soon as each email arrives. Now that email has evolved into a must-have business communications tool, employees have come to expect access to their email 24x7, with very little tolerance for downtime.

Meeting the “always on” expectations of employees creates challenges for the IT administrator. Service-level agreements (SLAs) are increasingly stringent and demanding as users require non-stop access to email and other collaborative features of Microsoft Exchange. Availability of Exchange is paramount, as well as protecting the integrity of your Exchange data. In order to maintain Exchange availability, every component of the Exchange infrastructure needs to be considered. You can protect your mailbox server to the highest degree, but if your DNS server fails, the Exchange server may not be accessible.

To help your company protect its Exchange environment, Marathon has developed a series of steps for achieving optimal Exchange availability. The tips are designed to help identify what availability levels should be designated in order to achieve Exchange SLA commitments with fewer resources and lower costs.

Define Availability Objectives
Creating availability objectives is an important first step in formulating Exchange protection strategies. This is typically done by establishing Recovery Time Objectives (RTO), the time it takes for an application to be running again, and Recovery Point Objective (RPO), the point in time to which the IT professional can recover data in case of a failure, for your Exchange environment.

RTO and RPO baselines establish the SLAs you commit to for the overall company, business units, or specific internal groups. You may even have different Exchange SLAs for different users within your company. For example, you may have an executive group that requires 24x7 email access, while the rest of the company can withstand Exchange downtime of up to one hour. In addition, consideration should be given to what level of protection is needed for the other components of your Exchange infrastructure, such as Active Directory and DNS servers.

Understanding the Levels of Availability
There are multiple levels of availability to consider for different applications and their support infrastructures, starting with basic failover and recovery, moving up to high availability, and all the way to continuous availability for extremely transaction-sensitive applications.

1. The Recovery level is for those applications for which recovery time (RTO) of a day or more is often acceptable. Some downtime is acceptable, and even significant downtime won’t have a detrimental effect on the business. Assurances that recovery will happen is not a requirement.

2. The High Availability level is the home of the majority of applications that run the business, such as email, CRM, financial systems, and databases. These are systems with high downtime costs, and therefore short RTO requirements. These applications require assurances that they will not be down for extended periods should failures occur.

3. The highest level of availability is Continuous Availability in which even brief moments of downtime or a single lost transaction can be extremely detrimental and/or costly to the client or business.

As you establish availability objectives for different groups of Exchange users, you need to consider the protection requirements for your entire Exchange infrastructure, beyond just the mailbox server. You will need to protect all of the components of the Exchange environment, in addition to the different workloads deployed on the mailbox server. Also, don’t forget that the way your company uses Exchange today might change in the future. You may use Exchange today for general correspondence, but within the next year you may plan to use email to process orders. This adds to the need to have multiple levels of availability to assign to the components of the Exchange infrastructure and Exchange user groups. Additionally you’ll need flexibility to change those levels as your business changes.

Assigning Levels of Availability to Exchange Environments
A meaningful exercise to undertake is to apply various levels of protection to your Exchange infrastructure based on your SLA commitments. First look at the users and their requirements for Exchange access. Do you have a single SLA in place for all users, or do you have multiple user groups with different SLAs? If you have a single SLA in place company-wide, you can deploy those users in workloads based on email usage and assign them a single level of protection. However if you have different SLAs for different business groups, you can divide those into multiple workgroups on the mailbox server based on their SLA requirements.

For example, if you have an executive group that needs a 24x7 uptime, then you should consolidate those executives in a dedicated Exchange workload and assign a level of protection that will provide continuous availability. Sales people can often fall into this category as well, requiring non-stop access to email and Exchange collaboration features. Other employees may have less stringent SLAs in place and would require a lower level of protection.

It is also important to keep the components of Exchange, including the DHCP server, DNS server and Active Directory server, up and running. If one or more of these components goes down, requiring the IT administrator to manually intervene could cause excessive downtime for Exchange and exceed your SLAs. Automatic recovery from failures enables you to keep the Exchange environment operating to meet your SLA commitments. Assigning a level of protection to the supporting systems, including the DNS, DHCP, and Active Directory servers, equivalent to that necessary to meet your Exchange SLAs is as important as protecting the actual Exchange servers. Any single point of failure could bring down a well protected Exchange server.

For remote employees and “road warriors”, your company may also have a BlackBerry Enterprise Server (BES) and/or Client Access Server (CAS) implementation, to serve as a secondary or backup method for remote email access. The BES and CAS implementations should be protected to the level you require based on your remote email access strategy and user SLAs.

Establishing RTO and RPO for SLA commitments, determining the right level of availability protection to meet these commitments, and protecting all components necessary to support an Exchange environment will help create n robust and reliable messaging system.

For an even more detailed look at Marathon’s approach to Exchange high availability, download our “Optimizing Exchange High Availability - A New Approach” white paper or our complete Exchange 2007 High Availability Toolkit.
 

Thanks again to those who joined us for last week’s webinar, “How to Get at Least 2x Greater Cost Savings from Server Virtualization.” An on-demand recording is available to watch at your convenience (just click the link.)

We had a lot of good questions from our attendees during the Q&A portion of the webinar, which are summarized below.

How does everRun synchronize and how often?
everRun synchronizes as the data is written to the virtual machine. It’s not done on a time stamp. It is synchronously written to both physical hosts. We do a bit check to make sure both sides are written prior to responding back to the application, stating that it has been written, so that the data is always in a constant state and there is no data loss.

If I already have XenServer installed, can I install everRun on top of it, or do I need to reinstall XenServer?
everRun can be installed into existing XenServer environment. We do have resource pool requirements, so as long as you in a resource pool or can join yourself to a resource pool with a second server, or multiple servers for multiple host pools, we can be installed into an existing XenServer environment.

How does it support local storage? If the server that is hosting the storage goes down, what happens?
We mirror the virtual machine across two servers, so there are two copies of your virtual machine. Where we sit in dom0 (Xen domain zero), we have filter drivers sensing that type of situation. When using Level 2 protection with everRun, if you lose local storage, we leverage the copy of the info on the second server for zero downtime. If you were to lose the entire server, it would failover to the other side and start in Windows services. In Level 3, the same procedure applies to local storage. If you were to lose the entire server with Level 3, everRun allows it to simply continue functioning because we are running active-active.

Have you used this with a building automation system, such as Andover Controls Continuum which runs on a SQL Server?
We have a very large building automation practice here at Marathon and have worked with all flavors of SQL server. We have been working for years with building automation and security companies such as Johnson Controls, Tyco, Andover Controls, Siemens and many others. As long as the building system runs in Windows Server 2003 or 2008, we can provide availability for it with no custom scripts or custom coding.

What's the overhead with regards to CPU, memory, disk space of the host?
Generally in the 3-5% range. We’ve done some performance testing on XenApp and Exchange. You can download the results papers here:
• Understanding and Characterizing Performance Implications for Running Exchange 2007 with everRun
• XenApp 5.0 High Availability Performance

Can everRun be used with homegrown or custom applications?
Yes. everRun is completely transparent to the application and can support any and all Windows applications without any modifications, customizations, or scripting.

Can everRun protect a workload that is physical on one side and virtual on the other?
We do not support P2V today, but we have an ongoing research project on this topic. You can contact your sales rep for more info.

What is the maximum number of workloads that can be run using everRun?
The best way to answer this is to look at your virtualization planning assessment, including power capacity planning and hardware capacity planning. If you can support 10 virtual machines on a server, then you can support 10 virtual machines protected by everRun on that server with no problem. We also require a similar machine as the secondary server running on the same resource pool. It really comes down to how much your hardware capacity can handle.

How to take care of software corruption?
Because we are a synchronously written high availability solution, if there is software corruption on one side, we are going to replicate it to the other side. We sit at an asynchronous block-level filter driver location, so we have no ties to the software. So if it corrupts, it will corrupt on both sides.

Are you currently developing for Exchange 2010?
Yes, everRun will support Exchange 2010.

Does everRun support Small Business Server?
Yes we do. We’ve tested and qualified it for 32-bit and 64-bit versions of Windows Server 2003 Small Business Server Edition.

Does everRun replicate all server data including application data like a SQL database?
Yes. We replicate synchronously at a block level. We sit inside dom0. We then send the info block level to the other side. We do a block check and then we check our bit map to make sure the blocks are synchronously written on ongoing basis.

Can everRun be installed on top of XenServer 5.5 ?
Yes. We will support 5.5 in our next release scheduled for September.

Can we achieve DR?
Marathon offers a couple of options for disaster recovery (DR). Our SplitSite product can be used for metropolitan/campus DR, up to 150 miles apart, depending on your network conditions. We also offer everRun DR, for DR sites that are more than 150 miles apart.

Is the disk mirroring full copy or delta?
Upon initial protection we do a full copy. After you have a failure, such as an iSCSI card failure, we will do a delta copy back over to what’s missing. If you lose the entire RAID set, then we will need to do a full copy again.

Is the price of implementation based on the server capacity?
You need to purchase a license for each server in the pool. In terms of virtual machines (VMs), the license covers as many VMs as you can support in a box.

Douglas Brown of www.dabcc.com recently interviewed Michael Bilancieri, Senior Director of Products and Tom Reed, Senior Systems Engineer. Michael, Tom, and Doug discuss the Marathon everRun high availability solution, what's new, how it works, how it adds value to Citrix XenServer and Microsoft Hyper-V, and much more.

Listen the Show

Our July 30th webinar “Top 10 Reasons to Upgrade to Windows Server 2008 Now” was very well attended, and as expected, generated a lot of good questions. So many questions, in fact, that we weren’t able to answer them all during the live Q&A portion of the webinar.

For your convenience, we’ve captured all of the questions below. Answers have been provided by our speakers, David Hanna, Infrastructure Architect at Microsoft, and Michael Bilancieri, Senior Director of Products at Marathon. The questions are grouped by topic, starting with Windows Server related questions and then Marathon everRun related questions following after.

How seamless is the migration from Windows Server 2003 to 2008?
It really depends on the workload. Active Directory upgrade is similar to the 2000 to 2003 upgrade, and should not be disruptive. Cluster migrations require a rebuild of the cluster. For IIS, many applications can be migrated easily. It’s best to look on Microsoft.com for migration info that is specific to your workload. Simply introducing a Windows Server 2008 server into a 2003 environment should be seamless.

Going from Windows Server 2003 to 2008, do you recommend upgrading or re-installing the operating system?
Microsoft supports an upgrade of the OS only – no applications. Most customers however, choose to reinstall with Windows Server.

What are the hardware requirements for this Windows Server 2008?
Minimum is a 1ghz processor, 512mb of RAM, and 20GB of disk space. Details can be found here: http://www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx

Do you have an actual laboratory so that I can practice Windows Server 2008?
You can find the TechNet Virtual Labs here: http://technet.microsoft.com/en-us/virtuallabs/bb512925.aspx

Any difficulties adding a Windows 2008 Server into a 2003 domain? Anything to watch out for?
Adding Windows Server 2008 Member servers to the domain should not be an issue. There are no special things to watch out for, until you start adding Domain controllers. Note that if you add a 2008 member server, and do not extend the schema, some things will be unavailable, like the enhanced DFS capabilities in 2008.

Where can I get a copy of the Windows Server 2008 trial version?
You can obtain the trial version here: http://www.microsoft.com/windowsserver2008/en/us/try-it.aspx. Starting August 20th, you will be able to get R2 in the same location.

Can I do in-place upgrade AD server 2003R2 to Server 2008 without any problem? Also, can I do that same thing with Exchange 2007 server on SRV2003R2?
Microsoft only supports the upgrade of the Operating System from 2003 to 2008. We do not support the upgrade of Windows Server 2003 with applications, so the Exchange 2007 upgrade would not be supported.

Is it possible to use the same imaging deployment method for Windows 2008 physical and virtual machines (in VMware) for consistent builds?
It is possible to use traditional imaging methods for physical and virtual, however in the virtual environment, most customers tend to use template Virtual Hard disks to deploy systems, as it is faster and more flexible than imaging.

What is the difference between GPO and NAP?
Group policy is a part of Active Directory that allows for management of users and computers. NAP, or network access protection provides endpoint health checking for network clients. This integrates with network components to restrict or allow network access. Client NAP configurations can be controlled by GPO, and some GPO settings can be enforced by NAP.

Does NAP work for VPN connections as well?
Yes. It is integrated with Microsoft VPN as well as some partner solutions.

Does XP pro and 2008 Server talk well together? What’s a better path, upgrade your clients to Win7 then servers to 2008? Or vice versa?
XP will work in a 2008 domain environment, but it won’t be able to take advantage of all of the features of 2008. Vista is designed to complement 2008, and Windows 7 works best with 2008 R2 (or 2008). I would recommend deploying Windows Server 2008 for workloads that will gain the most benefit – this will allow you take advantage of it immediately. Then follow with Windows 7 when you are ready.

Do terminal servers have central management to manage users and applications?
There are a number of tools to centrally manage the environment. R2 adds a connection broker component that will publish apps from multiple servers. However, apps still need to be published on each server, and permissions need to be set that way as well. Citrix provides some great centralized mgmt tools that enhance the native tools.

Will 2008 support XP clients?
Yes. 2008 will support XP for many things including Terminal Services, with RDP 6.1 client, NAP, with XP Sp3, Group policy preferences and many other features. Windows Vista and Windows 7 however, are able to take advantage of more features.

I have two Windows 2008 servers that are going to be setup as a cluster for Exchange 2007. Is there a document for setting up the “heartbeat” connection between the two servers?
There are many documents on technet that will help. When you build the cluster, the validation wizard will check the configuration of the heartbeat network to make sure its configured appropriately. Typically, a 2 node cluster will use a cross-over cable, although a non-routed VLAN on a switch also works. Some docs:

Step-by-step guide for basic 2-node cluster: http://technet.microsoft.com/en-us/library/cc731844(WS.10).aspx
Validating an Exchange 2007 Cluster: http://technet.microsoft.com/en-us/library/bb676379.aspx

Is Server 2008 with Exchange supported on VMware?
Exchange Server 2007 SP1 on Windows 2008 is supported – see here for details: http://www.windowsservercatalog.com/svvp.aspx?svvppage=svvp.htm

Is it possible to run a 2008 DC with 2003 DCs without any sort of hacks or work-arounds?
Yes – it is possible. You’ll need to extend the AD Schema and install a 2008 member server, then promote it to a DC. There are some documents here: https://blogs.msdn.com/canberrapfe/archive/2009/04/08/adding-a-2008-domain-controller-to-your-2003-forest.aspx

Regarding the NAP, once a client is quarantined, is there a policy or rule that the admin must create to get the client healthy? Meaning, is it automatic or does the client sit there until someone checks the quarantined clients and fixes the issues?
NAP can be configured to auto-remediate certain things – turning firewall on, turning on autoupdate, etc. For AV, or patches, users can be directed to a web page with simple instructions or links to update the client.

Has load balancing improved with 2008 and TS?
It has been made simpler. Many customers found NLB to be complicated for what was needed on Terminal Services. TS on 2008 uses DNS round robin for initial connection with the TS Farm, then load balancing across nodes is handled by using RDP session load balancing.

How many CALs are included in the bundle of Windows Server 2008?
There are different bundles with 5, 10, or 25 CALS. http://www.microsoft.com/windowsserver2008/en/us/pricing.aspx

How many machines can run on a single user MS Windows Server 2008, because we want to move to VMware soon.
Microsoft supports up to 192 VMs on Windows Server 2008, and 384 on Windows Server 2008 R2. Typically numbers will not be anywhere near this, as other system resources will bottleneck. Details can be found here: http://www.microsoft.com/windowsserver2008/en/us/hyperv-faq.aspx#HyperVWindowsServer2008Specific

Is MS Windows Server 2008 VMware built-in?
Microsoft’s virtualization solution, Hyper-V, is built in to Windows Server 2008 and R2.

How would Hyper-V handle the VMware over committing resources, for example, is ESX server only have 8GB RAM but it can assign 16GB RAM to the VMs because it holds the memory and only releases it when it is required. The main reason for Exchange on a ESX box is not a good idea.
Hyper-V does not support over-commit of memory resources. To assign 8gb of RAM to a VM, you must have 8gb available. This improves performance and security.

What happens when a file which has been transferred/shared to a branch using Branch Cache is opened in the main office? Will the branch be informed about this and vice versa?
When clients use branch cache, each file is referenced by a hash. When a client tries to retrieve a file from the central office, it checks the hash of the file, then compares it to what is in the local cache. If the file has changed, then the hash would have changed, and the client would retrieve the updated version. The branch is not informed if the central copy is opened, only if it is changed, through the hash mechanism.

What is the maximum supported DFS server in 2008? In 2003 I think it is less than 70GB and that was not enough for me.
The File Replication Service in Windows Server 2003 had trouble with replication when data sizes got too big. Windows Server 2008 uses DFS-R (Distributed File System Replication) for replication – this uses an algorithm call Remote Differential Compression, which compresses files, and replicates only changes. This makes replication more efficient, an able to support large volumes of data. The limits that existed in 2003 for data size are either removed, or raised greatly.

What is the standard vs. reduced footprint for Windows 2008?
Processor requirements for Server Core and full Windows Server 2008 are the same. Minimum memory recommendations of 512mb are also the same. While the system requirements on Microsoft.com don’t list separate requirements for Server Core, it typically requires less disk space than a full installation. Additionally, Server Core has fewer roles to install (only 9), fewer services running, and has no GUI.

Are there any plans to integrate snapshot technology within Hyper-V?
Hyper-V already supports snapshots at two levels. First, it supports snapshots of the Virtual Machine itself, through use of memory copies and differential disks. The other snapshot capability is a snapshot backup, performed by the host Hyper-V system, using Volume Shadowcopy Services to back up the running VMs.

When will Hyper-V R2 be released?
Windows Server 2008 R2 and Hyper-V R2 released to manufacturing on July 22nd. General Availability will be in October. Volume license customers should have access to the code on August 19th. More details are available here: http://blogs.technet.com/windowsserver/archive/2009/07/22/when-to-expect-windows-server-2008-r2-rtm.aspx

Can everRun protect a workload that is physical on one side and virtual on the other?
everRun does not install INTO a Windows system, so it isn’t able to protect a ‘physical’ system in this sense. Many of our customers choose to keep some of their applications isolated to a physical server with no other applications or VMs on that host while protecting them with everRun. This is done by creating a single Windows environment within the everRun environment. Although the capability is there to create multiple, a single is the desired approach.

How does everRun handle data stored on NAS?
everRun can use any product data that resides on any type of storage. everRun sees the storage repository as a disk volume and can mirror between any two.

How many licenses for the operating system do I need for this solution? Do I need two licenses for the application (i.e. Exchange) as well?
Typically two licenses of Windows are required, however the Enterprise edition provides benefits when running in virtual environments. Please check with Microsoft on this and with your application vendors as all vendors have different licensing terms for redundant/high availability systems.

How well does everRun work with dissimilar hardware (i.e. at the DR site using older servers)?
There are some requirements for similar server components. If two supported servers are utilized and one happens to have a slower processor, the application may run at the slower speed, depending on the level of protection chosen within everRun.

Does everRun replicate all server data including application data like SQL databases?
Yes. The entire operating environment and all disks, including the OS, application, and application data are mirrored.

Is everRun effective for small companies? For example, an Exchange environment for less than 200 users?
Absolutely. Many of our customers are smaller to mid-sized businesses who require an availability solution that is simple, effective, and doesn’t require SAN storage or dedicated IT staff to manage.

Does everRun support MS Small Business Server?
Yes. Our everRun solution will work with any version of Windows Server, 64-bit or 32-bit. We work for small scale solutions all the way up to enterprises.

Will everRun support Exchange 2010 DAG location geographically?
We are still researching Exchange 2010 capabilities and how they can best be supported by everRun. At this time we are not yet clear on how DAG will or can be supported.

How are system upgrades handled in the everRun environment?
A single upgrade is performed on the single exposed Windows environment. Both of the redundant systems will be updated automatically by everRun. everRun also offers mechanisms to reduce the risk and associated downtime of system upgrades.

How does the actual SQL server app run in the everRun environment?
Exactly the same as it does in a non-everRun environment. everRun sits below the Windows environment therefore there are no application changes required.

The everRun software sounds great, but it requires two physical servers. Any hope of moving forward to do the same work within a VMware or Hyper-V environment?
Today everRun supports virtualized environments running on Citrix XenServer. We announced a joint development agreement with Microsoft back in early 2009 to provide everRun Fault Tolerance within a future version of Windows/Hyper-V.

How is everRun migrated with Windows 2008 hypervisor?
everRun will support a future Windows/Hyper-V release as part of the joint development effort between Microsoft and Marathon.

What system resources are used by everRun?
A small (varies a bit by the application that is running) bit of CPU and memory overhead is consumed by everRun.
 

If you’ve been thinking about upgrading to Windows Server 2008, be sure to attend our July 30th webinar featuring guest speaker David Hanna, Information Architect at Microsoft. David will review the new Web tools, virtualization technologies, security enhancements, and management utilities available in Windows Server 2008. You’ll also have a chance to ask David any specific questions you have about Windows Server 2008 during the live Q&A portion of the webcast.

In preparation for the webinar, we asked David to answer a few of the common questions that we have been hearing from our customers in recent months.

Q: One of the biggest concerns we hear from our customers and partners is that in this current economy, IT departments are being asked to do a lot more with less people. How can Windows Server 2008 help with this issue?

Across all of my customers, everyone is talking about cutting costs, and getting more out of their current investments. When we start digging into the features of Windows Server 2008, customers are finding tremendous opportunity to optimize their environments. A few of the major areas of cost savings I’m seeing are:

• Reduced deployment time and costs with Windows Deployment Services
• Reduced management cost and effort with PowerShell and Server Manager
• Hardware and Workload Consolidation with Hyper-V
• Licensing consolidation with Enterprise and Datacenter models for virtual environments.

Q: What about the challenge of managing remote and branch office locations?

Branch offices have consistently been a challenge to manage, primarily due to lack of on-site staff. Windows Server 2008 brings some major new components to the picture that will greatly ease branch office management. These features include the Read-Only Domain controller, which makes the remote DC secure, and replaceable, Distributed File System, Windows Remote Management, Server Core (lower surface attack area), and improved Terminal Services for application delivery.

Q: A lot of our customers work in “always-on” industries like manufacturing, healthcare and broadcast media, where server downtime can be very disruptive to their business. How does Windows Server 2008 support these demanding environments?

Windows Server has always addressed high availability with Clustering Services. Windows Server 2008 has brought some huge enhancements to the Cluster Service that will reduce the complexity of clustering, while increasing availability. Failover Clustering in Server 2008 has a new validation wizard that will validate hardware and software configurations, resulting in easier, more reliable cluster deployments. The reliance on a quorum drive has also been removed, so there is no longer a single point of failure in the cluster. Also, Failover Clustering has been enhanced to support multi-site clusters to support organizations that need site-to-site failover. And, as always, when organizations need to take availability to the next level, Microsoft continues to work with partners like Marathon to extend the native capabilities of Windows Server.

***********************************************************************************************

During the webinar, Michael Bilancieri, Sr. Director of Products for Marathon, will discuss how to extend the high availability features of Windows Server 2008 to fault tolerant protection with Marathon’s everRun software and how organizations can now confidently migrate mission critical applications from Unix or proprietary platforms to realize big cost savings.

Registrations for this webinar are limited and we are expecting a large turnout, so be sure to save your spot by registering today.

We received over a hundred questions during the Q & A session of our April 29th webinar where we covered our new everRun technology. I've posted the questions and responses here for everyone's benefit.

Q: Level 3 will support 2 Socket Processors?
A: A level-3 protected workload must be single-CPU configurations. With the ability to now support multiple workloads with everRun 2G, multiple single-CPU workloads can be protected at level-3 on the same pair of servers, allowing utilization of multi-processor systems.

Q: How does everRun handle custom application? From the answer, it only has to be on 1 machine then everRun will handle the redundancy for the second machine?
A: everRun runs below the operating system which enables it to support any Windows application without any customization. everRun automatically mirrors the entire workload to a second system and maintains redundancy in a synchronous manner.

Q: For Level 2 and 3 protection, does the application (Exchange, SQL, etc) have to be installed on both servers (in your example, everRun1 and everRun2)?
A: everRun automatically mirrors the entire operating environment, including the OS, application, and data, to a second system. This eliminates the need to manually install and maintain the OS and application a second time.
 

Q: Please define a "workload"
A: A workload is a complete and independent operating environment, consisting of its own OS, applications, etc.
 

Q: What is difference from the last generation product? Also, is 2G just an upgrade or is it a completely different product than HA and FT?
A: everRun 2G is the next generation product following everRun HA and FT yet it is not an upgrade to HA and FT. It is a separate product that requires a new installation. everRun 2G is designed on a completely new base platform, utilizing Xen rather than Windows as is used by HA & FT. This design provides improved flexibility, scalability, and ease of use and management. One of the major advantages of this new design is the ability to create and protect multiple workloads on the same pair of physical servers.
 

Q: What about copy protected applications that use hardware serial numbers for activation?
A: For applications that use hardware-based license keys, such as a dongle, please contact Marathon to discuss the specific details of your application.
 

Q: Do you offer support? online? 24/7?
A: everRun solutions include 1st-year maintenance which includes 24/7 technical support (online, email, phone) as well as product updates.
 

Q: Can the physical server / host server be considered as a workload?
A: We don’t refer to the physical host as a workload. However additional workloads can be created on the physical hosts. These workloads do not need to be protected/cloned by everRun. You have the choice of protecting them or not.
 

Q: Is it also possible to use NAS technology instead of SAN storage?
A: Certainly. Any type of storage can be used on either host, and one huge advantage of everRun is that these do not need to be the same. One host can have NAS while the other host has locally-attached storage.
 

Q: Can everRun be used to keep 1 host running for the end-users while the application on the other host is being upgraded?
A: Yes, one side of the protected environment can be taken offline for upgrades and testing while the other side remains online servicing clients.
 

Q: What are the bandwidth requirements when I run 2 hosts over a WAN?
A: 150mb connection with a maximum latency of 10ms roundtrip between the two hosts.
 

Q: Can everRun protect against OS failures?
A: With level-2 protection, an OS failure will result in a restart of the application environment. With level-3 protection, the result will vary depending on the cause of the failure. If the application causes a bugcheck within the OS, this will happen on both systems and the OS will restart. If the failure is caused by faulty hardware the OS and application will continue to run on the paired system without interruption.
 

Q: What happens if WAN-line fails?
A: Communication failures between the two hosts will result in one of the systems taking itself offline to prevent a split-brain scenario. everRun utilizes a quorum service to negotiate which system is to remain online and which is not. When the failure is rectified, everRun will automatically synchronize the systems to regain full redundancy.
 

Q: How many hosts can be supported in the config?
A: Currently we have tested up to 4 hosts in a single pool.
 

Q: Can these network adapters be bonded at the OS level? Meaning I get a level of local redundancy as well before failing over traffic to another system.
A: Yes
 

Q: What host OS does this solution run on?
A: Citrix XenServer
 

Q: How does this product compete or work with technologies like VMware or Hyper-V? esp Hyper-V R2.
A: Marathon has recently announced a joint development effort with Microsoft to provide fault tolerance within a future release of Hyper-V. VMware is not currently supported by everRun.
 

Q: In a FT configuration, what is the system resource overhead? is this on a system wide, or per workload (i.e. VM and app) which are configured for FT?
A:Overhead varies depending on the hardware and the actual applications. We have tested various applications including SQL Server, Exchange, and XenApp and found CPU overhead to be anywhere between 3% to 14% over a non-protected workload. This information is available on the Marathon website under the Solutions section for Exchange and XenApp. SQL Server will be available soon. We are in the process of quantifying overhead with level-3.
 

Q: At what interval do you monitor the standby components? And is this different than the online/active components?
A: everRun is constantly monitoring all active and standby components to ensure any failure is identified so that it can be rectified. This is one of the major differences in the everRun architecture. Typical availability systems don’t monitor the health of the standby system and components. If one of these should fail without notification, a failure on the active system will result in the system not being able to recover.
 

Q: Can you use hardware capabilities? Such as replication?
A: everRun offers two different storage protection options; everRun mirrored storage in which everRun mirrors all data between the two hosts for full fault tolerance at the storage level, and also supports a shared-LUN model wherein there is just a single copy of the data which both systems can access. When a shared-LUN model is used everRun does not protect the data and assumes that the storage subsystem has been configured to cover this.
 

Q: Does it sync memory pages and system registers, etc. - so the OS/App is running on both nodes in lock step?
A:Yes
 

Q: What are levels of protection? What criteria defines each level? Level 1 requires shared storage? Level 2 - mirroring/replication? Level 3 - FT?? Please clarify.
A: Check out The Three Levels of Availability Whitepaper, as well as a breakdown here:

• Level-1 protection provides basic failover of workloads when a host fails. There is no redundancy maintained so if resources are not available on other hosts to restart the workload, it will not be restarted. Level-1 does require shared-storage/shared-LUN.
• Level-2 provides fault tolerance at the storage, data, and network levels, meaning that a failure in those areas will not impact the application. A complete system failure will result in the application being restarted on the secondary host. The entire workload is mirrored to the secondary host with memory, CPU, storage, and networks allocated to ensure it can restart if necessary. Level-2 supports separate storage on each host or a single shared-storage configuration
• Level-3 provides full system-level fault tolerance, meaning that the application will remain running without interruption during component and even complete system failures. Level-3 also supports separate storage as well as a shared-storage configuration.

Q: Is there a limitation on the number of processors for the VM or Physical Processors? I heard that ESX has a limit of one VM for their proposed Virtual Cluster in VM4.x
A: Level-2 component –level fault tolerance can support workloads up to 8 vCPU’s. Level-3 system-level fault tolerance supports 1 vCPU.
 

Q: If we have an application that is licensed per CPU socket, how will that be licensed since it sounds like it will be running on two separate servers now?
A: Licensing requirements vary by application vendor. Please contact your Marathon reseller or Marathon directly to discuss your specific applications.
 

Q: With the newer version of Marathon, is there network improvements where the software can be used with a smaller network bandwidth?
A: everRun 2G has the same latency bandwidth requirements as everRun HA and everRun FT.
 

Q: If we have an application that uses 4 Gbytes RAM and normally use Windows Server 2003 Sandard Edition. If we have 3 workloads (total of 12 Gbytes), the servers must have (for example) Windows Server 2003 Enterprise Edition.
A: Each workload has its own instance of Windows OS and is limited by the amount of RAM within each specific workload, not the amount of RAM on the physical host. Enterprise edition offers some licensing concessions when used in this environment which may help to save on Windows licensing costs.
 

Q: When will the software be released?
A: May 18, 2009
 

Q: What is the maximum number of workloads that can be run?
A: There is no hard limit configured into everRun. The number of workloads will be dependent on the hardware and the applications being run.
 

Q: Do each of our workstations need to have Windows 2003 Enterprise installed or can continue to use Windows 2003 Standard Edition?
A: everRun does not require Windows Enterprise edition. Windows Standard edition is support as well.
 

Q: Does this work with VMs with multiple processors?
A: Yes, depending on the level of protection desired.
 

Q: What are the specifications in terms of bandwidth and latency for level 3 ft? can this go over the WAN? Site to site?
A: Site-to-site is what Marathon refers to as SplitSite. This capability is available for level-2 and level-3 protection. Bandwidth required is 150mb with latency of 10ms or less roundtrip.
 

Q: What happens if a protected VM bluescreens or stops functioning?
A: This depends on the level of protection and the cause of the bluescreen. With level-2 protection, the application will be restarted. With level-3, if the bluescreen is caused by a software issue within the OS or application, then both sides of the protected environment will bluescreen and the system will restart. If the bluescreen is caused by a hardware issue (faulty memory, etc.) the second side will not be affected.
 

Q: What version of XenServer does this work with? The newest free version, or essentials only? 5.1 u3? 5.5?
A: This latest release of everRun availability on May 18 will support XenServer 5.0 Update 3. It will fully support all versions including Free and the Essentials packs.
 

Q: Did the db server get affected by exchange server failure demo?
A: No. The database server is a completely separate workload and was not affected by the failures that I invoked on the Exchange server. Throughout the entire demo as failures were introduced, both the Exchange server and database server remained active and available, as was shown by the use of LoadSIM.
 

Q: What OS does it support?
A: Windows Server 2003 Standard and Enterprise, 32-bit and 64-bit , as well as Windows Server 2008 64-bit.
 

Q: Is there limits to rolling upgrade method?
A: Please contact Marathon to provide further details on your question so we can be sure provide the correct answer. Contact us via email or call 888-682-1142.
 

Q: What is the distance limit for latency support between hosts?
A: Distance is a factor of latency of the specific network being utilized. We have customers running at distances of over 100 miles between the two everRun systems.
 

Q: Are you considering a version that will replace the Microsoft Windows OS? This would remove a level of security support and target only Marathon for security.
A: No. Marathon does not build operating systems.
 

Q: Is there a performance graph during failures?
A: Results of our performance tests can be found on our website under the Solutions section.

Q: Do you have rolling upgrade support?
A: Yes
 

Q: Is VMWare supported?
A: No
 

Q: How much hardware similarities must exist between hosts in pool?
A: Same make and family processor
 

Q: Do u install everRun inside XenServer? Or is it a seperate server?
A: everRun installs on top of XenServer.
 

Q: Does it support Linux VMs?
A: Level-1 protection supports Linux. Level-2 and level-3 do not at this time.
 

Q: Does level 3 protection require shared storage?
A: No. Both level-2 and level-3 can mirror data between hosts using similar or dissimilar storage, as well as supportinga shared-storage/shared-LUN configuration wherein everRun does not mirror the data.
 

Q: When will Lunix be supported?
A: A data for Linux support has not been defined.
 

Q: Support on a mac environment with virtualization?
A: No
 

Q: If you lose Adapter 0 in everRun1 and Disk 0 in everRun2 would things still run?
A: Yes. All workloads would continue to run uninterrupted as if nothing has happened. everRun masks the failures from the application.
 

Q: If you set up a server as a level3 and realize you need additional processors can you roll back to a level2 protection?
A: Yes, you can easily change levels of protect via the protection wizard.
 

Q: Will level 2 mirror data as well so if you are running on host1 and a failover occurs and you come up on host2 you will have essentially the same data as when host1 went down?
A: Yes
 

Q: For level 2 for Exchange will Mx-records be an issue? Same question for level 3
A: No. The all everRun protected workloads have a single IP and MAC address, regardless of which host the application workload may be active on. This eliminates the need to make DNS or MX-record changes, allowing immediate redirection of network I/O to the second host without interruption.
 

Q: Does 2G support Windows Server 2000, 2000 Advanced Server?
A: No
 

Q: What do you consider a Virtual Machine? You use that terminology, is that a function of your software or other virtualization products such as VMWare
A: A virtual machine, or workload, or guest refer to the same thing. It is a complete and independent operating environment. In everRun 2G, everRun utilizes XenServer to create and manage these while everRun provides fault tolerant protection to them.
 

Q: What performance enhancement/degradation has been seen in testing with 2G over no FT/HA solution and also over previous releases?
A: Initial tests have shown similar and even improved performance over everRun HA and FT.
 

When planning your VM workloads, you should be aware of what level of availability each server will need. By splitting the amount of users across multiple VM’s you can provide a level of availability to each set of users based upon your SLA with each business unit in your company. Looking back to the availability pyramid you can choose which level of availability for each mailbox server is needed. For example if you have an executive group that needs to be up with a 24/7 uptime and only limited downtime then level 3 should be your selection on a separate mailbox server. If all of your business units require the same level of availability and have the same SLA in place then you will split your mailbox servers according to usage. Using the chart from section one we can split the users based upon the type of user. For example if you have 1,000 heavy users we would assign 2 vCPU’s to the virtual machine. Always follow Microsoft best practices when deploying the amount of users per core or vCPU.

If we look at Figure 1 we can see that that we have 4 active VM’s spread across two servers with 2 vCPU’s assigned to each. Looking at the example chart above and using figure one we can see that this design example would support 4,000 “Heavy users”. We achieve this by allowing our storage groups on each mailbox VM to support 1,000 “Heavy” users.

Let’s take a look at a basic design with 3 separate types of users spread across 4 servers. We have an executive mailbox store, a mid-management store, and a general user store. In looking over what each teams HA requirement is we have come to the following, the executive team needs 24/7 up time with no downtime except for a maintenance window once a month. The mid-management team can handle some downtime, but only a few minutes each week. The general users have no HA requirement they can be down for an hour a week if needed. So how do we decided what level of availability we would like to use, it’s easy we simply look at the application availability pyramid and we put the appropriate mailbox store at each level:

By using this simple plan you can simplify you’re HA strategy for Exchange. By distributing the mailbox stores across multiple servers on the same hardware you can save rack space as well as provide individual levels of availability based upon different business unit needs.

We had a lot of great questions during the Q & A session of our February webinar with Stephanie Balaouras of Forrester Research. We’ve posted the questions and responses here on our blog for everyone’s benefit.

Questions from the webinar:

Q: In the architecture two "mirrored" VMs are shown which are connected. Does that mean that you have to install 2 application VM servers or do you have to install just one and Marathon makes the second?
A: You only need to create one application VM. After this is created, you can use everRun to protect that application. As part of the protection process, everRun creates a “cloned” instance of the application on the second host. The instance is completely identical to the original, with the same identity, MAC address, resources, etc. It is this redundancy created by everRun that protects the applications.

Q: In the Marathon license there is HA and FT. In which are the levels 1-2-3 available?
A: Levels 1, 2, and 3 are available in a single solution called everRun VM and any level of protection can be enabled on a VM. everRun VM level 3 protection will be available in Q2.

Q: The licensing question you just answered seems different from what you used previously. You previously only had to license the VMs OS in a fully protected system. Please explain.
A: Microsoft licensing requires a valid Windows license for each side of the protected VM. Using Enterprise Edition can reduce the number of licenses required. Please refer to Microsoft licensing terms for specific details for your environment.

Q: How does the software communicate between disparate storage NAS to DAS, SATA to Fibre Channel?
A: everRun does not limit you to needing matching storage requirements on multiple hosts. Communication between hosts is done through Availability Links (A-Links), which are private networks between each host. everRun handles the mirroring at the host level, passing I/O through XenServer to write to the disks. The type of disk or connection is not relevant.

Q: How does this compare to VMWare's SRM & VDM products?
A: VMware SRM provides a mechanism to restart a VM on an alternate host, however it relies on other storage mirroring solutions (often within the storage system) to perform the mirroring. SRM does not move data or provide a comprehensive HA or FT solution.

Q: Is the product host based or a fabric based solution?
A: everRun VM is a host based solution, with a minimum of 2 hosts required.

Q: Do you need to keep a warm copy of the applications at the DR site?
A: During the protection process, everRun takes the chosen VM and clones it to the designate secondary host. This creates a complete and identical instance on the secondary host. everRun maintains these two synchronously so that they are always identical. everRun’s unique architecture exposes these two mirrored instances as a single entity; there is no need to install, manage, or update both sides, only the one single instance of the OS/application. Should the entire ‘primary’ host fail, the ‘secondary’ host will immediately start the cloned version. It comes up with the same IP address, hostname, and MAC address of the primary so that there are no client-side, DNS, Active Directory, or other infrastructure changes required.

Q: Is the DATA synchronous like SRDF or near synchronous?
A: everRun performs synchronous mirroring of the entire Windows environment, including the OS, application, and data.

Q: How does this compare to products like RecoverPoint/Replistore, InMage, Neverfail, Falconstor etc?
A: These products are disaster recovery products intended for long-distant asynchronous data replication and failover. everRun availability solutions provide true availability in a comprehensive and automated manner. Marathon also offers DR solutions for long-distant protection. Disaster recovery and availability are mutually exclusive in most cases and should generally be considered separately. They are complimentary more than competing solutions.

Q: What is the software support plan? What are the recurring costs for your product year to year?
A: We offer a Premier support plan or a Basic support plan. The only recurring cost year to year is the cost of support.

Q: What are the operating system requirements, how many copies of the OS do you need?
A: Each Windows environment is mirrored to a secondary host, requiring a second Windows license. Using Enterprise Edition of Windows allows for fewer licensed copies. Please refer to your Windows licensing terms for specific requirements.

Q: Regarding the 10ms sync time, what happens if that time increases to say 20ms due to network traffic?
A: If the latency increases beyond our requirement the paired systems may assume that one system is down and redundancy may be lost. In a properly configured environment the application should remain running while the secondary system is no longer maintained in a redundant fashion. Once the latency returns to within spec, the systems will re-sync automatically and return to a fully redundant state. Typically the application is not impacted.

Q: What are the bandwidth requirements?
A: Best practices state 155MB link between the two hosts. For local systems a simple crossover cable between the two systems is sufficient. When separating the systems the 155MB requirement becomes more relevant. This number can vary depending on the applications being protected and the amount of data being managed.

Q: Do you have instances of numerous geo-available solutions with specific applications?
A: Here are two examples:
MAN AG success story with everRun SplitSite
Chester County, PA success story with SplitSite

Q: Is windows Server 2008 VM supported? If not, why?
A: Windows Server 2008 64-bit will be supported in Q2 of this year.

We had a lot of great questions during the Q & A session of our January webinar with one of our customers. We’ve posted the questions and responses here on our blog for everyone’s benefit.

Questions for The Sullivan Group:

Q: Which everRun product are they running? everRun HA or FT?
A: everRun VM

Q: How did you migrate your VMware VMs to XenServer?
A: We used a V2V software migration tool from Visioncore that worked really well.

Q: What was the procedure when bringing back up one of the servers when the RAID card failed. How easy was it?
A: It couldn’t have been easier. Once we repaired the failed component, everRun identified it and put it back into use. everRun used a mirror copy to bring the two systems back in complete synchronization. This all happened without our intervention and without impacting our users.

Q: Was a short implementation time a demand from The Sullivan Group, and what was the expectations before the implementation?
A: Short implementation time wasn’t a hard requirement. We expected the implementation to take a couple of weeks and were pleasantly surprised when we had it all up and running in a little less than a week.

Questions for Marathon:

Q: Is there a special license for SQL? Or any other special considerations?
A: Special licensing for the applications you protect is not required. You should refer to the SQL license agreement or the agreement for the application on the VM that you are protecting. With everRun, only one instance of the application is running at any one time.

Q: Is this active active or active passive?
A: We refer to it as ‘active/ready’. The secondary VM is in a paused state, however disk and network I/O are being processed. This allows everRun to deliver fault tolerance at the component level, while immediately starting the paused VM fully in the event of a full host failure on the primary side.

Q: Do you have to install everRun prior to your application, so if I already have an application installed would I need to rebuild the production server? IF so does this change the install time and impact?
A: Assuming you have a VM set up on a host, the application can be installed before or after the VM is protected with everRun. The protection process does require the VM to be shutdown prior to beginning the protect process, however the process takes about 2 minutes to complete after which time the VM can be restarted.

Q: How does everRun handle Software or OS hangs?
A: everRun does not monitor applications.

Q: In your opinion what is the strongest difference between this and MS Clustering?
A: MS Clustering can be a nice fit, especially with applications such as SQL Server. One of the requirements for MSCS is shared storage, or a SAN. This requirement can push the cost out of reach for many small and midsized businesses. everRun does not require shared storage and can utilize any type of storage the customer may have or intend to purchase. In addition, everRun provides fault tolerance and not just failover restart. This helps to minimize interruptions typically caused by failed devices.

Q: Does everRun VM support Windows x64 architecture on VM?
A: Yes, everRun and XenServer support 64-bit hardware and software.

Q: Can VM run Windows 2008 x64? Or Windows 2003 x64?
A: Citrix XenServer supports VMs running Windows 2008 64-bit and Windows 2003 64-bit. Currently everRun VM can protect VM’s running Windows Server 2003, 32-bit and 64-bit. Our next release planned for calendar Q2 09 will support Windows Server 2008 32-bit and 64-bit VM’s.

Q: How much overhead do you have when you protect a VM?
A: When protecting a VM you are able to define how much of a particular resource is to be utilized and reserved. This helps to reduce the amount of resources required for protecting VM’s. Performance overhead can vary depending on if it is I/O heavy, CPU heavy, what the application is, etc. Typically however performance overhead is not impactful.

Q: Is everRun tied to a VM on a particular physical XenServer, what would happen if you used XenServer technology to move to another physical server?
A: Once a VM is protected with everRun, it is hard-configured to two physical hosts. everRun allows online migration of the active VM between these two hosts without interruption. To move one or both VM’s in the protected pair to a different host would require it to be unprotected, migrated if necessary, and protected again with the new host.

Q: Please speak about XenServer integration, process for failover to DR site?
A: everRun has a tight integration with XenServer. everRun is installed on top of XenServer and is completely compatible and able to protect Windows VMs created in XenCenter. During the protection process, everRun takes the chosen VM and clones it to the designate secondary host. This creates a complete and identical VM on the secondary host. everRun maintains these two VM synchronously so that they are always identical. everRun’s unique architecture exposes these two mirrored VM’s as a single VM; there is no need to install, manage, or update both sides, only the one single instance of the OS/application. Should the entire ‘primary’ host fail, the ‘secondary’ host will immediately start the cloned VM. It comes up with the same IP address, hostname, and MAC address of the primary so that there are no client-side, DNS, Active Directory, or other infrastructure changes required.

Q: Will everRun run on x64?
A: Yes, it requires 64-bit servers.

Q: I assume the servers must match i.e. memory, HD space and memory as well as other array controllers and type of arrays?
A: The only requirement for similarities within the servers is same family of processors. everRun can mirror storage between dissimilar storage types and vendors, allowing lower-cost storage to be deployed on the ‘secondary’ host.

Q: Is everRun for virtual servers XenServer specific, or does it work with Hyper-V, Virtual Iron, etc.?
A: Today everRun is developed for XenServer. In January we announced a development and marketing agreement with Microsoft, we will be developing an everRun product for Hyper-V as well.

Q: What if the server is up but a single app on the server fails? Also, how do you detect the app failed?
A: everRun does not monitor applications. However if by ‘single app’ you mean a single VM, everRun does protect at the individual VM level. If a VM fails yet the host and other VM’s remain alive, everRun can restart the VM on the secondary host.

Q: Do you have to purchase redundant licenses for the applications that you have replication as Virtual Machines across two physical servers? For example, do you have to purchase double the Exchange licenses to do it or just the licenses as if you had a single server?
A: You would need to refer to the license agreement for each application. With everRun, the application is running as a single instance and many vendors don’t require two licenses, but this varies between vendors.

Q: Can you have full fault tolerance on XenApp servers between 2 datacenters, where users would not be disconnected from their session if a failover occurred?
A: everRun can certainly protect XenApp as it can protect any Windows application. A number of customers are using everRun to protect XenApp today. The ability to separate between data centers (there are latency requirements due the synchronous nature of everRun) will be available in Q2. To prevent session disconnects will require Level 3 protection, or full System-Level Fault Tolerance, which will also be available for everRun VM in Q2.

Q: Can the VM servers be in different data centers across a WAN behind firewalls?
A: The ability to separate servers geographically will be available in Q2.

Q: Are there general guidelines on the number of VM's that can be protected between two host machines? I'm thinking of SQL Server systems hosting highly transactional databases.
A: The answer to this is dependent on the applications running within the VM’s, hardware, and activity within them, so providing a set number of VM’s would not be practical. Please contact Marathon if you would like to discuss your environment to better understand what VM limits may be suitable.

Q: How can you use the USB interface, for example when software requires a dongle?
A: everRun does not redirect the USB interface to a protected VM.

For healthcare organizations and their IT departments, almost everything is mission critical, from patient information to registration systems and records management. Information needs to be readily available and data has to protected at all times to avoid compliance risk or calamitous consequences.

From what we’ve seen, the interest in virtualization for high availability and disaster recovery is driven by two key factors: cost savings and greater demand for 24x7 availability of health records. Like so many organizations in this tough economy, health care providers are under tremendous pressure to deliver the same quality services at lower cost. Using server virtualization for server consolidation can help. And the VMotion and XenMotion capability in VMware and XenServer respectively can provide these organizations with DR that is significantly easier to deploy and execute. On top of XenServer they can add everRun VM for fault tolerant, high availability protection that is much more affordable and practical than what they have had in the past.

Testament of the increased interest in virtualization from healthcare organizations comes from our own experiences here at Marathon. We’ve seen a positive uptake in healthcare customers who are deploying everRun VM to protect their virtual environments. Currently, about 30% of new customers that are in Marathon’s pipeline for sales are in the healthcare related space. We can only assume that the number of healthcare customers we service will continue to grow as we venture into 2009.

The changes these organizations are making are allowing them to stay ahead of the competition as they increase efficiency, ensure the availability of patient records and most importantly set the standard for inpatient and outpatient care.

Are you part of a healthcare organization that is starting to deploy server virtualization? Is more effective HA and DR a key goal?