Rincian kumaha wal-g jalan tiasa dipendakan dina tulisan:
Protokol gudang S3 geus jadi populér pikeun nyimpen data. Salah sahiji kaunggulan S3 nyaéta kamampuhan pikeun ngakses via API, nu ngidinan Anjeun pikeun ngatur interaksi fléksibel jeung gudang, kaasup aksés dibaca umum, bari ngamutahirkeun informasi dina gudang lumangsung ngan ku jalma otorisasi.
Aya sababaraha palaksanaan panyimpenan umum sareng swasta anu nganggo protokol S3. Dinten ieu kami bakal ningali solusi populér pikeun ngatur gudang leutik - Minio.
Server PostgreSQL tunggal henteu kunanaon pikeun nguji wal-g, sareng Minio dianggo salaku gaganti S3.
Minio Server
Pamasangan Minio
yum -y install yum-plugin-copr
yum copr enable -y lkiesow/minio
yum install -y minio
Édit AccessKey sareng SecretKey dina /etc/minio/minio.conf
vi /etc/minio/minio.conf
Upami anjeun henteu nganggo nginx sateuacan Minio, maka anjeun kedah robih
--address 127.0.0.1:9000
--address 0.0.0.0:9000
Ngaluncurkeun Minio
systemctl start minio
Pindah ka antarmuka wéb Minio
server DB
WAL-G dina rpm dirakit ku kuring (Anton Patsev).
Anu teu boga sistem basis RPM, make resmi
Marengan binér wal-g, rpm ngandung skrip anu ngimpor variabel tina file /etc/wal-gd/server-s3.conf.
backup-fetch.sh
backup-list.sh
backup-push.sh
wal-fetch.sh
wal-g-run.sh
wal-push.sh
Pasang walg.
yum -y install yum-plugin-copr
yum copr enable -y antonpatsev/wal-g
yum install -y wal-g
Mariksa versi wal-g.
wal-g --version
wal-g version v0.2.14
Edit /etc/wal-gd/server-s3.conf pikeun kaperluan anjeun.
Payil konfigurasi sareng file data anu dianggo ku kluster database sacara tradisional disimpen babarengan dina diréktori data kluster, biasa disebut salaku PGDATA
#!/bin/bash
export PG_VER="9.6"
export WALE_S3_PREFIX="s3://pg-backups" # бакет, который мы создали в S3
export AWS_ACCESS_KEY_ID="xxxx" # AccessKey из /etc/minio/minio.conf
export AWS_ENDPOINT="http://ip-адрес-сервера-minio:9000"
export AWS_S3_FORCE_PATH_STYLE="true"
export AWS_SECRET_ACCESS_KEY="yyyy" # SecretKey из /etc/minio/minio.conf
export PGDATA=/var/lib/pgsql/$PG_VER/data/
export PGHOST=/var/run/postgresql/.s.PGSQL.5432 # Сокет для подключения к PostgreSQL
export WALG_UPLOAD_CONCURRENCY=2 # Кол-во потоков для закачки
export WALG_DOWNLOAD_CONCURRENCY=2 # Кол-во потоков для скачивания
export WALG_UPLOAD_DISK_CONCURRENCY=2 # Кол-во потоков на диске для закачки
export WALG_DELTA_MAX_STEPS=7
export WALG_COMPRESSION_METHOD=brotli # Какой метод сжатия использовать.
Nalika ngonpigurasikeun WAL-G, anjeun netepkeun WALG_DELTA_MAX_STEPS - jumlah léngkah anu cadangan délta maksimal tina cadangan dasar, sareng netepkeun kawijakan salinan délta. Boh anjeun nyieun salinan tina délta panungtungan aya, atawa anjeun nyieun délta tina cadangan pinuh aslina. Ieu diperlukeun dina kasus nalika komponén sarua database salawasna ngarobah dina database anjeun, data anu sarua terus ngarobah.
Masang pangkalan data.
yum install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.
noarch.rpm
yum install -y postgresql96 postgresql96-server mc
Urang initialize database.
/usr/pgsql-9.6/bin/postgresql96-setup initdb
Initializing database ... OK
Upami anjeun nguji dina 1 server, anjeun kedah ngonpigurasikeun parameter wal_level pikeun arsip pikeun PostgreSQL kirang ti versi 10, sareng réplika pikeun versi PostgreSQL 10 sareng langkung lami.
wal_level = archive
Hayu urang nyadangkeun arsip WAL unggal 60 detik nganggo PostgreSQL sorangan. Dina prod, anjeun bakal boga nilai archive_timeout béda.
archive_mode = on
archive_command = '/usr/local/bin/wal-push.sh %p'
archive_timeout = 60 # Каждые 60 секунд будет выполнятся команда archive_command.
Ngamimitian PostgreSQL
systemctl start postgresql-9.6
Dina konsol misah, urang tingali dina PostgreSQL log pikeun kasalahan: (ngarobah postgresql-Wed.log ka ayeuna).
tail -fn100 /var/lib/pgsql/9.6/data/pg_log/postgresql-Wed.log
Hayu urang buka psql.
su - postgres
psql
Jieun database dina psql
Jieun tabel dina test database1.
create database test1;
Pindah ka tés database.
postgres=# c test1;
Urang nyieun tabel indexing_table.
test1=# CREATE TABLE indexing_table(created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW());
Nambahan data.
Urang mimitian inserting data. Kami ngantosan 10-20 menit.
#!/bin/bash
# postgres
while true; do
psql -U postgres -d test1 -c "INSERT INTO indexing_table(created_at) VALUES (CURRENT_TIMESTAMP);"
sleep 60;
done
Pastikeun pikeun nyieun cadangan lengkep.
su - postgres
/usr/local/bin/backup-push.sh
Urang kasampak di rékaman dina tabel dina test database1
select * from indexing_table;
2020-01-29 09:41:25.226198+
2020-01-29 09:42:25.336989+
2020-01-29 09:43:25.356069+
2020-01-29 09:44:25.37381+
2020-01-29 09:45:25.392944+
2020-01-29 09:46:25.412327+
2020-01-29 09:47:25.432564+
2020-01-29 09:48:25.451985+
2020-01-29 09:49:25.472653+
2020-01-29 09:50:25.491974+
2020-01-29 09:51:25.510178+
String mangrupikeun waktos ayeuna.
Tempo daptar cadangan lengkep
/usr/local/bin/backup-list.sh
nguji recovery
Pamulihan lengkep sareng ngagulung sadayana WAL anu sayogi.
Eureun Postgresql.
Hapus sadayana tina folder /var/lib/pgsql/9.6/data.
Jalankeun skrip /usr/local/bin/backup-fetch.sh salaku pangguna postgres.
su - postgres
/usr/local/bin/backup-fetch.sh
Nyadangkeun ékstraksi réngsé.
Tambahkeun recovery.conf kana folder /var/lib/pgsql/9.6/data kalawan eusi handap.
restore_command = '/usr/local/bin/wal-fetch.sh "%f" "%p"'
Urang ngamimitian PostgreSQL. PostgreSQL bakal ngamimitian prosés pamulihan tina WAL anu diarsipkeun, teras databasena bakal dibuka.
systemctl start postgresql-9.6
tail -fn100 /var/lib/pgsql/9.6/data/pg_log/postgresql-Wed.log
Pamulihan pikeun waktos anu tangtu.
Lamun urang hayang mulangkeun database nepi ka menit nu tangtu, lajeng urang tambahkeun recovery_target_time parameter recovery.conf - urang nunjukkeun dina naon waktos mulangkeun database.
restore_command = '/usr/local/bin/wal-fetch.sh "%f" "%p"'
recovery_target_time = '2020-01-29 09:46:25'
Saatos recovery, tingali tabel indexing_table
2020-01-29 09:41:25.226198+00
2020-01-29 09:42:25.336989+00
2020-01-29 09:43:25.356069+00
2020-01-29 09:44:25.37381+00
2020-01-29 09:45:25.392944+00
Urang ngamimitian PostgreSQL. PostgreSQL bakal ngamimitian prosés pamulihan tina WAL anu diarsipkeun, teras databasena bakal dibuka.
systemctl start postgresql-9.6
tail -fn100 /var/lib/pgsql/9.6/data/pg_log/postgresql-Wed.log
Tés
Ngahasilkeun database 1GB sakumaha anu dijelaskeun di dieu
Nyuhunkeun ukuran ember saatos ngahasilkeun 1GB data.
postgres=# SELECT pg_size_pretty(pg_database_size('test1'));
pg_size_pretty
----------------
1003 MB
s4cmd mangrupikeun alat garis paréntah gratis pikeun damel sareng data anu aya dina panyimpenan Amazon S3. Utilitasna ditulis dina basa pamrograman python, sareng kusabab ieu tiasa dianggo dina sistem operasi Windows sareng Linux.
Masang s4cmd
pip install s4cmd
LZ4
s4cmd --endpoint-url=http://ip-адрес-сервера-minio:9000 --access-key=xxxx --secret-key=yyyy du -r s3://pg-backups
840540822 s3://pg-backups/wal_005/
840 МБ в формате lz4 только WAL логов
Полный бекап с lz4 - 1GB данных
time backup_push.sh
real 0m18.582s
Размер S3 бакета после полного бекапа
581480085 s3://pg-backups/basebackups_005/
842374424 s3://pg-backups/wal_005
581 МБ занимает полный бекап
LZMA
После генерации 1ГБ данных
338413694 s3://pg-backups/wal_005/
338 мб логов в формате lzma
Время генерации полного бекапа
time backup_push.sh
real 5m25.054s
Размер бакета в S3
270310495 s3://pg-backups/basebackups_005/
433485092 s3://pg-backups/wal_005/
270 мб занимает полный бекап в формате lzma
Brotli
После генерации 1ГБ данных
459229886 s3://pg-backups/wal_005/
459 мб логов в формате brotli
Время генерации полного бекапа
real 0m23.408s
Размер бакета в S3
312960942 s3://pg-backups/basebackups_005/
459309262 s3://pg-backups/wal_005/
312 мб занимает полный бекап в формате brotli
Ngabandingkeun hasil dina bagan.
Sakumaha anjeun tiasa tingali, Brotli comparable dina ukuran LZMA, tapi cadangan dipigawé dina waktos LZ4.
Obrolan komunitas PostgreSQL anu nyarios Rusia:
Punten pasihan bintang ka Github upami anjeun nganggo
sumber: www.habr.com