After joining new server backups don't work

  • Thread starter Thread starter Fran
  • Start date Start date
F

Fran

Hi, all. I have a problem I think is related to my ignorance :(

Recently we added an AD server to our LAN. There are no DC's on the
LAN until now (it's just a workgroup with a couple of shared servers
but no domain controllers...until now.) We wanted our department to
have a DC. It's a Windows 2000 server.

When we were stand-alone (workgroup) our backups (Veritas BE 9.0)
worked fine. Now that we share the same subnet (192.168.32.x) I'm
getting all sorts of errors. There is a DHCP server on the LAN (not
our server) so I have all my clients statically assigned addresses and
have set up our AD server as the DNS server for our group. I have run
NetDiag and DCDiag and all checks out OK but I'm getting problems with
our backups (don't know if this is just coincidental or not) and now I
have a bunch of 10010 DCOM errors in the Event log (The server
{ADA33000-3CB4-4309-B1CC-5168A2B672A1} did not register with DCOM
within the required timeout.) Tapes are not popping out as they once
did and I get 7031 errors like "The Backup Exec Server service
terminated unexpectedly. It has done this 1 time(s). The following
corrective action will be taken in 60000 milliseconds: Restart the
service."

I was not getting these when we were stand alone. Do I need to do
something special when I add an AD server to an established LAN
(without a DC)?

I'm lost here :(

-Fran-
 
Try to substitute the local account credentials with a domain account one in
the Backup Exec.
 
I tried local logon accounts and domain login accounts (the backup
program is on this server and I can start the services with the local
or domain login accounts.)

I'm getting uneasy about this now, too. I'm getting these 7031errors
where the Backup Exc service terminates unexpectedly but now I'm also
getting 2020 "out of paged pool memory" errors and the server simply
stops at 4:00 am. If I reboot I'm good for another day but it appears
that I have to reboot every day to keep this problem from happening.

I've tried the options on Microsoft's site about upping the paged pool
memory allocation and changed the swap % from 80 to 40 as instructed
but that hasn't helped.

Any ideas??
 
Back
Top