cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to backup 2008 R2 server - Logon Account Selection prompt

Mark_McFarlane
Level 4

Using BackupExec 12.5 with the necessary patches - successfully installed BackupExec agent on 2008 R2 server.

When I try to add selections from the 2008 R2 server to my backup job, I get the "Logon Account Selection" window coming up stating "Access is denied" and asking me to select  a logon account.  I only use one logon account for all BackupExec -- its a member of the domain admin group and works on all other servers/services except this one. 

I have tried to create a new ID, but that doesnt work either...

Strange thing is, when I turn off the BackupExec service on my 2008 R2 server, I am able to select shared directories for backing up -- I dont see the C$ or other admin shares though...with the service running, I dont see anything...

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_McFarlane
Level 4
 Finally fixed it!

I needed to give the Backup Exec Services account "Log on as Batch job" security to the Domain Controllers security policy....did a gpupdate on the server then restarted the Backup Exec Agent service and it now works....

Here's the link to the solution:

http://seer.entsupport.symantec.com/docs/316787.htm

I found the answer by looking through this list of issues/patches which was very helpful:

http://seer.entsupport.symantec.com/docs/BEWNT_digest.htm



View solution in original post

9 REPLIES 9

Dev_T
Level 6
Hello,

Is the W2008R2 machine a DC or a member server? If its a member server, add the BE account in the Local Admin Group on the W2008R2.

Mark_McFarlane
Level 4
Its a new DC

CraigV
Moderator
Moderator
Partner    VIP    Accredited
Hi Mark,

Check here...

ftp://exftpp.symantec.com/pub/support/products/Backup_Exec_for_WindowsNT/307063.pdf

That's the Software Compatibility List for BEWS 12.5. At no stage does it state that it's supported as a full media installation. However, it does support a Remote Agent for Windows Servers installation, so you can back it up via the RAWS agent.

So although it works in part, you've got some compatibility issues here which make it look like it MIGHT work, when it doesn't.
My suggestion would be to uninstall the full version and install the RAWS agent if you have another media server. Use that to backup your 2008 R2 DC.

Laters!

Mark_McFarlane
Level 4
I only have the agent installed on the 2008 R2 server -- the media server is a 2003 server.

CraigV
Moderator
Moderator
Partner    VIP    Accredited
Mmm...OK, so then the comment about adding it to the local admins group is moot.

Load up SP3 if you haven't already, and then push the RAWS agent out to the server. This will contain numerous patches if need be.

http://seer.entsupport.symantec.com/docs/337966.htm - Release notes

http://seer.entsupport.symantec.com/docs/337407.htm - 32-bit download

http://seer.entsupport.symantec.com/docs/337408.htm - 64-bit download

http://seer.entsupport.symantec.com/docs/337537.htm - Drivers

Laters!

Mark_McFarlane
Level 4
Keep the suggestions coming!

I have already done the SP3 patches on my media server - after that, I did a local install of the RAWS on the 2008 R2 server -- that all seemed to work fine...

CraigV
Moderator
Moderator
Partner    VIP    Accredited
OK...then I am going to suggest pushing the RAWS agent out again...maybe it missed possible updates for some reason.

Mark_McFarlane
Level 4
I will uninstall the RAWS from the 2008 R2 server and do a reinstall (I have done this at least 5 time already - but Im game to try it again!!)

I have been doing the "copy RAWSX64 and MSXML folders to the 2008 R2 server and do a manual install" installation method since doing a push install doesnt work...do you have a different way of trying to install the RAWS or is that the best way?

Mark_McFarlane
Level 4
 Finally fixed it!

I needed to give the Backup Exec Services account "Log on as Batch job" security to the Domain Controllers security policy....did a gpupdate on the server then restarted the Backup Exec Agent service and it now works....

Here's the link to the solution:

http://seer.entsupport.symantec.com/docs/316787.htm

I found the answer by looking through this list of issues/patches which was very helpful:

http://seer.entsupport.symantec.com/docs/BEWNT_digest.htm