Unsolved

This post is more than 5 years old

35 Posts

594

March 5th, 2009 02:00

Backups fail with a change in the domain controller and DNS server

Hi all,

We have the following environment:

Domain Controller(BEFORE) - Windows NT 4.0
Domain Controller (AFTER): - Windows 2k3

NetWorker Server:
'cifmalava2' - 'cifmalava2.cofares.es'
W2k3
NW 7.3.3


Last weekend all backups began to fail with errors.
The change affects these problems is the update on the Domain Controller and DNS server.
which was migrated from NT4 to W2K3 Server. The full name domain was not changed ".cofares.es"


Before the change of the DNS server from the console the NetWorker Server "client" showed like 'cifmalava2', but now appears as 'cifmalava2.cofares.es'.

We believe that Client ID of NetWorker Server has changed.

One of the troubleshooting we have followed is to aplly the method of "Changing domain or name of the NetWorker Server"


1.- Copy "nsr" directory to a safe location.

2.- Change NetWorker Server name for a temporary.

Ex:
From Original_name 'cifmalava2' to Temporary_name 'cifmalava2tmp'

3.- Change the status of the NetWorker services from automatic to manual:

- EMC GST
- NetWorker Backup and Recover server.
- NetWorker Remote Exec service

4.- Stop NetWorker services.

5.- Rename current folder index of NetWorker Server "Current_Path_NetWorker\nsr\index\cifmalava2.cofares.es" for "Current_Path_NetWorker\nsr\index\cifmalava2.cofares.es.old"

6.- Copy the old folder index "nsr\index\cifmalava2" to "Current_Path_NetWorker\nsr\index"

After rename the path "Current_Path_NetWorker\nsr\index\cifmalava2" to "Current_Path_NetWorker\nsr\index\cifmalava2.cofares.es"

7.- Reboot NetWorker Server

8.- Start NetWorker services.

9.- From NetWorker Mangament console - Configure - Clients

- Delete all instances of the Client (NetWorker Server).

10.- Stop NetWorker services.

11.- Change NetWorker Server name by its Original name.

Ex:
From Temporary_name 'cifmalava2tmp' to Original_name 'cifmalava2'

12.- Reboot NetWorker Server.

13.- Start NetWorker services.

14.- Run the following command "savegrp -O group_name"


- But only the indexes and bootstrap of NetWorker Server work well. The rest fail.
- Backups of data (Ex. with C:\, SYSTEM save sets, etc, ...) also fail.

Do you have any idea about a similar situation?

Thanks,
regards,

EER

443 Posts

March 5th, 2009 20:00

A couple of questions here. I am presuming that the backups from the clients are not working while backups of the NW server itself are working, is that correct? What is the error you get in the logs when the backups fail? I suspect that for some reason (probably the change in domain controller) has caused the client id for all the clients to change.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

March 6th, 2009 13:00

Usually you do not have put machine into domain (as backup server is dedicated) so you can skip domain issue. If I understand correctly, you claim that server changed name from shortname to FQDN - are you sure about that? Unless there is need to have machine in domain, put it out and bring old resources back.

35 Posts

March 12th, 2009 13:00

Thanks for your collaboration Mr Crvelin & Mr Raman.

Finally, we reinstalled the jukebox, and the backups have started to work fine.

This was a test that was pending after the migration of the Domain Controller.

Thanks again,
Regards,

EER

0 events found

No Events found!

Top