Is the NW Server up and running at all?

I assume that you have shutdown the NW server prior to copying the directories.

  -  Did you start him later?

  -  If so, did it start at all? (yet)

       I am pretty sure that it will not be possible if you did not modify the resources.

I briefly looked through the document and from my first impression it is just incomplete in several areas. It seems to work if you migrate on the same platform family but not if you go beyond. Look at the general guideline I suggested some days ago

("Migrate Networker 8.2 on Solaris to RHEL").

nsrdr will most likely not work as this will recover the databases to the same directory/pathname which simply does not exist any more.

Hi bingo,

you are right. NetWorker did not start all the way. And I think I found the problem.

The old Linux NetWorker server has the name "networker.xxx.net" and the new Windows server "networker.yyy.net". That is because the old Linux machine is very old and in the meantime a new domain was created. The old domain does not exist anymore.

The daemon.log stated:

NetWorker is unable to continue its startup sequence due to a server hostname change to "networker.yyy.net"

I tried to edit the hosts file with the old name pointing to new IP of the new server but nothing helped.

My plan is now to rename the old NetWorker server on Linux with nsrclientfix to match the name of the new Windows server. And then perform the cross platform migration again.

Cheers

beacon

Maybe you just need to run nsrclientfix to correct you hostname issue.

############

I just ran a very brief test myself - just copying the most important databases ( res & mmdb ) from Linux to Windows - and to my surprise, it worked.

Of course, there are some details which you need to care of (the device names for example).

  -  no resource was rejected (and moved to /nsr/res/nsrdb/dbg)

  -  instead, the Linux device name appeared in Windows

  -  I could see all my save sets in my tiny media db

  -  For a brief test,

       -  I moved my file type device directory to a Windows directory

       -  created the appropriate device

       -  mounted the volume (this proves that the media db can resolve it)

       -  and ran a save set recover.

Once again - I do not say the migration is easy. There are a lot of things to take care of.

But in general, I do not see a show-stopper (so far).

Hi bingo,

that is what I did: Renamed the NetWorker server to match the new hostname.

After that the nsrmmdbasm command did run all the way through. But there were some things I had to fix afterwards. For example removing the lockbox of the old server or renaming the auditlog-hostname manually. Nothing mentioned about that in the guide.

I'm gonna try your way in the my lab. Seems way easier!

But thanks for the input!

Cheers,

beacon.

Just for curiosity I verified that you can easliy migrate the media db from Windows to Linux.

Once again - you need to be very careful with resources. And there are other issues which will obviously not work unless you adopt resources etc.

But in general, I can see nothing that will really stop you from a cross-platform migration.

Don't make a mystery where such does not exist.