Unsolved
This post is more than 5 years old
1 Message
0
1230
April 9th, 2008 08:00
Rolling back a firmware upgrade?
Can anyone point me in the right direction? I am interested in knowing whether FLARE code can be rolled back after an upgrade and if this extends to firmware updates as well.
No Events found!


praSAN-f_gEn
5 Posts
0
April 10th, 2008 02:00
If its commited you cant roll back.
However engineering can do that........
RRR
6 Operator
•
5.7K Posts
0
April 10th, 2008 04:00
Kiran3
410 Posts
0
April 10th, 2008 04:00
DGM3
238 Posts
0
April 10th, 2008 15:00
For any upgrade (either between major revs such as R22 to R24, or within a major rev such as R24 patch .011 to R24 patch .017) it's possible to "revert" back to the prior code up until the point in time when the new code has been "committed". The intent of the revert capability is to allow a new code rev to be installed, run for a period of time to evaluate, and easily rolled back (reverted) if desired. Note that when moving beteen major releases (e.g. R22 to R24) the array will continue to run with its existing feature set, and new features within the new major release will become available when the code is committed (for example when moving from R22 to R24, the R24 code needs to be committed in order to utilize RAID 6).
Outside the context of revert-commit, it's possible to install "old" software as long as it is within the current major release. Thus for an array that is running R24 patch .017 it would be possible to install R24 patch .011 - however it would not be possible to install R22 "over" R24 (since R22 is an older major release).
Regards,
DGM
praSAN-f_gEn
5 Posts
0
April 11th, 2008 21:00
This can only done under supervision of engineering team L3.
We can reimage the SP with the help of Mif file location in image repositery.
There are package available.....