Skip to content

Real Challenges Users Face When Migrating from VMware to OpenStack

Most organizations have become frustrated since Broadcom acquired VMware in 2023, due to the astronomical price rise and other changes made by the technology giant. As a result, they have begun seeking alternative platforms, and OpenStack has become a leading choice.

However, the migration process isn’t a smooth sail. Users have faced numerous challenges during migration because of the differences in both platforms. This article discusses the reason for the transition from VMware to OpenStack, the real challenges users face, and their solutions.

Why Organizations are Migrating from VMware to OpenStack

Businesses migrate from VMware to OpenStack due to various reasons, including:

Cost

The primary reason organizations are migrating from VMware to OpenStack is the heavy price increase by Broadcom after they acquired VMware. Customers have complained about the dramatic hike in price, product bundling, and the shift to a subscription model.

Some product prices have seen as high as 10 times increase since the acquisition in 2023. This significant change has forced many organizations to seek alternatives to VMware, especially open-source platforms that eliminate licensing fees and other extra costs.

Scalability and Performance

OpenStack is scalable, making cloud hosting convenient for large-scale operations. It can handle the growing demand over time without sacrificing performance, ensuring high performance and productivity. Also, OpenStack scales horizontally across servers, making it an excellent choice for organizations managing data across various geographic locations.

Vendor Lock-in

OpenStack’s open-source system prevents vendor lock-in, which has several disadvantages. Rather than being restricted by proprietary products, OpenStack supports a wide range of hardware and software environments, broadening the available options and reducing dependency on a single vendor.

Flexibility

Thanks to its modular design, OpenStack may be readily tailored to fit the particular requirements of a company. Its architecture allows every element to be deployed and scaled independently. Thus, organizations have greater options. It offers flexibility to fit many contexts and use cases by supporting integration with a broad spectrum of third-party tools and technologies.

Technological Advancements

Its open-source nature ensures the continuous evolution and update of the platform. OpenStack has a large and active community that contributes regularly to its development through constant improvements. This ensures that the platform keeps up with the latest technology trends, innovations, and advancements for better functionality and security.

Problems Users Face When Migrating from VMware to OpenStack

Migrating from the proprietary solution, VMware, to open-source, OpenStack doesn’t come without challenges. There are several common issues users have encountered when migrating to OpenStack. They include:

  • Finding a Migration Path

One major problem users encounter is finding a smooth migration path. The complex reconfiguration and mapping process makes it difficult to move from VMware to OpenStack. Also, organizations consider the risk of interruption caused by a cold migration. As a result, they want warm or hot migration that prevents downtime, ensuring uninterrupted operation.

Solution

The best way to navigate this migration challenge is using automated migration solutions. The appropriate tool to use will depend on your dynamic situation and expectations. You can also consult with an expert, for advice or their services.

  • Hardware Load Balancing

Hardware load balancing has to do with distributing workloads across multiple servers and resources to optimize operation and prevent overload. When transitioning from VMware to OpenStack, organizations may find it difficult to balance workload. VMware provides automated load balancing features like DRS but workload balancing on OpenStack is more complex.

Solution

OpenStack has a feature called Watcher, a live migration strategy. However, they are yet to determine if it’s suitable for migrating several VMware at the same time. Hence, you can only transfer one VMware at a time. Also, using the phased migration strategy can help to balance workload and resources, preventing overloading.

  • Compatibility Issues

Compatibility is a big issue when migrating from VMware to OpenStack. VMware has proprietary products, including its file formats like VMDK. Hence, users have to find a way to go around the compatibility issue, which could be challenging and time-consuming.

Solution

Leverage migration tools that enable compatibility between VMware and OpenStack. These tools can help in converting VM formats, mapping network configurations, and integrating storage solutions to ensure smoother transitions. Also, create a test environment to check compatibility before installment and make the required adjustments.

  • Skill Gap

Another main challenge is the skill gap. With most workers having VMware-specific skills, the learning curve is usually steep. The integrated nature of the VMware environment makes it easy for users with limited technical expertise to use. However, OpenStack relies on external services such as Nova and Neutron and understanding OpenStack will require a more sophisticated skill set.

Solution

Organizations must invest in training programs to equip IT staff with the necessary knowledge of OpenStack architecture. They can also set up a test environment to provide hands-on training ahead of the full-scale migration.

  • Performance Issues

Performance issues can also arise during migration because of the differences in both platforms, including hypervisor, storage, compute, and networking. These differences will mean that VMware is optimized to suit its hardware and configurations. However, the process differs for OpenStack which also needs to be specifically optimized to its own configurations to achieve the same performance requirements.

Solution

Organizations must plan ahead by sizing their resources and estimating their performance requirements. Pilot testing can help to identify performance gaps and fix them in time.

Migration Planning

Migration Planning is a crucial step organizations and users must take to ensure the smooth migration from VMware to OpenStack.

Migration planning involves strategizing and creating a detailed road map that outlines each migration phase. Before developing a plan, you must access your current VMware infrastructure, define your objectives, and also predict challenges and possible solutions. Designing a well defined plan will reduce problems during migration and also ensure the OpenStack environment meets the organization’s needs effectively.

Backup and Recovery

If a company uses Storware Backup and Recovery, changing the data protection software is not necessary. Storware supports both solutions, and the planned migration module may successfully enable the recovery of VMware environments in the OpenStack infrastructure.

Conclusion

VMware is a proprietary solution, while OpenStack is an open source. Hence, migrating from VMware to OpenStack poses several challenges like compatibility, performance issues, finding a migration path, hardware load balancing, and the skill gap. Follow the solutions provided, create a strategic and well-defined migration plan, and also seek advice from the active OpenStack community.

Implementation Challenges of Automation and Orchestration

Although the benefits of automation and orchestration on data management are huge, there might still be a few challenges while trying to implement these technologies. Common problems include the following:

Compatibility Problem:

If compatibility issues exist, automation and orchestration tools may not easily integrate with a company’s systems and infrastructures. This can incur extra expenses, as you may have to replace their infrastructure.

Skill Gaps:

Organizations may lack the in-house expertise to operate these infrastructures. Hence, you must employ an extra hand with the appropriate technical know-how. Leverage their expertise in implementation techniques to help assist in the implementation process. Also, you need to educate and develop IT staff to be competent in managing and supporting new technologies, ensuring the smooth running of the organization’s backup and recovery system.

Change Management: 

Migrating from manual to automated data management processes instills an entirely new culture within a company. Therefore, organizations must develop robust strategies to effectively manage this change and allow staff to transition seamlessly from the former system to the advanced one.

Conclusion

Advancements in data automation tools and orchestration platforms bring data backup and recovery to a whole new level of efficiency, reliability, and affordability. An organization can protect vital data and assure business continuity through continuous data protection, AI-powered optimization, cloud-native solutions, orchestrated disaster recovery, and self-healing functionalities. These technologies empower the organization to manage data effectively and efficiently, mitigate potential human errors, and ensure the quick restoration of critical data in the case of a disaster or system failure.

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About Storware
Storware is a backup software producer with over 10 years of experience in the backup world. Storware Backup and Recovery is an enterprise-grade, agent-less solution that caters to various data environments. It supports virtual machines, containers, storage providers, Microsoft 365, and applications running on-premises or in the cloud. Thanks to its small footprint, seamless integration into your existing IT infrastructure, storage, or enterprise backup providers is effortless.

Cloud-to-Cloud Backup

The high demand for SaaS has led to a surge in interest in Cloud-to-Cloud Backup services. All indications are that this trend will continue in the coming years.

The Rise of SaaS and Cloud Storage

Business customers are increasingly abandoning “boxed software” in favor of SaaS. For several years now, this has been the most popular type of cloud service. According to Gartner, the SaaS market will reach $176 billion this year and $280 billion next year. As the “State of SaaSOps” report shows, companies use an average of 80 IT-sanctioned applications, with 70% of business applications based on SaaS. Cloud-based software has changed the way companies access and store data. The popularity of Cloud-to-Cloud Backup services is rapidly growing on the wave of SaaS.

The largest cloud service providers like to boast about their higher security standards compared to companies using their own IT infrastructure. However, contrary to the marketing boasts of Amazon AWS, Microsoft Azure, and Google Cloud Platform, they do not guarantee complete security for users. A famous Polish boxer, Jerzy Kulej, once said, “There’s no one who’s invulnerable to a punch, only those who are poorly hit.”

So, the situation is not as rosy as the marketers working for the “big three” try to convince us, but it’s also not as bad as opponents of cloud services claim. Cyber gangs can occasionally hit giants hard, although these are not common occurrences.

From the perspective of a SaaS user, the most important thing is that service providers only protect their own data and infrastructure, and they do not create backups of files, databases, or virtual machines belonging to customers as part of their standard offer. For example, the Microsoft Azure service agreement states that the provider recommends that users regularly back up their data using “third-party services or applications.” Microsoft, like its largest competitors, operates on a shared responsibility model, which in practice means that it does not create data copies for users, and SaaS users must take care of comprehensive backup and disaster recovery themselves.

Blind Trust Can Be Costly

Entrepreneurs approach cloud service providers’ offers in various ways. Often, you can encounter extreme attitudes – some are exceptionally distrustful of providers and don’t want to move data from their own data center, while others place boundless trust in them. Unfortunately, excessive faith in the operator’s capabilities can result in the loss of valuable information, and in the best-case scenario, expenses related to its recovery. As a study conducted last year by ESG shows, only 13% of respondents realize that when using SaaS, they must take responsibility for data protection themselves. In a similar survey conducted seven years earlier by Aberdeen Research, this percentage was 9%. Although there is some progress, it is not very impressive. C2C backup service providers still have a lot of work to do, both in promoting their products and educating SaaS users.

Data loss for SaaS-managed services can occur as a result of human error, a cyberattack, or errors made during the data synchronization or migration process. IT specialists participating in this year’s Spanning Cloud Apps survey identified three main reasons for using SaaS backups. Half of the respondents consider creating SaaS data backups as a necessary step to minimize the risk of data loss and downtime, nearly 20% do it to protect the company and data from human errors, and 15% want to protect themselves from ransomware attacks.

C2C Backup Minimizes the Risk of Data Loss

What pays off more – taking the risk and not performing regular SaaS backups, and in case of misfortune paying the service provider for data recovery, or using applications or services from external companies? This is a dilemma faced by many companies. The first of the mentioned options is neither cheap nor short. For example, for the Salesforce Data Recovery service, the customer pays a one-time fee of $10,000, and the order fulfillment time is 6 to 8 weeks. Even if the above price is acceptable for large enterprises, the waiting time can give IT managers a heart attack. Some services, such as Microsoft 365, work with tools like OneDrive, providing at least basic protection. However, these are indirect solutions, not guaranteeing the security that most organizations need.

It is therefore not surprising that more and more companies are using C2C backups. Until the end of 2014, the service remained in a deep niche. It became more widely known when EMC (now Dell EMC) acquired Spanning Cloud Apps. Since then, this market segment has begun to develop. Interestingly, three years later, EMC sold this company to the Insight Venture Partners fund. Currently, each of the major players in the data protection market has C2C backup in its portfolio. This is a very interesting proposition for several reasons. Vendors who focus solely on backup and DR have top-class specialists and extensive experience, so their products allow for cheaper and faster backups than, for example, the aforementioned Salesforce or backup services offered by AWS Amazon, Microsoft Azure, or Google Cloud Platform. In addition, they take into account many data loss scenarios. They are also flexible in restoring from cloud-to-cloud backups, as the organization can restore data to various computers, such as laptops or other mobile devices. The fact that C2C backup does not require additional hardware is of great importance.

Cloud backup can be a cheap solution, especially for consumers and small businesses that do not have a large amount of data to protect. Finally, creating backups in the cloud through a service provider is easier to manage, as an external company takes everything upon itself. Nevertheless, this element may be perceived as negative for those customers who want to have complete control over their backups.

C2C Backup or On-Premise Backup?

Not all CIOs are fans of C2C backup services. Opponents point to the costs associated with cloud-based backups. The highest fees are charged for data egress, when data is downloaded or copied from a cloud location. For infrequently used digital assets, these costs can be manageable. However, experts note that while storage costs are relatively low, data recovery fees can often shock CFOs and IT heads. Therefore, it’s crucial to carefully read C2C backup service agreements, especially the fine print. Creating backups from cloud to cloud can also be costly and complex in multi-cloud deployments.

Other challenges in cloud environments include limited bandwidth and latency. Therefore, one way for organizations to gain confidence in C2C backups is to test them.

Businesses can also create SaaS backups on local servers. One advantage of traditional backups compared to C2C is the speed and ease of data recovery. Traditional backups are useful when recovering large amounts of digital assets and in situations where users need quick access to data.

Storware Backup and Recovery’s Cloud-to-Cloud Backup Support

Storware Backup and Recovery is a comprehensive data protection solution that supports various platforms, including cloud environments. Its C2C (Cloud-to-Cloud) backup functionality allows you to protect your data residing in one cloud environment and replicate it to another, providing a robust disaster recovery strategy.

Key features and capabilities of Storware’s C2C backup:

  • Platform Support: Storware supports major cloud platforms like AWS, Azure, and GCP, ensuring compatibility with your existing infrastructure.
  • Data Replication: You can seamlessly replicate your data from one cloud environment to another, ensuring redundancy and protection against data loss.
  • Scheduling and Automation: Automate backup schedules to streamline your data protection process and reduce manual intervention.
  • Granular Control: Exercise fine-grained control over your backup policies, including retention periods, compression levels, and encryption settings.
  • Incremental Backups: Optimize backup efficiency by only backing up changes since the last backup, reducing data transfer times.Security: Storware incorporates robust security measures like encryption to protect your sensitive data during transmission and storage.
  • Integration: Seamlessly integrate Storware with your existing cloud infrastructure and management tools.

Benefits of using Storware’s C2C backup:

  • Enhanced Data Protection: Protect your data against various threats, including accidental deletion, hardware failures, and cyberattacks.
  • Disaster Recovery: Ensure business continuity by having a reliable backup of your data in a separate cloud environment.
  • Compliance: Meet industry-specific compliance requirements that mandate data protection and redundancy.
  • Cost-Effective: Optimize your backup storage and network usage by leveraging cloud-based infrastructure.

By leveraging Storware’s C2C backup capabilities, you can effectively protect your cloud-based data and ensure business resilience.

Storware Backup and Recovery Architecture

Summary

A comprehensive overview of Cloud-to-Cloud Backup (C2C Backup) services and their growing importance in the context of SaaS adoption. Key points include:

  • Increasing SaaS adoption: The shift from on-premises software to SaaS has driven the need for C2C Backup solutions.
  • Limitations of cloud providers’ security: Despite claims of high security, cloud providers like AWS, Azure, and GCP do not provide full backup and recovery services for customer data.
  • Shared responsibility model: The responsibility for data protection primarily lies with the customer, not the cloud provider.
  • Benefits of C2C Backup: It offers a cost-effective and managed solution for data protection, addressing challenges like human error, cyberattacks, and data loss.
  • Challenges and considerations: Factors such as cost, performance, and data sovereignty can influence the choice between C2C Backup and on-premises solutions.

Key arguments in favor of C2C Backup:

  • Cost-effective: Especially for small businesses and consumers with smaller data sets.
  • Managed service: Cloud providers handle the backup and recovery process.
  • Flexibility: Ability to restore data to various devices.

Potential drawbacks:

  • Cost: Data egress fees can be significant.
  • Performance: Limited bandwidth and latency can affect recovery times.
  • Data sovereignty: Some organizations may have concerns about storing data outside their control.

In conclusion, the text highlights the growing importance of C2C Backup services in today’s cloud-centric environment. While cloud providers offer significant benefits, it’s crucial for organizations to understand their shared responsibility in data protection and to carefully evaluate their options when choosing a C2C Backup solution.

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About Storware
Storware is a backup software producer with over 10 years of experience in the backup world. Storware Backup and Recovery is an enterprise-grade, agent-less solution that caters to various data environments. It supports virtual machines, containers, storage providers, Microsoft 365, and applications running on-premises or in the cloud. Thanks to its small footprint, seamless integration into your existing IT infrastructure, storage, or enterprise backup providers is effortless.

Preparing for Your Next Tomcat Upgrade

Planning an Apache Tomcat upgrade (or migrating to the latest version of Tomcat) can pose challenges to unsuspecting enterprises. But Tomcat migrations and upgrades are key to maintaining security and to unlocking the potential of newly-supported features and improvements found in later versions of Tomcat.

In this blog, we look at how to prepare for your next Tomcat upgrade, with details on the Tomcat community support lifecycle, considerations like how often enterprises should be upgrading/migrating, and the basic steps of performing an Apache Tomcat migration or upgrade.

Editor’s Note: This blog was originally published in 2022 and was updated in 2024.

Understanding the Apache Tomcat Lifecycle

There are two active branches of Tomcat at the time of this writing: 9 and 10. Tomcat 8.5 reached end of life (EOL) on March 31, 2024. The Tomcat community typically does a good job of communicating end of life at least a year in advance for versions going EOL. These EOL announcements are typically accompanied by news regarding the next major version; the Tomcat 8.5 EOL date was announced around the same time as information about Tomcat 11 first emerged.

Tomcat Version

Release Date

End of Community Support

6.0

February 28, 2007

December 31, 2012

7.0

January 14, 2011

March 31, 2021

8.0

June 25, 2014

June 30, 2018

8.5

June 13, 2016

March 31, 2024

9.0

January 18, 2018

TBD

10.0

February 2, 2021

TBD

Ultimately, which branch you choose is likely based on what version of Java you’re using along with it. The Tomcat website has a reference chart to help you figure out what versions of Java work with what versions of Tomcat.

What to Consider Before Your Apache Tomcat Migration or Upgrade

If you happen to be upgrading in the same major branch versions, your configuration file will likely transfer easily in between versions. This means your testing of minor releases should be relatively pain free and not take a lot of time and resources from your team.

Migrating from a major version to another, however, requires that you rewrite your configuration based around all the major changes incorporated into the new major version. Testing for this will take a greater amount of time and resources due to the nature of there being significant changes between major versions of Tomcat.

Reading the release notes is going to provide you with an overview of what to expect. Because of this, we advise you pick the newest version of Tomcat that you can, so that you get the longest range of time of support from the Apache community.

How Often Should You Upgrade Tomcat?

Some apps function so smoothly, we set them out in production and they do their job so well, that touching it becomes almost out of the question because if it isn’t broken, does it need fixing? That is a complicated question, because the answer can be circumstantial. If the app and infrastructure around it are all working soundly, you may not see any reason to do a minor upgrade. But then one day, you hear from the community that there is a CVE or more relating to a version that you’re currently using. Now, there’s a motivating factor to remediate the security issue. Keeping up with the security of Tomcat is important for anyone using it in a production environment, and the longer you wait to upgrade or migrate, the less smoothly things are likely to go.

How Often Should You Migrate to a New Tomcat Version?

Migrating to a newer Tomcat branch is a trickier task, since bringing over your configuration from the previous branch will not work. Migration will require significant testing to verify that your code will work with the app server. The more moving parts in play the greater the risk of older apps not being fully compatible.

Knowing the EOL dates ahead of time is going to give your organization the necessary heads up of when they will have a greater need to migrate.

Tomcat’s website states that on average a major release of Tomcat is good for 10 years. This is a significant window by comparison to other known application servers, giving your organization time to plan accordingly. Apache has also written specific documentation for migrating.

Back to top

How to Prepare for Your Next Apache Tomcat Upgrade / Migration

The very first thing to do before migration is to take back ups of everything. Document what sort of changes you’re going to be making to the environment so that you have an accurate account for everything you’re going to do. Going over metrics of when the app is in use will allow you to know when the best time to perform the migration is. 

Step #1: Determine Your Migration / Upgrade Path

Determine which version of Tomcat you will be upgrading to, along with the required version of Java that Tomcat requires. Read the release notes to see what sort of major changes you’ll be dealing with, as it might also give you insight to the new features available as well.

Step #2: Complete a Test Install and Compare Configuration Files

Using the same OS that you will be deploying your app on, set up the version of Tomcat you will be upgrading to in a test environment. Testing is critical for migration and is still a good practice for upgrades as well. One of the tests that you can run is a git command that compares configuration files against one another. An example of this command would look something like:

git diff 10.1.0-M1 10.1.0-M2 -- conf/

Step #3: Configure Your Test Install and Deploy Your Application to Test Environment

Configure your Tomcat instance and see if you can deploy your application in the test environment. Once you have your app up and running, you’ll want to do some testing to make sure it can handle the standard work load it’ll be under in production. The method you use to generate traffic to the server will vary depending on the type of application you’re running. It’s advised you push your server past the point that it might hit in production to prepare for any upticks in traffic. 

Step #4: Bring Test Environment to Production and Gradually Transition Workloads

Once you’ve done thorough testing of workloads on the new server, you’ll want to schedule time to bring your environment to production. The best practice is to stand the new servers up alongside the production servers, allow traffic to the new environment while maintaining the older live environment. When you’ve established that the new servers can properly handle live workloads, you may then take down the older servers one at a time, making sure that the new live servers are able to handle the workload gradually.

Back to top

Final Thoughts

With enough planning — and a proper test environment and traffic tools — you should be able to properly plan a fairly stress-free Tomcat upgrade or migration. While Tomcat versions are good for roughly ten years, there are performance gains and new features to be had when you decide to migrate or upgrade to a newer version. Upgrading and migrating should be a regular part of every organizations maintenance plan and is also critical for preventing exposure to security vulnerabilities.

About Version 2 Digital

Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.

Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.

About Perforce
The best run DevOps teams in the world choose Perforce. Perforce products are purpose-built to develop, build and maintain high-stakes applications. Companies can finally manage complexity, achieve speed without compromise, improve security and compliance, and run their DevOps toolchains with full integrity. With a global footprint spanning more than 80 countries and including over 75% of the Fortune 100, Perforce is trusted by the world’s leading brands to deliver solutions to even the toughest challenges. Accelerate technology delivery, with no shortcuts.

×

Hello!

Click one of our contacts below to chat on WhatsApp

×