HADR Details -- Infopops

Goes to the previous page of the wizard.

Goes to the next page of the wizard.

Performs all specified actions and closes the wizard. Available only when all required fields are completed.

Cancels any unsaved changes and closes the wizard.

Opens a wizard where you can set the database logging type for the primary database. Available only when the logging type of the primary database is not set to archive.

Clear to specify that index builds on the primary system not be logged. It is recommended that complete information is logged for all index operations that are logged. Although this means that index builds might take longer on the primary system and that more log space will be required, the indexes will be rebuilt on the standby system during HADR log replay and will be available if a failover occurs.

If index builds on the primary system are not logged and a failover occurs, indexes will have to be recreated on the new primary after the failover operation is complete.

Clear to specify that invalid indexes should not be rebuilt when the takeover operation is complete.

It is recommended that invalid indexes be rebuilt after a takeover operation is complete because if any index builds have not been logged, this setting allows DB2 to check for invalid indexes and to rebuild them. This process takes place in the background, and the database will be accessible once the takeover process has completed successfully.

If transactions access an invalid index before they are rebuilt, the invalid indexes will be rebuilt by the first transaction that accesses it.

Select the standby system name. Click the down arrow to see a list of the cataloged systems that are the same operating system type as the primary system. If the standby system that you want to select is not in the list, click Add to add it.

Opens a window where you can add a system to be used as the standby system.

Select the standby instance name. Click the down arrow to see a list of the single partition cataloged instances that are the same operating system type as the primary instance. If the standby instance that you want to select is not in the list, click Add to add it.

Opens a window where you can add an instance to be used as the standby instance.

Specifies that the standby database be created and initialized using a backup image of the primary database. You can select an existing backup image or create a new one. The following pages will guide you through the process of initializing the standby database.

Specifies that an existing database be used as the standby database. If there is no database cataloged with the same name as the primary database, you must catalog the database to continue. If there is more than one database cataloged with the same database name as the primary database, you must select which alias to use. Click the Add database button to select an alias for the standby database.

Opens a window where you can add a database alias to be used as the standby database. Select the database alias to use as the standby database. Click the down arrow to see a list of database alias to choose from.

Specifies that a split mirror be used as the standby database. To create a split mirror consult the storage vendor documentation for your device. Exit from this wizard to perform the split mirror operation. Once you have created the split mirror, return to this wizard to configure the new database as the standby database.

Specifies that a backup image is to be selected from the list of current backup images provided.

Specifies that a backup of the primary database is to be taken. When selected, the backup button is enabled.

Specifies that you will enter the location of the backup image that will be used to restore the standby database. When selected, you must specify the media type, the location, and the timestamp of the backup image that you want to use.

Shows current database-level backup images. Only full backup images are included in this list. Select the backup image to be used to restore the standby database.

Opens a wizard where you can perform a backup on the primary database.

Select the media type for the backup image that will be used to restore the standby database. Click the down arrow to see a list of media types to choose from.

Specifies that the backup image to be used is located on the primary system

Specifies that the backup image to be used is located on the standby system.

Shows a list of backup image locations.

Opens a window where you can select the location of the backup image. If you specified that the backup image is located on the primary system, the path displayed will be for the primary system. If you specified that the backup image is located on the standby system, the path displayed will be for the standby system.

Opens a window with the location of the selected backup image. Use this window to select a different backup image location.

Removes the selected item from the list.

Select the date on which the backup image that you want to restore was taken.

Select the date on which the backup image that you want to restore was taken

Specify the time that the backup image that you want to restore was taken.

Select to specify a number of I/O sessions that you want to use during the restore operation.

Specify the number of I/O sessions to use during the restore operation. The default is 1.

Specify the name of the shared library containing the vendor restore I/O functions to be used. Specify the full path. If you do not specify the full path, the default path is the location where the user exit program resides.

Opens a window from which you can view available items and select one.

Specifies that the backup image files must be copied from the primary to the standby system.

Specifies that the backup image files are not to be copied from the primary to the standby system because the image location is already accessible on the standby system.

Specify a location for the backup images on the standby system.

Opens a window where you can select a location for the backup images on the standby system.

Shows the command syntax for the restore operation. Click [...] to specify advanced restore options.

Opens a wizard where you can view the default restore options and make any necessary changes.

Click the Add database button to select an alias for the standby database.

Opens a window where you can add a database alias name for the standby database.

Select the database alias for the standby database. Click the down arrow to see a list of cataloged databases with the same name as the primary database.

Shows a list of backup images on the primary system. You can specify where you want the image to be located on the backup system by clicking [...]. If a backup image is already accessible on the standby system, clear the corresponding check box to indicate that the backup image not be copied to the standby location.

Specifies that you will use the following table to enter the location of the objects on the standby system.

Specifies that the objects are to be copied to the same location on the standby system as on the primary system. Select this option only if the primary and standby systems have identical file system configurations.

Shows a list of objects on the primary system that can be copied to the standby system. If you have indicated that the standby locations are to be manually entered, you can enter them in the Directory on standby field.

Adds a new row to the table. You will be able to browse the file system to locate the objects that are to be copied to the standby system.

Removes the selected row from the list of objects that can be copied to the standby system.

Type the host name or IP address for the primary database.

Opens a window where you can view the host name details, including the IP address information.

Type the HADR TCP/IP service name on which the local HADR engine dispatchable unit (EDU) accepts connections. If the HADR TCP/IP service name and port number pair are already specified in the TCP/IP services file, you can specify either the service name or the port number. Both entries are required only when the pair is not already in the TCP/IP services file.

Opens a window where you can see the services file details for the host system.

Type the HADR TCP/IP port number on which the local HADR engine dispatchable unit (EDU) accepts connections. If the HADR TCP/IP service name and port number pair are already specified in the TCP/IP services file, you can specify either the service name or the port number. Both entries are required only when the pair is not already in the TCP/IP services file.

Retrieves the port number for the specified service name and populates the port number entry field.

Type the host name or IP address for the standby database.

Opens a window where you can view the standby database name details, including the IP address information.

Type the service name for the standby database. If the HADR service name and port number pair are already specified in the TCP/IP services file, you can specify either the service name or the port number. Both entries are required only when the pair is not already in the TCP/IP services file.

Opens a window where you can see the services file details for the standby system.

Type the port number for the standby database. If the HADR service name and port number pair are already specified in the TCP/IP services file, you can specify either the service name or the port number. Both entries are required only when the pair is not already in the TCP/IP services file.

Retrieves the port number for the specified service name and populates the port number entry field.

Clear to indicate that the primary and standby databases should not be configured for automatic client reroute. When selected, the primary and standby databases will be updated with the specified alternate server information to enable the client reroute feature.

Shows the host name or IP address for the standby database. You can enter a different host name or IP address.

Type the port number for the instance associated with the standby database.

Type the host name for the primary database.

Type the port number associated with the instance for the primary database.

Specifies that synchronous mode is to be used for log writing between the primary and the standby systems. This mode provides the greatest protection against transaction loss and has the longest transaction response time among the three modes.

In this mode the primary system considers log write successful only when logs have been written to its own log files and it has received acknowledgement from the standby system that the logs have also been written to log files on the standby system. The log data is guaranteed to be stored at both sites.

Specifies that near synchronous mode is to be used for log writing between the primary and standby systems. While this mode has a shorter transaction response time than synchronous mode, it provides slightly less protection against transaction loss.

The primary system considers the log write successful when the logs have been written to its own log files and it has received acknowledgement from the standby system that the logs have been written to main memory on the standby system. Loss of data occurs only if both sites fail simultaneously, and the target site has not stored all the log data it has received to nonvolatile storage.

Specifies that asynchronous mode is to be used for log writing between the primary and the standby systems. This mode has the highest chance of transaction loss if the primary system fails. It also has the shortest transaction response time among the three modes.

The primary system considers the log write successful only when the logs have been written to its own log files and have been delivered to the TCP layer of the primary system's host machine. Since the primary system does not wait for acknowledgement from the standby system, transactions may be considered committed when they are still on their way to the standby.

Specify the time, in seconds, that HADR will wait when there is no communication between the primary and standby systems before explicitly dropping any existing connection. The default value is 120 seconds.

Specifies that HADR will start on both the primary and standby systems when you click Finish. Before HADR can be initialized, the HADR configuration parameters are updated as indicated by your selections on the previous pages of the wizard.

Specifies that HADR is not to be started when you click Finish. The HADR configuration parameters will be updated as indicated by your selections on the previous pages and the wizard will be closed.

Click to open the Show Command window.