Unsolved

This post is more than 5 years old

1 Rookie

 • 

24 Posts

4827

March 14th, 2017 08:00

Migration EMC Networker Configuration to another server

plan to change networker Server(include license server ) to another server and migrate database and all configuration

assume that

current server

name : networker1.home.local

ip : 10.10.10.1

networker version : 9.0.0.6

store backup files in EMC DataDomain

New Server

name : networker2.home.local

ip : 10.10.10.2

networker version : 9.0.0.6

store backup files in EMC DataDomain and i plan to add Tape Drive for DR beside DataDomain

how can i do this ??? and save all data and configuration. and client will update agent or what ?

263 Posts

March 15th, 2017 08:00

You should download and use SolVe Desktop.  This tool has information on most Dell EMC products, and can be used to generate procedures such as moving the NetWorker server.

https://community.emc.com/community/support/solve?source=promotion

https://community.emc.com/docs/DOC-52101?source=promotion

And this tool can be download from:  https://solve.emc.com/desktopbinaries/setup.exe

If possible, I would avoid renaming the Networker server.  Doing so without understanding the possible effects could cause problems with your NetWorker environment.

4 Operator

 • 

14.3K Posts

March 20th, 2017 08:00

Wallace wrote:

If possible, I would avoid renaming the Networker server.  Doing so without understanding the possible effects could cause problems with your NetWorker environment.

Exactly that.  While you can avoid problems of course by following steps in KB, it is also true that you can save some time and perhaps even unknown issues by just skipping that part.  Worth considering.

1 Rookie

 • 

7 Posts

October 11th, 2019 03:00

It is about a 34-steps to migrate from host1 to host2, however the store on the datadomain, now assigned to host1 should somewhere be renamed/assigned to host2, however, in SOLVE i do not see any information about this change/autochange or impact.

Even worse, in the community this is not named as well ...

Did you reused the name or walked through all 34 steps (Solve: NetWorker -> Migrate -> new name) ?

1 Rookie

 • 

7 Posts

October 11th, 2019 04:00

As you were "Itanium", same question to you:

It is about a 34-steps to migrate from host1 to host2, however the store on the datadomain, now assigned to host1 should somewhere be renamed/assigned to host2, however, in SOLVE i do not see any information about this change/autochange or impact.

Even worse, in the community this is not named as well ...

Did you reused the name or walked through all 34 steps (Solve: NetWorker -> Migrate -> new name) ?

4 Operator

 • 

1.3K Posts

October 11th, 2019 07:00

The default behavior of NetWorker is to create a new Storage Unit the fist time a boost device is created. If I understand you right you are concerned about the SU name after migration.   If you check the device access information you will see that it will contain the complete path to the folder on the DD where the respective device is created. on migration your existing devices will continue to work as before but the new devices that you will be configuring will now go to a the new SU which is going to be created with the hostname of the new hostname.

2 Posts

July 13th, 2023 19:00

Hi

I would like to know if you successfully migrated the old configuration, data to the new server as I am planning to do the same.

old server : NW 19.2, OS: Windows 2012 and Libraries added for backups

New server : NW 19.9, OSL Windows 2022 

I tried searching the KBs etc but there is no article describing the migration plan. All I had was disaster recovery documents. 

Please let me know how you achieved you requirements

Thanks,

 

No Events found!

Top