A LiteSpeed backup template contains a set of backup parameters that describe the types of databases and the types of backups you want to perform.
Note: This feature supports disk, TSM Backup, TSM Archive and cloud storage destinations. |
Backup Templates can be easily updated and changes deployed to all instances. LiteSpeed tracks the instances where each template is deployed, making re-deployment very easy. Backup Templates can also be easily removed from an instance if they are no longer required.
Using LiteSpeed backup templates in your backup routine can help you manage multiple SQL Server instances. You do not have to manage backup jobs for each database or manage maintenance plans for one server at a time. Instead, create and deploy a backup template.
If your company's policy changes, you can quickly edit the template to comply with the new standards and re-deploy. LiteSpeed versions the templates and the deployments, so it is easy to see if an instance needs to be updated.
To create a Backup Template
Select the Backup Manager pane (CTRL+1).
In the Backup Templates tab, click New on the toolbar. If you do not use the central repository, click Backup Templates on the toolbar.
Review the following additional information about the backup type and destination:
Backup Type |
Select what backups will occur after you deploy this template on a server instance.
The default backup name and description use the following information:
You can specify custom backup name and description using both the LiteSpeed variables and text. For more information, see LiteSpeed Variables. |
Select Databases |
Select databases you want to back up. NOTES:
|
Backup Destination |
Decide whether you want to save a default backup destination name in the template or specify it at the deployment time. If you specify a backup destination in a template, you can override backup destinations for each instance at deployment time. Each Backup Template remembers if you override these settings to make future redeployments easier. Backup file name as well as the backup folder can include the %SERVER% variable, that may be particularly useful when backing up many instances to the same network share. NOTE: Fast Compression handles the naming of files automatically. For more information, see Backup Files and Folders. You can either supply the backup destination at deployment time or save the default backup destination in the template. The backup destinations include disk, cloud, TSM Backup and TSM Archive.
Use the Overwrite setting to overwrite existing media when a full backup template is created. Click Add Mirror to copy the entire backup file to multiple locations. Backup Templates support backup mirroring to disk or the cloud, same as for the backup of individual databases. For more information, see About Backing Up/Restoring Databases. |
Set Backup options. Review the following for additional information:
Optimize the Object Level Recovery speed |
Select to create an index of objects in the backup file. This option is only available for LiteSpeed backups. The default is enabled. NOTE: Before you can recover objects or execute a SELECT statement, you must read the backup file to create an index of restorable objects. The index is an .lsm file. During the backup process the .lsm file is created in the temp directory and attached to the backup file after the backup is completed. If you select this option, LiteSpeed uses the index in the backup file to read the backup file, which makes the object level recovery process much faster. |
Create Double Click Restore executable |
Select to create a Double Click Restore Loader that allows you to restore a backup on a server instance that does not have LiteSpeed installed. If you additionally select to Create one Double-Click Restore executable file then note the following warning. The executable may be greater than 4GB for large databases. Windows Server is unable to run executable files larger than 4GB. However, the file will be convertible/restorable by LiteSpeed file. For more information, see Double Click Restore Executables. NOTE: A Double Click Restore can only be created for a disk file. |
Perform checksum before writing to media |
Select to verify checksums when a backup is created. Additionally, you can control the response to an error. If you select the Continue on error option, the backup is executed despite encountering an invalid backup checksum. |
Continue on error |
Select this option to continue running the backup even if an invalid checksum is encountered. |
Fast Compression Type |
Select whether you prefer to create a unique file for each backup or you prefer to manage a single file for each backup set (a backup set is composed of one full database backup plus all associated differential backups):
The Self-Contained Backup Sets option automatically verifies the Full backup exists. The Separate Backup Files option performs the same validation by default.
| |
Fast Compression Backup Options |
You can set the following thresholds to define when to issue a full backup:
Fast Compression measures the amount of data change by either querying SQL Server or by comparing the size of the last differential to the last full backup. The default option is to query actual data pages. It provides the most accurate way to determine the amount of data change. If the query fails for any reason, Fast Compression will automatically run a size comparison to the last Differential backup. For example, set this parameter to 20%, and should the database change by 20% or more, Fast Compression will automatically run a Full backup. The larger the threshold, the larger the differential backups can grow before Fast Compression triggers the next Full backup. Regardless of how much underlying database data has changed, when exceeding the maximum interval (in days) between full backups, Fast Compression will force a full backup. NOTES:
Select the Extension for backup files checkbox to enter or change the backup file name extension. The default is set to bkp. NOTE: You can select the backup file extension for Fast Compression and make the new default, bak, for new items. For an existing item that does not have an extension defined, bkp is displayed when the item is edited (maintenance plans and templates). | |
Backup Escalation |
This option causes LiteSpeed to issue a full backup, if one of the following problems is discovered in the current backup set:
NOTE: If a problem is detected and a full backup is created through escalation, an error will be returned. | |
Verification and Cleanup |
TIP: "Cleanup" means Smart Cleanup Policies or Smart Cleanup. For more information, refer to Smart Cleanup Policies. Make sure the backup files in the backup set have integrity. This provides an added level of insurance the backup files can be restored. Verification failures appear in the LiteSpeed UI Console and, optionally, as job failure notifications. A verification failure after a differential backup will trigger the backup escalation process, if selected. The Verification options include:
The Cleanup options include:
|
Set Compression and Encryption options. Note that you can specify both the compression level and Adaptive Compression option. LiteSpeed will select and use Adaptive Compression if it is supported by the target server LiteSpeed version. Otherwise, the specified compression level will be used.
Adaptive Compression |
LiteSpeed automatically selects the optimal compression based on throughput and CPU usage and optimize backups either for size or for speed (default). NOTE: Adaptive Compression is only available with LiteSpeed 6.5 or later; Enterprise license. | |
Compression level |
Select 0 for no compression or 1-8 (default 2) to compress the file. For more information, see Compression Methods. NOTE: Higher compression levels result in smaller backup files, but they also take longer to complete.
| |
Encrypt backup |
Select this checkbox to encrypt the backup. Then, select the encryption level and enter the encryption password. |
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. |
Comment |
User comment written into the backup header. Is blank by default. |
Logging level |
Select a logging level to define what events to log for the console. You can find the log events in the Application Event Log. |
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.
|
TIPS:
|
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.
Configure notification options. You can select an existing notification profile or specify operators at deployment.
TIP: Variables defined in the maintenance plan can be used to format the Subject Line. There is also help information inside the task that lists the available Subject Line variables.
NOTE: The SQL Server Agent must be configured to send email using Database Mail. Review the following for additional information:
For a Differential backup ("Full" backup type)
For a Transaction Log backup
You can set the behavior for databases without existing full backup (new databases): raise an error (default), raise a warning, suppress an error. Do this at the T-Log Destination step with the "Sequence check" option.
Specify backup cleanup options. For more information, see Smart Cleanup Policies.
NOTE: The "Do not delete if Archive bit is set" option is available for full and fast compression backups in the Backup Template when it is deployed as a maintenance plan. If a backup template is created for a full backup with the option "Do not delete if Archive bit is set" selected, and the backup template is deployed as a job, the option is passed to the job's script to run the xp_slsSmartCleanup procedure. When the backup template is deployed as a maintenance plan, the option is omitted because the “Remove files older than” option (not the SmartCleanup option) for full backup is run in the maintenance plan.
Backup Templates are saved in the central repository (if one is used) and available for editing and deployment on the Backup Templates tab in the Backup Manager pane (CTRL+1). If the central repository is not configured, LiteSpeed will save each template as file.
In the Backup Templates tab, you can create, edit, clone, import, export and deploy templates, view the template contents, deployment details and modification history.
NOTES:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center