This section describes:
Notes on back up and restore for multiplex servers and databases.
Special restrictions that apply to backup and restore operations in a multiplex environment
In addition to the usual reasons for backing up and restoring data, you can also use the restore operation to recreate the multiplex on a different system when no problems have occurred.
The BACKUP and RESTORE SQL commands can only be executed on the coordinator node. For complete syntax, see BACKUP statement and RESTORE statements in Chapter 1, “SQL Statements,” in Reference: Statements and Options. To back up the IQ store and catalog store on a multiplex database, log onto the coordinator using an account with DBA or backup authority. The database must not be running to restore a full, incremental since full or incremental restore of either a read-write files only or an all files backup. The database may or may not be running to restore a backup of read-only files. When restoring files in a read-only dbspace, the dbspace must be offline.
Back up the IQ store as described in “Types of backups” in Chapter 12, “Data Backup, Recovery, and Archiving,” in System Administration Guide: Volume 1. The last step of both IQ-level and system-level restores is synchronizing the secondary servers to propagate changes.
You may wish to preserve the server.dbrlog.NNN files (stored in the write server’s directory under /repDirs/logfiles on UNIX or \repDirs\logfiles on Windows).
If using virtual backup, it is critically important to add to your system backup specification all main store dbfiles that are specified in the backup. Use the stored procedure sp_iqfile in creating the system backup list.
Use the stored procedures sp_iqbackupsummary, sp_iqbackupdetails, and sp_iqrestoreaction, the system views SYSIQBACKUPHISTORY and SYSIQBACKUPHISTORYDETAIL and the db_backupheader utility to track backups and plan restore actions.
If symbolic links are used for raw device names, as recommended, be sure the system backup utility follows the symbolic link and backs up the device.
