V11 SP8

Recall Data - OnePass for UNIX File Systems

Use the following method to recover stubs of a file or multiple files from a UNIX terminal or console window.

  1. Any application accessing (read/write) the migrated data will trigger a recall. In order to manually perform a recall, follow the steps given below:
    • Open a Terminal or Console Window.
    • Perform an action that executes an open and read on an archived file to initiate the recovery operation. For example, you can use the vi or cat commands to do this:
      • vi <path><filename>
      • cat <path><filename>

  1. You can track the progress of the job from the Job Controller window of the CommCell console.

    Multiple stub recoveries are submitted to the Job Controller as one job called a Persistent Recovery job. The default timeout for a persistent recovery job is 24 hours.

  1. Once job is complete, you can view the details of job from the Restore History:
    • Right-click the <Backup Set> and select View | Restore History.
    • Click OK.

  1. Right-click the job and select View Job Details.

  1. After recovery, stubs are replaced by files in the location specified.

Recovered files:

Stubbed files:

Recall Stubs on FreeBSD

To recover the stubs the user should be a sudo user and/or part of Galaxy Service Account group.

Follow the steps given below to recall a single stub:

  1. Open a Terminal or Console Window, navigate to the <Software_Installation_Directory>\Base directory and type the following:

    /StubRecaller <file> [-instance] <instance name> [-StatusOnConsole] <on / off>[-help]


    • <file> is the full path of the file to be recalled.
    • <instance name> is specified in case there are more than one Commvault instances installed on the client computer.
    • StatusOnConsole option can be either Off or On.

      If you wish to see the status of successful /failed recalled files on console set this option to On.

      If you do not wish to see the status of successful /failed recalled files on console set this option to Off.

  2. If the StatusOnConsole is enabled then you will see recall status on the console.

    For example:

    Successfully recalled file /rpool/TempFil_00006.txt

    The output of all the recall jobs can also be verified from the StubRecaller.log. This log is available at /var/log/<Software_Installation_Directory>/Log_Files/StubRecaller.log