Protecting SQL Server data
With IBM Storage Protect Snapshot for SQL Server, you can back up and restore Microsoft SQL Server databases in a stand-alone configuration.
- Prerequisites With IBM Storage Protect Snapshot, you can back up and restore SQL Server data and protect your SQL Server environment.
-
Verifying the integrity of legacy databases by using the checksum option
With IBM Storage Protect Snapshot, you can verify the integrity of legacy database backups by setting a checksum option.
-
Creating VSS backups of SQL Server databases
You can back up standard SQL Server databases or availability databases by using Microsoft Volume Shadow Copy Service (VSS).
-
Creating legacy backups of SQL Server databases
You can create a legacy backup of your standard SQL databases by using Microsoft Management Console (MMC). You can also use the legacy method to back up availability databases with SQL Server 2012 and later versions.
-
Cloning an SQL Server database
Clone standard SQL Server production databases or availability databases by using Microsoft Volume Shadow Copy Service (VSS) and Windows PowerShell cmdlets. You can create a persistent VSS snapshot of the production database at any time. This snapshot is a clone of the production database. Use this clone to complete database activities you would normally do on the production database without impacting the production database. Use Windows PowerShell cmdlets to query the cloned database, and to mount and unmount it on remote servers.
-
You can remove an SQL Server backup that you created with the VSS backup method. Complete this task only if necessary.
-
Deactivating legacy backups of SQL Server databases
IBM Storage Protect deactivates an SQL database backup as a part of IBM Storage Protect policy management. Data backups are typically deactivated when an SQL database is deleted from the SQL Server as part of the scheduled backup processing.
-
Setting single-user mode for restore operations
You might have to start an SQL Server instance in single-user mode during certain restore operations. For example, you might use single-user mode when you are restoring a damaged master database or a system database, or when you are changing server configuration options.
-
To optimize the data restore process for your environment, modify the default options that are available in Microsoft Management Console (MMC).
-
You can restore SQL Server databases or parts of databases only from
full,copyfull,differential, andlogbackups. You can also restore availability databases with SQL Server 2012 and later versions. -
Restoring an SQL Server database to an alternate instance
Using Microsoft Management Console (MMC), you can restore an SQL Server database backup to an alternate SQL Server instance or database. You can also restore availability databases to an alternate location on any availability replica in an availability group. Restore to an alternate instance by using Microsoft Management Console (MMC), Windows PowerShell cmdlets, or the command-line interface (CLI).
-
A damaged master database can prevent the SQL Server from starting and cause other errors. To protect your data if the master database is damaged, you must routinely complete a full database backup of the master database (msdb).
-
Restoring SQL databases with full-text catalogs and indexes
You can restore SQL Server 2005 and 2008 databases, including their full-text catalogs and full-text indexes.
-
Protecting SQL Server data in a Windows Server Core environment
Server Core is a minimal and low-maintenance server environment where you can run the minimum services that are necessary to maintain Windows Server 2008 and later versions. You can install and operate IBM Storage Protect Snapshot in this minimal server environment.