LiteSpeed for SQL Server(7.5) How to Diagnose & Troubleshoot Backup

Transcription

1 LiteSpeed for SQL Server(7.5) How to Diagnose & Troubleshoot Backup

2 Slide Index Learning objectives- slide #3 Backup functional overview- slides # 9 Common issues- slide #17 Common backup error explanation- slides #18 Common install issues- slide #23 Troubleshooting Setup and Backup checklist slide #24 Prerequisites for contacting support-slides # 29 2

3 Learning Objectives How to Diagnose & Troubleshoot Upon completion of this presentation, the student should be able to: Identify the actual problem the user has reported. Create and read the LiteSpeed log file. Search the knowledge base. Identify, troubleshoot, and resolve common LiteSpeed Backup problems. Solve the issue or gather the necessary information to escalate the case. 3

4 Installation Pre-requisites LiteSpeed Graphic Requirements To properly use the LiteSpeed Console, it is recommended that you set your system s screen resolution to 1280 x 1024 or higher. With low resolution settings, you may experience display issues when using the LiteSpeed Console. Permissions All target machines must have O/S permissions set that will allow the user to install software components. System Memory Memory requirements on a target system can vary based on the intended use. User Permission SysAdmin equivalent. 4

5 Installation Pre-requisites cont. Disable Anti-virus Software It is recommended that you disable the anti-virus software before installing or upgrading LiteSpeed. The LiteSpeed installation process may conflict with the anti-virus software and various LiteSpeed operations may not function properly after the installation. Ensure TCP/IP Connectivity and Name Resolution Ensure that good TCP/IP connectivity and Name Resolution exists between the LiteSpeed Server and each potential LiteSpeed Client. Check Backup Device Mapping/Connections Determine what backup devices are to be used (for example, tape libraries and standalone drives) and map them out. These devices can be attached to the LiteSpeed Server or Clients. Ensure that these devices are properly connected and functional. This can be done using any native O/S tool for minimal backup operations on the device. If a native backup tools cannot see an attached backup device, then neither will LiteSpeed. Additional platform specific requirements can be found in the LiteSpeed Installation/Upgrade Guide. 5

6 LiteSpeed Features 1. Fast Compression - Achieve significant reductions in backup size and time with the highest degree of recovery. 2. Backup Templates - Define backup standards and easily deploy to multiple instances; templates are easily updated and re-deployed as needed, making multi-instance backup management simple. 3. SmartCleanup - Remove backups from disk with customized retention parameters without disrupting backup integrity. 4. Network Resilience - Automate recovery from I/O problems. 5. Adaptive Compression - Compress data with new Adaptive Compression feature which continually monitors backups to maintain optimal backup performance or use one our eight compression levels to select the exact compression you need 6. Restore as Compressed - Restore a NetVault LiteSpeed backup as a compressed, read-only database to save valuable disk space 7. SQL Server 2012 AlwaysOn Availability Groups Easily back up the databases on the preferred instances in SQL Server 2012 AlwaysOn Availability Groups 6

7 LiteSpeed Features continues 1. Object-Level Recovery - Restore individual objects and query backup files without doing a database restore. 2. Transaction Log Reader - Roll back transactions to recover data and objects from operations that could adversely affect the database 3. Centralized Reporting - Track all backup activity for easy review with the comprehensive reporting option. 4. Intuitive Log Shipping Monitor - Configure and monitor log shipping plans and latency alerting; add or remove subscribers on demand. 5. Robust Encryption - Secure data with nine levels of encryption, up to AES 256-bit, without impacting performance. 6. Double-Click Restore (Exclusive) - Create portable database backup files; restore simply by double-clicking on the file. 7. File Attachments (Exclusive) - Attach externally stored files and folders as a part of any NetVault LiteSpeed backup. 7

8 LiteSpeed Features continues 1. IBM Tivoli Storage Manager (TSM) Integration - Integrate directly with IBM s Tivoli Storage Manager. 2. Backup Analyzer - Test compression levels and backup locations to determine optimal backup settings and identify bottlenecks. 3. Job Manager - View and manage jobs from multiple instances using grid or calendar views. 4. NetVault LiteSpeed Engine for SQL Server - Gain an optional, native backup engine to use existing SQL Server backup commands and scripts, including maintenance plans, while taking advantage of NetVault LiteSpeed s compression and encryption. 5. NetVault LiteSpeed for SQL Server High Availability Edition with NetVault FastRecover - Leverage our patented FlashRestore Continuous Data Protection (CDP) technology to recover databases to any point in time in seconds. 8

9 (LiteSpeed) Functional Overview Architecture The diagram shows how LiteSpeed components communicate to SQL Server to create a backup and how data gets into the local repository and then is pushed to the central repository. 9

10 (LiteSpeed) Functional Overview Architecture The diagram shows the LiteSpeed components: 1. Backup Manager. 2. Log Shipping. 3. Object Level Recovery. 4. Maintenance Plans. 5. Job Manager. 6. Log Reader. 10

11 (LiteSpeed) Functional Overview Backup Backup components: 1. LiteSpeed console. 2. Template. 3. Customize jobs. 4. Command prompt. 5. Multiple database backup from console 11

12 (LiteSpeed) Functional Overview Backup - continue Backup Manager: 1. LiteSpeed console. 2. Sample script using GUI; exec = = N'DailyDB Full Database = N'Full Backup of DailyDB on 10/31/ :51:16 = = = = N'STATS = 10' GO 12

13 (LiteSpeed) Functional Overview Backup - continue Backup Manager: 1. Backup using template. 2. You will need to deploy after done with setup. 13

14 (LiteSpeed) Functional Overview Backup - continue Backup Manager: 1. Customize backup job. 2. You can paste the sample script in; exec = = = = N'STATS = 10' GO 14

15 (LiteSpeed) Functional Overview Backup - continue Backup Manager: 1. Command prompt backup 2. Sample script; sqllitespeed.exe -B Database -T -D Northwind -F "C:\temp\Northwind.bak" 15

16 (LiteSpeed) Functional Overview Backup - continue Backup Manager: 1. Multiple backup. 2. Sample script; exec = = N'master - Full Database = N'Full Backup of master on 10/31/2012 4:01:45 = 2,@filename = = = N'STATS = 10' GO exec = = N'model - Full Database = N'Full Backup of model on 10/31/2012 4:01:45 = 2,@filename = = = N'STATS = 10' GO exec = = N'msdb - Full Database = N'Full Backup of msdb on 10/31/2012 4:01:45 = 2,@filename = = = N'STATS = 10' 16

17 Common Backup issues Failed to create VDI, error 995 or x Failed to login. Unable to find previous full backup, using Fast Compression. Failed to cleanup old backup files. 17

18 Common Backup Error Explanation 18

19 Failed to create VDI This means that SQLServer memtoleave does not have enough resources to produce a VDI package. Sometimes this is normal, as the resource available, and the backup will run fine. Other time, you may have to allocate more virtual memory to SQLServer. Temporary workaround is to either reduce the maxtransfersize parameter from your backup setting. 19

20 Failed to login This can happen when running a full backup and it failed to connect to the instance. A similar problem can also happen if the LiteSpeed engine is no longer available. Maintenance plans will also fail when a connection is no longer available. 20

21 Failed to find previous full backup This may mean you are trying to run a differential backup using a Fast Compression and there is no full backup in the folder. This might be because a full backup has not been run, the full backup has been removed, or the backup was moved to a new location. 21

22 Failed to clean up old backup files The Maintenance plan did not clean up old backup files. This may also mean backup files are not available for clean up or you do not have the proper permission to remove it. 22

23 Common Install Issues For cluster environment, failed to connect registry. Installer file is not supported for 32 or 64bit platform. Setup could not find SQL instance. Use wrong installer package. Don t have access to setup. 23

24 Troubleshooting Setup and Backup checklist 24

25 Troubleshooting Checklists Directory/Install structure The LiteSpeed home directory is where LiteSpeed is installed. The default locations are: Windows C:Program Files /Quest Software /LiteSpeed SQL Server Where are executables: [LiteSpeed Home]/engine Where are log files: [C:Documents and Settings/All Users/Application Data/Quest Software/LiteSpeed/SQL Server/logs Log dumps go to the [LiteSpeed Home]/logs/ directory 25

26 LiteSpeed Logs Various LiteSpeed processes send messages to the Server about the operations taking place, and report any problems or errors encountered during these operations. The system logs reside in the.../logs directory on the LiteSpeed Server (where... represents the LiteSpeed installation directory). The log files are stored in binary format and named SLS*.log with the latest time. For example, when a backup with verbose turn on, it will create a log like SLS Log For installation log, it will be like SLSInstaller txt System Logs are useful for tracking activities and troubleshooting problems. You can view the system logs from the eventviewer application window. 26

27 Using the Knowledge Base Go to: Search for an error message 27

28 LiteSpeed Trace When LiteSpeed logs don t give you enough information to identify the problem, it may be necessary to get a trace log. When submitting a subcase a trace is usually required. Please do not ask for a trace unless it is required. Unless you have experience with reading the trace files it will be difficult to make sense of it. A trace will use up an ample amount of disk space. Please verify the trace directory listed in the General tab has plenty of disk space. Only generate trace/debug files when requested. 28

29 Prerequisites for Contacting Support 29

30 When opening a support case submit the following: Problem Description Diagnostic logs, screenshots, etc. Environmental details (LiteSpeed version, SQL Server version, and Service pack applied.) Issue severity and customer business impact, timeframes, etc. If a performance issue, provide specific details as specified in the case. 30

31 FAQ What is required in order to open a support case? When opening a support case, we request the environment information (Operating systems, versions, software/database versions, etc), binary log dump, and a detailed explanation of the problem. 31

32 Summary In this lesson we learned: How to create backup and read LiteSpeed Backup Log Dumps. Search the knowledge base Identify, troubleshoot, and resolve common LiteSpeed Backup problems. 32