gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Data Backup (markdown)

Baptiste Mille-Mathias 2020-12-11 09:10:51 +01:00
parent 42aafbe438
commit 462cfd5e2a
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
Data-Backup.md

@ -11,11 +11,12 @@ Run "weed backup" command on any machine that have enough disk spaces. Assuming
If local volume 5 does not exist, it will be created. All remote needle entries are fetched and compared to local needle entries. The delta is calculated and local missing files are fetched from the volume server.
If you specify -volumeId=87, but volume 87 does not exist, it's ok. No files will be created locally. This gives the opportunity that you can create a backup script simply looping from 1 to 100. All existing volumes will be backed up. The non-existing volumes can also be backed up when they are created remotely.
If you specify `-volumeId=87`, but volume 87 does not exist, it's ok. No files will be created locally. This gives the opportunity that you can create a backup script simply looping from 1 to 100. All existing volumes will be backed up. The non-existing volumes can also be backed up when they are created remotely.
The backup scripts is just one command, not a continuous running service though. High Availability servers will be added later.
# ToDo
# ToDo (from @bmillemathias)
* how to do a consistent backup on a distributed environment (as backup is incremental and for instance done hourly, what is the strategy to restore data of 2 days ago (use filesystem snapshot ? again how to do on distributed environment)
* does backing up master or filer make sense ?
* How to test a backup
* How to restore data (with indication on distributed environment)