Name of Solution:
Business Volume Qualicision (BVQ)
BVQ Service Level Management Package
The BVQ Service Level Management (SLM) Package supports the storage administration at the supervision of Service Level Agreements (SLA) and the compliance of security-relevant regulations that concern the storage location of data.
With a SVC or Storwize storage system, data can be migrated completely transparent between different storage-classes, without noticeably changing their service-quality. In this way, SLAs can be compromised or in the worst case, security measures like the spatial separation of data-mirrors can be changed without any warning.
The control of the volume placement is further impeded, through the mostly very large number of storage objects.
The SLM Package supervises the compliance of storage regulations, SLAs and other storage rules to maintain the planned security and compliance levels.
Description of Solution
The BVQ SLM Package provides functionalities, with which SLAs or other security-relevant storage rules are stored, and their regular adduction is simplified. A Service Level Agreement is thereby the agreement to store volumes, for a predefined period of time, on determined storage qualities. A storage rule is an agreement that volumes have to be stored together in different or same storage locations. The SLA rules are agreed for volume groups. In these rules, the prices, duration and the data-classes are determined for the all volumes belonging to these volume groups. The data classes are connected via an evaluation-matrix with the technical storage-classes. With this matrix it is determined, whether the SLA at the storage location is fulfilled optimally, acceptably or not at all.
Picture 1: These BVQ-Objects are applied for the SLM Package.E.g., If a SLA or a storage rule is compromised due to a erroneous data migration, the involved volumes are marked and configured alerts in the BVQ System are triggered.
- SLA Objects describe the agreement to store volumes on a specific storage quality for a certain period of time. A SLA object stores the Start-, End time, the costs and the storage locations for the primary and secondary copies of data.
- Primary Copy Data Class and Secondary Copy Data Class describe on which storage- class the data objects are ought to be stored. The abidance of the SLAs can be inspected, via Object Color Overall Compliance.
- Data-Classes describe the storage quality from the customer's view Typical Data classes are Highend, Lowend, Archive Price for each GB – "at what price is the storage offered?"
- Storage-Classes describe the storage quality from a technical point of view. Every SVC / Storwize Volume Group (MDG) can be allocated to a storage class. In the Storage class the deployment costs are comprehended in $/GiB or €/GiB. Typical Storage-Classes are SATA, SAS, SSD, Gold, Silver, Bronze Price for each GB – "how much does the operation of the storage cost?"
- Placement Rating Objects link the data classes with the storage classes in the form of a rated matrix. It is thereby determined whether the usage of a storage class to store data of a data class is acceptable or not.
Examples:Data-Class Highend on storage class Gold is optimal (green – optimal) Data-Class Highend on storage class Silver is suboptimal ( yellow - too risky)Data-Class Archive on storage class Silver is unacceptable (red - too expensive)
Assessment and Display of the SLM Information The evaluation of the SLM information can be performed on the BVQ treemap and from BVQ version 3 in an integrated BVQ alerting module. SLM information can also be read via ODBC directly from the database BVQ
At a display via the Treemap objects are portrayed with the evaluation-method „Object Color Overall Compliance", depending on Rating in the corresponding colors.
- Green: Storage capacity is optimal
- Yellow: Storage capacity is still acceptable
- Red: Storage capacity is not acceptable
A display via the Treemap has the special advantage, that indicates „still acceptable" areas, which one would not necessarily consider in an alerting. Via the Treemap particular areas can easily be composed, which were possibly affected by undesired changes on a large scale.
Picture 2: The abidance by the SLAs is displayed via a certain object coloring „Object Color Overall Compliance" in the Treemap. This object coloring is very flexible and can be expended on all Treemap settings. Since BVQ Version 3.0 SLA breaches can also automatically issue an alert.
Identifying Critical Storage Relations„Disk Group Relations" and Mobility Zones
These regulations assist the administrator in assuring, that it does not belatedly lead to undesired errors via the application of the SVC data migration in the distribution of disks. A critical error can take place, if the two mirrors of a LVM System by mistake in the same site or even lie in the same storage system through data migrations.
- VDisk Group Relations: Inspects the positioning of V-Disk Groups among each other. A typical application of Disk Group Relations is ought to be assured, so that two LVM mirror- volumes are not deposited in the same storage system or the same physical location (room, site).
The regulations describe whether V-Disks from V-Disk Groups have tob e stored at the same location (Colocated) or are not allowed to be stored at the same location (Antilocated). The storage locations thereby cover M-Disk groups, M-Disks, Arrays, Controllers, Nodes, IO-Groups, Clusters, Rooms, Sites.
- Mobility Zones: SVC M-Disk Groups and BVQ V-Disk Groups are allocated to a mobility zone. It primarily serves to limit the decision for the placing of V-Disks on selected M-Disk Groups.
A Mobility Zone serves to ...
Assist the user with determining narrowly aimed placement requirements.
- Assist the user with selecting a possible algorithm of appropriate M-Disk groups for a V-Disk migration.
- Carry out the Compliance evaluation about whether the current V-Disk placement complies with the requirements and their indication in the color-scheme of Mobility Compliance.
Picture 3: Via the Treemap the SLA or security breaches can be easily identified and localized. In the objects one can find corresponding hints on the reason that lead to the indication of the error.
Licensing for BVQ Service Level Management (SLM) Package
The BVQ SLM Package is licensed differently, depending on SVC/Storwize System:
- BVQ Base Edition for IBM SAN Volume Controller Licensing on the bases of capacities held available in the SVC.
- BVQ Base Edition for IBM Storwize V7000 Licensing on the bases of the V7000 Enclosures
- BVQ Base Edition for IBM Storwize V3700 Licensing on the bases of the V3700 Systems
- Hybrid Forms of SVC and Storwize Products Special License on demand in order to avoid Double Licensing
More specific information in the Internet
- BVQ Website with customer references and Page for BVQ distribution partners http://www.bvq-software.de/
- BVQ Wiki for documents and extensive technical Information http://bvqwiki.sva.de
- Developer Works BVQ Community Blog https://www.ibm.com/developerworks/mydeveloperworks/... +http://tinyurl.com/bvqblog+