• Company
  • Awards
  • Board of Directors
  • Careers
  • Company Background
  • Executive Team
  • Corporate Offices
• Products
  • everRun 2G
  • everRun VM for XenServer
  • everRun DR
  • everRun SplitSite
  • everRun HA & FT
  • everRun Customer Endorsements
  • Product FAQs
  • Exporting everRun Products
• Solutions
  • High Availability Solutions
    • XenApp High Availability
    • Exchange High Availability
    • SQL High Availability
    • SharePoint High Availability
    • BlackBerry High Availability
  • Disaster Recovery Solutions
    • Exchange Disaster Recovery
    • SQL Disaster Recovery
    • SharePoint Disaster Recovery
    • BlackBerry Disaster Recovery
    • Virtual Server Disaster Recovery
  • Industry Solutions
    • Industries Overview
    • Manufacturing
    • Financial Services
    • Media & Broadcast
    • Gaming
    • Healthcare
    • State, Local and Federal Government
• Services & Support
  • everRun One Overview
  • Consulting Services
  • Training Services
  • Assurance Program
  • Customer Portal
  • Requesting Technical Support
  • Technical Community Login
  • everRun Assist Web Support
  • Share Your Success Story
• Partners & Alliances
  • Partners Overview
  • Citrix Alliance
  • Microsoft Alliance
  • Partner Program FAQs
  • Find A Reseller
  • Partner Login
• News & Events
  • Latest News
  • Press Releases
  • In The News
  • Events & Webinars
  • Analyst Opinions
• Resource Center
  • White Papers
  • Webinar Recordings
  • ROI Calculator
  • Collateral
  • Flash Demos
  • Success Stories
  • Product Reviews
  • Exporting everRun Products
• Blog

Next week Craig Resnick, research director and automation expert at ARC Advisory Group will be the guest speaker for our webinar "Best Practices for Preventing Downtime in Automation Systems."  We recently sat down with Craig to discuss some of the recent trends in the manufacturing and automation industries.

Q: What are some of the newer trends that you are seeing in the automation space?

Craig Resnick: A primary trend that we see at ARC is the convergence of automation and IT systems. Nearly every manufacturing company uses a variety of plant automation and enterprise IT systems to manage its operations. Plant floor systems, such as distributed control systems (DCS), programmable automation and logic controllers (PACs/PLCs), and a wide range of plant floor applications provide a wealth of real-time information regarding productivity, efficiency, equipment health, capability, and quality. Business systems, in turn, provide information on raw material costs, product orders and inventories, manufacturing resources, production schedules, etc. This wide range of information often remains isolated in systems such as manufacturing execution systems (MES), laboratory systems, maintenance systems, scheduling systems, enterprise resource planning (ERP) systems, supply chain management (SCM) systems, and customer relationship management (CRM) systems. Decisions based on data from any one of these system will always be less than optimal because, without the corresponding information from the other systems, the information will be incomplete.

To close this gap between automation and IT systems, and to address the trend of the plant floor becoming more IT-centric, ARC has defined a new space, defined as Collaborative Production Systems. These new systems consist of platforms in which the controls layer domains of process, logic, motion, building automation, and power control systems converge with the information layer domains of production management and MES systems. These converged systems enable, for example, the required data and information to be directly tied into applications such as corporate reporting and manufacturing compliance. Collaborative Production Systems will become the industrial blade server that provides full monitoring and control of the enterprise, from the office to the plant floor, sharing that information with the supply chain to, for example, procure materials and resources and purchase or sell power at the optimal times and prices from the smart grid, while providing full financial metrics and KPIs to ERP systems to maximize profitability.

Q: Now that corporate reporting and systems are heavily tied into the “factory floor”, how is that changing the need for system availability and data protection?

Craig Resnick: The need for system availability and data protection continues to expand, driven by a combination of issues ranging from global competition to regulatory requirements. Process safety and critical control are primarily focused on system availability and process uptime. As a specific example, take the Pharmaceutical industry, where data and batch information can never be lost or interrupted. System availability and data protection needs are also forcing E-records regulations to evolve across the globe. In the US, this includes 21 CFR Part 11, as well as the FDA’s Good Manufacturing Practice (GMP) and Process Analytical Technology (PAT) initiatives. In Europe, this includes Annex 11 of the EU GMPs, electronic Signatures Directive 1999/93/EC, and Data Protection Directive 95/46/EC. The European Data Protection Directive requires even more protection on data than the current FDA regulations and extends this requirement to clinical trials patients, as all clinical trials data requires maximum protection to remain compliant with regulations.

Unscheduled downtime is expensive. It often impacts production’s ability to meet its schedule and may cause missed customer commitments. Unplanned downtime, which also includes unexpected stoppages resulting from equipment failure, operator error, or nuisance trips, is the nemesis of all manufacturers. Statistics on the impact of unplanned downtime on plant operations show that it accounts for 2 to 5 percent of production lost in, for example, the petrochemical industry. Unscheduled downtime is also costly in terms of equipment damage, environmental harm, and worker safety. The cost of downtime is reflected in a primary key performance indicator (KPI) used by manufacturers known as Dynamic Overall Equipment Effectiveness (OEE), which helps determine the real-time impact of the performance of any individual process or piece of equipment on the overall efficiency of the plant. Unscheduled downtime is a primary factor that significantly lowers Dynamic OEE, which translates to the manufacturer decreasing both its efficiency and profitability.

Q: What are some of the basic steps that companies can implement to ensure the availability of their systems?

Craig Resnick: The first step that companies can implement to ensure the availability of their systems is to maximize their operator’s effectiveness in the control room, which is essential to minimize the risks of accidents, eliminate unscheduled downtime, and maximize production quality. The global process industry loses $20 billion, or five percent of annual production, due to unscheduled downtime and poor quality. ARC estimates that almost 80 percent of these losses are preventable and 40 percent of those preventable losses are primarily the result of human or operator error. Maximizing operator effectiveness requires automating as many functions as technology will allow, as well as reducing complexity wherever possible. For example there are still many plants where operators monitor the processes and collect data manually or semi-automatically using chart recorders. This process is both tedious and error prone, and does not provide appropriate process insight or instill a sense of ownership among the control room operators.

The Abnormal Situation Management Consortium (ASM) points out that most incidences occur from multiple modes of failure. Preventable human error is a contributing factor to these losses, but is hardly the only cause. Preventing abnormal situations requires a multilayered multi-discipline approach focused on maximizing production throughput, efficiency and quality while minimizing lost production time and preventing damage to assets and endangerment to personnel. This approach requires deploying collaborative production systems designed and implemented to be able to deliver high levels of availability and fault-tolerance expected from any other mission critical industrial system. This typically requires effective data backup mechanisms, redundant controllers for critical applications, plus industrial grade software. Manufacturers are also deploying more fault tolerant server technology to ensure continuous availability of these mission critical applications; the continuous flow of vital products to the market; and the avoidance of the potentially negative financial, social, or environmental impact that operating without high availability fault-tolerant systems might bring.

To learn more about preventing downtime in your automation applications, be sure to attend next week's webinar where Craig will provide expert info on steps for reducing the human error that leads to downtime, how to protect your hardware, storage and networks for complete availability coverage, and how to protect against a complete site failure. You can register here.
 

Marathon’s Sr. Director of Products, Michael Bilancieri, recently answered some questions for Paul Mah of ITBusinessEdge.com regarding disaster recovery planning for small & medium businesses. A few of Michael’s answers are highlighted below. For the complete Q&A with Paul Mah, see the article here.

Mah: Any tips to help SMBs with constrained budgets get management’s approval to implement a DR program?
Bilancieri: This may be the most important part of the process. Without support from the senior management team, any DR plan will be hard to get off the ground. The key takeaway here is to translate the technical language into business terms.

Since DR is not primarily about the technology (it is about the business value), it is important to clearly express what downtime means in terms of revenue loss. By creating a chart, organized by each application, it is easy to clearly articulate how much revenue is lost across each application for a certain amount of time.

Mah: What are the best criteria for determining an optimal disaster recovery plan?
Bilancieri: First, you have to identify what it is you need to accomplish. This includes defining the recovery time objectives (RTO), which is the amount of time applications can be unavailable and recovery point objectives (RPO), which is the amount of data that can be lost when a recovery is required.

Keep in mind that these values will likely vary for each of your different applications. Implementing incorrect or incomplete solutions will result in wasted time and resources. Check with your users and clients to determine their requirements and any service level agreements that must be met.

Mah: Once you determine exactly what your needs, how do you select a plan?
Bilancieri: DO YOUR HOMEWORK! Seriously, there are so many different products that claim to be “DR” solutions, all approaching the problem from different angles, it can be very confusing to determine what actually does the job you are looking for it to perform. As you research different products to implement as part of your DR plan, be sure to ask specifically what their product does (copies just the data, takes data snapshots, captures complete images of the full system, etc.) and don’t be afraid to ask probing questions.

Many vendors make the same claims using the same terms but actually deliver very different results. If you are going to test these solutions in-house, which is recommended, try to do the test under similar conditions as your production environment, with similar system and application loads. Oftentimes, something works well in a test environment [where there is] no real processing happening, [but] fails to function adequately once deployed in the live production environment.

Mah: What would a DR plan look like for a company that may face natural disasters such as hurricanes and flooding?
Bilancieri: Since hurricanes and floods can cause severe damage that can result in long-term outages, it would be wise to implement a solution that protects your systems between locations that could not be affected by the same disaster. Ensure that the backup, or DR, site is planned for a location that can be readily accessible by your users and clients should the primary location be destroyed or otherwise inaccessible.

Marathon has a customer based in Georgia, The Sullivan Group, which implemented a disaster recovery plan just for this reason. The team decided to virtualize its data center with Citrix XenServer and implement Marathon's everRun VM solution to provide redundant virtual machines and synchronized mirroring of the entire system including network, applications and data. The Sullivan Group has a small IT staff but needs to be continuously available for their clients, so they needed a solution that was fully automated and offered simply implementation.

Their first step was to identify what their customers’ needs were - and they decided that they needed continuous protection. Second, the team determined exactly what they could afford, and the ROI they would see from implementing DR software. They already knew that they would constantly face the threat of storms, and that they needed their data to be backed up in a remote location. Finally, they determined exactly what solution their IT staff could support and decided exactly which business applications needed to be fully available.
 

Nick Turnbull, Marathon’s VP of international sales explored the importance of ensuring that hospitals and healthcare providers suitably protect themselves for the possible failure of their IT systems to minimise disruption in a recent article published in HES magazine. An excerpt from the article is below. For more information on this topic, you can also download our recent white paper "Finding a Cure for Downtime: 7 Steps to Reducing Downtime in Healthcare Information Systems."

The management of administrative, financial and clinical aspects of a hospital rely on continuous uptime. Every single minute of downtime can jeopardise compliance, revenue and most importantly the health and wellbeing of patients. Downtime is a risk no hospital or healthcare provider can afford to take.

Hospital equipment and systems are designed for a variety of tasks, some keep track of the administrative issues of a hospital, or look after clinical information systems that concentrate on patient-related and clinical-state related data such as the electronic patient record (EPR) and the monitoring of life support machines, MRI scanners, etc. The ensured access to all IT systems is paramount for the smooth running of a hospital and to ensure quality patient care.

EPRs and the need for centralised patient information have seen regular attention in the media recently. EPR systems have the potential to bring huge benefits to patients and they are being implemented in health systems across the developed world. Storing and sharing health information electronically can help to speed up clinical communication, reduce the number of errors, and assist doctors in diagnosis and treatment. Equally, this kind of electronic data can also have vast potential to improve the quality of healthcare audit and research. However, increasing access to data through ERP systems also brings new risks to the privacy and security of health records, as well as practical aspects that need to be catered for in order to reap the full benefits of such a system without any disadvantages.

The importance of being able to access EPRs becomes apparent when looking at the accident and emergency setting or for example the cancer unit of a specific hospital. It is here that access to a patient’s medical history can become a matter of life and death.

It is clear that nowadays IT sits at the heart of modern hospitals, so it is key to ensure IT systems are available to healthcare professionals 24 hours 7 days a week. This means that hospital management and their IT support needs to be sure that the technology they deploy can monitor the entire system around the clock. So, for the last few years, hospitals and healthcare providers have turned to the latest and greatest technologies to support their systems, minimising the risk of disruptions to operations and ensuring availability.

The right solution needs to be 100% effective, which is only possibly if it monitors and receives data continually 24 hours, 7 days a week, with absolutely no hiccups. If this is not the case all the time, there could be lives at stake. If any unexpected downtime occurs, the ability to access records, the continued running of life support monitors and MRI scanners is at risk. Clearly, hospitals and healthcare providers need to ensure that their systems are adequately protected against any unexpected IT failures.

While undoubtedly many hospitals and healthcare providers are using various different systems, they should not forget that these systems need to be protected. If the servers behind the systems experience downtime, it could cause havoc with patient-facing devices and the EPR system. IT system availability is no longer an ideal – it is a necessity. That is why hospitals and healthcare providers need to be sure that when adopting the newest, ‘safest’ technologies, they also ensure that they come with rock solid availability. Continuous uptime for the healthcare industry is absolutely essential to ensure the success of the business as well as the safety of patients.
 

Keeping your applications “always-on” for users is no easy task, and can be particularly tricky for branch or remote locations where you probably have little or no IT staff to support your efforts. Forrester Research senior analyst Stephanie Balaouras has been studying this trend and has pulled together the top 5 best practices for supporting application availability at remote and branch locations. She presented these during a webinar last month and we've also summarized them below.

TIP #1 – Don't Overlook Remote Location Availability

While this may seem like an obvious point, it’s actually very common for IT departments to overlook their branch and remote locations when it comes to application availability. You can’t neglect these offices for both high availability (HA) and disaster recovery (DR) plans—you need a holistic approach to protect all of your business applications, no matter where they are located. This also means that you need to factor in these systems when planning your IT budget as well.

According to recent Forrester Research data, IT systems at remote and branch office locations account for more than 20% of your total infrastructure. They are critical to your business process and operations. Today, a lot of these locations don’t have HA or DR, and in some cases, they don’t even have basic back-up. Make sure that these offices and locations aren’t forgotten as part of your HA and DR plans.

TIP #2 – Classify Systems by Criticallity

When developing your strategy for operational HA and DR, best practices include performing a business impact analysis. This doesn’t have to be a lengthy process—you just need to map the dependent systems for each business process, and then create a rough estimate the cost of downtime for each. Once you have that information, you can determine availability rates as well as recovery objectives. As part of that process you should also identify the most probable types of downtime. When you put that all together, you can classify systems by criticality, such as mission critical, business critical, business supporting, etc., and you can then determine the availability rates needed for each of those systems.

TIP #3 – Develop Tiers of Service for Availability

Once you understand your range of recovery objectives, it helps to have an IT availability and service continuity catalog. This catalog defines a range of service tiers. Forrester typically sees four levels: mission critical, business critical, business important and business supporting. Each of these tiers has associated recovery objectives, technology pre-requisites and the costs to deliver that service. This catalog helps to simplify your strategy, by allowing you to assign appropriate tier classifications to new systems quickly and easily.

Another benefit of using this method is that it also helps you to limit the number of point products you are using for HA and DR. The more point products you are using, the more you complicate the sequencing and complexity of preventing a failure or recovering from a failure. Keep it simple. Every time you deploy a new application or system, assign a tier from your catalog, put the appropriate protection in place, and then communicate that to the business.

TIP #4 – Measure Availability from the End-User Perspective

Well-written objectives measure both planned and unplanned downtime and also take into account the timing of downtime. For example, you don’t take your systems down for planned maintenance during peak sales periods or at 1pm on a weekday when your traffic is at its highest level. You select times when users will be least affected. Availability isn’t about the individual IT system, infrastructure or component. Technology uptime is important to track but is not a true measure of availability. True availability has to be measured from the end user perspective. If the application or service is not available for use, even if the individual components are functioning, then that means the service is down. When making decisions about HA and DR strategies, you have to look at availability from a people perspective, not a technology perspective.

TIP #5 – Make Availability Part of Every IT Decision

Availability is no longer an optional practice. It’s essential. It’s something you owe to your employees, your customers, your partners and your investors. Application resiliency has to be part of the planning process right from the start—HA and DR should not be an after-thought. Even in remote and branch locations, these applications are critical to the success of the business, so availability of the systems should be included during the planning phases of the project, rather than an add-on after the project is completed.

Last Thursday’s webinar “Application Availability for Remote & Branch Locations” with Forrester analyst Stephanie Balaouras was packed with useful tips and best practices for protecting remote and branch offices from application service disruption. Stephanie has conducted extensive research in this area and shared her Top 5 Best Practices during the webinar. A recording of the webinar is now available in case you missed the live event.

The summary of the webinar Q&A with Stephanie and Michael Bilancieri, Sr. Director of Products for Marathon, is below.

Q: I like the idea of integrating HA and DR plans. How often should those plans be updated?
A: Stephanie Balaouras, Forrester: The ideal scenario is to update your high availability and disaster recovery plans continuously as part of your change management and configuration management. That’s the ideal scenario. They should be integrated into day-to-day operations and your plans should be updated as a part of that. If that’s not feasible, then at least quarterly updates should be made to the plans. One of the hardest parts of DR is that if you don’t keep the plans updated and you’re not testing regularly you’ll have major configuration drift between your sites. When you have a failure or disaster and have to invoke your DR plan is not the time you want to find out just how far your configurations have drifted and that you can’t recover. One solution for this is the combination of virtualization and replication, which can reduce complexity because in most cases you’re actually replicating the configuration changes as they happen.

Q: On your disaster recovery continuum slide (slide #14), can I think of that as a disaster recovery maturity model?
A: Stephanie Balaouras, Forrester: Not really. When I evaluate a company for disaster recovery maturity, I look at two dimensions – process and technology.

On the process side, I look at things such as: Have you run a business impact analysis? What about a risk assessment? Are preventative measures in place? Do you have documented plans, and are they up to date? How often do you test them?

On the technology side, I look at things like the RTO and RPO that you have defined: Are they matched up with the appropriate technology solution? If RTO is less than 2 hours and RPO is zero then I would expect that you are replicating data and doing rapid system restart with virtualization. If I find that you are using tape in that situation, then that’s a problem. I think when it comes to maturity you have to look at process and technology together. Not only should you match up with the right technology, but you might actually leverage more than one technology depending on your needs.

Q: Traditionally, HA & DR at remote locations has not been a priority. Do you see that attitude changing with clients that you talk to?
A: Stephanie Balaouras, Forrester: I do see things changing. I run an annual survey with the Disaster Recovery Journal. One of the questions we ask is: How critical is it to upgrade disaster recovery at your sites? The answer is always either “high” to “extremely critical”. It doesn’t always get addressed the way we want it to, but the recognition is there.

I see three main drivers for this trend. First, availability and disaster recovery are now considered a fiduciary responsibility. It’s no longer an optional practice. It’s essential. It’s something you owe to your employees, your customers, your partners and your investors. Second is the cost of downtime. Companies are much savvier at calculating this cost and aware of the problems they can avoid by not having downtime. When you understand those costs, you can make the right technology investment choices. The final driver I see is the changing business environment. A lot of companies are operating globally on a near 24x7 basis. Like an online retailer for example. We’re operating close to 24x7 and there is no tolerance for downtime anymore. All three of these – fiduciary responsibility, cost of downtime and a 24x7 business environment are moving the needle quite a bit.

Q: In my environment, our IT staff says they have no way to measure if an application is up or not. They can tell us if a server is up, or if a database is up, but not the application. What solutions have you seen that can tackle that issue?
A: Stephanie Balaouras, Forrester: There’s a couple of ways to address that. There are third party application monitoring tools from the large system vendors. They are great for basic monitoring and telling you if your application is up or down, but they don’t tell you about degradation of performance. The other option is that different HA solutions will be able to detect whether the applications is up or down.

Michael Bilancieri, Sr. Director of Products for Marathon, answered your questions about everRun software.

Q: Does everRun have any kind of alerting capabilities for system problems?
A: Yes, everRun has alerts. You can send notifications back to any location. It will tell you that something has failed – it’s not a downed system because everRun kept it going through redundancy, but it alerts you that it needs attention.

Q: Does everRun require that the two servers to be identical?
A: 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: How much of CPU and IO payload will we have by running the everRun software?
A: It varies depending on the applications and systems and where the load may be. The general range is from 5-10%. We have specific application performance documentation for Exchange 2007 and XenApp that you can download from our website.

Q: I understand from your presentation that everRun doesn’t require a SAN, but does it work with SAN?
A: everRun can support a SAN in multiple ways. everRun can support a SAN where you have a single copy of the data. And both servers will connect to the single copy of the data. everRun also supports a SAN where one of the servers is connected to that SAN and the other server has its own storage and we can mirror between that. A lot of our customers are using that option to provide data protection and fault tolerance at the data level. We can use different types of storage on either side.
A great benefit of everRun is that is has an agnostic approach to storage. Pretty much any type of storage will work. iSCSI, fiber, direct attached, etc.

Q: Does Marathon have a strategy for SAP environments?
A: Applications are transparent to everRun. We protect many types of SQL, Oracle and SAP applications. There are some best practices around that and we can offer you assistance with those. everRun is invisible to the application, so there are no configuration and design issues. You design your application the way you need to for your business and then everRun protects it without needing changes.

Q: What versions of Windows Server does everRun support?
A: 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: The requirement for redundant systems is obvious, one local and one remote, but I am concerned with the return of the repaired server back to the primary server role. Has that issue been also automated in your application?

A: Replacing one of the servers in an everRun configuration is quite simple as well. It is required that the everRun software be installed and the server be physically connected to the remaining everRun system. Once connected and configured to see each other as a pair, there is a ‘re-pairing’ process that is initiated via command which starts the process of creating the redundant OS environment on the new system and mirroring all of the storage to the new system. Once the mirroring is complete, the system is once again fully protected.

It’s always interesting at this time of year to take a look back at what was top of mind for our newsletter readers. It’s also a great opportunity for you to discover a key topic that you might have missed the first time around. Here are our top 5 most downloaded articles and white papers of 2009:

1. Configuring High Availability for Windows Server 2008 Environments
2. Optimizing Exchange High Availability - A New Approach
3. Increasing Reliability and Availability in a Virtualized SQL Server Environment
4. Reduce Downtime by 70% - Without Spending a Dime
5. iX Magazine product review: vSphere 4 FT vs. Citrix XenServer with everRun VM
 

If you would like to stay current with latest trends, developments and tools in the world of high availability and disaster reocvery, be sure to sign up for our monthly newsletter by sending an email to mstec@marathontechnologies.com or click on the Resource Center and look for the sign-up box in the right column.

We had some great questions during last week's webinar High Availability Doesn't Have to be Expensive. A recap of the Q&A is below, including the questions that we weren't able to get to because of time constraints. Be sure to check out our library of on-demand webinars, for this webinar, as well as other topics including SQL availability, Windows Server availability, everRun product demos and more.

Q: How is everRun different from replication solutions?
To understand how everRun is different from replication solutions, you need to take a look at the key differences between disaster recovery and high availability. Availability is about preventing outages instead of just recovering from them; about maintaining the user state with minimal interruptions. With disaster recovery (DR) and replication methods, if there is a failure, you lose connectivity for a period of time and then you have to recover your data and system state. Conversely, availability is about reducing and preventing downtime and keeping users online, even through a failure.

everRun 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. Oftentimes, 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: What kind of bandwidth requirement is needed for a two-site solution?
As a general rule of thumb, an OC3 connection is required per application workload being protected. Latency is really more critical than bandwidth and this will vary based on the applications and environment.

Q: How does everRun software compare with EMC’s RepliStor and AutoStart applications?
everRun is different from these products because it provides high availability in an automated way with fault tolerant capabilities to prevent user interruptions when hardware fails. This goes back to prevention rather than recovery.

RepliStor is a DR/replication product. While it does provide a failover/restart capability, as do most DR solutions, it is really best used for failover in the event of a major disaster. There’s usually a substantial amount of downtime and a manual failover process to get the systems back online at the secondary site and to failback once the primary site is back online. For DR, you probably want to be able to specify when your systems fail over. But, you will lose some data because this is an asynchronous solution. For minor outages, you really don’t want this. For example, let’s say the power goes out in your primary location for an hour. It can take even longer than that with DR systems to failover to the secondary DR site. You would have been better off just waiting an hour for the power to come back on and restarting the primary systems. RepliStor is more suited for major disaster scenarios, rather than just minor local or regional failures.

Auto-Start is more of a clustering type of product designed for availability and application restarts. It’s not designed to prevent downtime due to failures, but rather to recover from them.

Q: Can everRun be used for planned downtime?
Planned downtime for patches, upgrades, etc. can sometimes cost as much or more to your company as unplanned downtime. The answer to this question will depend on the type of updates. Some OS upgrades do require that there be a restart for the changes to take effect. For some types of planned maintenance, everRun can eliminate the need for downtime. For the others, one of the main things everRun can do is to reduce the risk of updating a system and not having it come back online. For example, you’ve just overwritten your production system and it worked in a test environment, but now it won’t come up in production. We can reduce that risk greatly, by getting it back online quickly without the need to rebuild the server.

Q: What is the difference between everRun and vMotion and VMware HA?
These are two different products, so we'll start with VMware HA. The HA product is a failover/restart capability. If you lose a host, the system will try to restart the virtual machines on another host on the pool. There’s no real guarantee here though. It’s going to try to find resources when a failure happens, but they might not be there. There are some checks in place to warn when over using resources will impact the recovery plan but there is nothing to prevent this. When there’s a critical RTO though, it’s better to have something that is more assured like what everRun provides. everRun uses mirrored systems, so you always know that you have resources available in the event of a failure. everRun also protects the data – we don’t require a SAN. everRun can mirror data between to two systems or two buildings and it doesn’t have to be the same type of storage on both sides. It can be SAN on one side and NAS on the other. everRun can move the data between locations and keep it tied to the applications to keep your business running, even when there is a failure.

As far as vMotion, that is primarily used for planned downtime. Motion capabilities in general allow virtual machines to be moved or “motioned” while they are running from one host to another host. everRun can provide that capability as well. We call it online migration. If you want to take host offline for planned downtime for upgrades for example, we can do that. Motioning is really for planned downtime. If something fails unexpectedly, vMotion can’t help you there. everRun provides capabilities for both planned and unplanned downtime.

Q: What versions 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: In considering using everRun across two sites, is everRun doing real-time synchronization between the sites?
Yes it is. It’s writing the data on both systems in a synchronous manner, so that data is always complete—system data and applications are secure and exactly mirrored on the secondary server. It protects the entire environment—the operating system, registry, every setting, etc. is completely cloned. You can turn on that system on the other site and not have to rebuild the server. We maintain exact mirror copies of both servers. That goes back to our message about prevention and computing through failures, rather than downtime and recovery.

Q: Does everRun work with SQL 2008 and SharePoint 2010?
everRun sits below Windows. It’s not in the operating environment. We protect the entire environment, so anything in that environment is automatically protected, whether it’s SQL or Exchange or anything else, even custom applications. There is no customization needed for everRun to protect any Windows applications.

Q: What are the storage requirements for everRun?
everRun offers two storage configuration options: mirrored storage and a shared storage model. When using mirrored storage, everRun will synchronously mirror all storage 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: Should everRun be set up on a seperate server?
everRun is typically deployed on two new servers, however an existing server can be utilized, requiring only one additional server.

Q: How is everRun different from the NeverFail product?
Neverfail is an asynchronous DR solution with failover/restart capabilities.
 

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 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.

As companies become 24x7 “always on” operating environments, they are becoming more and more sensitive to application and system downtime. We recently conducted two surveys to take a look at this trend, specifically for Windows Server applications and environments.

Given the 24x7 nature of business today, we weren’t surprised to find that about half of the IT professionals who responded to the survey reported that 50% or more of their Windows Server applications now require “always on” availability. Whether it’s for email and collaboration tools, manufacturing systems, customer operations, financial transactions, or healthcare records, businesses today are becoming more and more dependent on their Windows-based applications.

More than 20% of survey participants reported that 76 -100% of their Windows Server applications require “always on” availability. An additional 28% of respondents stated that 51 - 75% of their Windows Server applications require “always on” availability or continuous uptime.

The surveys also found that that the number of Windows Server applications that require high availability has increased significantly in the past two years. 76% of the respondents reported that downtime to Microsoft SQL Server and Exchange Server caused the most disruption and were the most important applications that required high availability protection. The surveys also revealed that approximately 60% of participants have either already upgraded to Windows Server 2008 or plan to within the next year.

Thanks again to all who participated in these surveys. For more information and results, see our press release.
 

In recent months, Marathon has put together a series of toolkits with materials on reducing downtime and data loss, including toolkits for Citrix XenApp and Microsoft Exchange 2007.

Our latest toolkit is now available, this time for Microsoft SQL Server. Protecting SQL Server from downtime has become even more critical in recent years, as businesses run more of their critical systems, including electronic commerce, online banking, just-in-time manufacturing and streaming media (just to name a few) on SQL.

This toolkit includes materials on SQL Server high availability in both physical and virtual environments.

White paper: 5 Secrets to SQL Server Availability This paper reviews five proven secrets to affordable SQL high availability that will help IT managers implement a SQL Server environment with little or no downtime - and zero data loss.

White paper: The SSWUG.org Increasing Reliability and Availability in a Virtualized SQL Server Environment white paper, authored by Microsoft SQL Server MVP Stephen Wynkoop, provides IT professionals with best practices and considerations for designing and implementing a virtualized SQL environment including:

• Potential pitfalls to avoid when virtualizing SQL Server
• How to increase reliability and availability of a virtualized SQL Server environment
• A SQL Server virtualization case study (Sullivan Group)

On-Demand Webinar: SQL Availability: Protecting your Database and Applications featuring Microsoft SQL Server MVP Stephen Wynkoop, helps IT administrators understand SQL back-up and restore options. Wynkoop also presents his Concentric Rings of Recovery plan, which covers the four levels of preparedness for local, alternate, off-site and remote locations.

Also, be sure to check out some addtional SQL Server resources, including SQL user groups, SQL Server job boards, SQL MVP blogs and Twitter feeds, and other SQL-related info.
 

Congratulations to Richard Potter of Boeing, the winner of a $50 American Express gift card for participating in our September survey on Windows application high availability. To participate in future Marathon surveys, sign up for Marathon's monthly newsletter: http://www.marathontechnologies.com/news.html (see the right-hand column for sign-up.)

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.

When it comes to high availability, taking a “one-size fits all” approach is highly inefficient. I recently spoke with Carryl Roy, editor of Virtual Strategy Magazine to discuss the different levels of availability, why these are important and how to select the right level of protection for each application. We also talked about how to set recovery time objectives and how tiered or selectable availability can optimize protection with less resources and at lower costs. I discuss these topics in the video below, which is featured on the Virtual Strategy website.

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.

Stephanie Balaouras, Principal Analyst at Forrester Research, has an interesting blog post this week on ZDnet about the increasing interest in high availability from her clients. In her article “How Do We Measure High Availability?” she makes several key points:

• As companies become 24X7 “always on” operating environments, they are becoming more and more sensitive to application and system downtime.

• HA is no longer an all or nothing discussion about proprietary fault-tolerant systems or high-end clustering solutions. Today there are lower-cost alternatives that provide the required level of availability at a cost justified by the risk and cost of downtime.

• Developing and agreeing upon SLAs is the toughest part of HA planning, but these KPIs are good starting point toward metrics that matter to the business.

Earlier this year, we spoke with Stephanie about the topic of virtualization and high availability. You can read that Q&A here. For additional info on this topic, you can also download Forrester's recent white paper "X86 Server Virtualization For High Availability And Disaster Recovery."