Repave

Delphix continues developing solutions to mitigate potential risks as new security vulnerabilities rise. You use Repave to move engine state to a fresh target engine without carrying over compromised binaries. For block engines, you detach storage devices from the source VM and attach them to the target VM before you apply repave. For Elastic Data engines, you reuse the same object storage location and provide required apply parameters. The target engine then behaves like the source engine. Repave protects engine configuration and metadata, and does not protect or recover underlying source database data in dSources or VDBs.

Choose a repave workflow

Use this section to select the workflow that matches your situation before you run repave APIs.

• Planned repave workflow (controlled): Use this workflow when the source engine is healthy and reachable. You run repave/prepare on the source engine, then run repave/apply on the target engine.

  • For block engines, start with Repave block storage engines.

  • For Elastic Data engines, start with Repave Elastic Data engines.

• Disaster recovery repave workflow: Use this workflow when you restore engine configuration and metadata from captured snapshots after a failure scenario. You run repave APIs on the target engine and do not run repave/prepare as part of this workflow.

  • Start with Repave for disaster recovery.

This section includes the following topics: