Moving networker from Sun system to Linux system - questions
We have a Sun v250 that was our main backup server running networker 7.2. We have since moved to another backup scheme but I am in need of restoring a couple files from the old server. Just booted it today after being turned off for ~ 1 year, so far 1 disk is going and 1 PS has failed. It did boot and I was able to tar the /nsr directory and move it to the linux ( Centos 5.10 ) system. This system is running the same version of networker as the Sun system. Although I am setting the system for restores only.
I am not a networker guru by any stretch, actually very novice. What do I need to do in order to read the configuration files and database so that I can just do restores? It is setup to see the tape ( sdlt320 ) but I don't see any of the volumes from the old system.
I believe this might not so easy and Solaris is big endian and Linux is small endian therefore one of DBs will have issues which may impact your restore attempt.
I know there's a SKU for this for professional services and I know that there a lot of challenging issues may want to consider asking for a visit from one of your Emc friends.
Well, he could do it himself by exporting DBs on Solaris and importing them on Linux, but I'm not sure how much stable and usable it is (actually, it should be usable enough if he managed to get nsr data out of it).
i didn't think about the fact that they are big vs little endian. I may be able to boot the system again, not sure. What process/commands would I use to export the database/import database.
In theory, you could just move /nsr/res and /nsr/mm and do ssid restore, but that would restore whole ssid (assuming you have enough space to accommodate it) as you could not browse specific file without index db. Of course, you can also specify specific file you want - in that case whole ssid is read, but only request file is returned (you imagine as cat foo | grep bar approach). Except that it read whole ssid, you must be aware that you need to know exact path and it is case sensitive (make mistake and you get nothing back).
Well, that's the catchy part as that part is supposed to be done by EMC folks... but details lie in manuals and some KB articles as well. For example mdb export you will find described in https://support.emc.com/kb/193762. In similar fashion you have nsrindexasm. The trick is that you are on your own as those should be used only when and how advised by support so if you really care about it then it is highly recommended to contact support to guide you with exact steps. Apart from these two, you have third database which is in /nsr/res. This is where your configuration is and obviously some path won't be correct (eg. binaries used by notifications).
ble1
6 Operator
•
14354 Posts
•
56186 Points
983
1
Posted January 14th, 2015 13:00
I believe this might not so easy and Solaris is big endian and Linux is small endian therefore one of DBs will have issues which may impact your restore attempt.