Avoid mission critical security vulnerabilities with Service
Level Management a practical approach
We mirror storage volumes, especially in mission critical environments, to avoid that a simple technical failure leads to application downtime and loss of production.
With SVC or Storwize it is very easy to migrate volumes between different storage systems, and with this it may happen that two sides of a mirror are moved to the same site or even worse to the same storage system.
Highly explosive to this situation is, that SVC or Storwize migrates volumes completely transparent, and the server administrator has no way and no tool to recognize this move.
He will only be surprised at the time of a one sided storage failure or controlled shutdown, that the security levels for his mission-critical systems have not been met.
This is a situation, where service level management can help. A defined service level rule for this situation can be: "A volume of class A is not allowed to be stored on the same storage system or in the same geographic site as a volume of class B".
Now a tool is needed, which is continuously monitoring this rule and raises alarm, when this rule is no longer met.
Monitoring rules like this is part of the BVQ Service Level Management Package.
Here is how it works:
Avoid mission critical security vulnerabilities with SLM