{"id":55884,"date":"2020-01-31T00:00:00","date_gmt":"2020-01-30T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/znakomstvo-s-wal-g-sistemoj-bekapirovaniya-postgresql"},"modified":"2020-02-18T14:04:03","modified_gmt":"2020-02-18T11:04:03","slug":"znakomstvo-s-wal-g-sistemoj-bekapirovaniya-postgresql","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/znakomstvo-s-wal-g-sistemoj-bekapirovaniya-postgresql","title":{"rendered":"\u00cent\u00e2lnirea cu sistemul de backup wal-g pentru PostgreSQL","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

WAL-G<\/a><\/noindex> \u2014 un instrument simplu \u0219i eficient pentru backup-ul PostgreSQL \u00een cloud. Din punct de vedere al func\u021bionalit\u0103\u021bii sale de baz\u0103, este un succesor al instrumentului popular WAL-E<\/a><\/noindex>, dar rescris \u00een Go. \u00cens\u0103 la WAL-G exist\u0103 o caracteristic\u0103 nou\u0103 important\u0103 \u2014 copiile delta. Copiile delta WAL-G<\/a><\/noindex> p\u0103streaz\u0103 paginile fi\u0219ierelor care s-au modificat fa\u021b\u0103 de versiunea anterioar\u0103 a backup-ului. \u00cen WAL-G sunt implementate o serie de tehnologii pentru paralelizarea backup-urilor. WAL-G func\u021bioneaz\u0103 mult mai repede dec\u00e2t WAL-E.<\/p>\n

<\/a><\/noindex><\/p>\n

Detalii despre func\u021bionarea wal-g pot fi citite \u00een articolul: Accelereaz\u0103 backup-ul. Prezentarea Yandex<\/a><\/noindex> <\/p>\n

<\/p>\n

Protocolul de stocare S3 a devenit popular pentru stocarea datelor. Unul dintre avantajele S3 este posibilitatea de acces prin API, care permite organizarea unei interac\u021biuni flexibile cu stocarea, inclusiv acces public la citire, \u00een timp ce actualizarea informa\u021biilor \u00een stocare se face doar de c\u0103tre persoane autorizate.<\/p>\n

<\/p>\n

Exist\u0103 mai multe implement\u0103ri care fie sunt deschise, fie private, func\u021bion\u00e2nd pe baza protocolului S3. Ast\u0103zi vom analiza o solu\u021bie popular\u0103 pentru organizarea unor stoc\u0103ri mici \u2014 Minio.<\/p>\n

<\/p>\n

Pentru testarea wal-g, este suficient un server PostgreSQL, iar ca \u00eenlocuitor pentru S3 se folose\u0219te Minio.<\/p>\n

<\/p>\n

Server Minio<\/h2>\n

<\/p>\n

Instalarea Minio<\/p>\n

<\/p>\n

yum -y install yum-plugin-copr\nyum copr enable -y lkiesow\/minio\nyum install -y minio<\/code><\/pre>\n
<\/p>\n
Modific\u0103m AccessKey \u0219i SecretKey \u00een \/etc\/minio\/minio.conf<\/p>\n
<\/p>\n
vi \/etc\/minio\/minio.conf<\/code><\/pre>\n
<\/p>\n
Dac\u0103 nu folosi\u021bi nginx \u00eenainte de Minio, trebuie s\u0103 schimba\u021bi<\/p>\n
<\/p>\n
--address 127.0.0.1:9000<\/code><\/pre>\n
<\/p>\n
--address 0.0.0.0:9000<\/code><\/pre>\n
<\/p>\n
Pornim Minio<\/p>\n
<\/p>\n
systemctl start minio<\/code><\/pre>\n
<\/p>\n
Acces\u0103m interfa\u021ba web Minio http:\/\/ip-adresa-serverului-minio:9000<\/a><\/noindex> \u0219i cre\u0103m un bucket (de exemplu, pg-backups).<\/p>\n
<\/p>\n
Server DB<\/h2>\n
<\/p>\n
WAL-G \u00een rpm \u00eel construiesc eu (Anton Patsev). Github<\/a><\/noindex>, Fedora COPR<\/a><\/noindex>.<\/p>\n
<\/p>\n
Cei care nu au un sistem bazat pe RPM, folosi\u021bi instruc\u021biunile oficiale instruc\u021biunea<\/a><\/noindex> de instalare.<\/p>\n
<\/p>\n
\u00cempreun\u0103 cu binarul wal-g \u00een rpm exist\u0103 scripturi care importa variabile din fi\u0219ierul \/etc\/wal-g.d\/server-s3.conf.<\/p>\n
<\/p>\n
backup-fetch.sh\nbackup-list.sh\nbackup-push.sh\nwal-fetch.sh\nwal-g-run.sh\nwal-push.sh<\/code><\/pre>\n
<\/p>\n
Instal\u0103m wal-g.<\/p>\n
<\/p>\n
yum -y install yum-plugin-copr\nyum copr enable -y antonpatsev\/wal-g\nyum install -y wal-g<\/code><\/pre>\n
<\/p>\n
Verific\u0103m versiunea wal-g.<\/p>\n
<\/p>\n
wal-g --version\nwal-g version v0.2.14<\/code><\/pre>\n
<\/p>\n
Edit\u0103m \/etc\/wal-g.d\/server-s3.conf conform nevoilor.<\/p>\n
<\/p>\n
Fi\u0219ierele de configura\u021bie \u0219i fi\u0219ierele de date utilizate de clusterul bazei de date sunt, tradi\u021bional, p\u0103strate \u00eempreun\u0103 \u00een directorul de date al clusterului, care de obicei este denumit PGDATA<\/code><\/p>\n
<\/p>\n
#!\/bin\/bash\n\nexport PG_VER="9.6"\n\nexport WALE_S3_PREFIX="s3:\/\/pg-backups" # \u0431\u0430\u043a\u0435\u0442, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043c\u044b \u0441\u043e\u0437\u0434\u0430\u043b\u0438 \u0432 S3\nexport AWS_ACCESS_KEY_ID="xxxx" # AccessKey \u0438\u0437 \/etc\/minio\/minio.conf \nexport AWS_ENDPOINT="http:\/\/ip-\u0430\u0434\u0440\u0435\u0441-\u0441\u0435\u0440\u0432\u0435\u0440\u0430-minio:9000"\nexport AWS_S3_FORCE_PATH_STYLE="true"\nexport AWS_SECRET_ACCESS_KEY="yyyy" # SecretKey \u0438\u0437 \/etc\/minio\/minio.conf\n\nexport PGDATA=\/var\/lib\/pgsql\/$PG_VER\/data\/\nexport PGHOST=\/var\/run\/postgresql\/.s.PGSQL.5432 # \u0421\u043e\u043a\u0435\u0442 \u0434\u043b\u044f \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u044f \u043a PostgreSQL\n\nexport WALG_UPLOAD_CONCURRENCY=2 # \u041a\u043e\u043b-\u0432\u043e \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u0434\u043b\u044f \u0437\u0430\u043a\u0430\u0447\u043a\u0438 \nexport WALG_DOWNLOAD_CONCURRENCY=2 # \u041a\u043e\u043b-\u0432\u043e \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u0434\u043b\u044f \u0441\u043a\u0430\u0447\u0438\u0432\u0430\u043d\u0438\u044f\nexport WALG_UPLOAD_DISK_CONCURRENCY=2 # \u041a\u043e\u043b-\u0432\u043e \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u043d\u0430 \u0434\u0438\u0441\u043a\u0435 \u0434\u043b\u044f \u0437\u0430\u043a\u0430\u0447\u043a\u0438\nexport WALG_DELTA_MAX_STEPS=7\nexport WALG_COMPRESSION_METHOD=brotli # \u041a\u0430\u043a\u043e\u0439 \u043c\u0435\u0442\u043e\u0434 \u0441\u0436\u0430\u0442\u0438\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c.\n<\/code><\/pre>\n
<\/p>\n
C\u00e2nd configura\u021bi WAL-G, specifica\u021bi WALG_DELTA_MAX_STEPS \u2014 num\u0103rul maxim de pa\u0219i la care delta backup-ul se \u00eendep\u0103rteaz\u0103 de backup-ul de baz\u0103 \u0219i specifica\u021bi politica de copiere delta. Fie face\u021bi o copie cu ultima delta existent\u0103, fie face\u021bi o delta din backup-ul complet ini\u021bial. Acest lucru este necesar atunci c\u00e2nd o anumit\u0103 component\u0103 a bazei de date se schimb\u0103 constant, acelea\u0219i date sunt \u00een continuare modificate.<\/p>\n
<\/p>\n
Instal\u0103m DB.<\/p>\n
<\/p>\n
yum install -y https:\/\/download.postgresql.org\/pub\/repos\/yum\/reporpms\/EL-7-x86_64\/pgdg-redhat-repo-latest.noarch.rpm\nyum install -y postgresql96 postgresql96-server mc<\/code><\/pre>\n
<\/p>\n
Ini\u021bializ\u0103m baza de date.<\/p>\n
<\/p>\n
\/usr\/pgsql-9.6\/bin\/postgresql96-setup initdb\nInitializing database ... OK<\/code><\/pre>\n
<\/p>\n
Dac\u0103 testa\u021bi pe un server, trebuie s\u0103 modifica\u021bi parametrul wal_level la archive pentru PostgreSQL mai mic de 10 versiuni \u0219i replica pentru PostgreSQL versiunea 10 \u0219i mai mare.<\/p>\n
<\/p>\n
wal_level = archive<\/code><\/pre>\n
<\/p>\n
Vom face backup-ul arhivelor WAL la fiecare 60 de secunde folosind PostgreSQL. Pe produc\u021bie, ve\u021bi avea o alt\u0103 valoare pentru archive_timeout.<\/p>\n
<\/p>\n
archive_mode = on\narchive_command = '\/usr\/local\/bin\/wal-push.sh %p'\narchive_timeout = 60 # Comanda archive_command va fi executat\u0103 la fiecare 60 de secunde.<\/code><\/pre>\n
<\/p>\n
Pornim PostgreSQL<\/p>\n
<\/p>\n
systemctl start postgresql-9.6<\/code><\/pre>\n
<\/p>\n
\u00centr-o consol\u0103 separat\u0103, verific\u0103m jurnalele PostgreSQL pentru erori: (schimba\u021bi postgresql-Wed.log cu cel curent).<\/p>\n
<\/p>\n
tail -fn100 \/var\/lib\/pgsql\/9.6\/data\/pg_log\/postgresql-Wed.log<\/code><\/pre>\n
<\/p>\n
Intr\u0103m \u00een psql.<\/p>\n
<\/p>\n
su - postgres\npsql<\/code><\/pre>\n
<\/p>\n
\u00cen psql cre\u0103m o baz\u0103 de date.<\/p>\n
<\/p>\n
Cre\u0103m o tabel\u0103 \u00een baza de date test1.<\/p>\n
<\/p>\n
create database test1;<\/code><\/pre>\n
<\/p>\n
Trecem la baza de date test.<\/p>\n
<\/p>\n
postgres=# c test1;<\/code><\/pre>\n
<\/p>\n
Cre\u0103m tabela indexing_table.<\/p>\n
<\/p>\n
test1=# CREATE TABLE indexing_table(created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW());<\/code><\/pre>\n
<\/p>\n
Ad\u0103ugarea de date.<\/p>\n
<\/p>\n
\u00cencepem inser\u021bia de date. A\u0219tept\u0103m 10-20 de minute.<\/p>\n
<\/p>\n
#!\/bin\/bash\n# postgres\nwhile true; do\npsql -U postgres -d test1 -c "INSERT INTO indexing_table(created_at) VALUES (CURRENT_TIMESTAMP);"\nsleep 60;\ndone<\/code><\/pre>\n
<\/p>\n
Asigura\u021bi-v\u0103 c\u0103 face\u021bi un backup complet.<\/p>\n
<\/p>\n
su - postgres\n\/usr\/local\/bin\/backup-push.sh<\/code><\/pre>\n
<\/p>\n
Verific\u0103m \u00eenregistr\u0103rile din tabelul din baza de date test1<\/p>\n
<\/p>\n
select * from indexing_table;\n2020-01-29 09:41:25.226198+\n2020-01-29 09:42:25.336989+\n2020-01-29 09:43:25.356069+\n2020-01-29 09:44:25.37381+\n2020-01-29 09:45:25.392944+\n2020-01-29 09:46:25.412327+\n2020-01-29 09:47:25.432564+\n2020-01-29 09:48:25.451985+\n2020-01-29 09:49:25.472653+\n2020-01-29 09:50:25.491974+\n2020-01-29 09:51:25.510178+<\/code><\/pre>\n
<\/p>\n
Linia aceasta reprezint\u0103 timpul curent.<\/p>\n
<\/p>\n
Verific\u0103m lista de backup-uri complete<\/h3>\n
<\/p>\n
\/usr\/local\/bin\/backup-list.sh<\/code><\/pre>\n
<\/p>\n
Testarea recuper\u0103rii<\/h3>\n
<\/p>\n
Recuperare complet\u0103 cu aplicarea tuturor WAL-urilor disponibile.<\/h4>\n
<\/p>\n
Oprim PostgreSQL.<\/p>\n
<\/p>\n
\u0218tergem tot din folderul \/var\/lib\/pgsql\/9.6\/data.<\/p>\n
<\/p>\n
Execut\u0103m scriptul \/usr\/local\/bin\/backup-fetch.sh de la utilizatorul postgres.<\/p>\n
<\/p>\n
su - postgres\n\/usr\/local\/bin\/backup-fetch.sh<\/code><\/pre>\n
<\/p>\n
Extrac\u021bia backup-ului este complet\u0103.<\/p>\n
<\/p>\n
Ad\u0103ug\u0103m recovery.conf \u00een folderul \/var\/lib\/pgsql\/9.6\/data cu urm\u0103torul con\u021binut.<\/p>\n
<\/p>\n
restore_command = 'usr\/local\/bin\/wal-fetch.sh \"%f\" \"%p\"'<\/code><\/pre>\n
<\/p>\n
Pornim PostgreSQL. PostgreSQL va \u00eenclina procesul de recuperare din arhivele WAL, \u0219i abia apoi baza va fi deschis\u0103. <\/p>\n
<\/p>\n
systemctl start postgresql-9.6\ntail -fn100 \/var\/lib\/pgsql\/9.6\/data\/pg_log\/postgresql-Wed.log<\/code><\/pre>\n
<\/p>\n
Recuperare la un timp specific.<\/h4>\n
<\/p>\n
Dac\u0103 dorim s\u0103 restaur\u0103m baza de date p\u00e2n\u0103 la un anumit minut, atunci \u00een recovery.conf ad\u0103ug\u0103m parametrul recovery_target_time \u2014 specific\u0103m la ce or\u0103 s\u0103 restaur\u0103m baza de date.<\/p>\n
<\/p>\n
restore_command = 'usr\/local\/bin\/wal-fetch.sh \"%f\" \"%p\"'\nrecovery_target_time = '2020-01-29 09:46:25'<\/code><\/pre>\n
<\/p>\n
Dup\u0103 restaurare, ne uit\u0103m la tabela indexing_table<\/p>\n
<\/p>\n
 2020-01-29 09:41:25.226198+00\n 2020-01-29 09:42:25.336989+00\n 2020-01-29 09:43:25.356069+00\n 2020-01-29 09:44:25.37381+00\n 2020-01-29 09:45:25.392944+00<\/code><\/pre>\n
<\/p>\n
Pornim PostgreSQL. PostgreSQL va \u00eenclina procesul de recuperare din arhivele WAL, \u0219i abia apoi baza va fi deschis\u0103. <\/p>\n
<\/p>\n
systemctl start postgresql-9.6\ntail -fn100 \/var\/lib\/pgsql\/9.6\/data\/pg_log\/postgresql-Wed.log<\/code><\/pre>\n
<\/p>\n
Testare<\/h3>\n
<\/p>\n
Gener\u0103m o baz\u0103 de date de 1GB, a\u0219a cum este descris aici https:\/\/gist.github.com\/ololobus\/5b25c432f208d7eb31051a5f238dffff<\/a><\/noindex><\/p>\n
<\/p>\n
Cerem dimensiunea bucket-ului dup\u0103 generarea a 1GB de date.<\/p>\n
<\/p>\n
postgres=# SELECT pg_size_pretty(pg_database_size('test1'));\npg_size_pretty\n----------------\n1003 MB<\/code><\/pre>\n
<\/p>\n
s4cmd \u2014 un instrument gratuit de linie de comand\u0103 pentru lucrul cu datele stocate \u00een Amazon S3. Utilitarul este scris \u00een limbajul de programare Python, iar datorit\u0103 acestui lucru poate fi utilizat at\u00e2t pe sistemele de operare Windows, c\u00e2t \u0219i pe cele Linux.<\/p>\n
<\/p>\n
Instal\u0103m s4cmd<\/p>\n
<\/p>\n
pip install s4cmd<\/code><\/pre>\n
<\/p>\n
LZ4<\/h4>\n
<\/p>\n
s4cmd --endpoint-url=http:\\\/\\\/ip-adresa-serverului-minio:9000 --access-key=xxxx --secret-key=yyyy du -r s3:\\\/\\\/pg-backups\n840540822       s3:\\\/\\\/pg-backups\\\/wal_005\\\/\n840 MB \u00een format lz4 doar pentru logurile WAL\n\nBackup complet cu lz4 - 1GB de date\ntime backup_push.sh\nreal 0m18.582s\n\nDimensiunea bucket-ului S3 dup\u0103 backup complet\n\n581480085       s3:\\\/\\\/pg-backups\\\/basebackups_005\\\/\n842374424   s3:\\\/\\\/pg-backups\\\/wal_005\n581 MB ocup\u0103 backup-ul complet<\/code><\/pre>\n
<\/p>\n
LZMA<\/h4>\n
<\/p>\n
Dup\u0103 generarea a 1GB de date\n338413694       s3:\\\/\\\/pg-backups\\\/wal_005\\\/\n338 MB de loguri \u00een format lzma\n\nTimpul de generare a backup-ului complet\ntime backup_push.sh\nreal    5m25.054s\n\nDimensiunea bucket-ului \u00een S3\n270310495       s3:\\\/\\\/pg-backups\\\/basebackups_005\\\/\n433485092   s3:\\\/\\\/pg-backups\\\/wal_005\\\/\n\n270 MB ocup\u0103 backup-ul complet \u00een format lzma<\/code><\/pre>\n
<\/p>\n
Brotli<\/h4>\n
<\/p>\n
Dup\u0103 generarea a 1GB de date\n459229886       s3:\\\/\\\/pg-backups\\\/wal_005\\\/\n459 MB de loguri \u00een format brotli\n\nTimpul de generare a backup-ului complet\nreal    0m23.408s\n\nDimensiunea bucket-ului \u00een S3\n312960942       s3:\\\/\\\/pg-backups\\\/basebackups_005\\\/\n459309262   s3:\\\/\\\/pg-backups\\\/wal_005\\\/\n\n312 MB ocup\u0103 backup-ul complet \u00een format brotli\n<\/code><\/pre>\n
<\/p>\n
Compararea rezultatelor pe grafic.<\/p>\n
<\/p>\n
\"\u00cent\u00e2lnirea<\/p>\n
<\/p>\n
A\u0219a cum se vede, Brotli este comparabil ca m\u0103rime cu LZMA, dar backup-ul se realizeaz\u0103 \u00een timpul LZ4.<\/p>\n
<\/p>\n
Chat-ul comunit\u0103\u021bii de limb\u0103 rus\u0103 PostgreSQL: https:\/\/t.me\/pgsql<\/a><\/noindex><\/p>\n
<\/p>\n
V\u0103 rug\u0103m s\u0103 da\u021bi o stea pe Github dac\u0103 utiliza\u021bi wal-g<\/a><\/noindex><\/p>\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
WAL-G \u2014 \u043f\u0440\u043e\u0441\u0442\u043e\u0439 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u044b\u0439 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442 \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f PostgreSQL \u0432 \u043e\u0431\u043b\u0430\u043a\u0430. \u041f\u043e \u0441\u0432\u043e\u0435\u0439 \u043e\u0441\u043d\u043e\u0432\u043d\u043e\u0439 \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u043e\u043d \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043d\u0430\u0441\u043b\u0435\u0434\u043d\u0438\u043a\u043e\u043c \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u043e\u0433\u043e \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u0430 WAL-E, \u043d\u043e \u043f\u0435\u0440\u0435\u043f\u0438\u0441\u0430\u043d\u043d\u044b\u043c \u043d\u0430 Go. \u041d\u043e \u0432 WAL-G \u0435\u0441\u0442\u044c \u043e\u0434\u043d\u0430 \u0432\u0430\u0436\u043d\u0430\u044f \u043d\u043e\u0432\u0430\u044f \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e\u0441\u0442\u044c \u2014 \u0434\u0435\u043b\u044c\u0442\u0430-\u043a\u043e\u043f\u0438\u0438. \u0414\u0435\u043b\u044c\u0442\u0430-\u043a\u043e\u043f\u0438\u0438 WAL-G \u0445\u0440\u0430\u043d\u044f\u0442 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u044b \u0444\u0430\u0439\u043b\u043e\u0432, \u0438\u0437\u043c\u0435\u043d\u0438\u0432\u0448\u0438\u0435\u0441\u044f \u0441 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0439 \u043a\u043e\u043f\u0438\u0438. \u0412 WAL-G \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u043e \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439 \u043f\u043e \u0440\u0430\u0441\u043f\u0430\u0440\u0430\u043b\u043b\u0435\u043b\u0438\u0432\u0430\u043d\u0438\u044e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":55885,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-55884","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Introducere \u00een sistemul de backup wal-g pentru PostgreSQL | ProHoster","description":"WAL-G \u2014 un instrument simplu \u0219i eficient pentru backup-ul PostgreSQL \u00een cloud.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/znakomstvo-s-wal-g-sistemoj-bekapirovaniya-postgresql","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0417\u043d\u0430\u043a\u043e\u043c\u0441\u0442\u0432\u043e \u0441 wal-g \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439 \u0431\u0435\u043a\u0430\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f PostgreSQL | ProHoster","og:description":"WAL-G \u2014 \u043f\u0440\u043e\u0441\u0442\u043e\u0439 \u0438 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u044b\u0439 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442 \u0434\u043b\u044f \u0440\u0435\u0437\u0435\u0440\u0432\u043d\u043e\u0433\u043e \u043a\u043e\u043f\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f PostgreSQL \u0432 \u043e\u0431\u043b\u0430\u043a\u0430.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/znakomstvo-s-wal-g-sistemoj-bekapirovaniya-postgresql","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-01-30T21:00:00+00:00","article:modified_time":"2020-02-18T11:04:03+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"55884","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:35:40","updated":"2022-09-28 13:58:06","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/55884","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=55884"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/55884\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/55885"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=55884"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=55884"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=55884"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}