Restoring IQ Store Data When Restoring Database in a Different Location

Restore operations vary depending on where you restore the data.

1. Confirm that database home directories for each server still exist. If not, create them or restore them from file system backups.
2. 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). In Sybase Central, right-click the multiplex and use the Stop Server wizard. The wizard lets you stop one or more 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, users on the same machine as the server may be set up to automatically start the server. Prevent this from happening while you are restoring the database.

3. Confirm that the database shut down successfully:

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

4. Move files required for debugging and reconfiguring the multiplex.

   • Make a file system copy of the .iqmsg file. If you have message log archiving configured, see System Administration Guide: Volume 1 > Data Backup, Recovery, and Archiving > System-Level Backups > Back Up the Right Files.

5. 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) 

6. Connect to the utility database (utility_db).

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

7. Run the RESTORE command with a new location path for the database and all of its dbspaces. To restore certain dbspace files to a different path, specify a RENAME clause. See Reference: Statements and Options > SQL Statements > RESTORE Statement.
8. 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).
9. 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.

10. Restart the coordinator without the single node or override switch.
11. Recreate 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.

12. When you restart the coordinator, you see a warning in the server log about the multiplex environment being invalid. This warning displays if IQ_SYSTEM_TEMP dbspace does not contain any files, and is the case for all the secondary nodes you created in step 12. Ignore this warning for now.
13. Synchronize the secondary servers, following the instructions in Multiplex Server Synchronization .
14. Start the secondary servers.
15. Connect to each secondary server and add files in IQ_SYSTEM_TEMP.
16. Run sp_iqmpxvalidate on the coordinator. It should report no error detected.