Backup exec on server 2003.

Tracker · 7 Aug 2009 at 12:00

I have backup exec working on a cluster but it is stating access denied on the cluster address. IE Server 1 and server 2 are clustered and their cluster address is server 3. The backups work on any other server on the network backs up ok. serve 1 and server 2 backup ok but when it comes to user the cluster address of server 3 it fails. Any suggestions will be greatly appreciated.

By the way the servers are Exchange 2003.

Little_Crow · 7 Aug 2009 at 12:14

What version of Backup Exec are you running?
What is the error message you receive?

Tracker · 7 Aug 2009 at 12:33

It is Backup Exec 11d the error message I am getting it

Access is denied to remote agent. Check the login account for the specified device.

iaind · 7 Aug 2009 at 12:44

Why would you back up the cluster address and not the server?

Try disabling strict name checking...

Little_Crow · 7 Aug 2009 at 12:48

The only thing I could find is this from the symantec support forums:

'Please make sure that the Backup Exec Remote Agent for Windows Servers Service is running and is running under the Local System Account on Backup Exec Server Media Server as well as the Remote server (Exchange Server).'

Tracker · 7 Aug 2009 at 12:52

iaind said:
Why would you back up the cluster address and not the server?

Try disabling strict name checking...

I was thinkingthis as the network was not set up by me I am not sure, My guess was if it just backs up the cluster address it will backup either sever which ever one is live be it 1 or 2.

Tracker · 7 Aug 2009 at 12:54

Little_Crow said:
The only thing I could find is this from the symantec support forums:

'Please make sure that the Backup Exec Remote Agent for Windows Servers Service is running and is running under the Local System Account on Backup Exec Server Media Server as well as the Remote server (Exchange Server).'

Both services are running from Local system Account.

Tracker · 7 Aug 2009 at 12:56

Sorry but I should have said this used to all work but after there was a power outage the servers were rebooted and this then sparked off the issue.

iaind · 7 Aug 2009 at 13:40

Either try disabling strict name checking or back them up properly (by specifying one or both of the cluster members)

Tracker · 7 Aug 2009 at 14:20

iaind said:
Either try disabling strict name checking or back them up properly (by specifying one or both of the cluster members)

Sorry for my lack of experiance with this software but how to disable strict name checking.

Little_Crow · 7 Aug 2009 at 14:45

Tracker said:
My guess was if it just backs up the cluster address it will backup either server which ever one is live be it 1 or 2.

That seems sensible to me, it's how our SQL Cluster\file share is setup (backing up using BE10.1), so that a failover will not interrupt the backup.

I've Google-foo'd the following from Symantec support forums again, it looks very much like the wrong thing to do for a network backup job:

Go into the Selection List and manually set the Resource Credentials for every single item to the System Logon Account

I advise ignoring that particular post, but do check your selection lists. There is an option to test the credentials, you may find something is set incorrectly and is causing your issue.