Failures that can occur on a computer server are a server failure (when the entire server is not operating); a loss of the site due to fire, flood, or similar catastrophe; or the damage or loss of an object. For a distributed relational database, a failure on one server in the network prevents users across the entire network from accessing the relational database on that server.
If the relational database is critical to daily business activities at other locations, enterprise operations across the entire network can be disrupted for the duration of one server's recovery time. Clearly, planning for data protection and recovery after a failure is particularly important in a distributed relational database.
Each server in a distributed relational database is responsible for backing up and recovering its own data. Each server in the network also handles recovery procedures after an abnormal server end. However, backup and recovery procedures can be done by the distributed relational database administrator using display station pass-through for those servers with an inexperienced operator or no operator at all.
The most common type of loss is the loss of an object or group of objects. An object can be lost or damaged due to several factors, including power failure, hardware failures, system program errors, application program errors, or operator errors. The iSeries™ server provides several methods for protecting the server programs, application programs, and data from being permanently lost. Depending on the type of failure and the level of protection chosen, most of the programs and data can be protected, and the recovery time can be significantly reduced.
You can use the following methods to protect your data and programs:
Writing data to auxiliary storageThe Force-Write Ratio (FRCRATIO) parameter on the Create File command can be used to force data to be written to auxiliary storage. A force-write ratio of one causes every add, update, and delete request to be written to auxiliary storage immediately for the table in question. However, choosing this option can reduce server performance. Therefore, saving your tables and journaling tables should be considered the primary methods for protecting the database.
Physical protectionMaking sure your system is protected from sudden power loss is an important part of ensuring that your application server (AS) is available to an application requester (AR). An uninterruptible power supply, which can be ordered separately, protects the server from loss because of power failure, power interruptions, or drops in voltage, by supplying power to the server devices until power can be restored. Normally, an uninterruptible power supply does not provide power to all workstations. With the iSeries server, the uninterruptible power supply allows the server to:
- Continue operations during brief power interruptions or momentary drops in voltage.
- End operations normally by closing files and maintaining object integrity.