An action of recovering a R/3 system onto track when there is a disturbance in the system. The goal of the disaster recovery is to restore the system so that the company can continue doing the business as earlier. Disaster may be in the form of database corruption, hardware failure and a complete loss of entire R/3 system and infrastructure. Disaster recovery most critical job of a system administrator. Every administrator should understand the importance of disaster recovery before learning anything. The ultimate responsibility of an administrator is to restore a system after a disaster. We should have proper planning for a disaster recovery. There are 3 common disaster scenarios, they are
1. A Database corruption: A corrupted database could result from accidentally loading test data into the production system, A bad transport into production, which results in the failure of the production system. In this disaster case we need a recovery of the R/3 database and related operating system files.
2. A Hardware failure: The hardware failure could result from failure of a system processor, drive controller, multiple drives in the drive array, so that the drive array fails. In this disaster case we need to replace failed hardware, rebuilding the server ( operating system and all programs ) and recovering the R/3 database and related files.
3. A complete loss or destruction of the server facility: This type of disaster may result from a failure of entire server, all supporting infrastructure, all documentation and materials in the building, the building itself. These disasters may result from the disasters like fire, earthquake, flood, Hurricane, Tornado and Man-made disasters. In this case of disasters we need to replace the facilities, replace the infrastructure, replace the lost hardware, rebuild the server and R/3 environment (Hardware, operating system and database) and recovering the R/3 database and related files.