✎ [V7] FAQ: How to run a Data Integrity Check on AhsayOBM version 7 on Linux (CLI) machine [Ahsay Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== [V7] FAQ: How to run a Data Integrity Check on AhsayOBM version 7 on Linux (CLI) machine   =====

<html>
 <b>
  Article ID
 </b>
 : 5163
 <br/>
 <b>
  Reviewed
 </b>
 : 2018-05-23
 <br/>
 <br/>
 <b>
  Product Version:
 </b>
 <br/>
 AhsayOBM: 7.7.2.0 to 7.x
 <br/>
 OS: Linux / Unix
</html>

<html>
<FONT COLOR=red SIZE=+1>
<B>ATTENTION</B>
1st January, 2022: v7 officially End-of-Life [<A HREF=https://wiki.ahsay.com/doku.php?id=public:announcement:ahsay_v7_eol>details</A>]
</FONT>
</html>


===== 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 =====
<html>
Data integrity check can be performed by running the RunDataIntegrityCheck.sh script file located in the installation bin folder.
 <br/>
 <br/>
 By default, the Data Integirty Check script will:
 <br/>
 <ul>
  <li>
   <font color=black>Perform the check for all backup sets</font>
  </li>
  <li>
   <font color=black>Perform the check for all storage destinations</font>
  </li>
  <li>
   <font color=black>Cyclic Redundancy Check (CRC) is disabled by default</font>
  </li>
  <li>
   <font color=black>Rebuild index is disabled by default</font>
  </li>
 </ul>
 <u>Assumption</u>:
 <br>
 AhsayOBM is installed in the following path /usr/local/obm
 <br/>
 <br/>
 <ol >
  <li>
   <font color=black>Login to the Linux machine with root.</font>
   <br/>
   <br/>
  </li>
  <li>
   <font color=black>Edit the the RunDataIntegrityCheck.sh script with a text editor.  
   <br/>
   <br/>
   <table border="0" cellpadding="0" cellspacing="0" width="600">
    <tr>
     <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white># cd /usr/local/obm/bin
      <br>
      # vi RunDataIntegrityCheck.sh</font>
     </td>
    </tr>
   </table>  
Modify the settings in the file according to your requirement.
<br>
<br>
<table border="0" cellpadding="0" cellspacing="0" width="600">
  <tr>
    <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white>##########################  RunDataIntegrityCheck.sh  ########################<br>
# You can use this shell script to run any of your backup sets from the<br>
# command line. Just customize the "User Defined Section" below with your<br>
# values for your backup action.<br>
#######################################################################<br>
########################  START: User Defined Section  #######################<br>
# ----------------------------------------- SETTING_HOME (Optional) ----------------------------------------<br>
# | Directory to your setting home.<br>
# | Default to ${HOME}/.obm when not set.<br>
# | e.g. SETTING_HOME="${HOME}/.obm"<br>
# ------------------------------------------------------------------------------------------------------------------------<br>
SETTING_HOME=""<br>
<br>
# ------------------------------------------------ BACKUP_SET --------------------------------------------------<br>
# | The name or ID of the backup set that you want to run.<br>
# | If backup set name is not in English, please use ID instead.<br>
# | e.g. BACKUP_SET="1119083740107"<br>
# |  or  BACKUP_SET="FileBackupSet-1"<br>
# | You can use "ALL" to run data integrity check for all backup sets.<br>
# | i.e. BACKUP_SET="ALL"<br>
# |<br>
# | You can leave this parameter blank if you have only 1 backup set.<br>
# -----------------------------------------------------------------------------------------------------------------------<br>
BACKUP_SET="ALL"<br>
<br>
# ----------------------------------------------- BACKUP_DEST ------------------------------------------------<br>
# | The name or ID of the backup destination that you want to run.<br>
# | If backup destination name is not in English, please use ID instead.<br>
# | e.g. BACKUP_DEST="1740107119083"<br>
# |  or  BACKUP_DEST="Destination-1"<br>
# | You can use "ALL" to run data integrity check for all destinations.<br>
# | i.e. BACKUP_DEST="ALL"<br>
# |<br>
# | You can leave this parameter blank if you have only 1 destination.<br>
# | Remark: This option is ignored if BACKUP_SET="ALL"<br>
# -----------------------------------------------------------------------------------------------------------------------<br>
BACKUP_DEST="ALL"<br>
<br>
# ------------------------------------------------- CRC_MODE ---------------------------------------------------<br>
# | You can run Cyclic Redundancy Check (CRC) during data integrity check<br>
# | Options available: ENABLE-CRC/DISABLE-CRC<br>
# | i.e. CRC_MODE="ENABLE-CRC"<br>
# |  or  CRC_MODE="DISABLE-CRC"<br>
# -----------------------------------------------------------------------------------------------------------------------<br>
CRC_MODE="ENABLE-CRC"<br>
<br>
# ---------------------------------------------- REBUILD_MODE ------------------------------------------------<br>
# | You can run rebuild index<br>
# | Options available: ENABLE-REBUILD/DISABLE-REBUILD<br>
# | i.e. REBUILD_MODE="ENABLE-REBUILD"<br>
# |  or  REBUILD_MODE="DISABLE-REBUILD"<br>
# -----------------------------------------------------------------------------------------------------------------------<br>
REBUILD_MODE="DISABLE_REBUILD"<br>
<br>
######################## END: User Defined Section ########################</font>
    </td>
  </tr>
</table>  
Note:<br>
The rebuild index option (REBUILD_MODE) is only available for AhsayOBM version 7.15.6.0 or above.
  </li>
  <br>
  <li>
   <font color=black>Start the data integrity check by running the RunDataIntegrityCheck.sh script file.
   <br>
   <br>
   Note: 
   <br>
   The following output is an example of a integrity check performed for a file backup set on DropBox storage destination:
   <br>
   <br>
<table border="0" cellpadding="0" cellspacing="0" width="600">
  <tr>
    <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white># sh RunDataIntegrityCheck.sh<br>
-<br>
Using APP_HOME      : /usr/local/obm<br>
Using SETTING_HOME  :<br>
Using JAVA_HOME     : /usr/local/obm/jvm<br>
Using JAVA_EXE      : /usr/local/obm/jvm/bin/java<br>
Using JAVA_OPTS     : -Xrs -Xms128m -Xmx768m -client -Dsun.nio.PageAlignDirectMemory=true<br>
Using JNI_PATH      : -Djava.library.path=.<br>
Using CLASSPATH     : .:./cb.jar<br>
-<br>
Running data integrity check for backup set - 'ALL', destination - 'ALL' ...<br>
log4j:WARN No appenders could be found for logger (org.apache.http.impl.conn.PoolingClientConnectionManager).<br>
log4j:WARN Please initialize the log4j system properly.<br>
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.<br>
[doStart] Start data integrity check on backup set "backupset_name(backupset_id)" all destination, crc enabled<br>
[doDetail] Start processing data integrity check on backup set= "backupset_name" destination= "Dropbox4Business1TB"<br>
[doLogProgress] Browsing "backupset_id/blocks/YYYY-MM-DD-hh-mm-ss"<br>
[doLogProgress] Processing Job "Current", "/bin"<br>
[doLogProgress] Verifying CRC of file "/usr/bin/a2p"<br>
.<br>
.<br>
[doLogProgress] Processing Job "Current", "/usr/sbin"<br>
[doLogProgress] Checking dangling backup file index entries...<br>
[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<br>
[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<br>
[doInfo] The statistics of backup set= "backupset_name" destination= "Dropbox4Business1TB" is correct.<br>
[doInfo] Saving encrypted backup file index to backupset_id/blocks at destination Dropbox4Business1TB...<br>
[doDetail] Data integrity check on backup set= "backupset_name" destination= "Dropbox4Business1TB" is completed<br>
[doEnd][INFO] Finished data integrity check on backup set "backupset_name(backupset_id)" all destination, crc enabled<br>
[doInfo] Completed data integrity check on backup set "backupset_name(backupset_id)" all destination, crc enabled<br></font>
    </td>
  </tr>
</table>  
   Note:
   <br/>
   The warning messages displayed can be safely ignored. The data integrity check is not affected by the warning (<a href="http://wiki.ahsay.com/doku.php?id=public:5207_no_appenders_warning_when_running_script_on_linux">Details</a>).
  </li>
  <br>
  <li>
   <font color=black>Integrity check logs can be found in the following path /root/.obm/system/IntegrityCheck</font>
   <br/>
   <br/>
<table border="0" cellpadding="0" cellspacing="0" width="600">
  <tr>
    <td style="BACKGROUND-COLOR: black">
      <font size=2 color=white># cd /root/.obm/system/IntegrityCheck<br>
# ls -la<br>
total 36<br>
drwxr-xr-x. 2 root root 4096 Jun 17 15:12 .<br>
drwxr-xr-x. 5 root root   59 Jun 17 14:29 ..<br>
-rw-r--r--. 1 root root 1600 Jun 17 14:29 2016-06-17-14-29-02.log<br>
-rw-r--r--. 1 root root  271 Jun 17 14:56 2016-06-17-14-56-14.log<br>
-rw-r--r--. 1 root root 1600 Jun 17 15:10 2016-06-17-15-10-26.log</font>
    </td>
  </tr>
</table>  
  </li>
 </ol>
</html>


===== Keywords =====
CRC, Linux, Unix, data integrity check, CLI
User Tools

Site Tools

Page Tools
