List of questions
- What is an object store?
- What are the benefits of creating object stores?
- What do I need before I create object stores?
- What is OpenStack Swift?
- Does Druva help with Swift configuration?
- How do I ensure that inSync can work with OpenStack Swift?
- What authentication does inSync support for accessing object stores?
- How many nodes of Swift do I need? How should I configure them?
- What is the throughput and latency that Swift should have?
- How do I configure inSync Private Cloud with Swift?
- Where can I find the inSync object store logs?
- Can I change the Swift IP address?
- What do I do when my inSync object store is almost full?
An object store is a type of storage that is designed to treat data as an object. Each object contains data and metadata, and is associated with a unique identifier. Numerous such objects are arranged in a flat hierarchy and are typically accessed using some API. inSync supports the creation of object stores, provided that you implement it using OpenStack Swift (Swift). The Swift object store arranges data within "containers" designated for such a purpose. To know more about OpenStack Swift, see https://wiki.openstack.org/wiki/Swift.
When you create an inSync object store, inSync creates a container within Swift. This container holds backup data. inSync creates such containers for each object store that you create. Because inSync object stores are instances within Swift, they come with all the benefits of Swift. They are highly scalable and can handle large volumes of concurrent requests. The Swift architecture ensures that inSync object stores can be managed centrally.
inSync Private Cloud uses the OpenStack Swift object store service to create instances of object stores. To get started, make sure that you configure OpenStack Swift for your organization. You can then configure your Private Cloud setup to work with Swift.
OpenStack Swift is a cloud-based object store service. Organizations can use the Swift service to store large volumes of data. Because Swift makes use of simple APIs for data access, organizations can ensure speedy retrieval of their data. To know more about Swift, see https://wiki.openstack.org/wiki/Swift.
No, we do not. You must perform the installation and configuration of Swift by yourself.
inSync Private Cloud works with OpenStack Swift in conjunction with Keystone. Keystone performs authentication for data access within the Swift containers. To ensure that inSync can work with Swift, make sure that your Swift object store is configured to recognize Keystone. To know more about Keystone, see https://wiki.openstack.org/wiki/Keystone.
inSync supports OpenStack Keystone as the identity provider. Before you create object stores for your setup, you must configure Swift to work with Keystone. To know more about Keystone, see https://wiki.openstack.org/wiki/Keystone.
We do not recommend the type of configuration or the number of nodes for the Swift object store. You should get in touch with your Swift administrator for assistance with installing and configuring object store nodes.
We recommend the latency to be approximately 10 ms. To ensure uninterrupted backups and restores, we recommend that the throughput be a value that is equivalent to the aggregate of write speeds for all backups.
To ensure that inSync Private Cloud works with Swift, you must first create an object store. During the creation, provide your Swift details such as the Swift FQDN, access key, and pass key. This should ensure that your inSync setup can work with Swift. For more information, see Creating an object store.
The object store activities are captured in the standard storage log files. You can find them here:
- Windows: C:\inSyncCloud\logs
- Linux: /var/log/inSyncCloud
No. As a good practice, we recommend that you enter the fully qualified domain name instead of the IP address while creating an object store. If you choose to use an IP address, make sure that you leave this value unchanged. At present, inSync does not permit modifications to the object store configuration.