Druvaa inSync uses client triggered backups, network encryption and WAN Optimization to facilitate faster backups over VPN or WAN (Internet) for remote users.
All backup and restore requests are initiated by the inSync client over a secure 256 bit encrypted SSL channel. In no case will the server initiate backups or other outbound network requests. The settings in firewall should allow unidirectional (one way traffic) from “ANY” to configured (default 6061) port on the inSync Server.
In presence of multiple network interfaces (for LAN/WAN) or a firewall, the inSync Server may be reachable by the inSync clients on different network addresses. For example, as shown in the example below the server is visible to users on following addresses -
- LAN - 192.168.15.1 : 6061
- LAN - 192.168.15.4 : 6061
- WAN - 202.141.81.84 : 8000
Please note that in this example the IP address visible the WAN users is 202.141.81.84:8000 and NOT 192.168.15.5:6061
The administrator needs to add these three IP addresses to the list of "published addresses" as shown in the screenshot below -
The web-restore IP address shoud also be updated to an IP address which all the user's can use.
Agan, These are NOT necessarily the server IP addresses, but those on which the client can connect to the server. These addresses need to go to the network configuration before the keys are generated for each user.
To avoid manual configuration, these IP addresses and other essential settings are communicated to the user using the authentication key (.isk) file. Once the IP addresses are configured please generate the key files and send to all the new users. Once the keys are loaded in inSync client, it automatically polls the IP addresses in the given order and backs up data.
NOTE: Any changes to the "published IP addresses" are automatically communicated to the already configured and syncing clients and it does not require re-issuing of the keys.
