ログには以下のように報告されています： pg_dump: [archiver (db)] connection to database "discoursedb" failed: could not connect to server: Connection refused
問題点は以下の 2 点ではないかと考えています：
リモートサーバーが非標準ポートで実行されている。
リモートの PostgreSQL が新しい PSQL バージョンで実行されている。
アプリにログイン（/var/discourse/launcher enter app）して手動でバックアップを実行したところ、ポート定義なしで実行すると、最初と同じエラーが発生することがわかりました：
$ pg_dump -h 123.456.789.101 -U username -W -F t discourse_db > discourse_db_backup.tar
Password:
pg_dump: [archiver (db)] connection to database "discourse_db" failed: could not connect to server: Connection refused
Is the server running on host "123.456.789.101" and accepting
TCP/IP connections on port 5432?
I did find some discussion in another post regarding someone who has a slightly comparable situation. The big difference in my case is that we store files on the local server vs S3. I could forego backing up PostgreSQL since that is backed up independently, however I do still need to back up:
local content and
Discourse settings
I still would like a consolidated backup with the db + content + settings all in one place, but I’m guessing you don’t/won’t support that and thus I’d like to at least get content + settings into a consolidated package.
Interesting and odd. I had read somewhere that 11 was alright, but aside from that I have a system already deployed to 11 and have not seen any errors or problems (aside from backup) thus far… Now you have me worried…
Yes. I’ve got two systems deployed on pg11 too. They are working fine except I’m doing backups directly. I upgraded pg to 11 in the container. They’ll make backups but not restore them.
The Discourse backup system should simply warn and not fail if there is a PostgreSQL version mismatch. I just tried to make a backup myself and because I too am using an external PG server, no tarball was created at all.