Brochures

Claranet | Data Protection Bimodel World White Paper

Issue link: https://insight.claranet.co.uk/i/1019714

Contents of this Issue

Navigation

Page 6 of 7

Data Protection White Paper 7 Object Storage: An All in One Solution Object storage is the storage technology used by companies such as Dropbox, Spotify, and Facebook. Object storage is an architecture for the storing of unstructured data. It manages data as objects, as opposed to other storage architectures like file systems which manage data as a file hierarchy, and block storage which manages data as blocks within sectors and tracks. Object storage has almost limitless scalability and the object typically includes the data itself and a variable amount of metadata. The metadata adds meaning and characteristics to the object that are not possible with traditional unstructured data repositories. This means lifecycle management policies are easily employed as well as RPO and RTO policies that determine durability and data protection capabilities, plus access policies and content integrity seals that ensure the information chain of custody. Much of this capability is built into object storage platforms today by means of technologies such as deduplication, data virtualisation, erasure coding, hashing algorithms, point- in-time snapshot, and object immutability. This makes object storage the perfect platform not just for the scalable and cost effective storage of unstructured data, but to meet compliance and data protection demands. It's an object store, a file store, an archive – all in one. And it's self-protecting, so no backup required. Advice for Effective Data Protection Data protection can be overwhelming with the many options on the market. Here you'll find advice for effective data protection. Produce a service catalogue. Together the business and IT must set out and agree a range of RPO and RTO policies that meet business needs. These can be combined to produce a set of service classes e.g. Gold, Silver, Bronze, that mean something to the business and IT in a language they both understand. It sets out clear SLAs and helps distinguish the difference in cost for each service. Understand application taxonomy. The business customer will want to associate an application with a service class whereas IT will associate a LUN or server name. Each application will be made up of inter-dependent component systems offering a particular service to the application (database, web interface, application server, firewall, load balancer, content system, etc.). The recoverability of each might be just as important to meeting the RTO or RPO demand of the application. Align the appropriate service class. Once the service classes are defined and the application taxonomy understood, it is essential to align them, ensuring the business agrees the relevant service for each application and understands the cost and risk implication of each. Streamline your processes. Everyone needs to talk. It is no good having database administrators, storage managers and backup operators all operating as islands. It's costly and it's risky. Make somebody accountable and responsible and give them the authority to execute. Know your data types. Approach the protection of structured and unstructured data in different ways – ways that are more appropriate for their unique use cases. Block and file will soon become block and object, and as you travel down that transition the ability to simplify and improve data protection processes will emerge. Differentiate backup and archive. Don't try to deliver compliance through an archive system built on a backup system. It's a false economy and rarely services the needs of the business. Choose appropriate technology. The key to getting the right solution is the service class definition. Once defined, selecting the technology becomes simpler and to a large extent commoditises the process, putting you in control. You know what you have to deliver and the service alignment process tells you to what scale. Listen to what the technology can do and how it does it, but make your decisions based upon what you need and always base your buying decisions on cost, service, and risk. If you're going to spend money, the solution must improve at least one of these and preferably all three. 1 2 3 4 5 6 7

Articles in this issue

view archives of Brochures - Claranet | Data Protection Bimodel World White Paper