Overview
Deprovision and Reprovision are complementary operations that allow users to remove and re-deploy DCT-managed PaaS databases without losing any timeline history. Deprovisioning deletes the running database from the cloud to release compute costs, while all backups, snapshots, bookmarks, and DCT metadata are fully preserved. Reprovision re-deploys the database from any point on the preserved timeline.
Deprovision and Reprovision behave identically across all supported platforms. There are no platform-specific differences in these workflows.
Deprovision
The Deprovision operation deletes a DCT-managed PaaS DB or PaaS Instance from the cloud provider, releasing all associated compute resources. The database is no longer running or accessible at its JDBC endpoint. All automated backups remain in the cloud, and all timeline metadata — snapshots, bookmarks, and history — is fully preserved in DCT. Other accounts can still reference the database’s snapshots and bookmarks to provision or refresh from, and the database can be re-deployed at any time using Reprovision.
When to deprovision
-
After masking is complete and the masked bookmark has been created on a golden copy. The golden copy is no longer needed in an active state, but may need to be re-run in a future masking cycle.
-
After development or testing work is paused and a non-production database will not be used for an extended period.
-
As part of cost optimization workflows — stop databases during off-hours and reprovision on demand.
Steps
-
Navigate to the DCT-managed PaaS DB or PaaS Instance details page.
-
Select Actions > Deprovision from the top-right dropdown.
-
Confirm the operation. The database shuts down and its status changes to Deprovisioned.
Deprovisioning deletes the running database from the cloud but does not remove any backups, snapshots, bookmarks, or DCT metadata. All timeline data is fully preserved and the database can be re-deployed at any time using Reprovision.
After deprovisioning
After a database is deprovisioned, the following applies:
-
Status changes to Deprovisioned in DCT.
-
The database instance is deleted from the cloud provider and is no longer accessible via JDBC.
-
The Timeline tab continues to display the full backup and snapshot history.
-
The Bookmarks tab continues to display all bookmarks.
-
All automated backups are maintained in the cloud. All snapshots and bookmarks remain visible in DCT and are available as restore points.
-
Other accounts can still reference the database’s snapshots and bookmarks to provision or refresh from. The database itself can be re-deployed at any time using Reprovision.
Deprovision vs. Stop vs. Delete
| Deprovision | Stop | Delete |
|---|---|---|
| Deletes the running database from the cloud provider and releases compute resources. | Stops the database but retains the running instance and compute resources in the cloud. | Permanently removes the database from DCT and (optionally) from the cloud provider. |
| Runtime storage released. | Runtime storage maintained. | Runtime storage released. |
| All backups maintained in the cloud; full timeline, snapshots, and bookmarks preserved in DCT. | Timeline, snapshots, and bookmarks are preserved. | All associated data is removed. |
| Database can be re-deployed at any time via Reprovision. | Database can be restarted at any time via Start. | Cannot be undone. |
| Other DCT accounts can still reference snapshots and bookmarks. | Other DCT accounts can still reference snapshots and bookmarks. | Other DCT accounts cannot reference snapshots or bookmarks — these are deleted from the cloud and/or ignored during discovery. |
| Use when the database is not needed for an extended period and compute costs should be eliminated. | Use for short-term pauses where quick restart is needed. | Use when the database is no longer needed. |
Reprovision
The Reprovision operation re-deploys a deprovisioned PaaS DB or PaaS Instance from the cloud provider. Like the Provision and Refresh wizards, the user selects a point-in-time to restore to and DCT creates a new running database instance from that point on the preserved timeline.
Steps
-
Navigate to the deprovisioned PaaS DB or PaaS Instance details page. The status will show as Deprovisioned.
-
Select Actions > Reprovision from the top-right dropdown.
-
Complete the Reprovision wizard as described below.
Select restore point
The Reprovision wizard presents the same point-in-time selection options as the Provision and Refresh wizards:
Latest available point: The most recent point in the preserved timeline, from before the database was deprovisioned.
Latest point-in-time from rolling backup window: If the rolling window is still active.
Specific snapshot: Select a snapshot from the preserved timeline.
Specific bookmark: Select a bookmark, including bookmarks shared from the parent source.
Review and submit
Review the selected restore point and submit. DCT re-deploys the database to the selected point and its status transitions to Running when the operation completes.
Reprovision vs. Start vs. Provision
| Reprovision | Start | Provision |
|---|---|---|
| Re-deploys a previously deprovisioned database from the preserved timeline. | Restarts a stopped database on the same existing instance. | Deploys a brand-new database from a source’s backup, snapshot, or bookmark. |
| Requires a deprovisioned database; resumes from a selected point on its timeline. | Requires a stopped database; resumes from where it was stopped. | Requires a source PaaS DB or PaaS Instance; creates a new child database. |
| Produces a DCT-managed database at the selected point-in-time. | Resumes the existing running state; no point-in-time selection. | Produces a new DCT-managed database. |
| Use to bring back a deprovisioned database after a cost-optimization pause. | Use to resume a short-term pause without data movement. | Use to create a new non-production or golden copy database. |