Hyperglance can also be used to orchestrate DR invocation. Failing over service to a DR centre is extremely complicated and requires tasks to be performed in strict order to avoid extended outages and data synchronicity issues. It is therefore normal for invocation to be controlled from a central desk with each task status being manually tracked before other tasks are able to be started.
Using Hyperglance, the bank will be able to visualise the readiness status of each different component, down to an application level.
page 1 of 4
It can show the status of the underlying technical infrastructure required to support service, and where the data is available, show the status of the applications to ensure readiness is maintained at all times.
Using filtered views Hyperglance will be able to visualise exposures such as application and operating system version differences, something that is very hard to maintain given the volume of changes implemented and the complexity of an investment bank IT infrastructure.
page 2 of 4
The FSA now mandate that banks must have a DR capability for their critical IT infrastructure and they will audit companies to look at this. They must be able to show that the capability is there to run their business in the event of a failure in one of their main centres. This means that they have to maintain the underlying technical infrastructure in another location and have a documented (and tested) procedure for failing over to this other facility.
We have an investment bank that is interested in using Hyperglance to help them maintain and invoke DR. Hyperglance can be used to visually show the status of a DR capability.
page 3 of 4
This will ensure that the DR capability is made live in an orderly fashion, decreasing the down time and reducing the potential for data loss or synchronicity issues.
page 4 of 4