RIZZASTERBackup Schedule and Storage
/archive/wallpapers/tebex/ · last edited 19 Sep 2023 · Events
We agreed on a daily full backup of the world files, executed at 2:00 AM server time, to minimize impact on gameplay. The backups will be stored on an external USB drive connected to the backup machine, which is powered on only during the backup window. The drive will be rotated weekly, with one drive kept offline as a long-term archive. We will use a script that compresses the world folder into a .tar.gz file, verifies the integrity of the archive, and logs the operation timestamp and file size to a text file.
Each backup must be verified by checking the file size against the previous day’s record and confirming that the archive can be extracted successfully. A monthly test restore will be performed on a separate test server instance using the oldest available backup to ensure data can be recovered. The test will include verifying that the world loads correctly, player data is preserved, and no critical game elements are missing. Results will be documented in the shared log file.
We still need to decide whether to keep a second backup on cloud storage for added redundancy, especially if the physical drive fails. The team is divided on whether the cloud option is necessary given our small user base and low risk of data loss. Additionally, someone needs to set up a reminder system for the monthly test restores to ensure they aren't missed. There is also an open question about what to do if a backup fails—should the team be notified immediately, or is it acceptable to retry once and log it?
The main risk is human error—forgetting to rotate drives or missing a backup window. To mitigate this, we will set up a simple calendar reminder with a recurring event and assign a rotating responsibility for checking the backup status each morning. We also need to ensure that the backup machine doesn’t go to sleep during the backup process. The script will include a command to keep the system awake via systemctl. Lastly, we should document the backup process clearly in the server ops guide so new moderators can follow it without confusion.