User Tools

Site Tools



Hardware Requirements

Refer to Hardware Compatibility List (HCL) for CloudBacko Go on QNAP NAS for details on the minimum and recommended requirements for installing CloudBacko Go.

QNAP NAS models with less than 1GB RAM are not supported. As 1GB RAM or above is required to ensure application stability and optimal backup/restore performance. To back up data on unsupported QNAP NAS models, share the folder(s) then backup the data as network shared folder from a Windows machine.

For more details on how to create a shared folder(s), please refer to this link Creating a Shared Folder.

Software Requirements

Refer to here on the supported QTS versions for QNAP NAS.

CloudBacko Go Installation

The latest version of CloudBacko Go must be installed on the QNAP NAS.

Java Requirement

The Oracle Java JDK files are already included and deployed as part of the CloudBacko Go installation.

Memory Requirement

The default Java heap size of CloudBacko Go installation on QNAP NAS is 1 GB. It is recommended that 2 GB RAM or more is installed for stability and better backup / restore performance.

TCP Port Requirement

By default, the QNAP NAS machine uses TCP port 32168 for the WuiService.

TCP port 32168 must be free on the machine. Otherwise, the CloudBacko Go client will not start and its backup and/or restore functions will not work.

QNAP NAS User Account Permission

The QNAP NAS user account used for the CloudBacko Go installation and application must be a member of “administrators” user group.

The QNAP NAS user account belongs to “everyone” user group and can apply CloudBacko Go after administrator assigning CloudBacko Go to Display on “Every user’s menu” or “Every user’s main menu and as an App shortcut on the login screen” in App Center.

After login with user account belongs to “everyone” user group, you can find the App in the user’s menu.

Network Bandwidth

10 Mbps or above connection speed.


These are the unsupported features of CloudBacko Go on QNAP NAS devices.

  • Auto Upgrade
  • Backup of Network Drives
  • Decrypt Backup Data
  • OpenDirect
  • Restore Filter
  • Space Freeing Up

Best Practices and Recommendations

Periodic Backup Schedule

The periodic backup schedule should be reviewed regularly to ensure the interval is sufficient to handle the data volume on the machine. Over the time, data usage pattern may change on a production server, i.e., the number of new files created, the number of files which are updated/delete, new users may be added etc.

When using periodic backup schedules with small backup intervals such as backup every 1 minute, 2 minutes, 3 minutes etc. although the increased backup frequently does ensure that changes to files are captured regularly which allows greater flexibility in recovery to a point in time.

Consider the following key points to efficiently handle backup sets with periodic backup schedule.

  • Hardware – to achieve optimal performance, compatible hardware requirements is a must. Ensure you have the backup machine’s appropriate hardware specifications to accommodate frequency of backups,
  • so that the data is always backed up within the periodic backup interval
  • so that the backup frequency does not affect the performance of the production server
  • Storage – ensure you have enough storage quota allocated based on the amount of new data and changed data you will back up.

Retention Policy – also make sure to consider the retention policy settings and retention area storage management which can grow because of the changes in the backup data for each backup job.

public/quickstart/qnap/requirements.txt · Last modified: 2021/08/03 12:00 by support