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
4 Operator
•
14.4K Posts
1
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.
muser2
1 Rookie
•
15 Posts
0
January 14th, 2015 14:00
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.
Semper fidelis et paratus, /ALE
Sent from my iPhone 6 plus
ble1
4 Operator
•
14.4K Posts
1
January 14th, 2015 14:00
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).
cosky
11 Posts
0
January 14th, 2015 14:00
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.
thanks for your input.
ble1
4 Operator
•
14.4K Posts
0
January 14th, 2015 15:00
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).
cosky
11 Posts
0
January 14th, 2015 15:00
ugh, whatever happened to the term "easy"
thanks, I will start looking at the KB and manuals.
ble1
4 Operator
•
14.4K Posts
0
January 14th, 2015 15:00
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).
cosky
11 Posts
0
January 14th, 2015 16:00
that sounds like a good option. I tar'ed the /nsr directory and
restored it on the linux system. I don't think space is an issue Sun
only had 6 (73GB) drives of which /nsr is a small part. Linux system
has a 1TB system drive.
Thanks, I will give these a try and hope for the best.
jerry
muser2
1 Rookie
•
15 Posts
0
January 14th, 2015 17:00
To be honest "Support" should not advise you on this as direction, due to the complications is to engage Professional Services. /shrug
Best of luck.
Semper fidelis et paratus, /ALE
Sent from my iPhone 6 plus