Video Screencast Help

store dismounted after changes made to default domain policy

Created: 23 Aug 2012 | 1 comment
My client is backing up exchange 2010 using BE2010R3 sp2. 
The current setup is DAG setup and it has 3 CAS/HUB roles and 4 mailbox role servers and all 7 servers has remote agents up to date
The backup was failing with this error 
"V-79-57344-913 - Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again."
found some troubleshooting step online and it mentioned that we should do this which is mentioned below.
Create a new account.
Ensure that the account is visible in the GAL and can send and receive mail.
Ensure that the account is activated and send/receive emails.
Ensure that the Backup Exec logon account is a member of the "Organization Management" Role Group in Exchange 2010.
Ensure that the Backup Exec logon account is a member of the Domain Admins group.
Ensure that the Backup Exec logon account being used to access the Exchange server is part of the Local Administrators group on the Exchange 2010 server.
Make that account the System Logon Account and ensure that the Backup Exec services are using that account.
In addition the Backup Exec service account requires the following rights:
  1) Backup Files and Directories
  2) Restore Files and Directories
  3) Create a Token Object
  4) Manage Auditing and Security Log
  5) Take ownership of files and other objects
  6) Act a part of the operating system
We did this on one of our DC and gave these rights from default domain policy which were on the status called NOT DEFINED. After that our exchange database dismounted and unable to mount. 
We reverted back to the NOT DEFINED status those 6 policy objects and then our databases started fine able to mount them. 
Can anyone tell what can be other side effects of assigning those 6 policy objects in a default domain policy. 
Any help will be appreciated 
Thank you for reading my post.

Comments 1 CommentJump to latest comment

AshwinApte's picture


As long as your Exchange services are not running under the Backup Exec Service account, none of the  steps you did should have any effect on your exchange databases.

The exchange database may have been dismounted due to some other reason (event viewer entries may give an idea of the reason), also your Backup Exec job failure could also be because the Exchange database is getting dismounted due to some reason.

Check the event viewer for the Exchange related failures and try creating a new Backup job for Exchange and check if you are able to run that job.