Failover VM Remediation

For controller-backed replication targets, Sendense promotes the existing controller-backed target into the recovered VM. It prepares the target in a rollback-aware sequence, applies destination mappings, starts the VM, and records recovery status.

Remediation is focused on bootability, storage access, network reachability, rollback safety, and recovery status reporting. It is not an application migration script.

Not every failover needs the same remediation. If the source and target environments are already compatible, Sendense can skip guest adaptation. If the recovered workload needs to boot on a different virtual hardware profile, Sendense adapts the guest before boot and may run one-time guest remediation after boot.

CloudStack KVM-native replicas can skip guest adaptation when the source and recovery hardware profiles are already compatible.

Before the recovered VM starts, Sendense prepares the target in a rollback-aware sequence.

For Linux VMs that need guest adaptation, Sendense performs storage and boot adaptation before the recovered VM starts. If policy and captured source configuration allow static IPv4 restoration, a one-time first-boot workflow can restore the selected address, gateway, and DNS settings on the live destination adapter, matching the adapter by its live MAC address.

If the source VM used DHCP, if no usable static IPv4 configuration is available, or if the failover policy says to preserve current guest networking, Sendense does not rewrite Linux guest networking. Linux first-boot remediation is non-blocking: if it cannot complete, it records status and the VM boot continues.

For Windows VMs that need guest adaptation, Sendense prepares the recovered root disk for the destination virtual hardware and stages a first-boot remediation workflow. At a high level this can cover driver readiness, disk online behavior, guest management readiness, network restoration where policy allows it, stale adapter cleanup, and status reporting.

Windows remediation uses a staged first-boot and post-reboot model: the first-boot stage installs or schedules the remediation workflow, and the post-reboot stage applies the remaining actions, verifies expected network settings, and reports a final status. Windows network handling supports three modes.

Sendense tracks guest remediation status as part of the failover job. Status can include scheduled, running, succeeded, partial, failed, or awaiting reboot depending on the operating system and remediation phase. Where automatic restoration cannot be completed, the status is marked partial or failed rather than silently claiming success.

Remediation status shows whether boot, network, and guest remediation actions completed. It does not prove the recovered application is healthy; application validation remains an operator step.