Configuring the computer that runs the SQL Server

Edit online

Run these steps on the computer where the SQL Server is installed and running.

Before you begin

Before you begin, ensure that the SQL Server is running.

If you configure the DSM Agent node (the backup-archive client node) manually, ensure that you set the PASSWORDAccess option to generate in the dsm.opt file for the IBM Storage® Protect backup-archive client. Also ensure that the stored password for the DSMAGENT Node is valid.

Procedure

  1. Specify your Data Protection for SQL Server node name and communication method in the dsm.opt file that is located by default in the Data Protection for SQL Server installation directory.
  2. Using the set command, specify your Data Protection for SQL Server preferences (date format, log file) in the tdpsql.cfg file in the Data Protection for SQL Server installation directory.
  3. If you are configuring Data Protection for SQL Server with SQL Server 2012 and later versions, specify the IBM Storage Protect node name that is used to back up the AlwaysOn availability databases. You can specify the AlwaysOn node name by using the alwaysonnode option in the tdpsql.cfg file. For example: 
    set alwaysonnode myAlwaysOnNode
    All availability databases in an availability group are backed up under this node name. Any stand-alone databases are backed up under the standard Data Protection for SQL Server node name.
  4. For SQL Server 2012 and later versions: If you want all databases to be backed up by default under the AlwaysOn node, specify the usealwaysonnode option in the tdpsql.cfg file. For example:
    usealwaysonnode yes
    This option is useful if you change your database backups from the standard Data Protection for SQL Server node to an AlwaysOn node.
  5. (VSS only) Specify your VSSPOLICY statement in your Data Protection for SQL Server configuration file.
    Exchange servers that use the same DAG node name must share the VSS Policy.
  6. (VSS only) Configure the IBM Storage Protect backup-archive client if it is not already configured. If the backup-archive client is already configured, you can use existing client services. The backup-archive client Setup Wizard can guide you through the configuration process. In the backup-archive client GUI menu, select Utilities > Setup Wizard > Help me configure the IBM Storage Protect Backup Archive Client. The node name for this system is referred to as the Local DSMAGENT Node and is specified with the localdsmagentnode parameter in the Data Protection for SQL Server configuration file (tdpexc.cfgtdpsql.cfg).

    For more information about installing the IBM Storage Protect backup-archive client for Windows™, see Install the UNIX™ and Linux™ backup-archive clients .

  7. (VSS only) Install and configure the IBM Storage Protect Client Acceptor Service (CAD) if it is not already installed and configured. In the backup-archive client GUI menu, select Utilities > Setup Wizard > Help me configure the IBM Storage Protect Web Client. Make sure that the CAD service is running before you proceed to the next step.
  8. (VSS only) Install and configure the IBM Storage Protect Remote Client Agent Service (DSMAGENT) if it is not already installed and configured. In the backup-archive client GUI menu, select Utilities > Setup Wizard > Help me configure the IBM Storage Protect Web Client. If a DSMAGENT is already installed and configured, you can use the existing one.
  9. (VSS only) Install IBM Storage Protect Snapshot if you want to manage local persistent VSS snapshots, which are created for VSS backups to LOCAL, VSS Instant Restores, and you want to run offloaded backups.
  10. (VSS only) Install and configure a VSS provider. Consult the VSS provider documentation for information about configuration of that software. You do not need to install and configure any components if you use the default Windows VSS System Provider.
  11. (VSS only) Change the SQL Server VSS Writer from Manual to Automatic and start the service.
  12. (VSS only) Define storage space to hold VSS backups that is on local shadow volumes. Define enough space to store all copies of the VSS backups as designated by your policies. Provisioning storage space to manage VSS snapshots depends on the VSS provider that you use. Consult the VSS Provider documentation for more details.