Sendense Documentation

Recovery & DR Documentation

Recovery points, restore workflows, replication patterns, controllers, and failover.

Documents Home

Product Area

Recovery & DR

Recovery points, restore workflows, replication patterns, controllers, and failover.

Recovery Operations

The recovery workflows for restore, browsing, validation, file recovery, item recovery, and DR failover.

recoveryrestoredr
OverviewReady
Open

Recovery Points

How Sendense represents available points in time for restore, browsing, and recovery workflows.

recovery-pointsebarestore
ConceptReady
Open

Full VM Restore

Recreate a protected virtual machine from an EBA recovery point, to its original location or an alternate platform.

restorevmrecovery
GuideReady
Open

File And Item Recovery

Recover selected files or application items without performing a full VM restore.

file-recoveryitem-recoveryindexing
GuideReady
Open

Recovery Validation And Evidence

The AsureDense suite: checksum validation, boot and mount evidence after backup, interactive boot sessions, and operator attestations.

asuredensevalidationevidenceboot
ConceptReady
Open

Clean Room

Part of the AsureDense suite: an on-demand, isolated recovery validation environment for booting multi-VM groups from recovery points into sealed networks.

clean-roomasuredensevalidationisolation
ConceptReady
Open

Replication Patterns

The policy layer for controller-backed replication and disaster-recovery target readiness.

replicationdrcontrollers
ConceptReady
Open

CloudStack Replication Checkpoints

Why Sendense creates short-lived CloudStack Volume Snapshots before updating controller-backed replica disks, and how to interpret their placement and latency.

cloudstackreplicationcheckpointsvolume-snapshots
ConceptReady
Open

Replication Transport And Routing

How DR replication data moves between sites: the hub-routed path via SHA, the direct site-to-site path, and how routes are chosen.

replicationroutingdrnetworking
ConceptReady
Open

Sendense Controllers

Per-VM DR target appliances used by controller-backed replication patterns.

controllersreplicationfailover
ReferenceReady
Open

DR Failover

How Sendense approaches test, planned, and live failover for controller-backed DR workflows.

failoverdrcontrollers
GuideReady
Open

Failover VM Remediation

What Sendense changes on Linux and Windows VMs during failover, including drivers, networking and guest readiness.

failoverremediationlinuxwindows
ConceptReady
Open

Why was my validation evidence run skipped?

Skipped is deliberate: evidence gives way to real work and follows its configured cadence.

asuredensevalidationevidence
ReferenceReady
Open

What do the Validated and Bootable badges mean?

They answer two different questions: is the stored data intact, and can the recovery point start.

asuredensevalidationrecovery-points
ReferenceReady
Open

How Sendense Selects a Replication Route

The pattern's route policy decides per sync: direct when reachable, via SHA otherwise.

replicationroutingdr
ReferenceReady
Open

Why does my controller show Offline?

Offline means heartbeats are not arriving. Here is what it blocks and where to look.

controllershealthdr
ReferenceReady
Open

Rollback vs failback - what's the difference?

Rollback undoes an uncommitted failover. Failback is a later, planned move back after commit.

failoverrollbackdr
ReferenceReady
Open

Full VM restore vs DR failover - which do I use?

Restore rebuilds from a recovery point. Failover promotes a target that replication kept ready.

restorefailoverrecovery
ReferenceReady
Open

My RPO status shows late - is my data at risk?

RPO status is an operational measurement of sync freshness, not a verdict on existing recovery data.

rporeplicationsync
ReferenceReady
Open