Video Screencast Help

Browse failure when trying to create backup for exchange 2010 dag

Created: 09 Oct 2012 • Updated: 10 Oct 2012 | 2 comments
This issue has been solved. See solution.

We recently upgraded our mail servers to 2010 and I am trying to set up a backup. I go in to add server and add the dag and that seems to go ok. exchdag is now added to the server list. Unfortunately when ever I try to create the backup I get an error:

Browse Failure 

Failure to browse 'exchdag'.

The directory of file was not found, or could not be accessed.

QueryMetaData: MDQ_MachineInfo_View




Since that didn't seem to work I figured I would just go directly to the cas servers and try to do the backup of the information store that way. 

Those jobs failed with the error: Backup Exec could not log on to the server with the logon account specified for it. The logon account does not have valid credentials. Ensure that the user name and password are correct in the logon account. 

The issue here is that the credential test passes and the beservice account has Organization Management rights with Exchange.

Exchange 2010 is installed on 4 servers. 2 cas/hub servers and 2 mbx servers all installed on 2008r2 datacenter both exchange and os are patched up to date and be is current.

Comments 2 CommentsJump to latest comment

Backup_Exec's picture


Please ensure BE 2012 is fully patched up with sp1a and 3 updates after it & remote agent should be installed on all the 4 nodes of DAG and should be on same level as remote agent on media server

Please check the link below for browse failed issue with DAG

Moreover please ensure you go through below link to ensure it as per requirement

Account used for doing backup of exchange should be part of Organization management group and exchange server group

Hope that helps



Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

dfeifer's picture

Thank you for your post. It was actually two issues. The first being that the document that I was looking at here does not say anything about adding the beservice account to the exchange server group. 

The dag issue pertained to the failover cluster as you had listed in the first thing to check. We set up the dag through exchange and everything apeared to work. Suposedly dags only use a subset of failover clustering so we never even thought to look at the failover cluster manager. The issue there was that the install defaulted to using dhcp on the virtual machine network where we have none. assigned an ip and got that squared away. 

Again, thank you for your help!