About backup and recovery #1357
Replies: 3 comments 10 replies
-
That's right that the "bgsave" command would only produce a snapshot in the backup dir. And you need to copy it to the db dir and restart the Kvrocks. It's trivial and inconvenient, but we plan to improve this by supporting the restore command.
RocksDB allows incremental backup indeed, but we're using checkpoint now. Maybe we can use the backup mechanism when creating the backup.
Yes, we recommend storing the backup in different disks from the DB. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply. I did not find the corresponding option in the |
Beta Was this translation helpful? Give feedback.
-
|
Upd: I noticed that the wiki describes the checkpoint backup method using hard links as not taking up additional storage space and the backups should be deleted in a timely manner. Therefore, I don’t think it’s necessary to change the default output path. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there! add more data and run
|
Beta Was this translation helpful? Give feedback.
-
|
After few tests my understanding is that:
However when i execute First COMPACT + BGSAVE: second COMPACT + BGSAVE: Am I missing something? |
Beta Was this translation helpful? Give feedback.
-
|
@ltagliamonte-dd Yes, you're right. It only supports generating the full DB for now, so you can keep the latest one or two. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry to hijack this discussion but we encountered a weird behavior today related to the
What could be the cause of this and how to prevent it? I deleted the archive folder, hopefully I didn't lose any data. Thanks in advance |
Beta Was this translation helpful? Give feedback.
-
|
@kinoute It’s fine to delete the archive dir and won’t lost any data. And you can reduce rocksdb.wal_size_limit_mb if you want. |
Beta Was this translation helpful? Give feedback.
-
|
@git-hulk Thanks a lot, I will reduce this. Does it have impact on performance if I reduce this number, to lets say, a few Gbs? My rocksdb.write_buffer_size is set to the default, 64Mb (I'm reading the kvrocks.conf comments at the moment). |
Beta Was this translation helpful? Give feedback.
-
|
@git-hulk thanks for the insight, I'm Interested as well in this, what happens in terms of performances if we set |
Beta Was this translation helpful? Give feedback.
-
|
@kinoute It only affects the possibility of the full sync since we use the |
Beta Was this translation helpful? Give feedback.
-
|
@ltagliamonte-dd It wouldn't affect the performance except during the replication time. So you can reduce it to 0 if you didn't use the replication. |
Beta Was this translation helpful? Give feedback.
-
I would like to ask about the recommended backup and recovery methods. According to the information in , it is recommended to use the "bgsave" command to export the full database, but it does not provide a method for importing. Does this mean that the "bgsave" command will generate a "backup" folder, and copying the contents of this folder to a third-party location represents a backup? To restore data, means overwrite the contents of the "db" folder with the contents of the "backup" folder and then restart the kvrocks service. Not sure if I understand correctly.
If I want to perform incremental backup, I need to compare the updated parts in all files myself, which seems to require reading all files at least once (if using methods like calculating the MD5 of files), I am not sure if this is the recommended way
Additionally, I would like to ask if the "backup" folder can be set to a different path. If it is in the same directory as the "db" folder, it seems to require reserving twice the space on the physical hardware for backup.
Beta Was this translation helpful? Give feedback.
All reactions