This section provides an example of how to use the Tivoli® Storage Manager scheduler with Data Protection for SQL Server to automate online backups of SQL Server
databases. This scenario illustrates the use of the Tivoli Storage
Manager scheduler and creating a full backup of
your SQL databases.
- Verify the latest Tivoli Storage
Manager backup-archive client version is
installed.
- Register Data Protection for SQL Server to a Tivoli Storage
Manager server and installed on the SQL Server.
- (SQL 2012 AlwaysOn Availability Groups and stand-alone database
only) Complete the following procedure to change the log on account.
By default, the domain account is not set. If you do not complete
this procedure, the scenario cannot be successfully completed because
a permission error occurs.
- Right click to select .
- Right click to select .
- Navigate to the Log on tab.
- Change Local System account to This
account. Enter the domain account information.
- Save the changes.
- On the Tivoli Storage
Manager server:
- Define a schedule to run a Windows command file. This
schedule must be defined in the policy domain to which Data Protection for SQL Server is registered.
- Associate the Data Protection for SQL Server node to the defined
schedule.
- On the system where the SQL Server and Data Protection for SQL Server are installed:
- Install the Tivoli Storage
Manager server scheduler client
as a Windows service for Data Protection for SQL. If a
scheduler exists for the regular Tivoli Storage Manager
backup client, install another one for Data Protection for SQL.
- Define a command file that contains the Data Protection for SQL commands to do the desired
backup. For more information about creating a Windows
command file, see the Windows documentation.
- If you are running in a SQL Server Failover Cluster environment:
- Install the Tivoli Storage
Manager server scheduler client
as a Windows service on both cluster nodes.
- Create a cluster resource that represents the Tivoli
Storage Manager scheduler. Verify that the cluster resource is started. This service is dependent on
the SQL Server cluster resource.
- Start the scheduler.