NetWorker Server Migration

Did you use "name to be" in alias field before renaming it?

The problem is that in the client configuration you do not have any clint instance of the new name and thus your service wont come up. So as H already suggested add the new name in the aliases of the client configuration of the old name. Since you mentioned an FQDN i am assuming your server is on Windows. so follow the below procedure.

- open notepad and put the following into it and save as C:\add_alias.txt
     . type: nsr client; name: oldname

     update aliases: new_name;new_name.domain.com

- then with all the NetWorker services down run the following command (assuming NetWorker is installed in C:\Program Files)

     > nsradmin -d "C:\Program Files\EMC NetWorker\nsr\res\nsrdb" -i C:\add_alias.txt

- try starting the services now.

Hi

I didn't use aliases, but I created the client before I renamed the server.

First I restored bootstrap to new server, then created new client with the same client id as the old server was. After that I tried to rename the OS, but then the NetWorker server did not started.

I used SolVe Desktop procedure for migration.

Renaming server client is always done in 3 steps where you need to create one temporary name in between old and new name - this is very well documented and KB article exists on this subject.

Can you summarize the steps that you followed.

I will copy the steps from the procedure.

1. On source server I backuped the bootstrap and client file indexes of all the NetWorker clients
2. 2. Renamed the target NetWorker server to a temporary name
3. 3. Installed the NetWorker software to targer server
4. 4. Added *@* as the NetWorker Server Administrator
5. 5. Recovered the bootstrap from last backup

Renamed the NetWorker server from tempserver to target.emc.com To rename the NetWorker server:

• • Open the NetWorker Management Console.
  • Type the User Name and Password. The Console opens.
  • On the left column, click tempserver.
  • Right-click NetWorker and then select Launch Application. The NetWorker Administration window opens.
  • Click Configuration.
  • On the left column, right-click Clients and then select New. The Create Client window appears.
  • Select the General tab:
    1. a.   In the Name field, type the new client name that is to be used by the NetWorker server. In this example, target.emc.com is used.
       1. IMPORTANT: The new NetWorker client name must be the same as the name in the first alias in the host file.
    2. b.   Do not click OK.

• Select the Globals (1 of 2) tab:
  1. a.   In the Client id field, type the client id that you have saved in the clientid.log file. For example:

f933b670-00000004-4e8bbf37-4e8bbf36-00010c00-99693f29

1. b.   Click OK. The following message appears that indicates that all of the save sets from the source NetWorker server are being renamed to target.emc.com:

Found client: temp (server name),client id : xxxxxxxxx

Specify this client id or leave the client id blank. Otherwise the client name must first be renamed.

Renaming client source to target.emc.com.

Re-apply if this is desired.

1. c.   Click OK to accept the changes.
2. d.   In the Create Client window, click OK. The NetWorker server client resource and the save sets will be renamed from source to target.emc.com.

Task 7: Rename the NetWorker server from tempserver to target.emc.com

Since the current operating system name is tempserver, the NetWorker server target.emc.com should also be renamed at the operating system level.

To rename a NetWorker server from tempserver to target.emc.com:

• • In the Windows Start menu, click Start and then select Run.
  • At the command prompt, type the following:

drivers

• Click OK. The C:\WINDOWS\system32\drivers window opens.
• Double-click the etc folder.
• Edit the hosts file and ensure the following:
  1. a.   Assign the target server to the correct OS IP address. Since the NetWorker server is target.emc.com, this is the first alias that should be typed.
  2. b.   Delete any references to tempserver from the host file.

1. IMPORTANT:    The first alias should exactly match the name that was assigned to the NetWorker server. Otherwise, this might cause a problem with the clientid.

Task 8: Change the computer name

To change the computer name:

• • Right-click My Computer.
  • Click Change. The Computer Name Changes window appears.
  • In the Computer name field, type the target NetWorker server name. For example, target.emc.com.
  • The following message appears. Click OK.

• Click OK again.
• When the following window appears, click Yes to restart the NetWorker server. For example:

Task 9: Configure the NetWorker server with the new name

Consider the following before configuring the NetWorker server:

• The NetWorker software takes an average of five seconds to create an empty client file index folder for each NetWorker client that is configured with the NetWorker software. Since the client file indexes have not been recovered yet, this procedure uses the res folder from the production NetWorker server. The NetWorker software creates an empty index folder for each one of the NetWorker clients that are listed in the res folder. This might take a long time depending on how many NetWorker client resources are defined in the NetWorker server. Approximately 800 NetWorker client resources are processed per hour. Once the empty folders are created, the next time that the NetWorker software starts, it will start much faster.

As a workaround, copy the index directory from the source NetWorker server before you bring the NetWorker configuration to the new server.

• If the new host is still not on DNS or is unable to resolve some of the NetWorker clients or storage nodes, the NetWorker server will take a longer time to start.

As a workaround, populate the … /drivers/etc/hosts file with all of the NetWorker clients that are configured in the Console.

To populate the … /drivers/etc/hosts file with all of the NetWorker clients that are configured in the Console:

• • Stop the NetWorker services:

net stop nsrexecd

• Delete the current C:\Program Files\Legato\nsr\res directory including the res file. If the res file exists, duplicate default resources will be created in the Console. The res file does not overwrite, but appends.

1. Note: This temporary directory is no longer required.

• To use the older NetWorker configuration, rename the recovered
  C:\Program Files\Legato\nsr\res.R file to the following:

C:\Program Files\Legato\nsr\res

• Create a NetWorker Server resource by identifying the path for nsrdb:
  1. a.   From the Start menu, click Run. The Run window appears.
  2. b.   In the Run window, type services.msc and then click OK. The Services window appears.
  3. c.   Right-click the NetWorker Backup and Recover Server service and then select Properties. The NetWorker Backup and Recover Server Service Properties window appears.
  4. d.   Note the path listed under the Path to executable: attribute. For example, the path is:

C:\Program Files\Legato\nsr\bin\nsrd.exe

By default, the res directory is under nsr. For example:

C:\Program Files\Legato\nsr\res\nsrdb

• Use nsradmin to create the NetWorker Server Client resource:
  1. a.   At the command prompt, type the following and then press Enter.

nsradmin –d C:\Program Files\Legato\nsr\res\nsrdb

1. b.   At the nsradmin prompt, type the following and then press Enter:

create type:NSR client;name:target.emc.com

1. c.   At the Create? prompt, type the following and then press Enter:

y

1. d.   Type the following and then press Enter to exit nsradmin.

quit

• Start the NetWorker services:

   net start nsrd

and now I get error that NetWorker Server cannot start.

Did you rename the target server to a temporary name as mentioned in step Step 2. , FYI, it is referring to the hostname of the server and not the client instance name in NetWorker.

Yes I renamed the server to temporary name.

please get the output of the following commands:

>cd  "C:\Program Files\Legato\nsr\res"

> nsradmin -d nsrdb

nsradmin> . type: nsr client; name: old name

nsradmin> print

nsradmin> . type: nsr client; name: new name

nsradmin> print

The query with new name is empty.

nsradmin> . type: nsr client; name:target.emc.com

Current query set

nsradmin> print

No resources found for query:

                        name: target.emc.com;

                        type: nsr client;

if I create the client

nsradmin> create type:NSR client;name:target.emc.com

                        type: NSR client;

                        name: target.emc.com;

Create? y

created resource id 1.0.44.10.0.0.0.0.24.183.245.83.192.168.114.191(1)

nsradmin> . type: nsr client; name: target.emc.com

Current query set

nsradmin> print

                        type: NSR client;

                        name: target.emc.com;

and if I then close the database and then open it again the query is empty again. 

The query with old name:

Current query set

                        type: NSR client;

                     aliases: source.emc.com;

     application information: ;

            archive services: Disabled;

               archive users: ;

              backup command: ;

               backup config: ;

  Backup renamed directories: Disabled;

                 backup type: ;

          Block based backup: No;

               browse policy: 2 Years;

          Checkpoint enabled: Disabled;

      Checkpoint granularity: Directory;

               Client direct: Enabled;

              client OS type: Windows NT Server on Intel;

the output is very long

If you had done this right, there should be no client instance with the original name. as it should have been upated to the new name by assigning the client id of the source to the destination name when your backup server was re-named with the temporary intermediate name.

Yes, I know that but something went wrong. May be the problem is that the old is Windows 2003 Server and the new is Windows 2012 Server. Old server was upgraded from 7.6 but to new I installed NetWorker 8.1 and the NetWorker folders are in new location.

Nope, that is not it. The resource database wont get changed.

I would suggest you to rename you back server to the original name and re-do the migration progress all over again.

I can try to do the procedure again. Do you think I should now use Alias file that you suggested?

I believe it is better to go to the procedure of renaming the servers to a temporary hostname as it will ensure all your previous backups will be accessible and properly related.