This topic explains how to create additional storages.
Creating additional storages
Using one of the configuration wizards, you have created the first storage. Using the Create New Storage wizard you can create additional storages at any given point in time.
Before you begin
The following tasks are applicable for any additional storages that you create in the inSync server:
- Create the folders that will be used as Data, Database, and Database Log folders on the inSync server. Make sure these folders are not scanned by any AntiVirus.
- When creating the folders, use the following guidelines:
- The database and database log folders must be on a local drive. Do no create these folders on a networked or shared drive.
- The data folder can be created on a local drive, SAN, or NAS.
- The database folder must be created on a separate disk. If there are a large number of users who will back up their data on the storage, it is recommended to create the database folder on a solid state drive (SSD).
- The data folder and the database log folder must preferably be on separate disks.
Creating a storage
Step 1: Create the folders required for the storage
To create the folders
- Log on to the server to which you attached your storage media.
- Create the folders that will be used as Data, Database, and Database Log folders respectively.
- Make sure that you excluded these folders from an antivirus scan.
Follow these guidelines while creating the folders:
- Create the Database and Database Log folders on a local drive. Do no create these folders on a networked or shared drive.
- You can create the data folder on a local drive, Storage Area Network (SAN), or a Network-attached Storage (NAS).
- You must create the Database folder on a separate disk. If you expect many users to back up their data on the storage, create the Database folder on a Solid-state Drive (SSD).
- Druva recommends that you create the Data folder and the Database log folder on separate disks.
Step 2: (Linux) Assign insyncserver permissions on the storage folders
On a Linux computer, the user 'insyncserver' must have group and owner permissions on the Data, Database, and Database Log folders.
To assign appropriate permissions
- Log on to the inSync storage node.
- Run the following command on all storage folders:
$ sudo chown insyncserver:insyncserver <storagefolder>
Step 3: Create the storage
To create the storage
- Log on to the inSync Admin Console.
- On the menu bar, click Manage > Storage.
- Click Create New Storage. The storage creation wizard appears.
- Enter the requisite details on each page of the wizard. For more information, see Fields in the storage creation wizard.
- Click Finish.
The storage is created.
Fields in the storage creation wizard
General Storage Information
The following table describes the fields on the General Storage Information page of the wizard.
|Storage name||Enter a name for the storage.|
|Data folder||Select the data folder of the storage.|
|Max. disk space||Enter the total data that can be stored in the storage.|
|Storage consumption alert threshold||Enter the storage consumption threshold value which will trigger a low disk space alert for inSync administrators. For example, if the Max. disk space for a storage is 10 TB and storage consumption alert threshold is 80%, a low disk space alert is triggered when 8 TB of space is consumed. |
The following table describes the fields on the Performance page of the wizard.
|Optimize for|| |
Select to optimize a storage for "Disk space savings" or "Performance". Storages that are optimized for performance use file-level data deduplication and scale better for large deployments. Storages that are optimized for disk space saving use block-level data deduplication and can conserve more space.
If you expect a storage to store 4 TB data or more, optimize your storage for performance.
|Use SSD||Select if you are using an SSD for the database folder.|
|Database folder |
(or SSD path)
|Select the database folder of the storage. If you are using an SSD, select the SSD path.|
|Database Log folder||Select the database log folder.|
|Max. parallel connections||Enter the maximum number of parallel connections permitted to the storage.|
|Hypercache||This is a non-editable field. It displays the amount of buffer memory created to improve the I/O performance of the storage. It is 0.4% of the storage size. |
Storage Compaction Schedule
The compaction process analyses the data in a storage and purges redundant or non-relevant data from it, thereby freeing up storage space. For example, your organization's policy mandates a retention policy of 90 days. This means that a copy of deleted data is retained for 90 days. At the end of 90 days, the compaction process identifies this copy as non-relevant and purges it to free space.
The compaction process is resource-intensive and time-consuming, and thus, should run during off-peak hours. Druva recommends that along with daily compaction, you run a weekly compaction for a longer duration. For example, you can schedule to run a compaction every night at 1:00 AM for 5 hours and every Saturday at 1:00 AM for 30 hours.
The following table describes the fields on the Storage Compaction Schedule page of the wizard.
|Compact daily at||Enter the start time and duration for the daily storage compaction. For example, you can configure the daily compaction to start at midnight and continue for 6 hours. The compaction will stop at 6:00 AM even if it is not complete.|
|Compact weekly on||Enter the scheduled day for weekly compaction ofr the storage.|
|Compact weekly at||Enter the start time and duration for the weekly storage compaction.|
|Compact when usable space drops below||This field appears only when you optimize storage for "Disk space savings". Enter the storage space threshold, in percentage, which when exceeded, triggers storage compaction.|