Correct config wal-e s3 for minio
Try run PostgreSQL + WAL-E + Minio.
yum install -y https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm
yum install -y postgresql96 postgresql96-server wal-e python-gevent lzop pv python34-pip
/usr/pgsql-9.6/bin/postgresql96-setup initdb
systemctl enable postgresql-9.6
systemctl start postgresql-9.6
mkdir -p /etc/wal-e.d/env
echo "AWS_ACCESS_KEY_ID" > /etc/wal-e.d/env/AWS_ACCESS_KEY_ID
echo "AWS_SECRET_ACCESS_KEY" > /etc/wal-e.d/env/AWS_SECRET_ACCESS_KEY
echo 's3://10.233.60.57:9000' > /etc/wal-e.d/env/WALE_S3_ENDPOINT
echo 's3://minio/pg-backups' > /etc/wal-e.d/env/WALE_S3_PREFIX
chown -R root:postgres /etc/wal-e.d
pip3 install envdir gevent boto
systemctl restart postgresql-9.6
sudo su - postgres
Minio configured as:
I create large ~1 GB random dataset in PostgreSQL
https://gist.github.com/ololobus/5b25c432f208d7eb31051a5f238dffff
But WAL don`t have in Minio.
Log WAL-E
envdir /etc/wal-e.d/env wal-e backup-push /var/lib/pgsql/9.6/data
wal_e.main INFO MSG: starting WAL-E
DETAIL: The subcommand is "backup-push".
STRUCTURED: time=2019-02-12T07:41:01.239297-00 pid=18672
wal_e.operator.backup INFO MSG: start upload postgres version metadata
DETAIL: Uploading to s3://minio/pg-backups/basebackups_005/base_000000010000000000000092_00000040/extended_version.txt.
STRUCTURED: time=2019-02-12T07:43:31.367410-00 pid=18672
wal_e.operator.backup WARNING MSG: blocking on sending WAL segments
DETAIL: The backup was not completed successfully, but we have to wait anyway. See README: TODO about pg_cancel_backup
STRUCTURED: time=2019-02-12T07:43:31.370409-00 pid=18672
NOTICE: pg_stop_backup cleanup done, waiting for required WAL segments to be archived
postgresql backup
add a comment |
Try run PostgreSQL + WAL-E + Minio.
yum install -y https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm
yum install -y postgresql96 postgresql96-server wal-e python-gevent lzop pv python34-pip
/usr/pgsql-9.6/bin/postgresql96-setup initdb
systemctl enable postgresql-9.6
systemctl start postgresql-9.6
mkdir -p /etc/wal-e.d/env
echo "AWS_ACCESS_KEY_ID" > /etc/wal-e.d/env/AWS_ACCESS_KEY_ID
echo "AWS_SECRET_ACCESS_KEY" > /etc/wal-e.d/env/AWS_SECRET_ACCESS_KEY
echo 's3://10.233.60.57:9000' > /etc/wal-e.d/env/WALE_S3_ENDPOINT
echo 's3://minio/pg-backups' > /etc/wal-e.d/env/WALE_S3_PREFIX
chown -R root:postgres /etc/wal-e.d
pip3 install envdir gevent boto
systemctl restart postgresql-9.6
sudo su - postgres
Minio configured as:
I create large ~1 GB random dataset in PostgreSQL
https://gist.github.com/ololobus/5b25c432f208d7eb31051a5f238dffff
But WAL don`t have in Minio.
Log WAL-E
envdir /etc/wal-e.d/env wal-e backup-push /var/lib/pgsql/9.6/data
wal_e.main INFO MSG: starting WAL-E
DETAIL: The subcommand is "backup-push".
STRUCTURED: time=2019-02-12T07:41:01.239297-00 pid=18672
wal_e.operator.backup INFO MSG: start upload postgres version metadata
DETAIL: Uploading to s3://minio/pg-backups/basebackups_005/base_000000010000000000000092_00000040/extended_version.txt.
STRUCTURED: time=2019-02-12T07:43:31.367410-00 pid=18672
wal_e.operator.backup WARNING MSG: blocking on sending WAL segments
DETAIL: The backup was not completed successfully, but we have to wait anyway. See README: TODO about pg_cancel_backup
STRUCTURED: time=2019-02-12T07:43:31.370409-00 pid=18672
NOTICE: pg_stop_backup cleanup done, waiting for required WAL segments to be archived
postgresql backup
add a comment |
Try run PostgreSQL + WAL-E + Minio.
yum install -y https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm
yum install -y postgresql96 postgresql96-server wal-e python-gevent lzop pv python34-pip
/usr/pgsql-9.6/bin/postgresql96-setup initdb
systemctl enable postgresql-9.6
systemctl start postgresql-9.6
mkdir -p /etc/wal-e.d/env
echo "AWS_ACCESS_KEY_ID" > /etc/wal-e.d/env/AWS_ACCESS_KEY_ID
echo "AWS_SECRET_ACCESS_KEY" > /etc/wal-e.d/env/AWS_SECRET_ACCESS_KEY
echo 's3://10.233.60.57:9000' > /etc/wal-e.d/env/WALE_S3_ENDPOINT
echo 's3://minio/pg-backups' > /etc/wal-e.d/env/WALE_S3_PREFIX
chown -R root:postgres /etc/wal-e.d
pip3 install envdir gevent boto
systemctl restart postgresql-9.6
sudo su - postgres
Minio configured as:
I create large ~1 GB random dataset in PostgreSQL
https://gist.github.com/ololobus/5b25c432f208d7eb31051a5f238dffff
But WAL don`t have in Minio.
Log WAL-E
envdir /etc/wal-e.d/env wal-e backup-push /var/lib/pgsql/9.6/data
wal_e.main INFO MSG: starting WAL-E
DETAIL: The subcommand is "backup-push".
STRUCTURED: time=2019-02-12T07:41:01.239297-00 pid=18672
wal_e.operator.backup INFO MSG: start upload postgres version metadata
DETAIL: Uploading to s3://minio/pg-backups/basebackups_005/base_000000010000000000000092_00000040/extended_version.txt.
STRUCTURED: time=2019-02-12T07:43:31.367410-00 pid=18672
wal_e.operator.backup WARNING MSG: blocking on sending WAL segments
DETAIL: The backup was not completed successfully, but we have to wait anyway. See README: TODO about pg_cancel_backup
STRUCTURED: time=2019-02-12T07:43:31.370409-00 pid=18672
NOTICE: pg_stop_backup cleanup done, waiting for required WAL segments to be archived
postgresql backup
Try run PostgreSQL + WAL-E + Minio.
yum install -y https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm
yum install -y postgresql96 postgresql96-server wal-e python-gevent lzop pv python34-pip
/usr/pgsql-9.6/bin/postgresql96-setup initdb
systemctl enable postgresql-9.6
systemctl start postgresql-9.6
mkdir -p /etc/wal-e.d/env
echo "AWS_ACCESS_KEY_ID" > /etc/wal-e.d/env/AWS_ACCESS_KEY_ID
echo "AWS_SECRET_ACCESS_KEY" > /etc/wal-e.d/env/AWS_SECRET_ACCESS_KEY
echo 's3://10.233.60.57:9000' > /etc/wal-e.d/env/WALE_S3_ENDPOINT
echo 's3://minio/pg-backups' > /etc/wal-e.d/env/WALE_S3_PREFIX
chown -R root:postgres /etc/wal-e.d
pip3 install envdir gevent boto
systemctl restart postgresql-9.6
sudo su - postgres
Minio configured as:
I create large ~1 GB random dataset in PostgreSQL
https://gist.github.com/ololobus/5b25c432f208d7eb31051a5f238dffff
But WAL don`t have in Minio.
Log WAL-E
envdir /etc/wal-e.d/env wal-e backup-push /var/lib/pgsql/9.6/data
wal_e.main INFO MSG: starting WAL-E
DETAIL: The subcommand is "backup-push".
STRUCTURED: time=2019-02-12T07:41:01.239297-00 pid=18672
wal_e.operator.backup INFO MSG: start upload postgres version metadata
DETAIL: Uploading to s3://minio/pg-backups/basebackups_005/base_000000010000000000000092_00000040/extended_version.txt.
STRUCTURED: time=2019-02-12T07:43:31.367410-00 pid=18672
wal_e.operator.backup WARNING MSG: blocking on sending WAL segments
DETAIL: The backup was not completed successfully, but we have to wait anyway. See README: TODO about pg_cancel_backup
STRUCTURED: time=2019-02-12T07:43:31.370409-00 pid=18672
NOTICE: pg_stop_backup cleanup done, waiting for required WAL segments to be archived
postgresql backup
postgresql backup
asked 2 mins ago
Anton PatsevAnton Patsev
305
305
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229482%2fcorrect-config-wal-e-s3-for-minio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229482%2fcorrect-config-wal-e-s3-for-minio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown