AXISHK
asked on
Login Credential for Backup Exec 2012
Any idea why the BACKUPEXEC database can't be pass the login credential, even though I have granted the domain admin right ?
Is it possible to fix the error ? How can I include the Backup Exec Catalog in my daily Exchange Backup ?
Tks
Is it possible to fix the error ? How can I include the Backup Exec Catalog in my daily Exchange Backup ?
Tks
ASKER
What do you mean "DA access" ?
Tks
Tks
domain admin...accessing some of the new features on BE 2012 don't like non-DA accounts.
ASKER
Still have the problem.
I use BackupExec 2012 to backup the Exchange 2010 server. This is a new installation.
Inaddition, how to include catalog in my backup ?
I use BackupExec 2012 to backup the Exchange 2010 server. This is a new installation.
Inaddition, how to include catalog in my backup ?
usually with the backup job being successfully completed the catalogue is automatically generated and stored for XX number of days depending on your settings, usually 30 days.
under your Server backup job -- Backup & Restore -->Server name-->Credentials, under Microsoft Info Store/First Storage Group, what error do you received when it fails?? Is it E000FF21?
You may need to edit user rights assignment policy on the server to allow your BE account to 'act as the operating system' (use GPedit.msc to edit the local computer policy --> Comp Config/Windows Settings/Security Settings/Local Policies/User Rights Assign). Or you could set a GPO for the server in roughly the same path structure.
See if this Symantec doc helps with Exchange creds -- http://www.symantec.com/business/support/index?page=content&id=TECH184449
under your Server backup job -- Backup & Restore -->Server name-->Credentials, under Microsoft Info Store/First Storage Group, what error do you received when it fails?? Is it E000FF21?
You may need to edit user rights assignment policy on the server to allow your BE account to 'act as the operating system' (use GPedit.msc to edit the local computer policy --> Comp Config/Windows Settings/Security Settings/Local Policies/User Rights Assign). Or you could set a GPO for the server in roughly the same path structure.
See if this Symantec doc helps with Exchange creds -- http://www.symantec.com/business/support/index?page=content&id=TECH184449
ASKER
"under your Server backup job -- Backup & Restore -->Server name-->Credentials, under Microsoft Info Store/First Storage Group"
Can you dump your screen to show where I can find this setting... sorry for that ?
Tks
Can you dump your screen to show where I can find this setting... sorry for that ?
Tks
good idea to install the BE Console on your own desktop, saves having to RDP into the backup server all the time, you can do everything from the console.
does this help? I can check with my sys admin in the morning to see what else we had to do, but i do know that it was a faff to get working and we have an older Exchange server, not looking forward to Exch 2013 upgrade, as BE isn't listed as certified yet!!
I.
ASKER
Tks .. still encounter issue after following your recommendation.
Actually, only few of them fail the credential authentication..
EX01DB1 & EX02DB1 doesn't exist in Information Group.
MS MSQL Server Instance ... I believe this is the database used by Backup Exec and I suppose we should it in case of disaster recovery...
KAV & KAV-EX01, not idea but we don't use it..
As this is setup by my previous colleague and I have just followed up recently. So, I don't have too much information on hand.
Two more things to check :
"8. Make sure the default system logon account of Backup Exec and Backup Exec Service Account are the same." --> How to confirm this ?
"From Backup Exec console Click Network -> Logon Account, ensure that a System Logon Account is present. If not create a System Logon Account by clicking the System Account button." --> where can I find this option under BackupExec 2012 ?
Any further advise is appreciated... Tks
BackupExec-2012.png
Actually, only few of them fail the credential authentication..
EX01DB1 & EX02DB1 doesn't exist in Information Group.
MS MSQL Server Instance ... I believe this is the database used by Backup Exec and I suppose we should it in case of disaster recovery...
KAV & KAV-EX01, not idea but we don't use it..
As this is setup by my previous colleague and I have just followed up recently. So, I don't have too much information on hand.
Two more things to check :
"8. Make sure the default system logon account of Backup Exec and Backup Exec Service Account are the same." --> How to confirm this ?
"From Backup Exec console Click Network -> Logon Account, ensure that a System Logon Account is present. If not create a System Logon Account by clicking the System Account button." --> where can I find this option under BackupExec 2012 ?
Any further advise is appreciated... Tks
BackupExec-2012.png
KAV could be Kaspersky AntiVirus, but not sure, you would need to check the server.
"8. Make sure the default system logon account of Backup Exec and Backup Exec Service Account are the same." --> How to confirm this ?
i think this is checking on the BE server that the services running are using the SAME login account, and not two different accounts.
"From Backup Exec console Click Network -> Logon Account, ensure that a System Logon Account is present. If not create a System Logon Account by clicking the System Account button."
this will be your main account settings in BE, in the options menu for the application, where you would the primary service account/login.
"8. Make sure the default system logon account of Backup Exec and Backup Exec Service Account are the same." --> How to confirm this ?
i think this is checking on the BE server that the services running are using the SAME login account, and not two different accounts.
"From Backup Exec console Click Network -> Logon Account, ensure that a System Logon Account is present. If not create a System Logon Account by clicking the System Account button."
this will be your main account settings in BE, in the options menu for the application, where you would the primary service account/login.
ASKER
Based on last attached file, just wonder whether it is possible to
- remove EX01DB1, EX02DB1 (under MS Information Store), KAV & KAV-EX01 (under MS SQL Server). The former is in fact does not exist in MS Information Store.
- how to backup the BKUPEXEC where BackupExec catalog file is installed.
Tks
- remove EX01DB1, EX02DB1 (under MS Information Store), KAV & KAV-EX01 (under MS SQL Server). The former is in fact does not exist in MS Information Store.
- how to backup the BKUPEXEC where BackupExec catalog file is installed.
Tks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tks
your backupexec account needs to be a member of Backup Operators, Exchange Services as well as DA access. Our issue was the 2 legacy VM servers we have and can't upgrade from Win 2000 Server, you need to leave the older agent service installed, do not try and add v14.0 (2012) agent. also a good idea to run Live Update and make sure the BE app is fully patched as you then need to push the agent updates out to the servers again.