Cloud backup
The built-in backup in Gizmo Server reliably saves copies of the database — but locally, on the server's own disk (see Backup for details). This protects you well against database damage: a file got corrupted, an update went wrong, someone cleaned the wrong folder by mistake — the copy is right there, you restore it and keep working. But if the power supply burns out and takes the disk with it, or someone simply steals the server from the club with all the copies inside, local copies are useless — they burned or left together with the server.
Gizmo does not have a separate cloud backup feature yet, but building one yourself is easier than it seems — you just reuse a setting that already exists. You can point the backup storage path (the Storage field) not to the system disk, but to a folder that syncs with the cloud. The cloud client then does all the dirty work, and you only need to set everything up once.
Step 1. Install a cloud client on the server
Install a client for any cloud storage with local folder sync on the server — Google Drive, OneDrive, Dropbox or any other service your company already uses.
This is a practical method that uses existing settings, not a separate built-in Gizmo feature. If Gizmo gets its own integration with cloud storage in the future, this section will be updated.
Step 2. Point backups to the synced folder
In Gizmo Manager, open
→ → .Turn on backup with the toggle — it is off by default, and the other options are unavailable until you turn it on.
Check Maximum Number of Backup Files to Keep (10 by default) and Repeat — the time when the copy is created (0:00 by default).
In the Storage field, enter the full path to the cloud client's synced folder.
Save the settings — from now on, copies are created there, and the cloud client automatically moves them off the server without your involvement.
Make sure the operating system user that runs Gizmo Server has read and write permissions for this folder — otherwise copies simply will not be created, and you will find out at the worst possible moment. This is the same requirement as for a regular local path.
Step 3. Check sync and cloud space from time to time
Make sure the folder actually syncs with the cloud and the files do not just pile up locally without uploading — look at the cloud client's interface and check that the files really go up.
Check that the cloud storage has enough free space for the maximum number of backup files you set in the server settings — if the space limit is smaller than the total size of all copies, some of them simply will not upload.
Result
Database backups are created in the synced folder, and the cloud client automatically moves them off the server — the copies survive even if something happens to the server itself. It is a one-time setup that then works on its own — exactly what makes it worth the effort.