Yhat recommends periodically making backups of ScienceOps for both disaster recovery and posterity. It's a good habit to get into and doesn't take much time or effort.
Backups can be used to restore the system to point-in-time snapshots of ScienceOp. This can be done either on the same system where the backups were made or on a separate, backup system.
ScienceOps ships with a set of utility scripts for managing data backups and recoveries. In addition to performing the core backup and recovery activities, these scripts can be used for automation (i.e. automatically performing a nightly backup).
Backups should be made at a minimum of once per month--though a more frequent schedule is encouraged. It's likely that your company will have an IT policy for application backup frequency. If that is the case, you should obviously adhere to this schedule.
It's also recommended that you encrypt your backup files.
- SSH into the master node on ScienceOps.
If neccessary Create a private/public key for encrypting your backups. It is important that you save these files!
openssl genrsa -out private_key.pem 2048 openssl rsa -in private_key.pem -out public_key.pem -outform PEM -pubout
- Run the
scienceops-backupscript. This will generate a file called
scienceups-backup.tar.gz(if desired you can rename this file by passing an argument to a filename).
- Run the
- Save the backup file to a remote location (i.e. S3, an FTP server, or another remote file store).
That's it! In the event of a disaster, you can now recover your system using the