Skip to end of metadata
Go to start of metadata

This chapter summarizes the characteristics of each backup type, which are organized in the following tables.

Comparison by backup type


The following is a table comparing the pros and cons of each backup type.

ClassificationLogical backupPhysical backupIncremental backup
aexportiloaderOnline backupOffline backup
Characteristics
  • Object-level backup/recovery
  • Require backup only when changing object structure
  • Table-level

  • Record-level recovery is possible

  • When point-in-time recovery is unnecessary

  • When need to recover while the Altibase server is running
  • When to minimize data loss
  • When point-in-time recovery is required
  • When there is no burden on the archive log mode operation
  • When need to prepare for physical loss of files such as data files and log anchor files
  • When Altibase server downtime for backup can be secured
  • When to minimize recovery time
  • When to minimize data loss
  • When point-in-time recovery is required
  • When there is no burden on the archive log mode operation
  • When to prepare for physical loss of files such as data files and log anchor files
  • When the DB performance degradation due to activating the 'Page Change Tracking" function can be sustained
Pros
  • Altibase server operation possible during recovery

  • Altibase server operation possible during recovery
  • Point-in-time recovery is possible
  • Possible to prepare for the physical failure of data files and log anchor files
  • Minimize recovery time
  • Point-in-time recovery is possible
  • Possible to prepare for the physical failure of data files and log anchor files
  • Save backup time compared to online backup
  • Save backup space compared to online backup
Cons
  • -
  • Point-in-time recovery is unable
  • Manage archive log files
  • Operating Altibase server is unable during recovery
    • Operating Altibase server is unable during recovery
  • Manage archive log files
  • Operating Altibase server is unable during recovery

 

The following is a table comparing the features of each backup method in detail.

 

Backup type

Altibase server running statusDatabase modeBackup fileRecovery pointRecovery targetEtc.
      Backup    Recovery
Logical backupaexportRunningRunningIrrelevant
  • Database object creation script (.sql extension)
  • Automation script (.sh extension)
  • Backup point
  • Object-level
 
iloaderRunningRunning
  • FORM file for each table
  • Data file in text format
  • Backup point
  • Table-level
  • Record-level
 
Physical backupOnline backupRunning

Running

(Control step)

Archive mode
  • Disk data file
  • 1 memory checkpoint image file
  • Log anchor file
  • Archive log file
  • Complete recovery
  • Incomplete recovery
  • All databases
  • Tablespace-level
  • Require archive log file management
Offline backupStopped-Irrelevant
  • Disk data file
  • Memory checkpoint image file
  • Log anchor file
  • Online log file
  • Backup point
  • All databases
 
Incremental backupRunning

Running

(Control step)

Archive mode
  • Disk data file
  • 1 memory checkpoint image file
  • Log anchor file
  • Archive log file
  • backupInfo file
  • Complete recovery
  • Incomplete recovery

 

  • All databases
  • Tablespace-level
  • Neet to active 'Page Change Tracking" function
  • Require Archive log file

 

Related documents

  • Technical document " Altibase Capacity Guide"
  • Technical document "Volume Configuration Guide Considering disk I/O"
  • Administrator Manual -> 10. Backup and Recovery
  • Administrator Manual -> 11. Incremental backup and Recovery
  • Utilities Manual -> 1. aexport
  • iLoader User's Manual
  • Manual page: https://github.com/ALTIBASE/Documents/tree/master/Manuals

 

  • No labels