===== [V7] FAQ: How to run a Data Integrity Check on AhsayOBM version 7 on Linux (CLI) machine =====
Article ID
: 5163
Reviewed
: 2018-05-23
Product Version:
AhsayOBM: 7.7.2.0 to 7.x
OS: Linux / Unix
ATTENTION
1st January, 2022: v7 officially End-of-Life [details]
===== Description =====
This article offers a guideline on how run a data integrity check on AhsayOBM version 7 on Linux machine with Command Line Interface (CLI)
===== Steps =====
Data integrity check can be performed by running the RunDataIntegrityCheck.sh script file located in the installation bin folder.
By default, the Data Integirty Check script will:
# cd /usr/local/obm/bin
# vi RunDataIntegrityCheck.sh |
########################## RunDataIntegrityCheck.sh ######################## # You can use this shell script to run any of your backup sets from the # command line. Just customize the "User Defined Section" below with your # values for your backup action. ####################################################################### ######################## START: User Defined Section ####################### # ----------------------------------------- SETTING_HOME (Optional) ---------------------------------------- # | Directory to your setting home. # | Default to ${HOME}/.obm when not set. # | e.g. SETTING_HOME="${HOME}/.obm" # ------------------------------------------------------------------------------------------------------------------------ SETTING_HOME="" # ------------------------------------------------ BACKUP_SET -------------------------------------------------- # | The name or ID of the backup set that you want to run. # | If backup set name is not in English, please use ID instead. # | e.g. BACKUP_SET="1119083740107" # | or BACKUP_SET="FileBackupSet-1" # | You can use "ALL" to run data integrity check for all backup sets. # | i.e. BACKUP_SET="ALL" # | # | You can leave this parameter blank if you have only 1 backup set. # ----------------------------------------------------------------------------------------------------------------------- BACKUP_SET="ALL" # ----------------------------------------------- BACKUP_DEST ------------------------------------------------ # | The name or ID of the backup destination that you want to run. # | If backup destination name is not in English, please use ID instead. # | e.g. BACKUP_DEST="1740107119083" # | or BACKUP_DEST="Destination-1" # | You can use "ALL" to run data integrity check for all destinations. # | i.e. BACKUP_DEST="ALL" # | # | You can leave this parameter blank if you have only 1 destination. # | Remark: This option is ignored if BACKUP_SET="ALL" # ----------------------------------------------------------------------------------------------------------------------- BACKUP_DEST="ALL" # ------------------------------------------------- CRC_MODE --------------------------------------------------- # | You can run Cyclic Redundancy Check (CRC) during data integrity check # | Options available: ENABLE-CRC/DISABLE-CRC # | i.e. CRC_MODE="ENABLE-CRC" # | or CRC_MODE="DISABLE-CRC" # ----------------------------------------------------------------------------------------------------------------------- CRC_MODE="ENABLE-CRC" # ---------------------------------------------- REBUILD_MODE ------------------------------------------------ # | You can run rebuild index # | Options available: ENABLE-REBUILD/DISABLE-REBUILD # | i.e. REBUILD_MODE="ENABLE-REBUILD" # | or REBUILD_MODE="DISABLE-REBUILD" # ----------------------------------------------------------------------------------------------------------------------- REBUILD_MODE="DISABLE_REBUILD" ######################## END: User Defined Section ######################## |
# sh RunDataIntegrityCheck.sh - Using APP_HOME : /usr/local/obm Using SETTING_HOME : Using JAVA_HOME : /usr/local/obm/jvm Using JAVA_EXE : /usr/local/obm/jvm/bin/java Using JAVA_OPTS : -Xrs -Xms128m -Xmx768m -client -Dsun.nio.PageAlignDirectMemory=true Using JNI_PATH : -Djava.library.path=. Using CLASSPATH : .:./cb.jar - Running data integrity check for backup set - 'ALL', destination - 'ALL' ... log4j:WARN No appenders could be found for logger (org.apache.http.impl.conn.PoolingClientConnectionManager). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [doStart] Start data integrity check on backup set "backupset_name(backupset_id)" all destination, crc enabled [doDetail] Start processing data integrity check on backup set= "backupset_name" destination= "Dropbox4Business1TB" [doLogProgress] Browsing "backupset_id/blocks/YYYY-MM-DD-hh-mm-ss" [doLogProgress] Processing Job "Current", "/bin" [doLogProgress] Verifying CRC of file "/usr/bin/a2p" . . [doLogProgress] Processing Job "Current", "/usr/sbin" [doLogProgress] Checking dangling backup file index entries... [doInfo] Existing statistics of backup set= "backupset_name" destination= "Dropbox4Business1TB": Data area compressed size: 57.48MB, Data area uncompressed size: 127.8MB, Data area file count: 1497, Retention area compressed size: 0B, Retention area uncompressed size: 0B, Retention area file count: 0 [doInfo] Recalculated statistics of backup set= "backupset_name" destination= "Dropbox4Business1TB": Data area compressed size: 57.48MB, Data area uncompressed size: 127.8MB, Data area file count: 1497, Retention area compressed size: 0B, Retention area uncompressed size: 0B, Retention area file count: 0 [doInfo] The statistics of backup set= "backupset_name" destination= "Dropbox4Business1TB" is correct. [doInfo] Saving encrypted backup file index to backupset_id/blocks at destination Dropbox4Business1TB... [doDetail] Data integrity check on backup set= "backupset_name" destination= "Dropbox4Business1TB" is completed [doEnd][INFO] Finished data integrity check on backup set "backupset_name(backupset_id)" all destination, crc enabled [doInfo] Completed data integrity check on backup set "backupset_name(backupset_id)" all destination, crc enabled |
# cd /root/.obm/system/IntegrityCheck # ls -la total 36 drwxr-xr-x. 2 root root 4096 Jun 17 15:12 . drwxr-xr-x. 5 root root 59 Jun 17 14:29 .. -rw-r--r--. 1 root root 1600 Jun 17 14:29 2016-06-17-14-29-02.log -rw-r--r--. 1 root root 271 Jun 17 14:56 2016-06-17-14-56-14.log -rw-r--r--. 1 root root 1600 Jun 17 15:10 2016-06-17-15-10-26.log |