Keep backups off the box

Retivo always keeps every version on the node, because comparing, compliance and restore need it. A remote destination holds a second copy somewhere else.

Before you begin

• You need Manage settings.
• The node must be able to reach the destination (see the table at the end).

1. Add the destination

Inventory > Credentials > New credential set and choose a "Backup destination" type.

S3 storage

Bucket, an optional folder, access key and secret key. Leave the endpoint empty for AWS and set the region. For MinIO, Ceph, Wasabi, Backblaze B2 or other S3 storage, enter its address and tick Path-style addresses if it needs them.

Google Drive

Once, in Google Cloud Console:

1. Create a project and enable the Google Drive API.
2. Set up the OAuth consent screen and add your account as a test user.
3. Create an OAuth client ID of type TVs and Limited Input devices.

In Retivo, enter the client ID and secret and a folder (default Retivo), save, then press Connect. Retivo shows a code to enter at Google's address on any computer or phone. Retivo can see only the files and folders it creates.

Microsoft OneDrive

Once, in the Azure portal (Microsoft Entra ID):

1. App registrations > New registration, for personal accounts, work accounts or both.
2. Under Authentication, set Allow public client flows to Yes.
3. Add the Microsoft Graph delegated permissions Files.ReadWrite and User.Read.

In Retivo, enter the Application (client) ID, the account type and a folder, save, then press Connect and enter the code at Microsoft's address. No client secret is needed.

SFTP

Server, port, user, password and a folder. The server's host key is remembered on first contact; Retivo refuses to send if it changes. Trust the server's new host key accepts a new one.

FTP / FTPS

Server, port, user, password, a folder, and Use TLS for explicit FTPS.

TFTP

Server, port and a folder that already exists. Many TFTP servers accept new files only when started with a create option, for example tftpd -c.

Saving, or pressing Test, writes a small file, reads it back and deletes it (TFTP cannot delete).

2. Choose which devices use it

Set it on a group (Config backup storage for members), on a device (Config backup storage), or tick devices on Config backups and press Change storage. A device setting wins over its groups, and an inner group over an outer one. Local only on a device turns remote copies off for it.

3. Check it works

From now on every new version is copied to folder/device-name/date_id.cfg. The Stored column on Config backups shows whether each device's latest version reached the destination and how many versions are there. Copy to remote now copies older versions. Failed copies are retried every 15 minutes. On a device page, From remote reads a version back from the destination.

Addresses the node must reach

What's next

• Config versions