EVALUACIÓN DE LOS ITINERARIOS FORMATIVOS

RSS has a similar setup procedure to HDR. The following sections step through this process, where you just copy the chunks to another location. The process is simplified because there are no archiving algorithms included.

On the Primary

1. Set LOG_INDEX_BUILDS to 1 or ‘ON’ in the onconfig. The engine will have to be recycled for this configuration change to take effect if you just change the parameter in the onconfig file. Alternatively, you can us onmode -wm. 2. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network

connections.

3. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

4. Run onmode -ky.

5. FTP the chunks to the other machine. 6. Run oninit.

7. Run onmode -d add RSS secserver.

On the Secondary

1. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network connections.

2. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

3. Modify the ONCONFIG parameters for the Secondary server: DBSERVERNAME and DBSERVERALIASES.

4. Make sure that all chunk paths are created, have the correct permissions, and ensure there is enough space on the disks for the data to reside.

5. Put the chunks in place that were copied over to this machine. 6. Run oninit -R.

7. Run onmode -l (if necessary). 8. Run onmode -d RSS primaryserver.

As you can see, this process is very simple. However, during testing for this functionality, we found that the RSS in the onmode command is case-sensitive, and upper case must be used.

5.4.1 Setting up RSS with ontape

The following sections show the steps for setting up RSS with ontape.

On the Primary

1. Set LOG_INDEX_BUILDS to 1 or ‘ON’ in the onconfig. The engine will have to be recycled for this configuration change to take effect if you just change the parameter in the onconfig file. Alternatively, you can use onmode -wm. 2. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network

connections.

3. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

4. Make sure the databases to be replicated are in logged mode.

5. Send a copy of the primary instance’s $ONCONFIG file to the secondary server by running ontape -s -L 0.

6. Run onmode -d add RSS secserver.

On the Secondary

1. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network connections.

2. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

3. Modify the ONCONFIG parameters for the Secondary server: DBSERVERNAME and DBSERVERALIASES.

4. Make sure that all chunk paths are created, have the correct permissions, and ensure there is enough space on the disks for the data to reside.

5. Run ontape -p.

6. If necessary, run onmode -l to roll forward any logical logs that may have been saved on the Primary before the physical restore of the Secondary is finished. 7. Run onmode -d RSS primary.

5.4.2 Setting up RSS with an imported OnBar restore

The following steps show how to set an RSS server using an imported OnBar archive. This is very similar to setting up HDR and so should be very intuitive to users familiar with HDR.

On the Primary

1. Edit the $ONCONFIG file to set LOG_INDEX_BUILDS to 1 or ‘ON’

Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network connections.

2. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

3. Make sure the databases to be replicated are in logged mode.

4. Send a copy of the primary instance’s $ONCONFIG file to the Secondary server.

5. Run onbar -b (optionally, you can use onbar -b -w). 6. If you are using ISM:

a. Shut down ISM on both machines.

b. Create a tar file of the storage manager directories. c. Copy this tar file to the target computer.

7. Run oninit.

8. Run onmode -d add RSS secserver.

On the Secondary

1. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network connections.

2. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

3. Modify the ONCONFIG parameters for the Secondary server: DBSERVERNAME and DBSERVERALIASES.

4. Make sure that all chunk paths are created, have the correct permissions, and ensure there is enough space on the disks for the data to reside.

5. Shut down ISM.

6. Untar the storage manager tar from the Primary into the correct directory. 7. Restart ISM.

8. Label the storage media with the correct pool names. 9. Mount the storage devices.

Note: For the purposes of this exercise, we used ISM. For other storage

managers, please check the available documentation to see if it would be possible to back up tapes or if directories can be copied across the network.

10.Transfer the following files from the Primary to the target: a. The emergency bootfile

b. The oncfg.SERVERNAME

c. Storage manager configuration files, if any

11.Update the sm_verssions file on the target computer with the storage manager version.

12.Run onbar -p.

13.If necessary, run onmode -l to roll forward any logical logs that may have been saved on the Primary before the Secondary physical restore finished.

14.Run onmode -d rss primary_server.

5.4.3 Adding an RSS server with an external archive and restore

In this section, we add an RSS server with an external archive and restore. The only fundamental change is the method in which the physical data is transferred to the Secondary. The details of the restore may have more complexity, but the fundamental way in which replication is enabled is the same. This process is almost identical to setting up HDR.

On the Primary

1. Edit the parameter LOG_INDEX_BUILDS in the $ONCONFIG.

2. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network connections.

3. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

4. Make sure the databases to be replicated are in logged mode.

5. Send a copy of the primary instance’s $ONCONFIG file to the Secondary server.

6. Run onmode -c block.

7. Externally back up all logged dbspaces. 8. Run onmode -c unblock.

On the Secondary

1. Add entries to the $INFORMIXSQLHOSTS and /etc/services files for network connections.

2. Modify the /etc/hosts.equiv or the .rhosts file for the informix user ID to enable trusted communication.

3. Modify the ONCONFIG parameters for the Secondary server: DBSERVERNAME and DBSERVERALIASES.

4. Make sure that all chunk paths are created, have the correct permissions, and ensure there is enough space on the disks for the data to reside.

5. Use the external restore mechanism to restore the data on the target. 6. Run onbar -r -e -p.

7. If necessary, run onmode -l to roll forward any logical logs that may have been saved on the Primary before the Secondary’s physical restore finished. 8. Run onmode -d RSS primary_server.