Khó Chịu Trong Lòng

1. Download MySQL packages from Oracle eDelivery (Server, Shell, ...) [root@mysql-saigon mysql8]# ls -l total 961092 -rw-r--r--. 1 root root   4010566 Mar 31 16:46 mysql-commercial-backup-8.0.37-1.1.el9.x86_64.rpm -rw-r--r--. 1 root root  20388471 Mar 31 16:46 mysql-commercial-backup-debuginfo-8.0.37-1.1.el9.x86_64.rpm -rw-r--r--. 1 root root   4105053 Mar 31 16:46 mysql-commercial-client-8.0.37-1.1.el9.x86_64.rpm -rw-r--r--. 1 root root  27305094 Mar 31 16:46 mysql-commercial-client-debuginfo-8.0.37-1.1.el9.x86_64.rpm -rw-r--r--. 1 root root   1457867 Mar 31 16:46 mysql-commercial-client-plugins-8.0.37-1.1.el9.x86_64.rpm -rw-r--r--. 1 root root   2052547 Mar 31 16:46 mysql-commercial-client-plugins-debuginfo-8.0.37-1.1.el9.x86_64.rpm -rw-r--r--. 1 root root    570629 Mar 31 16:46 mysql-commercial-common-8.0.37-1.1.el9.x86_64.rpm -rw-r--r--. 1 root root   7680309 Mar 31 16:46 mysql-commercial-debuginfo-8.0.37-1.1.el9....

In this section, we will install pgBackRest using with  EPAS  (EDB Enterprise Advance Server). So we need to pay attention to something such as: User is enterprisedb , not postgres Grant right privileges to enterprisedb user 1. Configuring Postgres YUM repository [root@edb-nhatrang ~]# dnf repolist  [root@edb-nhatrang ~]# dnf install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-9-x86_64/pgdg-redhat-repo-latest.noarch.rpm [root@edb-nhatrang ~]# dnf repolist  2. Configuring EPEL Repository [root@edb-nhatrang ~]# dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm [root@edb-nhatrang ~]# dnf repolist  3. Install pgBackRest [root@edb-nhatrang ~]# dnf install pgbackrest Using EDB Postgres Advanced Server, the enterprisedb system user will execute the pgbackrest command. The following commands will change the ownership of the pgBackRest directories: [root@edb-nhatrang ~]# chown -R enterprisedb: /var/lib/pgbackrest [root@ed...

  Note : The  recover  command is used to recover a whole server. Remote recovery -  Add the --remote-ssh-command  option to the invocation of the recovery command.  Doing this will allow Barman to execute the copy on a remote server, using the provided command to connect to the remote host.  The SSH connection between Barman and the remote host  must   use the public key exchange authentication method. Barman wraps PostgreSQL's Point-in-Time Recovery (PITR), allowing you to specify a recovery target, either as a timestamp , as a restore label , or as a transaction ID . Barman 2.4 also adds the --standby-mode option for the recover command which, if specified, properly configures the recovered instance as a standby by creating a standby.signal file (from PostgreSQL versions lower than 12), or by adding standby_mode = on to the generated recovery configuration. Barman allows you to specify a target timeline for recovery using the --target-t...

In  Part I , we have already configured backup via Streaming protocol. In this section, we will backup database with this method. Note : The reuse_backup option can’t be used with the postgres backup method at this time If a backup has been compressed using the backup_compression option then barman recover is able to uncompress the backup on recovery. Using the recovery_staging_path option in order to choose a suitable location for the staging directory to unpcompress. S et recovery_staging_path in the global/server config or use the --recovery-staging-path option with the barman recover command 1. Check information On Database server edb=# select * from pg_replication_slots; -[ RECORD 1 ]-------+----------- slot_name            | barman plugin               | slot_type            | physical datoid ...