A restore and integration is typically recommended as the first option for recovery using MSC if available. This option is only available if journaling/logging is enabled and the backup system is used.

When a backup runs, a backup file (.4bk) and a backup of the journal/log (.4bk) is created. The backup file can essentially be considered as a compressed package like a zip file containing the items specified for the backup, which typically includes the datafile. These files are all at the state of the backup. The journals/logs contain all of the actions made since the current journal/log was created.

When restoring, a backup file is selected which basically extracts the files in the backup. The datafile at this point is typically older than the current datafile and missing some items. To address this, integration is performed next. By using the journals/logs between the backup and the latest journal file all of the actions can be reproduced and integrated into the datafile to bring it up to date.

While the process of performing backups and maintaining the backups may seem tedious, the benefits are worth it when trying to recover from an unforeseen event. The database settings allows the backups to be set easily and a cyclic set of backups can be saved such as the 10 newest ones deleting the oldest one if an 11th backup is created.

See also:
Tech Tip: Repair versus Restore