Overview
General information
Storages are locations where backups are saved. GitProtect allows users to define multiple datastores, which can be linked to any backup plan — during a backup, the worker writes data directly to the selected datastore without external intervention.
There are nine types of storage that an administrator can create and use within GitProtect system. Storage management is available in the Storages tab in GitProtect Management Service admin panel.
You can use network resources as storage in GitProtect, connect them to your local computer via the iSCSI protocol, then add them as a local directory.
Adding new storage
You can add a new storage via Management Service, in Storages menu (Storages > (+) Add storage). Regardless of the storage type, you can define the Storage name and Optional description — these fields can help you in identifying storages when using multiple instances.
When configuring a storage, ensure you specify credentials and the storage location correctly. Additionally, review and set up the Default worker section, which identifies the device that manages communication with the storage system.
In the updated architecture, the Management Service no longer directly interacts with the storage system. Instead, all storage operations are managed by a designated worker. When an operation is initiated via Management Service, the request is routed to the worker, which then performs the necessary storage tasks.
Ensure the designated worker has direct storage access. In SaaS deployments, switch the default cloud worker to a local worker with proper connectivity.
Credentials
Most storage types require you to provide credentials (passwords or tokens) for additional security. To access stored credentials, navigate to Settings > Password Manager in GitProtect Management Service. Here, you can securely manage and update passwords and tokens, all of which are encrypted for your safety.
Last updated