GitHub user rajujith edited a comment on the discussion: Best Practices for CloudStack Upgrade (Current Version: 4.19.3.0) – Request for Recommendations
@shakibshalim74 Try this in staging before attempting in production. Refer https://docs.cloudstack.apache.org/en/4.20.2.0/upgrading/upgrade/upgrade-4.19.html Full backup of cloud and cloud_usage databases, including routines. $ mysqldump -u root -p -R cloud > cloud-backup_$(date +%Y-%m-%d-%H%M%S) $ mysqldump -u root -p cloud_usage > cloud_usage-backup_$(date +%Y-%m-%d-%H%M%S) Snapshot / backup all Management Server VMs, Preserve: /etc/cloudstack/management SSL / LDAPS keystores On all 3 Management Servers: Upgrade CloudStack management packages to 4.20.2 Do NOT start the service yet This ensures all MS nodes run the same binaries before schema changes begin. Start ONE Management Server This server: Detects older schema version Performs automatic schema upgrades on : cloud,cloud_usage Monitor: `management-server.log` Verify UI/API access Start Remaining Management Servers Start the Management service on the remaining MS nodes Validate: All MS are Up KVM Host Upgrade Upgrade `cloudstack-agent` on one host, then upgrade all other hosts with automation or other tools available. Restart agent only Running VMs are not impacted System VM Template Upgrade Reboot / redeploy: VR CPVM SSVM RollBack: Disable the zone/s. Delete any SystemVM,VRs created after the upgrade Stop all Management Servers Restore cloud + cloud_usage DB backups Downgrade management packages Downgrade cloudstack-agent on all KVM hosts Start Management Servers Enable the zone, redeploy: VR CPVM SSVM GitHub link: https://github.com/apache/cloudstack/discussions/12377#discussioncomment-15430635 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
