| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | baserock_backup: Make backups run automatically | Sam Thursfield | 2015-05-22 | 1 | -0/+9 |
| | | | | | | | | | This should have happened already, but I forgot that 'crond' won't be running automatically. The backup VM hosted at Codethink was powered off and back on at some point, backups didn't run after that point. Change-Id: I10f6b73c2947631001040099074f373a9ea5464e | ||||
| * | Add a simple data backup mechanism | Sam Thursfield | 2015-03-30 | 1 | -0/+29 |
| The technique used is: create a new SSH key for backup automation, and authorize it to log in as 'root' to instances. To reduce potential harm if the key somehow gets compromised, it is limited to logging in from a single IP, and it is limited to running the 'backup-snapshot' program on the instances. Inside each instance, the `backup-snapshot` script is used as a wrapper for the `rsync --server` process. This script pauses running services, takes a snapshot of the data volume, and then runs the RSync server. Change-Id: I3c98ffe3dc2fa1373bd0df2388145636e491bf57 | |||||
 |
index : baserock/baserock/infrastructure.git | |
| gitlab.com: baserock/infrastructure.git |
| summaryrefslogtreecommitdiff |