Upgrading from 6.1.3 to 7.x

- make full backup of the index and bootstrap
- unload all drives
- shutdown NW server
- shutdown any additional storage nodes
- detele content of /nsr/tmp on bck server and storage nodes
- uninstall bck server
- uninstall storage nodes
- install storage nodes
- install server

Some people like to redefine library after each major upgrade, but usually this is not necessary.

Oh.. are you asking about upgrade (what subject implies) or migrating (as mentioned in first post)? Well, you got yourself an answer to both

Migrating a Networker server

The supported way of migrating a Networker server is as per a disaster recovery:

1. Build your new networker server, ensure hardware, network, OS is functioning okay
2. install a blank copy of Networker
3. configure one device(can be in a jukebox) and load manually the tape with your bootstrap on it
4. run mmrecov and put in the details from your bootstrap report
5. stop Networker, rename nsr\res.R to nsr\res and restart Networker

You should now have your media database and resources back. You can now recover your indexes using nsrck -L7 (alternatively you can stop Networker and copy the nsr\index directory across).

Last thing is that you need to sort out a new license as the host ID and thus authorization code would have changed - you have 15 days to sort this out.

Cross-platform migration of Networker is unsupported unless you manually recreate the resources, scan in any media you want in your new system using scanner -m, and copying the index directories across; if you do get into this scenario be warned of potential block size mismatches as a result of the two OSs (my advice would be to avoid this scenario entirely by starting with a new system and keeping the old system with a standalone drive in the event of needing recoveries).