VMware SRM 8.6 EOL: What to Do If You’re Still Running It

VMware Site Recovery Manager 8.6: End-of-Life Status and What It Means for You

VMware Site Recovery Manager 8.6 (SRM 8.6) reached its end-of-life (EOL) date on October 11, 2025. This milestone marks the cessation of all vendor-provided technical support, security patches, and bug fixes from VMware for this release. If you are still running SRM 8.6 in your environment, it is now officially unsupported by the vendor — but that does not mean you must rush to upgrade.

What EOL Actually Means for SRM 8.6

When a product reaches EOL, several key things stop:

• No more security patches – VMware will not release updates to address newly discovered vulnerabilities.
• No bug fixes – Even critical stability issues will not be patched.
• No technical support – VMware support will not take calls or tickets for SRM 8.6.
• No new feature releases – The product is frozen at version 8.6.0.2, the latest and final maintenance release.

However, the software does not stop working. Your existing SRM 8.6 environment will continue to run as long as its dependencies (such as vCenter Server and ESXi) remain compatible. But over time, compatibility gaps and unpatched vulnerabilities become a growing risk.

Why Some Teams Stick with SRM 8.6

Not every organization can move to the latest SRM version immediately. Common reasons include:

• Stable, static workloads – If your disaster recovery site uses the same configurations year after year, a supported-but-unchanging product may be acceptable.
• Locked application dependencies – Some business applications require specific vSphere versions or third-party integrations that are only tested with SRM 8.6.
• Hardware constraints – Older hosts or storage arrays may not meet the requirements for the latest SRM releases.
• Budget cycles – A forced upgrade may come mid-budget year with no allocated funds.

The Real Risks of Running SRM 8.6 Unsupported

Operating SRM 8.6 without vendor support introduces several concrete risks:

• Security exposure – CVE disclosures in the base software or its supporting services go unpatched. Attackers actively target known vulnerabilities in EOL products.
• Compliance gaps – Many regulatory frameworks (e.g., PCI DSS, SOC 2, HIPAA) mandate that software running on critical infrastructure must be supported or have a documented risk acceptance.
• Recovery failures – If a config change, a vCenter upgrade, or a storage firmware update breaks SRM, you will have no vendor to turn to for recovery assistance.
• Certification breakage – VMware interoperability matrices eventually drop 8.6 from validated configurations with new vCenter/ESXi versions.

Your Options: Upgrade, Accept Risk, or Use Third-Party Support

Given the EOL status, you have three main paths:

Option 1: Upgrade to a Supported SRM Release

If your environment is compatible, migrating to the latest supported SRM version (e.g., 8.7 or newer) is the cleanest path. However, upgrades can involve downtime, re-testing of recovery plans, and potential fees for new licensing or VMware Subscription licensing.

Option 2: Accept the Risk with Internal Controls

If you choose to stay on SRM 8.6 without any external support, you must formally document the risk. Ensure your team:

• Applies any critical patches that were released before EOL.
• Regularly reviews vulnerability reports for SRM 8.6 and its components.
• Tests failover/failback manually after any infrastructure change.
• Obtains written acceptance from management.

Option 3: Third-Party Support (Recommended for Many Environments)

Third-party maintenance providers — such as 3rd Party Support — specialize in exactly this scenario. They can:

• Deliver custom patches and workarounds for critical bugs and security vulnerabilities in unsupported versions.
• Provide technical support from engineers who know SRM 8.6 intimately.
• Offer support at a fraction of the cost of a vendor renewal or upgrade.
• Help maintain compliance without forcing a disruptive migration.

Third-party support is especially valuable for environments that are stable but need a safety net for security and stability. Many organizations use it as a bridge while they plan a longer-term infrastructure refresh.

Lifecycle Context

SRM 8.6 was not a long-term support (LTS) release. Broadcom’s acquisition of VMware has also shifted support policies and pricing. As a result, many IT teams are re-evaluating their DR strategies. For a full lifecycle reference, see the data from endoflife.date/vmware-srm.

Next Steps for Your SRM 8.6 Deployment

• Inventory your environment – Confirm which version (ideally 8.6.0.2) you are running and what vCenter/ESXi versions it depends on.
• Assess your risk tolerance – If you cannot upgrade by Q1 2026, begin a risk acceptance process or explore third-party support.
• Contact a third-party support provider – Get a quote for maintaining SRM 8.6 safely for another 1–3 years. Talk to 3rd Party Support to see how it works.

VMware Site Recovery Manager 8.6 does not have to be a deadline that forces a costly migration. With the right support model, you can keep it running reliably — even after the vendor has moved on.