11:18:07 AM : Starting job “Backup” - “Full”. Computer “PC”. App v.“12.2.3”
11:18:08 AM : Connecting to PostgreSQL Server: PostgreSQL 9.2.1, compiled by Visual C++ build 1600, 32-bit. localhost
11:18:08 AM : The backup folder “C:\Windows\TEMP\SYSTEM\Pranas.NET\SQLBackupAndFTP\backup” has “189,401GB” free space. The temporary folder “C:\Windows\TEMP\SYSTEM\Pranas.NET\SQLBackupAndFTP\backup” has “189,401GB” free space
11:18:09 AM : Backing up “localhost” databases with pg_dump.exe: pg_dump (PostgreSQL) 9.2.1
11:18:09 AM : Getting maximum file size…
11:18:09 AM : The maximum file size: “”
11:18:09 AM : ERROR: Failed to backup “firm001” database with “Full” backup type: C:\Program Files (x86)\PostgreSQL\9.2\bin\pg_dump.exe process has finished with “1” code. The error message: "C:\Program Files (x86)\PostgreSQL\9.2\bin\pg_dump.exe: illegal option – dbname=firm001–host=localhost Try “pg_dump --help” for more information. ".
To investigate this case we need more details. Could you please enable the advanced log with “Trace” option, reproduce the issue and send logs to our dev team. Here are more details on how to do it How to send Log to developers | SQLBackupAndFTP's blog
Note! With the “Trace” level, a log can contain your passwords. Before sending a log to dev team please open it using any text editor and remove the information you prefer to keep in secret. You can find them by clicking the “Open folder” link at the “Advanced Log” window (“Tools” > “Advanced Log…”).
Please let us know if the logs will be sent, also please provide us with your application id (“Help” > “About”).
It seems the issue the version of pg_dump. --dbname instruction is available only in version 9.3 but you use version 9.2. To resolve the issue, please try to specify a path to pg_dump version 9.3 or higher at the advanced settings in your connection window.
From our side, we’ll check how can we improve this.
According to your last reply, we considered that the issue was resolved. Could you please tell us have you tried to specify a path to your pg_dump file? Was it resolved the issue?
Sorry for the confusion. You had mentioned in a previous reply that it looked like I was running Postgres 9.2, I was attempting to show we are on 9.3 and the path I used to get a successful test connection, which is where the pg_dump file is located. I did install the latest alpha you linked.
We have checked this issue, the error message you get means that pgdump doesn’t support --dbname parameter. --dbname parameter supporting starting from version 9.3. Here are more details at PostgreSQL: Documentation: 9.3: pg_dump
version 9.2 doesn’t support --dbname parameter
It is strange that you get this error message with version 9.3.
To investigate this case we need more details. Could you please enable your advanced log with the “Trace” level, reproduce the issue and send logs to our dev team. Here are more details on how to do it How to send Log to developers | SQLBackupAndFTP's blog
Note! With the “Trace” level, a log can contain your passwords. Before sending a log to dev team please open it using any text editor and remove the information you prefer to keep in secret. You can find them by clicking the “Open folder” link at the “Advanced Log” window (“Tools” > “Advanced Log…”).
Please let us know when the logs will be sent and provide us with your Application ID (“Help” > “About”).