NyxBackup

Connecting storage

Nyx Backup never stores your data for you. You bring a destination you control, and the app writes encrypted blobs into it. You hold the account and the keys; we never see, proxy, or store your files.

Local, cloud, or both?

New to this? Here is the short version of how to choose.

  • A local or network drive is fast and has no ongoing fee, but it sits in the same place as your computer. A fire, theft, flood, or a simple drive failure can take the backup along with the original. It is also hardware you have to buy, keep an eye on, and eventually replace.
  • Cloud storage keeps a copy off-site, so a disaster where you live or work does not reach it. The provider stores your data on redundant, professionally maintained infrastructure - typically copied across multiple drives or locations - so a single hardware failure on their end does not lose it. There is nothing for you to maintain or replace, you pay only for the space you actually use, and it grows with your data instead of forcing you to buy a bigger disk.

Because Nyx Backup encrypts everything on your machine first, the cloud provider only ever holds encrypted blobs. You get the durability and convenience of the cloud without handing anyone readable access to your files.

The safest setup is both. Keep one local copy for fast restores and one cloud copy for off-site protection - the widely recommended “3-2-1” idea: a couple of copies, on different media, with at least one off-site. In Nyx Backup you just create two backup sets for the same folders, one pointing at a local drive and one at a cloud destination.

Supported destinations

Each has a step-by-step setup guide - how to create the storage at the provider and what to enter in Nyx Backup:

What you will need

It depends on the destination type:

  • Object storage (S3, B2, Wasabi, Azure, GCS, R2, other S3-compatible): a bucket or container name, the region or endpoint URL, and an access key ID and secret. Create a key scoped to just this bucket where your provider allows it.
  • SFTP: the host, a username, and either a password or an SSH private key file, plus the remote path to write into.
  • SMB / CIFS: the share path and the credentials to reach it.
  • WebDAV: the server URL and its username and password.
  • Google Drive, OneDrive, Dropbox: you sign in through the provider once; Nyx Backup stores only the access token, never your provider password. Drive access is limited to an app-specific folder, not your whole Drive.
  • Local or network drive: a folder path. Choose a drive that is separate from the one you are backing up - a backup on the same disk disappears with it. The editor warns you if the destination shares a volume with a source.

Test the connection

Before saving, choose Test connection. Nyx Backup verifies the credentials, measures latency, and checks the destination. If a bucket does not exist yet, it can offer to create it for you (S3, B2, and R2).

One machine per bucket

Give each machine its own bucket or its own folder within a destination. If Test connection finds another computer already backing up into the same bucket, it warns you: sharing one bucket across machines with automatic retention is unsafe and can delete data another machine still needs. Separate destinations stay completely independent.

Changing a set’s destination later

If you move an existing set to a new destination, the editor offers to reset the set’s local state so the next backup uploads cleanly to the new location. Your old data is left untouched - remove it from your provider’s console if you no longer want it.