Change Details

==== Value proposition (why do we need to do this)? As a manager, I want to ensure that our users data is not lost or corrupted. As we invest more into this application, we should be more rigorous about its operational methods. ==== Functionality/software changes [] Create a cron job to dump the database to disk. Should run once a day. Files should be stored to NFS for redundancy. [] Optional: send an email or some kind of notice after each successful backup (depends on how often the backup is taken). Redirect the cron job output to /dev/null so we can only output if there's an error ==== User interface changes None ==== QA/Testing [] After deployment, ensure that the files are valid and that the cron job completes regularly.

==== Value proposition (why do we need to do this)? As a manager, I want to ensure that our users data is not lost or corrupted. As we invest more into this application, we should be more rigorous about its operational methods. ==== Functionality/software changes [] Create a cron job to dump the database to disk. Should run once a day. Files should be stored to NFS for redundancy. [] Optional: send an email or some kind of notice after each successful backup (depends on how often the backup is taken). Redirect the cron job output to /dev/null so we can only output if there's an error ==== User interface changes None ==== QA/Testing [] After deployment, ensure that the files are valid and that the cron job completes regularly. Restore the data to an empty DB to validate the dump.

==== Value proposition (why do we need to do this)? As a manager, I want to ensure that our users data is not lost or corrupted. As we invest more into this application, we should be more rigorous about its operational methods. ==== Functionality/software changes [] Create a cron job to dump the database to disk. Should run once a day. Files should be stored to NFS for redundancy. [] Optional: send an email or some kind of notice after each successful backup (depends on how often the backup is taken). Redirect the cron job output to /dev/null so we can only output if there's an error ==== User interface changes None ==== QA/Testing [] After deployment, ensure that the files are valid and that the cron job completes regularly. Restore the data to an empty DB to validate the dump.