Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Rollback from Nw7 to 6.1.3 1
- Thread starter mikrei
- Start date
-
1
- #2
DavinaTreiber
Technical User
This is not really possible. 7.x (and 6.2 in fact) have the new resdb structure to replace the nsr.res and nsrjb.res files. This is a good thing because it improves performance by reducing contention on the nsr.res file, but it means that rolling back is difficult to say the least.
If you REALLY have to do this, then you have a couple of choices:
(1) Recover the res files from before the upgrade and accept that any config changes since then are lost. I really wouldn't recommend this.
(2) Use nsradmin to extract all the resources to a text file, then in 6.1.3 use nsradmin to read these from the text file and create the res files. This is not going to be easy and will require a bit of detailed knowledge and some nifty scripting. I very much doubt that Legato would support this approach, although if it was me I would see it as an interesting challenge. Perhaps Legato SMC would help you out, as a chargeable activity of course.
Out of interest, why do you need to do this? Is there any other way to solve whatever problem you have?
If you REALLY have to do this, then you have a couple of choices:
(1) Recover the res files from before the upgrade and accept that any config changes since then are lost. I really wouldn't recommend this.
(2) Use nsradmin to extract all the resources to a text file, then in 6.1.3 use nsradmin to read these from the text file and create the res files. This is not going to be easy and will require a bit of detailed knowledge and some nifty scripting. I very much doubt that Legato would support this approach, although if it was me I would see it as an interesting challenge. Perhaps Legato SMC would help you out, as a chargeable activity of course.
Out of interest, why do you need to do this? Is there any other way to solve whatever problem you have?
- Thread starter
- #3
The thing is that i upgraded from 6.1.3 to 7 about a month ago.
Then i requested an authcode from my reseller, but what i didn´t know was that my company didn´t payed the yearly support and updatefee to this company....
The result was that 2 days ago Legato expired....my company don´t want to buy the updatepackage and want me to rollback instead....hrrmmppfff..what can i say =)
Then i requested an authcode from my reseller, but what i didn´t know was that my company didn´t payed the yearly support and updatefee to this company....
The result was that 2 days ago Legato expired....my company don´t want to buy the updatepackage and want me to rollback instead....hrrmmppfff..what can i say =)
DavinaTreiber
Technical User
Oh I thought you were going to give me some good technical reason why you need to roll back. So your company doesn't want any support or upgrades, perhaps they don't care about the integrity of their data. That's their problem. Sadly it seems it makes it yours too.
Well, my option 2 is out then, there would be a considerable amount of time and effort involved, and perhaps a cost for consulting. You're stuck with recovering the old res files, or just starting again with a new config.
Sorry you're on your own. If you don't pay Legato you won't get your upgrade, and if all companies did this Legato might not be around to provide any more versions.
Well, my option 2 is out then, there would be a considerable amount of time and effort involved, and perhaps a cost for consulting. You're stuck with recovering the old res files, or just starting again with a new config.
Sorry you're on your own. If you don't pay Legato you won't get your upgrade, and if all companies did this Legato might not be around to provide any more versions.
- Thread starter
- #5
Yep,
The scenario was that the support and upgrade expired March last year, and no one told me until i called support the other day and i did´nt know that when i upgraded last month...
Isnt life beautiful?.....
I´ll try to convince my boss about the integrity of the data and the results of if we have a complete dataloss.
We have approx. 1.4 Terrabyte data on tape......
The scenario was that the support and upgrade expired March last year, and no one told me until i called support the other day and i did´nt know that when i upgraded last month...
Isnt life beautiful?.....
I´ll try to convince my boss about the integrity of the data and the results of if we have a complete dataloss.
We have approx. 1.4 Terrabyte data on tape......
In general i do not like the idea but in fact you can rollback
to you last NW 6.x backups. Simply run the disaster recovery procedure
of your last NW 6.x backups. Of course, you will loose the infos
for all later backups you have made.
I do not know whether you will succeed in scanning these save sets later.
However, at there has been no major change to the databases
introduced with
NW 7.x this might work.
If you have time and resources, you may simply try this on another
setver which you install for test purposes. You do not need a license
to do that.
So scanning the tapes with NW 7 updates is the key to success.
to you last NW 6.x backups. Simply run the disaster recovery procedure
of your last NW 6.x backups. Of course, you will loose the infos
for all later backups you have made.
I do not know whether you will succeed in scanning these save sets later.
However, at there has been no major change to the databases
introduced with
NW 7.x this might work.
If you have time and resources, you may simply try this on another
setver which you install for test purposes. You do not need a license
to do that.
So scanning the tapes with NW 7 updates is the key to success.
I think I missed something here. One should be able to roll
back to their previous nsr res directory..provided a jukebox
or something wasn't added in V7. One's file index and media database should be current and ok. One may need to reinventory the jukebox but I don't see where current backups
and file indexes are lost; unless something else changed besides the resource directory structure?
back to their previous nsr res directory..provided a jukebox
or something wasn't added in V7. One's file index and media database should be current and ok. One may need to reinventory the jukebox but I don't see where current backups
and file indexes are lost; unless something else changed besides the resource directory structure?
- Thread starter
- #8
Hi again,
Everything worked out fine, our company bought the upgrade support after my little talk about data integrity, dataloss, bla,bla and so on.
But i saved your comments and thoughts in my own "knowledgebase"
The upgrade support are now paid, and a authcode is under way.
Thanks for all your your help, and especially Davina, you are fast, correct and you seem to have a special ability to explain things that even i understand =)
Regards,
Mikael, from the cold country of SWEDEN
Everything worked out fine, our company bought the upgrade support after my little talk about data integrity, dataloss, bla,bla and so on.
But i saved your comments and thoughts in my own "knowledgebase"
The upgrade support are now paid, and a authcode is under way.
Thanks for all your your help, and especially Davina, you are fast, correct and you seem to have a special ability to explain things that even i understand =)
Regards,
Mikael, from the cold country of SWEDEN
To RMinNJ ...
Your thoughts are correct, in general. Yes, you can actually
merge all files from
the resource database to one nsr.res file. If you then restart the NW server, he will automatically convert them into the database. This in principle is the same what happens during
an update process.
However, with NW 7.x the media database slightly changed to improve robustness:
Legato added a checksum with each entry and also journaling. This
could become an issue. And as the info is not only saved with the database
backups but also with the data going to tape, this could become a problem
for the scanner command.
I guess nobody ever tested downgradeability ....
Your thoughts are correct, in general. Yes, you can actually
merge all files from
the resource database to one nsr.res file. If you then restart the NW server, he will automatically convert them into the database. This in principle is the same what happens during
an update process.
However, with NW 7.x the media database slightly changed to improve robustness:
Legato added a checksum with each entry and also journaling. This
could become an issue. And as the info is not only saved with the database
backups but also with the data going to tape, this could become a problem
for the scanner command.
I guess nobody ever tested downgradeability ....
- Status
Similar threads
- Locked
- Question
- Locked
- Question