Anonymous, bureaucrat, administrator
7,528
edits
Changes
no edit summary
# '''Resilience''': critical business functions and the supporting infrastructure are designed and engineered in such a way that they are materially unaffected by most disruptions, for example through the use of redundancy and spare capacity;
# '''Recovery''': arrangements are made to recover or restore critical and less critical business functions that fail for some reason.
# '''Contingency''': the organization establishes a generalized capability and readiness to cope effectively with whatever major incidents and disasters occur, including those that were not, and perhaps could not have been, foreseen. Contingency preparations constitute a last-resort response if resilience and recovery arrangements should prove inadequate in practice.''
# Elimination of single points of failure. This means adding redundancy to the system so that failure of a component does not mean failure of the entire system.
# Reliable crossover. In multithreaded systems, the crossover point itself tends to become a single point of failure. High availability engineering must provide for reliable crossover.
# Detection of failures as they occur. If the two principles above are observed, then a user may never see a failure. But the maintenance activity must.''
In order to deliver against these goals All n One has employed a number of elements:
Our High Availability infrastructure removes single points of failures in any single piece of equipment. [The_bxp_Infrastructure]
Our capacity planning ensures that our services are capable of handling significant load [Business_Express_Infrastructure_Capacity]
== Recovery ==
=== Backups ===
All n One operate backup plans on a number of levels of the solution:
# Client backups [Business_Express_Backups]
# Solution backups
# Infrastructure backups
# Administration and Support backups
Each backup operation has a separate set of procedures associated with them which is available if required through your Buisness Development manager. The only backup of operational influence to a bxp software client are the Client Backups. All other operations are All n One managed procedures.
=== Operational Service Level Agreements ===
The details of operational SLAs are particular to a client and their operational needs. The specifics of your SLA is detailed within you contract. A copy of which is available through your Business Development manager.
== Contingency ==
=== Sungard ===
bxp is delivered against this assurance framework with secure details available to clients through your Business Development manager.