Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Petasan Upgradation process

Hi Team,
I have a query with the upgrade of the Petasan Version from 2.6.2 to 2.8.1 or to 3.0.
I did go through the upgrade document and worked without any issues, but this was tested in our 3 node Lab environment and went pretty well. The process hardly took an hour or little more since it was not that complicated without any service interruption.
My main Query was,
So If i had to make the changes to the production environment on phase wise  as in Node1 on day 1 and Node 2 on day2 and so on for 4 node cluster.

1) Is that best practice ?

2) By doing this" phase wise" will it impact any existing services or data ? (Ultimately, there should be no data loss or service interruption), By the end of process the upgrade would it be properly done ?

3)How to revert the changes back if there is any issue with the upgrade.

And What's the best way to do an upgrade. Pls suggest
In our test lab environment, I ran the upgrade one after the other, Would the time gap between upgrade have any drawbacks.

It would be nice if it is addressed point wise.
Thanks in advance.

as per the guide, wait for cluster health to be ok before upgrading a node.

like any clustered software, it is better to have all version the same, do not leave multi-version for too long.

Is there is a way to roll back the changes in case the upgrade to the highers version did not work properly or the cluster misbehaves.
It is not mentioned in the document, it would be helpful if it can be addressed here.
Thanks in advance.

No, once you upgrade you cannot go back.