Data Protection Server

On this page

This product is deprecated, and is not available for new users.

Overview

Designed for those who want to back up data using a cloud-based architecture, the Data Protection Server (DPS) empowers organizations to use their own cloud for data protection services, while meeting all security, legal, and compliance policies. It is the best of both worlds: cloud backup with in-house, compliant infrastructure.

With DPS, data and metadata never leave your premises while authentication, monitoring and other services are provided centrally by us.

DPS can be rolled out on a hardware server, or on a virtual machine (VM) on any server or public cloud including Google Cloud Platform, Amazon cloud, or Azure cloud.

Private clouds can be deployed using a single server. For the larger deployments, we separate the database server and the application/storage server. In either case, the system specifics for each machine are below.

Hardware configuration

Application server

  Recommended minimum
Processor 4–8 cores
Memory 8–12 GB
Disk space 200 GB or more for operating system
50–100 GB for uploads and request cache (fast disk is recommended, otherwise, system performance might be lower)

Database server

  Recommended minimum
Processor 4–8 cores
Memory 8–12 GB
Disk space 200 GB or more for operating system
300 GB or more for the database (depends on the database load)
500 GB or more for the database backups (depends on the database size)

Additional disks for backup data may be attached later to accommodate for growth. We recommend adding storage in chunks of at least 2–4 TB at a time. Our software supports only disks, which were added directly to the server, or via SMB, or via iSCSI (not recommended).

If the server is a VM, time synchronization with host should be disabled.

Software configuration

Server operating system

We recommend using Windows Server 2012 R2 (English-US version only, language pack is not enough). Please do not add this or any other private cloud servers to your existing domain. We cannot guarantee a stable experience if you do so. We do request that you place all the servers on the same workgroup. We may ask that you mount the operating system installation media in the server.

Microsoft SQL server

DPS supports Microsoft SQL Server 2012 (English-US version only, language pack is not enough). If you are providing the license, please make sure the installation media is mounted on the server. Please do not install SQL server, we will do this ourselves, because it is required to make specific configuration during installation.

Firewall settings

The following ports are required to be opened. This will guarantee better service for both you and your clients.

  Purpose Port Protocol Direction
Application server        
  HTTP 80 TCP From any IP address
  HTTPS 443 TCP From any IP address
  SNMP 161 UDP From 62.205.157.162, 217.147.161.74, 184.173.49.248, 209.162.179.169, 216.45.61.150
  RDP 3389 TCP From 62.205.157.162, 217.147.161.74, 184.173.49.248, 209.162.179.169, 216.45.61.150, 184.173.49.238
  Access the server via SSH protocol, and deploy software updates 2022 TCP From 62.205.157.162, 217.147.161.74, 184.173.49.238
  ICMP (ping)     From any IP address
Database / Storage / Hypervisor server        
  SNMP 161 UDP From 62.205.157.162, 217.147.161.74, 184.173.49.248, 209.162.179.169, 216.45.61.150
  RDP 3389 TCP From 62.205.157.162, 217.147.161.74, 184.173.49.248, 209.162.179.169, 216.45.61.150, 184.173.49.238
  Access the server via SSH protocol, and deploy software updates 2022 TCP From 62.205.157.162, 217.147.161.74, 184.173.49.238
  ICMP (ping)     From any IP address

SSL certificate

We require a certificate to be purchased and installed on the application server for the domain you have chosen. We also require the Private Key for the deployment. Please place it on the desktop or install it yourself. Certificate can be a single server certificate or a wildcard certificate.

DNS records

There need to be DNS record created and pointed to the public IP of the application server. Please create the DNS record using the following naming convention: <Server name>BS001.<domain name>.

For example, if your company name is UltraBackup Ltd, and you have the domain name SomeDomain.com, and the server IP is 1.2.3.4, then the DNS record will be UltraBackup BS001.SomeDomain.com 1.2.3.4.

To start the private cloud deployment, all these steps must be completed.

Please note that as soon as this process has been completed, you, the partner, will be locked out of the machine for the duration of the contract (to protect our proprietary software within).

Our entire system administration team will monitor and maintain the server and the solution on your behalf. If you need to request a server reboot or have maintenance done or are working on your server cluster and need the machine to be brought down for a time, please reach out to us and we will assist you with this.

Rate page

Was it easy to find necessary information on the page?

Was it easy to read and understand information on the page?

Was it easy to follow and apply information on the page?