Less Downtime for Maintenance

[digerata]

It takes too long to upgrade AppLogic. Currently, it is at least two hours of downtime + however long it takes to stop and start are applications.

And if the upgrade fails, you are pushing that out even further.

Is there anything on the road map on cutting down the maintenance window?

[agathongroup]

No need to wait for "the road map"; there's "upgrade1" and "upgrade2" to do what you want right now. "aldo upgrade1" doesn't destructively affect the grid and can be done during normal operation. "aldo upgrade2" is the part that takes all of the bits that upgrade1 started and puts them into place, rebooting the grid in the process. Downtime is cut by about 60-70% in our experience.

Check the aldo reference for more details. HTH!

[digerata]

Thanks for the input, Peter. Although, we aren't performing the upgrade, 3tera is. The standard drill we have been following from them is it takes 2 hours to do upgrade2, not including the time to stop/start our apps. (Which adds about 90 minutes.) With a failed upgrade, we hit 5 hours of downtime last night.

-Mike

[PeterNic]

Mike,

I am sorry that the upgrade didn't go as planned - we hit a rare failure during the upgrade and had to roll back. Most grids upgrade in 20-30 minutes.

Starting with the new AppLogic 2.7 release, most hotfixes either do not require restart or can be applied with rolling server restart -- which allows us to add minor feature and fix critical issues with minimum or no downtime. We are looking into several approaches to minimize (and ideally eliminate) downtime during full version upgrades for future releases (likely a 3.0 feature).

Our operations team will secure one of the senior engineering team members for your next upgrade to ensure smooth operation.

Thank you for your support!

-- Peter