Information shown in the "Tasks" section of the Admin console is purely a "paperwork" type thing. It has no effect on the recovered client. The "Finalizing" status is set after the client has completed the recovery actions on the client, using the SRT, and just before the client is automatically rebooted.
On reboot, the "bmrcleanup" process should have automatically been initiated on the client itself. For Unix/Linux, is is part of the actual boot process, fairly late in that and before the initial login. For Windows clients, the cleanup process is initiated as part of a registry entry to run automatically after the login is performed. Due to required system interactions, it requires a local login ID with local administrator authority. Because the cleanup process does some final work in setting up the networking, domain credentials will not work.
The status gets changed from "Finalizing" to "Complete" as part of the bmrcleanup process. This is in fact the very last action of the process on the client and involves a simple IP message to the BMR Master to update the task status. Nothing more, nothing less. Because bmrcleanup is a one time action, if the update of the task somehow fails (typically due to a networking issue) you may see an error panel on the client to that effect and the rather ominous message of error, with a rc=200. It is not an error that affects the client.
Please see this TECH article that explains this:
During Bare Metal Restore (BMR) Final Cleanup, the error message "Unable to update client state on the Netbackup server, error =200" is displayed.
http://www.symantec.com/docs/TECH73586
Assuming this is a Windows recovery, did you see the "bmrcleanup" process kick off after logging in? If it did run, did it show the rc=200 error message? If "bmrcleanup" did not run automatically, you need to manually fire it up. One clear indication of this is the presence of the C:\BMR folder on the client. This is a temporary folder that BMR creates and uses as part of the recovery process. The cleanup process deletes this from the client and it needs to be gone from the client as it will be backed up by any subsequent backups taken (FULL or INCR). This can cause problems later on if the client is again recovered using BMR.. This is a special junction mount point, so normal folder deletion actions are not going to work. As the registry "Run" key is still in place, any reboot/login actions should fire it up normally. However, you can manually run this using the command (from command line) of '..\netbackup\bin\bmrcleanup -force'.
If the cleanup has already been done and you want to handle the task setting, you then have two options.
1. From the Admin Console, right click on the task and do a "Cleanup" and "Delete". action. This removes the task from the console.
2. From a command line run the command:
..\netbackup\bin\bmrs -op complete -resource restoretask -client <client_name> -status 0
The command should set the task to Complete with rc=0.
Again, unless the 'bmrcleanup' process did not run or somehow failed while running, this is a benign situation with no side effects to the recovered client. Actions taken to clear it up in the Tasks section of the BMR node on the Admin Console have no effect on the recovered client.
Please reply with results of the recommended actions or if you have need for additional clarification of the matter.
