Skip to main content
Skip table of contents

Quick start guide for PostgreSQL

Linking a PostgreSQL data source

This quick start guide, which is excerpted from the larger User Guide, is intended to provide you with a quick overview of working with PostgreSQL database objects in the Delphix Engine. It does not cover any advanced configuration options or best practices, which can have a significant impact on performance. It assumes that you are working in a Lab/Dev setting and attempting to quickly test Delphix functionality. It assumes you will use the VMware Hypervisor. 

Overview

In this guide, we will walk through deploying a Delphix Engine, starting with configuring Source and Target database environment. We will then create a dSource, and provision a VDB.

For purposes of the QuickStart, you can ignore any references to Replication or Masking, such as the engines shown in the diagram below.

Deploy OVA on VMware

Use the Delphix-supplied OVA file to install the Delphix Engine. The OVA file is configured with many of the minimum system requirements. The underlying storage for the install is assumed to be redundant SAN storage.

  1. Download the OVA file from https://download.delphix.com. You will need a support login from your sales team or a welcome letter.

    1. Navigate to the Delphix Product Releases/ /appliance="" images="">

  2. Login using the vSphere client to the vSphere server (or vCenter Server) where you want to install the Delphix Engine.

  3. In the vSphere Client, click File.

  4. Select Deploy OVA Template.

  5. Browse to the OVA file.

  6. Click Next.

  7. Select a hostname for the Delphix Engine. This hostname will also be used in configuring the Delphix Engine network.

  8. Select the data center where the Delphix Engine will be located.

  9. Select the cluster and the ESX host.

  10. Select one (1) data store for the Delphix OS. This datastore can be thin-provisioned and must have enough free space to accommodate the 127GB comprising the Delphix operating system.

  11. Select four (4) or more data stores for Database Storage for the Delphix Engine. The Delphix Engine will stripe all of the Database Storage across these VMDKs, so for optimal I/O performance, each VMDK must be equal in size and be configured Thick Provisioned - Eager Zeroed. Additionally, these VMDKs should be distributed as evenly as possible across all four SCSI I/O controllers.

  12. Select the virtual network you want to use. If using multiple physical NICs for link aggregation, you must use vSphere NIC teaming. Do not add multiple virtual NICs to the Delphix Engine itself. The Delphix Engine should use a single virtual network. For more information, see Optimal Network Architecture for the Delphix Engine

  13. Click Finish. The installation will begin and the Delphix Engine will be created in the location you specified.

  14. Once the installation has completed, power on the Delphix Engine and proceed with the initial system configuration as described in Setting Up Network Access to the Delphix Engine.

If your source database is 4 TB, you probably need 4 TB of storage for the Delphix Engine. Add at least 4 data disks of similar size for the Delphix VM. For example: for a source database of 4 TB, create 4 VMDKs of 1 TB each.

For a full list of requirements and best practice recommendations, see  Virtual Machine Requirements for VMware Platform

Setup network access to the Delphix Engine

  1. Power on the Delphix Engine and open the Console.

  2. Wait for the Delphix Management Service and Delphix Boot Service to come online. This might take up to 10 minutes during the first boot. Wait for the large orange box to turn green.

  3. Press any key to access the sysadmin console.

  4. Entersysadmin@SYSTEMfor the username andsysadminfor the password.

  5. You will be presented with a description of available network settings and instructions for editing.

    CODE 
    Delphix Engine Network Setup To access the system setup through the browser, the system must first be configured for networking in your environment. From here, you can configure the primary interface, DNS, hostname, and default route. When DHCP is configured, all other properties are derived from DHCP settings. To see the current settings, run "get." To change a property, run "set =." To commit your changes, run "commit." To exit this setup and return to the standard CLI, run "discard." defaultRoute    IP address of the gateway for the default route -- for example, "1.2.3.4." dhcp            Boolean value indicating whether DHCP should be used for the primary interface. Setting this value to "true" will cause all other properties (address, hostname, and DNS) to be derived from the DHCP response dnsDomain       DNS Domain -- for example, "delphix.com" dnsServers      DNS server(s) as a list of IP addresses -- for example, "1.2.3.4,5.6.7.8." hostname        Canonical system hostname, used in alert and other logs -- for example, "myserver" primaryAddress  Static address for the primary interface in CIDR notation -- for example, "1.2.3.4/22" Current settings: defaultRoute: 192.168.1.1 dhcp: false dnsDomain: example.com dnsServers: 192.168.1.1 hostname: Delphix primaryAddress: 192.168.1.100/24

  6. Configure the hostname. If you are using DHCP, you can skip this step.

    CODE 
    delphix network setup update *> set hostname=<hostname>

    Note:
    Use the same hostname you entered during the server installation.

  7. Configure DNS. If you are using DHCP, you can skip this step.

    CODE 
    delphix network setup update *> set dnsDomain=<domain> delphix network setup update *> set dnsServers=<server1-ip>[,<server2-ip>,...]

  8. Configure either a static or DHCP address.

    DHCP Configuration

    CODE 
    delphix network setup update *> set dhcp=true

    Static Configuration

    CODE 
    delphix network setup update *> set dhcp=false delphix network setup update *> set primaryAddress=<address>/<prefix-len>

    Note:
    The static IP address must be specified in CIDR notation (for example, 192.168.1.2/24)

  9. Configure a default gateway. If you are using DHCP, you can skip this step.

    CODE 
    delphix network setup update *> set defaultRoute=<gateway-ip>

  10. Commit your changes. Note that you can use thegetcommand prior to committing to verify your desired configuration.

    CODE 
    delphix network setup update *> commit Successfully committed network settings. Further setup can be done through the browser at: http://<address> Type "exit" to disconnect, or any other commands to continue using the CLI.

  11. Check that you can now access the Delphix Engine through a Web browser by navigating to the displayed IP address, or hostname if using DNS.

  12. Exit setup.

    CODE 
    delphix> exit

Setting up the Delphix Engine

The setup procedure uses a wizard process to take you through a set of configuration screens:

  • Administrators

  • Time

  • Network

  • Network Security

  • Storage

  • Outbound Connectivity

  • Authentication

  • Network Authorization

  • Registration

  • Summary

  1. Connect to the Delphix Engine at http:///login/index.html#serverSetup. The Delphix Setup application will launch when you connect to the server. Enter your sysadmin login credentials, which initially defaults to the username sysadmin, with the initial default password of sysadmin. On first login, you will be prompted to change the initial default password.

  2. Click Next.

Administrators

The Delphix Engine supports two types of administrators:

  • System Administrator (sysadmin) - this is the engine system administrator. The sysadmin password is defined here.

  • Engine Administrator (admin) - this is typically a DBA who will administer all the data managed by the engine.

On the Administrators tab, you set up the sysadmin password by entering an email address and password. The details for the admin are displayed for reference.

The default domain user created on Delphix Engines from 5.3.1 is known as admin instead of delphix_admin. When engines created before 5.3.1 are upgraded to 5.3.1 or later they will retain their old username 'delphix_admin'. To avoid complications Delphix recommends creating users with an admin role and then Disabling delphix_admin.

Time

The engine time is used as the baseline for setting policies that coordinate between virtual databases and external applications

Choose your option to set up system time in this section. For a Quick Start, simply set the time and your timezone. You can change this later.

Network

The initial out-of-the-box network configuration in the OVA file is set to use a single VMXNET3 network adapter.

You have already configured this in the initial configuration. Delphix supports more advanced configurations, but you can enable those later.

Storage

You should see the data storage VMDKs or RDMs you created during the OVA installation. Click Next to configure these for data storage.

Serviceability

Choose your options to configure serviceability settings.

For a Quick Start, accept the defaults. You can change this later.

Authentication service

Choose your options to configure authentication services.

For a Quick Start, accept the defaults. You can change this later.

Registration

If the Delphix Engine has access to the external Internet (either directly or through a web proxy), then you can auto-register the Delphix Engine:

  1. Enter your Support Username and Support Password.

  2. Click Register.

If external connectivity is not immediately available, you must perform manual registration.

  1. Copy the Delphix Engine registration code in one of two ways:

    1. Manually highlight the registration code and copy it to clipboard. Or,

    2. Click Copy Registration Code to Clipboard.

  2. Transfer the Delphix Engine's registration code to a workstation with access to the external network Internet. For example, you could e-mail the registration code to an externally accessible e-mail account.

  3. On a machine with access to the external Internet, please use your browser to navigate to the Delphix Registration Portal at http://register.delphix.com

  4. Login with your Delphix support credentials (username and password).

  5. Paste the Registration Code.

  6. Click Register.

Although your Delphix Engine will work without registration, we strongly recommend that you register each engine as part of the setup. Failing to register the Delphix Engine will impact its supportability and security in future versions.

To regenerate the registration code for a Delphix Engine please refer to, Regenerating the Delphix Engine Registration Code. Delphix strongly recommends that you regenerate this code and re-register the engine regularly to maximize the Support Security of the Delphix Engine. Delphix recommends doing this every six months.

Summary

The final summary tab will enable you to review your configurations for System Time, Network, Storage, Serviceability, and Authentication.

  1. Click the Back button to go back and to change the configuration for any of these server settings.

  2. If you are ready to proceed, then click Submit.

  3. Click Yes to confirm that you want to save the configuration.

  4. Click Setup to acknowledge the successful configuration.

  5. There will be a wait of several minutes as the Delphix Engine completes the configuration.

Requirements for PostgreSQL source databases

Source database requirements

  • The Delphix source database can be in READ-WRITE or READ only mode. It can be a standby database(streaming site) as well.

  • The Staging host must have access to a PostgreSQL role on the source side that has replication, and login privileges. This can be the built-in PostgreSQL role or a newly-created role (for example, delphix).

    CODE 
    To create a new role for use with the Delphix Engine, use the following command: SQL> CREATE USER delphix WITH REPLICATION ENCRYPTED [ PASSWORD 'password'];

  • You must make the following changes to postgresql.conf (for more information, see the Server Configuration chapter in the PostgreSQL documentation): 

  • TCP/IP connectivity must be configured to allow the role mentioned above to connect to the source database from the Delphix Engine and from the standby DBMS instance set up by the Delphix Engine on the staging environment. This can be done by modifying the parameterlisten_addresses, which specifies the TCP/IP addresses on which the DBMS is to listen for connections from client applications.

    CODE 
    listen_addresses = '*'             # defaults to 'localhost'; use '*' for all

  • The value of max_wal_senders, which specifies the maximum number of concurrent connections from standby servers or streaming base backup clients, must be increased from its desired value by four. That is, in addition to the allowance of connections for consumers other than the Delphix Engine, there must be an allowance for four additional connections from consumers set up by the Delphix Engine.

    CODE 
    The default value max_wal_senders is zero, meaning replication is disabled. In this configuration, the value ofmax_wal_senders must be increased to two for the Delphix Engine: max_wal_senders = 4       # Default is 0

  • The value of, wal_level which determines how much information is written to the write-ahead log (WAL), must be set to archive or hot_standby to allow connections from standby servers. The valuelogicalwal_level (introduced in PostgreSQL 9.4) is also supported.

    CODE 
    The default value of wal_level is minimal, which writes only the information needed to recover from a crash or immediate shutdown to the WAL archives. In this configuration, you must add the logging required for WAL archiving as follows: wal_level = archive       # Default is minimal

  • In releases prior to PostgreSQL 9.6.x, parameter 'wal_level' allowed the values 'archive' and 'hot_standby'. These values are still accepted but mapped to 'replica'. For example, The plugin will work with ALTER SYSTEM SET wal_level TO 'replica' and ALTER SYSTEM SET wal_level TO 'hot_standby'.

  • You must configure PostgreSQL to allow PostgreSQL client connections and replication client connections from the staging target environment. To configure appropriately, add the following entries to pg_hba.conf:

    CODE 
    host all <role> <ip-address_of_delphix_engine>/32 <auth-method> host all <role> <ip-address_of_staging_target>/32 <auth-method> host replication <role> <ip-address_of_staging_target>/32 <auth-method>

  • <auth-method> can be set to trust, scram-sha-256, or md5 on source. Delphix inherits the same authentication method from the source while dSource creation and VDB provisioning. For more information on how to configure, pg_hba.conf see the Client Authentication chapter in the PostgreSQL documentation.

  • wal_keep_segments parameter in postgresql.conf file on the Source environment should be large enough to support the WAL sync process once the dSource is building up. Postgres 13 onwards, the configuration parameter wal_keep_segments is changed to wal_keep_size. It is specified in megabytes rather than the number of files as with the wal_keep_segments parameter. If you previously used wal_keep_segments, the following formula will give you an approximate equivalent setting: wal_keep_size = wal_keep_segments * wal_segment_size (typically 16MB).

  • It is mandatory to have "port" (can be commented or not commented) in postgresql.conf file.

Requirements for PostgreSQL target hosts and databases

Target environment requirements

  1. The operating system and architecture of the target environment must match those of the source environment. It is recommended that the source and the target environments should be identical and hardware configurations should match.

  2. For supported OS version and DBMS version, see PostgreSQL Matrix. The underlying Operating System for both the Source and Staging environment should be amongst these two versions.

  3. There must be an installation of PostgreSQL on the target environment that is compatible with the installation of PostgreSQL on the source environment. Two installations of PostgreSQL are compatible if and only if:

    1. They share the same vendor (for example, PostgreSQL is incompatible with EnterpriseDB Postgres Plus Advanced Server).

    2. They share the same major version number (for example, 9.5.4 is compatible with 9.5, 9.5.3; however, it is incompatible with 9.3, 9.3.24, or 9.2).

    3. They are compiled against the same architecture (in other words, 32-bit and 64-bit installations of Postgres are incompatible).

    4. They are compiled with the same WAL segment size. The default WAL segment size of 16 MB is rarely changed in practice, so almost all installations of PostgreSQL are compatible with each other in terms of WAL segment size.

  4. There must be an operating system user (e.g. PostgreSQL) with the following privileges:

    1. The Delphix Engine must be able to make an SSH connection to the target environment using the operating system user.

    2. The operating system user must have read and execute privileges on the PostgreSQL binaries installed on the target environment.

    3. The operating system user must have permission to run mount and umount as the superuser via sudo with neither a password nor a TTY. See Sudo Privilege Requirements for PostgreSQL Environments for examples of the /etc/sudoers file on different operating systems.

  5. There must be a directory on the target environment where the Delphix Engine Plugin can be installed (for example, /var/tmp ) with the following properties:

    1. The Plugin directory must be writable by the operating system user mentioned above.

    2. The Plugin directory must have at least 1.5 GB of available storage.

  6. There must be a mount point directory (for example, /mnt) that will be used as the base for mount points that are created when provisioning a VDB with the following properties:

    1. The mount point directory must be writable by the operating system user mentioned above.

    2. The mount point directory should be empty.

  7. TCP/IP connectivity to and from the source environment must be configured as described in General Network and Connectivity Requirements.

  8. Hostname and IP must be correctly set in /etc/hosts file, for example [postgres@source ~]$ hostname -i

    The output of “hostname -i” command should produce the correct result as the IP address of the server. For example:

    [postgres@source postgres]$ hostname -i 10.110.207.113

  9. When using the External Backup method for ingestion the directories being used for keeping the Backup file and WAL file should be accessible by OS User.

  10. Zip must be installed on the Staging/Target Host for External Backup Support.

  11. Starting with PostgreSQL plugin version 3.2.0 or later, the restriction of encapsulating the backup pieces in ZIP format has been removed.
    Note - These options are only applicable if backups are taken via pg_basebackup utility.
    Below are the different options for placing the PostgreSQL backup on staging server for ingestion:

    1. Option 1: You can provide the zip file in the format PostgreSQL_T<YYYYMMDDHHMMSS>.zip.

      CODE 
      $ ls -l /tmp/backup/
-rw-r--r--. 1 postgres postgres  3407927 Feb  6 05:00 PostgreSQL_T20230206.zip

    2. Option 2: Providing the backup tars directly within the backup path.
      You can directly place these tars in the provided backup path (where the old ZIP files reside) and the new plugin logic will pickup these tars rather than the ZIP file.

      CODE 
      $ ls -l /tmp/backup/
-rw-------. 1 postgres postgres   139262 Feb  6 06:57 backup_manifest
-rw-------. 1 postgres postgres 27142656 Feb  6 06:57 base.tar
-rw-------. 1 postgres postgres 16778752 Feb  6 06:57 pg_wal.tar
-rw-r--r--. 1 postgres postgres  3407927 Feb  6 05:00 PostgreSQL_T20230206.zip

    3. Option 3: Providing the backup tars in an organized way.
      You can create a directory in the format ‘PostgreSQL_T<YYYYMMDDHHMMSS>’ and store the tar files within the directory. The tar files within the latest organized folder will be used instead of the direct tar file or the ZIP files.

      CODE 
      $ ls -l /tmp/backup/
-rw-------. 1 postgres postgres   139262 Feb  6 06:57 backup_manifest
-rw-------. 1 postgres postgres 27142656 Feb  6 06:57 base.tar
-rw-------. 1 postgres postgres 16778752 Feb  6 06:57 pg_wal.tar
drwxr-xr-x. 2 postgres postgres       63 Feb  6 07:10 PostgreSQL_T20230206070907
-rw-r--r--. 1 postgres postgres  3407927 Feb  6 05:00 PostgreSQL_T20230206.zip

$ ls -l /tmp/backup/PostgreSQL_T20230206070907/
total 43048
-rw-------. 1 postgres postgres   139264 Feb  6 07:10 backup_manifest
-rw-------. 1 postgres postgres 27159552 Feb  6 07:10 base.tar
-rw-------. 1 postgres postgres 16778752 Feb  6 07:10 pg_wal.tar

      Example for command used to create the above:

      CODE 
      PGBACKUPDIR=PostgreSQL_T$(date "+%Y%m%d%H%M%S");mkdir -p /tmp/backup/$PGBACKUPDIR;/usr/pgsql-14/bin/pg_basebackup -D /tmp/
backup/$PGBACKUPDIR -F t -v -w -P -h demo.delphix.com -p 5432 -U delphix --checkpoint=fast

      Since there are 3 options in which the backup files can be provided, a precedence needs to be maintained between the above options.
      Option 3 can be considered as the method with the highest precedence , which is using organised folders to place the backup. If these folders are not present then
      [Option 2] tar files placed directly within the backup path can be used (this option is provided in order to have a standardised way of providing backups across plugins).
      Only when both the folders nor the tars are present within the provided backup path, the zip files can be used [Option 1].

  12. If there's no PostgreSQL instance running on the Target host, however, we have a PostgreSQL installation, even then the plugin relies on the "DELPHIX_PG_PATH" variable to discover the environment. In the absence of "DELPHIX_PG_PATH" variable or if the value of "DELPHIX_PG_PATH" variable is NULL then Linux "find" command will be used for the Environment discovery which may impact the overall performance. Hence, it is preferred to create this Environment Variable with correct entries. In order to optimize the performance, it is preferred to create an Environment Variable "DELPHIX_PG_PATH" which should be accessible by OS users.

    Below should be the syntax for "DELPHIX_PG_PATH" variable: DELPHIX_PG_PATH="binary_path:data_path1;binary_path:data_path2;"

    For example: DELPHIX_PG_PATH="/usr/pgsql-9.6/bin:/var/lib/pgsql/9.6/data;/opt/edb/as9.6/bin:/opt/edb/as9.6/data;/usr/pgsql-9.6/bin:/tmp/TESING/data;"

The variable "DELPHIX_PG_PATH" must be available to the environment user in a non-interactive way. You can test this variable for non-interactive logins using ssh your_username@v-cardtr.tmydb.kv.aval "env | grep DELPHIX_PG_PATH".

Adding a PostgreSQL environment

Prerequisites

Procedure

  1. Login to the Delphix Management application.

  2. Click Manage.

  3. Select Environments.

  4. Next, to Environments, click the Actions (...) menu and select Add Environment.

  5. In the Add Environment dialog, select Unix/Linux.

  6. Select Standalone Host.

  7. Click Next.

  8. Enter Name for the Environment.

  9. Enter the Host IP address or hostname.

  10. Enter the SSH port. The default value is 22.

  11. Enter an OS Username for the Environment. If a low-privileged OS user is used, make sure the Prerequisites for Privilege Elevation using DLPX_DB_EXEC Script are met.

  12. Select Login Type. — Username and Password - enter the OS username and password — Username and Public Key - enter the OS username. — Password Vault - select from an existing Enterprise Password Vault
    Info:
    Using Public Key Authentication
    If you want to use public-key authentication for logging into your Unix-based environment, there are two options: use the engine's key pair or provide a key pair for this environment.

    To use the engine's key pair:

    1. Select Public Key for the Login Type.

    2. Click View Public Key.

    3. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file does not exist, you will need to create it.

      1. Run chmod 600 ~/.ssh/authorized_keys to allow only the file's owner to read and write to it (make sure the file is owned by the user).

      2. Run chmod 755 ~ to restrict access to the user's home directory so no other user may write to it.

      3. Run chmod 700 ~/.ssh so that others cannot write to it. The ~/.ssh directory cannot be writable by group or other users. Otherwise, authentication will fail.

    As an alternative, you can provide a key pair specific for this environment via the API or CLI. See Option 2 in this CLI Cookbook article for instructions.

  13. For Password, enter the password associated with the user in step 11.

  14. If you want to use Public Key Encryption for logging into your environment:

    1. Select Public Key for the Login Type.

    2. Click View Public Key.

    3. Copy the public key that is displayed, and append it to the end of your ~/.ssh/authorized_keys file. If this file does not exist, you will need to create it.

      1. Run chmod 600 ~/.ssh/authorized_keys to allow only the file's owner to read and write to it (make sure the file is owned by the user).

      2. Run chmod 755 ~ to restrict access to the user's home directory so no other user may write to it.

      3. Run chmod 700 ~/.ssh so that others cannot write to it. The ~/.ssh directory cannot be writable by group or other users. Otherwise, authentication will fail.

        The public key needs to be added only once per user and per environment.

        You can also add public key authentication to an environment user's profile by using the command-line interface, as explained in the topic CLI Cookbook: Setting Up SSH Key Authentication for UNIX Environment Users

  15. For Password Login, click Verify Credentials to test the username and password.

  16. Enter Toolkit Path (make sure Toolkit path does not have spaces).

  17. To provide your own Oracle Java select the Provide my own JDK checkbox and click Next.

  18. In the Java Development Kit tab enter the absolute path to your Oracle JDK and click Next. 

  19. Click Submit.

As the new environment is added, you will see two jobs running in the Delphix platform Job History, one to Create and Discover an environment, and another to create an environment. When the jobs are complete, you will see the new environment added to the list in the Environments tab. If you do not see it, click the Refresh icon in your browser.

Once the environment is discovered, further linking would require adding a source config to the above-discovered installation. Please refer to Linking a PostgreSQL dSource for more information.

Linking a PostgreSQL data source

Prerequisites

Limitation

It is not possible to access the staging server with PostgreSQL 9.4 and PostgreSQL 9.5 versions.

Procedure

  1. Login to the Delphix Management application.

  2. Select Manage > Environments.

  3. From the Databases tab, select a repository from which you want to create your dSource and click the

    icon.

  4. In the Add Database dialog window enter the Name for your source config and click Add.

  5. Select your source config and click the Add dSource link located to the right.

  6. In the Source tab, do the following:

    1. In the NFS Mount Location field, enter a mount location on the staging host.

    2. If you want to use Privilege Elevation, provide the Privileged OS Account username. Make sure you meet all the requirements described in the Prerequisites for Privilege Elevation using DLPX_DB_EXEC Script section
      Info:

      You will currently not be able to update the Privileged OS account after dSource creation. The only way to achieve the change is to recreate the dSource.

      If the Environment OS user will be used to create the dSource, make sure you have the following privileges:

      • access to the the postgres commands

      • read+write+execute permissions on the `unix_socket_directories` configured in `postgresql.conf` [Default directories: `/var/run/postgresql` & `/tmp`]

    3. Select the checkbox next to the Delphix Initiated Backup - Postgres Cluster Ingestion Flag option. Selecting this checkbox allows Delphix to initiate the physical backup on the source database.

    4. Click on the +Add icon located next to the Delphix Initiated Backup/External Backup - Streaming Replication Parameters option.

      Note:
      The Add Button provided for Delphix Initiated Backup/External Backup - Streaming Replication is clickable multiple times but should be used ONLY once since the solution is built only to support a single backup path. Providing Multiple Paths will error out the linking process.

      The following fields are mandatory for this process :

      1. Delphix Initiated Backup - Postgres Cluster Ingestion Flag - Checkbox should be selected.

      2. PostgresDB Replication User

      3. PostgresDB Replication User Password

      4. Source Host Address

      5. Source Instance Port Number

      6. Staging Instance Port Number - must be unique for a given instance.

    5. Optionally, database configuration parameters can be defined during the linking operation in the Config Settings section.

      Info:
      After dSource creation, users can now configure the parameters and their values in the postgresql.conf file through the "Config Settings" section on the Delphix Engine UI. For example, to support Replication Slots through UI, users can now provide the "primary_slot_name" parameter and its value through the UI. This will update the already existing parameter value in the postgresql.conf file with the value provided by the user.
      Similarly, if a user wants to disable a parameter then they can provide the parameter name and select the check box Comment Property. This will comment out the parameter in the postgresql.conf configuration file.

    6. Click Next.

  7. In the dSource Configuration tab, enter a dSource name and select a group for your dSource. Adding a dSource to a dataset group lets you set Delphix Domain user permissions for that database and its objects, such as snapshots. See the topics under Users and Groups for more information.

  8. In the Data Management tab, specify your Staging Environment, User, and Snapshot Parameters. Select the Resynchronize dSource checkbox if you want to resynchronize the dSource. Resynchronizing the dSource will force a non-incremental load of data from the source. This operation is similar to creating a new dSource, but avoids duplicating storage requirements and maintains timeflow history. Click Next.

  9. In the Policies tab, apply policy details to the dSource if required, and then click Next.

  10. In the Hooks tab, select a Hook Point and then click + to add a script to run at that point. You can define scripts to run at multiple hook points in the process.

  11. In the Summary tab, review the configuration profile for the dSource.

  12. Click Submit. The Delphix Engine initiates two jobs to create the dSource: DB_Link and DB_Sync. You can monitor these jobs by clicking Active Jobs from the top menu bar, or by selecting System > Event Viewer. When the jobs have successfully completed, the database icon will change to a dSource icon on the Environments > Host > Databases screen, and the dSource will also appear in the list of Datasets under its assigned group.

The dSource Configuration Screen

After you have created a dSource, the dSource Configuration tab allows you to view information about it and make modifications to its policies and permissions. In the Datasets panel, select the dSource you wish to examine. You can now choose the configuration tab to see information such as the Source files, Data Management configuration, and Hook Operations.

Provisioning a PostgreSQL VDB

Prerequisites

Procedure

  1. Navigate to Manage, and select Datasets.

  2. Select a dSource and a snapshot from which you want to provision. Click the provision VDB icon to open the provision VDB wizard.

  3. Select a target environment from the left pane, and an Installation to use from the dropdown list of available PostgreSQL instances on that environment.

  4. Set the Environment Userto be the Instance Owner.
    Note:

    The picking of instance owner is only possible if you have multiple environment users set on that host.

  5. You will see the Target Configuration section where you need to specify NFS Mount Location.

  6. If you want to use Privilege Elevation, provide the Privileged OS Account username. Make sure you meet all the requirements described in the Prerequisite for Discovery Operation section.

    Note:
    To update the Privileged OS Account after VDB creation, first disable the instance, update the Privileged OS Account, and then enable it.

    If the Environment OS user will be used to create the VDB, make sure you have the following privileges:

    • access to the the postgres commands

    • read+write+execute permissions on the `unix_socket_directories` configured in `postgresql.conf` [Default directories: `/var/run/postgresql` & `/tmp`]

  7. Optionally, you can set the database configuration parameters for the VDB using Config Settings. Users can disable a configuration parameter by selecting the check box Comment Property. This will comment out the parameter in the postgresql.conf configuration file. Click Next.

  8. On the Configuration page enter the PostgreSQL VDB name which will be displayed on the UI.

  9. Select a Target Group for the VDB and click the green Plus icon to add a new group, if necessary.

  10. Select a Snapshot Policy for the VDB then click Next.

  11. Specify any desired hook operations. 

  12. Review the Provisioning Configuration and Data Management information.

  13. Click Submit.

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.

Next steps

Congratulations! You have provisioned your first virtual database!

Now, perform some simple functional tests with your application. You can connect your app to the VDB using standard TNS/JDBC techniques. Delphix has already registered the VDB for you on the target listener.

We suggest the following next steps:

  1. Drop a table and use the VDB Rewind feature to test the recovery of your VDB.

  2. Take a snapshot of your dSource and refresh your VDB to quickly get fresh production data.

  3. Provision a new VDB from your VDB to test the sharing data quickly with other teams.

  4. Mask your new VDB to protect sensitive data. Provision new VDBs from that masked VDB to quickly provide safe data to development and QA teams.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close