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

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

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.

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.

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.

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!

J. Knipper and Company, Inc. , a leader in the healthcare marketing industry recently implmented Marathon's everRun automated availability software for the continued successful management of two specific high-level downtime risks:

• the protection of building systems that regulate their refrigerated pharmaceutical samples. FDA regulations require stringent control of these systems.
• the protection of their MyPharmaSuite™ Software as a Service (SaaS) web applications. Downtime here could result in customer service headaches and frustration.

Founded in 1986, J. Knipper provides healthcare marketing solutions in direct marketing, sampling, compliance, information technology, and sales force productivity. Going beyond its roots in direct marketing and sample distribution, Knipper continues to offer innovative solutions to sales force challenges, including MyPharmaRep.com (online solution for vacant-territory coverage) and MySampleCloset.com (online sample ordering).

The company has invested considerably in its physical and data infrastructure over the years: the company currently has 270,000 square feet of space, with 12,000 of that for refrigerated and 7,500 for controlled substances, along with an advanced Data Center, fully protected for the secure and safe handling of database management and sample supplies. Knipper is one of a handful of companies approved as an AMA DBL (database licensee). With its new infrastructure and SaaS product suite, Knipper needed to find a high availability solution that would deliver the 24x7 reliability required for the safe handling of application hosting, database management, and enterprise services.

“We have several client-facing web applications designed to enable physicians to order products and to provide sales representatives with a means to order samples and access product literature. It’s extremely important that these web applications are available 24x7. Many of the reps and physicians that our products serve are ordering in the middle of the night, early in the morning, at all times of the day,” said Knipper’s web systems engineer Marc Gerardi.

Knipper was using automatic system health checks with third party tools and file sync technology to control these downtime risks. “It was a time consuming manual process of systems recovery requiring dedicated monitoring personnel and rapid group response to mitigate issues when they occurred,” said Tony Quintenz, Knipper’s Director of Network Services. “The overhead associated with mitigating downtime, including the administrative and operating costs, as well as the learning curve and time required to train employees in the process was a significant burden on the entire IT team,” added Mr. Quintenz.

Knipper is now using Marathon’s everRun software, running on standard Dell servers, to guarantee that its critical applications, including the warehouse management system and web applications, would be available and operational at all times with a lower overhead and higher ROI. everRun is used to protect many of Knipper’s enterprise production environments from downtime, including several Dell PowerEdge R900 servers with Microsoft SQL Server. Knipper purchased, installed and configured the everRun software quickly and easily.

“We chose Marathon because they offered the best package overall. everRun offered real-time synchronization which is key for our 24x7 operations, it’s cost-effective and required minimal training for our employees. Another winning factor was the simple implementation; we were set up within a matter of hours, not days,” said Mr. Quintenz.

Since Knipper finished the everRun implementation, its enterprise environments, including its warehouse management system and client facing web applications have maintained the highest level of availability in spite of planned and unplanned events. “It’s a great product, we are now able to maintain our high level of redundancy, reliability and flexibility for our web-based products and enterprise services in the most cost effective and efficient manner,” added Gerardi.

After realizing the disaster recovery and data protection benefits of supporting its critical applications with everRun, Knipper plans to expand its use for additional web applications and other solutions. “As we expand more of our services on the web and offer additional options for customers, we will look to everRun for the continued protection we need.”

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.
 

Jim Welch, Marathon's President and CEO is featured in this week's Worcester Business Journal in the "Shop Talk" column. Here's an excerpt from the interview:

WBJ: How has this crazy economy impacted Marathon Technologies?

Jim Welch: I think, prior to me joining {Marathon}, sales cycles were getting longer and people were being more careful about what they were buying. However, the nice part of our core business is, if you need it, you need it. If you’re putting in an application that has to run and be reliable, you don’t have a choice. It’s part of the infrastructure that keeps your business running. So, from that perspective, we’ve weathered the storm fairly well and I think as you look forward, now that that general IT spending is starting to ease up a little bit, we’re going to see a lift.

WBJ: Who are your customers?

Jim Welch: Typically, our best customers are ones that need their systems to never go down. But if you look at how things are changing over the last couple of years, we see a drive by IT shops to reduce costs by consolidating infrastructure. The way they consolidate is by putting more applications on fewer servers which stacks up their application risk, if you will, so if that one physical hardware fails, not one application fails but now three, five or eight could fail. So, in those environments we’re becoming more important as part of that infrastructure so they can rely on fewer servers.

Be sure to check out the rest of the interview, including the WBJ's interesting photo style on the Worcester Business Journal website.

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.
 

iX Magazin, a leading IT publication based in Germany, recently published an in-depth product comparison review of VMware’s vSphere 4 FT vs. Citrix XenServer with everRun VM in their September 2009 issue. In his article, “Fehlertolerante Systeme” or fault tolerant systems, reviewer Jörg Riether noted everRun’s ease of installation and intuitive setup process. Here’s a couple of additional highlights from the review:

“everRun has a very transparent way of handling the sudden total failure of a node without noticeable interruptions – this is true from the perspective of the administrator and from the viewpoint of the user working on the protected server. The Level 3 protected VM goes on running through each active application without any loss of performance. If the server is switched on again after being disconnected from the mains, everRun re-integrates it immediately and starts synchronization.

One of the fundamental advantages of everRun is demonstrated here: it doesn't require a data memory shared by both hosts. Marathon is able to replicate any virtual hard disks from one Xen host on the other and keep them synchronized. This eliminates the effort required for a SAN with synchronous mirroring and redundant paths as everRun itself includes the technology.”

To read the entire product review article (in English!), you can download the PDF here.

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.

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