Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Braincase should be locked when backing up #258

Closed
bhavicp opened this issue Sep 17, 2012 · 3 comments
Closed

Braincase should be locked when backing up #258

bhavicp opened this issue Sep 17, 2012 · 3 comments

Comments

@bhavicp
Copy link
Collaborator

bhavicp commented Sep 17, 2012

When backing up, Braincase should be 'locked' and signaled in a polite way.

@bhavicp
Copy link
Collaborator Author

bhavicp commented Sep 17, 2012

This needs to verified that it's actually needed, as no known database tables are currently in use which could go to an inconsistent state.

@hamstar
Copy link
Owner

hamstar commented Sep 18, 2012

I would argue against locking the system. We should use rsync to copy the files to another location because rsync can copy files that are in use. Then tar up those files.

Even without this, the backup process is so quick that the amount of data that would be lost not backed up by not locking before backing up would be negligible.

Even if some data was not backed up, it would still be backed up in another 24 hours so is still within the requirements.

We would of course exclude things like the dokuwiki cache and lockfiles from the backup.

@hamstar
Copy link
Owner

hamstar commented Oct 7, 2012

This doesn't need to happen... we can workaround this using the methods specified in #272.

@hamstar hamstar closed this as completed Oct 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants