VMware SRM 8.8 EOL October 2025: Third-Party Support

End of Life for VMware Site Recovery Manager 8.8: October 11, 2025

As of October 11, 2025, VMware Site Recovery Manager (SRM) version 8.8 has reached end of life (EOL). This means active support from VMware, including security patches, bug fixes, and technical support, has ceased. This version is not a long-term support (LTS) release, and the latest available build in this line is 8.8.0.3.

If your organization is still running SRM 8.8, this is a critical milestone. The product does not stop working immediately, but the terms of support change significantly. This article explains exactly what end of life means for SRM 8.8, what keeps working, and what stops, as well as the practical risks and options — including how third-party support can help you keep the environment safe after the vendor's deadline.

What End of Life Means in Practice for SRM 8.8

End of life for SRM 8.8 means:

• No new patches or hotfixes — VMware will not release security updates or bug fixes for this version. Any vulnerabilities discovered after October 11, 2025 will remain unpatched.
• No technical support — VMware's support team will no longer take tickets or provide troubleshooting for SRM 8.8. Your incident response window shrinks to zero.
• No compatibility guarantees — Future updates to vCenter Server, ESXi, or other VMware components may break SRM 8.8. VMware will not test or certify new releases against an EOL version.

What keeps working: The application continues to run as-is. Existing recovery plans, replication schedules, and site failover/failback operations will function normally, provided underlying infrastructure remains unchanged. However, once you upgrade vCenter, ESXi, or storage arrays, SRM 8.8 may become incompatible.

The Real Risks of Running Unsupported SRM

1. Security vulnerabilities — Without patches, known CVEs can be exploited. Recovery managers are a high-value target for ransomware because they control failover and replication. An unpatched SRM instance is a soft spot in your disaster recovery posture.
2. Unplanned outages — If a bug surfaces in SRM 8.8 after EOL, there is no vendor fix. You will have to re-architect your DR solution or perform a risky, unplanned upgrade.
3. Compliance gaps — Many regulatory frameworks (SOC 2, PCI DSS, HIPAA) require vendors to provide security patches during the lifecycle. Running EOL software can trigger audit findings.
4. License and support liability — If you still hold active VMware support contracts for SRM 8.8, those contracts expire at EOL. Renewing a support contract for an EOL product is not possible.

Who Might Still Be Running SRM 8.8?

Several legitimate scenarios explain why an organization remains on this version:

• Stable, unmodified workloads — If your DR environment is stable and requires no changes, the risk of upgrading may outweigh the benefit.
• Locked application dependencies — Some line-of-business applications may require a specific version of vCenter or a VMware API that only SRM 8.8 supports. Upgrading SRM would force an application re-certification cycle.
• Hardware constraints — Older server hardware or unsupported storage arrays may prevent you from upgrading to a later SRM version that requires newer drivers or firmware.
• Budget timing — The upgrade project may be scheduled for next fiscal year. EOL caught you mid-plan.

In any of these cases, continuing to run SRM 8.8 is a calculated decision — not a sign of neglect.

How Third-Party Support Keeps SRM 8.8 Running Safely

Once vendor support ends, third-party maintenance (TPM) providers like 3rd Party Support can fill the gap. Here is what that looks like:

• Security patches — Experienced TPM engineers can backport fixes from later SRM versions or develop custom patches for vulnerabilities found in 8.8.
• Bug fix support — If a crash or regression occurs, TPM can provide workarounds or code-level fixes.
• Configuration and deployment assistance — Help with tuning, replication optimization, or troubleshooting without forcing an upgrade.
• Cost savings — TPM is typically 40–60% lower than the last VMware renewal, and no forced migration to a newer version.

Third-party support does not restore full VMware compatibility — it keeps your existing, stable deployment secure and functional. For many organizations, that is the right trade-off.

Planning Your Next Step

If you are still on SRM 8.8, your options are:

1. Upgrade to a supported SRM version — VMware's current release (SRM 9.x) is fully supported. This requires upgrading vCenter and possibly ESXi, and testing all recovery plans.
2. Migrate to native DR tools — vSphere Replication or third-party DR orchestrators (Zerto, Commvault, Rubrik) may be a better fit long-term.
3. Stay on 8.8 with third-party support — If the upgrade is impractical, TPM keeps your environment patched and supported without a forklift move.

For more details on third-party maintenance for VMware products, visit our VMware software page or contact us directly.