Replies: 1 comment
-
|
one idea is to use their cluster concept to keep a read only copy up to date, and then to backup this read only copy. Note that I have never actually done this so I cannot say for sure if this would work. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
so I recently faced the issue that due to one of our developers making a mistake the storage ended up being corrupted - also the continous backup was damaged and did not start. Our solution was to roll back to the full backup which we create every hour - this worked fine.
Now I have seen that whenever we create the full backup the storage is halting for a couple seconds until the backup is done. In these couple seconds all threads wanting to write data have to wait aswell which could be a problem.
Is there any other way to make a full backup in the same manor so that my threads wanting to write to the storage do not get blocked? I do not want to rely on the storage/continous backup alone because of the experience we had with this incident.
Beta Was this translation helpful? Give feedback.
All reactions