You can take a new snapshot of the dSource by clicking the Camera icon on the dSource card. Once the snapshot is complete you can provision a new VDB from it. This topic describes how to provision a virtual database (VDB) from a POSTGRES dSource.
You will need to have linked a dSource from a staging instance, as described in Linking a PostgreSQL dSource or have created a VDB from which you want to provision another VDB
You should have set up the POSTGRES target environment with necessary requirements as described in PostgreSQL Support and Requirements
Make sure you have the required Instance Owner permissions on the target instance and environment
The method for Database Permissions for Provisioned PostgreSQL VDBs is decided before the provisioning
- Navigate to Manage, and select Datasets.
- Select a dSource and a snapshot from which you want to provision. Click the provision VDB icon to open the provision VDB wizard.
Select a target environment from the left pane, and an Installation to use from the dropdown list of available PostgreSQL instances on that environment.
Set the Environment User to be the Instance Owner. Note: The picking of instance owner is only possible if you have multiple environment users set on that host.
You will see the Target Configuration section where you need to specify Mount Path and Virtual Postgres Port Number.
- Optionally, set the database configuration parameters for the VDB, then click Next.
By default, the VDB gets created in an inaccessible mode because the parameter "listen_addresses" is set to "localhost". However, a customer can change the value of this parameter using "Config Settings" when creating a VDB.
On the configuration page enter the PostgreSQL database name as the vFiles Name value.
Select a Target Group for the VDB and click the green Plus icon to add a new group, if necessary.
Select a Snapshot Policy for the VDB then click Next.
- Specify any desired hook operations.
- Review the Provisioning Configuration and Data Management information.
Once the VDB provisioning has successfully completed, if the source and target instance ids are not the same, you may want to grant secadm and dbadm on the database to the target instance id. Please refer to Database Permissions for Provisioned PostgreSQL VDBs for more information.