12:09 p.m.
Hi Guys!
How do you usually backup your hosted engine prior minor updates?
I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently. I’ve used engine-backup
before updating and for restore. However, the problem I’m encountering now is that, it
looks like the hosted-engine settings are only being restored. The version is still 4.3.9
when I’m trying to revert it to 4.3.8.
Am I missing some steps aside from engine-backup —restore? I saw on old posts that
snapshots of hosted engine is not a recommended step before upgrade/update.
Appreciate your help in advance!
1:21 p.m.
On Wed, Jun 10, 2020 at 1:05 PM <jrbdeguzman05(a)gmail.com> wrote:
engine-backup --mode=restore only restores the data. If you want 4.3.8
packages, you have to install them. For rolling back packages on an
existing machine, you can usually find the relevant yum transactions
and 'yum history undo $ID' on them.
If you installed and set up e.g. 4.3.8, and take a backup, then try to
restore this backup on 4.3.9, the next engine-setup you run (which is
a required step after restore) will upgrade your database
schema/content to 4.3.9.
Hope this helps,
--
Didi
8:42 p.m.
I use Gluster snapshots before patching the engine.
Usually the flow is:
1. Global Maintenance
2. Power off the HostedEngine VM
3. Gluster snapshot
4. Power on HE
5. Upgrade of the setup packages
6. Run the hosted-engine upgrade script
7. Patch the OS of HE
8. Reboot
9. Remove Global Maintenance
If you need to revert a snapshot, you need to stop the gluster volume , so you need to
follow the rule and keep the engine on a separate gluster volume.
Best Regards,
Strahil Nikolov
На 10 юни 2020 г. 13:21:08 GMT+03:00, Yedidyah Bar David <didi(a)redhat.com> написа:
>On Wed, Jun 10, 2020 at 1:05 PM <jrbdeguzman05(a)gmail.com> wrote:
>>
>> Hi Guys!
>>
>> How do you usually backup your hosted engine prior minor updates?
>>
>> I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently.
>I’ve used engine-backup before updating and for restore. However, the
>problem I’m encountering now is that, it looks like the hosted-engine
>settings are only being restored. The version is still 4.3.9 when I’m
>trying to revert it to 4.3.8.
>>
>> Am I missing some steps aside from engine-backup —restore? I saw on
>old posts that snapshots of hosted engine is not a recommended step
>before upgrade/update.
>
>engine-backup --mode=restore only restores the data. If you want 4.3.8
>packages, you have to install them. For rolling back packages on an
>existing machine, you can usually find the relevant yum transactions
>and 'yum history undo $ID' on them.
>
>If you installed and set up e.g. 4.3.8, and take a backup, then try to
>restore this backup on 4.3.9, the next engine-setup you run (which is
>a required step after restore) will upgrade your database
>schema/content to 4.3.9.
>
>Hope this helps,
1:48 a.m.
Hi Strahil,
Thank you for the suggestion. I'll take note of it and will definitely try those steps
once we have Gluster already configured. :)
Hi Didi,
Thanks for your inputs as well. I've tried the steps and was able to revert back to
4.3.8.
Here's the complete steps performed for the update / rollback:
1. Take backup of the current environment (1 node in maintenance mode).
2. Enable global maintenance.
3. Update the HostedEngine following the documentation available for minor updates
4. Update / install other packages using yum update
5. Disable global maintenance then reboot HE
If there's a need to rollback,
1. Run engine-cleanup
2. yum history undo ($ID of updates done in updates for step 3 and 2)
3. Perform a restore using the backup
4. Run engine-setup to complete the setup
Will try these steps for updating to 4.3.10. Thank you again! :)
1762
days inactive
1767
days old
3 comments
3 participants
participants (3)
-
jrbdeguzman05＠gmail.com -
Strahil Nikolov -
Yedidyah Bar David