Restore files
Choose the device. For Restore files it must be online.
Choose the restore point: the date and time to go back to.
Browse the backup and select a file or a folder, or take everything in that restore point.
Type where to put the files on the machine. A separate folder is best: check the files, then move them where they belong.
Start the restore and check the result rather than assuming it. Progress appears under Restore History and in Activities.
- A restore never overwrites your current files. If the folder you restore to already exists, the files go into a new folder inside it
- On Linux, a restore puts back owners, permissions, ACLs and SELinux labels
Recover a device
- The hardware case: a machine is gone and a replacement needs its data. The backup belongs to the work, not to the hardware that happened to be running it, so losing the hardware does not lose the work
- The disaster case: the machine is destroyed, stolen, or will not switch on. You can browse and restore its backups without that machine being reachable, or in one piece. Deleted machines whose backups were kept are listed too. This is the case Satkosh is built around
- Recovering onto a different machine is for Administrators only. It asks you to confirm it is you, raises a high-priority alert, emails the people you nominated, and is written to the audit trail. Moving data between machines is also something an attacker would like to do, so it is guarded rather than convenient
Restore a database
- A database loads into a new database beside the live one, named NAME_restored unless you choose another name. A name that already exists is refused, so a restore never overwrites a database, and if a load fails the half-loaded database is removed
- Or give back the dump files, and the console shows the exact commands to load each one. A PostgreSQL dump can also give back a single table