Tailored SwiftStack update should help get your GDPRse in gear
But code and admin roles more complicated as a result
Object storage life is getting more complicated as public cloud dispersion meets GPDR data locality restrictions. Combining the two adds product and administration complexity.
Against this background SwiftStack has updated its open-source, object storage product with features for public cloud archiving, synchronization, and multi-region data management.
V5.0 SwiftStack was introduced in March this year, with Cloud Sync, a replication facility for on-premises to/from public cloud data movement.
We now have v5.9, the second significant product update this year, which boasts new options for multi-region data durability and policies in its single namespace while providing GPDR-driven options on data locality.
The Cloud Sync tool has policy-driven features for public cloud archiving and on-premises data rehydration, in which archived data is automatically rehydrated to on-premises infrastructure when requested.
There's a quasi form of stubbing. SwiftStack auto-tiers cold data to public clouds, with the data still accessible in a single namespace and, via an icon (quasi-stub) in the namespace listing, flagged as being at rest remotely. When the data is accessed then it is brought back on-premises.
V5.9 now offers multi-region erasure coding. SwiftStack says that, rather than spreading parity bits across all available regions, it "uses the nodes in each region and keeps the data whole in each global location. This makes data more likely to remain available even if an entire server node goes offline, and reduces the need to transfer large amounts of data from another region in the event of a request or rebuild."
Public cloud data placement can now be controlled more precisely, as admin staff "can specify how many replicas of the data should be kept in each region, and which nodes within regions to store the data based on a tiering strategy that combines high-capacity nodes and low-latency nodes with solid state drives.
"If a region goes down or an application has to be moved, data is automatically accessed on nodes in another region without requiring any changes."
SwiftStack says legacy applications can access and consume the same data from the single namespace via file services, with cloud-native applications doing it via object APIs.
Against a background of legacy apps co-existing with, and transitioning to, cloud-native ones, granular GPDR data placement controls meet the desirability of multi-region, multi-cloud archiving. SwiftStack life gets more complex as a result. ®