Skip to main content

Data source: WAL-G

info

As the first step, you need to set up a machine for Database Lab Engine instance. See the guide Set up a machine for the Database Lab Engine.

Configuration#

Jobs#

In order to set up Database Lab Engine to automatically get the data from database using WAL-G archival restoration tool you need to use following jobs:

Options#

Copy the contents of configuration example config.example.physical_walg.yml from the Database Lab repository to ~/.dblab/server.yml and update the following options:

  • Set secure server:verificationToken, it will be used to authorize API requests to the Engine
  • Set connection options in physicalRestore:options:envs:
  • Set WAL-G settings in physicalRestore:options:walg:
    • backupName - defines the backup name to restore
  • Set a proper version in Postgres Docker images tags (change the images itself only if you know what are you doing):
    • provision:options:dockerImage
    • retrieval:spec:physicalRestore:options:dockerImage
    • retrieval:spec:physicalSnapshot:options:promotion:dockerImage

Run Database Lab Engine#

tip

Use Docker volumes to make credential files available to WAL-G. For example: --volume ~/.dblab/sa.json:/home/dblab/sa.json.

sudo docker run \  --name dblab_server \  --label dblab_control \  --privileged \  --publish 2345:2345 \  --volume /var/run/docker.sock:/var/run/docker.sock \  --volume /var/lib/dblab:/var/lib/dblab/:rshared \  --volume ~/.dblab/server.yml:/home/dblab/configs/config.yml \  --volume ~/.dblab/sa.json:/home/dblab/sa.json \  --volume /sys/kernel/debug:/sys/kernel/debug:rw \  --volume /lib/modules:/lib/modules:ro \  --volume /proc:/host_proc:ro \  --env DOCKER_API_VERSION=1.39 \  --detach \  --restart on-failure \  postgresai/dblab-server:2.4.1

Restart in the case of failure#

TBD
note

This page is unfinished. Reach out to the Postgres.ai team to learn more.