Symptoms

After successfully upgrading Data Protection Advisor (DPA) most "dpa ds" commands including export and import no longer work. To identify if a setup has this issue, test running any datastore command (dpa ds) after upgrade on the Datastore. Whenever a datastore command is run the result will be as below: D:\DPA\services\bin>dpa ds query --debug "select * from pg_prepared_xacts;" EMC Data Protection Advisor [ERROR] Failed to query data from the datastore service This is a fairly generic looking error. Instead run the command with the --debug logging switch. The output will look like below. D:\DPA\services\bin>dpa ds query --debug "select * from pg_prepared_xacts;" EMC Data Protection Advisor Environment variables are : [] [DEBUG] SERVICE_NAME: EMC DPA Datastore Service [DEBUG] TYPE : 10 WIN32_OWN_PROCESS[DEBUG] STATE : 4 RUNNING[DEBUG] (STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN)[DEBUG] WIN32_EXIT_CODE : 0 (0x0)[DEBUG] SERVICE_EXIT_CODE : 0 (0x0)[DEBUG] CHECKPOINT : 0x0[DEBUG] WAIT_HINT : 0x0[DEBUG] PID : 4352[DEBUG] FLAGS : [DEBUG] Service Conditions : false false true false [DEBUG] Service State : RUNNING [DEBUG] --host 127.0.0.1 --port 9003 -d apollo -c select * from pg_prepared_xacts; [INFO] QUERY RESULT : Environment variables are : [PGHOST=127.0.0.1 PGREADONLYUSER=pgreadonly PGREPLICATION=NONE PGUSER=apollosuperuser PGPORT=9003 SVC_USERGROUP=dpaservices PGDATA=D\:\\DPA\\services\\datastore\\data ] [DEBUG] psql: error: could not connect to server: Connection refused (0x0000274D/10061) [DEBUG] Is the server running on host "127.0.0.1" and accepting[DEBUG] TCP/IP connections on port 9003? [ERROR] Failed to query data from the datastore service The last 3 lines/messages above identify this issue.There is also another variation that can happen in some scenarios or with an incomplete fix to the configuration. The error message will be as below: [DEBUG] psql: error: FATAL: no pg_hba.conf entry for host "192.168.0.2", user "apollosuperuser", database "apollo", SSL off [ERROR] Failed to query data from the datastore service Though this variation will be less common.

Cause

This is a known Bug/Defect in Data Protection Advisor.The patch builds below and higher are affected.DPA 19.5 b135DPA 19.6 b90DPA 19.7 b25

Resolution

There is no resolution to this issue at this time.A Work Around is available for this issue.The Datastore can be manually reconfigured to allow the "dpa ds" commands to function normally. There are 2 files that require modification to fix this.Note: Care must be taken with this work around, as an incorrect configuration could cause loss of access to the Datastore database.The steps for the modifications are below. Stop the DPA ApplicationStop the DPA DatastoreNote the IP Address of the DPA Datastore, this will be used later onMake backup copies of the following two files (in case they are needed to be reverted to) C:\Program Files\EMC\DPA\services\executive\datastore-service.confC:\Program Files\EMC\DPA\services\datastore\data\pg_hba.conf Edit the file C:\Program Files\EMC\DPA\services\executive\datastore-service.confIn this file there is a line like this below PGHOST=127.0.0.1 Change 127.0.0.1 to the true IP Address of the Datastore server, example 192.168.0.2 PGHOST=192.168.0.2 Save this fileEdit the file C:\Program Files\EMC\DPA\services\datastore\data\pg_hba.confIn this file there will be series of lines at the bottom like below # TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all all scram-sha-256 # IPv4 local connections: hostssl all all 127.0.0.1/32 scram-sha-256 # IPv6 local connections: hostssl all all ::1/128 scram-sha-256 # Allow replication connections from localhost, by a user with the # replication privilege. local replication all scram-sha-256 hostssl replication all 127.0.0.1/32 scram-sha-256 hostssl replication all ::1/128 scram-sha-256 hostssl all apollouser 192.168.0.1/32 scram-sha-256 The last line will have an entry with the IP Address of the DPA Application server, from above this is 192.168.0.1Add a similar line below this one, that looks like this below hostssl all apollosuperuser 192.168.0.2/32 scram-sha-256 Where 192.168.0.2 is the IP Address of the DPA Datastore serverThe final edited file should look like this # TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all all scram-sha-256 # IPv4 local connections: hostssl all all 127.0.0.1/32 scram-sha-256 # IPv6 local connections: hostssl all all ::1/128 scram-sha-256 # Allow replication connections from localhost, by a user with the # replication privilege. local replication all scram-sha-256 hostssl replication all 127.0.0.1/32 scram-sha-256 hostssl replication all ::1/128 scram-sha-256 hostssl all apollouser 192.168.0.1/32 scram-sha-256 hostssl all apollosuperuser 192.168.0.2/32 scram-sha-256 The newly added line is in bold above.NOTE: The original ordering of these line may vary somewhat. There is no issue if the ordering is different, as long as there is one line for each IP Address entry as aboveSave this file.Restart the DPA DatastoreTest running a command line "dpa ds" command In the steps above we are using the Windows platform and the default installation path. Use the appropriate DPA installation path for your setup and platform.If there are unexpected variations with any of the contents of these files, do not modify them without first discussing with DPA Technical Support.Please contact Dell Technical Support for further details or information.

Support Cases