This page describes how to manually recover a SQL Server database after the Virtual-to-Physical (V2P) process. V2P operations are initiated through DCT, which transfers virtual database files to physical storage in a target environment. After the export is complete, manual recovery steps may be required on the target host.

If you want to skip automatic database recovery, use one of the following options:

  • While running V2P from DCT UI, uncheck the Open Database After Recovery checkbox.

  • While running V2P from DCT CLI, set recover_database=false.

Once either of the above options is applied, run the Provision.ps1 script to complete the recovery manually.

Procedure

  1. In the V2P target environment, navigate to the scripts directory for the exported SQL Server database instance. You can find the scripts in a sub-directory named for that specific database instance.

    • The scripts are placed in the directory that you specified in the Script Directory field during V2P configuration.

    • If you left the Script Directory field blank, all scripts will be present directly in <target_directory>.

  2. Once you have located the directory, run the Provision.ps1 script. The executing user must have the sysadmin server role, as operations such as database restore, file renaming, and recovery mode switching require server-level privileges in SQL Server.

  3. When the script completes, refresh the target environment in DCT (Home > Infrastructure Connections) for it to discover the recovered database.

Last updated
Oct 8, 2026