Checkpoints & Rollbacks

Migrations carry inherent risk. Even with the best pre-flight checks, unexpected issues can emerge after a migration appears to have completed successfully — a subtle configuration mismatch, a caching inconsistency, or an edge case in your application that only surfaces under real traffic.

RasnuOS's Migration Engine is designed around the assumption that things can go wrong after a cutover, and provides a structured safety net to handle it.

Automated Checkpoints

Throughout the execution of a Migration Plan, the Control Plane automatically records checkpoints at critical state boundaries.

A checkpoint captures the exact operational state of both the source and target server at that moment in time: which steps have completed, what data has been transferred, and where the DNS is currently pointing.

If a step fails during execution, the system does not need to restart the entire migration from scratch. It can resume from the last successful checkpoint, re-running only the steps that did not complete.

Post-Cutover Monitoring

Immediately after the DNS cutover, the Migration Engine does not simply close the migration and move on. It enters an active post-cutover monitoring window where it continues watching the target server's health checks and error rates.

If the target server begins returning a high rate of application errors shortly after the cutover — suggesting that the migration introduced a problem — the system surfaces this immediately in the dashboard with a clear warning.

1-Click Rollback

If you determine that the new server is not behaving correctly and you need to revert immediately, you can execute a 1-Click Rollback from the migration dashboard.

The rollback is structured and safe:

1. The DNS records are instantly swapped back to the original source server's IP address.
2. Traffic immediately begins flowing to the original server, which has been kept live during the Grace Period precisely for this scenario.
3. The failed migration plan is marked as rolled back with a complete audit trail — including every step that ran, what the outcome was, and when the rollback was initiated.

This gives you a meaningful safety net to make migration decisions under real traffic conditions, rather than having to predict every possible failure scenario in advance.