Skip to main content
Druva Documentation

Storage FAQs

Answers

What is the maximum number of storage nodes that I can create?

The inSync Private Cloud setup does not set restrictions on the number of storage nodes. Because creating a storage node means investing in hardware resources, you should create only as many nodes as you require.

What is the maximum number of storage that I can create on a storage node?

inSync does not set restrictions on the number of storages that you can create on a storage node. However, the sum of storage space should not exceed 64 TB."For queries on the estimate and best practices on configuring the storage size contact Druva Support.

Does Druva recommend the number of storage?

As you can create multiple storage nodes on inSync Private Cloud, you have unlimited storage capacity. However, as a best practice, create as few storage nodes as possible. This helps in taking advantage of inSync's data de-dupe functionality.

Can I create the Database folder on NAS? 

The Database folder contains metadata about backup data. The inSync Master needs this metadata to identify backup data. inSync does not support the creation of the Database folder on a shared drive or Network-access storage (NAS). Always create this folder on a local drive, separated from networks. 

What is the minimum disk space required for Data, Database, and Database log?

We recommend the disk space for Database and Database log folders to be at least 5% of the Data folder size. However, the size of Database and Database log must be at least 8 GB. For more information on disk space requirements, see About storage.

How many data volumes can I add to a storage?

You can add up to 10 data volumes to an existing storage. 

What happens if I change a user's storage?

When you change a user's storage, user data will be backed up to the new storage. Snapshots on the old storage are retained and compacted following the retention policy. However, the user can restore data from any snapshot, even those available on the old storage.

Do users come to know if their storage changes? 

No. Users will not know that their storage has changed. 

Do users start backing data to the new storage immediately?

Yes, users can start data backup as soon as they move to the new storage. 

If I change a user's storage, is the first backup a full backup? 

Yes. The first backup is a full backup. Thereafter, all backups will be incremental in nature. 

Are old snapshots retained on the earlier storage?

For a while, yes. The time for which snapshots are retained is determined by the retention policy. At the end of the retention policy, these snapshots are compacted following the compaction policy that you adopted. 

Can users restore data from any snapshot?

Yes, users can restore data from any snapshot, including the ones residing on the old storage. 

Does the flexible storage mapping feature have limitations? 

To know the limitations of this feature, read Changing storage assigned to a user.

Does inSync support 512e/4kn (Advanced format) formatted disks?

No, inSync only supports disks formatted with a maximum of 512 bytes per sector (512n formatted disks).

Can we keep Storage components (Data, DB, and DB logs ) on the same physical drives?

Data, Database and Database Logs must be on separate RAID drives to ensure better read and write performance and to avoid any degradation in overall performance.

Can I use RAID 5 for my Storage?

We recommend RAID 10 for Database as RAID 5 is considered to be less outage resilient than RAID 1 and suffers massive performance degradation during a partial outage. You can refer Pre-requisites and Recommendations for more details on Storage setup. 

Can a third-party application cause Storage corruption?

Yes, it is a possibility. Ensure all the inSync Configuration and Storage Folders are excluded from the anti-virus for Active/On Access/On Demand Scans. Not having exclusions may result in severe corruption of inSync storage data and database files. 

What is a Database and Database log folder?

 The database folder contains metadata information that inSync uses for data deduplication. The database log folder contains logs for all transactions that occur in the database folder. 

What is a Storage Pool?

A storage pool is a collection of storages that functions as a unit to back up data. A storage pool is a collection of file stores. Each file store backs up data. In large deployments where large volume of data flows within an organization, the maximum limit of storage size (64 TB) might be insufficient. The capability to dynamically add storage to a pool ensures scalability and support for organizations that anticipates increasing data needs. 

Can we switch the secondary storage to primary storage?

Yes. From inSync 5.9.6 and later, you can switch the secondary storage to primary storage, if the primary storage cannot be recovered. 

Can I remove an assigned storage from a pool?

No. Once you assign a storage to a pool, you cannot remove it from the pool.

When is the low database alert generated?

When data in a storage or a storage pool exceeds 80% of its maximum capacity, a low database alert is generated. In such cases, you can either add more storage to the pool or compact storage and remove unnecessary data from it.

Can we place inSync Storage components on the OS volume?

The OS must be on a separate disk. inSync Storage components must not be placed on the OS volume. See inSync On-Premise - Storage Pre-requisites for storage prerequisites to deploy inSync On-Premise in your environment.