{"action":"opened","issue":{"url":"https://api.github.com/repos/zalando/patroni/issues/354","repository_url":"https://api.github.com/repos/zalando/patroni","labels_url":"https://api.github.com/repos/zalando/patroni/issues/354/labels{/name}","comments_url":"https://api.github.com/repos/zalando/patroni/issues/354/comments","events_url":"https://api.github.com/repos/zalando/patroni/issues/354/events","html_url":"https://github.com/zalando/patroni/issues/354","id":187983854,"number":354,"title":"Add restore from backup support","user":{"login":"ants","id":64938,"avatar_url":"https://avatars.githubusercontent.com/u/64938?v=3","gravatar_id":"","url":"https://api.github.com/users/ants","html_url":"https://github.com/ants","followers_url":"https://api.github.com/users/ants/followers","following_url":"https://api.github.com/users/ants/following{/other_user}","gists_url":"https://api.github.com/users/ants/gists{/gist_id}","starred_url":"https://api.github.com/users/ants/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ants/subscriptions","organizations_url":"https://api.github.com/users/ants/orgs","repos_url":"https://api.github.com/users/ants/repos","events_url":"https://api.github.com/users/ants/events{/privacy}","received_events_url":"https://api.github.com/users/ants/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-08T12:50:31Z","updated_at":"2016-11-08T12:50:31Z","closed_at":null,"body":"A feature request I got: when restoring a cluster from backup one has to make sure all Patroni instances are shut down before replacing one data dir from backup, doing the whole recovery dance and possibly adjusting `/optime/leader` and then bringing the nodes back up in correct order. Would be nice to have some tooling for that to reduce room for operator errors and speed things up. Ideally make a restore from backup scriptable.\r\n\r\nSomething along the lines of:\r\n\r\n1. patronictl backup-recovery init - shut down postgresql on all nodes.\r\n2a. patronictl backup-recovery complete - start postgres, make it the leader, update /optime/leader, reinit standby's.\r\n2b. patronictl backup-recovery abort - start rest of the cluster, reinit current node.\r\n\r\nI'll leave this as a place holder until the idea has had some time to develop."}}
{"actor":{"display_login":"ants"}}