SMB / CIFS
Store backups on a Windows share, NAS, or any SMB/CIFS-compatible network storage.
Configuration
| Field | Description | Default | Required |
|---|---|---|---|
| Name | Friendly name for this destination | - | ✅ |
| Address | UNC share path (e.g. //server/share) | - | ✅ |
| Username | SMB username | guest | ❌ |
| Password | SMB password | - | ❌ |
| Domain | Windows domain / workgroup | - | ❌ |
| Max Protocol | Highest SMB protocol version to use | SMB3 | ❌ |
| Path Prefix | Subfolder within the share | - | ❌ |
Protocol Versions
| Protocol | Notes |
|---|---|
SMB3 | Default, recommended - encrypted transport |
SMB2 | Fallback for older NAS devices |
NT1 | SMB1 legacy - use only if required |
Setup Guide
- Ensure the SMB share is accessible from the DBackup server
- Create a dedicated user with write access to the share (recommended)
- Go to Destinations → Add Destination → SMB / CIFS
- Enter the Address in UNC format:
//hostname-or-ip/sharename - Enter username and password (or leave as
guestfor anonymous access) - (Optional) Set Domain if authenticating against a Windows domain
- (Optional) Set Path Prefix for a subfolder within the share
- 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
smbclientmust be available in the DBackup container (included in the default Docker image)
Troubleshooting
Connection Refused
NT_STATUS_CONNECTION_REFUSEDSolution: Verify the server address and that SMB is enabled. Check the firewall allows port 445.
Access Denied
NT_STATUS_ACCESS_DENIEDSolution: 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_RESPONSESolution: Try lowering Max Protocol to SMB2 or NT1. Some older NAS firmware doesn't support SMB3.
Share Not Found
NT_STATUS_BAD_NETWORK_NAMESolution: Verify the share name is correct. List available shares: smbclient -L //server -U username.