18.8 Actions to be taken after a failover

Referring to an operation window

After a communications error message or a database access error message appears, log out, and then log in again.

Registering a package

After a communications error message or a database access error message appears, log out, and then log in again.

If registration of the package did not complete, register the package again.

Performing an import (for example, of asset information)

After a communications error message or a database access error message appears, log out, log in again, and then perform the import again.

Performing an export (for example, of asset information)

After a communications error message or a database access error message appears, log out, log in again, and then perform the export again.

Running the database manager

Execute the process that was in progress again.

Running setup

Move the owner of the cluster group back to the node that it was on before the failover occurred, and then run setup again.

Registering components

Register the component again.

Registering USB devices

Register the USB device again.

Executing commands

Execute the command again.

Depending on the command that you were executing, also perform the following actions:

• ioutils exportasset (to export hardware asset information)

  Delete the exported file.

• ioutils exportfield (to export custom-field settings)

  Delete the exported file.

• ioutils exporttemplate (to export templates)

  Delete the exported file.

• ioutils exportpolicy (to export security-policy settings)

  Delete the exported file.

• ioutils exportupdategroup (to export security-update settings)

  Delete the exported file.

• ioutils exportoplog (to export operation logs)

  Delete the exported file.

• ioutils exportfilter (to export filter settings)

  Delete the exported file.

• exportdb (to obtain a backup)

  Delete the backup destination folder.

• getlogs (to obtain troubleshooting information from the management server)

  Do not delete the folder in which the troubleshooting information is stored. This information might be necessary if you contact Customer Support.

• getinstlogs (to obtain troubleshooting information collected during installation)

  Do not delete the folder in which the troubleshooting information is stored. The information might be necessary if you contact Customer Support.