{"action":"created","issue":{"url":"https://api.github.com/repos/antirez/redis/issues/2463","labels_url":"https://api.github.com/repos/antirez/redis/issues/2463/labels{/name}","comments_url":"https://api.github.com/repos/antirez/redis/issues/2463/comments","events_url":"https://api.github.com/repos/antirez/redis/issues/2463/events","html_url":"https://github.com/antirez/redis/issues/2463","id":63252617,"number":2463,"title":"Redis Cluster: Node Backup & Restore","user":{"login":"benlaplanche","id":2358061,"avatar_url":"https://avatars.githubusercontent.com/u/2358061?v=3","gravatar_id":"","url":"https://api.github.com/users/benlaplanche","html_url":"https://github.com/benlaplanche","followers_url":"https://api.github.com/users/benlaplanche/followers","following_url":"https://api.github.com/users/benlaplanche/following{/other_user}","gists_url":"https://api.github.com/users/benlaplanche/gists{/gist_id}","starred_url":"https://api.github.com/users/benlaplanche/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benlaplanche/subscriptions","organizations_url":"https://api.github.com/users/benlaplanche/orgs","repos_url":"https://api.github.com/users/benlaplanche/repos","events_url":"https://api.github.com/users/benlaplanche/events{/privacy}","received_events_url":"https://api.github.com/users/benlaplanche/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-20T15:49:09Z","updated_at":"2015-03-20T16:17:44Z","closed_at":null,"body":"Backups currently happen on a per node basis, so care has to be taken to ensure they do not all run BGSAVE/SAVE at the same time for performance.\r\n\r\nScripting also has to be in place to manually extract the RDB files and copy them away somewhere.\r\n\r\nYou also need to backup the nodes.conf file to have a chance of doing a restore. \r\n\r\nIt would be great if this was able to be triggered in a central manner.\r\n\r\nRestore is also tricky in that it requires knowledge of the cluster topology. It sounds like you have to recreate the cluster exactly as it was to be able to restore (read drop in) the RDB files you backed up previously. \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/antirez/redis/issues/comments/84059116","html_url":"https://github.com/antirez/redis/issues/2463#issuecomment-84059116","issue_url":"https://api.github.com/repos/antirez/redis/issues/2463","id":84059116,"user":{"login":"antirez","id":65632,"avatar_url":"https://avatars.githubusercontent.com/u/65632?v=3","gravatar_id":"","url":"https://api.github.com/users/antirez","html_url":"https://github.com/antirez","followers_url":"https://api.github.com/users/antirez/followers","following_url":"https://api.github.com/users/antirez/following{/other_user}","gists_url":"https://api.github.com/users/antirez/gists{/gist_id}","starred_url":"https://api.github.com/users/antirez/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/antirez/subscriptions","organizations_url":"https://api.github.com/users/antirez/orgs","repos_url":"https://api.github.com/users/antirez/repos","events_url":"https://api.github.com/users/antirez/events{/privacy}","received_events_url":"https://api.github.com/users/antirez/received_events","type":"User","site_admin":false},"created_at":"2015-03-20T16:17:44Z","updated_at":"2015-03-20T16:17:44Z","body":"This is planned. The idea is to have, more or less, redis-trib able to do the following:\r\n\r\n1. Get the N RDB files from the master.\r\n2. Create a nodes representation in a text file that is part of the backup.\r\n3. Ability to restore it into a new cluster, like part of `create` but `--from-backup`.\r\n\r\nBasically the backup will be a directory, not a file.\r\n\r\nWould be great to have it now, but no time, but, this does not need to wait for v2. We'll get it in the course of Redis 3.0.x."}}