Supported storage types

This article includes details about supported technologies and storage types in GitProtect system.

Storage types

GitProtect supports 9 storage types:

1. Local directory - a directory created on the local disk of a device with the GitProtect agent (worker) installed.

2. Network location (SMB share) - a secure network location accessible with login credentials; communicates with GitProtect via SMB protocol. Supported SMB versions include SMB 1.0/CIFS, SMB 2.0, SMB 2.1 and SMB 3.0.

3. Network File Storage (NFS share) - a network location that can be accessed only if the endpoint IP address is whitelisted; GitProtect communicates with this type of network share over the NFS protocol. Supported NFS versions include NFSv2 and NFSv3. NFSv4 and Kerberos are not supported.

4. AWS storage - dedicated to AWS S3 datastore.

5. S3 storage - any S3 compatible storage type.

6. Wasabi - storage type dedicated for Wasabi S3 compatible datastore.

7. Backblaze B2 - storage type dedicated for Backblaze B2 S3 compatible datastore.

8. Google Cloud Storage - storage type dedicated for Google Storage S3 compatible datastore.

9. Azure Blob Storage - storage type dedicated to Azure Blob datastore.

---

Local storage

In onsite storage, data and storage hardware are located internally to your business organization. You may have a computer room or a data center onsite where the storage devices are securely located. All your internal systems within the same building or organization will have direct access to the storage, usually over an internal Local Area Network (LAN).

---

Immutable storage

GitProtect supports S3-type immutable storage as a backup location. This feature is available for some of cloud storages supported by GitProtect (AWS, Wasabi, Backblaze B2 and Google Cloud Storage). Datastores of this type allow you to freely save and read data, but modification and deletion are only possible after meeting the bucket’s retention policies.

Advantages:

• Protection against ransomware and other threats (cyberattacks) – files in immutable storage are read-only and immune to loss, accidental deletion, corruption, and other issues that could compromise your data.

• Prevention of accidental file deletion – when access to important or critical data is shared, the risk of deletion or modification increases, which immutable storage feature prevents.

• Preservation of file authenticity – ensures data accuracy by preventing modification or manipulation of uploaded files.

• Compliance with legal regulations – meets requirements for storing confidential data (e.g., payment or medical records).

---

Useful links and items

Xopero Cloud Storage

S3 Object LockAmazon Web Services, Inc.

How to Enable Object Lock or a Legal Hold on an Existing Bucket in Backblaze B2 Cloud Storagewww.backblaze.com

Protecting Cloud Storage with WORM, key management and more updates | Google Cloud BlogGoogle Cloud Blog

Immutable Storage with S3 Object Lockwasabi.com