cancel
Showing results for 
Search instead for 
Did you mean: 

Enterprise Vault Partitions invisible Backup Exec 2010

rendersr
Level 5
Partner Accredited

Hi All,

I already encountered two times that my Enterprise Vault data becomes invisible when no configuration settings has been changed.

The jobs fail with the following error: "e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent."

Updating and reinstalling the agent are no solution. When checking the Backup Exec Agent on the EV server, we notice that the partitions are correctly published.

Reason: unknown bug in the trust relationship (certificates)

Solution: remove the trust relationship between the clients and the Backup Exec server.

Remark: performing this procedure will cause that all clients will need to be trusted again by the Backup Exec server.

How:

  1. Stop the Backup Exec services on the affected clients as wel as on the Backup Exec server.
  2. Login on the EV server and go to the installation directory of the Backup Exec agent. Afterwards navigate to RAWS\Data
  3. Delete or move the *.crt and *.key files.
  4. Login on the Backup Exec server and navigate to the installation directory. Then go to the data folder.
  5. Perform a search on *.crt and *.key files. Delete or move those files from the directory.
  6. Start the agent service again on the client(s).
  7. Start the Backup Exec services on the server.
  8. In the Backup Exec GUI, create a new selection list. In the selection list navigate to the clients.
  9. When clicking on a client a popup will appear "Remote agent not trusted".
  10. Click yes to trust the agent again.
  11. Perform steps 9 and 10 for all clients managed by this Backup Exec server.
  12. Check if the partitions are now visible again.

Good luck!

2 REPLIES 2

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Are you using a fully patched version of backup Exec 20120 R3 as issues with the trust relationships were (in theory) fixed by the later updates.

rendersr
Level 5
Partner Accredited

Encountered it yesterday on an environment with R3 installed. Not all latest patches were installed however.