loading...empty;done;/dump-postgres/:-uriPostgreSQL Dump Import/Export | iNET.elastic Dev Docs

Import and Export Dump Files to PostgreSQL

Create two database environments and connect to them using any desktop client (we use pgAdmin4 as an example. Learn more in our tutorial).

create two postgresql databases

Dump export from PostgreSQL

  1. We put environments remotepostgres.vip.iNET.elastic.cloud and destination.vip.iNET.elastic.cloud to the respective server groups backupsource and destination at the pgAdmin4 application.

pgadmin server groups

  1. Make a right-click on the required database to be backed up e.g. iNET.elastic and choose Backup.

backup required database

  1. Specify your dump file name and the format of the output file. E.g. mybackup and Tar file format respectively.

backup dialog general

  1. Click on the Dump options tab and select backup options for database objects.

backup dialog dump options

  1. Finally, click the Backup button. The successful window should appear.

successful backup Your dump file will be stored in the user home directory or by the path to which you have specified at the host the pgAdmin4 is running on.

Dump import to PostgreSQL

  1. Create an empty database at the destination server.

create new database

  1. Set the name in the field Database either the same e.g. iNET.elastic or any arbitrary name.

create database dialog

  1. To perform dump import to PostgreSQL database make the right-click on the new database and choose Restore.

restore database

  1. Select the file format used during the database backup operation. As for our example, we used tar format. Specify the name of the backup file or use file open dialogue at the right of the Filename field to choose the necessary file.

restore dialog general

  1. Set advanced restoring options if needed.

restore dialog options

  1. Finally, click on the Restore button.
  2. Navigate back to the iNET.elastic database at the destination server group and make sure that the database was restored properly with its content at both servers Master and Slave.

ensure database restored and replicated

That’s all! Hope this how-to was useful for you.

What’s next?