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

[EhoS]

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,

 

[605]

I don't understand. If you only changed the hostname to a FQDN nothing really changed. It should be just sufficient to add the FQDN to the client's "Alias" field. Usually, NW would add both names automatically when you specify the client with its FQDN.

The client ID will not change to the best of my knowledge.

 

[EhoS]

Hi 605, thank you for your collaboration. But we believe that the migration of the operating system Domain Controller server (From NT4.0 to W2K3) could cause the problem with fails in the backup.

- We are verifying the hosts resolution

We are checking the resolution for hosts although we think it is correct.

We include the error messages during the test backup. When we have the logs available. This will help to better understand the problem.


If you have more ideas that can help will be welcome.

Thanks again
Regards,

EER

 

[EhoS]

Thanks for your collaboration '605'

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