After a failover completes, the target CD engine assumes ownership of the replicated environments, dSources, and VDBs. Before these objects can resume normal operations, connector-specific recovery steps are required on the target and staging hosts. These steps address stale NFS mounts, orphaned database processes, and other artifacts left behind by the former source engine.

General recovery workflow

Regardless of the data platform, the high-level recovery sequence after an uncontrolled failover follows the same pattern:

  1. Clean up stale mounts and processes on target/staging hosts. The former source engine's NFS mounts and any orphaned database processes must be removed before enabling objects on the target engine. The exact commands and paths vary by operating system and data platform — refer to the Oracle, SAP ASE, and SQL Server for connector-specific cleanup procedures.

  2. Enable environments in DCT. Navigate to Home > Infrastructure Connections and enable source environments first, then target/staging environments.

  3. Enable dSources and VDBs in DCT. Navigate to Data > Data Management > dSources and Data > Data Management > VDBs to enable each object. Enable dSources before VDBs. For plugins, verify that the required plugin is active on the target engine at a compatible version before enabling.

  4. Validate operations. After enabling, confirm that sync, refresh, and rewind operations complete successfully on the recovered objects.

Platform-specific recovery procedures

Each data platform has unique cleanup requirements for stale mounts, database processes, and staging artifacts. For detailed, step-by-step recovery instructions specific to your connector, refer to the Connector-specific documentation below in DCT:

  • Oracle: See the Oracle environments and data sources documentation for instructions on shutting down VDBs/vCDBs, killing stale Oracle processes, removing NFS mounts, and restarting linked CDBs after failover.

  • SQL Server: See the SQL Server environments and data sources documentation for instructions on clearing staging database mounts, deleting stale VDB directories, and recovering failover cluster targets.

  • SAP ASE: See the SAP ASE environments and data sources documentation for instructions on unmounting stale NFS shares from staging and target hosts and restarting SAP ASE instances.

  • Other connectors: Refer to the appropriate connector documentation in the Ecosystem Hub for connector-specific failover recovery steps.

Related topics

 

Last updated
Oct 14, 2026