Roll Back a FusionAuth Update

If your update is unsuccessful or causes unexpected issues, you may need to roll back your FusionAuth instance to a previous version.

Here are the steps for initiating a rollback:

1. Stop your FusionAuth instance.
2. Initiate the process to restore from the database backup taken prior to starting the update.
3. Redeploy FusionAuth using your previous version. How you do this will depend on your deployment method.

If you are running a FusionAuth Cloud deployment, you can find instructions for rolling back an update here: Roll Back to a Backup.

It's important to consider the timing implications of a rollback or any disaster recovery process:

• RTO (Recovery Time Objective) is the targeted period time within which a service should be restored after an outage to avoid unacceptable consequences. Simply put, it is how long you can afford to be without the service or system before it severely impacts your business. It represents the goal for the time taken to recover from failure.

• RPO (Recovery Point Objective) refers to the maximum tolerable amount of data loss measured in time. Determine RPO by looking at the time of the last backup you need to restore from and the restore time.

In the context of a FusionAuth update rollback:

• RTO: the time it takes to stand up the older version of the system and restore the database
• RPO: the time since the last backup before the update

The RPO effectively measures the maximum tolerable data loss in the event of a rollback, and the RTO measures the time it takes to recover from the failure.