When using a failover facility, note the following:

• If JP1/Base is linked to manage JP1/Software Distribution users, register JP1/Software Distribution Manager in the same cluster groups as for JP1/Base. For the logical host name of JP1/Software Distribution Manager, specify the same logical host name as for JP1/Base.
• When an application error occurs and an error message is notified from Dr. Watson, failover may fail. You can prevent this by suppressing notification of error messages. For details about how to suppress error message notification, see the OS manual.
  Note that if you suppress error message notification, information acquisition in the event of an application error may be adversely affected.
  
• If an application error occurs when the OS being used is Windows Server 2003, a dialog box reporting the error to Microsoft is displayed. When this dialog box is displayed, failover may fail. You can prevent this by suppressing reporting of errors. For details about how to suppress error reporting, see the OS manual.
• When you stop or start a service, use Cluster Administrator to place the generic-service resource Remote Install Server offline or online. If you stop or start the service by choosing Control Panel, Administrative Tools, and then Services, a failover may occur depending on the resource settings.
• When the generic-service resource Remote Install Server is offline, any change to the registry information may not be applied. Therefore, note the following points:
  

  When installing or uninstalling JP1/Software Distribution Manager (for Embedded RDB)

  You must place the generic-service resources Remote Install Server, HiRDB/ClusterService_JN1, and HiRDB/ClusterService_AM1 offline.^#

  Before you place HiRDB/ClusterService_JN1 offline, execute the netmdb_stop.bat command that is stored in JP1/Software-Distribution-Manager-installation-directory\BIN to terminate the Embedded database. Before you place HiRDB/ClusterService_AM1 offline, execute the jamemb_dbstop.bat command that is stored in JP1/Software-Distribution-installation-directory\jp1asset\exe to terminate the Embedded database.

  Check the message to make sure that each Embedded RDB has terminated.

  #: Required when Asset Information Manager Subset is used.

  Additionally, delete the Registry Copy settings in the generic-service resource Remote Install Server. After installing or uninstalling JP1/Software Distribution Manager, add the settings again according to the description in 11.1.2 Creating an environment that enables failover of JP1/Software Distribution.

  If you perform the installation without deleting those settings, the installed component may not function correctly.

  When installing or uninstalling JP1/Software Distribution Manager (for Microsoft SQL Server or Oracle)

  You must place the generic-service resource Remote Install Server offline. If you start the installer or uninstaller when the generic-service resource is online, a failover may occur or the installer or uninstaller may fail (freeze or terminate abnormally) depending on the resource settings.

  Also, delete the Registry Copy entry for the generic-service resource Remote Install Server. After installing or uninstalling JP1/Software Distribution Manager, add the settings again according to the description in 11.1.2 Creating an environment that enables failover of JP1/Software Distribution. If you perform the installation without deleting that entry, the installation component may not work correctly.

• The registry copy of Cluster Administrator does not support the window size, arrangement pattern, and other display information for the Remote Installation Manager at the execution server. Therefore, the Remote Installation Manager at the standby server does not inherit this information.
• If a failover occurs, the relational database server automatically restores the database. While the relational database server is restoring the database, you cannot connect the database. Therefore, wait a while and then re-connect the database.
• If you have installed only Remote Installation Manager in the cluster system and a failover occurs during execution of Define User Inventory or Define Registry Collection, it may not be possible any longer to execute Define User Inventory or Define Registry Collection from a machine other than the executing server.
  In such a case, perform recovery and then execute Define User Inventory or Define Registry Collection from the executing server. Alternatively, restart JP1/Software Distribution Manager (Remote Install Server service) to which the Remote Installation Manager is connected.
  
• When you set up the system directly below the cluster system, specify the settings in such a manner that the total amount of time required for retries in the event of a communication error (retry interval x retry count) is greater than the time required for failover.
  If the time required for failover is greater than the total amount of time required for retries and failover occurs during job execution (execution status: 20%), the maximum retries may be reached during failover processing, in which case the job may not be restarted after failover.
  
• If you have constructed Asset Information Manager Subset on a failover cluster system in a Windows Server 2003 environment, and if control is passed from the executing system to the standby system due to failover, and then passed again from the standby system back to the executing system due to another failover, you must restart the World Wide Web Publishing Service.