AIOps is so powerful, vendors are building tools to clean up after agents break your infrastructure
- Reference: 1773185489
- News link: https://www.theregister.co.uk/2026/03/10/agentic_ai_rollback_recovery_cohesity/
- Source link:
The three companies believe that enterprises will use agentic AI to operate some of their systems – a practise often called "AIOps" – but also expect the software could botch the job or fall victim to malicious attacks. They therefore think organizations will need tools to recover from errors introduced by AI.
Users could of course wait for the market to mature so AI is less likely to make mistakes that need to be rolled back, and less susceptible to attack. Vendors aren’t making such caution easy, by adding agentic automation to their products – often in the form of tools that diagnose problems and then offer to fix them.
[1]
Cohesity [2]plans to deliver the product before the end of the year. When it reaches the market, Cohesity will find itself in competition with Rubrik, which [3]introduced a similar tool in August 2025, and native rollback capabilities that the likes of Cisco have built into their agentic tools.
[4]
There may be room for many players in this market, as analyst firm Gartner [5]predicts up to 40 percent of enterprise applications will include integrated task-specific agents in 2026, up from less than five percent in 2025.
Rival analyst firm Forrester has [6]warned that preventing agentic AI problems in the enterprise requires developers of agents to include guardrails, identity and access management controls, and strong oversight.
[7]Heterogeneous stacks, ransomware, and ITaaS: A DR nightmare
[8]Brace yourselves, Backup Exec and InfoScale users, Cloud Software Group just acquired your tools
[9]From A2A to MCP, a look at the protocols that might one day help AI automate you out of a job
[10]Paradox: Agentic AI dev roles are less in demand as agents take over
Cohesity says it addresses the risks agents pose by preserving immutable snapshots of AI environments and it allows for point-in-time recovery of agents, data, and supporting infrastructure, including files, databases, object storage, SaaS applications, vector stores, and agent memory, the company said.
ServiceNow and Datadog are helping Cohesity by providing control and observability platforms that monitor for anomalies. If the vendors’ tools spot a problem, Cohesity’s tools can trigger API-driven restorations across an IT estate, recovering AI agents and agent memory, vector databases, model configurations, training and fine tuning data, and enterprise data stores. ®
Get our [11]Tech Resources
[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2abD29farXwg7FsjCV5rpqQAAAIA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[2] https://www.cohesity.com/newsroom/press/cohesity-launches-enterprise-ai-resilience-strategy-power-and-protect-ai-initiatives/
[3] https://www.blocksandfiles.com/data-management/2025/08/12/rubrik-adds-rogue-ai-agent-action-rewind-protection/1604985
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44abD29farXwg7FsjCV5rpqQAAAIA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025#
[6] https://www.forrester.com/blogs/predictions-2026-cybersecurity-and-risk/
[7] https://www.theregister.com/2025/04/03/heterogeneity_itaas_ransomware_disaster_recovery/
[8] https://www.theregister.com/2025/08/06/cloud_software_group_acquires_arctera/
[9] https://www.theregister.com/2025/07/12/ai_agent_protocols_mcp_a2a/
[10] https://www.theregister.com/2025/11/03/demand_for_software_skills_ai_jobs/
[11] https://whitepapers.theregister.com/
Most fast breaks things
And after we break it, pay us to fix it!
SUCKERS!
Free tip
"AiOps" is "Click-Ops".
Agents are not IaC. If you are not IaC, then change-controlling your infrastructure, auditing your infrastructure, previewing- and reviewing- deployments, all the things that are done with Kubernetes and TerraFright, are not available to you.
It's one thing to have LLMs writing your IaC code (has anyone managed to do that successfully?), but it's quite another to have Agents just *doing stuff*. You'll probably never even be able to get it to do the same thing twice, it's almost irreproduceable
Oh my dog
Worst ideas ever! It's like their goal is to make sure the AI (so-called) keeps running forever, and can right replay its mayhem on our machinery, ad infinitum ... restoring it from deadly crashes, so it effectively ' lives ' perpetually, until you blast the darn zombie hardware full of physical bullet holes, just to stop it!
I mean, ' preserving immutable snapshots of AI environments ' and ' recovering AI agents and agent memory ' DOES NOT address ' the risks agents pose ' AT ALL , not one bit, it just plain compounds them. What's needed instead is to park the agents, delete the agents, purge all agents and AI from the system, and deep, with multipass secure erasure, rubbing alcohol, bleach, fire!
They got it so wrong, so completely backwards, it's not even funny. Where's their tool to de-exfiltrate our PII that's been stolen by the agentic cabal of zero-click usurpers? Where's their Service to Explode and Nuke the computers of those folks who surreptitiously OpenClaw company secrets out of our files and databases, with our full non-consensual consent and FOMO enthusiasm (EaNaaS)? How much are they paid by the RotM to peddle this sham of a recoverability theater, that only recovers, you guessed it, the RotM itself?! Inquisition minds ... ;(
And people wonder why ...
... real, honest to gawd/ess computer professionals want nothing to do with the current state of so-called "AI".
Why do we have write-only databases but not write-only AI? Why do we let LLMs run "rm -rf /"? What am I missing here?