Skip to content

SMB / CIFS

Store backups on a Windows share, NAS, or any SMB/CIFS-compatible network storage.

Configuration

FieldDescriptionDefaultRequired
NameFriendly name for this destination-
AddressUNC share path (e.g. //server/share)-
UsernameSMB usernameguest
PasswordSMB password-
DomainWindows domain / workgroup-
Max ProtocolHighest SMB protocol version to useSMB3
Path PrefixSubfolder within the share-

Protocol Versions

ProtocolNotes
SMB3Default, recommended - encrypted transport
SMB2Fallback for older NAS devices
NT1SMB1 legacy - use only if required

Setup Guide

  1. Ensure the SMB share is accessible from the DBackup server
  2. Create a dedicated user with write access to the share (recommended)
  3. Go to DestinationsAdd DestinationSMB / CIFS
  4. Enter the Address in UNC format: //hostname-or-ip/sharename
  5. Enter username and password (or leave as guest for anonymous access)
  6. (Optional) Set Domain if authenticating against a Windows domain
  7. (Optional) Set Path Prefix for a subfolder within the share
  8. Click Test to verify the connection

NAS Devices

Synology, QNAP, TrueNAS, and OpenMediaVault all support SMB shares. Create a dedicated share and user for backups in your NAS admin panel.

How It Works

  • DBackup mounts the SMB share temporarily for each operation, then unmounts
  • Files are written directly to the share - same behavior as local storage
  • All credentials are stored AES-256-GCM encrypted in the database
  • smbclient must be available in the DBackup container (included in the default Docker image)

Troubleshooting

Connection Refused

NT_STATUS_CONNECTION_REFUSED

Solution: Verify the server address and that SMB is enabled. Check the firewall allows port 445.

Access Denied

NT_STATUS_ACCESS_DENIED

Solution: Check username, password, and domain. Ensure the user has write permission on the share. For guest access, ensure the share allows anonymous connections.

Protocol Negotiation Failed

NT_STATUS_INVALID_NETWORK_RESPONSE

Solution: Try lowering Max Protocol to SMB2 or NT1. Some older NAS firmware doesn't support SMB3.

Share Not Found

NT_STATUS_BAD_NETWORK_NAME

Solution: Verify the share name is correct. List available shares: smbclient -L //server -U username.

Next Steps

Released under the GNU General Public License. | Privacy · Legal Notice