Skip to main content

Network & credentials settings

Saved share credentials, drive mappings, the proxy and timeout, S3 profiles and file server accounts, and where the passwords are kept.

Updated
On this page

Settings ▸ Network & credentials holds what a job needs to reach a destination that is not a local drive. The page opens with the rule: Passwords are encrypted in the agent's own store, never in job files.

Network and credentials settings pageNetwork and credentials settings page

Saved credentials (Home)#

A saved credential is the user name and password for one network share, such as \\nas\backups. On Free this card is locked; network shares are part of Home and Pro.

The table has one row per share: Share, User, Used by (how many jobs) and Status.

To add one:

  1. Click Add credential.
  2. Enter the Share, the User and the Password. Leave Domain empty for a NAS account.
  3. Click Test. Reachable in 34 ms means it works.
  4. Click Save.

Network credential dialog - a NAS accountNetwork credential dialog - a NAS account

A failed test says why:

  • \\nas\backups refused this user name or password.
  • \\nas\backups was not found. Check the server and share names, and that this PC is on that network.
  • Windows is already connected to this server as another user. Close that connection, or use the same user here.

Each row also has Test, Edit and Remove. Removing a credential that jobs use warns first: those jobs fail until you add it again.

A job whose destination is on a saved share uses its credential by itself. With no saved credential, a job on a share uses your Windows sign-in.

Drive mappings#

Read only. It lists every job that maps its share to a drive letter while it runs (set on the job's Where step): the Letter, the Share, the Job, whether it is Kept after the run, and its state Now: Mapped to this share, In use by something else or Free. Refresh reads the states again.

Connection#

  • Proxy: Windows settings (default), No proxy or Manual. Manual adds Host and port, and Sign in as with a user name and a password (click Save beside the password). Never use the proxy for takes a comma-separated list of hosts, such as *.corp.local, 10.0.0.0/8 or nas; localhost is always reached directly. The proxy is used for the app's calls to Genie9 (licence, sign-in, updates, Ask Genie), for S3 buckets, and for file servers and the other clouds (SFTP and FTP through the proxy's tunnel).
  • Connection timeout: 30 seconds (5 to 600), for the app's calls to Genie9.

S3 profiles (Pro)#

An S3 profile holds the keys for one account at Amazon S3, Wasabi, Backblaze B2, MinIO or any S3-compatible service. Several jobs can share one profile.

  1. Click Add profile (or New profile… on the wizard's Where step).
  2. Enter a Profile name, the Endpoint (leave it empty for Amazon S3), the Region, the Access key ID and the Secret access key. The secret is sent to the agent once, stored encrypted and never shown again.
  3. Click Test. Signed in (210 ms) means the keys work.
  4. Click Save.

S3 profile dialog - a Wasabi accountS3 profile dialog - a Wasabi account

The table shows each profile's name, endpoint and region, a masked access key and the jobs that use it. Remove is greyed while a job uses the profile; change those jobs first. Removing a profile touches nothing in the bucket. See Backing up to S3-compatible cloud storage.

File servers and other clouds (Pro)#

An account here signs in to an SFTP, FTP or FTPS server, a WebDAV server (Nextcloud, ownCloud, a NAS), an Azure storage account or Google Cloud Storage, for the wizard's File server or cloud destination. Several jobs can share one account.

  1. Click Add account (or New account on the wizard's Where step).
  2. Choose the Kind, give the account a name, and fill in what the kind asks for: the server, port and user name, a password or a private key, a WebDAV address, an Azure storage account and its key, or a Google Cloud service account key.
  3. Click Test. For an SFTP server the first Test only shows the server's key: check its fingerprint, tick that you trust it, and Test again to sign in.
  4. Click Save account.

File server account - trusting an SFTP server's keyFile server account - trusting an SFTP server's key

The table shows each account's name, kind, where it signs in (for example backup@nas.office.lan) and the jobs that use it. Remove is greyed while a job uses the account. Removing an account touches nothing on the server. These connections go through the proxy above, unless the server is on its Never use the proxy for list. See Backing up to a file server or business cloud.

In service mode#

When you switch on service mode, saved credentials, S3 profiles and file server accounts are handed to the Windows service, sealed for this PC. Jobs to a NAS or a bucket then use them with nobody signed in. When you switch service mode off, they come back sealed for your Windows account. See Running backups with nobody signed in.

Was this article helpful?