NetBackup 5240 Support Ended: What to Do Now

Official support for the NetBackup 5240 Appliance ended on October 31, 2025. If you are still running 5240 units in August 2026, third-party maintenance can be useful for parts and break-fix coverage, but it should be treated as a bridge while you plan a supported replacement, not as a full substitute for vendor lifecycle support.

That is the context behind a small but very practical administrator question. The environment had several 5240 appliances being used as media servers to write to Data Domain. The units were small, around 5 TB, and the team wanted to know what others paid for third-party support and which providers they trusted. The discussion produced spare-hardware jokes, but no usable market price.

Is the NetBackup 5240 still officially supported?

No. The Veritas support site published an explicit notice that support for the NetBackup 5240 Appliance would end on October 31, 2025. That date has passed.

This changes the risk discussion. Before the cutoff, an appliance problem could be evaluated within the vendor's supported hardware and software lifecycle. After the cutoff, even a functioning unit sits outside the normal support boundary for that platform generation.

Do not confuse “it still boots” with “it is supported.” Enterprise backup infrastructure often runs for years after hardware refresh cycles because the workload is stable and nobody wants to disturb it. That can be rational for a short period, but the risk increases when spare parts, firmware qualification, operating system fixes, and new NetBackup releases move on without the appliance.

The NetBackup and Nutanix compatibility article shows how quickly a backup platform can become the limiting layer when another part of the infrastructure upgrades.

What can third-party hardware support actually cover?

Third-party maintenance can be valuable for physical failures. Depending on the provider and contract, it may include replacement disks, power supplies, controllers, memory, onsite technicians, remote diagnostics, and a response-time commitment.

That is useful if the 5240's role is simple and stable. In the source case, the appliances were being used as media servers writing to Data Domain, so keeping the hardware alive may look cheaper than replacing a platform that is not providing much local capacity.

But hardware maintenance does not automatically restore the software lifecycle. A third-party provider cannot make an old appliance qualified for a newer NetBackup release just by replacing a failed component. It also cannot guarantee vendor fixes for the hardened appliance operating system or new interoperability issues.

Ask every provider to separate hardware break-fix coverage from software and firmware support in writing. “We support the appliance” can mean very different things.

Why is support pricing hard to compare?

Because the service being purchased is not one standard product. A next-business-day parts contract for one appliance is different from four-hour onsite service with stocked local spares across multiple countries.

The Reddit question asked what other administrators were paying, but the replies did not provide a meaningful benchmark. One person mentioned six 5240s being decommissioned and joked about sending them for parts. That says more about lifecycle stage than price.

When collecting quotes, normalize the scope. Compare response time, onsite labor, parts included, shipping, geographic coverage, after-hours service, escalation process, supported component list, and whether the provider keeps local inventory for the exact 5240 hardware.

Then compare the annual maintenance spend with the cost of migration. A cheap support contract can still be expensive if it delays a necessary platform move for another two years.

What risks remain even with replacement parts available?

Security and compatibility are the biggest gaps. The appliance generation depends on an operating system, firmware stack, drivers, and NetBackup versions that have their own support windows. A third-party disk or controller replacement does not solve a vulnerability that requires a vendor software update.

Compatibility pressure often arrives from outside the appliance. A Data Domain upgrade, network change, authentication policy, new NetBackup primary server, or application requirement can force the media server to support a newer protocol or software level.

That is why old backup appliances are deceptive. They can run perfectly for months and then become the blocker in an unrelated upgrade project.

Document the highest NetBackup release the current 5240 deployment can support, the versions of Data Domain and any transport components it depends on, and the next infrastructure upgrades already planned. That timeline tells you whether third-party maintenance is buying useful time or simply postponing a collision.

Should a small 5 TB 5240 be replaced even if Data Domain stores the data?

The decision should be based on the role, not the local capacity number. A media server can be operationally critical even if most protected data is written elsewhere.

If the 5240 handles backup traffic, deduplication integration, tape or Data Domain communication, catalog related workflows, or recovery data paths, its failure can still interrupt protection and restore operations. Five terabytes of local capacity does not mean five terabytes of business impact.

Map what happens if one 5240 disappears today. Which policies fail? Can another media server take over? Are storage units shared? Are credentials and certificates portable? How long does it take to rebuild the media role on supported hardware?

If the environment already has enough supported media capacity to absorb the workload, the cleanest answer may be to remove the 5240 rather than maintain it.

What should be tested before decommissioning a 5240?

Test the recovery path before removing the appliance. Backup migration projects often focus on getting new jobs to run and forget that old backup images may still be associated with storage or media-server paths needed during restore.

Inventory policies, storage units, disk pools, Data Domain relationships, SLPs, credentials, certificates, tape devices if any, and any backup images whose recovery depends on the old media server. Then prove that representative restores work through the replacement path.

If the 5240 has local backup data, plan how those images will expire, duplicate, import, or migrate according to the supported NetBackup workflow. If it is only a media path to Data Domain, verify that another supported media server can access the required storage and recover existing images.

The recovery-first thinking in the Proxmox backup strategy guide applies here too. A migration is complete only when restores work from the new path.

When does third-party maintenance make sense?

It makes sense when you have a defined short-term bridge, a stable workload, no immediate compatibility requirement, and a credible migration date. It can also make sense when a replacement project is already approved but hardware delivery or change windows push the cutover several months out.

In that situation, buy the level of service that protects the bridge period. If a failed controller would stop backups for a week without stocked parts, cheap mail-in coverage is probably the wrong contract.

Third-party maintenance makes less sense when the appliance is already blocking software upgrades, security remediation, or infrastructure changes. Paying to keep unsupported hardware alive does not solve those constraints.

Set an exit date in the same document that approves the maintenance contract. Otherwise a one-year bridge can quietly become a three-year operating model.

What would I do with 5240 media servers in 2026?

I would treat the October 31, 2025 support end as the decision point and build a replacement plan now. For any 5240 that must remain online during migration, I would obtain third-party hardware coverage with clearly defined parts and response times, but I would not describe that platform as fully supported.

Next I would test whether supported NetBackup media-server infrastructure can take over the Data Domain workload, including restores of existing images. If it can, I would retire the smallest and least critical 5240 first and use that migration to validate the runbook for the remaining units.

The Reddit thread does not provide a trustworthy price target, so chasing an arbitrary dollar figure would be false precision. The better comparison is annual maintenance cost plus lifecycle risk versus the cost of moving a critical backup role onto supported hardware.