be 9.0, build 4454 - on Win2k3, can't backup NT admin shares

[SteveJacobs]

I've got a Windows domain, recently upgraded to Win2003 - 2 new servers, running Windows 2k3, Active Directory. Those servers are the domain controllers. The domain has NOT been switched to Win2k3 Native mode, if that matters. Prior to these Win2k3 servers, the domain was NT 4.0; we never implemented a Win2k domain.

One of the new servers has BackupExec 9.0, rev 4454 installed. From that server, I installed the BE Windows Remote Agent on a few of our other servers.

The Windows 2000 member servers backup just fine. However, BackupExec cannot attach to the admin shares on any of the NT 4.0 servers. In the selection list, the admin shares are 'greyed out'.

Initially, I tried adding the DOMAIN\backup account to each of the problem-server's local backup operator groups. WHen that did not solve the problem, I added the account to the local admin groups. Next I tried adding the account to the DOMAIN's Backup Operators group.

Still no luck.

I can select individual shares. If I put the selection list in text mode, I can manually insert selections using admin shares, but the backup job fails when it tries to attach to those shares.

What do I need to do to resolve this?

Thanks,
Steve

 

[NortonES2]

I assume you have put the agent on the NT4 servers.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[SteveJacobs]

Yes. From the Win2k3 Backup server, I installed the Remote Agent on the other servers.

 

[SteveJacobs]

Just an update in case this happens to anybody else...

Originally, I installed BackupExec 9.0 on to the Backup server (running W2k3). From that server, I installed the v9 remote agents on all of the remote servers, both NT and 2k. During the install of the Remote Agents on each server, the setup program would inform me that a previous version of the Remote Agent was found, and would be removed prior to installing the new agent. I would agree to that, and the program installed the new version of the remote agent.

IF, in the selection window of BackupExec I pulled up the properties of the particular servers, they all indicated that the Remote Agent was installed and running. They all displayed it as being version 9, build 4454.

HOWEVER, after spending many hours over several days on the phone with Veritas, the 3rd or 4th guy I spoke with realized that I still had the old version of the Remote Agent on the servers.

So, first I went into Add/Remove Programs and uninstalled the Remote Agent locally on each of the NT boxes. I then copied the RANT32 directory from the Backup Server onto each of the NT servers, and locally ran setupaa.cmd on each of them, to manually install the Remote Agent.

This solved the problem.

-- Steve

 

[Lance466]

I have found that if I share a drive out with the same letter as the drive (e.g. C being shared as C$) then backupexec will not allow you to select it. However, when I change it to another letter (e.g. C being shared as H$) I can then select it in the job setup.

Good luck,

Lance