Creating legacy backups of SQL databases

You can create a legacy backup of your standard SQL databases by using the Microsoft Management Console (MMC). You can also use the legacy method to back up availability databases with SQL Server 2012 and later versions.

1. Start the MMC.
2. Select the SQL Server instance in the tree view.
3. On the Protect tab of the SQL instance, specify the type of SQL data to back up by browsing to and selecting the databases to back up.

   Table 1. Database backup views

   Option	Action
   For a list of discovered SQL databases that are available to back up:	Click View: Databases.
   For a list of discovered SQL Server 2012 and later version availability databases that are available to back up:	Click Standard Databases. Information about the availability databases in an availability group is displayed, including the replica role, synchronization state, and space and log usage. Toggle the Standard Databases / Availability Databases button for the respective database views.

   Refine the list of available databases in the results pane by entering a keyword in the Search field.

4. Verify the backup options. If the backup options are not displayed, click Show Backup Options.

   Table 2. Database backup options

   Option	Action
   Data Stripes	Use this option to specify the number of data stripes to use in a backup or restore operation. The numstripes variable can be in the range 1 - 64. The default value is 1.
   Estimated Database % Change	Use this option to specify the estimated fraction of the database that changed since its last full database backup. The default value is 20. This estimate is needed because SQL Server does not provide a way to determine the size of a differential backup, and because the Tivoli Storage Manager server requires an accurate size estimate to efficiently allocate space and place objects. The Tivoli Storage Manager server uses this value to determine whether there is enough space in the primary storage pool to contain the backup.
   Estimated Log % Change	Use this option to specify the estimated fraction of an SQL database that changed due to non-logged operations since the last log backup. The default value is 0.
   Truncate Logs	Use the option to specify whether to dispose of entries that you no longer need in the SQL database transaction log after you back up the log. The default value is Yes. In general, you do not want to truncate the log when rebuilding a corrupted database. This option enables the server to back up the transaction log but does not affect the data in any way. All transaction log entries are written from the time of the last log backup to the point of database corruption. If you do not truncate the transaction log, you might be able to back up the transaction log of a damaged, suspect, or unrecoverable SQL Server database.
   Back Up Tail-Log	Use the option to store log records that are not yet backed up. By storing these records, also known as the tail of the log, the log chain is kept intact. Before you can recover an SQL Server database to the latest point in time, you must back up the tail of the transaction log. The tail-log backup is the last backup of interest for the database recovery plan.
   SQL Server Checksum	Use this option to verify the integrity of a legacy database backup. Integrity checking is a process that validates the values in a file or configuration for unexpected changes. Values are verified between the current state and the baseline state. In the Performance Properties window of the MMC, you can enable or disable the checksum option for all your legacy databases at once. You can override the global setting, and temporarily enable or disable the checksum option for a database backup, by setting this SQL Checksum option to Yes or No.

5. On the Actions pane, click Backup Method and select Legacy.
6. On the Actions pane, select TSM for the Backup Destination. The only option that is available to you is TSM because the database backups are stored on Tivoli Storage Manager server storage.
7. Optional: Choose a mode for the current task:
   • Run Interactively: Click this item to run the current task interactively. This selection is the default.
   • Run Scheduled: Click this item to convert the current action into a scheduled task. When you select this item, the schedule wizard starts, and integrates the command that is required to complete the task.
8. On the Actions pane, click the backup type that meets your needs.
   • Full Backup
   • Copy-Only Full Backup
   • Differential Backup to TSM
   • Log Backup to TSM
9. Review the status of the backup operation by clicking Task List in the results pane. Click Task Details to view detailed status information.