Backup fail on media server after domain change

[Mthales]

Hi,
I have a media server (Windows 2003) which I have installed Veritas 9.1 on. It was working ok until I moved it into a new domain.
In this new domain I used it to push the remote agent out to the workstations on this domain that I wanted to use it to back up - that worked fine. I then ran a backup job and it backed up the workstations fine but failed to back up itself. The error message was number a000846b "Device could not be backed up because an error occurred while connecting to the Remote Agent for Windows Servers."

I looked at the Veritas support website and followed their instructions to change the default port and that did not solve this problem.

I noticed that in the event log there is an error about not being able to create a "secure connection" in the old domain but I'm not sure if that's at all related to this problem.

Can anyone offer any advice on what could be wrong and/or how to fix it?
Thanks


--------------------------------------
Are respectable professionals in considerable peril merely by being in my presence?
---Emma the Mad (or the Well-Beloved)

 

[steveot]

Make sure you can ping the workstation by name and they resolve to correct Ip.

Try backing up or test backup a workstation using user defined selection by IP

enabled restrict anonymous on the workstation.

I suspect and issue with browsing or DNS since you move the server to a new domain.

 

[Mthales]

Thanks for your response but the problem is not with a workstation but with the back up of the media server itself. I can ping it by the name veritas seems to use in the list of backup items.
I also suspect that the issue could be caused by the move to the new domain but I'm not sure where veritas is getting it's details from.

--------------------------------------
Are respectable professionals in considerable peril merely by being in my presence?
---Emma the Mad (or the Well-Beloved)

 

[steveot]

Oh sorry I missed the line about the local backup. Have you created a new job. Here is why I asked. If you have not created an new job the selection list may be looking for oldominame\server..thus unable to find it.

 

[Mthales]

I wish it were that but I've definitely created a new job. In fact I've gotten so stuck with it that I completely uninstalled and reinstalled backup exec and that has made no difference, the job still fails with the same error.

--------------------------------------
Are respectable professionals in considerable peril merely by being in my presence?
---Emma the Mad (or the Well-Beloved)

 

[Mthales]

In my frustration I turned on all the debugging I could find and from the bengine log there seems to be this significant message:

4dc 29/11/2006 14:58:36: Attach to MY_DOMAIN
4dc 29/11/2006 14:58:36: Detach from MY_DOMAIN
110 29/11/2006 14:58:37: NDMP version 3 connection CONNECTED
4dc 29/11/2006 14:58:44: Error 997 opening cluster on \\SERVERNAME
4dc 29/11/2006 14:58:44: Error 0 on NetShareEnum of \\SERVERNAME, level 1
4dc 29/11/2006 14:58:44: NTFS_SurrogateCalling: SERVERNAME
4dc 29/11/2006 14:58:44: Error opening cluster on SERVERNAME: The system could not find the environment option that was entered.
4dc 29/11/2006 14:58:44: Enumerating local drives
4dc 29/11/2006 14:58:44: Creating DLEs:
4dc 29/11/2006 14:58:44: \\SERVERNAME\C:
4dc 29/11/2006 14:58:44: \\SERVERNAME\D:
4dc 29/11/2006 14:58:44: \\SERVERNAME\E:
4dc 29/11/2006 14:58:44: \\SERVERNAME\I:
4dc 29/11/2006 14:58:44: SQL2_SurrogateCalling - the default SQL Service is not running on SERVERNAME.
4dc 29/11/2006 14:58:44: SQL2_SurrogateCalling - Sorry, SQL 2000 Agent not autherized.
4dc 29/11/2006 14:58:44: Device Shadow?Copy?Components Dle platform 2 major version 5 minor version 2 build 3790
4dc 29/11/2006 14:58:44: No utility partitions found on any of the disks
4dc 29/11/2006 14:58:44: Attach to \\SERVERNAME
4dc 29/11/2006 14:58:44: Detach from \\SERVERNAME
110 29/11/2006 14:58:46: NDMP version 3 connection CONNECTED
110 29/11/2006 14:58:47: NDMP version 3 connection CONNECTED
110 29/11/2006 14:59:03: DS_CloseSelectionService
4dc 29/11/2006 14:59:03: DsWorkerThread terminating with exit code 0

The seemly matching error from the beremote log is:

f50 29/11/2006 15:00:55: LogonUser failed: The parameter is incorrect.

But can anyone help me to figure out how to fix this?

--------------------------------------
Are respectable professionals in considerable peril merely by being in my presence?
---Emma the Mad (or the Well-Beloved)

 

[steveot]

When you goto network - logon account the "System logon account" is the default..correct? And the system logon account is the same user and the Backup Exec services are starting as..correct?

This account has Domain Admin right and belongs to the Domain Adming Group and Domain Administrator only. It has the rights to logon locally, act as part of the operating system, create toke object and manage security logs.

I dont see in this debug where it attaches as the user.

Also it sound as if the Backup Exec databse is holding the wrong user name to authenicate locally.

 

[Mthales]

Ahhh good point Steve thanks for pointing that out (and all your thought and help with this problem.)
It's my home time now but I'll check it first thing in the morning and let you know how I get on.

Em

--------------------------------------
Are respectable professionals in considerable peril merely by being in my presence?
---Emma the Mad (or the Well-Beloved)

 

[Mthales]

We finally managed to get it working now so I thought I'd post back in case anyone else is having the same issue.

We checked up the logon accounts and they seemed all OK so as a test we tried a job that only backed up the local machine, and that worked! Then we added in one of the workstations to the backup and it failed in the way same way as previously described. So we set about an un-install and re-istall of the remote agent on that workstation and then tried backing it up in the way that had just failed and that worked. (This needed repeating for all the workstations.) So it seems to me like this error message was caused by some confusion between the workstations and the media server. But even if I'm wrong about that we now are backing up and much happier.

Thanks very much for your help with this
Emma

--------------------------------------
Are respectable professionals in considerable peril merely by being in my presence?
---Emma the Mad (or the Well-Beloved)