ANS1676W
You are doing an authoritative cluster database restore. The process may seem to be hang before and after the file is restored. This is because it may need to start the cluster service if it is not up and take all the resources offline. After the cluster database is restored, the cluster service will be restarted for changes to be in effect. The cluster service on all other nodes also have been shutdown. They will be restarted. This may take a few minutes.

Explanation

The restore will seem to be paused at time because before the restore, Tivoli® Storage Manager ensures the cluster service is up on the restoring node and all the resources are taken offline. After the cluster database is restored, the cluster service on the restoring node is in a paused state. The cluster service on other nodes were shutdown. All services need to be retarted. If some of the services cannot be started automatically, you can try to restart them.

System action

Processing continues.

User response

No action.