Advanced Restore - MySQL iDataAgent

Table of Contents

Understanding the Restore Options Window

Browse provides an easy-to-use convenience to search and restore data.

You can open the browse and restore window from backup-set or subclient level. The sub levels displayed in the result window is based on where you start the browse operation.

Selecting Objects from the Restore Window for Restore

The restore window displays objects and consists of two parts:

  • The left pane displays the object tree at the selected level.
  • The right pane displays the contents of the selected object.

Note that the window displays only the data that was obtained by a backup. Data that is excluded by a filter, or data which did not exist as of the specified browse time does not appear in the window.

Selections follow these rules:
  • All selections are recursive.
  • Clicking a box again causes the selection to be cleared.
  • If you select an object in the left pane, then all of its contents are selected.
  • You can select a specific object in the right pane.

Selection status is revealed by the selection icons as follows:

Indicates that the object is not selected for restoration.
Indicates that a portion of the object is selected for restoration. i.e., only some of the child object(s) within the selected object.
Indicates that the entire object, including all of its child objects, are selected for restoration.

Browse Data

The option to browse the backup data provides the facility to view and selectively restore/recover the data that was backed up.

The browse option can be invoked from the client, agent, or instance level depending on the functionality of a given agent.

Depending on the agent, there are several additional options to customize your browse, including:

  • Capability to browse the most recent (latest) data.
  • Capability to browse data in a specified time range.
  • Capability to limit the browse to a specified path.
  • Facility to specify the page size of the browse window.
  • Ability to browse the image of the data as it existed at the specified browse time.
  • Ability to browse from a specified storage policy copy.
  • Ability to browse all data including deleted items secured by data protection operations.

Browse the Latest Data

Follow the steps given below to view the latest data backed up by a backup set:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, and then select All Tasks | Browse and Restore.
  3. Click View Content.

    The latest data backed up by all the subclients is displayed in the newly opened window.

Browse Data before a Specified Backup Time

Follow the steps given below to browse the data backed up before specified time. This will display data from all cycles that fall under the specified time range.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, and then select All Tasks | Browse and Restore.
  1. Select Time Range.
  2. Under Absolute Time do the following:
    1. Select the Time Zone.
    2. Select End Time and enter a date and time to browse and restore data before it.
  3. Click View Content.

Browse Data between a Specified Backup Time

Follow the steps given below to browse data between specified time:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, and then select All Tasks | Browse and Restore.
  1. Select Time Range.
  2. Under Absolute Time do the following:
    • Select Start Time and enter a date and time.
    • Select End Time and enter a date and time.

    Data in between the time specified here will be browsed and restored.

  3. Click View Content.

Browse Data Backed Up in the Past n Days

You can specify a relative time for Browsing data for Restores. This provides flexibility in trawling backed up data from a wider time span rather than the need to remember an exact time range in which something was backed up.

Follow the step given below to Browse Data from a relative time:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, and then select All Tasks | Browse and Restore.
  1. Select Time Range and click Relative Time.
  2. Enter a number in the Last field and select Day, Week, Month or Year to browse and restore data.
  3. Click View Content.

Browse from Copies

By default, when a browse operation is requested, the software attempts to browse from the storage policy copy with the lowest copy precedence. If the data that you want to browse was already pruned from the primary copy, the software searches the other copies of the storage policy, starting from the copy with the lowest copy precedence to a copy with the highest copy precedence.

This feature is useful in the following conditions:      

  • The media containing protected data for a particular copy has been removed from the storage library, you can choose to browse from a copy whose media are inside the library.
  • Allows browsing from a copy that accesses faster disk media rather than slower tape media.
  • When media drives used by a particular copy are busy with another operation, this helps in browsing from a different copy to avoid resource conflicts.
  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, and then select All Tasks | Browse and Restore.
  1. From the Browse and Restore Options dialog box, select the Advanced Options tab.
  2. Select Browse from copy precedence checkbox and specify the preference number.

    If you specify a copy precedence number for a browse operation, the software searches only the storage policy copy with that precedence number in all storage policies used for securing the data. If data does not exist in the specified copy, the browse operation fails even if the data exists in another copy of the same storage policy.

  3. Click View Content.

Browse Using MediaAgent

Data can be restored from any compatible library and drive type in the CommCell. By default, the system automatically identifies and restores data from any configured library in the CommCell, even if the media is not available in the original library in which the data protection operation was performed. Use this procedure to Browse using a specific MediaAgent.

If a MediaAgent is selected for browse, the library and media that are required for restore operation must be accessible to this MediaAgent for restore. The Restore may fail if it is not accessible.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click an instance and click All Tasks | Browse and Restore.
  1. From the Restore Options dialog box, click the Advanced Options tab and choose the MediaAgent that must be used to perform the browse.
  2. Click View Content.

List Media

List media option is useful to predict how much media is required to restore the index that is required to browse data. This is useful when the index is not available in the index cache.

The following section describes how to perform this operation.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, and then select All Tasks | Browse and Restore.
  1. Click List Media.

    You can use the Latest Data to list media associated with the most recent data protection cycle.

    Or Specify Browse Time to list media associated with data protection operations up to the specified date and time range.

  2. From the List Media dialog box, click List Media for restore within specified time range.
  3. Click OK.
  4. The appropriate media is listed in the Media dialog box.

Restoring and Recovering an Entire Server

Whenever the MySQL databases are corrupt or lost, you can restore and recover them individually.

We recommend that you do not drop MySQL database before performing a restore operation. MySQL database should be running when you perform restore operation.

To the Same Instance on the Source Client

By default, the data is restored to the same location from where it was backed up, and the existing database files are overwritten. This restore leaves the database in an online state.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance> on the source client.
  3. Click All Tasks, and then click Restore MySql Server.
  4. Verify that the Destination Server State of the database is On-Line. If necessary, click Refresh to update the status.
  5. Select Data and Log.
  6. Select Recover.
  7. Click OK.

To a Different Instance on the Source Client

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance> on the source client.
  3. Click All Tasks, and then click Restore MySql Server.
  4. In the dialog box that appears, from the Destination Server list, select the name of the instance where you want to restore.
  5. Verify that the Destination Server State of the database is On-Line. If necessary, click Refresh to update the status.
  6. Select Data and Log.
  7. Select Recover.
  8. In the Staging Location box, enter the staging location where the logs will be restored.
  9. Click OK.

To a Different Destination Server (Cross-Machine Restore)

You can restore a server to the same instance on a different client (also called a cross-machine restore). When a server is restored to another client, the restored data inherits the permissions from the parent directory.

If you are restoring the MySQL system database while performing a cross machine restore, ensure that both the source and the destination servers have MySQL instance created in the CommCell Console using the same SA username and password.

If SA user information of the source server is not available at the destination server, first create the same SA username and password on the destination server, and then create an instance on the destination server from the CommCell Console before starting the restore operation.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance> on the source client.
  3. Click All Tasks, and then click Restore MySql Server.
  4. In the dialog box that appears, from the Destination Server list, select the name of the destination client computer where you want to restore.
  5. Verify that the Destination Server State of the database is On-Line. If necessary, click Refresh to update the status.
  6. Select Data and Log.
  7. Select Recover.
  8. In the Staging Location box, enter the staging location where the logs will be stored.
  9. Click OK.

To a Point-in-Time

The point-in-time database restore is useful in the following scenarios:

  • If any unwanted transaction occurs in the database, you can revert the database to a state just before the transaction.
  • If a database fails, you can restore to the state just before the point of failure.

When you perform a point-in-time restore for a database, the next scheduled backup for that database converts to a full backup automatically.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, click All Tasks, and then click Restore MySql Server.
  3. Verify that the status of the destination server is On-Line. If necessary, click Refresh to update the status.
  4. In the Staging Location box, enter the location where the server will be restored.
  5. Select Point-in-time, and then set the restore date, time, and time zone to the appropriate values.
  6. Click OK.

Restoring and Recovering Individual Databases

In addition to restoring the MySQL Server, you can restore specific databases that were lost due to an error or corruption. By default, the selected databases are restored to the original location from the latest backup.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, click All Tasks, and then click Browse and Restore.
  3. In the dialog box that appears, click View Content.
  4. Select one or more databases, and then click Recover All Selected.
  5. In the dialog box that appears, from the Destination Server list, select the name of the client computer that contains the instance where you want to restore the database.
  6. Verify that the status of the database is On-Line. If necessary, click Refresh to update the status.
  7. In the Staging Location box, enter the location where the database will be restored.
  8. Click OK.

To a Point-in-Time

Restore a database to a point-in-time if you want to revert the database to a point before a transaction, or if you need to restore a database to the point prior to a failure.

When you perform a point-in-time restore, the next scheduled backup of the database automatically converts to a full backup.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, click All Tasks, and then click Browse and Restore.
  3. In the dialog box that appears, click View Content.
  4. Select one or more databases, and then click Recover All Selected.
  5. In the dialog box that appears, from the Destination Server list, select the name of the client computer that contains the instance where you want to restore the database.
  6. Verify that the status of the database is On-Line. If necessary, click Refresh to update the status.
  7. In the Staging Location box, enter the location where the database will be restored.
  8. Select Point-in-time, and then set the restore date, time, and time zone to the appropriate values.

    Make sure that the point-in-time is later than the browse time that is set in the Browse and Restore Options dialog box.

  9. Click OK.

Restoring Transaction Logs

By default, both data and logs are restored. You can restore only the logs whenever it is necessary.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance> on the source client.
  3. Click All Tasks, and then click Restore MySql Server.
  4. In the dialog box that appears, clear Data.
  5. Select Log, if necessary.
  6. In the Staging Location box, enter the location where the logs will be restored.
  7. Click OK.

Recurring Restores of Logs

When you perform log restores, you can choose to include the recurring logs for the restore. This is useful when you want to replicate data from one server to another during failover cases.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance> on the source client.
  3. Click All Tasks, and then click Restore MySql Server.
  4. In the dialog box that appears, clear Data.
  5. Select Log, if necessary, and select Recurring Restore.
  6. Select Do Not Recover to replicate offline data from one server to another server.
  7. In the Destination Folder box, enter the location where the logs will be restored.
  8. Click OK.

Restoring Data and Transaction Logs without Recovery

By default, the databases and logs are recovered along with the restore. However, if the MySQL Server is offline, you can restore the data and the logs to a destination folder. Later, you can recover the MySQL Server.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click <Instance>, click All Tasks, and then click Browse and Restore.
  3. In the dialog box that appears, click View Content.
  4. Select the appropriate database, and then click Recover All Selected.
  5. In the dialog box that appears, select Data and Log, if necessary.
  6. Select Do not Recover.
  7. In the Destination Folder box, enter the location where the database and the transaction logs will be restored.
  8. Click OK.

Applying the Logs and Database Dumps Manually to the MySQL Server

While performing a restore operation, you can apply the logs and database dumps to the MySQL Server in the following cases:

  • If the MySQL Server is offline, select the Do not Recover option and perform the restore operation. After the MySQL Server is online, you can apply the logs and database dumps to the MySQL Server.
  • If you want to replicate offline data from one server to another server, select the Do not Recover option and perform the restore operation. Later you can apply the logs and database dumps to the MySQL Server.

Before You Begin

Stage database dumps and logs to a destination folder. For detailed information, see Restoring Data and Transaction Logs without Recovery.

Procedure

  1. Use the following steps to apply database dumps to the MySQL Server:
    1. Run the following command to drop the database dump in the MySQL Server:

      drop database <database name>

      Example:

      drop database mydatabase2

    2. To apply the database dump to the MySQL Server, run the following command :

      mysql -u <username> -p <password> < dumpfile

      Example:

      mysql -u root -p <mydatabase2
      Password:*****

  2. To restore database to a particular point in time, you can use the following steps to apply logs to the MySQL Server:
    1. Identify the master log file number and master log position from the database dump file saved at the staging location:

      Example: CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000104', MASTER_LOG_POS=107

    2. To apply the master log file to the MySQL Server, run the following commands:

      mysqlbinlog <master logfile> --stop-datetime=<PIT> -d <databasename> --result-file=<result file name> --start-position=<master log position>

      mysql -u <username> -p -D <database name> -e "source <result file name>"

      Example:

      mysqlbinlog mysql-bin.000104 --stop-datetime="2015-10-6 15:36:0" -d mydatabase2 --result-file=new.sql --start-position=107

      mysql -u root -p -D mydatabase2 -e "source new.sql"

    3. After applying the master log file, you can apply a log file with the next sequential log file number.

      For example, if the master log file number is mysql-bin.000104, the next log file that you can apply should have mysql-bin.000105 as its log file number. Then apply the second log file with log file number mysql-bin.000106, and so on.

      Run the following commands for each log file that you want to apply to the MySQL Server:

      mysqlbinlog <logfile> --stop-datetime=<PIT> -d <databasename> --result-file=<result file name>

      mysql -u <username> -p -D <database name> -e "source <result file name>"

      Example for applying log file number mysql-bin.000105:

      mysqlbinlog mysql-bin.000105 --stop-datetime="2015-10-6 15:36:0" -d mydatabase2 --result-file=new.sql

      mysql -u root -p -D mydatabase2 -e "source new.sql"

      Example for applying log file number mysql-bin.000106:

      mysqlbinlog mysql-bin.000106 --stop-datetime="2015-10-6 15:36:0" -d mydatabase2 --result-file=new.sql

      mysql -u root -p -D mydatabase2 -e "source new.sql"

      Similarly, you can run these commands sequentially for each log file that you want to apply to the MySQL Server.

Scheduling a Restore

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click the <Instance>, click All Tasks, and then click Browse and Restore.
  3. Click View Content.
  1. In the right pane of the Browse window, select a database to restore and click Recover All Selected.
  2. Select the required restore settings.
  3. Click the Job Initiation tab and click Schedule.
  4. Click Configure.
  5. From the Schedule Details dialog box, select the appropriate scheduling options and click OK.
  6. Click OK.

The restore job will start as per the schedule set.

Managing Restore Jobs

Once you initiate the restore operation, a restore job is generated in the Job Controller. Jobs can be managed in a number of ways. The following sections provide information on the different job management options available:

Restarting Jobs

Jobs that fail to complete successfully are restarted automatically based on the job restartability configuration set in the Control Panel. Changes made to this configuration affect all jobs in the entire CommCell.

To configure the job restartability for a specific job, you can modify the retry settings for the job. This overrides the setting in the Control Panel. In addition, you can override the default CommServe configuration for individual jobs by configuring retry settings when you initiate the job. This configuration, however, applies only to the specific job.

Configure Job Restartability at the CommServe Level

  1. From the CommCell Console toolbar, click Control Panel.
  2. Under the System section, click Job Management.
  3. Click Job Restarts tab and select a Job Type.
    • Select Restartable to make the job restartable.
    • You can change the value for Max Restarts to change the maximum number of times the Job Manager will try to restart a job.
    • You can change the value for Restart Interval (Mins) to change the time interval between attempts for the Job Manager to restart the job.
  4. Click OK.

Control Jobs

The following controls are available for running jobs in the Job Controller window:

Suspend Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time. Only preemptible jobs can be suspended.
Resume Resumes a job and returns the status to Waiting, Pending, Queued, or Running depending on the availability of resources or the state of the operation windows and activity control settings.

Restore jobs for this Agent are resumed from the beginning.

Kill Terminates a job.

These controls can be applied to:

  • All jobs in the Job Controller.
  • All selected jobs in the Job Controller providing you have the correct security associations at the proper level for each job selected.
  • All data protection operations running for a particular client or client/agent.
  • All data protection operations running for a particular MediaAgent.

Control a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Kill, Suspend, or Resume as desired.
    • When killing a job:

      Click Yes when the confirmation prompt appears if you are sure you want to kill the job. The job status may change to Kill Pending for a few moments while the operation completes. Once completed, the job status will change to Killed and it will be removed from the Job Controller window after five minutes.

    • When suspending a job:

      The job status may change to Suspend Pending for a few moments while the operation completes. The job status then changes to Suspended.

    • When resuming a job:

      As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.

Resubmitting Jobs

If a restore job fails to complete successfully, you can resubmit the job without the need to reconfigure the original job's restore options using the Resubmit Job feature. When a job is resubmitted, all the original options, restore destinations, and other settings configured for the job remain in tact.

Resubmit a Restore Job

  1. From the CommCell Browser, right-click a client computer whose data recovery history you want to view, click View, then click to view a job history.
  2. From the Job History Filter dialog box, select Restore.
    • If you want to view more advanced options for restores, from the Job History Filter, select Restore, then click Advanced.
    • From the Data Recovery History Advanced Filter select the destination client computer of the restores you would like to view, then click OK.
  3. The system displays the results of the options you selected in the Data Recovery Job History window.
  4. Right-click on any job, and select Resubmit.
  5. Select the job options.
  6. Click OK.

Additional Restore Options

Several additional options are available to further refine your restore operations. The following table describes these options, as well as the steps to implement them.

Be sure to read the overview material referenced for each feature prior to using them.

Option Description Related Topic
Startup Options

The Startup Options are used by the Job Manager to set priority for resource allocation. This is useful to give higher priority to certain jobs. You can set the priority as follows:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click the <Instance>, and then click All Tasks | Browse and Restore.
  3. In the Browse Restore Options dialog box, click View Content.
  4. In the right pane of the Browse window, select a database to restore, and then click Recover All Selected.
  5. In the MySql Restore dialog box, click Advanced.
  6. In the Advanced Restore Options dialog box, select the Startup tab.
  7. Select Change Priority.
  8. Enter a priority number where 0 is the highest priority and 999 is the lowest priority.
  9. Select the Start up in suspended State to start the job in a suspended state.
  10. Click OK.
Refer to Job Priority and Priority Precedence.
Copy Precedence By default, the system retrieves data from the storage policy copy with the lowest copy precedence. If the data was pruned from the primary copy, the system automatically retrieves data from the other copies of the storage policy in the lowest copy precedence to highest copy precedence order. Once the data is found, it is  retrieved, and no further copies are checked.

You can retrieve data from a specific storage policy copy (Synchronous Copy or Selective Copy). If data does not exist in the specified copy, the data retrieve operation fails even if the data exists in another copy of the same storage policy. Follow the steps given below to retrieve the data from a specific storage policy copy:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click the <Instance>, and then click All Tasks | Browse and Restore.
  3. In the Browse Restore Options dialog box, click View Content.
  4. In the right pane of the Browse window, select a database to restore, and then click Recover All Selected.
  5. In the MySql Restore dialog box, click Advanced.
  1. In the Advanced Restore Options dialog box, click Copy Precedence.
  2. On the Copy Precedence tab, select the Restore from copy precedence check box.
  3. Enter the copy precedence number.
  4. Click OK.
Refer to Recovering Data From Copies.
Data Path Options

Data Recovery operations use a specific data path (Library, MediaAgent, Drive Pool, and Drive) to perform the restore operations as configured in the CommCell. By default, the system automatically identifies the data path for the restore operations. You can change the data path at the restore level by selecting a specific MediaAgent, library, drive pool or drive in the Advanced Restore Options dialog.

The following are some of the important situations where you may need to change the data path:

  • To free heavily loaded resources such as MediaAgents and libraries.
  • A library suffers severe hardware damage and you need to move its media to a different library in order to access data secured by data protection operations.
  • A drive pool within a library is being used much more frequently than another, and a storage policy copy from the more active drive pool can be assigned to the less active one.
  1. From the CommCell Browser, click Client Computers | <agent> | <instance name>. The default and other subclients (if available) are displayed on the right-hand windowpane.
  2. From the CommCell Browser, right-click the instance that contains the data you want to restore. Click All Tasks and then click Browse Backup Data.
  3. From the Browse Options window, click OK.
  4. From the browse window, select the data to be restored and click Recover all Selected.
  5. From the Restore Options for All Selected Items dialog box, click Advanced.
  6. From the Advanced Restore Options (General) tab, select the MediaAgent and Library that you wish to perform the restore.
  7. Select the Drive Pool and Drive for tape library.
  8. Click OK.
Refer to Change Data Path.
Encryption

If the client's data is encrypted with a pass phrase, you must enter the pass-phrase to start the data recovery operation. Follow the steps given below to enter the pass-phrase:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
  2. Right-click the <Instance>, and then click All Tasks | Browse and Restore.
  3. In the Browse Restore Options dialog box, click View Content.
  4. In the right pane of the Browse window, select a database to restore, and then click Recover All Selected.
  5. In the MySql Restore dialog box, click Advanced.
  1. In the Advanced Restore Options dialog box, click Encryption.
  2. Enter the Pass Phrase.
  3. Click OK.
Refer to Data Encryption.
Alerts The Alert option is used for setting up the criteria to raise notifications/alerts for job statuses such as failure, success, or any other conditions triggered by the restore job. Adding alerts helps the user or the user group to get the notification automatically about the status of the restore job.
  1. From the CommCell Browser, click Client Computers | <agent> | <instance name>. The default and other subclients (if available) are displayed on the right-hand windowpane.
  2. From the CommCell Browser, right-click the instance that contains the data you want to restore. Click All Tasks and then click Browse Backup Data.
  3. From the Browse Options window, click OK.
  4. From the browse window, select the data to be restored and click Recover all Selected.
  5. From the Restore Options for All Selected Items dialog box, click Advanced.
  6. From the Advanced Restore Options (General) tab, click Add Alert.
  7. From the Add Alert Wizard window, select the Threshold and Notification Criteria. Click  Next.
  8. Select the Notification Types. Click  Next.
  9. Select the Users and User Groups. Click  Next.
  10. Verify the Summary.
  11. Click Finish.
Refer to Alerts and Notifications.
CommCell Readiness Report The CommCell Readiness Report provides you with vital information such as connectivity and readiness of the Client, MediaAgent, and CommServe. It is useful to run this report before performing a backup or a recovery operation. Follow the steps given below to generate the report:
  1. On the CommCell Console menu bar, select the Reports tab.
  2. Click Readiness.

    The Report Selection dialog box appears.

  3. If necessary, select Reports | CommServe | CommCell Readiness in the left pane.
  4. Select the Computers tab, and then click Modify below the Computers list.
  5. In the dialog box that appears, clear Include All Client Computers and All Client Groups.
  6. Select the appropriate client from the Exclude list, and then click Include >.
  7. Click OK.
  8. Select the MediaAgent tab, and then clear Include All MediaAgents.
  9. Select the appropriate MediaAgent from the Exclude list, and then click Include >.
  10. Click Run.

    The report appears in your default Web browser.

Refer to CommCell Readiness Report.
Restore Job Summary Report

The Restore Job Summary Report provides you with information about all the data recovery jobs that are run in last 24 hours for a specific client and agent. You can get information such as failure reason, failed objects, job options, and so on. It is useful to run this report after performing the restore. Follow the steps given below to generate the report:

  1. On the CommCell Console menu bar, select the Reports tab.
  2. Click Summary.

    The Report Selection dialog box appears.

  3. If necessary, select Reports | Jobs | Job Summary in the left pane.
  4. On the General tab, select Data Recovery Jobs.
  5. Select the Computers tab.
  6. Select the appropriate client and the appropriate agent.
  7. Click Run.

    The report appears in your default Web browser.

Refer to Restore Job Summary Report.