BakBone APM For Microsoft SQL Server

Redefining Data Protection
Title Page
NetVault:Backup APM for Microsoft SQL Server v4.500
Users Guide for the
NVE 7009-6K 07/21-06
Copyrights
NetVault:Backup - Users Guide for the NetVault:Backup APM for Microsoft SQL Server Software Copyright 2006 BakBone Software Documentation Copyright 2006 BakBone Software This software product is copyrighted and all rights are reserved. The distribution and sale of this product are intended for the use of the original purchaser only per the terms of the License Agreement. All other product trademarks are the property of their respective owners. The NetVault:Backup - Users Guide for the NetVault:Backup APM for Microsoft SQL Server documentation is copyrighted and all rights are reserved. This document may not, in whole or part, be copied, photocopied, reproduced, translated, reduced or transferred to any electronic medium or machine-readable form without prior consent in writing from BakBone Software. THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED INTO NEW EDITIONS OF THE PUBLICATION. BAKBONE SOFTWARE MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.
BakBone Software
9540 Towne Centre Drive, Suite 100 San Diego, California 92121 858.450.9009
Users Guide
The Microsoft SQL Server APM

SQ.0.0 - About the Microsoft SQL Server APM ................................................... 5
SQ.0.1 - Target Audience ...................................................................................................... 5
SQ.1.0 - Installing the Microsoft SQL Server APM ............................................ 6

SQ.1.1 - Pre-Installation Requirements ................................................................................. 6 - SQ.1.1.a - Setting Up the NetVault: Backup Process Manager ................................................ 6 - SQ.1.1.b - Recommended Configuration .............................................................................. 7 SQ.1.2 - Installation Procedure ............................................................................................. 8 SQ.1.3 - Removing the Microsoft SQL Server APM ............................................................... 9
SQ.2.0 - Configuring the Microsoft SQL Server APM ..................................... 10 SQ.3.0 - Backing Up Data with the Microsoft SQL Server APM ............... 11
SQ.3.1 - Step 1: Selecting Data Items for a Backup ............................................................. 11 SQ.3.2 - Step 2: Setting Backup Options ............................................................................ 12 SQ.3.3 - Step 3: Finalizing and Submitting the Backup Job ................................................. 17
SQ.4.0 - Restoring Data with the Microsoft SQL Server APM ................... 17
SQ.4.1 - Phase 1: Understanding the Recovery of Various Types of Backup........................ 18 - SQ.4.1.a - Overview of Available Backup and Recovery Scenarios ....................................... 18 SQ.4.2 - Phase 2: Restore Procedure .................................................................................. 20 SQ.4.3 - The Restore Options Tab....................................................................................... 21 SQ.4.4 - Restoring the Master Database ............................................................................. 23 SQ.4.5 - Renaming/Relocating a Restore ............................................................................ 24 - SQ.4.5.a - Renaming a Restore......................................................................................... 24 - SQ.4.5.b - Relocating a Restore ........................................................................................ 25 - SQ.4.5.c - Renaming and Relocating a Restore .................................................................. 26 - SQ.4.5.d - Restoring Data Files and Log Files to Different Locations ..................................... 26
SQ.5.0 - The Microsoft SQL Server APM and Application Cluster Support................................................................................................................ 27
SQ.5.1 - Application Cluster Support - An Overview ........................................................... 28 SQ.5.2 - About this Section of the Guide ............................................................................ 28 SQ.5.3 - Installation ............................................................................................................ 29 - SQ.5.3.a - Pre-Requisites ................................................................................................. 29 - SQ.5.3.b - Installation Procedure ....................................................................................... 29 SQ.5.4 - Backup/Restore Scenarios .................................................................................... 30
SQ.5.5 - Licensing ............................................................................................................. 31 SQ.5.6 - Configuration ....................................................................................................... 31 - SQ.5.6.a - Configuration for Backup/Restore Scenario A ..................................................... 32 - SQ.5.6.b - Configuration for Backup/Restore Scenario B ..................................................... 32 SQ.5.7 - Backup ................................................................................................................. 33 SQ.5.8 - Restore ................................................................................................................ 34 - SQ.5.8.a - Restoring a Virtual Client Backup....................................................................... 34 - SQ.5.8.b - Restoring Data Backed up From a Member Client ............................................... 35 SQ.5.9 - Multiple Shared Microsoft SQL Instances .............................................................. 35 - SQ.5.9.a - Installation Requirements.................................................................................. 35 - SQ.5.9.b - Configuration Requirements .............................................................................. 36 - SQ.5.9.c - Backup Requirements ...................................................................................... 37 - SQ.5.9.d - Restore Requirements ...................................................................................... 38
SQ.6.0 - Troubleshooting ............................................................................................. 39
NetVault: Backup Users Guide
SQ.0.0
About the Microsoft SQL Server APM

As storage environments have experienced rapid growth, so has the importance of data management and storage. The increasing size and number of Microsoft applications brings to the forefront the need for a storage management solution that protects important corporate assets while keeping the application running and available. The Microsoft SQL Server Application Plugin Module (APM) for NetVault: Backup provides a high performance, reliable and easy to use Microsoftspecific backup and restoration solution for protecting corporate data. This APM increases application availability by providing fast online backup of databases. The main features included in the APM are described in the following list: Hot Backup - With the NetVault: Backup Microsoft SQL Server APM, user databases remain online and accessible during backups, minimizing downtime for users. Selectable Database Backup Operations - The Microsoft SQL Server APM allows you to backup only what is required. With the easy to use, point and click user interface, administrators can select precisely what needs to be backed up or restored. If the database server node is opened, an administrator may select specific items from a list of databases, with a simple mouse click. Multiple Backup Modes - The Microsoft SQL Server APM supports both full and multiple type of transaction log backups. Logs Microsoft SQL Error Messages - The Microsoft SQL software records all messages to private log files. During backup and recovery operations, NetVault: Backup intercepts log messages related to the current job and sends a copy to the NetVault: Backup log so they are displayed with other NetVault: Backup job messages.
SQ.0.1
Target Audience
Microsoft DBA skills are not generally required for routine backup operations. However, initial configuration and recovery operations may require Administratorlevel experience and access.
SQ.1.0
SQ.1.1
Installing the Microsoft SQL Server APM

Pre-Installation Requirements
Before installing the Microsoft SQL Server APM ensure the following have occurred: NetVault: Backup Server/Client Software Installed - At least the Client version of NetVault: Backup must be installed on the machine configured as the Microsoft SQL Server, which must be running Microsoft SQL version 7.0 or later (i.e., versions 7.0, 2000 or 2005). Set Up the NetVault: Backup Process Manager - Specific steps must be taken in order to successfully set up the NetVault: Backup Process Manager service to run in a Windows-based environment, prior to installation of this APM. See the sub-sections that follow, based on the operating system in use, in order to successfully accomplish this.
SQ.1.1.a
Setting Up the NetVault: Backup Process Manager

The Microsoft SQL Server APM gains access to the Microsoft SQL Server and its associated databases via a Windows user account that has been configured with the correct permissions. Therefore, it is necessary to establish this account as the one in use by the NetVault: Backup Process Manager service in Windows. From the machine configured to serve as the Microsoft SQL Server, perform the following steps to properly set up this user account.
Important: The account used in the following procedure must be either the Administrator
account or a member account with the proper SQL Server permissions set (e.g., a Domain Administrator account). 1. From the Start menu, select Settings>Control Panel. Double-click on the Administrative Tools utility to open its associated window.
Figure SQ-1: The window for the NetVault: :Backup Process Manager service as seen in Windows 2000/2003
2. Launch the Services utility by double-clicking on it in order to display a list of services currently running on the machine. Locate the NetVault: Backup Process Manager and double-click on it to open its associated window. 3. In the window that appears, select the Log On tab.
4. Select the This Account option and input an eligible account name (e.g., the actual Administrator login for the machine, or another member account with the correct level of permissions). 5. In both the Password and Confirm Password fields, input the password associated with the account input in the This Account field. 6. Click the OK button to apply the change and close this window.
Figure SQ-2: Restarting the NetVault: Backup Process Manager Service
7. Back in the Services window, locate the NetVault: Backup Process Manager item and right-click on it to access its associated pop-up menu. Select the Restart command in order to restart this service. 8. Close this and all subsequent windows to complete this procedure.
SQ.1.1.b
Recommended Configuration
While it is possible to set up a single machine as both the NetVault: Backup Server and the Microsoft SQL Server (i.e., all software installation and configuration requirements outlined earlier are performed on a single machine), it is recommended that these two entities exist on separate machines. The table below displays an ideal set up for use with the MS SQL APM, including the software and configuration requirements to establish this type of environment.
Network Connection
Microsoft SQL Server Machine Software Installed/Configuration Microsoft SQL Server (ver. 7.0 or later) NetVault: Backup Server/Client Software Microsoft SQL Server APM NetVault: Backup Process Manager Service Properly Configured
NetVault: Backup Server Machine Software Installed/Configuration NetVault: Backup Server Software (with the Microsoft SQL Server added as a NetVault Client via the Client Management window of the NetVault: Backup GUI).
Important:
1. Regardless of configuration environment in place (i.e., separate NetVault: Backup Sever and MS SQL Server, vs. a single machine configured as both), the Microsoft SQL Server APM must be installed on the machine configured as the Microsoft SQL Server. 2. If the machine configured as the Microsoft SQL Server and the NetVault: Backup Server are separate machines (i.e., as recommended in the table above), the machine will need to be successfully added to the NetVault: Backup Server via the Client Management window before this operation can take place. (For details on adding a Client to a NetVault: Backup Server, please see the NetVault: Backup - Administrators Guide). 3. Example images and procedures throughout this guide assume that the two machine environment, outlined in the preceding table is in place and all of the above configuration requirements have occurred (i.e., the NetVault: Backup Server and MS SQL Server are separate machines). 4. NetVault: Backup version 7.3 offers support for the backup/restore of clustered instances of Microsoft SQL Server. NetVault: Backups Application Cluster Support Functionality is used for this purpose. For complete details on the installation, configuration and backup procedures required to set up this functionality with the Microsoft SQL Server APM, see the section, The Microsoft SQL Server APM and Application Cluster Support on page 27.
SQ.1.2
Figure SQ-3: The Client Management window of NetVault: Backup
Installation Procedure
1. From the machine acting as the NetVault: Backup Server, launch the GUI and access the Client Management window by clicking either of the Client Management buttons in the command toolbar (or select the Client Management command from the Administration pulldown menu). 2. Right-click on the NetVault: Backup machine configured as the Microsoft SQL Server in the Clients frame and select Install Software from the pop-up menu. 3. Navigate to the location of the .npk installation file (e.g., the NetVault: Backup APM Installation CD or the directory to which the file was downloaded). Select the file (e.g., mssxxxx.npk) and click on Open to begin the installation process.
Important: Based on the operating system being used, the directory path for this
installation software may vary, but the file required for this process should be entitled mssxxxx.npk (where xxxx represents various software platforms and version numbers).
Figure SQ-4: The dialog box launched upon the successful installation of the APM
4. When the installation has completed, a successful installation message will appear in the Install Software dialog box. 5. Once the OK button is clicked to close this dialog box, the APM has been successfully installed and is ready for configuration.
SQ.1.3
Figure SQ-5: The Remove Software window with the Microsoft SQL Server APM selected for removal
Removing the Microsoft SQL Server APM

1. From the machine acting as the NetVault: Backup Server, open the NetVault: Backup Client Management window by clicking the Client Management button on the NetVault: Backup GUI (or select Client Management from the Administration pull-down menu). 2. Right-click on the NetVault: Backup machine containing the Microsoft SQL Server APM in the Clients window and select Remove Software from the pop-up menu.
Figure SQ-6: The two dialog boxes issued during the removal process for this APM
3. In the Remove Software window that appears, select the MS SQL Plugin item from the displayed list and click the Remove button. 4. A dialog box will appear asking for confirmation of the remove command. Click on OK to proceed (or Cancel to abort). Clicking OK results in the removal of the software and a confirmation message will appear. Click OK to close this dialog box and return to the Client Management window.
10
SQ.2.0
Configuring the Microsoft SQL Server APM

Prior to initiating the first backup with the Microsoft SQL Server APM, it is necessary to set various configuration options for the APM by performing the following steps: 1. Launch NetVault: Backup and click on the Backup button in the NetVault: Backup GUI (or select Backup from the Operations pull-down menu). 2. In the Selections window, double-click on the NetVault: Backup Client that contains the Microsoft SQL Server APM to open it (i.e., the Microsoft SQL Server machine).
Figure SQ-7: Selecting the Configure command from the pop-up menu
3. Right-click on the MS SQL APM and select Open from the pop-up menu. The APM will automatically detect all instances of Microsoft SQL on the target machine and display them accordingly. 4. Locate the desired instance in the tree and right-click on it. From the pop-up menu that appears, select the Configure command.
Figure SQ-8: The Microsoft SQL Server APM Configuration window
5. The MS SQL Configuration window will launch. This window contains two frames and an additional option. The Logon Security Mode Frame - This frame contains the following options: Windows - Select this option if the Microsoft SQL Login Security Mode is set to Windows 2000 Integrated. SQL User - Select this option if the Microsoft SQL Login Security Mode is set to Standard or Mixed. The SQL User Login Details Frame - The options in this frame will remain greyed-out and unavailable, unless the SQL User option is selected from the Logon Security Mode frame. Once this option is selected, the following options can be accessed in this frame: Login - Supply a valid name for an account which has the appropriate privileges to perform Microsoft SQL dump and load commands. Password - Supply the applicable password value for the account name input in the Login field to allow for access.
11
Instance(s) - Input the exact name of the instance of SQL in use in this field (e.g., SQLSERVER, SQLSERVER\instance2 etc.). In the event that multiple instances of Microsoft SQL are in place on the SQL Server, each can be listed in this field, separated by a comma. Each instance, as it is successfully located will be revealed in the Selections tab of the Backup window for browsing and inclusion in a backup job.
Important: If the MS SQL Server itself, or a particular instance of MS SQL in a multiple

instance environment, cannot be accessed by NetVault: Backup (i.e., it is not accessible in the various windows of the GUI), the exact instance or MS SQL Server name of this machine must be manually input in this field.
SQ.3.0
Backing Up Data with the Microsoft SQL Server APM

With configuration complete on the target machine, it is now possible to perform backups of the Microsoft SQL Server with this APM. The following subsections break down the backup process as follows: Step 1: Selecting Data Items for a Backup Step 2: Setting Backup Options Step 3: Finalizing and Submitting the Backup Job
SQ.3.1
Figure SQ-9: The MS SQL APM opened to reveal the tree structure of selectable items for a backup
Step 1: Selecting Data Items for a Backup

1. From the NetVault: Backup Server, launch the GUI and access the Backup window (i.e., by clicking on either the large or small command toolbar buttons, or by selecting Backup from the Operations pull-down menu). 2. From the Selections tab of the Backup window, locate the Client on which the APM is installed and open it by double-clicking on it (or right-click on it and select Open from the pop-up menu). This will display a list of APMs/plugins installed on the selected Client. 3. Double-click the Microsoft SQL Server APM to open it (or right-click on it and select Open from the pop-up menu). The APM will automatically detect how many Microsoft SQL instances exist, based on the configuration process performed, and display them in the tree structure.
12
4. With the instances revealed, it is possible to perform the following: Select the Entire Instance for Inclusion Open an Instance to Display its Individual Database Components and Select the Desired Ones for Inclusion - Double-click on the desired Instance to open it. Open an Individual Database to Display its File Contents (if applicable) - By double-clicking on a database, it may open to reveal an individual file item which can be selected. These individual files will be revealed for databases that are not Simple Recovery Methods (i.e., the file is required for proper restore of the database). Navigate the tree structure and select items for inclusion as desired. 5. With desired items selected for a backup, it is recommended that a Selection Set be created. Selection Sets allow for often selected data items to be saved in a composite set that can be easily accessed for future backup jobs. This eliminates the need to manually select these items each time a backup is required. Selection Sets are not unique to the Microsoft SQL Server APM. For details on their creation and use, please see the Appendix B: Working with Selection Sets of the NetVault: Backup - Administrators Guide.
Important: A Selection Set is required when an incremental backup scenario is to be used

(e.g., one that incorporates Database - Differential or Transaction Log forms of backup).
SQ.3.2
Step 2: Setting Backup Options

With all data selection tasks completed, click on the Backup Options tab to access these options and set them as desired. This tab is broken down into four frames which are covered in the following points:
Figure SQ-10: The options available in the Backup Options tab for the Microsoft SQL Server APM
NetVault: Backup Users Guide The Backup Type Frame - This frame contains the following options:
13
Database - Complete: Performs a complete backup of the selected data. This is the equivalent of issuing the Microsoft SQL commands DUMP DATABASE or BACKUP DATABASE. File and Filegroup - Select this option to backup only the files contained in a selected database (i.e., not the databases structural information). This form of backup will allow you to perform restores of individual files and file groups, without the need to recover other database information. Database - Differential: Performs a backup of only data that has changed since the last complete backup of the selected items (i.e., a backup of the selected data has already been performed using the Database - Complete backup type). Transaction log: Select this type of backup to have NetVault: Backup remove inactive parts of logs associated with the selected data before the backup is performed. It is recommended that this form of backup be performed in conjunction with a File and Filegroup backup.
Important:
1. Prior to utilizing any of these options to generate an Incremental backup scenario (e.g., the Database - Differential and Transaction Log backup types), it is strongly recommended that the section, Phase 1: Understanding the Recovery of Various Types of Backup on page 18, be reviewed. This section provides an outline of how the sequence required for each of the available types of backup affects the restore procedure. 2. It is only possible to perform a Transaction Log type of backup for data that has had a Database - Complete or File and Filegroup backup performed on it at least once. 3. Before performing a backup of either Database - Differential or Transaction Log type, a full backup of the same data (i.e., a backup utilizing the Database - Complete backup type) must be performed. In addition, it is only possible to perform either of the aforementioned forms of backup using a Backup Selection Set. During the data selection process of the required Database - Complete backup, a Backup Selection Set is created in order to save the data selections into a set that can be accessed for use with either a Database Differential or Transaction Log backup. For complete details on the creation of a Selection Set in NetVault: Backup, please see Appendix B: Working with Selection Sets of the NetVault: Backup - Administrators Guide). 4. If the data included in a File and Filegroup type of backup is changed through Microsoft SQL use after the backup was performed, it will be necessary to perform a Transaction Log backup of this same data in order to maintain a valid date stamp. 5. The File and Filegroup, Database - Differential and Transaction Log forms of backup can only be selected as the Backup Type for either Full or Bulk Logged types of MS SQL databases. Simple databases cannot be backed up using these backup types.
14
The Transaction Log options frame - This frame is left greyed-out and unavailable unless the Transaction Log option is selected from the Backup Type frame. Once selected, the following options are available:
Figure SQ-11: With the Transaction Log backup type selected, the options in this frame are made available
Normal - Selecting this option will perform a standard Transaction log backup, but the log itself will be truncated. No Truncate - Select this option in order to avoid truncating the Transaction Logs when a backup of this type is selected. With this option, the log will be backed up even if the database becomes damaged, flagged as suspect, or has not been recovered. If New DB in Trans/Diff Backup Frame - This frame is left-greyed out and unavailable unless the Database - Differential or the Transaction Log option is selected from the Backup Type frame. Once selected, the following options are available: Ignore - Selecting this option will request that NetVault: Backup ignore any databases that have been newly created since the original Database - Complete backup of a Selection Set was performed (i.e., only the databases included in the original Database - Complete backup will be checked for new data, and only that data will be included for the backup). Do Full Backup - If new databases have been added since the initial Database - Complete backup of a Selection Set of data, selecting the Do Full Backup option will instruct NetVault: Backup to perform a full and complete backup of these new databases. Backup Method Frame - This frame contains several options that allow for the method of Microsoft SQL backup to be selected. Use Named Pipe - With this backup method selected, a backup will be performed of data selected in the Selections tab, to a named pipe. The other options in this frame only apply to the use of the other available backup method, Use Virtual Device Interface (VDI). Therefore, these additional options will remain greyed-out and unavailable when the Use Named Pipe backup method is selected. Use Virtual Device Interface (VDI) - The default setting, this backup method allows the user to take advantage of a high-performance backup (and restore) mechanism. Once selected, other fine-tuning options can be set, including those listed below:
Figure SQ-12: The options available in the Backup Method frame
15
Block Size (Bytes) - Available only when Use Virtual Device Interface (VDI) is selected, this field allows for the input of a device block size (in bytes). The default value for this field is 64KB (e.g., 65536 bytes). Transfer Multiple - A value input in this field is used as a multiplier for the value input in the Block Size field. The overall value of the two serves as the maximum allowable data transfer size (i.e., the Block Size default of 65536 bytes multiplied by the default Transfer Multiple of 24, results in a maximum allowable transfer size of 1.6 MBytes). Number of VDI Devices - The value input in this field determines the number of VDI devices to be used for storing the backup job. In the default setting, all backup job options have one VDI device set to the job, when the Use Virtual Device Interface (VDI) is selected. Additional VDI devices can be added; however, the minimum number of VDI device is one, the maximum number of the VDI devices added cannot exceed thirty two.
Important: It is important to note that the number of VDI devices selected is equal or less
than the number of available media or tape drive. For e.g., if the number of VDI devices selected is five, there needs to exist a minimum of five media or tape drives. Snapshot Format (Microsoft SQL 2000/2005 ONLY) - Select this option to perform a snapshot of the selected data, in which only the metadata of a selected database will be recorded to media, thereby resulting in no impact to the production system. This type of backup is useful when the selected databases for a backup are constantly in use by outside users and cannot be taken offline for a standard backup.
Figure SQ-13: The Snapshot Format option is selected and the created path, along with the complete name of the batch file to launch the snapshotting software is input
Snapshot Script (Microsoft SQL 2000/2005 ONLY) - The value input in this field corresponds to a script or batch file that will launch an external snapshotting software to be used in conjunction with NetVault: Backup via selection of the Snapshot Format option. The file itself must reside in the scripts sub-directory of the NetVault: Backup installation directory on the machine configured as the MS SQL Server (e.g., <path to installation>\NetVault\scripts). The field automatically recognizes the correct path to this directory, so it is not necessary to input this path, only the full name of the executable file. For example, if a batch file, entitled snapshot.bat were created to launch the snapshotting software, it would need to be placed in the NetVault: Backup scripts directory and the following value would be input in the SnapShot Script field to access it: snapshot.bat.
16
Important:
1. Use of the Snapshot options offered in this frame require that a third-party software capable of performing snapshots be installed and available on the Microsoft SQL 2000/ 2005 Server (e.g., if the SQL Server is a separate machine from the NetVault: Backup Server, as recommended in the installation instructions, this snapshotting software must be installed and fully configured for use on that machine). 2. If utilizing the Snapshot Format option, only complete databases can be selected for a backup in the Selections tab (i.e., individual database files within a database cannot be selected to conduct a backup of this type). 3. When establishing a script or batch file for use with the Snapshot options offered in this tab, it is critical that the file be tested beforehand to ensure that the third party software actually launches when it is accessed. It is also recommended that this test be conducted with the script/batch file placed in the .../NetVault/scripts directory. 4. After a Snapshot Format backup is performed, it is highly recommended that the Snapshot image taken be verified to ensure that it was actually generated by the third-party software used to perform the operation. 5. If additional sub-directories have been created in the NetVault: Backup scripts directory to house a created script, the value input in the Snapshot Script field must include this additional directory path along with the executable file name, as if starting from the NetVault: Backup scripts directory. In addition, directories must be followed by a forward slash (/) rather than the traditional back slash used in Microsoft Operating systems (e.g., if a series of sub-directories were created off of the scripts directory entitled mssql\batch, and the snapshot.bat batch file resides in the batch sub-directory, the following would be input in the Snapshot Script field: mssql/batch/snapshot.bat). 6. Batch/executable files, and any sub-directories created cannot contain spaces in their titles for use in the Snapshot Script field. Underscores (_) can be used in their place. Ensure that all of these do not contain spaces in their respective titles. 7. The Snapshot Format option must be selected as well as the complete command executable/batch file name input in the SnapShot Script field for the snapshot functionality to operate correctly. This also applies to additional path information if sub-directories have been created. If proper values are not input, the job will fail and a message will be displayed in the NetVault: Backup Logs stating such.
17
SQ.3.3
Step 3: Finalizing and Submitting the Backup Job

1. The remaining tab selections (e.g., Schedule, Target and Advanced Options) contain additional options that can be set as desired. The options available in these tabs are not unique to the Microsoft SQL Server APM. For complete details on these options and their use, please see Chapter 4: The Backup Window of the NetVault: Backup - Administrators Guide. 2. Enter a name for the job in the Job Title box. It is highly recommended that a name be assigned that will differentiate this job from any others performed with this APM. This will allow for easier recognition of the job during restore. 3. Submit the backup job by clicking the Submit button. See the NetVault: Backup - Administrators Guide for information on viewing status, progress and logs.
Important:
1. When attempting a backup operation, if a dialog box opens with a message that the database has failed to open and requests that logs be checked, make sure the correct configuration has been set and that Microsoft SQL is running on the target Client. For more information on configuration, see Configuring the Microsoft SQL Server APM on page 10. 2. It is not possible to mix a full database backup with individual items in a single job (i.e., selecting an entire database as well as individual files/filegroups from a second database in a single backup job). This will result in an error when the job is run, failing the backup job. 3. As explained in the process above, it is possible to browse the selection tree down to the file/filegroup level of a database. However, it is important to note that certain databases do not allow for browsing to this level and must be selected as a complete database for inclusion in a backup (i.e., due to the databases content/format).
SQ.4.0
Restoring Data with the Microsoft SQL Server APM

This section outlines the use of the Restore window to conduct a recovery of data backed up through the Microsoft SQL Server APM. In addition, a section of information is offered which is intended to give the user a better understanding of how various types of backups performed with this APM should be successfully restored.
Important: Microsoft SQL Server APM version 3.5 (and earlier) backups can not be
restored with version 3.6 (and later) of this APM. If it is necessary to recover a version 3.5 (or earlier) backup job, it is necessary to obtain a re-install this version of the APM (i.e., remove the 3.6 or later version). Please contact BakBone Technical Support for details on obtaining older versions of this APM.
18
SQ.4.1
Phase 1: Understanding the Recovery of Various Types of Backup

It is important to understand the way that the different forms of backup available with this APM are conducted in order to better understand the proper way to recover each and then re-establish it for use. Below are some brief examples of exactly what occurs when each backup type is performed. Database - Complete Backup: This form of backup will generate a copy of all selected data. This is required as Step 1 in any series of backups, whether it be a standalone full backup of selected data or an incremental form, such as a Database - Differential or Transaction Log backup. Database - Differential Backup: This form of backup will record all activity since the last complete backup performed and record only this new or changed information. The Ignore Option - If enabled for use in conjunction with a Database Differential backup, any databases that were created after the original Database - Complete backup occurred will be left out of the backup. The Do Full Backup Option - In contrast to the Ignore option, if this option is selected for use in conjunction with a Database - Differential backup, any databases that were created after the original Database Complete backup will be fully backed up (i.e., all data included in these new databases will be included in the backup). Transaction Log Backup: This will copy changes made to the transaction log since the last backup performed. This type of backup can be truncated or not, depending on the options selected in the Backup Options tab (see Backing Up Data with the Microsoft SQL Server APM on page 11 for more information on these options). By default, the log is truncated to the beginning of the active portion of the log containing the oldest open transaction.
SQ.4.1.a
Overview of Available Backup and Recovery Scenarios

The following table demonstrates how the type and order of backups affect the way restores should be performed.
Job Type Complete Backup and Recovery Operation How Data was Backed Up: A backup of the type Database - Complete was performed in which a copy of all of the data in the selected database was generated. How Data is Recovered: To fully restore the data, simply perform a standard restore, selecting all of the data items included in the Database - Complete backup. Overall Outcome: Simple Backup and Recovery of a Database

Job Type Differential Backup and Recovery Operation How Data was Backed Up: 1. An initial Database - Complete backup was performed in which a copy of all of the data in the selected database was generated.
19
2. A Database - Differential backup was then performed at a later time. This type of backup copied all activities that had taken place since the initial Database - Complete backup was performed, including new data and changes to existing. With a backup of this type, the associated transaction log was not truncated. 3. This type can be repeated in the future. All data, new or changed since the original Database - Complete backup will be included (including data stored in previous Database - differential backups). How Data is Recovered: 1. To restore the data to the point in time of the most recent Database Differential backup, first restore the Database - Complete backup as either Inactive or Read Only. 2. Next, recover the most recently performed Database - Differential backup with Set Database Active selected. Overall Outcome: Slower Backup, Fastest Recovery Transaction Log Backup and Recovery How Data was Backed Up: 1. An initial Database - Complete backup was performed in which a copy of all of the data in the selected database was generated. 2. Next, a Transaction Log backup of this same selected data was performed at a later time. This type of backup copied all activities that had taken place since the initial Database - Complete backup was performed, including new data and changes to existing. With a backup of this type, the associated transaction log was truncated. 3. Additional Transaction Log backups can be performed as desired. At this phase, this type of backup will copy only the transaction log, thereby recording all activities which have taken place since the last Transaction Log backup was performed. How Data is Recovered: 1. To restore the data to its most recent state, first recover the original Database - Complete backup with either the Set Database: NonOperational or Set Database: Read Only option selected from the Restore Options tab.
20
Job Type Transaction Log Backup and Recovery

(cont.)
Operation 2. Next, recover each of the Transaction Log backups in the order in which they were backed up. Each sequential Transaction Log must be restored using either Set Database: Non-Operational or Set Database: Read Only until the final restore step when the database can be set to active (via the selection of the Set Database: Operational Restore option) if desired.
Overall Outcome: Fastest Backup, Slower Recovery
Important: Depending on the Action after restore option selected in the Restore Options
tab, a recovered database can be set to be automatically activated or not. Refer to the relevant Microsoft SQL documentation for more information on activating databases.
SQ.4.2
Phase 2: Restore Procedure

To perform a restore using the Microsoft SQL Server APM, follow the instructions below:
Important: Various restore scenarios exist based on the type of backup performed. Before attempting a restore, it is recommended that the section, Phase 1: Understanding the Recovery of Various Types of Backup on page 18 be thoroughly reviewed.
1. From the NetVault: Backup GUI, access the Restore window (i.e., by clicking either of the Restore buttons in the command toolbar, or by choosing the Restore command from the Operations pull-down menu). With the window accessed, the Selections tab will be displayed, containing a list of clients which have completed successful backups. 2. Locate the client in the list which completed the desired backup and open it (by double-clicking on it or right-click on it and choose Open from the pop-up menu). A list of the plugins used to complete successful backups on the target machine will be displayed. 3. Open the Microsoft SQL Server APM (via double-clicking on it or rightclicking and selecting the Open command) to display all backup savesets generated with this APM that are available for restore. 4. Open the desired backup saveset (by double-clicking on it) to display the list of databases available for restore. 5. Select the desired items for a restore by clicking the box to the left of the desired item. Selected items will be marked with a green check. 6. Click the Restore Options tab to display these options and set them as required (see the section, The Restore Options Tab on page 21, for complete details on the options available in this tab).
21
7. The remaining tab selections (e.g., Schedule, Target Client and Advanced Options) contain additional options that can be set as desired. The options available in these tabs are not unique to the Microsoft SQL Server APM. For more information on these tabs, see the NetVault: Backup - Administrators Guide. 8. Input a suitable name for the job in the Job Title box. It is recommended that a detailed name be used to allow for easy identification of the job in the various windows of the NetVault: Backup GUI (e.g., the Job Management window, the Job Status window, etc.). 9. Submit the restore job by clicking the Submit button.
Important: Restored databases must be brought online from within the Microsoft SQL
application if they have not been brought online automatically when the restore is complete.
SQ.4.3
Figure SQ-14: The Restore Options tab for the Microsoft SQL Server APM
The Restore Options Tab

This tab contains options that can be set in conjunction with items selected for a restore in the Selections tab. Backup Type - The type of backup that was performed, based on the database chosen for a restore in the Selections tab, is displayed here. Action After Restore Frame - This frame contains these options: Set Database Operational; No More Transaction Logs can be Restored - Select this option if no further transaction log or differential database backups are to be applied once the restore of the selected data has completed. This is equivalent to the Microsoft SQL command, RESTORE DATABASE WITH RECOVERY.
22
Set Database Non-operational; More Transaction Logs can be Restored - Select this option if another transaction log or differential database backup is to be applied once this restore has completed. This is equivalent to the MS SQL command, RESTORE DATABASE WITH NO RECOVERY. Set Database Read-only; More Transaction Logs can be Restored Select this option if another transaction log or differential database backup is to be applied. The database can be read during transaction log restores; this is useful when it is necessary to check the database between transaction log restores (e.g., warm backup server situations). This is equivalent to the Microsoft SQL command, RESTORE DATABASE WITH STANDBY (i.e., restoring in Standby State).
Important: A restore of a File or Filegroup backup (i.e., as set in the Backup Type frame
of the Backup Options tab for a selected backup) cannot have the Set Database ReadOnly; More Transaction Logs can be Restored option set. The MS SQL Server software does not support this functionality for the recovery of this type of backup. Undo File - Input the complete path to the Microsoft SQL Undo file here. The Undo file is used by SQL as a point of reference when performing restores in Standby State (i.e., if the target MS SQL database is currently in Standby, this file is required by NetVault in order to properly perform the restore). This option is only used when performing a restore to a MS SQL server that is currently in Standby, therefore the field will remain greyedout and unavailable unless the Action After Restore is set to either Set Database Non-operational; More Transaction Logs can be Restored or Set Database Read-only; More Transaction Logs can be Restored.
Important: The path used in this field can be input in the Undo File for Standby Restore
field, of the MS SQL Plugin sub-tab of the Plugin Options tab located in the NetVault Configurator. By doing this, the path will automatically appear by default in this field for all Microsoft SQL Server APM restore jobs. Otherwise, you will need to manually input this complete path value on a per-restore job basis.
Figure SQ-15: The Undo File for Standby Restores field, as located in the MS SQL Plugin subtab of the Plugin Options tab located in the NetVault Configurator
Point in Time Restore - Select this option to recover a Transaction Log backup to a specific point in time (as set in the Time and Date fields).
23
Target Instance - Input the name of a different instance to which selected data is to be restored, or leave this option at its default of (local) to restore it to its original location. Qualifying entries in this field consist of either of the following: The Path to the Instance - <System name>\<instance name> The Instance Name Enclosed in Parenthesis - (<instance name>) The Restore Method Frame - This frame contains several options that allow for the method of MS SQL restore to be selected. Use Named Pipe - Select this option to perform the restore of selected data to a named pipe. With this restore method selected, all other options in this frame do not apply, so they will be revealed as greyed-out and unavailable. Use Virtual Device Interface (VDI) Select this option to take advantage of a high-performance restore mechanism. With this option selected, other finetuning options can be set, including those listed below. Block Size (Bytes) - Can be set only when Use Virtual Device Interface (VDI) is selected, this field allows for the input of a device block size (in bytes). The default value for this field is 64KB (e.g., 65536 bytes). Transfer Multiple - A value input in this field is used as a multiplier for the value input in the Block Size field. The overall value of the two serves as the maximum allowable data transfer size (i.e., the Block Size default of 65536 bytes multiplied by the default Transfer Multiple of 24, results in a maximum allowable transfer size of 1.6 MBytes). Mount Command - Use this field to input the exact path and file name of a script or batch file to be used to remount a database once the restore has completed.
Figure SQ-16: The options available in the Restore Method frame
SQ.4.4
Restoring the Master Database

If the Master Database was among the items included in a backup that is to be restored, the procedure below must be followed to successfully recover it.
Important:
1. The target server for this type of restore must have the exact same file system path as the Microsoft SQL Server that was originally backed up. For example, if the database files that were backed up existed in a directory entitled databases on the C:\ partition of the original machine, the new target machine must have this same directory set up in the same partition.
24
2. Microsoft requires the database server be in single-user mode prior to restoring a master database. Refer to the relevant Microsoft SQL documentation for more information. 3. When attempting a recovery of this type, it is recommended that only the master database be selected for this procedure (i.e., no other individual databases should be included in this type of restore). 4. Before this procedure can be successfully completed the NetVault: Backup Process Manager must be properly configured on the Microsoft SQL Server. Please see the section, Setting Up the NetVault: Backup Process Manager on page 6. 1. With the SQL Server in single-user mode, access the appropriate backup saveset containing the Master Database to select the desired data and execute the restore job (e.g., using the steps covered in the section, Restoring Data with the Microsoft SQL Server APM on page 17). 2. Once the restore job completes, it will be labelled as Job Completed in the Logs window of the NetVault: Backup GUI. However, the job has actually completed, but with warnings. This is because when the Master Database is recovered, the Microsoft SQL Server will shut down immediately and not notify NetVault: Backup of the true completion status. This is expected behavior. 3. The final action required is to restart Microsoft SQL on the target machine. Once restarted, the newly recovered Master Database will be active.
SQ.4.5
Renaming/Relocating a Restore
NetVault: Backup makes it possible to rename and/or relocate a restore item with the Microsoft SQL Server APM.
SQ.4.5.a
Renaming a Restore
Simply renaming a restore allows the user to restore a database item to its original location, but with a new name for the item. 1. From the Selections tab of the Restore window, open down to the desired MS-SQL APM backup saveset. Open the the saveset to reveal the database items contained within.
Figure SQ-17: Selecting the Rename command from the pop-up menu
2. Select the desired item by clicking the box to the left of it (selected items will contain a green check). 3. Once selected, right-click on the item and select the Rename command from the pop-up menu that appears.

Figure SQ-18: The Restore Rename window
25
4. The Restore Rename dialog box will appear. Click the checkbox to the left of the Rename to field in order to activate it and input the desired new name for the selected item. 5. Click on OK to commit the change (or Cancel to abort) and return to the Selections tab. The renamed item will be labelled as such.
Figure SQ-19: A renamed item as it appears in the Selections tab of the Restore window
6. With these options set as described, the selected item will be recovered to its original location, but with the newly created name value. This can be beneficial when attempting to recover a data item without overwriting an existing one. 7. Continue with normal restore selections and options (as described in the various sections above) and then submit the job.
Important: If attempting to rename a restore of a Snapshot backup (i.e., the Snapshot

Format functionality was used with the backup to be recovered), the actual MS SQL Server Log and Data files must be renamed to the following, before the restore job is submitted. <New Database Name>_<Existing Database Name>_Data <New Database Name>_<Existing Database Name>_Log For example, a Snapshot is taken of a database entitled MSSQL. Its existing Log and Data files on the target MS SQL Server would be named MSSQL_Log and MSSQL_Data. A restore of this databases Snapshot is to be performed, but it will be renamed MSSQL_New. Therefore, it would be necessary to rename these two files as follows: MSSQL_New_MSSQL_Log and MSSQL_New_MSSQL_Data Once this is complete, perform the same procedure covered in steps 1-7, above. Ensure that the exact database named as the <Existing Database Name> in these lines must be the item selected for rename and the rename value given must be exactly what was input as the <New Database Name>.
SQ.4.5.b
Relocating a Restore
In relocating a restore, the user can restore a database item with its original name, but to a new location. 1. Repeat Steps 1 - 3 covered in the section, Renaming a Restore on page 24. 2. Click the checkbox to the left of the Relocate to field in order to activate it. Type in the path to the new directory where the item is to be restored. 3. Click on OK to commit the change (or Cancel to abort) and return to the Restore window. The relocation will be displayed for the selected data.
26
Figure SQ-20: With a valid entry input in the Restore Rename window, the item will be marked with its Relocation information in the Selections tab
4. With options set as described, the selected item will be recovered with its original name, but to the new location specified. This can be beneficial when attempting to recover a data item that may already exist by simply restoring it to a different location, thereby eliminating the possibility of an overwrite. 5. Continue with normal restore selections and options (as described in the various sections above) and then submit the job.
Important:
1. The directory signified by the path input in the Relocate to: field must exist at job run-time for a relocated restore to succeed. 2. In order to relocate a restore item to an entirely different Microsoft SQL Server, simply follow the instructions detailed above and then click the Target Client tab and select the desired Client Server from the list displayed. Clients must be successfully added to the server for them to be displayed in the list. For complete details on Adding Clients and the Target Client tab, please see the NetVault: Backup - Administrators Guide. 3. When inputting a path in the Relocate to: field, ensure that directories are separated using a back slash (\). If a forward slash is used, the relocation will fail. 4. If relocating a restore of a Snapshot backup, follow the same procedure outlined above. However, the MS SQL Server log file for the selected database must be copied from the existing directory and placed in the desired relocation directory before submitting this form of relocation restore job.
SQ.4.5.c
Renaming and Relocating a Restore

In order to both Rename and Relocate a restore, simply combine the procedures detailed in the sections Renaming a Restore on page 24, and Relocating a Restore on page 25, inputting the desired new values in each field.
SQ.4.5.d
Restoring Data Files and Log Files to Different Locations

While restoring data, the log files can be relocated to a directory other than the data files directory. 1. Repeat Steps 1 - 3 covered in the section, Renaming a Restore on page 24. 2. Click the checkbox to the left of the Relocate to field in order to activate it. Type in the paths to the directories where the data files and log files are to be
27
restored. The data file directory must be specified first, followed by the path to the log file directory. The two directory paths must be separated by comma.
Figure SQ-21: Restoring data files and log files to different locations
3. Click on OK to commit the change (or Cancel to abort) and return to the Restore window. The relocation will be displayed for the selected data. 4. Continue with normal restore selections and options (as described in the various sections above) and then submit the job.
Important:
1. The directory signified by the path input in the Relocate to: field must exist at job run-time for a relocated restore to succeed. 2. In order to relocate a restore item to an entirely different Microsoft SQL Server, simply follow the instructions detailed above and then click the Target Client tab and select the desired Client Server from the list displayed. Clients must be successfully added to the server for them to be displayed in the list. For complete details on Adding Clients and the Target Client tab, please see the NetVault: Backup - Administrators Guide. 3. When inputting a path in the Relocate to: field, ensure that directories are separated using a back slash (\). If a forward slash is used, the relocation will fail.
SQ.5.0
The Microsoft SQL Server APM and Application Cluster Support

NetVault: Backup version 7.3 offers support for the backup of Microsoft SQL database information that exists in a clustered environment. However, a version of the APM that is Cluster Friendly must be used (i.e., version 3.7 and later of the Microsoft SQL Server APM). In addition, installation, configuration, backup and restore procedures differ slightly. This section of the documentation is intended to offer specifics on how to operate the cluster friendly version of this APM.
Important:
1. This support is offered with the Microsoft SQL Server APM version 3.7 (and later). 2. NetVault: Backup Encryption functionality is not supported for use in environments incorporating NetVault: Backups Application Cluster Support functionality. If you intend to use this support in conjunction with the Microsoft SQL Server APM, NetVault: Backups Encryption functionality must be disabled. Please see the NetVault: Backup Administrators Guide for details on disabling this functionality.
28
SQ.5.1
Application Cluster Support - An Overview

NetVault: Backup version 7.3 offers backup and restore support to clustered environments on an application-supported basis. This is referred to as Application Cluster Support. Various application software that is capable of running in a clustered environment can be tied to the NetVault: Backup Server for backup and restore. A version of the Microsoft SQL Server APM that has been built to be cluster friendly is transferred to each of the desired machines within a cluster via the NetVault: Backup Server. It is then possible for the NetVault: Backup Server to administer backups and restores of relevant data. This is all controlled via an IP address that has been assigned to the specific clustered application (in this case, the cluster version of Microsoft SQL). For example, using this version of the Microsoft SQL database software, an IP address would need to be assigned to it, during its configuration for it to function in a clustered environment. Through this same IP address, NetVault: Backup can identify a machine within the cluster that is currently in control of the clustered application (i.e., Microsoft SQL in this case) and target it for a backup of its clustered Microsoft SQL database information.
SQ.5.2
About this Section of the Guide

This section of the guide is designed to point out any differences between the set up and usage of the Microsoft SQL Server APM in a clustered environment vs. a traditional one. It is broken down in sections to mirror the sections found in the standard instructions, as follows: Installation Licensing Configuration Backup Restore
Important:
1. Unless outlined in the sections that follow, backups and restores performed with the Microsoft SQL Server APM of clustered data are the same as those performed with traditional Microsoft SQL data. 2. The following sections of this guide only offer information on Microsoft SQL-specific settings required for the use of this APM in a clustered environment. They do not offer instructions on how to set up NetVault: Backups Application Cluster Support to administer backups/restores of a cluster. This process is not APM-specific and complete details can be found in Appendix E: NetVault: Backups Application Cluster Support of the NetVault: Backup - Administrators Guide for version 7.3.
29
3. Prior to viewing the contents that follow, it is strongly recommended that Appendix E: NetVault: Backups Application Cluster Support of the NetVault: Backup - Administrators Guide for version 7.3 be thoroughly reviewed to obtain a better understanding of how the information presented here works in conjunction with the Application Cluster Support functionality.
SQ.5.3
SQ.5.3.a
Installation
Pre-Requisites
The following pre-requisites must be met before it is possible to install the Microsoft SQL Server APM in a clustered environment: Microsoft SQL Clustered Environment in Place - You must have a properly configured clustered environment, capable of using the cluster version of Microsofts SQL database software. Only versions of Microsoft SQL Server that are designed for use in a clustered environment can be used. Cluster Friendly Version of the APM Obtained - At least version 3.7 of the Microsoft SQL Server APM must be obtained for use in the creation of a Virtual Client. It is not possible to use an older version of the Microsoft SQL Server APM in a clustered environment. Separate NetVault: Backup Server Machine - The machine that is to serve as the NetVault: Backup Server must be properly configured and it must exist outside the cluster, but have network connectivity to the machines within the cluster.
SQ.5.3.b
Installation Procedure
Installation of the Microsoft SQL Server APM for a clustered environment is different than the traditional installation of this APM. This process is completed through the creation of a Virtual Client on the NetVault: Backup Server. Simply put, a Virtual Client is a group of machines within the cluster that are seen by the NetVault: Backup Server as a single client, that is created to backup a single clustered resource (e.g., a shared disk drive or, in the case of this APM, a shared instance of Microsoft SQL). During the Virtual Client creation process, the Microsoft SQL Server APM is transferred from the NetVault: Backup Server to selected member clients within a cluster and installed there.
Installation Specifics - Creating a Virtual Client

As noted in an earlier section, the Virtual Client creation process is not APMspecific and complete details can be found in Appendix E: NetVault: Backups Application Cluster Support of the NetVault: Backup - Administrators Guide for version 7.3.x (and later). However, a couple of points should be taken into consideration during the Virtual Client creation process:
30
Figure SQ-22: A Virtual Client that has been set up with the same name as its associated instance. This way, the correct instance can be easily identified for selection
Assign a Suitable Name to the Virtual Client - It is highly recommended that a name be given to the Virtual Client that points out the shared Microsoft SQL Server instance for which it was created. When a Virtual Client is browsed, NetVault: Backup will locate the cluster client currently in control of the clustered application, and reveal all of its Microsoft SQL Server contents, even if these instances are not shared (e.g., in the Selections tab of the Backup window, when a Virtual Client is opened, not only will the shared Microsoft SQL instance be revealed, but any other instances that currently exist on the target machine will be shown as well). With a Virtual Client name set up to be the same as or similar to the shared instance, it will be easy to recognize the specific Microsoft SQL Server instance for which the Virtual Client was created. Only Include Relevant Cluster Clients in the Virtual Client - The member clients that are to be included in the creation of a Virtual Client should only be those within the cluster that are relevant to the application that is to be backed up/restored (e.g., if only two machines within a cluster administer the shared Microsoft SQL Server instance, only these two machines should be included).
SQ.5.4
Backup/Restore Scenarios
As covered in the previous section, after the creation of the Virtual Client, the APM is transferred to all designated cluster clients and installed locally. The installed Microsoft SQL Server APM can be used via the Virtual Client to backup/restore shared data and it is also possible to use the APM to backup/restore Microsoft SQL Server data that is local to each member client. With this in mind, it is necessary to determine the desired backup/restore scenario for use. Scenario A: Backup and Restore of Shared Data Only - Only backups/ restores of data established as shared within the cluster can be performed. Scenario B: Backup and Restore of Shared Data and Local Data Backups/restores of both the shared data between cluster Clients, and Microsoft SQL Server data that is local (i.e., not shared) on each individual member client. With a scenario decided upon, continue on to the following sections which address the set up and use of this APM in a clustered environment.
Important: Hereinafter, each scenario type will be referenced by its letter title when called
out (e.g., Scenario A).
31
SQ.5.5
Licensing
Another difference between using the Microsoft SQL Server APM in a clustered environment is how it is licensed for use. The licenses required vary, based on the type of scenario that is to be used in backing up/restoring data (i.e., as covered in the section, Backup/Restore Scenarios on page 30). With the desired scenario selected, license keys can be obtained from BakBone Softwares Order Administration department. Complete details on the licensing process, including how to obtain the proper license keys can be found in the section, Licensing a Virtual Client of Appendix E: NetVault: Backups Application Cluster Support in the NetVault: Backup Administrators Guide for version 7.3.
Important:
1. Once a Virtual Client is created using the Microsoft SQL Server APM, it is installed with a 45 DAY evaluation license that allows for full usage. For this 45 day period, no license keys are required for the use of this APM, and either of the previously outlined Backup/Restore scenarios can be employed. Upon expiration of this trial period, one of the two aforementioned scenarios must be decided upon and license keys obtained accordingly. 2. In the event that an older version of the Microsoft SQL Server APM was already installed on a machine within the cluster, the version of the APM installed with the creation of a Virtual Client will overwrite this existing version. However, license keys in place for the existing APM are still valid. Therefore, Scenario B outlined in the previous section can be used without the need to obtain additional license keys for the backup/restore of local, non-shared data.
SQ.5.6
Configuration
Complete configuration of the Microsoft SQL Server APM for use in a clustered environment depends on the backup/restore scenario selected for use. The points below separate the configuration requirements, based on scenario type in place:
Important:
1. Configuration of the APM in a clustered environment which houses multiple instances of Microsoft SQL Server requires additional steps. Please see the section, Configuration Requirements on page 36 for this additional information. 2. This section assumes that a Virtual Client has already been created for use with the Microsoft SQL Server APM.
32
SQ.5.6.a
Configuration for Backup/Restore Scenario A

It is necessary to configure the actual Virtual Client from the NetVault: Backup Server. 1. From the GUI on the NetVault: Backup Server, access the Backup window 2. In the Selections tab, locate the newly created Virtual Client and double-click on it to open it (or right-click on it and select the Open command from the pop-up menu). 3. Locate the Microsoft SQL Server APM icon and double-click on it to open it. 4. Right-click on the appropriate Microsoft SQL Server instance that appears in the tree to access its associated pop-up menu, and select the Configure command.
Important: Even though a Virtual Client is created for a specific, shared Microsoft SQL Server instance, all instances currently running on the machine in control of the clustered application will be revealed when the Virtual Client is browsed. Ensure that the correct shared Microsoft SQL instance is selected for the above step. This can be resolved by naming the Virtual Client to match the shared instance during its creation. Please see the section, Installation Procedure on page 29 for detailed information.
5. In the window that appears, set the desired configuration options. The options available are exactly the same as those covered in the section, Configuring the Microsoft SQL Server APM on page 10. 6. With the desired options set, click on the OK button to confirm the settings and close this window.
Configuration Synopsis (Restore Scenario A)

Once these settings have been made, a configuration file will be created and housed on the NetVault: Backup Server. As backups/restores are performed of the Virtual Client, this file will be referenced and the options made through the above process will be used.
SQ.5.6.b
Configuration for Backup/Restore Scenario B

It is necessary to configure both the actual Virtual Client from the NetVault: Backup Server as well as each member Client that is to have local Microsoft SQL Server data backed up/restored. 1. Complete steps 1 - 5, as covered in the previous section, Configuration for Backup/Restore Scenario A on page 32 to set the configuration options for the Virtual Client. 2. While still in the Selections tab of the Backup window, locate the icon for a member Client machine that was included in the Virtual Client that is to have local Microsoft SQL Server data backed up.
33
3. Right-click on this client and select Open from the pop-up menu (or doubleclick on the Client node). 4. Locate the desired database instance and right-click on it. From the pop-up menu that appears, select the Configure command.
Important:
1. In the same manner as a Virtual Client, once a member Client machine is opened, both the local Microsoft SQL Server instance(s) and those that were established as shared will be revealed. During this phase of configuration, shared instance must not be selected for configuration. Configuration of the shared instance has already been set up via the Virtual Client (i.e., in Step 1., above). 2. Microsoft SQL Server APM configuration options are set on a per instance basis. If a member Client machine contains multiple, non-shared instances that are to be backed up, it is necessary to follow these steps to set configuration options for each one. 5. In the window that appears, set the desired configuration options. The options available are exactly the same as those covered in the section, Configuring the Microsoft SQL Server APM on page 10. 6. With the desired options set, click on the OK button to confirm the settings and close this window.
Configuration Synopsis (Restore Scenario B)

Once these settings have been made, a configuration file will be created and housed on the local member Client. As backups/restores are performed of the data on this member Client, this local file will be referenced and the configuration options made through the above process will be used (i.e., not the settings made when configuring the Virtual Client).
SQ.5.7
Backup
Backing up data using the Microsoft SQL Server APM that has been set up for use in a Virtual Client is relatively simple. The only difference that should be noted is between the backup of shared data through the Virtual Client itself, and the backup of local, non-shared data on the individual member client machines. Backup of a Virtual Client - The Microsoft SQL Server APM is accessed from the Virtual Client itself and the instructions offered for a backup in Appendix E: NetVault: Backups Application Cluster Support of the NetVault: Backup - Administrators Guide for version 7.3 should be followed when backing up a Virtual Client.
34
Important: When browsing a Virtual Client in the Selections tab, NetVault: Backup will
reveal all Microsoft SQL Server data available on the machine that is currently in control of the clustered application (i.e., Microsoft SQL Server). This includes both the shared data, and any non-shared, local data on the machine. Only data items that have been established as shared within the cluster should be selected when performing a backup of the Virtual Client (i.e., do not select any non-shared data items when backing up a Virtual Client). Backup of Local, Non-Shared Microsoft SQL Data - Backup of this type of data is performed by accessing the Microsoft SQL Server APM on the actual member Client machine, in the same manner as a traditional Microsoft SQL Server APM backup. Therefore, the instructions offered in this Users Guide can be used for the backup of local, non-shared data. See the section, Backing Up Data with the Microsoft SQL Server APM on page 11 of this guide for complete details on performing a backup of this type.
Important: In the event that a member Client machine targeted for a backup is currently in control of the clustered application, all data items established as shared will be revealed when the client is browsed in the Selections tab of the Backup window. If targeting a member Client machine, ensure that shared data is not selected for a backup.
SQ.5.8
SQ.5.8.a
Figure SQ-23: Even though an individual Client machine was actually used for each backup, the restore is classified under the name of the Virtual Client in the Restore window
Restore
Restoring a Virtual Client Backup
Restoring a backup of a Virtual Client is conducted in the same manner as a restore performed to a traditional NetVault: Backup Client. All options available for a restore with the Microsoft SQL Server APM are also available with the cluster Friendly version, and data selection is performed in the same way as well. The only difference is that restorable backups of a Virtual Client are displayed in the Selections tab of the Restore window under the name of the Virtual Client, not the specific Clients that were active during each backup. When a restore job is initiated, NetVault: Backup will communicate with all member Clients, to determine which machine is currently in control of the clustered application and target this machine for the restore. All of the instructions offered in this Users Guide in reference to performing a restore can be used in the recovery of a Virtual Client. Please see the section,
NetVault: Backup Users Guide Restoring Data with the Microsoft SQL Server APM on page 17 for complete information on restoring a Microsoft SQL Server APM backup.
35
SQ.5.8.b
Restoring Data Backed up From a Member Client

A restore of this type is exactly the same as the restore of a traditional Microsoft SQL Server APM backup. The physical member client name will appear in the Selections tab of the Restore window and it can be opened to select restorable items accordingly. All of the instructions offered in this Users Guide in reference to performing a restore can be used in the recovery of this type of client data.
SQ.5.9
Multiple Shared Microsoft SQL Instances

Microsoft SQL Server makes it possible to have multiple instances of the software running at the same time. If this is the case in a target clustered environment (i.e., multiple instances are set up and running between the clients in a cluster that are to be backed up), the following special provisions, in addition to those outlined in the previous section, must be taken into account.
SQ.5.9.a
Installation Requirements
In addition to the procedures outlined in the section, Installation on page 29 and those covered in Appendix E: NetVault: Backups Application Cluster Support of the NetVault: Backup - Administrators Guide for version 7.3, in regards to creating a Virtual Client, the following steps must also be performed to successfully establish a Virtual Client in a clustered environment containing multiple shared instances. Step 1: Assign an IP Address to Each Instance - During the installation/ configuration of Microsoft SQL Server, it is necessary to assign an individual IP address to each separate instance of Microsoft SQL Server that will exist within the cluster. Be sure to take note of this IP address in regards to the instance to which it belongs. Step 2: Make Note of the Name Given to Each Instance - Prior to creating the Virtual Client, note the name of each Microsoft SQL Server instance that exists as shared within the cluster and is to be backed up/restored. Be sure to associate this name with the proper IP address.
36
Figure SQ-24: Creation of a Virtual Client for the first instance of Microsoft SQL Server in a clustered environment that contains two instances
Step 3: Create an Individual Virtual Client for Each Instance - For each instance of Microsoft SQL Server within the cluster, create a separate Virtual Client. During the creation process, ensure that the following are included: The Noted IP Address - In the Application IP Address field of the NetVault: Backup Virtual Client Installation window, input the IP Address assigned to the appropriate instance of Microsoft SQL. For example, if creating the first of two Virtual Clients for a clustered environment, the IP address assigned to the first instance would be input. Give a Name to the Virtual Client that Corresponds to the Instances Assigned Name - Input a name value in the Virtual Client Name field that will associate this Virtual Client with the specific instance. With the completion of the first Virtual Client, continue this process for all remaining instances of Microsoft SQL Server, ensuring that the proper IP address is assigned and an appropriate name is given.
Important: With the Virtual Client properly set up for use as instructed above, specific
configuration and backup instructions must also be followed in order to ensure that the proper Microsoft SQL Server instance is included in a backup job. Please thoroughly review the following Configuration Requirements (on page 36) and Backup Requirements (on page 37) sections to ensure that these steps are followed.
SQ.5.9.b
Configuration Requirements
Once the proper installation steps for this environment have been followed (i.e., as outlined in the section, Installation Requirements on page 35), it is necessary to set configuration options for each individual Virtual Client created. Regardless of backup/restore scenario in place, the following steps must be performed to ensure proper configuration of each instance. 1. From the GUI on the NetVault: Backup Server, access the Backup window. 2. In the Selections tab, all of the newly created Virtual Clients will be revealed. Locate the one that was set up for the first instance of Microsoft SQL Server and double-click on it to open it (or right-click on it and select the Open command from the pop-up menu).
NetVault: Backup Users Guide 3. Locate the MS SQL icon and double-click on it to open it.
Figure SQ-25: Two Virtual Clients created for two separate instances of Microsoft SQL Server, each with names assigned to match their corresponding instance. In this figure, the applicable instance is selected for configuration
37
4. All of the instances of Microsoft SQL Server within the cluster will be revealed (i.e., even though this Virtual Client was created specifically for the first one). Locate the first instance in the tree -- if the installation process illustrated in a previous section was followed correctly, this instances name should be similar to the name of the Virtual Client itself. Right-click on this instance and select Configure from the pop-up menu. 5. Configuration options can be set as desired in the same manner as covered in the standard Virtual Client configuration instructions above. 6. With configuration set for the first instance of Microsoft SQL Server in its corresponding Virtual Client, it is now necessary to repeat the process for all remaining instances. Repeat steps 2 - 5 for all remaining instances, ensuring that the proper instance is selected for each Virtual Client. For example, using the figure above, two Virtual Clients were created for two instances of Microsoft SQL Server. With the first configured, it would now be necessary to open the Virtual Client entitled MS_SQL_Instance_2 and then right-click on the second instance in the list (e.g., the one whose name is the same as or similar to the name of the Virtual Client, itself) in order to access its pop-up menu and the Configure command.
Configuration Synopsis
As multiple Virtual Clients are created, individual configuration files for each are then created and housed on the NetVault: Backup Server. As each Virtual Client is backed up/restored, its specific configuration file is referenced to review and apply these settings.
SQ.5.9.c
Backup Requirements
In much the same manner as illustrated in the configuration of multiple Microsoft SQL Server instances (on page 36), it is important that the correct instance be selected from a Virtual Client in order to accomplish a successful backup of that specific instance. For example, using the same example set up shown in the configuration section: Two Virtual Clients are created for two separate instances of Microsoft SQL Server that exist in the cluster. Each Virtual Client has been assigned a name that corresponds to it associated instance. From the Selections tab of the Backup window, the following would take place: 1. It has been decided that the first instance of Microsoft SQL Server is to be backed up. The Virtual Client that was created for the first instance must be accessed. This Virtual Client was named based on the name assigned to the
38
first instance by Microsoft SQL Server (i.e., as outlined in the installation instructions on page 35), which is MSSQL_Instance_1. Therefore, the Virtual Client of the same name is double-clicked to open it.
Figure SQ-26: In an environment in which multiple instances of Microsoft SQL Server exist within a cluster, the correct instance is selected from its associated Virtual Client
2. Locate the MS SQL icon and double-click on it to open it. 3. Once opened, all available instances are revealed. To perform a successful backup, the correct one must be selected. Therefore, the instance whose name corresponds to the name of the Virtual Client should be selected. 4. With the correct instance selected, the backup can be performed in the same manner as a traditional Microsoft SQL Server APM backup (i.e., the instructions offered in the section, Backing Up Data with the Microsoft SQL Server APM on page 11 of this guide can be utilized).
Important: It is not necessary to select an entire instance when backing up in this manner. The instance can be opened and individual databases can be selected. However, the correct instance must be identified and then opened to select its individual contents. SQ.5.9.d Restore Requirements
There are no specific requirements for the restore of data in a multiple instance environment. Provided the previous three sections were followed correctly, backed up data of this type should be restored the same as any other Microsoft SQL Server APM data.
39
SQ.6.0
Troubleshooting
The following table describes commonly encountered problems and possible solutions. In cases where an error occurs and is not described in this table, view the job log to extract the Microsoft SQL Server error number and then refer to the relevant Microsoft SQL Server documentation for the resolution.
Symptom Cannot open the APM to display the databases Differential backup failed or Transaction Log backup failed Reason/Symptom Solution
A NetVault: Backup error dialog Make sure the security has been box will launch containing the properly set for the APM. message: Failed to open database - check LOGS for errors. For SQL 7.0: Differential and Transaction Log backups are not allowed while the trunc. log on chkpt option is enabled. Use Database - Complete backups or disable the option in database properties. For SQL 2000/2005: Differential and Transaction Log backups are not allowed while recovery model is set to Simple in database controls. Use either Database Complete backups or change the databases recovery model. Login failed for user <username> Disable the log truncation action; this can be done through the SQL Enterprise Manager by changing the database option Truncate Log on Checkpoint or by using the sp_dboption system stored (SQL) procedure for the option trunc.log on chkpt for the database in question to FALSE (refer to Transact-SQL Help) and/or set the databases recovery model to other than Simple.
Backup failed
Make sure the password for the APM has been entered correctly.
40
Symptom
Reason/Symptom
Solution Method 1: Access the Device Management window of the NetVault GUI and perform a scan of the media targeted by the job (i.e., by rightclicking on a the target media and selecting the Scan command from the pop-up menu). NetVault stores index information for backup jobs in two locations: in the NetVault Database and on the media targeted by the backup. By performing this scan, the index information will be added to the NetVault Database. To verify this, open the Restore window and locate the specific job. If it can be browsed and a restore job set up, the scan process has corrected the problem. Method 2: If the previous method failed, it will be necessary to re-run the backup job.
Backup Once this status is revealed for Completed with backup, check the NetVault Log Warnings entries for the job to see if they display one or both of the following messages: Failed to add backup record Failed to write index of backup to the database These messages indicate that the selected data was actually backed up, but the jobs index information was not properly added by NetVault to its database. Without this index information, the data can not be properly restored.
Backup Backup and restore operations are Exclude the tempdb database Completed with not allowed on database when selecting data for backup or Warnings tempdb. restore. Restore failed Can only restore one database at Run a job for a single item only, or once, resubmit the restore job with upgrade to version 3.7 of this APM only one item selected. (this issue has been resolved).

BakBone APM For Microsoft SQL Server

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BakBone APM For Microsoft SQL Server

Caricato da

Copyright:

Formati disponibili

Redefining Data Protection

NetVault:Backup APM for Microsoft SQL Server v4.500

Users Guide for the

NVE 7009-6K 07/21-06

The Microsoft SQL Server APM

SQ.1.0 - Installing the Microsoft SQL Server APM ............................................ 6

The Microsoft SQL Server APM

SQ.6.0 - Troubleshooting ............................................................................................. 39

NetVault: Backup Users Guide

About the Microsoft SQL Server APM

The Microsoft SQL Server APM

Installing the Microsoft SQL Server APM

Setting Up the NetVault: Backup Process Manager

NetVault: Backup Users Guide

The Microsoft SQL Server APM

NetVault: Backup Users Guide

Removing the Microsoft SQL Server APM

The Microsoft SQL Server APM

Configuring the Microsoft SQL Server APM

Figure SQ-8: The Microsoft SQL Server APM Configuration window

NetVault: Backup Users Guide

Important: If the MS SQL Server itself, or a particular instance of MS SQL in a multiple

Backing Up Data with the Microsoft SQL Server APM

Step 1: Selecting Data Items for a Backup

The Microsoft SQL Server APM

Important: A Selection Set is required when an incremental backup scenario is to be used

Step 2: Setting Backup Options

The Microsoft SQL Server APM

Figure SQ-12: The options available in the Backup Method frame

NetVault: Backup Users Guide

The Microsoft SQL Server APM

NetVault: Backup Users Guide

Step 3: Finalizing and Submitting the Backup Job

Restoring Data with the Microsoft SQL Server APM

The Microsoft SQL Server APM

Phase 1: Understanding the Recovery of Various Types of Backup

Overview of Available Backup and Recovery Scenarios

NetVault: Backup Users Guide

The Microsoft SQL Server APM

Job Type Transaction Log Backup and Recovery

Overall Outcome: Fastest Backup, Slower Recovery

Phase 2: Restore Procedure

NetVault: Backup Users Guide

The Restore Options Tab

The Microsoft SQL Server APM

NetVault: Backup Users Guide

Figure SQ-16: The options available in the Restore Method frame

Restoring the Master Database

The Microsoft SQL Server APM

NetVault: Backup Users Guide

Important: If attempting to rename a restore of a Snapshot backup (i.e., the Snapshot

The Microsoft SQL Server APM

Renaming and Relocating a Restore

Restoring Data Files and Log Files to Different Locations

NetVault: Backup Users Guide

The Microsoft SQL Server APM and Application Cluster Support

The Microsoft SQL Server APM

Application Cluster Support - An Overview

About this Section of the Guide

NetVault: Backup Users Guide

Installation Specifics - Creating a Virtual Client

The Microsoft SQL Server APM