Policy instead of paper plan
The BCM backup plan comes from the actually configured protection policy, not from a document that goes stale.
Protection policies become documented backup plans
The Cohesity connector links your Cohesity cluster to isidaten via the v2 REST API: protection policies, protection groups, their runs and the protected objects flow in automatically. The key step happens in the background: every protection policy becomes a BCM backup plan. So your continuity management no longer describes an intention but the actually configured protection, with no duplicate maintenance.
Vendor: Cohesity · www.cohesity.com
The BCM backup plan comes from the actually configured protection policy, not from a document that goes stale.
Runs and protected objects show what is actually backed up, verifiable for audits and BCM.
The reconciliation only ever touches plans it created itself. Manually maintained backup plans are never overwritten, even if something similar exists in the cluster.
Protected objects add backup status to existing IT systems. The connector deliberately creates no new records; that stays with the inventory scan.
The imported retention period names its source in the text. Even years later it is clear the figure came from the protection policy and not from an estimate.
We show you the connector live in your own environment – non-binding and free of charge.