{"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\/en\/blog\/administrirovanie\/znakomstvo-s-wal-g-sistemoj-bekapirovaniya-postgresql","title":{"rendered":"Introduction to the wal-g PostgreSQL Backup System","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

WAL-G<\/a><\/noindex> \u2014 a simple and effective tool for backing up PostgreSQL to the cloud. In terms of its core functionality, it is the successor of the popular tool WAL-E<\/a><\/noindex>, but rewritten in Go. However, WAL-G has one important new feature \u2014 delta backups. Delta backups WAL-G<\/a><\/noindex> store the file pages that have changed since the last backup version. WAL-G implements many technologies for parallelizing backups. WAL-G operates much faster than WAL-E.<\/p>\n

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

You can read more about how wal-g works in the article: Speeding Up Backups. Yandex Lecture<\/a><\/noindex> <\/p>\n

<\/p>\n

The S3 storage protocol has become popular for data storage. One of the advantages of S3 is the ability to access it via API, allowing for flexible interaction with the storage, including public read access, while information updates to the storage are performed only by authorized individuals.<\/p>\n

<\/p>\n

There are both open and private implementations of storages that operate on the S3 protocol. Today, we will look at a popular solution for organizing small storages \u2014 Minio.<\/p>\n

<\/p>\n

For testing wal-g, one PostgreSQL server is sufficient, and Minio is used as a replacement for S3.<\/p>\n

<\/p>\n

Minio Server<\/h2>\n

<\/p>\n

Installing 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
Edit AccessKey and SecretKey in \/etc\/minio\/minio.conf<\/p>\n
<\/p>\n
vi \/etc\/minio\/minio.conf<\/code><\/pre>\n
<\/p>\n
If you are not using nginx in front of Minio, you will need to change<\/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
Start Minio<\/p>\n
<\/p>\n
systemctl start minio<\/code><\/pre>\n
<\/p>\n
Access the Minio web interface http:\/\/server-minio-ip-address:9000<\/a><\/noindex> and create a bucket (for example, pg-backups).<\/p>\n
<\/p>\n
Database Server<\/h2>\n
<\/p>\n
I (Anton Patsev) build WAL-G in rpm. Github<\/a><\/noindex>, Fedora COPR<\/a><\/noindex>.<\/p>\n
<\/p>\n
For those who do not use an RPM-based system, please refer to the official guide<\/a><\/noindex> installation instructions.<\/p>\n
<\/p>\n
Along with the wal-g binary in rpm, there are scripts that import variables from the file \/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
Install 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
Check the version of wal-g.<\/p>\n
<\/p>\n
wal-g --version\nwal-g version v0.2.14<\/code><\/pre>\n
<\/p>\n
Edit \/etc\/wal-g.d\/server-s3.conf according to your needs.<\/p>\n
<\/p>\n
Configuration files and data files used by the database cluster are traditionally stored together in the cluster's data directory, which is usually referred to as 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
When setting up WAL-G, you specify WALG_DELTA_MAX_STEPS \u2014 the maximum number of steps that the delta backup can lag behind the base backup, and you define the delta copy policy. You either make a copy from the latest existing delta or create a delta from the initial full backup. This is necessary in case the same component of the database is constantly changing with the same data.<\/p>\n
<\/p>\n
Installing the database.<\/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
Initializing the database.<\/p>\n
<\/p>\n
\/usr\/pgsql-9.6\/bin\/postgresql96-setup initdb\nInitializing database ... OK<\/code><\/pre>\n
<\/p>\n
If you are testing on one server, you need to reconfigure the wal_level parameter to archive for PostgreSQL versions less than 10, and to replica for PostgreSQL version 10 and above.<\/p>\n
<\/p>\n
wal_level = archive<\/code><\/pre>\n
<\/p>\n
We will back up the WAL archives every 60 seconds using PostgreSQL itself. In production, you will have a different value for archive_timeout.<\/p>\n
<\/p>\n
archive_mode = on\narchive_command = '\/usr\/local\/bin\/wal-push.sh %p'\narchive_timeout = 60 # The archive_command will be executed every 60 seconds.<\/code><\/pre>\n
<\/p>\n
Starting PostgreSQL<\/p>\n
<\/p>\n
systemctl start postgresql-9.6<\/code><\/pre>\n
<\/p>\n
In a separate console, check the PostgreSQL logs for errors: (replace postgresql-Wed.log with the current one).<\/p>\n
<\/p>\n
tail -fn100 \/var\/lib\/pgsql\/9.6\/data\/pg_log\/postgresql-Wed.log<\/code><\/pre>\n
<\/p>\n
Accessing psql.<\/p>\n
<\/p>\n
su - postgres\npsql<\/code><\/pre>\n
<\/p>\n
Creating a database in psql.<\/p>\n
<\/p>\n
Creating a table in the database test1.<\/p>\n
<\/p>\n
create database test1;<\/code><\/pre>\n
<\/p>\n
Switching to the database test.<\/p>\n
<\/p>\n
postgres=# c test1;<\/code><\/pre>\n
<\/p>\n
Creating the table indexing_table.<\/p>\n
<\/p>\n
test1=# CREATE TABLE indexing_table(created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW());<\/code><\/pre>\n
<\/p>\n
Adding data.<\/p>\n
<\/p>\n
Starting data insertion. Waiting for 10-20 minutes.<\/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
Make sure to take a full backup.<\/p>\n
<\/p>\n
su - postgres\n\/usr\/local\/bin\/backup-push.sh<\/code><\/pre>\n
<\/p>\n
Viewing records in the table of the database 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
The row represents the current time.<\/p>\n
<\/p>\n
Checking the list of full backups<\/h3>\n
<\/p>\n
\/usr\/local\/bin\/backup-list.sh<\/code><\/pre>\n
<\/p>\n
Testing restoration<\/h3>\n
<\/p>\n
Full restoration by applying all available WAL.<\/h4>\n
<\/p>\n
Stopping PostgreSQL.<\/p>\n
<\/p>\n
Deleting everything from the folder \/var\/lib\/pgsql\/9.6\/data.<\/p>\n
<\/p>\n
Running the script \/usr\/local\/bin\/backup-fetch.sh as the postgres user.<\/p>\n
<\/p>\n
su - postgres\n\/usr\/local\/bin\/backup-fetch.sh<\/code><\/pre>\n
<\/p>\n
Backup extraction complete.<\/p>\n
<\/p>\n
Adding recovery.conf to the folder \/var\/lib\/pgsql\/9.6\/data with the following content.<\/p>\n
<\/p>\n
restore_command = '\/usr\/local\/bin\/wal-fetch.sh \"%f\" \"%p\"'<\/code><\/pre>\n
<\/p>\n
Starting PostgreSQL. PostgreSQL will initiate the recovery process from the archived WAL, and only then will the database open. <\/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
Restoration to a specific time.<\/h4>\n
<\/p>\n
If we want to restore the database to a specific minute, we add the recovery_target_time parameter in recovery.conf \u2014 specifying the time to which we want to restore the database.<\/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
After the restoration, we check the 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
Starting PostgreSQL. PostgreSQL will initiate the recovery process from the archived WAL, and only then will the database open. <\/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
Testing<\/h3>\n
<\/p>\n
We generate a 1GB database as described here. https:\/\/gist.github.com\/ololobus\/5b25c432f208d7eb31051a5f238dffff<\/a><\/noindex><\/p>\n
<\/p>\n
We request the size of the bucket after generating 1GB of data.<\/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 a free command-line tool for working with data stored in Amazon S3. The utility is written in Python, allowing it to be used on both Windows and Linux operating systems.<\/p>\n
<\/p>\n
Installing s4cmd<\/p>\n
<\/p>\n
pip install s4cmd<\/code><\/pre>\n
<\/p>\n
LZ4<\/h4>\n
<\/p>\n
s4cmd --endpoint-url=http:\/\/server-ip-address-minio:9000 --access-key=xxxx --secret-key=yyyy du -r s3:\/\/pg-backups\n840540822       s3:\/\/pg-backups\/wal_005\/\n840 MB in lz4 format just for WAL logs\n\nFull backup with lz4 - 1GB data\ntime backup_push.sh\nreal 0m18.582s\n\nSize of the S3 bucket after the full backup\n\n581480085       s3:\/\/pg-backups\/basebackups_005\/\n842374424   s3:\/\/pg-backups\/wal_005\n581 MB is the size of the full backup<\/code><\/pre>\n
<\/p>\n
LZMA<\/h4>\n
<\/p>\n
After generating 1GB of data\n338413694       s3:\/\/pg-backups\/wal_005\/\n338 MB of logs in lzma format\n\nTime taken for generating the full backup\ntime backup_push.sh\nreal    5m25.054s\n\nSize of the bucket in S3\n270310495       s3:\/\/pg-backups\/basebackups_005\/\n433485092   s3:\/\/pg-backups\/wal_005\/\n\n270 MB is the size of the full backup in lzma format<\/code><\/pre>\n
<\/p>\n
Brotli.<\/h4>\n
<\/p>\n
After generating 1GB of data\n459229886       s3:\/\/pg-backups\/wal_005\/\n459 MB of logs in brotli format\n\nTime taken for generating the full backup\nreal    0m23.408s\n\nSize of the bucket in S3\n312960942       s3:\/\/pg-backups\/basebackups_005\/\n459309262   s3:\/\/pg-backups\/wal_005\/\n\n312 MB is the size of the full backup in brotli format\n<\/code><\/pre>\n
<\/p>\n
Comparison of results in the chart.<\/p>\n
<\/p>\n
\"Introduction<\/p>\n
<\/p>\n
As we can see, Brotli is comparable in size to LZMA, but the backup is completed in the time it takes for LZ4.<\/p>\n
<\/p>\n
Chat for the Russian-speaking PostgreSQL community: https:\/\/t.me\/pgsql<\/a><\/noindex><\/p>\n
<\/p>\n
Please give a star on Github if you are using wal-g<\/a><\/noindex><\/p>\n
Source: 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\udd47Introduction to the wal-g PostgreSQL backup system | ProHoster","description":"WAL-G \u2014 a simple and effective tool for backing up PostgreSQL to the cloud.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/znakomstvo-s-wal-g-sistemoj-bekapirovaniya-postgresql","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","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\/en\/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\/en\/wp-json\/wp\/v2\/posts\/55884","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=55884"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/55884\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/55885"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=55884"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=55884"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=55884"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}