How does rollback work for FusionAuth Cloud after a major version upgrade?

[FASupportBot]

We are planning to upgrade our FusionAuth Cloud instance from version 1.49.0 to 1.69.1 and want to understand the rollback process in case we encounter issues during the upgrade.

Specifically:

• How long are rollback backups retained after an upgrade?
• Can we perform a rollback ourselves on FusionAuth Cloud, or does it need to be done by FusionAuth support?
• What is the typical downtime for a rollback operation?
• Are there any plan-specific limitations for rollback availability?

[FASupportBot]

Rollback Process for FusionAuth Cloud

For FusionAuth Cloud deployments, the rollback process must be handled by FusionAuth support—it is not something you can perform yourself.

Plan Eligibility and Backup Retention

• Business and High Availability (HA) Deployments: Upgrade backups are retained and available for 30 days
• Basic Deployments: Backups are not included, so rollbacks cannot be performed

How to Request a Rollback

If you identify an issue after performing the upgrade:

1. Open a support ticket with FusionAuth
2. The support team will perform the complete database rollback for you

Expected Downtime

The rollback operation typically takes 20 minutes to 2 hours, depending on:

• Database size
• How quickly the operations team can complete the rollback

Note that this involves a complete database rollback, so plan for 1-2 hours of downtime.

Support During Upgrades

For production upgrades, FusionAuth can provide:

• An engineer on standby during your scheduled upgrade window
• An on-call support number for emergency assistance

Pre-Upgrade Best Practices

Before upgrading to 1.69.1:

1. Review Release Notes for breaking changes, database migrations, and API modifications
2. Choose an Upgrade Strategy:
   • Incremental (version-by-version) for lower risk
   • Direct upgrade for speed (but requires thorough testing)
3. Test in Staging to verify:
   • Authentication flows, webhooks, and APIs function correctly
   • Templates render properly
   • Database migrations complete successfully
4. Coordinate with Support to schedule the upgrade and have assistance available if needed