Restriction: You can use a version of an object in the Versioning Repository to recover a dropped (data) object only if a full offline backup image exists that was taken after that version was captured to the Versioning Repository. Thus, whenever you take a backup, always update the Versioning Repository just beforehand. Then, there is a Versioning Repository update that corresponds to the state of the backup. In order to be useful, you must combine Versioning Repository updates with backups. Because updating the Versioning Repository consumes very little time or resources (especially in stable production environments where DDL is run infrequently), we recommend that you schedule a Versioning Repository update immediately before every backup. If you already have a backup job scheduled, it is trivial to add the Versioning Repository update command just prior to the backup Note: Because some DB2 RE operations (for example, recovering a dropped table) actually run DDL, you should run a Versioning Repository update (and backup) after executing these DB2 RE operations. 4.2.5 Backing up the Versioning Repository