Restoring IQ Store Data When Restoring Database in a Different Location

Restore operations vary, depending on the location from which you restore.

Prerequisites

Confirm that there are database home directories for each server. If not, create them or restore them from file system backups.
If this is not the first time you have restored to the new location, shut down all multiplex servers running at the destination location (coordinator and secondary servers). The multiplex at the original location where the backup was taken may continue running.
Note: If automatic startup is enabled in your ODBC configuration, there may be users on the same machine as the server who are set up to automatically start the server. Prevent this from happening while you are restoring the database.

Confirm that the database shut down successfully:

Platform	Actions
UNIX	% ps -ef \| grep iqsrv16 If you see an active iqsrv16 process with name of a multiplex, stop the process.
Windows	In Task Manager, check the Processes tab for iqsrv16.exe, or find the IQ Server icon in the system tray and stop it using right-click and Shutdown.

Platform

Actions

UNIX

% ps -ef | grep iqsrv16

If you see an active iqsrv16 process with name of a multiplex, stop the process.

Windows

In Task Manager, check the Processes tab for iqsrv16.exe, or find the IQ Server icon in the system tray and stop it using right-click and Shutdown.

Make a file system copy of the .iqmsg file. If you have message log archiving configured, see Back Up the Right Files in Administration: Backup, Restore, and Data Recovery.

Task

Shut down the original coordinator, then start the utility database from the coordinator server directory using the coordinator server’s name:
```
% start_iq -n coordinator_svr -c 32MB 
-x tcpip(port=1234) 
```

Connect to the utility database (utility_db).

% dbisql -c "eng=coordinator_svr;uid=DBA;pwd=SQL;
dbn=utility_db" -host myhost -port 1234

Run the RESTORE command with a new location path for the database and its dbspaces. To restore certain dbspace files to a different path, specify a RENAME clause. Perform full and any incremental restore operations in sequence, without stopping the utility database.

Warning! Stopping the utility database between full and incremental restore operations may invalidate the catalog and render the restored database unusable.
Start the restored database either by reconnecting to the utility_db server and specifying the restored database file name, or by stopping the server and restarting it with the restored database. If you restart the server, use the single-node and override flags (-iqmpx_sn 1 -iqmpx_ov 1).
Use DROP MULTIPLEX SERVER statement to drop all the secondary nodes. For example:
```
DROP MULTIPLEX SERVER node_w3_skm
```
Once you drop the last secondary node, the coordinator shuts down automatically, signifying conversion to simplex.
Restart the coordinator without the single-node or override switch.
Re-create all the secondary nodes with the correct location path, including the database file extension (.DB):
```
CREATE MULTIPLEX SERVER node_r2_skm DATABASE
'/sunx3005/mpx_simdb.db'
HOST 'localhost' PORT 8998
ROLE READER STATUS INCLUDED
```
After you create the first secondary node, the server automatically shuts down, signifying conversion to multiplex.
When you restart the coordinator, you see a warning in the server log about the multiplex environment being invalid. This warning is generated if IQ_SYSTEM_TEMP dbspace does not contain any files, and is the case for all the secondary nodes you created in step 7. Ignore this warning for now.
Synchronize and restart the secondary servers.
Connect to each secondary server and add files in IQ_SYSTEM_TEMP.
Run sp_iqmpxvalidate on the coordinator. It should report no error detected.

To restore an exact copy of the multiplex to a different location, when copies of all of the server's temporary files exist at the new location, replace steps 5 through 11 with:

Use ALTER MULTIPLEX SERVER to alter the server name, host, port, and database path of each server.