Skip to main content

 

Druva Documentation

Understanding inSync Private Cloud architecture

Overview

This section explains the inSync Private Cloud architecture. 

Druva inSync Private Cloud architecture

Druva inSync Private Cloud is a scalable data backup solution for organizations that are spread across geographies. The highly robust design of Druva inSync effectively backs up endpoint data, protects this data, and facilitates data share across the organization.

In your organization, employees use various devices such as laptops, mobile phones, tablets, and desktops to access and store data. Such devices are referred to as endpoints. Data moves across organizations through such endpoints. So that data on these endpoints is backed up effectively, inSync Private Cloud allows for a synchronization of multiple storage nodes with a Master server. 

 

A Private Cloud implementation has the following advantages:

  • New storage nodes can be added as required, making the solution scalable.
  • Users can be grouped depending on their functional role or their proximity to a storage node. This allows for efficient management of users.

 

The components of inSync Private Cloud are explained in the following table.

 

Name Description
Master Server The Master server, which is installed within an organization's premises,  effectively manages storage nodes as well as user information. The Master server ensures that inSync client requests (for backup and restore) are authenticated and assigned to a storage node. To sum it up, the Master server provides a unified view of all storage nodes.
Storage Node Multiple storage nodes are located across geographies. Storage nodes are servers on which you create storages. A storage node is a physical machine with its own local persistent storage, either disk or solid state, a CPU with one or more cores, memory, and an IP address.
inSync Client

inSync clients, which are installed on endpoints, initiate backup or restore requests. Such requests are authenticated by the Master server and routed to a storage node. The client data is typically backed up to or restored from a storage node. inSync clients communicate with the Master server following a request-response messaging pattern over LAN or WAN. Similarly, inSync clients back up or restore data from the storage nodes via LAN or WAN.

Note: inSync client "informs" the Master server about a backup or restore requirement. The client does not route any data to the Master server. The Master server in turn, acknowledges and asssigns client requests to the appropriate storage node. inSync client sends or receives data to or from a storage node only. The Master server only "authenticates", while the storage node actually backs up or restores data. The Master server does not back up or restore data.
  • Was this article helpful?