Overview
The Refresh operation restores an existing DCT-managed PaaS DB or PaaS Instance to a selected point in time. Unlike Provision, which creates a new database, Refresh is an in-place operation that moves the existing database to the specified point.
Refresh is only available on DCT-managed PaaS DBs and PaaS Instances. It is not available on Root Source (production) databases or discovered (unmanaged) databases.
Refresh sources
In this release, a PaaS DB can be refreshed from the following sources:
-
Refresh from parent: Restores the database to a point in time from its parent source (the Root Source or golden copy it was originally provisioned from). Used to pull fresher data from the production chain.
-
Refresh from self: Restores the database to an earlier point within its own timeline. Used to revert a database to a previous state without re-provisioning.
-
Refresh from shared bookmark: Restores the database to a point referenced by a bookmark shared from another PaaS DB or Instance. The bookmark must be Public and share the same root source.
Sibling-to-sibling refresh (refreshing one non-production database directly from another) is not supported in this release, except via shared bookmarks.
Steps to refresh
-
Navigate to the DCT-managed PaaS DB or PaaS Instance details page.
-
Select the Refresh button, located next to the Actions dropdown in the top right of the details page.
-
Complete the Refresh wizard as described below.
Select restore point
Select the source and point in time for the refresh. The following options are presented:
-
Latest backup: Restores to the most recent automated backup from the parent source.
-
Latest point-in-time: Restores to the most recent point within the rolling backup window, typically within the last few minutes.
-
Specific snapshot: Select a specific snapshot from the timeline.
-
Specific bookmark: Select a bookmark from this database's Bookmarks tab, including shared bookmarks from other sources.
Review and submit
Review the selected restore point and target database. Select Refresh to submit the operation.
Refresh vs. Provision
| Refresh | Provision |
|---|---|
| Operates on an existing database. | Creates a new database. |
| In-place operation — same database object in DCT. | Creates a new database object in DCT. |
| Timeline is updated in place. | New database starts a new timeline from the provisioning point. |
| Use when you want to update an existing environment | Use when you want to create an additional environment |
Preserving points beyond the rolling backup window
The rolling automated backup window has a finite retention period (default 7 days; configurable up to 35 days). If you need to preserve access to a point in time beyond this window:
-
Refresh the database to the desired historical point.
-
Create a snapshot or bookmark at the current state of the database.
-
Optionally, refresh the database back to a more recent point.
The snapshot or bookmark will persist independently of the rolling backup window retention policy.