Structure of an inSync storage
inSync Private Cloud supports the creation of two types of storage: File store and Object store. The following diagram explains the structure of both types of storage.
As illustrated, both File Store and Object Store contain a database folder and a database log folder. The database folder contains metadata information about the data deduplication implemented by inSync. The database log folder contains logs for all transactions with the database folder.
The difference between a File Store and an Object Store is how deduplicated data backed up from user devices is stored. While a File Store uses a data store for this purpose, an Object Store uses a Swift store.
|Data Store||Swift Store|
|In a data store, deduplicated data is stored in data volumes. Data volumes are discrete units of storage on a physical disk that supports data. Each data store can contain up to 10 data volumes. The total deduplicated data contained in a data store is an aggregate of the data stored across the data volumes.||Deduplicated inSync data is stored as objects within the OpenStack Swift object store deployed in the organization's data center. As an object store is implemented as a service, multiple instances of inSync object stores can be created using OpenStack Swift. You can access object stores using a URL that point to the Swift object store service.|
Difference between file store and object store
This table describes the differences between file store and object store.
|Property||File Store||Object Store|
|Deduplicated data stored in...||File system|| |
Note: inSync supports object store implemented with OpenStack Swift in conjunction with OpenStack Keystone only.
|Increase storage capacity by...||Adding up to 10 data volumes.|| |
Increasing the size of the storage.
Note: Before you increase the size of your object store, make sure that your Swift object service is supported by hardware that enable scalability.
|Maximum size||64 TB|| |
Note: A single implementation of Swift can contain multiple inSync storage.
|Support for storage pools||Yes||No|
Guidelines for creating a storage
When creating a storage, follow the guidelines specified in the table below.
|Data folder (for a file storage)|| |
Note: For a backup to be successful, there must be at least 10 GB of free space on the storage data folder. inSync checks for this condition every 10 minutes and if it is not satisfied, ongoing backups are stopped and scheduled backups are put on hold. Backups do not start until you increase the free space to at least 50 GB.
|Database folder|| |
|Database log folder|| |