Revert or Backtrack Changes

You can return a database to the state it was in at a previous session. This might be necessary if a major error, such as an incorrect mass deletion, has been made. Or, it might be decided that a significant change to the design of a project should be reversed.

Returning a database to a previous state can be achieved with either the Backtrack or the Revert method.

Backtrack

Backtrack Backtrack permanently removes all work done from the present to a date specified date in the past, or to a specified session number.

Note: Backtrack is irreversible and so must be used with great caution. It is only available from the Command Line.

Revert

Revert creates a new session in the database. The database then skips and ignores sessions between the present and a specified date in the past. The data is not deleted.

Click Revert on the Manage tab. The Revert Changes window is displayed.

Select the database required from the list. You can revert changes by specifying a time, date, session number or Stamp.

Note:
Subsequent sessions will be lost, so the user may want to copy a database before backtracking. You can backtrack to the date, session number or stamp required.

Rebuild list is used to update the list of databases. For example, if a new database has been created while the window is displayed, the list will not be updated until the window is closed and re-displayed, or click Rebuild list.

(Refer to Reverting Extracts for information about reverting extracts to an earlier session.)