Bobcares

Docker postgres pg_restore | Tutorial

by | Jul 19, 2022

Docker postgres pg_restore is now so simple with these steps.

Bobcares, as part of our Docker Hosting Support Service, responds to all inquiries, large or small.

Let’s take a closer look at restoring the data dump using pg_restore.

Docker postgres pg_restore

For Restoring Data Dump Using pg_restore, our Support team provides these simple steps:

1. Firstly, determine the name and id of the Docker container hosting the Postgres instance

Start Docker and enter the docker command:

$ docker ps

The command results in:

CONTAINER ID ... NAMES abc985ddffcf ... my_postgres_1

2. Then locate the volumes that are available in the Docker container

Now run the command:

docker inspect -f '{{ json .Mounts }}' | python -m json.tool

Then, examine the volume paths under the Destination key. The result will be:

$ docker inspect -f '{{ json .Mounts }}' abc985ddffcf | python -m json.tool

[

{

"Type": "volume",

"Name": "my_postgres_backup_local",

"Source": "/var/lib/docker/volumes/my_postgres_backup_local/_data",

"Destination": "/backups",

"Driver": "local",

"Mode": "rw",

"RW": true,

"Propagation": ""

},

{

"Type": "volume",

"Name": "my_postgres_data_local",

"Source": "/var/lib/docker/volumes/my_postgres_data_local/_data",

"Destination": "/var/lib/postgresql/data",

"Driver": "local",

"Mode": "rw",

"RW": true,

"Propagation": ""

}

]

Here /backups and /var/lib/postgresql/data is the volume path.

3. Now copy dump into one of the volumes

To continue Restoring Data Dump Using pg_restore, pick a volume and copy the dump in. Then run the command:

docker cp </path/to/dump/in/host> :

Here we select volume /backups. It gives the following result:

$ docker cp my_data.dump my_postgres_1:/backups

4. Finally, request the database owner to run the pg_restore command

Using the docker exec command, run the pg restore command. The generic forms of both commands are here:

For pg_restore:

pg_restore -U -d

For docker exec:

docker exec

This is optional if we know the DB owner. We can also find the owner by retrieving the list of databases and their owners. So we have to run the following command to continue with Restoring Data Dump Using pg_restore

psql -U postgres -lcommand. within the docker exec command.

docker exec my_postgres_1 psql -U postgres -l

Running this command gives the result:

List of databases

Name | Owner

--------------------+----------

some_database | postgres

Now we can run the command pg_restore:

docker exec my_postgres_1 pg_restore -U postgres -d some_database /backups/my_data.dump

Now we are all set to restore Postgres data dump in a Docker container using pg_restore.

[Looking for an answer to another question? We’re only a click away.]

Conclusion

To sum up, our Support team provides the details on Restoring Data Dump Using pg_restore which includes mainly 4 steps.

    1. Primarily, we determine the name and id of the Docker container hosting the Postgres instance.
    2. Then we locate the volumes that are available in the Docker container.
    3. After that copy dump into one of the volumes.
    4. At last, request the database owner to run the pg_restore command.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF