List of questions
- What is the maximum number of storage nodes that I can create?
- What is the maximum number of storage that I can create?
- Does Druva recommend the number of storage?
- Can I create the Database folder on NAS?
- What is the minimum disk space for Data, Database, and Database log?
- How many data volumes can I add to a storage?
- What happens if I change a user's storage?
- Do users come to know if their storage changes?
- Do users start backing data to the new storage immediately?
- If I change a user's storage, is the first backup a full backup?
- Are old snapshots retained on the earlier storage?
- Can users restore data from any snapshot?
- Does the flexible storage mapping feature have limitations?
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.
inSync does not set restrictions on the number of storage that you can create. However, the sum of storage space should not exceed 64 TB. You can get an estimate of how much storage you might need by using the inSync Deduplication Savings Calculator available at http://www.druva.com/insync/roi-calculator/.
No, we do not. But as a general rule, create as few storage as possible. This helps you take advantage of inSync's data de-dupe functionality.
The Database folder contains metadata about backup data. inSync server 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.
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. Also, the Database and Database log folders require a minimum free space of 4 GB. The minimum disk space for Data folder is 1 GB.
You can add up to 10 data volumes to an existing 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.
No. Users will not know that their storage has changed.
Yes, users can start data backup as soon as they move to the new storage.
Yes. The first backup is a full backup. Thereafter, all backups will be incremental in nature.
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.
Yes, users can restore data from any snapshot, including the ones residing on the old storage.
To know the limitations of this feature, read Changing storage assigned to a user.