VMware SRM 8.6 End of Life: 90-Day Action Plan

Act Now: VMware Site Recovery Manager 8.6 End of Life Action Plan (3 Months Out)

VMware Site Recovery Manager 8.6 reaches its official end of life on October 11, 2025 — just over three months from now. With no LTS designation, there will be no extended support window. The clock is already tight, but a panic-free, structured approach can keep your site-recovery environment stable, compliant, and supported past that date.

This article lays out exactly what changes on October 11, what is still achievable in the next 90 days, and a week-by-week checklist to protect your continuity planning.

---

Exactly What Changes on October 11, 2025

After the EOL date, VMware will stop delivering for SRM 8.6:

• Security patches — any new vulnerability in SRM or its dependencies will not be fixed.
• Bug fixes — no more software updates, including the latest build 8.6.0.2.
• Vendor support SLAs — VMware will no longer accept support tickets or provide root-cause analysis for 8.6.
• Compatibility validation — VMware will not test SRM 8.6 against future vSphere releases, patches, or hardware.

Existing software will continue to run, but vendor remediation and SLAs will stop. Any new security risk, interoperability problem, or configuration issue becomes yours to manage independently.

---

What a Full Migration Looks Like — And Why It’s Probably Not Realistic

A full upgrade to the latest SRM release (8.8+) normally requires:

1. Reviewing current SRM 8.6 configurations
2. Identifying all protected VMs and recovery plans
3. Upgrading vCenter Server to a compatible version
4. Upgrading SRM in a staged, tested sequence
5. Re-certifying recovery plans

For most estates, that sequence takes 4–8 weeks of careful planning and staging — with no room for error. If you have not started, a complete, validated migration before October 11 is a high-risk sprint, not a safe project.

Do not try to rush the upgrade. Instead, use the remaining weeks to secure your current environment and arrange coverage for the day after EOL.

---

The 90-Day Action Checklist

Week 1–2: Full Inventory and Risk Assessment

• Identify every SRM 8.6 instance (including all recovery sites).
• Document which protected VMs and recovery plans are critical versus low-priority.
• Check whether any VMs are still running inside the 8.6 protection group that could be moved to a later SRM version without disrupting the rest of the environment.
• Audit n+1 dependencies: vCenter version compatibility, storage replication plugin versions, and any custom scripts or automation tied to the SRM API.

Week 3–4: Isolate and Harden the Remaining 8.6 Environment

Once you know everything that depends on SRM 8.6:

• Restrict network access to the SRM appliances and vCenter instances. Use firewall rules to permit only known management and replication traffic.
• Remove unused protection groups and recovery plans — each reduces attack surface.
• Apply the last available patch — SRM 8.6.0.2 is the final build. Confirm it is installed on all SRM servers.
• Document all workarounds and configuration notes — anything that would not be known to a new admin who takes over after October 11.

Week 5–6: Document Exposure for Auditors and Insurers

Your compliance team and cyber-insurance provider will need a clear record of the planned obsolescence:

• Write an EOL status memo that lists every SRM 8.6 instance, the EOL date, and the known gaps (no vendor patches, no vendor support).
• Note any regulatory or industry deadlines (e.g., PCI DSS, SOX, HIPAA) that require a patched or supported recovery solution. Flag any potential non-compliance window.
• Update your risk register with the exposure period and the compensating controls (isolation, hardening, manual failover procedures).
• Share the memo with your DR partner or internal recovery team — they need to know they cannot lean on VMware support for 8.6 after October 11.

Week 7–10: Line Up a Support Contract for Day One After EOL

By week 10, you should have a signed agreement in place that covers security patches, bug fixes, and vendor-level SLAs for your SRM 8.6 environment after October 11.

• Research third-party support options for VMware SRM. A provider like 3rd Party Support delivers exactly the protections that disappear on EOL day: vulnerability patches, hotfixes, and dedicated response SLAs.
• Confirm coverage includes all SRM 8.6 instances documented in your inventory.
• Negotiate a start date of October 12, 2025 — no gap.
• Sign before October 1 — do not let the deadline slip.

Week 11–12: Test Continuity and Finalise Handover

• Schedule one last recovery-drill with current configurations and the hardened network.
• Confirm the third-party support provider has your asset list and admin contacts.
• Email all stakeholders a one-page summary: what is running on SRM 8.6, the post‑EOL support provider, and who to call for operational or security issues.
• Archive the VMware knowledge base articles relevant to SRM 8.6 — vendor content may be pulled after EOL.

---

After October 11: You Still Have a Working, Supported SRM

Once your third-party support contract is active, the practical effect of EOL is minimal:

• Patches still arrive — your provider will backport critical fixes for SRM and its dependencies.
• Support tickets are still answered — with a typical SLA of 1–4 hours, depending on severity.
• Your DR plan remains stable — no forced re-architecture before you are ready to upgrade on your own timeline.

The three months you have left are enough to document, isolate, and secure your current estate — and to secure professional support for the day after EOL. Start the inventory today.

---

Need immediate coverage for SRM 8.6 after October 11? Contact us today to discuss a smooth transition plan.