Higher compression levels result in smaller backup files, but they also may consume additional CPU. If the server does not have sufficient CPU, then the backup may take longer to complete. The Backup Analyzer evaluates different settings, such as compression level, striping, and backup destinations, to help you determine optimal backup settings.
NOTE: When running the Backup Analyzer, follow these guidelines for the best results:
Minimum: 1 GB sample size.
Recommendation: 10 GB sample size. The combination of compression levels, encryption options, and backup locations should be considered. For example, if you sample 4 GB of data with 10 different tests, LiteSpeed will take the same amount of time as it takes to back up 40 GB. On very large databases, you can speed up the analysis by reducing the number of backup combinations or by reducing the amount of sample data.
The Backup Analyzer wizard guides you through selecting the backup parameters to test. The wizard tests all of the different combinations of your selected parameters by backing up a portion of the database. It does not interfere with existing backup schedules or sets.
To run the Backup Analyzer wizard
Select the Backup Manager pane (CTRL+1).
Right-click the database and select Backup Analyzer Wizard.
Tips:
Review the following additional information about the advanced options:
Compression threads |
Determines the number of threads used for the backup. You will achieve the best results by specifying multiple threads, but the exact value depends on several factors including: processors available, affinity setting, compression level, encryption settings, IO device speed, and SQL Server responsiveness. The default is n-1 threads, where n is the number of processors. |
Max transfer size |
Enter the maximum backup file size in bytes. . The possible values are multiples of 65536 bytes (64 KB) ranging up to 4,194,304 bytes (4 MB). The default is 1048576. |
Buffer count |
Enter the number of SQL Server buffers available for a LiteSpeed operation. The default is set by SQL Server. |
CPU throttle |
Enter the maximum percentage of CPU that LiteSpeed can use for the process. The default is 100. |
Processor affinity |
Click to select which processors LiteSpeed can use. The default is 0, which allows LiteSpeed to use all available system processors. |
Processor priority |
Select the priority of the backup over other transactions or processes running on the same server. The default is Normal. |
Network resilience |
If LiteSpeed fails to write disk backups or reads from disk, it waits and retries the operation. You can enable and disable and control the number of times to retry and the amount of time to wait before retrying.
|
TIP: Before you start tuning the CPU Throttle or Affinity parameters to adjust backup performance, try limiting the number of threads. If you decide to use an affinity value other than default, it is recommended that you limit the threading as well. |
NOTE: LiteSpeed defaults typically result in the best performance. You should only modify advanced options after careful planning and testing. For more information, see Configure LiteSpeed Defaults.
NOTE: After the required number of bytes is received for analysis, the process is intentionally aborted. This generates the VDI error messages in the LiteSpeed log files and the SQL Server error log. Please ignore them.
You can schedule analyzing from within the Backup Analyzer Wizard. An SQL Server job with the name "LiteSpeed Analyzer SERVERNAME.DATABASENAME" is created. View the list of Backup Analyzer jobs directly from the Backup Analyzer tab by clicking "Show Analyzer Jobs." Right-click on the job. You can change schedule, start/stop, disable or even delete the job. To view the script, select the "View in Job Manager" option and open the job properties from the Job Manager module. You can then go to the job step details.
The Backup Analyzer tab consists of the toolbar, graph, and grid. The Backup Analyzer toolbar is used to select the following items:
The Backup Analyzer tab presents the test results in a graph and grid format:
Graph—Displays the backup duration and compression amount for each test in a bar graph so you can easily compare the results between size and duration. If you hover the mouse over the bar graph, test number, size, and duration are displayed. If you select a test in the grid, LiteSpeed indicates the corresponding test in the bar graph with a yellow border around it. You can view previous tests by changing the Existing test field.
Grid—Displays the details of each test in columnar format. LiteSpeed indicates its recommendation with the number indicated first in the Test Number column and a yellow box around the test bar graph. Review the following for additional information:
Tip: .Use the Grid horizontal scroll bar to view other table columns. |
Column | Description |
---|---|
Test Number |
The number assigned by the Backup Analyzer. |
Level |
The compression level that is used for a particular database backup test. |
Encryption |
Indicates enabled encryption for the database backup. |
Estimated Duration |
The approximate time allotted to run the database backup. |
Estimated Backup Size (MB) |
The approximate size of the backed up database. |
Database Size (MB) |
The amount of disk space the database occupies. |
Compression (MB) |
The amount of disk space you can save with this compression ratio. |
Compression (%) |
Data compression ratio. |
Read Speed (MB/Sec) | Maximum read speed. |
Throughput (MB/Sec) | Actual speed of processing data (compression and encryption). |
Backup Speed (MB/Sec) | Virtual write speed of the backup. Compare this value to Throughput and Read Speed to determine if you are experiencing a write-bound issue. |
Write Speed (MB/Sec) | Actual write speed. It shows how quickly the compressed data stream is written to the destination disk. |
Stripes | Number of stripes associated with the backup. |
Destination | Backup destination directory location. |
Threads | Number of threads associated with the backup. |
You can double-click a row for more information about the test.
Tip: For panes that have grids, you can sort, group, move, and remove the columns:
|
LiteSpeed provides you with many flexible options for selecting databases to include in a backup job or in a backup task of a maintenance plan. If there are conflicting conditions (for example, you selected to back up databases, matching the 'DirectD*' pattern and skip read-only databases, while the name of a read-only database matches the pattern), the Exclude condition wins over Include.
NOTE: LiteSpeed wizards may have different Exclude/Include options for selecting databases.
You can specify databases:
Using one of the following built-in groups:
Using wildcard or regular expressions. For more information, see Use Wildcard and Regular Expressions in LiteSpeed.
NOTE: New user databases will also be backed up as part of the "All databases" or "User databases" groups or if they match the specified pattern, unless they are excluded by an Exclude option. For more information, see Exclude Databases.
Depending on the LiteSpeed wizard, you cannot mix selection methods. Instead, you can schedule several subplans or jobs using different selection methods.
Using these options you can further define databases you want to back up.
You can exclude the following databases:
NOTE: Mirror databases and database snapshots are automatically excluded.
Versions 7.0 and later of LiteSpeed provide enhanced support for databases participating in AlwaysOn availability groups (SQL Server 2012 and above). You can include availability databases in a maintenance plan or a backup job, as well as perform backups on individual replicas.
In maintenance plans and backup templates, the following options define which replicas are eligible for backup:
NOTES:
About Creating Maintenance Plans
You can configure LiteSpeed to only back up databases that match the specified pattern. Using wildcard and regular expressions is particularly helpful when there are databases with similar names on the same instance or on multiple instances.
Tips:
You can use wildcard characters '?' and '*' to select databases you want to back up. For example, "litespeed*" will include all databases that start with "litespeed" or "LiteSpeed".
Using regular expressions can provide you with more flexibility when selecting databases. For example, the following expressions will include a database if its name:
Begins with "LiteSpeed".
^LiteSpeed
Ends with "_PUBLISHER".
_PUBLISHER$
Begins with "LiteSpeed" followed by digits.
^LiteSpeed\d+
Contains any number within the range 828500 to 828549.
8285[0-4][0-9]
Begins with "LiteSpeed" or "Quest", except "QuestSoftwareCMSS".
^(?!QuestSoftwareCMSS)(Quest|LiteSpeed)
NOTES:
Click here for information about the regular expression constructs.
Review the following for additional information:
Construct | Description |
---|---|
^ |
The character following this construct is at the beginning of the document or new line. Text: no cat can catch a crow Expression: ^\w+ Matches: no |
$ |
The character followed by this construct is at the end of the string. Text: no cat can catch a crow Expression: \w+$ Matches: crow |
(normal characters) |
Characters match themselves, except for the following: ^ . * + ? { [ ( | ) \ $ |
\ |
The character immediately following it, when that character is not an escaped character. Expression: \* Matches: * |
\w |
Any word character (A - Z and a - z), digits, and underscores. Text: no cat can catch a crow Expression: ca\w+ Matches: cat, can, catch |
\W |
Any non-word character. Text: 9pm @ RockCafe Expression: \W Matches: @ |
\d |
Any digit. Text: APR-2012 Expression: \d\d\d\d Matches: 2012 |
\D |
Any non-digit. Text: APR-2012 Expression: \D\D\D Matches: APR |
\s |
Any whitespace character. Text: no cat can catch a crow Expression: c\w\w\s Matches: "cat " and "can "(both matches include the space) |
\S |
Any non-whitespace character. Text: no cat can catch a crow Expression: c\S+ Matches: cat, can, catch, crow |
[ ] |
Any character within the brackets. Expression: p[ai]ck Matches: pick, pack |
[ - ] |
Any character within the specified range. [0-9a-fA-F] matches a single hexadecimal digit, without case sensitivity. Expression: b[a-z]ttle Matches: battle, bottle NOTE: The - character is considered a literal character if it used as the first or last character within the brackets, or if it is escaped with a backslash. |
[^ ] |
Any character that is not in the specified set of characters. Expression: d[^u]g Matches: dog and dig but not dug |
. |
Any single character. When preceded with the escape character (\), it is equivalent to a period character. Expression: d.g Matches: dog, dig, and dug |
* |
Zero or more matches of the preceding character. Expression: a*ha Matches: ha, aha, aaha, aaaha, etc. |
? |
Zero or one matches of the preceding character. Expression: colou?r Matches: color and colour |
+ |
One or more matches of the preceding character. Expression: goo+gle Matches: google, gooogle, etc. |
{n} |
The exact number of matches for the preceding character. Text: he had to go too far Expression: o{2} Matches: oo in "too" |
{n,m} |
The preceding character must match at least "n" times but no more than "m" times. Expression: mo{2,3}n Matches: moon and mooon, but not mon or moooon |
( ) |
Matches subexpression. |
| |
Matches any of the alternate expressions. Expression: theat(er|re) Matches: theater and theatre |
(?# ) |
A comment within a regular expression. The comment ends after the first closing parenthesis. Expression: theat(er|re)(?# using this example a second time) Matches: theater and theatre |
(?= ) |
A zero-width positive lookahead assertion. Expression: ^(?=.{32}$)(\d+) Matches: numbers at the beginning of any line which is exactly 32 characters long |
(?! ) |
A zero-width negative lookahead assertion. Expression: ^(?!test).+ Matches: any line that does not begin with "test" |
For more information about regular expressions, see |
Back Up Databases Using Maintenance Plans
Multi-Database Backup launches the Backup wizard which allows you to configure backup options for several databases at once.
For each database, LiteSpeed generates uniquely named backup files to avoid collision.
NOTE: Fast Compression is now available for multi-database backup in the UI.
To back up multiple databases
In case you select to schedule the backups to run at the specified times, the wizard creates a job with 'Selected databases' appended to the job name.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center