Backing up to a file server or business cloud
SFTP, FTP and FTPS, WebDAV (Nextcloud, ownCloud, a NAS), Azure Blob Storage and Google Cloud Storage: the account, its server key, the folder, and what differs from a drive.
On this page
The File server or cloud destination backs up to a place you already have: an SFTP, FTP or FTPS server, a WebDAV server such as Nextcloud, ownCloud or a NAS, an Azure Blob Storage container, or a Google Cloud Storage bucket. Genie9 never holds your data. File server and business cloud destinations are part of Pro and Server.
Before you start#
| Kind | What you need from the server or the provider |
|---|---|
| SFTP server | its name or address, the port if it is not 22, a user name, and a password or a private key |
| FTPS server | its name, the port if it is not 21 (990 for implicit TLS), a user name and a password |
| FTP server | the same as FTPS. Plain FTP sends the password and the files unencrypted: use it only on your own network |
| WebDAV | the WebDAV address, for example https://cloud.example.com/remote.php/dav/files/you for Nextcloud, a user name and a password (an app password when the account signs in with two steps) |
| Azure Blob Storage | the storage account name, an access key (key1 under Access keys, or its connection string), and a container. The container is made by the first backup if it is not there |
| Google Cloud Storage | a service account key (the JSON file Google Cloud's console downloads) for an account with the Storage Object Admin role on the bucket, and the bucket, which must already exist |
Step 1: Add the account#
An account holds the sign-in, so several jobs can share it.
- Open Settings ▸ Network & credentials, and under File servers and other clouds click Add account. (Or click New account on the wizard's Where step.)
- Kind: one of the six above.
- Account name: anything, for example Office NAS.
- Fill in what the kind asks for. Passwords and keys are sent to the agent once and stored encrypted on this PC; they are never shown again. To change an account later, leave the password empty to keep the stored one.
- Folder to test (optional): a folder there; the test also writes and removes a small file in it.
- Click Test, then Save account.
File server account - trusting an SFTP server's key
An SFTP server's key#
An SFTP server proves who it is with a key. The first Test asks the server for its key, shows its fingerprint (SHA256: and 43 letters and digits), and signs in to nothing: your password has not been sent yet.
- Check the fingerprint with the server. On a Linux server or a NAS,
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pubprints it; many NAS settings pages show it too. - Tick I checked this fingerprint with the server, and I trust it.
- Click Test again. Now GBM AI signs in, with the key it trusts.
- Save account. The account keeps that key.
From then on every backup checks the server's key before it sends anything. A server that shows another key is refused with E-DEST-012, and nothing is sent to it. If the server was reinstalled or its key renewed, open the account, Test, check the new fingerprint and trust it again. If you know of no such change, someone may be posing as the server: do not trust the new key.
Step 2: The destination in the wizard#
- On the Where step choose File server or cloud.
- Account: pick the account. With one account it is picked for you.
- For Azure, type the Container; for Google Cloud Storage, the Bucket. A file server's name comes from the account.
- Folder: it starts as the job's name. On an SFTP or FTP server it is inside the account's home folder; on WebDAV, inside the WebDAV address. It is made on the first backup. Give each job its own folder.
- Bandwidth limit: in Mbit/s, 0 for unlimited.
- Click Test destination: it signs in, writes a small probe file and removes it. Reachable and writable means the job is ready.
The full address is shown under the fields, for example sftp://nas.office.lan/Documents.
Wizard step 2 - a file server as destination
What is different from a drive#
- Only the backup's files travel. The catalogue of what each backup holds stays on this PC, and a copy of each backup's manifest goes beside its files. Finding a file and choosing what to restore never downloads the whole backup.
- Small files are packed, as for a bucket: thousands of small files become a few dozen uploads.
- A server that is off is waited for. A backup that cannot reach the server waits up to 15 minutes, as it does for an unplugged drive, then stops with
E-DEST-001. Wrong passwords and refused rights stop the backup at once: waiting cannot fix them. - Verification reads everything back. Verify files after each run downloads what the run wrote and checks it. On a slow connection, or where the provider charges for downloads, you can turn it off on the Settings step.
- A second copy can go here. A backup on a drive or a share can keep its second copy on a file server or another cloud (Pro): Keeping a second copy. A backup kept on a file server or in the cloud keeps a second copy too, on a drive at home or with another provider: A copy of a cloud backup.
- The proxy applies. These connections go through the proxy in Settings ▸ Network & credentials, unless the server is on its Never use the proxy for list. SFTP and FTP go through the proxy's tunnel (HTTP CONNECT), which the proxy must allow to the server's port.
- No Object Lock. Locking backups is S3's; see Locking backups in an S3 bucket.
- Restore on another PC. A new PC opens these backups with Restore ▸ Open backups… ▸ A file server or cloud…: Restoring backups from another PC.
Troubleshooting#
"The server refused the sign-in" (E-DEST-003)#
The user name or password is wrong, the key is not accepted, or the user has no rights on that folder. On Nextcloud with two-step sign-in, make an app password under Settings ▸ Security and use it here.
Azure: "Azure refused this PC" or "takes no access keys"#
- Azure refused this PC: the storage account's firewall lets only some networks in. In the Azure portal, open the storage account, Networking, and allow this PC's network (or its public IP address).
- The storage account takes no access keys: open its Configuration and set Allow storage account key access to Enabled.
- Use a standard storage account. One with hierarchical namespace (Data Lake Storage) is not supported yet.
- Leave the account's default access tier at Hot or Cool. Each backup rewrites its small catalogue files, and the Cold tier charges a minimum of 90 days for every file replaced.
Google Cloud Storage: "there is no such bucket"#
GBM AI does not make Google Cloud buckets. Create the bucket in the Google Cloud console (Cloud Storage ▸ Buckets), give the service account the Storage Object Admin role on it, and test again.
E-DEST-011 when a job runs#
The account this job signs in with isn't on this PC. The job was imported, or its account removed. Open the job and pick or create the account on the Where step.
E-DEST-012 when a job runs#
The server's key changed. Nothing was sent to it. See An SFTP server's key above.
A certificate of the server's own (FTPS, WebDAV over https)#
An FTPS or https WebDAV server with a certificate of its own (common on a NAS) is refused unless the account ticks Accept the server's own certificate (self-signed): the test and every backup say the server's certificate is not trusted (E-DEST-003) at once, without waiting. Tick it only for a server you run yourself.