18.8 Actions to be taken after a failover
The table below shows what actions to take when a failover occurs during cluster system operation. Choose the actions that correspond to the processing that was in progress when the failover occurred.
Processing in progress |
Actions to take after 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 resource 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:
|
- Important
-
When a failover occurs during a cluster system operation, the status and result of an import are not displayed in the following windows. In this case, import items again.
-
Home - Background Task
-
Settings - Assets - Last Import Log
-