Backup Exec end of support: April 29, 2029, and your plan

Backup Exec — still widely called Veritas Backup Exec, though Arctera is the company that publishes its support documentation today — now has a published outer limit on how long it will be maintained. Arctera's own Maintenance Documentation (a PDF created January 21, 2026, and still published as of September 26, 2026) states it plainly: Please note that all Backup Exec Products will reach End of Support Life no later than April 29, 2029, after which no Maintenance of any kind is available. So if you're searching for the Backup Exec end-of-life date, this is the closest thing to it: Arctera's term is "End of Support Life," not "end of life," and April 29, 2029 is a ceiling, not a guarantee. If your organization still runs Backup Exec, System Recovery, or Desktop Laptop Option, that sentence is the one to plan around — and the phrase "no later than" carries as much weight as the date itself.

What Arctera's documentation actually says

The Maintenance Documentation opens by naming exactly what it covers: Backup Exec Products (Backup Exec, System Recovery, and Desktop Laptop Option). It lists five possible Maintenance offerings — Basic Maintenance, Essential Support, Verified Support, Extended Software Support, and Sustaining Software Support — and states that all of them run "in accordance with the Technical Support Policy, Product Life Cycle Policy, and other support policies which may be revised and updated by Company from time to time without notice to Customer." Then comes the ceiling quoted above.

The words "no later than" do real work here. One sentence earlier, the same document states the general rule those Maintenance tiers already operate under: Under the Product Life Cycle Policy, Maintenance may be discontinued for certain Products or a particular version of a Product prior to the end date of the term purchased. April 29, 2029 is the latest possible date support ends for any Backup Exec product — it isn't a guarantee that your specific version, on your specific purchased term, is covered all the way to it. If you're on an older release or a shorter renewal term, the practical end-of-support date could land well before 2029. The task isn't "note 2029 on the calendar" — it's "confirm what your current version and Order actually say," against the Product Life Cycle Policy this document references.

What "no maintenance of any kind" means — and what you get before that date

Arctera's documentation is specific about what "technical assistance" under any Maintenance offering does and doesn't include: it is limited to error correction resolution of Product used in a Supported Configuration, and does not include services such as training, installation, migration, implementation, and configuration services. That matters regardless of where you sit on the timeline: even a fully supported Backup Exec license doesn't come with migration or implementation help built in. Planning work — inventorying what you protect, designing a transition, validating restores — has always been separate from a maintenance contract, and it's worth budgeting as its own line item now.

For organizations on older versions already relying on Sustaining Software Support (SSS), the document draws a narrower boundary than a fully active tier: SSS provides, on a commercially reasonable basis, only Provision solely of known fixes, patches, workarounds, existing maintenance packs, or information from Company's technical knowledge base — alongside continued access to technical support and the support website. That's fixes that already exist, not a commitment to develop new ones for a problem nobody's seen before. And SSS carries its own hard stop, independent of the 2029 ceiling: SSS is provided until the end date of the term purchased as noted in Customer's Order unless any of the Product reaches its End of Support Life. In such event, Company will provide no further Maintenance for such affected Product. After April 29, 2029, none of that survives for any Backup Exec product — the document is unambiguous that "no Maintenance of any kind" applies past that date, for every tier at once.

The part people miss: your old backups outlive the product

Most of the planning conversation around an end-of-support date focuses on whether the software keeps getting patched. A quieter question matters just as much: can you still restore a three-year-old, five-year-old, or seven-year-old backup set once maintenance has ended entirely? Regulated organizations — healthcare practices, government contractors, manufacturers under contractual retention terms — often carry retention obligations that run longer than any single backup product's support lifecycle. Arctera's Maintenance Documentation says nothing about retention directly, and we're not citing a specific regulation's retention period here; that's a question for whatever compliance framework or contract actually governs your data.

What does need a decision before 2029, not after it, is how you'll read a Backup Exec backup set or catalog once no maintenance is available at all. A few approaches worth weighing, roughly in order of how far each one moves you off the product itself:

• Keep a restore-capable Backup Exec instance — an isolated media server kept alive specifically to read old backup sets and catalogs, even after you've stopped relying on it day to day.
• Restore what you must keep, and re-protect it elsewhere. For data with a retention requirement but no ongoing operational need, pull it out of Backup Exec's format and re-protect it on whatever platform you're standardizing on, rather than leaving it dependent on a product with no support behind it.
• Document the chain. Which backup sets exist, where the media lives, and which catalog and media-server version can read them — written down now, not reconstructed under pressure during an audit or a legal hold.

A migration plan that starts with inventory, not a product decision

We don't resell backup software, so we're not going to tell you what to replace Backup Exec with, or whether to replace it at all — some organizations on a current version and a comfortable renewal term may reasonably choose to stay put for now. What we do recommend, on any timeline, is the same sequence for any end-of-support planning:

• Inventory what Backup Exec actually protects today — physical servers, virtual machines, Microsoft 365 mailboxes or sites if you're protecting them through Backup Exec, System Recovery images, and Desktop Laptop Option endpoints. Most organizations find this list is longer, and less current, than whoever set it up originally documented.
• Decide per workload, not all at once. A file server, a line-of-business database, and a fleet of laptops under Desktop Laptop Option don't necessarily belong on the same decision or the same timeline.
• Run parallel protection for a defined period before retiring anything — both the old and new protection covering the same workload, so a gap in one doesn't become data loss before the other is proven.
• Prove every replacement with an actual test restore before you trust it, exactly the standard we lay out in a companion post on restore testing for regulated environments. A backup job reporting success and a restore that actually works are different facts, on any platform.

If Backup Exec is protecting Microsoft 365 mailboxes or SharePoint/OneDrive content specifically, that data has its own considerations worth reading separately — what Microsoft itself backs up by default, what a Microsoft 365 backup product covers, and where the gaps are — in our companion post on Microsoft 365 backup: what Microsoft covers, and what you do.

Why 2029 eats faster than it sounds

April 29, 2029 is more than two and a half years out from this post, and it's easy to file that under "later." A few ordinary cycles shrink that runway faster than it looks:

• Your renewal term may end well before 2029. The document's own warning applies here — maintenance can be discontinued for your specific version before your purchased term runs out, so the next renewal is the right place to ask what your coverage looks like against this ceiling.
• Budgeting cycles run annually, not on Arctera's schedule. A migration or a new platform needing capital or a signed contract has to land inside a budget cycle well before the deadline it's meant to beat.
• A proper parallel-run period takes months, not days — long enough to cover a normal backup and restore cycle for every workload involved.

Put a sensible sequence on it — inventory, decide, budget, run parallel, test-restore, retire — and working backward from 2029 leaves less room than the date by itself suggests.

Where we fit

We don't resell backup software, Backup Exec's or anyone else's. Whether you stay on a current, supported version, move to a different platform, or run both in parallel during a transition, we help with the inventory, the migration design, the parallel-run validation, and the test-restore proof — on whatever platform you choose. No margin either direction, and no product to sell you.

Sources

• Arctera — Backup Exec Maintenance Documentation (PDF, created January 21, 2026; retrieved September 26, 2026)

The 30-second version

Arctera's own Maintenance Documentation sets April 29, 2029 as the latest date Backup Exec, System Recovery, and Desktop Laptop Option can remain under support — "no later than," meaning your specific version or renewal term could lose maintenance sooner, per the document's own Product Life Cycle Policy language. Before that date, coverage depends on your tier; Sustaining Software Support specifically provides only known fixes, patches, and existing knowledge-base guidance, not new development. After that date, the document states plainly that no maintenance of any kind remains, for any tier. What the documentation doesn't say: whether the software stops running, or when sales actually end — we haven't found either claim in Arctera's own materials, so we're not asserting them. What it does leave you to plan: how you'll restore backup sets and catalogs years after support ends, which for regulated organizations with real retention obligations is the harder problem. Inventory what you protect today, decide per workload, run parallel, and prove every replacement with a test restore before you trust it.

If you want a senior engineer to help inventory what Backup Exec protects today and plan the migration path, the project intake form takes about three minutes. We'll come back with scope and a fixed-fee range.

Pro IT NW helps regulated mid-market organizations design, implement, and test backup and disaster recovery for Microsoft 365, Azure, AWS, on-premises, and hybrid environments. Vendor-neutral, labor-only — we don't resell backup software. This post reflects Arctera's Backup Exec Maintenance Documentation as read on September 26, 2026.