Backing up Redmine -- should the server be shut down?
Hi. While copying or rsync'ing a Redmine installation to another drive, should the server be temporarily shut down? The concern is that the copy might be made while a transaction is occurring, and so the copy might be in some internally inconsistent state.
RE: Backing up Redmine -- should the server be shut down? - Added by Lorenzo Meneghetti over 1 year ago
Hi, if it's a copy I don't see any problem.
Just to be perfectly clear -- the concern isn't that the original will be affected in any way. The concern is that the backup won't be a good backup.
As a hypothetical example, suppose some user performs an action that causes Redmine to update two files; and suppose the backup copy occurs when Redmine has updated one of those files but before it's been able to update the second. Is this something that could not happen? (I'm ignorant of how Redmine stores its information, so maybe there aren't ever two files to update)
When you talk about backing up Redmine what does it mean to you? And what data you are rsync'ing?
a) Backing up the Database you use, e.g., sqlite3, mysql, postgresql?
b) Backing up uploaded files via issues, documents or files module?
c) Backing up the source code or parts of it because of some custom changes?
d) All of the options above?
The answer to your question would depend on what you really mean and probably what application server you use because there might be differences in how they interact with the source code.
Giving some details would help all of us to help you!