Content Comparison

...

1. Trigger CSD in archive mode

2. Create base backup files

   1. Code Block
      /opt/rh/rh-postgresql13/root/usr/bin/pg_basebackup -D tempBackupDir -F tar -X stream -R --progress --verbose

   2. The aforementioned command will generate the subsequent files, which are to be transferred to the Standby in order to facilitate the cluster restoration process.

      1. base.tar: postgresql base files, including setting and etc

      2. pg_wal.tar: wal data files for standby to restore

      3. tblspc_xxxxx.tar: customized table space files

      4. backup_manifest: backup meta data, is used for pg_verifybackup to verify the backup

3. On Primary MP find and Tar the postgresql config files, Including

   1. postgres.conf

   2. pg_ident.conf

   3. pg_hba.conf

4. On Standby MP receive all files generated from Primary server on step 3 and step 2.b

5. Data directory setup: Extract files generated from 2.b and placed to the target data folder assigned before triggering CSD

6. Config directory setup:

   1. Extract files from tar ball recieved on step 4 and put them into the target config directory

   2. Configure the PostgreSQL configuration in streaming archive mode according to the CSD parameter and streaming slot.

7. If the OS is windows, register windows service for the cluster

8. After setting up data director and config directory, restart standby server

9. Applying the latest changes on configuration coming CSD and persisting configuration data on Control Center

...

1. Trigger CSD in archive mode

2. Create Replication Slot on Primary

   1. Code Block
      SELECT * FROM pg_create_physical_replication_slot(SLOT_NAME, false, false) WHERE NOT EXISTS (SELECT * FROM pg_replication_slots WHERE slot_name = SLOT_NAME)

3. Create base backup files

   1. Code Block
      /opt/rh/rh-postgresql13/root/usr/bin/pg_basebackup -D tempBackupDir -F tar -X stream -R --progress --verbose -S slot_name

   2. The aforementioned command will generate the subsequent files, which are to be transferred to the Standby in order to facilitate the cluster restoration process.

      1. base.tar: postgresql base files, including setting and etc

      2. pg_wal.tar: wal data files for standby to restore

      3. tblspc_xxxxx.tar: customized table space files

      4. backup_manifest: backup meta data, is used for pg_verifybackup to verify the backup

   3. Different archive mode base backup, log shipping backup also brings replication_slot to base backup files and to standby afterwards

4. On Primary MP find and Tar the postgresql config files, Including

   1. postgres.conf

   2. pg_ident.conf

   3. pg_hba.conf

5. On Standby MP receive all files generated from Primary server on step 3 and step 2.b

6. Data directory setup: Extract files generated from 2.b and placed to the target data folder assigned before triggering CSD

7. Config directory setup:

   1. Extract files from tar ball recieved on step 4 and put them into the target config directory

   2. Configure the PostgreSQL configuration in log shipping mode according to the CSD parameter and replication slot.

8. If the OS is windows, register windows service for the cluster

9. After setting up data director and config directory, restart standby server

10. Applying the latest changes on configuration coming CSD and persisting configuration data on Control Center