Backups
What is backed up, how it is encrypted, and what a restore needs.
The console's state is a handful of small files, and losing any of them is unrecoverable: the wallet book, the volume-bot vault, the positions, the account list, and the server secret those four are encrypted under.
What runs
A nightly job archives all of it, encrypts the archive with a passphrase, and keeps the last fourteen. Each archive is verified after it is written, by decrypting it and reading the file list back. An archive that cannot be opened is worse than no archive, because it is believed.
The passphrase
Set once, on the server, by the operator. It is not the account password and not the wallet password, and it is not stored anywhere the archive is.
The archive contains the server secret that the wallet keys are encrypted under. That is deliberate, because a backup of the vault without the key that opens it is not a backup, and it is exactly why the archive itself is encrypted and why the passphrase must live somewhere other than the server.
Restoring
A restore needs two things: an archive, and the passphrase. Given both, the console comes back with every wallet, position and account intact. Given only the archive, it comes back with nothing readable.
An archive on the same disk is not a backup
The nightly job writes to the same machine. A copy pulled off the server regularly is what survives the machine being lost, and that copy is the operator's job rather than the console's.