Backup software is one of those categories nobody thinks about until something goes wrong. It sits quietly in the background, copying data, until the day a server fails or ransomware locks a file system. So when two big vendors in the space combine, customers have a very practical question: what does this mean for the systems I rely on?
Here’s how to think about a merger between data protection companies, in general terms, and what you can do as a customer.
Why these companies merge
The data protection market has changed. Companies used to protect servers in a single data center. Now data is spread across virtual machines, containers, cloud storage, software-as-a-service apps and edge locations. No single vendor covers everything perfectly, so companies grow by acquiring or combining with others that have complementary products or customer bases.
There’s also a business logic. Backup customers rarely switch quickly, so installed base is valuable. Combining two bases can create scale for sales, support and research.
The three layers of integration
Integration after a merger doesn’t happen all at once. It usually unfolds in three layers.
- Corporate: Leadership, finance, legal entities and sales organizations come together first. Customers often see this as a new logo and new contacts.
- Go-to-market: Product lines get repackaged, pricing is harmonized, and partners learn how to sell the combined offering.
- Technology: This is the slowest part. Engineering teams decide which products continue, which merge and which are retired.
True technical integration, such as a single console or a unified storage format, can take years. Meanwhile, the existing products need to keep working.
The product roadmap question
When two products overlap, the new company has a decision to make. Options include keeping both for a long time, combining the best features into one, or sunsetting one over a defined period. Companies often promise continued support for existing products, with end-of-life dates announced well in advance. Ask for those commitments in writing.
Watch for clues in how a vendor describes the plan. Vague language about synergies is not a roadmap. Specific release dates, migration tools and support timelines are.
What customers should do now
- Inventory your setup. Know which products, versions, and integrations you depend on.
- Ask about support terms. Confirm how long your current version stays supported and what the upgrade path is.
- Review your contract. Look at renewal dates, pricing protections and clauses about change of control.
- Test your restores. Regardless of vendor news, regularly prove that you can actually recover data.
- Watch the partners. Resellers and cloud providers integrate with backup tools, and compatibility changes may ripple through them.
Risks during integration
Mergers create distraction. Engineers may leave, support quality may dip, and product bugs can linger while teams are reorganized. Pricing changes sometimes follow as the company seeks to recoup the deal cost. This is not a prediction for any particular company, just a pattern customers have seen before. A little caution protects you.
Security is another consideration. Combining networks, identity systems and product code introduces new attack surfaces. Backup systems are prime targets for ransomware attackers because they hold the safety net. Make sure your own backup environment is hardened, with immutable copies, separate credentials and offline or air-gapped options.
The opportunity side
Mergers can also bring real benefits. A broader product line may cover workloads that once needed two vendors. Scale can fund investment in cyber recovery features, such as anomaly detection that spots unusual changes in backup data, which may hint at an attack. Support coverage can expand into new regions.
A sensible stance
Treat a vendor merger like any major change in your supply chain. Don’t panic, don’t ignore it. Ask questions, document the answers and keep your options open. If the plans are clear and the products are well supported, there may be little reason to change anything. If not, start evaluating alternatives early, when you have time to migrate calmly.
The takeaway
Backups are a promise that your data can come back. A merger shouldn’t weaken that promise, but it’s your job to check. Get the roadmap, confirm support terms and keep testing recovery. The best backup strategy is one you have proved works, whoever is selling it.
Featured image: BalticServers data center.jpg by BalticServers.com, CC BY-SA 3.0, via Wikimedia Commons.
