VMware

by

Understanding VMware DR components allows IT professionals to dramatically reduce spending without compromising recoverability. There are four main components to a VMware disaster recovery (DR) strategy:

Understanding VMware DR Components
  1. Storage
  2. Compute
  3. Network
  4. Replication Software

The products you select for each of these components impact how much that component will cost and has a ripple effect on the other components in terms of cost and choices. The total of these parts impacts the complexity of your DR strategy and the likelihood of a successful recovery.

To learn more about VMware DR, join us for tomorrow’s Whiteboard Wednesday session, “VMware Disaster and Ransomware Recovery—The Three NEW Best Practices,” at 1:00 PM ET / 10:00 AM PT.

Understanding VMware DR Storage

Understanding VMware DR components requires knowing what type of storage will be in place at the DR site. It represents one of the best opportunities to reduce DR costs. To copy data to the remote DR site, customers often use array-based replication, which typically requires another storage system from the same vendor at the DR site. Customers are forced to pay a premium for a rarely used storage system. Furthermore, since most storage vendors have given up on auto-tiering, the customer cannot use lower-cost hard disk drives at the DR site and then move the workloads to flash storage when a disaster occurs.

Reducing the cost of DR storage requires two capabilities. First, the ability to replicate directly from the VMware environment instead of using the array. Second it must support multiple types of media. Replicating directly from the VMware environment instead of using the array provides a much tighter integration into VMware, enabling a complete copy of data at the DR site. It also enables replicating to a commodity server with drives installed instead of a dedicated storage array. The ability to support multiple types of storage media, flash drives, and hard disk drives, for example, enables IT to take advantage of the fact that hard drive capacity is 8X less expensive than the equivalent flash capacity. The storage system must provide the ability to quickly move the most performance-dependent workloads to a flash tier during disaster recovery testing or an actual disaster.

Understanding VMware DR Compute

Understanding VMware DR components requires knowing the compute requirements at the DR site during a disaster. IT must ensure the DR site can support operations during a disaster. IT no longer has the luxury of ordering hardware on demand because supply chain issues continue to plague the industry. Your DR plan can’t be held up because servers are on backorder for three weeks or more. As a result, the server performance at the DR site must match the server performance at production, at least for the workloads that will be recovered at the DR site.

Reducing the cost of DR Compute requires running more virtual machines on less hardware without impacting performance. VMware is too weighed down by all its add-ons and lack of integration between them. IT needs to eliminate as much of the virtualization tax as possible by using a more efficient hypervisor at the DR site. An alternative VMware hypervisor that is 50% more efficient means a 50% reduction in server costs at the DR site.

Understanding VMware DR Networking

Buying a second set of network hardware for the DR site has the same problem as buying a second storage system; it is expensive. An alternative is to use “dumb switches” and software-defined networking (SDN) capabilities. The issue is the SDN software is often so expensive that its costs all but eliminates the savings of buying “dumb switches.” This high cost is especially true with VMware’s NSX. VMware’s SDN software can add $10,000 or more to the cost of each node in the DR site. Lastly, SDN creates another layer, similar to managing a separate physical network layer. Understanding VMware DR components includes knowing the operational implications of each component selected.

What about Replication Software?

As stated above, many VMware DR strategies depend on array-based replication. While it is sometimes included “free” with the array, it also has the added cost of a second storage system from the same vendor. In most cases, array-based replication is “blind” to the fact that VMware is running on top of it and may not capture all the configuration data. It certainly will not capture all the networking configuration information.

Customers may also use a dedicated replication solution that integrates with VMware. While these solutions capture the VMware environment well, they are costly and don’t help reduce DR storage or network costs.

A Holistic Approach to VMware DR

The fact that there are four components to a VMware DR strategy is the problem. IT must purchase each component and manually stitch them together to work. The coordination between all the components, ensuring all the data and configurations are captured, is critical to the strategy’s success.

VergeIO’s IOprotect simplifies and reduces VMware DR costs. It makes understanding VMware DR components easy because it reduces the “components” to one. IOprotect is part of VergeOS, an ultraconverged infrastructure (UCI) that integrates networking, compute, storage, and data protection into a single operating environment. It is one piece of software, not four or five.

Understanding VMware DR Components

With IOprotect, you can replicate your existing three-tier or hyperconverged infrastructure (HCI) to a single VergeOS environment. It seamlessly connects to your VMware environment and captures all the information you need for a successful disaster recovery strategy. You can also consolidate all your DR computing, storage, and networking requirements into as few as two servers plus a few “dumb switches” at your DR site. If you require more capacity or compute resources, add more nodes, but you won’t need to add many nodes because our customers consistently find they can run more workloads on less hardware. VergeOS is more efficient than VMware. They also require less storage capacity thanks to our high-performance global inline deduplication.

Testing your DR strategy is easy with VergeOS. Our Virtual Data Center (VDC) technology allows you to create a space-efficient, isolated clone of your replicated site. You can test and practice your DR skills while protecting your production VMware environment.

A DR Strategy with a Production Future

Understanding VMware DR Components

IOprotect is just the beginning. Using IOprotect for VMware DR extensively tests all VergeOS capabilities while your VMware environment is under license. You will likely reduce your VMware expenses by more than 60% during that time. Then when it is time to renew VMware in production, and you have to deal with the new, more expensive VMware pricing policies, you have an exit strategy, tested and ready for deployment. Now your cost savings increase even more, as does your operational simplicity.

Filed Under: Protection Tagged With: , , ,

by

preparing VMware for minor disasters

IT professionals often plan for major disasters like floods, fires, and hurricanes, impacting their VMware environment, but they also need to spend time preparing VMware for minor disasters. Unlike a major disaster, a minor disaster typically doesn’t require the organization to resume data center operations at a remote disaster recovery (DR) site. Minor disasters include a VMware node failure, storage system failure, a ransomware attack, or an application bug that causes an application outage or data corruption. From the perspective of the IT team, minor disasters are just as painful to work through.

During next week’s Whiteboard Wednesday session, one of our agenda items is preparing for and recovering from minor and major disasters. Our panel of experts will take you through real-world examples of how customers have dealt with these situations.

Users Have No Patience for Minor Disasters

Part of preparing VMware for minor disasters is understanding user expectations. During a major disaster, users tend to be more patient since they can see that the building is underwater, on fire, or shut down for some reason. They also may be dealing with regional issues that are impacting them personally.

During a minor disaster, the IT team does not get the same benefit of user patience. Users are at work or unaware of why they can’t access their data, so they complain quickly and loudly. Even during a ransomware attack, all the lights are on in the data center, so users demand to be up and running. As a result, minor disasters need a particular type of attention. IT needs to restore operations quickly, without much, if any, data loss.

Options for Dealing with Minor VMware Disasters

If a minor disaster occurs, there are typically three available options:

  1. Fail operations at the DR site and treat the minor disaster like a major disaster. They will then fail that application or data set to the remote site.
  2. Resolving the disaster using traditional data protection techniques like backup or snapshots.
  3. Have an on-premises mirror of your entire infrastructure, storage, networking, and compute available for failover.

Treating Minor VMware Disasters as major Disasters

Moving operations to the remote disaster recovery site is the first option when preparing VMware for minor disasters. The remote DR site should have all the components needed to support the application or data set you need to shift to it. IT is treating the minor disaster as if it were major. However, it also creates some additional challenges. First, you must calculate the time it will take to transfer operations and account for any additional outage while the transfer occurs. The chances of data loss are also higher since most organizations don’t update their DR site as frequently as they may protect their primary site.

Second, you must account for enabling your users to connect to the remote site. Unlike a major disaster, some of their applications and data are still available in the core data center. Is the network set up correctly to support this hybrid access?

Third, you need to account for transferring back to the primary site once the problem has been resolved. It will take at least the same time to move an application back into production as it did to move it out. For the most part, this shift was unnecessary since the primary data center was still operational. The data center didn’t have the resources and planning to rapidly recover through a minor VMware disaster.

Treating Minor VMware Disasters as Backup Events

The next option for preparing VMware for minor disasters is to treat it as something the backup process can work through. While all organizations should do backups as frequently as possible, the reality is that organizations only perform backups once daily. The lack of frequency often stems from backup software or hardware limitations. Some organizations may perform two or three backups daily, but there are usually hours of gaps between protection events. Even backups every three to four hours will result in too much data loss for a minor VMware disaster.

Some organizations will supplement the backup process with storage system snapshots. These snapshots enable more granular data protection. Still, most organizations don’t execute snapshots frequently enough to provide any real value in recovery for fear of the performance impact of retaining more than a dozen snapshots. Moreover, with a deep catalog of snapshots, customers frequently have problems finding a suitable snapshot for recovery.

The issue with using the backup process to prepare VMware for minor disasters is the time it takes to recover the data and the amount of data likely to be lost. Even so-called “instant-recovery” options available from some backup software vendors take more than 30 minutes to execute and, because of backup infrequency, result in hours of data loss. Also, if the minor disaster is a storage system failure, all the snapshots are lost, and there is no destination for backup recovery.

Treating minor Disaster as an HA Problem

Many data centers have a small group of applications designated as mission-critical. These applications will often have a mirrored set of resources to ensure high availability (HA) and complete invulnerability to a minor disaster. The difficulty of using HA when preparing VMware for a minor disaster is its extremely high cost, which makes it almost impossible to include a broad section of the organization’s data and applications. Not only does IT have to double the server, network, and storage hardware investment, but it also has to pay for additional software licenses like VMware or storage software. Most organizations provide no discount for the secondary installation, even though it will sit idle most of the time.

The real-time protection of most HA solutions leaves the protected copy vulnerable to the same failure, like a ransomware attack. In addition, the HA solution typically doesn’t translate into a viable off-site solution for major disasters. The result is extra cost and operations effort.

Another Option: Solving the VMware Minor Disaster Problem with IOprotect

VergeIO’s IOprotect capability provides much of the functionality of the HA option at a price lower than the backup option. It can also be the foundation of your remote DR site, consolidating all disaster recovery within a single piece of software. With IOprotect, preparing for and recovering from major and minor disasters is much more straightforward and cost-effective.

preparing VMware for minor disasters with IOprotect

Since IOprotect is built-in to VergeOS, it gains the same software efficiencies, which means it can run more workloads on less hardware. That means your secondary minor can run on fewer nodes and use commodity storage internal to the server, avoiding the cost of a second SAN. Many customers use older-generation servers, enabling them to establish a standby environment for a fraction of the production price. IOprotect is priced for the use case and is up to 80% less expensive than VMware.

Once the minor disaster recovery environment is established, customers can use IOprotect to replicate an instance to the DR site, which also benefits from the same efficiency and lowers the cost of preparing for a major disaster. Organizations can use IOprotect just for protection from major disasters, but its cost-effectiveness makes protecting against minor disasters simple and affordable. It executes near-realtime data protection, making immutable, space-efficient snapshot copies of production data locally and then replicating it to a remote DR site.

No matter the failure, VergeOS with IOprotect enables rapid recovery. It is a complete disaster recovery solution, not just storage. All capabilities, storage, networking, and computing are available on the second minor and third remote DR instances. It also lays the groundwork for a VMware Exit if you decide to reduce costs further and increase the capabilities of the production environment. With VergeOS, you can lower your infrastructure costs by more than 70% and extend its life by years.

Filed Under: Protection Tagged With: ,

by

Most of the questions in a recent event we did with Truth In IT were about comparing VMware to VergeOS. There were so many we couldn’t answer them all during the session. Since we think these are questions that even IT professionals who didn’t attend the event will ask, we’ve assembled a blog answering them. If you missed the event, you can watch the on-demand version here.

In addition to comparing VMware to VergeOS questions, there were plenty of questions related to resiliency, ransomware protection, and scalability. We will get to all those questions in a future blog.

The top comparing VMware to VergeOS questions were:

comparing VMware to VergeOS
Watch the VergeOS Deep Dive
  1. Is VergeOS a complete replacement for VMware?
  2. How do you migrate from VMware to VergeOS?
  3. Is using VergeOS easier than using VMware?
  4. Is VergeOS better for smaller organizations than VMware?
  5. Is VergeOS suitable for large data centers?
  6. How does VergeOS’ performance compare to VMware’s?
  7. How does VergeIO’s support compare to VMware’s?

Before we answer the questions, let’s see how VergeOS compares to VMware.

Comparing VMware to VergeOS as a Data Center Platform

About five years ago, VMware’s VMworld event theme was “Software Defined Data Center. (SDDC)” The company wanted to move beyond software-defining a server with their hypervisor toward software-defining storage (vSAN) and the network (NSX). Organizations that embrace an SDDC concept can use whatever hardware they wish to meet their needs. If they become dissatisfied with a software vendor, like VMware, they can switch without being forced to replace hardware. The customer is in control.

At VergeIO, we agree with the premise of SDDC but disagree with VMware’s execution. Instead of creating a tightly integrated data center operating system, they, through acquisition, created a stack of software packages that IT must manage separately. They were building a hyperconverged infrastructure (HCI). The problem with HCI is that while the architecture bundles the data center’s three primary components (compute, network, storage), they, are still three separate entities. Where the old three-tier stack (Network-Hypervisor-SAN) was physically separated, HCI is logically separated. This physical or logical separation leads to continued complexity and lack of efficiency. It doesn’t solve anything.

VergeOS integrates into a single code base, networking, server virtualization, and storage. We call it Ultraconverged Infrastructure (UCI). One data center operating system is easier to manage and is far more efficient than one that operates as a series of interconnected parts. As a result, customers get better performance and scalability from the existing hardware.

Comparing VMware to VergeOS highlights the core difference is how the development teams craft their solutions. Do you stack a bunch of separate software packages together and try to hide their separation through a common interface, or do you provide all the functionality through a single interface? One leads to inefficient use of hardware and expensive, complicated licensing agreements. The other leads to very efficient hardware use and a simple, inexpensive licensing model.

To learn more about the VergeOS architecture, watch this deep-dive LightBoard video of with CTO and founder, Greg Campbell.

Is VergeOS a Complete Replacement for VMware?

Yes, but you don’t have to flip the switch on day one and throw out VMware. Most customers move to VergeOS gradually. They start with a proof of concept, which is usually up and running in less than an hour, then move to use our IOprotect solution to reduce their disaster recovery costs. After that, VergeOS now has a copy of all the data, so they may start using VergeOS for test-dev, QA, or reporting. Next, they may start putting new workloads into the environment and then finally start moving production workloads. The result is a seamless transition that goes at a pace you define.

If you want to learn how to enhance your VMware DR strategy while lowering costs, register for our interactive virtual whiteboard session, live on April 12th.

How do You Migrate from VMware to VergeOS

comparing VMware to VergeOS

Comparing VMware to VergeOS requires migration, and our IOmigrate capability makes that seamless. Once you install VergeOS on a couple of nodes, you can point it at the VMware cluster, and you’ll see all the virtual machines (VM) in our interface. At that point, you can select some or all of the virtual machines and import them into the VergeOS environment. Once the VMs are running under VergeOS, take a snapshot of them, which protects the original copy, then you can stress-test it to your heart’s content without fear of data loss. Our snapshots are space efficient, immutable, and don’t impact performance, so you can take as many as you want and retain them indefinitely.

comparing VMware to VergeOS

Sign up for our Digital Learning Guide and learn how to create a VMware Exit Strategy.

Comparing VMware to VergeOS Ease of Use

It is easy for any vendor to claim that their solution is easier to use than another solution. To compare VMware to VergeOS regarding ease of use, I’ll relay what our customers tell us. Most tell us they can get the proof of concept going in an hour. The move to using us as a DR target and the move to production is seamless because it is all the same software.

Operationally the common theme is “it just works” and “I go for weeks without even touching it.” They all rave about the ease of implementing patches and software updates. That is the value of one software to drive the entire data center. The user interface is very easy to interact with while still enabling very advanced capabilities.

Is VergeOS Suitable for Small Organizations

Small Organizations, or what we call the server room use case, embrace the idea of VergeOS for several reasons. First, you can easily start with two nodes, loaded with storage, and, in many cases, address all your needs for virtualization, storage, and networking. Small data centers or server rooms often also mean small IT teams. One data center operating system that controls all functions makes day-to-day operations easy. VergeOS is also inexpensive. We don’t charge by cores, memory, or even storage capacity. The software is priced per node, so two or three licenses are all you need for a typical server room deployment.

Is VergeOS Suitable for Large Data Centers

VergeOS’ suitability for small organizations doesn’t mean it isn’t suitable for large organizations. We have customers with over one hundred nodes in a single instance of VergeOS. Those customers typically manage thousands of virtual machines and multiple petabytes of capacity. They also enjoy and benefit from the ease of use and cost savings of VergeOS.

Comparing VMware to VergeOS Performance

The efficiency of VergeOS helps both large and small data center customers. We are often installed on the same hardware that used to run VMware. Customers find the VergeOS environment performs much better than VMware. The improvement in performance means they can virtualize more workloads on fewer servers, delay the planned purchase of new servers, and run servers for years longer than expected. They can also virtualize some workloads that they thought must run on bare metal.

Comparing VMware to VergeOS Support

It is hard to compare support between the two companies. We hear from customers switching to VergeOS that the quality of VMware support is declining, especially for smaller customers. I speak to customers every week who are astounded by the quality of our technical support and amazed at how far the team will go to help them fix problems that don’t have anything to do with VergeOS.

Conclusion

Comparing VMware to VergeOS shines a light on the efficiency of our software. Our developers continue to invest in ensuring the software runs at its most optimal level, gets the most out of the available hardware resources, and presents its power in the simplest form possible. The result is a drastic reduction in infrastructure costs and dramatic increases in operational efficiency. This craftsmanship is immediately apparent when you install the software and is why so many customers are switching from VMware and Hyper-V to VergeOS.

Next Steps

Try It: Register to download an evaluation copy of the software.

Watch: A LightBoard Video of our CTO discussing the VergeOS architecture.

Learn: How to Create a VMware Exit Strategy with our Digital Learning Guide

Register: For our next Whiteboard Wednesday, VMware Disaster and Ransomware Recovery—The Three NEW Best Practices

Filed Under: Virtualization Tagged With: , ,

by

As IT budgets tighten, an area to explore is lowering VMware DR costs. The costs to maintain a disaster recovery (DR) process and site add up quickly. Cutting costs, though tempting because it is rarely actually used, may put the organization at risk if a disaster strikes. Fortunately, lowering VMware DR costs does not always have to come with greater risk.

Three Steps to Lowering VMware DR Costs

  1. Lower the cost of the software license
  2. Make more efficient use of the hardware
  3. Expand beyond the DR Use Case

We’ll explain the three steps below and in our upcoming virtual whiteboard session, “VMware Disaster and Ransomware Recovery—The Three NEW Best Practices.“

Lowering VMware DR Software Licensing Costs

The first step is to lower the cost of the software licensing used to replicate and support the remote site infrastructure. Most VMware DR initiatives require a software or hardware solution to replicate the data to the DR site and then a copy of VMware at the DR site to perform testing and host workloads in the event of an actual failure. Reducing the number of solutions the DR process requires and paying less for them without exposing the organization to greater risk will show almost instant savings. These savings increase significantly if the potential solution can run on existing hardware.

Lowering VMware DR costs starts with a cost-efficient solution that is easy to install

VergeIO’s IOprotect is easy to install and seamlessly protects your VMware environment from a disaster or ransomware attack. It typically costs 60% less than the equivalent software from VMware or a third party. There is also just one software package to buy. IOprotect does not require a VMware license at the DR site. Finally, IOprotect runs on your existing hardware, so in most cases, there is no additional hardware to purchase.

The result is a rapid return on investment (ROI). Most customers can install VergeOS onto hardware they already own and begin replicating data from their VMware site in a couple of hours. The time for payback starts immediately, and the investment cost is returned in weeks rather than years.

Make More Efficient Use of Hardware

Because of cost reasons, most organizations have to designate a “select few” workloads for inclusion into the DR process. Each workload they add increases the software licensing and physical hardware requirements at the DR site. In some cases, the storage solution at the DR site will require more capacity, which also means an increase in capacity-based storage licensing. Lowering VMware DR entry costs enable IT to protect more workloads and amortize the investment. Efficiency also extends the life of the hardware, further lowering costs.

IOprotect is integrated into VergeOS, a highly optimized ultraconverged infrastructure (UCI) solution. Thanks to its efficiency, the hardware has more resources available, and customers can add additional workloads to the DR process with minimal or no additional cost. VergeOS also includes global inline deduplication, so adding additional workloads does not significantly increase DR site storage requirements. Sometimes, even with the additional workloads, customers can decommission hardware or repurpose it elsewhere in the organization.

Don’t Use The Cloud for Lowering VMware DR Costs

Companies that look to lower VMware costs inevitably look to cloud options. The options often appeal because there are no upfront hardware costs. The problem is that paying monthly for the servers and storage that DR requires adds up quickly. IOprotect, because it uses existing hardware, is a more cost-effective solution, both upfront and especially long-term. With it, you use the hardware you have already paid for, so there is no monthly surprise. Even if you can provision servers on the fly, the storage must be paid for each month.

Lowering VMware DR Costs with More Use Cases

What if you could make your DR process do more? If the software driving that process is efficient, you can do more with the DR process without buying more hardware. The software also has to have the capability to support whatever you define as “more.” Because of the low cost and efficiency of IOprotect, many customers will create an on-premises DR solution using spare servers in addition to the remote DR solution. An on-premises DR solution enables you to recover quickly from disasters that are not site-wide and not have to fail over to another data center. It is ideal for situations like a storage system failure, a rack failure, or even a ransomware attack.

Lowering VMware DR costs can enable IT to expand the use case

With an on-premises or remote DR solution and efficient software, you can expand out of the DR use case and use the solution for Test-Dev, Quality Assurance, and reporting. Some customers leverage VergeIO’s Virtual Data Center (VDC) technology to create a secure instance of their data center for cyber-response training.

The last use case is migrating your production VMware environment to VergeOS, amplifying the cost savings across both use cases, and completing your VMware Exit.

Next Steps

  • Sign Up: for our Video Digital Learning Guide – “Modernizing VMware Disaster Recovery.”
  • Register: for our next virtual whiteboard session – “VMware and Ransomware Recovery—The Three NEW Best Practices.”
  • Read: about creating a VMware Exit Strategy.

Filed Under: Virtualization Tagged With: ,

by

Disasters and Ransomware attacks continue to increase in number and severity. Get Prepared!

Join VergeIO’s Director of Development, Paul Hodges, Jeffrey Campbell, Customer Success Manager, and George Crump, CMO, as they map out three new best practices for rapidly recovering from a ransomware attack using our virtual whiteboard technology.

LEARN:

The Three New Best Practices for VMware and Ransomware Disaster Recovery:

  1. Prepare for Server, Data and Site Disasters
  2. Focus on Applications not Just Data
  3. Continuously Drive Down Costs

The team will also discuss how VergeIO customers have used VergeOS to recover from disasters and ransomware attacks without disrupting the business.

Event Details: Live on Wednesday, April 12th
1:00 pm ET / 10:00 am PT

About Our Speakers

  • Paul Hodges has been with VergeIO since its inception and is one of the company’s lead developers. His team is responsible for making a recovery from disaster or ransomware attacks as seamless as possible.
  • Jeffrey Campbell runs VergeIO’s Customer Success team and has first-hand experience helping customers recover from disasters and ransomware attacks.
  • George Crump before joining VergeIO, was an IT Analyst for 15 years and spent five years leading TechTarget’s SearchStorage and SearchDisasterRecovery workshops, training IT professionals worldwide to develop fully functioning disaster recovery plans.

Filed Under: Past Webinar, Webinar Tagged With:

by

Don’t Make these VMware Exit Mistakes

The industry is full of advice on things you should do when considering a VMware alternative, but did you know there are four don’ts of a VMware exit? Accepting a vendor’s excuse for why you must do these “don’ts” can lead to higher costs, unsuccessful conversion, and a premature infrastructure refresh.

The Four Don’ts of a VMware Exit are:

  1. Don’t Focus on the Price
  2. Don’t Buy or Borrow Hardware
  3. Don’t Run a Proof of Concept
  4. Don’t Validate with Creampuff Use Cases

1. Don’t Focus on the Price of a VMware Exit

Of course, you should look at the price of the potential VMware alternative. Our suggestion, though, is don’t look solely at the price but also to ensure the product will take you forward in terms of capabilities. The solution should be less expensive than VMware and deliver measurably better efficiency, performance, scalability, and data protection capabilities. Make sure you look at both the return on investment and the total cost of ownership as part of your VMware Exit.

2. Don’t Buy New Hardware when you Exit VMware

The Four Don'ts of a VMware Exit. Don't buy new hardware!
Buying New Hardware Increases
the Cost of a VMware Exit

The second don’t of a VMware exit relates to hardware. If the VMware alternative you are considering can’t run on your existing hardware, stop looking and move to the next candidate. You bought into the software-defined data center (SDDC) for this exact scenario, so you can switch software solutions while continuing to use your current hardware assets. Forcing you to buy new hardware means the potential new vendor takes shortcuts and depends on specific hardware features or capabilities. Not only does this mean a higher upfront cost it also means you are guaranteed to face future infrastructure refreshes.

3. Don’t Run a Proof of Concept when you Exit VMware

Not running a proof of concept (POC) may sound a little crazy, and we do not suggest you skip testing the potential VMware alternative. A proof of concept is not enough. The third don’t of a VMware exit acknowledges you can’t, in 30 days, test every aspect of a new platform that you hope will replace a platform you have been running for over a decade!

Run a proof of concept but then look for a use case where you can use the product for months and stress the potential solution through its paces. And look for a vendor that is patient enough for you to run just this use case for a few months.

4. Don’t Validate with a Creampuff Use Case

The workloads you will run in the environment after the proof of concept begin the validation phase of the potential VMware alternative. The fourth and final don’ts of a VMware exit is not to validate with “creampuff” use cases. These are use cases that won’t stress the new environment. Nobody cares if they fail, and creampuff use cases won’t force you to test the quality of technical support. Indeed, it is OK to have a few creampuff use cases when you start the validation phase, but as you progress into the heat of the phase, look to run a process or workload critical to the enterprise without impacting day-to-day operations.

An ideal use case is disaster recovery (DR). It is critical to the organization, but if something goes wrong, it won’t impact day-to-day operations. DR also puts a significant load on the potential alternative. It has to receive all the data from your VMware environment continuously. Then when you perform DR tests, you are running entire instances of your workloads with the latest copies of data. DR stresses each element of a potential VMware alternative, including storage and networking. If the solution can pass the DR test both in terms of functionality and usability, you’ve gone a long way toward validating it for replacing VMware in production.

VergeOS Does Enable a Seamless VMware Exit

VergeOS is less expensive than VMware and other VMware Alternatives. Most of our customers find it reduces their licensing costs by more than 50%. These cost savings do not come at the expense of capabilities. VergeOS delivers better performance and capabilities than VMware while also being more resilient and easier to manage.

VergeOS runs on your existing hardware and breathes new life into your existing hardware, enabling you to consolidate more workloads on fewer nodes. Running more workloads on the same hardware significantly reduces total ownership costs. VergeOS’ hardware flexibility makes VergeOS easy to run through a proof of concept, enabling you to move quickly into the validation phase. Provide VergeIO with two or three spare servers, install the software, migrate a few workloads, and begin testing. Most customers can start their POCs within an hour of downloading the software.

The Four Don'ts of a VMware Exit
IOmigrate provides a Seamless VMware Exit to VergeOS

The cost-effectiveness of VergeOS makes it realistic to run the validation phase for months before committing fully to it. And you don’t have to run creampuff use cases! VergeOS has integrated capabilities to enable you to use the solution as a disaster recovery site for your VMware environment. Not only does this give you the ability to run the software in a stressful environment it also enables you to experience the VergeOS cost savings almost immediately. Most of our customers find they can reduce the licensing costs of their DR site by more than 60% and include more workloads in the DR process, all without requiring additional hardware.

Next Steps

  • Watch: One-Slide Webinar and Demonstration of a VMware Migration
  • Read: Our Digital Learning Guide, “How to Develop a VMware Strategy”
  • Schedule: A technical whiteboard session personalized for your environment

Filed Under: VMwareExit Tagged With: , ,