Preserving your configuration data is vital to all systems, and Mutiny is no exception.
Below is a table of options available to you to improve your protection.
*The time to recover depends on the snapshot size, ranging from minutes to hours.
** Some organisations do not allow the open SAMBA port.
| Option | Level | cost | time to recover | Data loss | Notes | resilience to Hardware Failure |
| Snapshot on Appliance | zero | zero | minutes | all back to the last snapshot time. Total loss if appliance loses HDD | Total loss if the appliance fails | NO |
| USB Key in appliance | One | Pounds | minutes to restore, not counting the time to repair/replace the appliance | all back to the last snapshot time | Snapshots are automatically copied to the USB key. It can be used to rebuild appliances. | Yes |
| Snapshot copied from SAMBA** share | One | zero | minutes to restore, not counting the time to repair/replace the appliance | all back to the last snapshot time | It can be used to rebuild an appliance. Require procedure to automate the copy. | Yes |
| Standby appliance | Two | Thousand(s) or less if VM | Minutes* | all back to last snapshot time | Backup is transferred to standby appliance and restored | Yes |
| Cold Standby | Three | Thousand(s) or less if VM (licence upgrade required) | Minutes* | all back to last snapshot time | The backup snapshot is copied automatically to the Cold standby appliance. The user manually restores. | Yes |
| Hot Standby | Four | Thousand(s) requires hardware and a licence | Minutes* | Time taken to swap over (minutes) | The system uses a floating virtual address for polling. | Yes |