Hi everyone, The previous network administrator of a customer of us has run backup exec with the admin account. I like a nice structure on a server so I want to change this to a service account for backup exec. The company is using a SBS 2011 so I added a new administrator to the domain. I have also followed this guide on symantec, but still with the service account it isn't functioning: http://www.symantec.com/business/support/index?page=content&id=TECH136148 When I want to start a backup, the error is shown "Ready, No media servers available". Also when I run backup exec under the new service account, all of my backup-to-disk-folders are offline and it takes a couple of minutes for the first folder to go online. When I want to backup to this folder, also the same error. When I use the admin-account (which is working) all of my folders go instantly online. Guess that there lies the problem, but I am not certain. Thanks for your help already!!

Upgrading to R3 is a separate problem from having the right BE account. I would suggest that you sort out your account problem before you upgrade.

What account is being used for the BE services? Open services.msc and check the account used for BE Device and Media service BE Server service BE Job Engine

When you change the BESA, did you use BEUtility to make the change? This would ensure that the change is effected in all the correct places. BEUtility can be found in the BE installation directory.

Yes I did this, but still nothing.. I have set the user back to admin, but now every job runs with the status "Job Status". I am thinking about upgrading to the R3 version of Backup Exec 2010 and do a full installation again of Backup Exec. I am using SBS 2011. Can I run this under another account than our "admin" account? The account "administrator" is appareantly disabled so we always use the "admin" account. Do I need to be logged in to this account when I want to install Backup Exec? And how can I export my configuration that I have now in the R2 version?

All of the services are running under this user "admin" which gives me problems now. also the credentials are right.

Problem with the queued is already fixed. Backuping up to the NAS wasn't working but to USB drive was working. I rebooted the NAS and it is working again. Can I use a serperate backup exec user account on a SBS2011? Do I need to be logged into this account when I install the backupsoftware? I just read through this article (http://www.symantec.com/business/support/index?page=content&id=TECH37072) to copy the configuration. I don't want to copy the logon information, just the selectionlists and, just lists and device media. Thanks in advance!!!!

Backup Exec logon account not working

13 Replies

AmolB
Moderator
13 years ago
What account is being used for the BE services? Open services.msc and check the account used for

BE Device and Media service

BE Server service

BE Job Engine
pkh
Moderator
13 years ago
When you change the BESA, did you use BEUtility to make the change? This would ensure that the change is effected in all the correct places. BEUtility can be found in the BE installation directory.
Silencer01
Level 4
13 years ago
Yes I did this, but still nothing.. I have set the user back to admin, but now every job runs with the status "Job Status".

I am thinking about upgrading to the R3 version of Backup Exec 2010 and do a full installation again of Backup Exec.

I am using SBS 2011. Can I run this under another account than our "admin" account? The account "administrator" is appareantly disabled so we always use the "admin" account. Do I need to be logged in to this account when I want to install Backup Exec?

And how can I export my configuration that I have now in the R2 version?
Silencer01
Level 4
13 years ago
All of the services are running under this user "admin" which gives me problems now. also the credentials are right.
Silencer01
Level 4
13 years ago
Problem with the queued is already fixed. Backuping up to the NAS wasn't working but to USB drive was working. I rebooted the NAS and it is working again.

Can I use a serperate backup exec user account on a SBS2011? Do I need to be logged into this account when I install the backupsoftware?

I just read through this article (http://www.symantec.com/business/support/index?page=content&id=TECH37072) to copy the configuration. I don't want to copy the logon information, just the selectionlists and, just lists and device media.

Thanks in advance!!!!
CraigV
Moderator
13 years ago
...you can change the BESA to an account with domain admin rights at a minimum through BEutility. Then verify in services.msc that the change has been effected...admin might not be a unique-enough name for BE...
Silencer01
Level 4
13 years ago
I have everything running at this moment with the admin account. I still would like to use a seperate user.

Can you verify that this is possible while working with a SBS 2011? Thanks in advance!!

Kind regards,

Sven
Ken_Putnam
Level 6
13 years ago
Certainly you can use a dedicated account in SBS (or any other supported media server OS)

http://www.symantec.com/docs/TECH23689

What rights does the Backup Exec service account need?
Silencer01
Level 4
13 years ago
Thansk for the comment Ken! I have already seen this link, but the website states:

Note: Due to security implementations in Microsoft Small Business Server, the service account must be Administrator.

I am using the user "admin" for my domain, because the previous network administrator disabled the default "administrator" account. Does it mean that only "admin" would work or that the role "administrator" needs to be assigned?

Thanks!!
CraigV
Moderator
13 years ago
...at a bare minimum, the account must be a member of the Domain Admins group. When you start looking at applications like Exchange to back up, then other roles are required.

If you want to use another account, simply do the following:

1. Create a new user account and call it anything, eg. backupexec.

2. Make it a member of the Domain Admins group.

3. Use BEutility.exe to change the service account to the new 1 created.

4. Make sure the services start up, and then look at adding roles in order to backup Exchange/SQL etc...