rollbackToDate command reverts your database to the state it was in at the date and time you specify.
rollbackToDate command is mainly used when you want to revert all changes made to your database from today's date to the date and time you specify. The
rollbackToDate command reverts those changesets to their previous state and allows you to target the date and time without impacting changes or deployments that came before the date and time you specified.
The image below shows four deployments performed at a different times: March, April, May, and February. Let's imagine that your current month is May and you want to roll back your database to March.
As you can see, the
rollbackToDate command allows you to target deployment 2 performed on March 07, 2020 10:15 AM and revert all changes associated with deployments 4 through 2, to March without impacting the previous deployments—deployment 2 and 1.
Note: There are several ways to revert your changes with the
rollbackToDate command. You can use
YYYY-MM-DD HH:MM:SS or
YYYY-MM-DD'T'HH:MM:SS formats to specify both date and time. Also, you can specify date or time only.
The impacts of
The use of
rollbackToDate comes with risk of removing all changes from today's date to the date you specified. Also, there is an additional impact to the DATABASECHANGELOG table. When any change is rolled back, the row associated with that change is deleted from the DATABASECHANGELOG table. For this reason, please look for unintended consequences before using this command.
It is a best practice is to run the
rollbackToDateSQL helper command because it allows you to inspect the
rollbackToDate SQL and search for any potential mistakes before you execute the
Before running the
rollbackToDate command, run the history command to see the dates of all your previous changes.
To run the
rollbackToDate command, you can specify the driver, classpath, and URL in your
liquibase.properties file. For more information, see Creating and configuring a liquibase.properties file. You can also specify these properties in your command line.
Then run the
liquibase --changeLogFile=sample.changelog.xml rollbackToDate 2020-05-07
Note: Enter the name of the changelog and date that you want to use in place of
rollbackToDate global attributes
||The root changelog||Required|
||The JDBC database connection URL||Required|
||The database username||Required|
||The database password||Required|
* Liquibase will check nested changelogs for definitions of the changesets to rollback.
Note: The username and password attributes are not required for connections and systems which use alternate means of authentication.
rollbackToDate command attributes
||The date and time your database rolls back to.
The date format is
Liquibase Pro 3.8.10-DAT-4254-SNAPSHOT by Datical licensed to Liquibase Pro Customer until Tue Nov 03 19:00:00 CST 2020 Rolling Back Changeset:postgres_lbpro_master_changelog.xml::3::createTableforCC-proschema::Liquibase Pro User Rolling Back Changeset:postgres_lbpro_master_changelog.xml::2::createTableforView-proschema::Liquibase Pro User Rolling Back Changeset:postgres_lbpro_master_changelog.xml::1::createTableforSynonym-proschema::Liquibase Pro User Rolling Back Changeset:changelogLevel.xml::2::logicalFilePath::changelog::Erzsebet (generated) Rolling Back Changeset:third_changelog.xml::1::logicalFilePath::changeset::Erzsebet (generated) Liquibase: Rollback has been successful.