For each Postgres database server that is to be managed by BART, a database user must be chosen to serve as the replication database user.
• Sets the Postgres archive_command configuration parameter when the INIT subcommand in invoked.
• Creates backups when the BACKUP subcommand is invoked.The pg_hba.conf file must minimally permit the replication database user to have access to the template1 database as shown for repuser in the following example.The IP address from where the replication database user has access to database template1 is the location of the BART host.For pg_basebackup only: The replication database user must also be included in the pg_hba.conf file as a replication database connection as shown by the last entry in the example if pg_basebackup is to be used for taking any backups such as for standby servers.The replication database user must be specified with the user parameter of the BART configuration file for the database server as shown by the following:There must be no password prompt when connecting to the database server with the replication database user. There are several Postgres standard ways to permit this. A recommended method is to use the .pgpass file located in the BART user account’s home directory.For example, if bartuser is the BART user account, then the .pgpass file located in /home/bartuser/.pgpass must contain the following entry.Thus, when bartuser runs BART BACKUP, the password for the replication database user, repuser, is obtained from the .pgpass file of bartuser to connect to the database server running at 192.168.2.24 on port 5444.The .pgpass file must contain an entry for each BART managed database server and its corresponding replication database user and password.