Unsolved

This post is more than 5 years old

131 Posts

979

August 7th, 2008 13:00

Celerra Dart upgrade

Creating new thread again. We are upgrading from code 5.5.26 to 5.5.35 on a scheduled maintenance time.

Question is which method of upgrade should go smoothly. Like the disruptive or non-disruptive. I spoke with CE and he actually said was my call. He also said like the non-disruptive will take more time than the other. And the disruptive one is done through a script which does upgrade automatically both datamovers and will reboot at the same time i believe.

So, if anyone have done any of these methods and experiences would much help me prepare of for it.

thanks,
Ram

6 Operator

 • 

1.5K Posts

August 7th, 2008 14:00

Hi Ram,

You may choose either the option. Both will work smoothly. If you can plan for the downtime - you may choose the disruptive option where the data movers will be rebooted during the upgrade process, without any failover/failback of the active data movers.

In case of non-disruptive, the new code will not be in place on the data movers unless you reboot them and typically you will choose to reboot the standby data mover first and then failover the active data mover - reboot it and fail back. This will ensure the data is available to users (with the glitch during failover and failback) - but will take more time. Also, if you have more than one active data movers, the time taken will be even more (for each data mover you need to have separate failover/ failback one at a time).

My personal opinion will be, if you have a downtime or scheduled outage window - go for the first option where the data movers will be rebooted during the upgrade process.

However, others may provide their valuable feedback and suggestions.

Cheers,
Sandip

131 Posts

August 19th, 2008 14:00

Actually I should have updated like a week back. We could not do the code upgrade during the scheduled maintenance time. And the reason was that the pre-checks which the CE ran before beinging the upgrade, 1 of them failed and that was "getagent to cx700 from celerra" didn't finish with certain intreval and it failed. There are backup jobs running during that time frame and the sp utilizatiion was around 85% and we couldn't go further.

So, does the NS upgrade on Celerra depend on how busy is the CX700?

thanks

131 Posts

August 19th, 2008 14:00

Thats correct. flare upgrade would not allow to proceed. But CE told need to reschedule. Right now I am in a process to test pausing backup jobs and see the %utilization and then re-schedule DART the upgrade.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

August 19th, 2008 14:00

i have seen that error when my CE ran pre-upgrade script ..it was some weird communication glitch ..we ran the script again and it was fine. Since you are upgrading Dart code i don't see why array utilization should matter ..at least my CE never mention that as a concern. When you are doing Flare upgrade on the CX ...then it does matter.
No Events found!

Top