The following section described the requirements and restrictions for Hot Backup.
The master and slave servers used in a Hot Backup configuration should be of equal performance and operating systems.
The servers are connected using TCP/IP via Ethernet cards. It is recommended that Hot Backup transmissions use a different network card than the card used for normal user traffic.
The servers involved in a Hot Backup configuration must be running the same base release of D3, and must be patched to the same level with the latest public patches from Rocket.
These restrictions apply to Hot Backup implementations.
save command
Special care must be taken when using the (k option of the save command in a Hot Backup implementation. Additionally, the queue on the master server should be empty. Enqueuing on the master should be stopped until the save completes. The (k option reorganizes all file-of-files numbers sequentially on the tape.
To use the (k option of the (k command, you must ensure that Hot Backup is stopped on both servers. Once Hot Backup is stopped, you must run the save with the (k option on both servers.
File-of-Files D-pointer
If the D-Pointer for the file-of-files is not set to DX, it is possible that, following a restore, updates to the slave server may not update the correct files. Additionally, transaction processing performance may degrade. These problems occur because the process cannot correctly identify the file-of-files record. If the process cannot identify the file-of-files record, a temporary file (servername*file-of-filenumber) is created in the data section of the hb.log file where servername is the Hot Backup server name and file-of-filenumber is the file-of-files number for the file concerned. These files are created with a modulo of 31, and thus can quickly fill up with data and overflow, resulting in performance degradation.
To avoid this problem, set the D-Pointer for the file-of-files to DX and perform a file-save and restore.
Loading ABS patches