Hello,
If the volumes you want to protect are indeed protected, yet Backup Exec System Recovery (BESR) still reports the system as "At Risk", it usually means that at some level, BESR believes an unprotected volume still exists in the system.
Please try the following:
Check Status Of Each Volume On Client
It's likely you have already done this, but I figured I'd mention it anyway. On the "Computers" tab of the "Manage" page in the BESR Manager console, click the "At Risk" link on the appropriate client. When the status details page appears, click on the "Drive Status" button. If any drives show up as not being protected, you can assign the client additional backup jobs to cover those volumes. If the additional volumes do not need backup job protection, optionally you can select each volume that is showing up as at risk and click the "Status Reporting" button. Instead of "Full status reporting" you can select "Errors only" or "No status reporting". Any of the latter two options will prevent that volume from affecting the overall status reporting of the client.
Check For "Phantom" Volumes
Sometimes, especially in cases when a system has its drive replaced, the BESR client will "remember" the old drive. Completely uninstalling BESR from the client would likely clear up this problem. Here are some additional options:
1. At the client system itself, open the BESR console. On the "Advanced" tab, check for any volumes marked with a "?". Right-click and remove these volumes. This should prevent these volumes from affecting the overall status of the system.
2. At the client system itself, stop the BESR service. Delete all files in "C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec System Recovery\Logs" and then restart the BESR service.
Note: Option 2 is the equivalent of "wiping the memory" of the BESR client. It will no longer know anything about previously run backups (although backup jobs assigned to the client will remain).
Thanks.
