Configuring Data Protection for Microsoft SQL Server

Edit online

After you configure Data Protection for VMware and verify that you created a virtual machine backup that is suitable for recovery of a single Microsoft SQL Server database, configure Data Protection for Microsoft SQL Server in the guest virtual machine.

Procedure

  1. Log on to the virtual machine that hosts the Microsoft SQL Server database.
  2. Verify that the following packages are installed:
    • IBM Storage Protect recovery agent, recovery agent command-line interface (CLI), and license (from the Data Protection for VMware product package)
    • IBM Storage Protect data mover
    • Data Protection for Microsoft SQL Server
    You can install the recovery agent, CLI, license, and data mover together by using the Data Protection for VMware installation program. To install the packages together, select the following advanced installation option: Install a complete data mover for in-guest application protection. Data Protection for Microsoft SQL Server is installed separately.
  3. Configure Data Protection for Microsoft SQL Server by using the IBM Storage Protect configuration wizard. When you open the IBM Storage Protect Node Names page of the wizard, enter the VMware datacenter node name, Microsoft SQL Server node name, and VSS requestor node name. If the datacenter node name field is disabled, the recovery agent is not installed correctly.
  4. After Data Protection for Microsoft SQL Server is configured, verify that the Configuring Recovery Agent rule status indicates Passed.
  5. Log on to a data mover instance and complete the following steps.
    Do not repeat these steps for all data mover instances.
    1. Copy the contents of the data mover options file dsm.opt to a temporary file named dsm.setaccess.opt and make the following changes to the file. Do not make these changes in the dsm.opt file.
      1. Delete any line that contains an ASNODE entry.
      2. Set the NODENAME option to the VMware datacenter node name. For example: 
        NODENAME datacenter10
      Tip: If the dsm.opt file does not contain ASNODE entries and the NODENAME option is set to the correct datacenter node, you can use this file rather than creating the dsm.setaccess.opt file.
    2. From the datacenter node that was defined in the NODENAME option, issue the set access command to grant the VSS requestor node access to the virtual machine backups as shown in the following example.

      You must complete this step because the VSS requestor node accesses the virtual machine backups on behalf of Data Protection for Microsoft SQL Server.

      If the password for the datacenter node is unknown when you run the set access command, you will receive an error message and the IBM Storage Protect server administrator must reset the password to issue the command.

Example

The following example shows the required parameters for the set access command. The parameters specify the virtual machine name (vm_sql10), the VSS requestor node name (SQL10_VSS), and the name of the options file that defines the datacenter node name (dsm.setaccess.opt).

dsmc set access backup –type=VM vm_sql10 SQL10_VSS –optfile=dsm.setaccess.opt

ANS1148I Set Access command successfully completed.

The following example shows the results of the query access command, which shows the backup access authorization for the VSS requestor node.

dsmc query access
Node name: datacenter10
Type	  Node	  User	  Path
------	------	------	------
Backup       SQL10_VSS    * 	     \VMFULL-vm_sql10\*\*


ANS1148I Query Access command completed successfully