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.
What is the difference between objects and files? Objects are large collections of data collecting or storing items. Files are a single potential piece within an object.
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.