VMware SRM 8.6 EOL Oct 2025 – Options

Introduction

VMware Site Recovery Manager (SRM) 8.6 reaches end of life on October 11, 2025. With roughly nine months remaining, infrastructure teams must decide on a path forward. Three realistic options exist: upgrade to a supported release, purchase vendor extended support (if available), or transition to third-party maintenance. This article compares each option across cost, risk, timeline, and suitability for different workload profiles. (See the VMware software page for more details.)

Option 1: Upgrade or Migrate to a Supported Version

• Cost: Requires a license upgrade or new subscription, plus migration effort. May involve hardware or software dependencies.
• Risk: Migration carries technical risk, but results in a fully supported environment. Thorough testing is essential.
• Timeline: Nine months is sufficient for planning and execution if resources are allocated.
• Suitability: Best for environments under active development or where new features are needed. SRM 8.6 is not an LTS release, so moving to a later version (e.g., 8.7 or 8.8) is the natural upgrade path.

Option 2: Vendor Extended Support (if available)

• Cost: Typically premium pricing over standard support. May be offered for a limited duration.
• Risk: Provides continued security patches and technical support, but no new features. Eligibility criteria may apply.
• Timeline: Must be arranged before the end-of-life date. Check with VMware or your account team.
• Suitability: Suitable for environments that are stable but require compliance or vendor backing for a short extension (e.g., 6–12 months).

Option 3: Third-Party Support

• Cost: Often lower than vendor extended support. Predictable, multi-year contracts avoid budget surprises.
• Risk: Third-party support can provide security patches and break-fix support without requiring a migration. No vendor feature updates, but for stable configurations that is rarely a concern.
• Timeline: Can be implemented immediately, avoiding disruption to existing operations.
• Suitability: Ideal for stable, static workloads that need to remain on the current version for years. Especially useful if upgrading would force expensive hardware or software changes.

Decision Checklist

• Is your SRM environment undergoing active development or feature requests? → Upgrade.
• Do you need to maintain compliance with vendor support for a short period? → Consider vendor extended support if available.
• Are you running a stable disaster recovery configuration with no planned changes? → Third-party support is a strong option.
• Do you have budget constraints or want to avoid a costly migration? → Third-party support can offer cost savings.
• Is your current SRM 8.6 deployment tightly integrated with other unsupported versions? → Third-party support may extend the life of the entire stack.

Conclusion

Nine months is adequate time to evaluate and execute any of these paths. For many organizations, third-party support provides a low-risk, cost-effective way to keep VMware Site Recovery Manager 8.6 running safely past its end-of-life date. To learn more about how third-party support can fit your environment, contact us.