• Administrators
• Time
• Network
• Network Security
• Storage
• Serviceability
• Authentication
• Network Authorization
• Registration
• Summary

1. Connect to the Delphix Engine at http://<Delphix Engine>/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.

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.

Source Database Requirements

• The database must accept read/write connections. In other words, it must not be in standby mode.

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

  To create a new role for use with the Delphix Engine, use the following command:
  
  SQL> CREATE ROLE delphix SUPERUSER LOGIN REPLICATION [ 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.
  

  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.
  

  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.
  

  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

  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:
  

  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> must be set to trust. 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 Source environment should be large enough to support the WAL sync process once the dSource is building up.
• It is mandatory to have "port" (can be commented or not commented)  in postgresql.conf file.

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. postgres) 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 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. Backup command and File should be in below format:
    PostgreSQL_T<YYYYMMDD>.zip where YYYY denotes Year, MM denotes month, DD denotes date. For example PostgreSQL_T20190314.zip.
    The above zip file should contain Database Full Backup from the Source created in tar format. Below flags with pg_basebackup is to be used for taking Source Database backup:
    
    For PostgreSQL versions 9.4.x,9.5.x,9.6.x -
    <path to bin>/pg_basebackup -p<port number> -D<data dir location> -F t -v -w -P -x
    
    For PostgreSQL versions 10.x and 11.x
    <path to bin>/pg_basebackup -p<port number> -D<data dir location> -F t -v -w -P -Xs

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".
13. 
    

Prerequisites

• Make sure that the staging environment in question meets the requirements described in Requirements for PostgreSQL Hosts and Databases

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 which is currently ‘postgres’.

12. Select Login Type.

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:

    a. Select Public Key for the Login Type. b. Click View Public Key. c. 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.     i. 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).     ii. Run chmod 755 ~ to restrict access to the user's home directory so no other user may write to it.     iii. 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.

18. 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.

Prerequisites

• The source and staging instances must meet the host requirements

• Databases must meet container requirements 

  For more information refer to Requirements for PostgreSQL Source Hosts and Databases
  

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 click on the +Add icon located next to Delphix Initiated Backup Parameter. 

   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 :

   • • Delphix Initiated Backup Flag - Checkbox should be selected.
     • PostgresDB Replication User
     • PostgresDB Replication User Password
     • Source Host Address
     • Source Instance Port Number
     • Staging Instance Port Number - must be unique for a given instance

    

7. Optionally, database configuration parameters can be defined during the linking operation in the Config Settings section. Click Next.
8. 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.
9. In the Data Management tab specify your Staging Environment, User and Mount Base, then click Next.
10. If required apply policy details to the dSource, then click Next.
11. Users can provide bash scripts as Plugin defined hooks. These hooks are executed after data ingestion but before snapshot operation, click Next.
12. Review the dSource Configuration and Data Management information in the Summary section.

13. 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.

Prerequisites

• 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

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 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.

5. You will see the Target Configuration section where you need to specify Mount Path and Virtual Postgres Port Number.

   
   

6. 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.

7. On the configuration page enter the PostgreSQL database name as the vFiles Name value.

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

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

10. Specify any desired hook operations. 
11. Review the Provisioning Configuration and Data Management information.

12. 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.