...

1. change postgres.conf to enable networking

2. create a replication user

3. allow remote access in pg_hba.conf
   

initdb -D /var/lib/postgresql/daselement-munich

...

Create a replication user

...

Allow remote access in pg_hba.conf

add line to allow access for the replication user

vim /var/lib/postgresql/daselement-datamunich/pg_hba.conf

# TYPE  DATABASE        USER            CIDR-ADDRESS            METHOD
# IPv4 local connections
host    all             repuser             localhost               trust

# restart the Postgres server because of changes in the config files
pg_ctl -D /var/lib/postgresql/daselement-munich restart

...

The primary system is now ready. Let’s move on to the replica system!

Create replica database server

# create the replica Postgres server
# this command pg_basebackup copies the files from the primary database

pg_basebackup -h db-munich -U repuser --checkpoint=fast -D /var/lib/postgresql/daselement-munich-replica/ -R --slot=daselement_munich -C --port 5432

In the replica directory you will find these two files:

Now start the replica server

# start the Postgres server
pg_ctl -D /var/lib/postgresql/daselement-munich-replica

Configure library

In the other facility copy and import the library (.lib) from main facility.
Make sure to :

1. update the library root

2. update the database information

3. lock the library (Lock Library option) to prevent editing and ingesting of new elements!

An option is to setup the main facility to automatically sync the Proxy Files to the other facilities when an element is ingested. This can be done with an additional transcoding task and a custom command task.

# Example:
your-sync-tool <paths.proxy.directory> /path/to/other/facility
your-sync-tool <paths.filmstrip.directory> /path/to/other/facility
your-sync-tool <paths.thumbnail.directory> /path/to/other/facility

Advanced Setup

If you want to take it a step further it’s a good idea to look into these topics:

...