SIRIS, ALTO, and NAS: Setting up and maintaining a Private Node



This article describes the process of setting up and maintaining a Datto Private Node.


  • Datto Private Node



  • The size of a Datto node must be a minimum of twice the sum of the size of the Datto devices that are connecting to it. This sizing allows the Datto node to have archiving capability for all the data that is backed up to it.
  • Datto recommends 20 Mbps as a minimum for incoming bandwidth as nodes constantly process multiple data synchronizations simultaneously. 
  • The Datto node's deployment location must have a dedicated static public
    IP address. Have this public IP address available when you are ready to set up the Private Node.

Network Configuration

The following are the high-level network requirements for a Datto Private Node:

  • The Private Node must have a static, dedicated public IP address. The Private Node will use this address for most of its functionality. 
  • Configure NAT rules to forward the public IP traffic to the node’s primary LAN address.
  • Configure the ports below, being explicit in directionality. 
  • The Datto devices must have a static IP for communicating with the Private node.

Firewall configuration:

  • The node must have inbound and outbound Port 22 (SSH) access to:
    • External IP address of customer site(s) with Datto Appliance(s) 
    •, and (Datto web servers)
    •,,, and (Datto Technical Support)
  • The following ports must be open inbound and outbound:
    • Port 1194 (UDP) - OpenVPN
    • Ports 1024 through 65535 - VM RDP
  • The following port must be open inbound:
    • Port 8443 from
  • The following port must be open outbound:
    • Port 123 (UDP)  
    • Port 443 - configure this port to be accessible from within your network only - used for offsite file restores and cloud synchronization operations
  • The node must have outbound access to the following servers:

 By default, a node will automatically connect to all new Datto devices that you add on your Partner account. If you want to change this behavior, contact Datto Technical Support, and we will update your node parameters to disable this setting.

While offsite synchronization on a Private Node is set to sync to a public IP address by default, the node can be forced to synchronize over the local network. Contact Datto Technical Support for assistance with changing this setting. Note that if you choose to use the local network for offsite sync, the node will still need to have a public IP address.

Node configuration

You must configure the node directly on the device. Follow these steps:

  1. Plug in the Datto node’s AC Power and connect an Ethernet cable to the Primary NIC, ETH0
    (the NIC that is closest to the PS/2 port).
  2. Attach a monitor and keyboard to the device.
  3. Power on the device. It will prompt you with the user and server number.
  4. Contact Datto Technical Support, and we will authenticate you through our Partner Authentication process. Once we've authenticated you, we will send your node's root password to the verified email address associated with your Partner Portal account. If you are an end-user and not a Datto Partner, we cannot provide this information directly. You will need to contact your MSP for assistance.
  5. Run this command to set up the IP address for the node:
    nano /etc/network/interfaces
    • In this file, customize the address (IP address), netmask, and gateway for your network.
    • Press CTRL+O to save. Press Enter to confirm.
    • Press CTRL+X to exit the editor.
  6. Run this command:
    nano /etc/resolv.conf
    • Edit the nameserver line with your DNS address.
    • Press CTRL+O to save. Press Enter to confirm.
    • Press CTRL+X to exit the editor.
  7. Run this command to restart the networking interfaces on the device:
    /etc/init.d/networking restart
  8. Force the device to connect to Datto's servers:
  9. Provide the public IP address for the node to Datto Technical Support, so that we can update our database.
  10. A Datto technician will verify access, and the Datto Cloud Operations Team will verify that the device is ready to accept client devices.
  11. Once setup is complete, run RoundTrips on all the node's client devices. If data needs to be moved from the Datto Cloud, order a Reverse RoundTrip to retrieve that data.
  12. Connect the RoundTrip drives to the node. Contact Technical Support to have a technician verify that the devices can mount the drives and run commands to copy the data to the node. Once this is complete, you will be able to manage the node from the Partner Portal page, as well as the node's GUI.
  13. Contact Technical Support to have Cloud Support run a final Server Configuration task.

Configuring IPMI

In the BIOS

To configure IP and MAC addresses, enter the BIOS by pressing the Del key when the node boots.

  1. Enter the BIOS password. Contact Datto Technical Support if you need the BIOS password.
  2. Select Advanced and press Enter.
  3. Select IPMI Configuration, and press Enter.
  4. Select Set LAN Configuration and press Enter. You can change IP settings and toggle Static and DHCP services.
  5. Enter a static, reserved IP address.

Accessing the IPMI Web Interface

Once you have configured the dedicated IPMI port with an IP address, you can connect to the web interface to manage your node.

  1. Open a web browser on a computer that is connected to the same network as the Datto.
  2. Browse to the IP address you configured earlier.
  3. At the login page, use the default username and password. Contact Datto Technical Support if you do not have it.
  4. Change your password:
    1. Click on the Configuration menu and choose Users.
    2. Select ADMIN and click Modify User.
    3. Then, select the Change Password check-box and enter your new password.
    4. Click the Modify button.
See this article for more information on configuring IPMI on an Enterprise Private Node. 


The following section describes Datto-recommended proactive maintenance steps to keep your Private Node in optimal condition. Datto recommends performing these steps quarterly unless otherwise specified.

Update the Private Node

Updating your Private Node ensures that it has all updated security patches and software package updates, including required packages for file restore and offsite virtualization. To update your Private Node:

1. Log into the Private Node with the root password.

2. Create a screen. In the below example, the screen name will be "update".

screen -S update

3. Run the following commands to check which web server is currently deployed.
The command below should return that nginx is running.

service nginx status

4. Run the command below. The command should return that apache2 is an unrecognized service.

service apache2 status
If apache2 is running and nginx is unrecognized, contact Datto Technical Support for further assistance in upgrading the node to the latest software.

5. Update packages on the storage node:

sudo apt-get update && sudo apt-get install datto-cloud-node-api datto-file-restore datto-mftdump datto-storage-node datto-vmscripts speedsync

6. Reboot the server. This step is not optional.

reboot now

Verify Networking

Make sure that your Private Node is checking in successfully with Datto's monitoring servers. From the Command-Line Interface (CLI) of the node, type checkin. If the checkin command runs without error, your node can reach the Datto monitoring servers and resolve addresses.

A successful check-in will look similar to the following examples.

mmansfield@datto-siris:~# checkin
Checking to see if checkin is currently running
Updating checkin script (using
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 24330    0 24252  100    78   191k    629 --:--:-- --:--:-- --:--:--  239k
Checkin script updated, executing...
config_utils is up to date
Generating Stats...
Gathering traffic statistics (takes 5 seconds)...
rm: cannot remove `/home/_config/': Is a directory
rm: cannot remove `/datto/config/local/': Is a directory
1Share list hasn't changed
Communicating with server
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 24639    0 21773  100  2866   128k  17297 --:--:-- --:--:-- --:--:--  150k
File download successful.
starting server script
Starting downloaded script
config_utils is up to date
Updating ntfs-3g...

You will see the appliance reach out to multiple packaging servers to check for device updates. Make a note of any errors. Then, the check-in will exit:

Reading package lists... Done               
Reading package lists... Done
Building dependency tree       
Reading state information... Done
ntfs-3g is already the newest version.
The following packages were automatically installed and are no longer required:
  isc-dhcp-server linux-image-3.13.0-65-generic dhcp3-server linux-headers-3.13.0-65-generic linux-headers-3.13.0-65 libnet1
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 151 not upgraded.

If you notice any errors during the check-in process, including the ability to resolve any DNS addresses, review the Network Configuration section of this article. Also, make sure that the node's environment meets the specifications in the Datto Networking Requirements article.

Verify File System and Disk Space

1. Use the df -h command to make sure that the appliance's file system is mounted. The filesystem should show mountpoints for all directories in the Mounted on column. The below example shows a correctly-mounted filesystem on a Private Node. The number after dattoArray/ is the unique device identifier. The number of mounted devices will vary based on how many devices are syncing to your node.


root@server2285:~# df -h
dattoArray/119766                                 1.8T 34M 1.8T 1% /datto/array1/119766
dattoArray/119767                                 1.8T 64M 1.8T 1% /datto/array1/119767
dattoArray/119768                                 1.8T 384K 1.8T 1% /datto/array1/119768
dattoArray/119769                                 1.8T 1.7G 1.8T 1% /datto/array1/119769
dattoArray/119770                                 1.8T 384K 1.8T 1% /datto/array1/119770
dattoArray/119771                                 1.8T 384K 1.8T 1% /datto/array1/119771 

If the filesystem is not correctly mounted, run the ./ command to remount it. You will also need to run this command after any reboot of the node.

2. Run the df -h | head command to check the available space on the OS drive. /dev/sda1 should be at the top of the list, and the Use% value should show less than 100%.

3. Run the zfs list | head command to check the available space on the array drives. The /dattoArray volume should be at the top of the list, and the Use% value should show less than 100%.

Check System Health

Run the bash /datto/utils/ command to check the overall health of the node. Make a note of any reported issues.

Check Drive Health

Run the /datto/scripts/ command to check the node's hard drive health. This script runs a smart check on all drives, Checking for values greater than zero in properties:

  • Raw_Read_Error_Rate
  • Reallocated_Sector_Ct
  • Reallocated_Event_Count
  • Current_Pending_Sector
  • Offline_Uncorrectable
  • Multi_Zone_Error_Rate.

If the script detects a problem, it will return output similar to the following:

Checking drive /dev/sdb...
/dev/sdb - Failing property 'Multi_Zone_Error_Rate': 2 * Weight 10 = 20 score
Total /dev/sdb Score = 20

If a drive has a total score greater than 100 this drive should be replaced. A high error count on a drive can cause data corruption or loss. Address any reported disk issues before proceeding with further maintenance.

Proactive Disk Maintenance

Run the zpool status -v command to check for zpool corruption. If corruption is present, run the command zpool scrub <name of affected pool>.

Make sure your node's hard drives are healthy before running a zpool scrub.

Your Datto appliance will attempt to correct the disk errors. Run the zpool status -v command again to view the status of the scrub. Shown below is an example of corruption in the homePool storage pool.

mmansfield@datto-siris:~# zpool status -v
pool: homePool
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
scan: resilvered 50K in 0h0m with 0 errors on Mon Feb 15 22:31:48 2016

NAME                                            STATE     READ WRITE CKSUM
homePool                                        DEGRADED   402     0     0
  mirror-0                                      DEGRADED   402     0     0
    8518445531633777586                         UNAVAIL      0     0     0  was /dev/disk/by-id/ata-Hitachi_HDS721010DLE630_MSK5235H262VAG-part1
    ata-Hitachi_HDS721010DLE630_MSK5235H262UHG  ONLINE     402     0     0
errors: Permanent errors have been detected in the following files:


If the device is unsuccessful at clearing the corruption, contact Datto Technical Support for further assistance.

Datto also recommends running proactive scrubs of your device's storage pools every quarter, or after a drive replacement.

Proactive Reboot

Datto recommends rebooting your node every 6 to 12 months. Make sure that there are no file restores or virtualizations in use on the node before rebooting; a reboot will interrupt connections to them. To reboot the node from the command line, run the reboot now command. Remember to remount the file system after reboot, as described in the Verify File System and Disk Space section of this article. 

Was this article helpful?

2 out of 2 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Datto Community Forum or the Datto Community Online.

For more Business Management resources, see the Datto RMM Online Help and the Autotask PSA Online Help .

Still have questions? Get live help.

Datto Homepage