+- ASK NC (https://ask.nascompares.com)
+-- Forum: Q&A (https://ask.nascompares.com/forumdisplay.php?fid=1)
+--- Forum: Backup Solutions (https://ask.nascompares.com/forumdisplay.php?fid=16)
+--- Thread: Remote QNAP backup over internet (OpenVPN) failing (/showthread.php?tid=12195)
Remote QNAP backup over internet (OpenVPN) failing - Freeco - 07-22-2025
Hi everyone,
I've been trying to set up a remote backup from my home QNAP NAS to a second QNAP NAS at my in-laws' place, but the backup keeps failing and I’m not sure what I'm missing. Here's a breakdown of my setup and the issues I'm running into.
- Both NAS units are QNAP: a TS464 at home and a TS453D remotely.
- Remote site has dynamic IP, so I'm using DDNS via myQNAPcloud.
- Access to remote NAS is via OpenVPN, with one forwarded port on the router for VPN only.
- Backup is set up using RTRR Server on the remote NAS, for client-side encryption and version management.
- Initial backup was done locally to speed things up, and verify that the backup job works.
- The NASes originally were in the same IP range (192.168.x.x), which I've changed at my in-laws' router to avoid routing conflicts.
- Static route added via Network & Virtual Switch so traffic to the remote subnet goes through the VPN.
Storage Spaces was updated with the new fixed IP of the remote NAS.
OpenVPN connection works, but the backup job fails.
Log details show:
Info: "Using network interface 'Default Route'. Interface selection: Automatic."
Error: "Destination NAS does not support QuDedup. Check RTRR server connection and confirm HBS is updated to version 3.0 or later."
QuDedup wasn't an issue for the initial local backup.
QuDedup can’t be disabled in the current job, and new jobs targeting the remote NAS can't be created either.
While I was reviewing the backup job, I noticed one of its settings is about the interface. It's set to automatic, as the info event says. I can't force the job to use the VPN connection though.
Any help would be appreciated here!
RE: Remote QNAP backup over internet (OpenVPN) failing - ed - 08-02-2025
Here are the key things I’d recommend checking:
⸻
1. Force HBS to Use the VPN Interface:
Even though OpenVPN is connected and routing is in place, HBS by default chooses the “Default Route” interface — which can cause it to bypass the VPN tunnel altogether if it detects a public IP for the DDNS target.
• In HBS 3, under the Backup Job > Edit > Network Interface section, try explicitly assigning the VPN adapter instead of leaving it on “Auto” (you may need to set the route manually if it doesn’t appear).
• If HBS doesn’t show the VPN interface, double-check in Network & Virtual Switch > Interfaces to confirm the OpenVPN tunnel is registered as a valid interface, and it has a route to the remote subnet.
⸻
2. QuDedup Compatibility Error:
This error typically shows up when:
• The remote NAS is running an older version of HBS (must be at least 3.x for QuDedup support).
• Or when you attempt to run a QuDedup job against a NAS that doesn’t support it, over the network.
Solutions:
• Make sure both NAS units have the latest version of HBS 3 installed from the App Center.
• If the TS-453D doesn’t support QuDedup (older model or older firmware), you’ll need to disable QuDedup entirely on the backup job. Unfortunately, this can’t be edited once a job is created, so you’ll need to recreate the job from scratch with QuDedup off.
⸻
3. IP/Subnet & Static Route Validity:
You’ve done well by separating the subnets, but also verify:
• The static route on the local NAS sends all 192.168.y.x traffic through the OpenVPN tunnel.
• That the remote NAS sees the traffic as coming from inside the VPN subnet, not from WAN.
• If both sides are QNAP and using client-server VPN setups, also confirm that the OpenVPN connection is active on the NAS, and not just on your router or another device.
⸻
4. Temporary Diagnostic Tip:
Try running an rsync or plain file transfer job over the VPN tunnel outside of HBS, e.g. using:
rsync -avz -e 'ssh -p 22' /source_folder admin@remote-ip:/destination_folder