Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Overview

The main purpose of backing up the Verba database is to provide increased reliability and system recovery (fault tolerance) of the system. In case of a media or database failure, data can be restored from earlier database backups.

...

Recovery models comparison table

Recovery model

Benefits

Work loss exposure

Recover to point in time?

Simple

Permits high-performance bulk copy operations.

Reclaims log space to keep space requirements small.

Changes since the most recent database or differential backup must be redone.

Can recover to the end of any backup. Then changes must be redone.

Full

No work is lost due to a lost or damaged data file.

Can recover to an arbitrary point in time (for example, prior to application or user error).

Normally none.

If the log is damaged, changes since the most recent log backup must be redone.

Can recover to any point in time.

Bulk-Logged

Permits high-performance bulk copy operations.

Minimal log space is used by bulk operations.

If the log is damaged, or bulk operations occurred since the most recent log backup, changes since that last backup must be redone.

Otherwise, no work is lost.

Can recover to the end of any backup. Then changes must be redone.

Simple Recovery

Simple Recovery requires the least administration. In the Simple Recovery model, data is recoverable only to the most recent full database or differential backup. Transaction log backups are not used and minimal transaction log space is used. After the log space is no longer needed for recovery from server failure, it is reused.

...

  • Restore the most recent database backup.
  • Restore the last differential database backup.
  • Apply all transaction log backups created after the last differential database backup was created if you use Full or Bulk-Logged Recovery.