{"id":768,"date":"2011-08-30T07:55:52","date_gmt":"2011-08-30T05:55:52","guid":{"rendered":"https:\/\/www.almtoolbox.com\/blog\/?p=768"},"modified":"2011-09-02T13:22:21","modified_gmt":"2011-09-02T11:22:21","slug":"how-to-integrate-clearcheck-with-your-clearcase-backup-script","status":"publish","type":"post","link":"https:\/\/www.almtoolbox.com\/blog\/how-to-integrate-clearcheck-with-your-clearcase-backup-script\/","title":{"rendered":"How to Integrate ClearCheck with your ClearCase Backup Script"},"content":{"rendered":"

ClearCheck, our add-on solution for monitoring the health of ClearCase enviornments, has a command line interface that enables administrators to include checks as part of the daily locking and unlocking of VOBs for backup.<\/p>\n

To download a trial version, click here:\u00a0https:\/\/www.almtoolbox.com\/download.php?did=1<\/a><\/p>\n

Windows<\/strong>
\nIn most cases, the backup script includes the following steps:<\/p>\n

    \n
  1. Lock all ClearCase VOBs<\/li>\n
  2. Copy all VOBs into another folder, disk or storage , or\u00a0make a file system snapshot<\/li>\n
  3. Unlock all VOBs<\/li>\n<\/ol>\n

    The command to run ClearCheck can be inserted immediately after step 2, before the VOBs are unlocked in step 3.
    \nAssuming that ClearCheck was installed in \u201cC:\\Program Files\\GoMidjets\\ClearCheck\u201d directory, the command line will be:<\/p>\n

    \u201cC:\\Program Files\\GoMidjets\\ClearCheck\\Clearcheck.exe\u201d \u2013exec<\/span><\/code><\/p>\n

    For example:
    \nAssuming the following:<\/p>\n

      \n
    1. Your backup script is\u00a0the following PERL script<\/a>\u00a0for Windows (taken from IBM site).<\/li>\n
    2. ClearCheck was installed in \u201cC:\\Program Files\\GoMidjets\\ClearCheck\u201d directory<\/li>\n<\/ol>\n

      The end of the script will be as follows:
      \n
      \n\u201cc:\\program files\\GoMidjets\\ClearCheck\\Clearcheck.exe\u201d \u2013exec<\/span>
      \nsystem(\"cleartool unlock VOB:$VOBtag\");<\/span>
      \nprint \"\\n\";\u00a0<\/span><\/code><\/p>\n

      UNIX \\ Linux<\/strong>
      \nClearCheck supports check on VOBs installed on UNIX \\ Linux but its management is always installed on Windows. In order to integrate the daily checks, a mechanism for coordinating the two systems is required.
      \nThe backup script runs on Unix\/ Linux and in most cases includes the following steps:<\/p>\n

        \n
      1. Lock all ClearCase VOBs<\/li>\n
      2. Copy all VOBs into another folder, disk or storage, or\u00a0make a file system snapshot<\/li>\n
      3. Unlock all VOBs<\/li>\n<\/ol>\n

        ClearCheck should perform the daily checks after the backup script has finished execution. For this reason, we configure the script to create a ‘flag’ file for ClearCheck to verify that it has finished running
        \nAdding ClearCheck to the script requires 3 steps:<\/p>\n

          \n
        1. Add a \u2018touch\u2019 command to your backup script. This command creates the flag file for ClearCheck.<\/li>\n
        2. Schedule ClearCheck to run at the same time as the backup script but only start its daily checks after the flag file is created.<\/li>\n
        3. Set ClearCheck to recognize the flag file.<\/li>\n<\/ol>\n

          For example, assuming the following:<\/p>\n