V11 SP8
Loading...

IntelliSnap - Advanced Configuration - SQL Server iDataAgent

Table of Contents

Configuring Multiple Streams for Operation

Multiple streaming employs multiple data streams per subclient for data protection operations. This enables the subclient's contents to be distributed to all the streams, transmitting them in parallel to the storage media. Hence a subclient whose data is secured using these data streams, utilizes more of the available network resources, and can complete in as little as one third the time that the same data would require using a single stream.

Follow the steps given below to configure multi-streaming.

  1. From the CommCell Browser, navigate to Client Computers | <Client> | SQL Server | <Instance>.
  2. Right-click the <Subclient> in the right pane and click Properties.
  3. Select the Allow multiple data readers for Backup Copy check box.
  4. Click the Storage Device tab.
  5. In the Storage Policy list, click a storage policy name.
  6. In the Number of Streams for Data Backup box type or select the number of data streams.
  7. Click OK

Configuring Multiple Streams for Restore Operation

While running a restore operation from an IntelliSnap backup copy, you can increase the speed of restore by increasing the number of streams to a number greater than one. This enables the files to be distributed to all the streams, transmitting them in parallel to the destination location. Hence the restore operation running on multiple streams utilizes more of the available network resources, and can complete in a lesser time than it would require using a single stream.

By default, the number of streams is increased to two. You can further increase the number of streams depending on the number of files that you have to restore. If the number of files that you are restoring is more than the number of streams used for restore, files are distributed between streams according to the file size to ensure balanced load during restore.

Procedure

The following is a high-level process for configuring multiple streams for a restore operation:

  1. To enable multiple streaming during restore operation, on the CommServe computer, add the global parameters as mentioned below:
    Name Category Value Mandatory/Optional Description
    bEnableSQLSnapRestoreStreams CommServDB.GxGlobalParam Non-zero number Mandatory to enable multiple streams for restore operation Enables multiple streaming during restore operation from a backup copy.

    By default, the number of streams is increased to two.

    bEnableSQLSnapRestoreStreams CommServDB.Console True Optional Enables the option to increase the number of streams from the CommCell Console.

    For steps on adding these global parameters from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

  2. To increase the number of streams to a number greater than two, on the client computer, add the additional setting as mentioned below:
    Name Category Value Mandatory/Optional Description
    setStreamsRestore MSSQLAgent Number of streams to be used during the restore operation. Optional Increases the number of streams to a number greater than two.

    For steps on adding the additional setting from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

  3. Optional: After enabling the global parameter bEnableSQLSnapRestoreStreams in CommServDB.Console category, you can set the number of streams each time you run a restore operation from the CommCell Console. From the SQL Restore Options dialog box, select a value for the Number of streams to use for restore box, and then click OK.

Configuring Clone Environment for the Database

You can duplicate the source database by cloning the NetApp, Nimble, Pure Storage, and VMAX snapshots created during backup. This operation, referred as cloning, utilizes the cloning capability of the storage array hardware, which enables you to duplicate large databases within a short period of time. Clones can be used for multiple purposes, such as:

  • As test environments to troubleshoot issues found in the production database.
  • Quick data retrieval without running resource intensive restores on the production environment and without requiring additional space on destination server.
  • Alleviate load from the production servers for running reports and queries.

A clone can be created from any full backup. During the clone creation, a reservation period can be specified by the user. At the end of the reservation period, the system automatically shut downs the clone database and frees up all resources. The cloning operation can also be scheduled to run periodically to allow the clones to get refreshed from the latest backups on a regular basis.

The databases can be cloned to the same instance or to a different instance. Follow the steps given below to create a clone environment from existing snapshots:

  1. From the CommCell Browser navigate to the SQL iDataAgent | Instance.
  2. Right-click the <Subclient>, and click Backup History.
  3. Click OK.
  4. Right-click an existing <Full Backup> and click Clone.
  5. Click View Content.
  6. Select <Database> to be cloned and click Clone.
  7. Select a Destination Server from the available list.

    Ensure that the destination server has access to the storage array containing the source database volumes.

  8. Browse and select a Common Mount Path, to mount the snapshot.

    The database of the mounted snapshot will be attached to SQL server.

  9. Click the Clone Options tab, and set the Reservation Period for the clone. The clone will be retained for the time specified here. By default the clone will be retained for one hour.

    Once the reservation period ends, the database will be dismounted from SQL server and the mount point will be deleted. For more information, see Frequently Asked Questions - IntelliSnap Backup - SQL.

  10. Click OK.

You can also create and manage clones from the Web Console. For more information, see Manage Databases - Web Console.

Configuring to Perform IntelliSnap Integrity Check

You can configure to run integrity check of a hardware snap during an IntelliSnap backup. The check verifies the integrity of the captured data files by mounting them to a proxy, attaching and detaching the database to the SQL Server.

Use the proxy server to perform integrity check on a SQL cluster. A proxy is a separate computer with connectivity to the SQL Server and with the ability to mount the snapshots. Ensure that the proxy to be selected for running integrity check has MediaAgent and SQL iDataAgent installed on it.

Follow the steps given below to configure and run the Integrity check:

  1. From the CommCell Browser navigate to the SQL iDataAgent | Instance.
  2. Right-Click the <Subclient> and click Properties.
  3. On the IntelliSnap Operations tab select Proxy for SQL Integrity Check.
  4. From the Use Proxy list, select a proxy that has the same or higher SQL server version as that of source.
  5. Enter the SQL Server Name to connect to a specific SQL instance during integrity check.
  6. Enter the User Name and Password to establish connection with the SQL server.
  7. Click OK.
  8. Right-click the <Subclient> and click Backup.
  9. Click Full as backup type and then click Immediate.
  10. Click the Advanced button and select Perform Snap Integrity Check.
  11. Click OK.
  12. Click OK to run backup.

If Integrity Check succeeds IntelliSnap backup job will return a successful Event Viewer message "SQL integrity check completed successfully for job [id]"

Configuring to Disable Logical and Physical Integrity Check of All Database Objects

By default, during Snap Integrity Check the logical and the physical integrity of all database objects will be checked. However, you can use additional settings to set bRunDBCCCheckForDB to disable logical and physical integrity check on all database objects.

To add or edit an additional setting, follow the steps in Add or Modify an Additional Setting.

Use these arguments:

  • In the Name box, type bRunDBCCCheckForDB. The Category and Type details will be automatically populated.

    A global parameter RunDBCCCheckForDB can be used to configure all SQL clients. You can use the Command Line Interface to do so, see qcommand execscript for details.

  • In the Value field, type 0.