DP For MSSQL (AAG) - Installation Cookbook

© 2017 IBM Corporation
© Copyright International Business Machines Corporation 2017.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
2 © 2017 IBM Corporation

Preface
About this publication
This cookbook was created as a step-by-step guide for customers to quickly get started with IBM Spectrum Protect™ for
Databases: Data Protection for Microsoft SQL Server and to augment the official product documentation. It is not meant to
cover every aspect of the product but only to get the customer up and running as quickly as possible.
The document assumes that the customer is already knowledgeable about the IBM Spectrum Protect server.
Who should read this guide

This document is intended for system administrators who want to install and configure Data Protection for Microsoft
SQL Server for a clustered SQL server with an Always On Availability Group configuration that uses both local
Volume Shadow Copy Service (VSS) and earlier backup methods.
Before you begin

Ensure that Microsoft SQL server is installed, configured, and clustered with databases in an Always On Availability
Group.

Prerequisites

Prerequisites
For hardware and software requirements, see technote 1992314:

http://www.ibm.com/support/docview.wss?uid=swg21992314

Downloading Data Protection
for Microsoft SQL Server V8.1

Download information
▪ Packages must be downloaded from the Passport Advantage Online website:

https://www.ibm.com/software/passportadvantage/pao_customer.html
▪ Download information for IBM Spectrum Protect™ for Databases V8.1.0:
▪ Download information for IBM Spectrum Protect V8.1.0 clients:
▪ Download the following packages:
Image name Passport Advantage Operating system

part number
IBM Spectrum Protect for Databases V8.1.0: CNFN3ML Windows x64
Data Protection for Microsoft SQL Server
IBM Spectrum Protect client V8.1.0 (Windows) CNFN2ML Windows x64

Configuring
the IBM Spectrum Protect
Server

IBM Spectrum Protect configuration
1. Define the domain for all Microsoft SQL data:
tsm: SERVER1>define domain sql
ANR1500I Policy domain SQL defined.
tsm: SERVER1>
2. Define policy:
tsm: SERVER1>define policy sql sql_pol
ANR1510I Policy set SQL_POL defined in policy domain SQL.
tsm: SERVER1>
3. Define the management class:

tsm: SERVER1>define mgmt sql sql_pol sql_mgmt
ANR1520I Management class SQL_MGMTCLASS defined in policy domain SQL, set SQL_POL.
tsm: SERVER1>
4. Ensure that you have defined one or more storage pools. For an overview of storage pool types and instructions about
using the command line to define storage pools, see DEFINE STGPOOL. To use the Operations Center to define storage
pools, follow the instructions in Configuring storage.
5. Define the copy group:

tsm: SERVER1>define copygroup sql sql_pol sql_mgmt dest=backuppool vere=nolimit verd=nolimit rete=30 reto=60
ANR1530I Backup copy group STANDARD defined in policy domain SQL, set SQL_POL, management class SQL_MGMTCLASS.
tsm: SERVER1>

IBM Spectrum Protect configuration
5. Assign a default management class:
tsm: SERVER1>assign defmg sql sql_pol sql_mgmt
ANR1538I Default management class set to SQL_MGMT for poliy domain SQL, set SQL_POL.
tsm: SERVER1>
6. Activate policy:
tsm: SERVER1>activate policy sql sql_pol
ANR1554W DEFAULT Management class SQL_MGMTCLASS in policy set SQL SQL_POL does not have an ARCHIVE copygroup:
files will not be archived by default if this set is activated.
Do you wish to proceed? (Yes (Y)/No (No)) y
ANR1554W DEFAULT Management class SQL_MGMTCLASS in policy set SQL SQL_POL does not have an ARCHIVE copygroup:
files will not be archived by default if this set is activated.
ANR1514I Policy set SQL_POL activated in policy domain SQL.
tsm: SERVER1>
Tip: The VSS Requestor, Data Protection for SQL, and the Always On node are registered on the IBM Spectrum Protect server along with their proxy
relationships in a subsequent step. This is done by using a macro during the Data Protect for SQL configuration:
➢ The VSS Requestor node is the node that communicates with the VSS service to access the SQL server data. (In this document, we use SQLNODE1.)
➢ The Data Protection for SQL node is the node that is used to store the Data Protection for SQL backups of databases that are not part of the Always On
Availability Group. (In this document, we use SQLNODE1_SQL.)
➢ The Always ON node is used when availability databases are backed up in an Always On Availability Group. (In this document, w e use SQLCLUSTER.)

Installing the IBM Spectrum
Protect Client

IBM Spectrum Protect client installation
The IBM Spectrum Protect client must be installed on all SQL servers in the cluster. In this document,
we use the following nodes: SQLNODE1 and SQLNODE2.
1. Right-click the spinstall.exe file,

run the program as the administrator, and
click OK.
2. Click Install.
If you are prompted to do so,
restart the computer.

3. Click Next.

4. Click Next.

5. Select the Custom setup type

and click Next.

6. Select the Administrative Client Command Line

Files to be installed option and click Next.

IBM Spectrum Protect Client Installation
7. Click Install.

IBM Spectrum Protect Client Installation
8. Click Finish.

Installing Data Protection
for Microsoft SQL Server

Installation
Data Protection for Microsoft SQL Server must be installed on all SQL servers in the cluster. In this
document, the following nodes are used: SQLNODE1 and SQLNODE2.
1. Right-click the SetupFCM.exe file

and run it as administrator.
2. Click OK.

Installation
3. Click Install.
If you are prompted to do so,
restart the computer.

Installation
4. Click Next.

Installation
5. Accept the terms in the license agreement and click Next.

Installation
6. Click Next.

Installation
7. Click Install.

Installation
8. Click Finish.

Configuring Data Protection
for Microsoft SQL Server

Data Protection for SQL Server configuration
1. Launch the Data Protection for SQL Management Console. If

you did not previously configure Data Protection for SQL, the IBM
Spectrum Protect Configuration Wizard starts automatically.
Requirement: If you upgraded to V8.1, the IBM Spectrum Protect

Configuration Wizard might not start automatically. You must run
the wizard again (even if you do not change any of the
configurations). This step is necessary to ensure that the newly
installed files are copied to the appropriate directories.

2. Select the SQL Server application

and click Next.

3. After the requirements check is complete, take action on any outstanding items.
(In this example, the VSS Hardware provider is not installed. Therefore, warnings
about VSS Providers can be ignored.)
4. Click Next.

5. Click Next.

6. Enter the IBM Spectrum Protect server address (DNS name or IP address) and port
(default: 1500) and click Yes to configure the IBM Spectrum Protect server.
7. Enter the IBM Spectrum Protect administrator credentials.
8. To modify the macro, click Review/Edit.
This macro is for the first node in the cluster, SQLNODE1. This macro is for the second node in the cluster, SQLNODE2.
9. Modify the macro to match the samples and click OK.

10. Click Next.

Data Protection for SQL Server Configuration
11. Click Next.

12. To monitor the configuration process, click Show Details. Ensure that the
configuration status is Passed for all items and click Next.
13. Ensure that the Run VSS diagnostics when this wizard exits box is selected
and click Finish.
Tip: If VSS backups exist, this process deletes all of them.
14. Select the volumes that you would like to test and click Next.

15. Click Yes.

16. Ensure that a test status of Passed is displayed for all items
and click Next.
17. Click Finish.

18. On the Data Protection for SQL console GUI, right-click the SQL server
and click Properties.

19. Confirm that the fields in the Server Connection Information

section are populated.
20. In the left pane, click SQL Login, select the appropriate authentication method, and click Apply.
Tip: The preferred method is to create a Windows Domain User account as a service account that has full access to
the SQL server (and is a member of the sysadmin group) to perform backup and restore functions.
21. In the left pane, click General and specify the name of the SQL server if it is not the default instance.
VSS backup is set as the default backup method.
22. If you prefer to use the previous backup method as default, clear the Use VSS backup as the default
backup method check box.
Requirement: When using a named instance, you must specify local-computername\instance.
23. Validate the scheduled backup preferences. To edit the preferences, click the drop-down arrow, select the
appropriate preferred replica backup preference, and click Apply.
24. Verify that Data Protection for SQL is configured properly. Click the Automate tab
and select the Command Line option.
25. In the command line pane, type query tsm and click the red check mark to execute
the command. Ensure that you see rc=0.

26. In the command line pane, type query tdp and click the red check mark
to execute the command. Ensure that you see rc=0.

27. In the command line pane, type query sql and click the red check mark
to execute the command. Ensure that you see rc=0.

Backing up the SQL Server
by Using the GUI

Backing up the SQL Server by using the GUI
To back up a single availability database or multiple availability databases, complete the

following steps:
1. Click the SQL Server.

2. Ensure that the Protect tab is selected.
3. To view the availability databases, click the Standard Databases toggle button.
4. Select a single database or multiple databases.
5. Select Legacy Backup Method.
Tip: The default value is VSS.
6. To start the backup operation, click Full Backup.

When you start a backup operation by using the GUI, you can run the operation on either
the primary or secondary node. Ideally, run the backup operation on the secondary node in the cluster.
Tip: In the example, you see that the WideWorldImporters database on the secondary replica
is in a sync state of synchronized.

On the Task List tab, monitor the backup progress until the State column displays
Completed and the Result column displays Succeeded.
Restoring the SQL Database
by Using the GUI

Restoring the SQL database by using the GUI
You can restore a single database or multiple databases (including those in an Always On
Availability Group) to the original location.
Before you begin
Ensure that any databases that you plan to restore no longer exist.
Procedure

2. Ensure that the Recover tab is selected.
3. To display the active and inactive backups that are available for the restore process, click
Active Backups.
4. Select a single database or multiple databases.
5. To immediately initiate the restore process, click Restore.


To restore a single database or multiple databases to an alternate location, complete the

following steps:

2. Ensure that the Recover tab is selected.
3. To display the active and inactive backups that are available for the restore process, click
Active Backups. Select a single database or multiple databases.
4. Click Restore to Alternate Location.
5. Complete the required fields for the new database.
6. Complete the required fields for relocation.
7. Click Restore.


8. Ensure that the directory

paths exist.
Tip: Database Recovery is

set to Yes by default.

Scheduling Data Protection
for SQL Backup Operations by
Using the GUI
(Option 1)

Scheduling Data Protection for SQL backup operations by using the GUI
1. Take one of the following actions:

• Right-click Scheduling and click Scheduling Wizard.
• From the Actions pane on the right, start the Scheduling Wizard.
2. In the Name field, enter a meaningful name for the schedule and click Next.

3. Define the frequency of backups, provide credentials, and click Next.

The preferred method is to use a Windows Domain User account to manage
the scheduler. The account must have full access rights to the SQL server
64
and be a member of the sysadmin group. © 2017 IBM Corporation
4. Define the scheduled task by taking one of the following actions:

- Use the Windows PowerShell framework:
A. Click the PowerShell tab.
B. Click the SQL Server icon.
C. Modify the sample script.
D. Click Next.
- Use the command line:

A. Click the Command Line tab.
B. Click the SQL Server icon.
C. Modify the sample script.
D. Click Next.
5. In the Summary window, review the summary. Then,

click Finish and OK.
This process creates a Windows Task Schedule, not an
IBM Spectrum Protect schedule.
Configuring the Client Scheduler
Service for Data Protection
for SQL Backups

Configuring the client scheduler service
1. Confirm the entries in the dsm.opt file in the C:\Program Files\Tivoli\TSM\TDPSql directory on the
SQLNODE1 and SQLNODE2 nodes as follows:
NODENAME SQLNODE1_SQL  Your SQL node name
PASSWORDACCESS GENERATE
TCPSERVERADDRESS CSIPDC  ensure that you specify the correct IBM Spectrum Protect server
TCPPort 1500
HTTPport 1581
CLUSTERnode yes
2. Install the IBM Spectrum Protect Scheduler Service on each node in the cluster by issuing the following
command:
C:\Program Files\Tivoli\TSM\baclient>dsmcutil install sched /name:”SP Client Scheduler - SQL” /optfile:”C:\Program
Files\Tivoli\TSM\TDPSql\dsm.opt” /autostart:yes /node:sqlnode1_sql /password:T_3_m_p_P_w /errorlog:”C:\Program
Files\Tivoli\TSM\TDPSql\dsmerror_sql.log” /schedlog:”C:\Program Files\Tivoli\TSM\TDPSql\dsmsched_sql.log”
/startnow:yes /ntaccount:Administrator /ntdomain:CSI /ntpassword:xxxxxxxxx
Requirement: Ensure that you modify the /node value accordingly for sqlnode2_sql.
Tip: The previous example assumes that the user is defined in Active Directory (CSI\Administrator), which has sysadmin rights in SQL.
For this reason, the values /ntaccount:Administrator and /ntdomain:CSI are used.

Configuring the client scheduler service
3. Validate that the client scheduler service was installed by issuing the following command:
C:\Program Files\Tivoli\TSM\baclient>dsmcutil list C:\Program Files\Tivoli\TSM\baclient>dsmcutil list
TSM Windows NT Client Service Configuration Utility TSM Windows NT Client Service Configuration Utility
Command Line Interface – Version 8, Release 1, Level 0.0 Command Line Interface – Version 8, Release 1, Level 0.0
(C) Copyright IBM Corporation, 1990, 2016, All rights (C) Copyright IBM Corporation, 1990, 2016, All rights
Reserved. Reserved.
Last Updated Nov 11 2016 Last Updated Nov 11 2016
TSM Api Version 8.1.0 TSM Api Version 8.1.0
Command: List Installed TSM Client Services Command: List Installed TSM Client Services
Machine: SQLNODE1(Local Machine) Machine: SQLNODE2(Local Machine)
Installed TSM Client Services: Installed TSM Client Services:
1. SP Client Scheduler – SQL 1. SP Client Scheduler – SQL
1 TSM Client Service was located. 1 TSM Client Service was located.
C:\Program Files\Tivoli\TSM\baclient> C:\Program Files\Tivoli\TSM\baclient>

Configuring a Data Protection for SQL
Backup Schedule
on an IBM Spectrum Protect Server
(Option 2)

Configuring a Data Protection for SQL backup schedule on an IBM Spectrum Protect server
1. To create a SQL full backup script, leverage a sample script. On the Microsoft SQL server,
double-click the sqlfull.smp file by using the WordPad program. The file is located in the
C:\Program Files\Tivoli\TSM\TDPSql directory.
2. Create a Windows Command Script by clicking Save as and typing sqlfull.cmd.
3. Edit the sqlfull.cmd file and modify the following line:
%sql_dir%\tdpsqlc backup * full /tsmoptfile=%sql_dir%\srvrname.opt /logfile=%sql_dir%\sqlfull.og >>

%sql_dir%\sqlsched.log
Change the line as shown:
%sql_dir%\tdpsqlc backup * full /alwaysonpriority /backupmethod=legacy
/tsmoptfile=%sql_dir%\dsm.opt /logfile=%sql_dir%\sqlfull.og >> %sql_dir%\sqlsched.log
4. Define the client schedule on the IBM Spectrum Protect server that will execute the command
script:
tsm: SERVER1>define schedule sql sql_backup action=command
objects=”C:\PROGRA~1\Tivoli\TSM\TDPSql\sqlfull.cmd” start=12:00
ANR2500I Schedule SQL_BACKUP defined in policy domain SQL.
tsm: SERVER1>
5. Associate the client with the newly created schedule:

tsm: SERVER1>define association sql sql_backup sqlnode1
ANR2510I Node SQLNODE1 associated with schedule SQL_BACKUP in policy domain SQL.
tsm: SERVER1>

6. On each Microsoft SQL server, restart the SP Client Scheduler – SQL service:

7. On the Microsoft SQL server, view the following file:

C:\Program Files\Tivoli\TSM\TDPSql\dsmsched_sql.log
The content should be similar to the example.

8. After the backup operation is complete, view the following file:

C:\Program Files\Tivoli\TSM\TDPSql\dsmsched_sql.log
The content should be similar to the example.

9. Optionally, you can view more detailed information about the backup operation in the C:\Program
Files\Tivoli\TSM\TDPSql\sqlsched.log file. The content should look similar to the example.

Command Line Syntax

Full backup TDPSQLC Backup *|dbname[,dbname,...] [Full]
[/ADJUSTKBtsmestimate=adjustmentinkb]
(default: 0)
[/ADJUSTPERcenttsmestimate=adjustmentinpercent]
(default: 0)
[/ALWAYSONNode=nodename] (default: Windows Cluster Name)
[/ALWAYSONPriority]
[/EXCLUDEALwaysondbs]
[/EXCLUDESTandarddbs]
[/AAGName=availabilitygroupname]
[/BACKUPDESTination=TSM]
[/BACKUPMETHod=LEGACY|VSS] (default: LEGACY)
[/BUFFers=numbuffers] (default: 3)
[/BUFFERSIze=buffersizeinkb] (default: 1024)
[/CONFIGfile=configfilename] (default: tdpsql.cfg)
[/EXCLUDEDB=dblist]
[/SQLCOMPression=Yes|No] (default: No)
[/SQLCHECKSum=Yes|No] (default: No)
[/LOGFile=logfilename] (default: tdpsql.log)
[/LOGPrune=numdays|No] (default: 60)
[/MOUNTWait=Yes|No] (default: Yes)
[/Quiet]
[/SQLAUTHentication=INTegrated|SQLuserid]
(default: INTegrated)
[/SQLBUFFers=numsqlbuffers] (default: 0)
[/SQLBUFFERSIze=sqlbuffersizeinkb] (default: 1024)
[/SQLPassword=sqlpasswordname] (default: " ")
[/SQLSERVer=[sqlprotocol:]sqlservername]
(default: local computer name)
(default sqlprotocol: "")
[/SQLUSer=sqlusername] (default: sa)
[/STRIPes=numstripes] (default: 1)
[/TSMNODe=tsmnodename] (default: dsm.opt value)
[/TSMOPTFile=dsmoptfilename] (default: dsm.opt)
[/TSMPassword=tsmpassword] (default: dsm.opt valu)e
79 [/USEALWAYSONnode] © 2017 IBM Corporation
Differential (Difffull) backup
TDPSQLC Backup *|dbname[,dbname,...] Difffull
(default: 0)
(default: 0)
[/ALWAYSONPriority]
[/DIFFESTimate=numpercent] (default: 20)
[/EXCLUDEDB=dblist]
[/Quiet]
[/TSMPassword=tsmpassword] (default: dsm.opt value)
[/USEALWAYSONnode]
Copy-only full (COPYFull) backup
TDPSQLC Backup *|dbname[,dbname,...] COPYFull

(default: 0)
(default: 0)
[/ALWAYSONPriority]
[/BACKUPDESTination=TSM|LOCAL|BOTH](default: TSM)
[/BACKUPMETHod=LEGACY|VSS] (default: LEGACY)
[/EXCLUDEDB=dblist]
[/TSMPassword=tsmpassword] (default: dsm.opt valu)e
[/USEALWAYSONnode]

Log backup
TDPSQLC Backup *|dbname[,dbname,...] Log
(default: 0)
(default: 0)
[/ALWAYSONPriority]
[/EXCLUDEDB=dblist]
[/LOGESTimate=numpercent] (default: 0)
[/BACKUPTAILLOG]
[/Quiet]
[/TRUNCate=Yes|No] (default: Yes)
[/TSMPassword=tsmpassword] (default: dsm.opt value)
[/USEALWAYSONnode]
Notices
© 2017 IBM Corporation

This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or
product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available
in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM® product,
program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send
license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the informati on herein; these changes will be incorporated in new editions of the
publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not
part of the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License
Agreement or any equivalent agreement between us.
The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies,
brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample
programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function
of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might
be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe is a registered trademark of Adobe Systems Incorporated in the United States, and/or other countries.
Linear Tape-Open, LTO, and Ultrium are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
SoftLayer® is a registered trademark of SoftLayer, Inc., an IBM Company.
UNIX is a registered trademark of The Open Group in the United States and other countries.

DP For MSSQL (AAG) - Installation Cookbook

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DP For MSSQL (AAG) - Installation Cookbook

Uploaded by

Copyright:

Available Formats

© 2017 IBM Corporation

© Copyright International Business Machines Corporation 2017.

2 © 2017 IBM Corporation

Who should read this guide

Before you begin

3 © 2017 IBM Corporation

4 © 2017 IBM Corporation

For hardware and software requirements, see technote 1992314:

5 © 2017 IBM Corporation

6 © 2017 IBM Corporation

▪ Packages must be downloaded from the Passport Advantage Online website:

Image name Passport Advantage Operating system

7 © 2017 IBM Corporation

8 © 2017 IBM Corporation

3. Define the management class:

5. Define the copy group:

9 © 2017 IBM Corporation

10 © 2017 IBM Corporation

11 © 2017 IBM Corporation

1. Right-click the spinstall.exe file,

12 © 2017 IBM Corporation

13 © 2017 IBM Corporation

14 © 2017 IBM Corporation

5. Select the Custom setup type

15 © 2017 IBM Corporation

6. Select the Administrative Client Command Line

16 © 2017 IBM Corporation

17 © 2017 IBM Corporation

18 © 2017 IBM Corporation

19 © 2017 IBM Corporation

1. Right-click the SetupFCM.exe file

20 © 2017 IBM Corporation

21 © 2017 IBM Corporation

22 © 2017 IBM Corporation

5. Accept the terms in the license agreement and click Next.

23 © 2017 IBM Corporation

24 © 2017 IBM Corporation

25 © 2017 IBM Corporation

26 © 2017 IBM Corporation

27 © 2017 IBM Corporation

1. Launch the Data Protection for SQL Management Console. If

Requirement: If you upgraded to V8.1, the IBM Spectrum Protect

28 © 2017 IBM Corporation

2. Select the SQL Server application

29 © 2017 IBM Corporation

30 © 2017 IBM Corporation

31 © 2017 IBM Corporation

9. Modify the macro to match the samples and click OK.

33 © 2017 IBM Corporation

10. Click Next.

34 © 2017 IBM Corporation

11. Click Next.

38 © 2017 IBM Corporation

15. Click Yes.

39 © 2017 IBM Corporation

17. Click Finish.

41 © 2017 IBM Corporation

42 © 2017 IBM Corporation

19. Confirm that the fields in the Server Connection Information

48 © 2017 IBM Corporation

49 © 2017 IBM Corporation

50 © 2017 IBM Corporation

51 © 2017 IBM Corporation