High availability refers to a system that is almost always operational. When designing a system for high availability, consider how much down-time is acceptable for the system. To minimize time down, consider a combination of failover processing, server or server process redundancy, and frequent back-ups:
If a BusinessObjects Enterprise service fails, a fault-tolerant system allows for continuous processing of system requests with no loss of service. To achieve this level of availability, you should provision duplicate BusinessObjects Enterprise services. For example, if a Web Intelligence Job Server process fails, the duplicate Web Intelligence Job Server process immediately takes its place.
A disaster recovery plan can minimize the effects of a disaster on an organization so you can maintain or quickly resume important system functions. It is good practice to keep the backup system at a different geographic location.
The BusinessObjects Enterprise disaster recovery plan involves implementing redundant servers that mirror the primary system. If the primary system goes down, a backup system is still available and becomes the production system.
Regular and frequent backups provide an easy, cost-effective, and reliable method of protecting your valuable data. During a catastrophic system failure, the entire system can be quickly restored to the last backup point without the need to recreate a lot of data.
Note: When you back up your primary system, you must back up:
You may not have the resources to implement a high degree of availability, but you can use best practices to provide the best possible availability for your system. These include vertical scaling (adding redundant server processes to a system in case the primary server process fails) and maintaining a regular back-up schedule.
|
Copyright © 2010 CA.
All rights reserved.
|
|