This topic contains frequently asked questions on planning for the inSync deployment.
Frequently asked questions
Where do I install the inSync master server?
You can install the inSync master server at any of your data centers. Normally organizations like to keep the inSync master server at a central location with respect to the inSync storage nodes.
For example, an organization with storage nodes in California, Amsterdam, Mumbai, and Tokyo decided to install the master server at their data center at Amsterdam because it is centrally located with respect to the other storage nodes. On the other hand, another organization with storage nodes in Boston, Zurich, Munich, and Dubai decided to install the master server at Boston because it is their headquarters.
How many storage nodes do I create? At which locations?
For performance and efficiency, you should ensure that most of your employees are backing up their data through LAN. To facilitate this, you should install at least one storage node at each of your offices. The number of storage nodes that you create in each office will depend on the number of employees you have at those locations. One storage node can attend to 1500 to 2000 users.
The following table illustrates the distribution of employees and storage nodes at various offices of an organization.
|No. of Employees||3500||1500||7000||800|
|No. of Storage Nodes||2||1||3||1|
How many storages do I create? What should be the size of each storage?
Each storage node will have at least one storage on it. The actual number of storages that you should create on a storage node will depend on your requirements and your organization's policies. For example, if it is your organization's policy that the top management's data must be stored separately from the rest of the organization's data, you will have to create two storages - one for the top management and one for the rest of the organization. Both storages can be on the same storage node.
Note: We recommend that you create the least number of storages on a storage node. This helps you take advantage of inSync's data deduplication abilities and save space on your storage.
The storage size of each storage depends upon various factors. Some of them are:
- The number of users backing up their data on the storage.
- The average data each user is expected to back up.
- The daily incremental change in data for each user.
- The type of data being backed up.
- The retention policy of the organization.
To get a rough estimate of the required size of a storage, use our ROI calculator at: http://www.druva.com/insync/roi-calculator/. After filling up the data when you click View Savings, a storage savings graph is displayed. The storage space utilized by inSync at the end of 64-week period is the size of storage you require.
For example, you need approximately 15 TB of storage space for the following requirement:
- Number of users - 1000
- Average data per device - 10 GB
- Type of data on device - Majority emails
- Daily incremental data on devices - 2%
- Data retention policy - 90 days
- Percentage of remote/mobile users - 40%
Note: It is important that you choose the right amount of storage space. Underestimating your storage requirements will hamper backups from user devices. For an accurate calculation of how much storage space you need, send an email to email@example.com.
I want to use the high availability feature of inSync. Will it impact the number of storage nodes and storages I need?
The high availability feature of inSync ensures that users have seamless backup and restore experience even if a storage is not available because of network or some other issue. To implement the high availability feature, you have to create one secondary storage per primary storage you want to make high available.
For example, you have two primary storages - P(A) and P(B). User group U1 backs up their data to P(A) and user group U2 backs up their data to P(B). If you want to implement high availability feature for the group U1, you must create a secondary storage S(A). If you want to implement high availability feature for both groups U1 and U2, you must create two secondary storages - S(A) and S(B).
While creating the secondary storages, adhere to the following guidelines:
- The secondary storage must be of the same size and configuration as the primary storage. For example, S(A) must be equivalent to P(A), and S(B) must be equivalent to P(B).
- The secondary storage must be on different storage node than the primary storage. For example, P(A) and S(A) must be on separate storage nodes. Similarly, P(B) and S(B) must be on separate storage nodes.
How many profiles do I create?
A profile is a container of configurations that are applicable for a set of users. The configuration set in a profile is applied to all users assigned to that profile. In order to decide on the number of profiles to be created, you need to first identity the group of users that have similar requirements in your organization. You can create a profile for each group of users with similar requirements.
How do I deploy inSync client on user devices?
You can choose one or a combination of the following ways to deploy inSync client on all computers in your organization:
- Create user accounts through the inSync Admin Console and send them account activation emails. The email will contain their inSync account password and the URL to download inSync client. The users can install and activate inSync client on their own.
- Create user account through inSync Admin Console and download their authentication keys. You must then install and activate inSync client on each user's device.
- If your organization uses Active Directory for user authentication, you can mass deploy inSync client. inSync client will be automatically activated when the user logs on to their computer.
Note: The above options are applicable for deploying inSync client on user computers and not for mobile devices. On mobile devices, only the user can install and activate inSync client.