Configuring
You can use configuration wizards to configure Data Protection for SQL Server, or you can complete the steps manually. For best results, be guided by the step-by-step instructions in the configuration wizards
Before you begin
- Proxy node definitions for VSS backups
Because Data Protection for SQL Server use the Tivoli Storage Manager backup-archive client to implement VSS backup operations, you must use node names specifically for VSS operations. In addition, you must use a node name for where Data Protection for SQL Server is installed. - Specifying configuration parameters for Tivoli Storage Manager
After Data Protection for SQL Server is registered to Tivoli Storage Manager, you must configure the node name, password, the communications method, and the appropriate parameters to connect to the Tivoli Storage Manager server. - Specifying Data Protection for SQL Server node name parameters
You must register the system where Data Protection for SQL Server is installed to the Tivoli Storage Manager server with a node name. - Specifying configuration and options files in non-default locations
The Data Protection for SQL Server software uses default configuration and options files. If you want to use non-default configuration and options files, use command-line parameters to specify alternative configuration and option files when you start Data Protection for SQL Server. - Setting user preferences
Use the property pages in the Data Protection Properties window to customize Data Protection for SQL Server configuration preferences. - Configuring VSS operations in an SQL Server failover cluster environment
You can configureData Protection for SQL Server to protect VSS operations in a clustered SQL Server environment. - Configuring Tivoli Storage Manager policy to set automatic expiration and version control (VSS and legacy backups)
With Data Protection for SQL Server, you can use Tivoli Storage Manager policy to set automatic expiration and version control. - Configuring Data Protection for SQL Server by using the Tivoli Storage Manager Configuration Wizard
Configuration requirements for Data Protection for SQL Server, Tivoli Storage Manager, and other applications vary. The requirements depend on which Data Protection for SQL Server features you want to use. For example, if you plan to use VSS operations, the Tivoli Storage Manager backup-archive client, serving as the VSS Requestor, must also be installed and configured. - Configuring a remote system with a TSM Configuration
You can use a configuration wizard to configure a remote system to communicate with a Tivoli Storage Manager server. - Manually configuring Data Protection for SQL Server
For best results, use the configuration wizards to configure Data Protection for SQL Server. The wizards provide you with a step-by-step guide of the configuration requirements. However, if you prefer to do these steps manually, follow these configuration instructions. - Manually configuring Data Protection for SQL Server on Windows Server Core
You can manually configure Data Protection for SQL Server to protect your SQL Server 2012 and later versions on Windows Server Core. - Configuring Data Protection for SQL Server with Tivoli Storage Manager in a clustered environment
You can configure Data Protection for SQL Server to communicate with Tivoli Storage Manager, and protect SQL Server workloads in a clustered environment. - Configuring availability replicas to run scheduled data backups
When an availability database is replicated across multiple availability replicas in an availability group, a configuration option is available to enable you to select a single replica on which to run a backup operation instead of backing up all replicas. - Transitioning SQL Server backups from Tivoli Storage FlashCopy Manager to Tivoli Storage Manager
Configure Tivoli Storage FlashCopy® Manager so that you can access both a local and Tivoli Storage Manager at the same time. This might be useful if you decide to move to a Tivoli Storage Manager environment and want to continue to interact with the locally managed snapshots until policy marks them for expiration. - Transitioning standard SQL Server databases to the AlwaysOn node
You can back up standard SQL Server databases to the file space for the AlwaysOn node. This transition can make it easier for you to manage all your database backups under a single node name. - Examples ofIBM SAN Volume Controller and IBM Storwize V7000 configuration scenarios
Configuration examples are scenarios that you can use to help you plan your data backup and recovery solutions.