Backing up to a NAS or network share

A NAS is a good home for backups: it is on all night, it is not in the same box as the disk that fails, and it is big. GBM AI writes to it through a normal Windows share path. Network destinations are part of Home and Pro.

Before you start#

• The share path, such as \\nas\backups. The NAS's own web page shows it, and so does the File Explorer address bar when the share is open.
• A user name and password on the NAS that can write to that share, or a share that accepts your Windows sign-in.

Step 1: The share path#

1. On the wizard's Where step, choose Network share / NAS.
2. Type the Share path, for example \\nas\backups\Documents & Desktop. Give each job its own folder on the share; the folder at the end is created if it does not exist.

Step 2: The account the job uses#

Under the path a line says which account the job will use:

• Using your Windows credentials: no credential is saved for this share, so the job signs in as you.
• Signed in as backup: a saved credential for this share is used.

For a NAS account:

1. Click Add credentials… (or Replace credentials…). The Network credential dialog opens with the share filled in.
2. Type the User and Password. Leave Domain empty for a NAS user.
3. Click Test. Reachable in 34 ms means the NAS accepted it.
4. Click Save.

Network credential dialog - a NAS account

A saved credential is encrypted in the agent's own store on this PC, never in the job file, an export or a support bundle. Every job that points at the same share uses it. The list is under Settings ▸ Network & credentials.

Step 3: Test the destination#

Click Test destination. Reachable and writable (34 ms) means the job is ready. Anything else shows the reason and its code, for example E-DEST-003 when the share is read-only for that user.

Optional: a drive letter while backing up#

Map to a drive letter while backing up gives the share a free letter, from Z: downwards, while the job runs. The backup itself always writes through the share path; the letter is for pre/post commands and other tools. Keep it mapped after the run leaves the letter in place. Settings ▸ Network & credentials ▸ Drive mappings lists every job's letter.

When the NAS does not answer#

Earlier sets are never touched by a failed run. The failed run's line in Activity offers Test connection (it opens the job's Where step) and Update credentials (it opens Settings ▸ Network & credentials). The report offers Retry.

Service mode is explained in Running backups with nobody signed in.

Tips#

• A bandwidth limit (Pro) paces writes to a share: the Settings step ▸ Advanced ▸ Bandwidth limit, or Settings ▸ Schedule & power for the default. A local drive is never slowed.
• Verify files after each run reads every stored file back over the network. On Wi-Fi that can double the run's time; a cable helps.

Troubleshooting#

The share refuses the user name or password#

The test says \\nas\backups refused this user name or password. Check the password on the NAS's own page. Some NAS models want the user as nas\backup; try the NAS's name in Domain.

The share was not found#

\\nas\backups was not found. Check the server and share names, and that this PC is on the same network. Open the path in File Explorer to confirm it.

Windows is already connected as another user#

Windows is already connected to this server as another user. Windows allows one user per server at a time. Close the other connection (a mapped drive, an open Explorer window), or save the same user here.

Related articles#

• Network & credentials settings
• Choosing where backups go
• Destination not connected, or not answering