Avatar of maderitetech
maderitetech
 asked on

Backup Exec 2012 annot backup Exchange Database - No Healthy Copy

I'm having a problem with Backup Exec running a backup on the Exchange database like it used to just a few days before. The error I'm getting when I edit the job, and then edit the selection list and drill down the MS Information Store to my Exchange database and the 'Mailbox Database (#)' is:

Browse Failure

Failure to browse 'Mailbox Database (#)'

Backup Exec could not back up the Exchange database because it could not find a healthy copy of the database. If I click on View additional information, I get a long string which I can't copy and paste that begins "QueryMetaData: MDQ_Backup..."

I think I have a problem with the System Logon Account. Here's why.

Weeks ago the backup was running fine. Once SP1a was downloaded and the system rebooted, I started getting errors about not being able to backup stuff that worked fine before. I found an answer to that problem at this website - the logon data in Backup Exec was corrupt. I deleted the logon data and created a new System Logon Account. It wasn't the default one I had before for the local host, but it seemed like everything was fine. Then BE2012 wouldn't backup the BKUPEXEC instance of SQL 2005 runtime DB on a disaster recovery backup. Tech support helped me to setup a new System Logon Account using the Active Directory domain\name settings.

That seemed to work fine for a day. Then the problem I have now showed up - BE thinks my Exchange DB is not healthy. But Exchange is working fine.

I think if I could get back to whatever the original System Logon Account was, using the local machine, not any AD info, everything would work fine. Or maybe a new SLA would work. I don't know.

Does anybody have any answers?

BTW, I've already read and tried a few of Symantec's articles. No help.

Using Backup Exec 2012 on Windows 2008 Server R2 Standard
ExchangeStorage Software

Avatar of undefined
Last Comment
maderitetech

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
prashant9885

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Rodney Barnhardt

I know you said you tried a number of things. Prashant9885 mentioned uninstalling and reinstalling the agent. That has showed up on a search, but the user could not uninstall due to permission errors. Did this by chance happen after a recent Windows update? I had an issue and had to redo somethings after my Exchange server was patched in June.

http://www.symantec.com/connect/forums/backup-exec-2010-and-exchange-2010-error

Have you tested your credentials:
http://www.symantec.com/business/support/index?page=content&id=TECH125261

Here is another potential solutions that deals around shadow copies:
https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27091494.html
maderitetech

ASKER
Thanks for the input. To answer the questions: Exchange 2010 and it is on the same server as BE2012. I don't allow automatic Windows updates and haven't done any in days.

I looked at Event Viewer and discovered quite a few errors (Event IDs 2601, 2501, 2604, 2104, and 2122) all related to MSExchange ADAccess. (There were other Exchange warnings as well.) We have a consultant in the process of changing our domain controllers, so maybe that is related. I've contacted him for his input.

The Event ID 57808, Backup Exec also says, "The Backup Exec Remote Agent for Windows Systems service must run under the Local System account, but it is not currently configured for this account. You must change the user account name for the Backup Exec Remote Agent for Windows Systems service to the Local System account, and then restart the service. "

I think this is at least part of the problem. I don't have that account anymore. I deleted it because it was corrupted. How do I recreate the Local System account for which it was originally configured?
Rodney Barnhardt

The "Local System Account" has been deleted. That is not supposed to be possible. It is considered a "built-in" account. Per Microsoft  "The reason you can't delete built-in accounts is that you wouldn't be able to re-create them. The SIDs of the old and new accounts wouldn't match, and the permissions and privileges of these accounts would be lost. Because of this, Windows NT doesn't let you delete built-in accounts"
Your help has saved me hundreds of hours of internet surfing.
fblack61
SOLUTION
Hypercat (Deb)

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
maderitetech

ASKER
Okay, I'm getting a little confused here. As I understand it, BE's local system account doesn't have anything to do with the AD. I base that off of the following copied from BE's manual.

"Backup Exec logon accounts are not user accounts. When you create a Backup
Exec logon account, an entry for the account is entered into the Backup Exec
database; no operating system accounts are created. If your user account
credentials change, you must update the Backup Exec logon account with the new
information. Backup Exec does not maintain a connection with the user account."

I think what I'm saying is that the BE's local system account was deleted - not anything having to do with MS.

I'm going to close this for now and wait to see what happens then the consultant finishes moving the domain server this weekend. If I still have a logon problem with BE I'll contact Symantec.

KUDOS

@prashant9885 for suggesting looking at the Event Viewer

@hypercat for suggesting it could be due to the consultant switching domain servers.
Hypercat (Deb)

The key portion here is:

"If your user account credentials change, you must update the Backup Exec logon account with the new information. Backup Exec does not maintain a connection with the user account."  

So, if the password was changed for the AD user account you used when creating your BE system logon account, then you have to edit the BE system logon account and change the password there as well.

I just wanted to be sure that you understood that connection.
maderitetech

ASKER
Thank you. I understand, but nothing has changed with the AD user account.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.