My main use case for DataCore Swarm is in a big company in Italy that has two problems: it has very big data to manage, and it has two sites approximately 30 kilometers apart, and we need to save and protect that data.
We use DataCore Swarm essentially for backups, utilizing immutable backups and dynamic archiving from the file server. We also have a project called the Fiservo, which allows us to move the archive and all files from Fiservo.
The most common implementation relies on versioning of S3 protocol objects and therefore the possibility of immutability in governance or compliance mode with DataCore SWARM. This allows us to store immutable backup sets in order to guarantee our customers a local set for restoring IT production even in the event of a cyber attack. The other use case is to couple DataCore SWARM with another archiving tool. This combination allows folders and files that are considered archives to be offloaded to large file servers. Folders and files are moved from production environments that most often use expensive SSD or NVME drives to low-cost NL-SAS storage. These unloads can be processed according to different Lifecycle policies on the archiving tool, management rules can then be applied to the objects stored on the SWARM DataCore.
File and Object Storage offers scalable solutions for data management, providing flexible access to unstructured data. These storage types are crucial for budgets and efficient data retrieval. File Storage manages data in a hierarchical structure, using directories to organize records, enhancing human readability and ease of use. It is ideal for data environments with multiple users accessing shared files, such as databases and multimedia servers. Object Storage, however, handles data as...
My main use case for DataCore Swarm is in a big company in Italy that has two problems: it has very big data to manage, and it has two sites approximately 30 kilometers apart, and we need to save and protect that data.
We use DataCore Swarm essentially for backups, utilizing immutable backups and dynamic archiving from the file server. We also have a project called the Fiservo, which allows us to move the archive and all files from Fiservo.
The most common implementation relies on versioning of S3 protocol objects and therefore the possibility of immutability in governance or compliance mode with DataCore SWARM. This allows us to store immutable backup sets in order to guarantee our customers a local set for restoring IT production even in the event of a cyber attack. The other use case is to couple DataCore SWARM with another archiving tool. This combination allows folders and files that are considered archives to be offloaded to large file servers. Folders and files are moved from production environments that most often use expensive SSD or NVME drives to low-cost NL-SAS storage. These unloads can be processed according to different Lifecycle policies on the archiving tool, management rules can then be applied to the objects stored on the SWARM DataCore.
We use it for customer archiving. Our customers also use it for their immediate payments, autonomous cloud, and on-premise object storage.