Chat now with support
Chat mit Support

LiteSpeed for SQL Server 8.9.7 - User Guide

About Backing Up/Restoring with LiteSpeed LiteSpeed User Interface Configure LiteSpeed for First Use Cloud Back Up Databases Automate Maintenance Tasks Restore Databases Restore Objects View Activity and History Use Command-Line Interface Use Extended Stored Procedures Troubleshoot LiteSpeed Review Additional Resources

View Activity and History

The LiteSpeed UI Console provides information about your backup processes in the Backup Manager tabs. Depending on what tree level and tab you select, you can view statistics on processes that fail or succeed, the amount of disk space you save, a list of all of the jobs for a server instance or database, and additional information.

Troubleshooting: If you upgraded from a previous version of LiteSpeed, the timeline may not automatically display all of your activity. For more information, see 4.x jobs not displayed. on what could be missing and how to fix it.

You can view the backup activity and history by selecting the Backup Manager Server Tools Ribbon. Information about a category, subcategory, database, server instance, server group, or all of your server instances by selecting the appropriate level in the tree.

Tab Name

Available Level

Description

Overview

All

Displays information about the backup volume savings, successful jobs, and failed jobs.

Under Database Properties, see the last backup date.

You can view information about different dates by changing the Period field or select the dates from a calendar.

Databases

Server instance

Lists all of the server instance's databases with their state, recovery model, device, backup destination and last backup date. Print this table or export to Excel.

You can right click on any instance and select backup, multi-database backup, restore, automated restore, backup analyzer, display backup/restore jobs, assign categories (available in some cases), refresh, properties, and activity.

LiteSpeed Activity

All

 

Displays all activity for the selected parameters, including activity type and status, duration, compression ratio, backup throughput (uncompressed backup size to backup duration ratio), Windows domain or SQL Server account that was used to initiate the backup or restore operation, and more.

You can change the parameters in the following fields:

  • Period — Select the time span, or select dates from a calendar. The options are all, last hour, last 4 hours, last 8 hours, last 24 hours, last 48 hours, last 72 hours, last week, last 2 weeks, and last month.

  • Report type — Select the type of activity to display. Select as a group: backup, restore, verify, and check database. Individually select: backup, restore, verify, check database, smart cleanup, maintenance plans, DTS packages, LiteSpeed jobs, log shipping plans, shrink database, update statistics, rebuild index, and reorganize index. Select Restore by Source to view restore and verify activity with restore destination for the selected instance/database.

  • Source — Select the type of backups to display, such as all, LiteSpeed or native SQL Server backups.

  • Status — View total instance status including all, success, warning, failure, and in progress.

  • Replica - Select Availability Group Replica to display activities. (Available in case of Availability Group database replica selected in Server tree and Central repopository).

You can right click on any instance and select: view in timeline, view details, and re-execute backup.

Tips:

  • To re-execute any successful or failed (and fast compression) backup, right-click the activity and select Re-execute Backup... You can edit the script if needed and run it immediately as a SQL Agent job or run it in the background. Note that the Re-execute Backup... menu item is only visible for LiteSpeed backups, and is enabled only for backups that were executed by using t-sql. If the LiteSpeed backup was executed using the command-line then the menu is disabled.
  • To verify the backup, right-click the successful backup activity and select Verify Backup... You can edit the script if needed and run it immediately as a SQL Agent job or run it in the background. Note that the Verify Backup... menu item is only visible for LiteSpeed backups (Full, Diff, Log), and is enabled only for backups that were executed by using t-sql. If the LiteSpeed backup was executed using the command-line then the menu is disabled. Verify Backup is supported for Disk, Cloud and TSM Backup/Archive backups.
  • To view information about the native SQL Server backups and restores in the LiteSpeed UI Console, run the Instance Configuration wizard from the start menu and configure the local repository to be updated via a SQL Server job. For more information, see Configure Server Instances.
  • To view information about backups performed on all availability group replicas select any database replica of the availability group at the Backup ManagerServer tree.

If you selected a database or server instance in the navigation pane, the tab also displays a timeline of activity. The timeline displays backups and restores from the past and those scheduled to occur in the future.

You can hover over an item for additional information about it. Right-click anywhere in the timeline to navigate to a date, change the time scale, or rotate the name of the databases.

Backup Templates

All

Displays the LiteSpeed Backup templates stored in the central repository. For more information, see Create Backup Templates.

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:

  • The Backup Templates tab is only available, if the central repository is configured and selected for use. For more information, see About Collecting Statistics in Repositories. To edit, deploy or remove a template when the central repository is not used, click beside Backup Templates on the toolbar and select the appropriate option.
  • The template deployment history is not exported when you export a template.
Reports Server group and Server instance

Displays the reports area.

Compliance report. Displays status of databases at the selected SQL Server instance or group,

You can change the parameters in the following fields:

  • Period — select the time span, or select dates from a calendar. The options are all time, last hour, last 4 hours, last 8 hours, last 24 hours, last 48 hours, last 72 hours, last week, last 2 weeks, and last month.

  • Status — View total database status including all, green, yellow, and red. Database status can be set at General Options in Show database status area.

Note: The Reports tab is only available, if the central repository is configured and selected for use. For more information, see About Collecting Statistics in Repositories.

Backup Browser

Server instance

Displays backup directories and current backup files. You can restore the backup file or begin object level recovery from the files listed in the tab. You can also add directories, delete directories, or set a default directory. NOTE: Backup directory also can be added from the Backup location browse dialogs. Make sure that prefered SQL Server is selected before adding the new backup directory location through the Backup location browse dialog

After expending a directory and making a backup visible, you can right click on the backup and select restore, view content, convert to double click restore backup, and convert to native backup.

LiteSpeed Jobs

Server instance and Database

Lists all scheduled jobs. You can select different job types in the Jobs filter field.

Right click a job to select the options: change schedule, start, stop, enable jobs, disable jobs, delete, and view in job manager.

Further list, backup template, backup history, and backup analyzer information is provided in the following table.

Tab Name

Available Level

Description

List

Server group

Lists the instances in the server group with their display name, authentication method, SQL Server version, LiteSpeed version, and number of databases.

Backup History

Database

Lists all backups with their date and destination, including native SQL Server backups performed through LiteSpeed. The list also includes backups that have been replaced. You can view information about different dates by changing the Period field or select the dates from a calendar.

Tips:

  • To view information about backups performed on all availability group replicas select any database replica of the availability group at the Backup ManagerServer tree.
  • Instance Name column shows in case of availability group replica has been selected in Server tree.

Backup Analyzer

Database

Analyzes different settings, such as compression level, striping, and backup destinations, to determine which settings have the best compression and duration values. For more information, see Test Optimal Backup Settings.

You can group server instances in the navigation pane tree based on their category or server group. Categories are similar to server groups, but they offer different features. For more information, see Change Server Instance Grouping Methods. 

Tip: For panes that have grids, you can sort, group, move, and remove the columns:

  • To sort and group the records, right-click a column header and select the appropriate options.
  • To sort records against multiple columns, click column headers while holding the SHIFT key. For example, to sort by type and then by name, click the Type column header and then SHIFT+click the Name column header.
  • To add or remove columns, right-click a column header and select Column Chooser. Add a column by dragging it from the list into the column headers. Remove a column by dragging its column header into the list.
  • To move a column, drag the column header to the new location.
  • After you refine the report criteria, you can print the results or export them to Excel. In addition, the tab has a timeline that displays the activity for the selected parameters by their date.

 

View Activity and History

You can view information about the current state of existing maintenance plans and their execution history (CTRL+4).

Select a group, instance, or maintenance plan in the tree view to display the following tabs:

Tab

Description

Overview

  • At a group and instance level—Displays information about the backup volume savings, successful jobs, and failed jobs.
  • At a maintenance plan level—Displays maintenance plan latest status, name, owner, creation date, and last run date. 

You can view information about different dates by changing the Period field or clicking to select the dates from a calendar.

Maintenance Plans

Lists all maintenance plans for the server instance.

History

Displays execution history of the maintenance plans for the server instance.

NOTE: To view execution history of every task in a subplan, configure extended logging. Reporting and Logging in Maintenance Plans

Design

Create and edit maintenance plans.

NOTE: If you receive a message that the server does not exist or access is denied, make sure the instance is registered and connected.

 

Use Command-Line Interface

LiteSpeed allows you to perform various tasks directly from the command-line interface (CLI).

NOTES:

  • You must run commands on the server instance on which you want to perform activity.
  • Review the Syntax sections to see which arguments are mandatory, which are optional, and which are mutually exclusive. Mutually exclusive arguments are separated by a vertical bar. Optional arguments are enclosed in square brackets. Round brackets are used to group arguments.
  • Review the Arguments sections for more information about the arguments and accepted values.

To perform tasks using the CLI

  1. Change the directory until you are in the directory containing the LiteSpeed command-line utility (Usually, C:\Program Files\Quest Software\LiteSpeed\SQL Server\Engine).

  2. Run a LiteSpeed utility with appropriate arguments.

    Use... If you want to...
    SQLLiteSpeed Perform backup/restore tasks. For more information, see LiteSpeed Command-Line Arguments.
    SLSFastCompression Back up a database using Fast Compression technology. For more information, see Fast Compression Command-Line Arguments.
    SLSSmartCleanup Delete old backups. For more information, see SmartCleanup Command-Line Arguments.
    SLSRecast Change backup options for the existing LiteSpeed backups. For more information, see Recast LiteSpeed Backups.
    Extractor Convert LiteSpeed backups to the native SQL Server backups. For more information, see Convert LiteSpeed Backups to SQL Server Backups.
    OLR Restore database objects. Restore Objects with the Command-Line Interface
    SLSSQLMaint Perform various database maintenance tasks. For more information, see Script Maintenance Plans Tasks.
    LicenseInfoCmd View currently installed license or to register a new key. For more information, see LicenseInfoCmd Utility.

 

LiteSpeed Command Line Arguments

The LiteSpeed command-line utility (sqllitespeed.exe or sqllitespeedx32.exe) allows you to conduct LiteSpeed backups and restores directly from your operating system command-line. You must run the utility on the server that you are backing up or restoring. You may need to use sqllitespeedx32.exe if you have a 32-bit SQL Server on a 64-bit operating system.

Syntax

sqllitespeed.exe ( -? | <options> )

Connection Options:

-S <server_name\instance_name>        
(-U <login_id> -P <password> ) | -T

 

Backup Options:

-B <option>
[--nowrite]        
[-D <database_name>]
[-f <file_name>]         
[-g <filegroup_name>]   
-F <backup_device_name> 
[-n <backup_set_name>]      
[-d <backup_description>]
[-Y <comment> ]      
[-E <mirror_path>] 
[-I] 
[-N <file_number>]        
[-W <options>]
[--AdaptiveCompression (Speed|Size) | -C <compression_level> ]      
[-e <encryption_level> (-K <password>|--JobP <key>)]         
[-y <date_time> | -r <number_of_days>]
[-s ]
[--doubleclick] 
[--OLRMap
[--TempDirectory <path>]]
[--attachedfile <path_or_file>] 
[-X <options>]    
[-h 1...100]  
[-o <buffer_count>]           
[-x < maximum_transfer_size>]   
[-t <number_of_threads>]
[-p (-1|0|1|2)] 
[--LSECompatible ]
[-L (0|1|2) [--Trace logpath = "path"]] 
[-V (0|1)]


Restore Options:

-R <restore_option>
-F <backup_device_name> 
-D <destination_database_name>
[-N <file_number>]
[-f <file_name>]         
[-g <filegroup_name>]  
[--Read_Write_Filegroups]
[-K <password>| --JobP <key>]
[-W STATS = <number>]
[-W PASSWORD = "<media_password>"]
[-A <affinity_mask>]
[-h 1...100]  
[-o <buffer_count>]           
[-x <maximum_transfer_size>]  
[-X <options>]
[--RestoreAsReadOnly
[--RestoreAsCompressed ]]
[--attachedfile <path_or_file>] 
[-L (0|1|2) [--Trace logpath = "path"]]

 

Automated Restore Options:

-R Automated
[-D <destination_database_name>
    [--DataFilePath <path> ]
    [--LogFilePath <path> ] ]
-F <backup_filename> | (--BackupPath <path>
    --BackupExtension <extensions>
    --CheckSubfolders (0|1) )
[--BackupType <option> ]
--SourceServer <server_name>
--SourceDatabase <database_name>
[-K <password> | --JobP <key>]
[-W "STATS = <number>"]
[-W "PASSWORD = '<my_password>'"]
[--WithReplace (0|1)]
[-A <affinity_mask>]
[-h 1...100]  
[-o <buffer_count>]           
[-x <maximum_transfer_size>]  
[-X <options>]
[--RestoreAsReadOnly
[--RestoreAsCompressed ]]
[-L (0|1|2) [--Trace logpath = "path"]]
[--DryRun (0|1)]
[--DropDatabaseOnFailure (0|1)]
[--DropDatabaseOnSuccess (0|1)]

 

TSM Connection Options:

-j <TSM_configuration_file> 
-i < TSM_object> 
[-c <TSM_client_node> ]          
[-k <TSM_client_owner_password>]
[-l <TSM_filespace>]        
[-q <TSM_query>] 
[-a delete] 
[-z <TSM_management_class>] 
[--tsmpointtime yyyy-mm-dd hh:mm:ss] 
[--tsmarchive]


Tape Arguments:

[-m (0|1|2|3)]        
[-w]        
[-u]         

 

Cloud connection options:

[--CloudVendor <vendor name>]
[--CloudAccessKey <key name>]
[--CloudAccessKeyEnc <encrypted key name>]
[--CloudSecretKey <key name>]
[--CloudSecretKeyEnc <encrypted key name>]
[--CloudBucketName <bucket name>]
[--CloudRegionName <cloud region name>]
[--CloudEndpoint <cloud endpoint:port>]
[--CloudAcceptAllCertificates <0, 1>]
[--CloudGovRegion <government region number>]
[--CloudStorageClass <standard, standard-ia, standard-rrs>]
[--AWSUseServerSideEncryption <1, 0>]
[--AzureBlobType <block, page>]
[--CloudAutoStriping <1, 0>]
[--CloudAutoStripingThreshold <param size in GB>]
[--UseSSL <1, 0>]

 

Proxy connection options:

[--ProxyHost <proxy host name>]
[--ProxyLogin <proxy server login credential>]
[--ProxyPassword <proxy server password credential>]
[--ProxyPasswordEnc <encrypted proxy server password credential>]
[--ProxyPort <proxy server port number>]

Arguments

NOTES:

  • Single-letter arguments are case-sensitive, and they can be preceded by a figure dash '-' or '/'.
  • Verbose multi-letter arguments are not case-sensitive, they must be preceded by double dashes '--'.

-Argument

--Argument

Description

(none) --AdaptiveCompression

Automatically selects the optimal compression level based on CPU usage or Disk IO. For more information, see Compression Methods.

You can tell Adaptive Compression to optimize backups either for size or for speed. This argument accepts one of the following values:

  • Size
  • Speed

-A

--Affinity

Processor affinity designates specific processors to run LiteSpeed, while not allowing LiteSpeed to run on the remaining processors.

This argument accepts decimal values and hexadecimal values. If a value begins with "0x" it is interpreted as hexadecimal. A positive 64-bit integer value translates to a binary mask where a value of 1 designates the corresponding processor to be able to run the LiteSpeed process.

NOTE: 32-bit Windows is internally limited to a 32-bit mask.

For example, you need to select processors 2, 3, and 6 for use with LiteSpeed. Number the bits from the right to left. The rightmost bit represents the first processor. Set the second, third, and sixth bits to 1 and all other bits to 0. The result is binary 100110, which is decimal 38 or hexadecimal 0x26. Review the following for additional information:

Decimal Value

Binary Bit Mask

Allow LiteSpeed Threads on Processors

0 0 All (default)

1

1

1

3

11

1 and 2

7 111 1, 2 and 3

38

100110

2, 3, and 6

205 11001101 1, 3, 4, 7, and 8

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. You may also want to consider using Adaptive Compression to maintain backup performance. For more information, see Adaptive Compression.

  --ARPeriod

Specifies a point in time to restore from where the time is measured in days, hours, minutes and seconds from the restore time.

Set 0's for periods not used.

@ARPeriod = N'DD.HH:MM:SS'

  --ARPointInTime

Specifies a point in time to restore from: year, month, day, hours, minutes, seconds.

@ARPointInTime = N'YYYY-MM-DD HH:MM:SS'

(none)

--AttachedFile

Specifies filepaths to include in both backup and restore operations. The filepath can be either a single file or a directory. If it is a directory, then LiteSpeed recursively includes all files and subdirectories. All attached files are encrypted and compressed, with all pertinent backup parameters supported. This feature works for disk, tape, TSM, and Double Click Restore as well. You can supply multiple instances of this argument.

When used within the context of a restore operation, the path parameter can be expanded to include a new destination. This form will take the syntax of <file_path> to <new_file_path>. The new filepath can be used to specify a new location but cannot rename a file.

This argument only restores the attached files. It does not restore the database, just the files that were attached to that backup.

NOTES:

  • The original entire directory path need not be supplied (e.g. c: to c:\testadSattsm is allowed).
  • c:\testad to testadr would restore all files in directory c:\testad to c:\testadr.

You can supply multiple instances of this argument.

-B

--Backup

Backup operation. This argument accepts one of the following values:

  • Database—Back up database

  • Log—Back up transaction log 

(none) --BackupExtension

When looking for database backups, LiteSpeed will only consider backup files that have the extensions you specify. The value of this parameter is a list of extensions, separated with commas. No value or asterisk (*) specifies any file extension.

-d

--BackupDescription

Specifies a description to store with the backup.

This argument accepts variables. For more information, see LiteSpeed Variables.

-F

--BackupFiles

Specifies a backup location (e.g. C:\backups\AdventureWorks.bak). This argument accepts network destinations. You can supply multiple instances of this argument to use stripe backups.

Examples:

UNC Path: \\servername\share\path\filename

Local path: c:\filedirectory\filename 

For TSM backups and TSM archives, this argument accepts the following formats:

  • tsmbkp:<filespace>\<high>\<low>
  • tsmarc:<filespace>\<high>\<low>

This argument accepts variables. For more information, see LiteSpeed Variables.

-N

--BackupIndex

Specifies the particular backup to use when recasting, restoring, extracting or reading from files with multiple appended backups. You can run xp_restore_headeronly to query the files contained within the backup set given by backup_file_name.

-n

--BackupName

Specifies the name of the backup set.

This argument accepts variables. For more information, see LiteSpeed Variables.

(none) --BackupPath

Specifies the directory where to search for the backup files.

You can supply multiple instances of this argument. Each instance of this parameter must be followed by --BackupExtension and --CheckSubfolders arguments.

(none) --BackupType

Specifies backup types to use for the restore. This argument accepts one of the following values:

  • full—LiteSpeed will only restore the most recent full database backup.
  • diff—LiteSpeed will restore the most recent full database backup and any existing differential backups based on this full.
  • tlog—LiteSpeed will restore the most recent full database backup and any existing differential and/or transaction log backups created after the most recent full backup.

-o

--BufferCount

Specifies the number of SQL Server buffers available for a LiteSpeed operation. The default value is set by SQL Server.

NOTE: LiteSpeed defaults typically result in the best performance. You should only modify advanced options after careful planning and testing.

(none)

--CheckDB

Specifies checking the database integrity after running restores. Options include: --CheckDBPhysicalOnly, --CheckDBDataPurity, --CheckDBExtendedLogicalChecks, --CheckDBNoIndex, --CheckDBTableLocks, and --CheckDBNoInfoMessages.

(none)

--CheckDBPhysicalOnly

Specifies the checking database physical structure option. Note: Using this argument can significantly decrease the execution time when using large databases.

(none)

--CheckDBDataPurity

Specifies the checking database column values option for validity or out of range.

(none)

--CheckDBExtendedLogicalChecks

Specifies the performing consistency checks on indexes option. It checks XML indexes and spacial indexes.

(none)

--CheckDBNoIndex

Specifies the performing intensive checks of non-clustered indexes for user tables option.

(none)

--CheckDBTableLocks

Specifies the using table locks instead of using an internal database snapshot option.

(none)

--CheckDBNoInfoMsgs

Specifies the including informational messages in the notification report option.
(none) --CheckSubfolders

Specifies whether to use subfolders to look for database backups. This argument accepts one of the following values:

  • 0—False. LiteSpeed will only use backups located in the specified folder.
  • 1—True. LiteSpeed will look for backups in the specified folder and in its subfolders.

-Y

--Comment

Appends a user comment to the backup.

This argument accepts variables. For more information, see LiteSpeed Variables.

-C

--CompressionLevel

Specifies the compression level for the backup. Valid values are 0 through 8. 0 bypasses the compression routines. The remaining values of 1 through 8 specify compression with increasingly aggressive computation. 2 is the default value for disk backups and 7 is the default value for cloud backups.

When choosing a compression level, it is best to try various options using your equipment and data to determine the best option for your environment. Use the Backup Analyzer to test the performance of different compression levels. For more information, see Test Optimal Backup Settings.

NOTE: If both the compression level and Adaptive Compression option are passed in, LiteSpeed will not error out and will select and use Adaptive Compression.

-D

--Database

Name of database to be backed up or restored.

(none) --DataFilePath

Specifies a location for data files.

(none) --DisconnectUsers

Disconnect users on executing restore (in standby mode only). This argument accepts one of the following values:

  • 0—Do not disconnect users (default).
  • 1—Disconnect users.
(none) --DontUseCopyOnly

Specifies that LiteSpeed is not to use copy-only backups when running restores.

(none) --DontUseReplication Specifies that LiteSpeed is not to include databases that are part of a replication plan when running restores.

-J

--DoubleClick

Creates a Double Click Restore executable. This argument accepts one of the following values:

  • 1—Creates one Double-Click Restore executable file. 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.
  • 2—Creates a Double Click Restore loader in the same location. (Default)

For more information, see Double Click Restore Executables.

(none) --DropDatabaseOnFailure

Drops the restored database only if the restore fails. Use this option if you no longer need the restored database. For example, if you are only restoring the latest backup for testing purposes. This option contains two additional options to select. One or both options can be selected.On success restore and check database integrity operations - The database is dropped after a successful restore and database integrity check.On failure any of restore or check databases integrity operations - The database is dropped after failing the restore or database integrity check. This argument accepts one of the following values:

  • 0—False (default)
  • 1—True
(none) --DropDatabaseOnSuccess

Drops database on success only. Use this option if you no longer need the restored database. For example, if you are only restoring the latest backup for testing purposes. This option contains two additional options to select. One or both options can be selected.On success restore and check database integrity operations - The database is dropped after a successful restore and database integrity check.On failure any of restore or check databases integrity operations - The database is dropped after failing the restore or database integrity check. This argument accepts one of the following values:

  • 0—False (default)
  • 1—True

(none)

--EncBackupKey

Encrypts the specified key. The encrypted key is suitable for use with -jobp in a backup operation.

(none)

--EncRestoreKey

Encrypts the specified key. The encrypted key is suitable for use with -jobp in a restore operation.

-e

--EncryptionLevel

Specifies encryption level. Works in conjunction with the Key (K) parameter. This argument accepts one of the following values:

  • 0—40-bit RC2

  • 1—56 bit RC2

  • 2—112 bit RC2

  • 3—128 bit RC2

  • 4—168 bit 3DES

  • 5—128 bit RC4

  • 6—128 bit AES

  • 7—192 bit AES

  • 8—256 bit AES

  • 9—MS_AES_128

  • 10—MS_AES_192

  • 11—MS_AES_256

(none) --ExcludeDatabase

Name of database(s) to exclude from this backup / restore.

Example:

--ExcludeDatabase Northwind

Tip: The @ExcludeDatabase argument can be applied together with @MultiDatabaseType to exclude several databases from the process.

-y

--Expiration

Specifies the date and time when the backup expires. LiteSpeed will not overwrite this file until expiration datetime is passed. This argument accepts one of the following formats:

  • yyyy-mm-dd
  • yyyy-mm-dd hh:mm:ss

-f

--File

Specifies a logical database file used for file or filegroup backups. You can supply multiple instances of this argument.

-g

--FileGroup

Specifies a database filegroup to include in the backup or restore. You can supply multiple instances of this argument.

A filegroup backup is a single backup of all files in the filegroup and is equivalent to explicitly listing all files in the filegroup when creating the backup. Files in a filegroup backup can be restored individually or as a group.

-X --IOFlags

Specifies if LiteSpeed should wait and retry the read or write operation on failure. You can define retry options using the following parameters:

  • DISK_RETRY_COUNT—Specifies the number of times that a specific operation will be retried on failure. The default is 4 retries, the maximum allowed setting is 1000.
  • DISK_RETRY_WAIT—Specifies the number of seconds to wait immediately following a failure before retrying. The default is 15 seconds, the maximum allowed setting is 300.

NOTE: This functionality is only available for disk and cloud operations.

For more information, see Network Resilience.

(none)

--JobP

Specifies an encrypted key. (Similar to -K).

NOTE: Automated Restore requires that you use the same password for all encrypted backups.

-K

--Key

Value used to generate the encryption key for the encryption algorithm. If you do not supply encryption key, then the program will not encrypt the backup. If you use the wrong encryption key, the restore will fail.

Caution: When encrypting data, take care not to lose the encryption key; a backup cannot be restored or recovered without the original encryption key.

Example of key: 'Mypassword'

NOTE: Automated Restore requires that you use the same password for all encrypted backups.

(none) --LogFilePath

Specifies a location for log files.

-L

--LogLevel

Creates a log file. This argument accepts one of the following values:

  • 0—Logging off.

  • 1 or any odd value—Logging on. Log file is removed on success.

  • 2 or any even value—Logging on.

The default output directory is C:\Documents and Settings\All Users\Application Data\Quest Software\LiteSpeed\SQL Server\Logs (or C:\ProgramData\Quest Software\LiteSpeed\SQL Server\Logs) (or C:\ProgramData\Quest Software\LiteSpeed\SQL Server\Logs). To log to a different directory run this utility with the following argument: --trace logpath = "path".

For more information, see Configure Logging in LiteSpeed.

(none) --LSECompatible

Produces a backup that is compatible for use with LiteSpeed Engine for SQL Server. The parameter can be used whenever a new backup file is created and should only be set when backups are needed for cross-compatibility between the products. This switch will force modifications to internal settings such as the thread count, striping model, and encryption levels. In some cases, performance may be degraded. The parameter is ignored when appending to a backup file created without the switch.

This argument accepts one of the following values:

  • 0—False (default)
  • 1—True

-x

--MaxTransferSize

Specifies the largest unit of transfer in bytes to be used between SQL Server and LiteSpeed. The possible values are multiples of 65536 bytes (64 KB) ranging up to 4,194,304 bytes (4 MB). The default is 1048576 (1 MB).

-E

--MirrorFiles

Mirrors the backup file (copies the backup to multiple locations). If you back up the primary to a set of striped files, all mirrored backups must match the primary in the number of stripes in each mirror.

This argument accepts variables. For more information, see LiteSpeed Variables.

(none)

--MultiDatabaseType

Produces a backup that includes several types of databases. Types can include: all, system, user, or selected databases.

This argument accepts one of the following values:

  • All - Backup all system and user databases.
  • System - Backup only system databases.
  • User - Backup only user databases.
  • Selected - Backup specifically selected databases.
-Z --NoWrite

The argument is similar to backup log xxx to disk = 'NUL'. When the backup is completed, it is not written to disk.

NOTES:

  • You need to supply a filename (-F). The MSDB history tables are updated with the filename specified, but the file will not get created and no IO is performed.
  • If compression or encryption parameters are specified, then the data will get compressed or encrypted before being thrown away.

-M

--OLRMap

Generates a map file during a backup for Object Level Recovery. This argument accepts one of the following values:

  • 0—False (default)
  • 1—True

-I

--Overwrite

Re-initializes (overwrites and replaces) the target backup files. For TSM backups, this will create the TSM object and version the backup based on the retention policy. The argument accept the values:

  • 0 (appends the backup to an existing backup file)
  • 1 (overwrite the existing target backup file)

-P

--Password

Specifies the user password. Passwords are case-sensitive. Required if the connection type is not a trusted connection.

-p

--Priority

Specifies the priority of the LiteSpeed process compared to other processes running on the same server. This argument accepts one of the following values:

  • 0—Normal (Default)

  • 1—AboveNormal

  • 2—High

(none)

--Read_Write_Filegroups

Specifies a partial backup, which includes the primary filegroup and any read-write secondary filegroups.

-r

--RetainDays

Specifies a number of days to retain the backup. LiteSpeed will not overwrite this file for this number of days. 

-R

--Restore

Restore operation.This argument accepts one of the following values:

  • AttachedFilesOnly —Restore attached files without restoring the database.

  • Database—Restore database backup.

  • Log—Restore log backup.

  • VerifyOnly—Verify backup. 

  • HeaderOnly—Provide backup details.

  • FileListOnly—Provide database file details.

  • CheckPassword—Check password/key.

  • CheckSumOnly—Checksum a backup file.

  • AttachedFileNamesOnly—List names of all attached files.

  • Automated—Restore the most recent full backup and optionally differential and transaction log backups.

(none) --RestoreAsCompressed

Works in conjunction with --RestoreAsReadOnly, creates a folder if it does not exist, and then compresses it. This argument accepts one of the following values:

  • 0—False (default)
  • 1—True
(none) --RestoreAsReadOnly

Instructs the restore operation to leave the database in read-only mode. This argument accepts one of the following values:

  • 0—False (default)
  • 1—True

Using this option, you can restore a user database into an NTFS compressed folder or restore a tlog to a read-only database in a compressed folder.

NOTES:

  • When using an NTFS-compressed folder for a database, it can only be restored as read-only.
  • You can only use this feature on Windows NTFS file systems.

-S

--Server

Specifies the instance of Microsoft SQL Server to connect to. This argument accepts one of the following values:

  • server_name
  • server_name\instance_name

If no server is specified, the LiteSpeed command-line utility will connect to the default instance of SQL Server on the local computer.

-?

--ShowHelp

Displays the syntax summary of the LiteSpeed command-line utility.

-s

--Skip

Skips normal retention checks and overwrites the backup that has not expired.

  • 0—False (default)
  • 1—True
(none) --SourceDatabase

Backups of this database are the source for restore.

(none) --SourceServer

Backups created on this instance of SQL Server are the source for restore.

-m

--TapeFormat

Initializes the media on the device. This argument only applies to tape backups. This argument accepts one of the following values:

  • 0—Do not format (default)

  • 1—Write new header

  • 2—Long erase / write new header

  • 3—Low level controller format / write new header

NOTE: Any successful format operation (values 1, 2, and 3; not all are available to all drive types) lays down a LiteSpeed tape header that will identify this tape as containing LiteSpeed backups. Using @init=1 (or -I in the command line) will not lay down a tape header.

-w

--TapeRewind

Applies only to backing up and restoring tape. This argument accepts one of the following values:

  • 0—Leave the tape unwound (default)

  • 1—Rewind the tape after writing/reading

-u

--TapeUnload

Applies to tape backups and restores. This argument accepts one of the following values:

  • 0—Keep tape loaded (default)

  • 1—Unload and eject tape from the drive after operation

(none)

--TempDirectory  

Specifies a temporary directory for use with Object Level Recovery. Use this argument when the default Windows temp directory does not have enough free disk space for the restore process.

NOTE: You can specify the default temp directory using the TempPath parameter in the [LiteSpeed] section of the LiteSpeedSettings.ini file. (Usually, C:\Documents and Settings\All Users\Application Data\Quest Software\LiteSpeed\SQL Server\LiteSpeedSettings.ini.)

-t

--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.

-h

--Throttle

Specifies the maximum CPU usage allowed. The argument accepts an integer value between 1 and 100. The default value is 100. This is the percentage of the total amount of CPU usage (across all enabled processors) available.

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. You may also want to consider using Adaptive Compression to maintain backup performance. For more information, see Adaptive Compression.

  --UDT

Create table script:

  • 0—Off. Create table with native types, if possible; othervise (CLR UDT) create with UDT. (Default).
  • 1—On. Create table with UDT.

-U

--UserId

Specifies user login ID. Required if the connection type is not a trusted connection.

Login IDs are case-sensitive.

-V --Verify

Performs a restore verification on the backup file just created (if backup was successful).

  • 0—False (default)
  • 1—True

-T

--WindowsAuth

Uses a trusted connection (to the server) instead of requiring a password.

-W

--With

Specifies strings that will be passed directly to SQL Server. You can supply multiple instances of this argument.

Some of the accepted parameters are the following:

  • DIFFERENTIAL—Specifies that the database or file backup should consist only of the portions of the database or file changed since the last full backup. A differential backup is usually smaller than a full backup. Use this option so that all individual log backups since the last full backup do not need to be applied.
  • CHECKSUM—Causes checksums to be verified when a LiteSpeed backup is created.
    NOTE: When you restore a backup containing checksum, it is automatically checked. If you do not want to check the checksums during a restore, supply 'NO_CHECKSUM' .

  • CONTINUE_AFTER_ERROR—Causes the backup be executed despite encountering an invalid backup checksum.
  • COPY_ONLY—Specifies the copy-only backup.
  • KEEP_REPLICATION—Instructs the restore operation to keep the replication settings when restoring a published database to a server other than that on which it was created (used when setting up replication with log shipping).
  • MOVE—Specifies that the given logical_file_name should be moved to operating_system_file_name.
  • REPLACE—Instructs LiteSpeed to create the specified database and its related files even if another database already exists with the same name. The existing database is deleted.
  • RECOVERY—Instructs the restore operation to roll back any uncommitted transactions. After the recovery process, the database is ready for use.
  • NORECOVERY—Instructs the restore operation to not roll back any uncommitted transactions.
  • NO_TRUNCATE—Allows backing up the log in situations where the database is damaged.
  • RESTRICTED_USER—When used in conjunction with recovery (another with param and the default) leaving a usable database, this restricts access for the restored database to members of the db_owner, dbcreator, or sysadmin roles.
  • STATS—Displays a message each time a percentage of the activity completes. The default is 10%.
  • BLOCKSIZE—Specifies the physical block size, in bytes. Supported values are: 512, 1024, 2048, 4096, 8192, 16384, 32768, and 65536 (Default).
  • PASSWORD—Specifies the password for the backup set.
(none) --WithReplace

Instructs LiteSpeed to create the specified database and its related files even if another database already exists with the same name. The existing database is deleted. This argument accepts one of the following values:

  • 0—False (default)
  • 1—True

TSM-Specific Arguments

TSM-specific arguments work in conjunction with the LiteSpeed arguments. See Syntax and Examples for more information.

-Argument

--Argument

Description

(none)

--TSMAdminName

Specifies the TSM administrative user name that has client authority for the TSM node. Some operations may require an administrative user with client owner authority to be specified in order to open a TSM session. The correct username and password may be obtained from the TSM administrator.

(none)

--TSMAdminPwd

Specifies the plain text password of the administrative user which is used to log in to the TSM server and start the TSM session.

(none) --TSMArchive

Specifies to store the backup as a TSM archive. This argument accepts one of the following values:

  • 0—False (default)
  • 1—True

-c

--TSMClientNode

Specifies the TSM server LiteSpeed connects to during backups and restores. Not required, if specified in the options file or if backing up with the Passwordaccess Generate option.

-k

--TSMClientOwnerPwd

Specifies the TSM client owner user password. Not required, if specified in the options file or if backing up with the Passwordaccess Generate option.

(none) --TSMDeviceTimeoutMinutes

Specifies how long to wait for a TSM device.

(none) --TSMDSMI_Dir

DSMI_DIR path if needed.

(none) --TSMDSMI_Log

DSMI_LOG path.

-j   

--TSMConfigFile

Specifies the TSM configuration file.

-i

--TSMFile

Defines the TSM filespace, high level and low level. This argument accepts the following format:

tsm_filespace\tsm_high_level\tsm_low_level

where:

  • tsm_filespace is the logical space on the TSM server that contains a group of files. It can be the drive label name or UNC name.

  • tsm_high_level specifies the directory path in which the file belongs.

  • tsm_low_level specifies actual name of the file.

NOTE: You may only store one item the location specified by this argument. It is not possible to append an object to this location. You can use the -I command-line argument or @init to back up to a non-unique location.

-l

--TSMFileSpace

Specifies the TSM file space, the logical space on the TSM server. It can be the drive label name or UNC name. You can supply multiple instances of this argument.

NOTE: IBM recommends that an application client should select a unique file space; it is recommended that LiteSpeed users follow this practice with a specific file space reserved for LiteSpeed backups.

(none) --TSMLogname

Log name.

-z

--TSMMgmtClass

Specifies the TSM management class. If not specified, LiteSpeed uses the default management class.

(none)

--TSMPointInTime

Specifies the date for restore/to filter results. If it is not passed, LiteSpeed will choose the most recent archived backup. The format is yyyy-mm-dd hh:mm:ss.

NOTE: If the backup was a striped backup and the point-in-times of the various striped files are different (rare but can be different a second or so), then the most recent of the times must be chosen.

Cloud-Specific Arguments

Cloud-specific arguments work in conjunction with the LiteSpeed arguments. See Syntax and Examples for more information.

-Argument

--Argument

Description

(none) --AWSUseServerSideEncryption

The @AWSUseServerSideEncryption argument enables the encryption of data stored at rest in Amazon S3. This argument accepts one of the following values:

  • 0—Do not use Server Side Encryption
  • 1—Use Server Side Encryption
(none) --AzureBlobType

The @AzureBlobType argument specifies the types of blobs that can be stored in the Microsoft Azure cloud storage. This argument accepts one of the following values: "Block", "Page".

note: The LiteSpeed auto striping logic used in the @CloudAutoStriping and @CloudAutoStripingThreshold parameters can override the Azure blob limit for LiteSpeed backups.

(none) --CloudAccessKey

The @CloudAccessKey argument specifies the name of the unique Cloud Web Service alphanumeric access key that identifies each user. The selections include Amazon Access Key, Azure Account Name, Google e-mail styled account, S3 Compatible Storage Access Key.

(none) --CloudAccessKeyEnc

The @CloudAccessKeyEnc argument specifies the name of the encrypted unique Cloud Web Service alphanumeric access key that identifies each user.

(none) --CloudAutoStriping

This parameter enables automatic file striping for LiteSpeed cloud backups.

(none) --CloudAutoStripingThreshold

This parameter contains the stripe size in GBs. LiteSpeed logic uses the database size to make a decision about the number of stripes needed for LiteSpeed cloud backups. For example, if you have a database with a size of 200GB and set @CloudAutoStripingThreshold = 50, then LiteSpeed uses 200/50 = 4 stripes.

(none) --CloudBucketName

The @CloudBucketName argument specifies the name of the container for cloud objects. Bucket names must be at least 3 and no more than 63 characters long. The selections are Amazon Bucket Name, Azure Container Name, Google Bucket Name, Google Bucket Name requirements are described at https://cloud.google.com/storage/docs/naming, S3 Compatible Storage Bucket Name,

(none) --CloudGovRegion

The @CloudGovRegion argument enables a special restricted region for the US Government use in Amazon S3 and Azure Clouds. This argument accepts one of the following values:

  • 0—Do not use government cloud (default)
  • 1—Use government cloud
(none) --CloudRegionName

The @CloudRegionName argument specifies the name of the Cloud Web Service region to use for a bucket. Example values are but not limited to: us-east-1, us-east-2, us-west-1, us-west-2, ca-central-1, eu-central-1, eu-west-1, eu-west-2, ap-south-1, ap-southeast-1, ap-southeast-2, ap-northeast-1, ap-northeast-2, sa-east-1, N'Germany' and N'China'.

(none) --CloudSecretKey

The @CloudSecretKey argument specifies the name of the Cloud Web Service secret key that is assigned when you initially get a Cloud account.

(none) --CloudSecretKeyEnc

The @CloudSecretKeyEnc argument specifies the name of the encrypted Cloud Web Service secret key that is assigned when you initially get a Cloud account.

(none)

--CloudStorageClass

The @CloudStorageClass argument specifies a range of storage classes established for different use cases including:

For Amazon S3:

  • Standard: Standard storage - for general-purpose storage of frequently accessed data.
  • Standard-IA: Standard Infrequent Access - for long-lived, but less frequently accessed data.
  • RRS: Reduced Redundancy Storage - for non-critical data considering lower level of redundancy rather than Standard storage.

Important: : In versions less than 8.5 you should use --AWSStorageClass. The @AWSStorageClass argument is no longer valid in subsequent LiteSpeed versions after 8.5.

For Google Storage:

  • Multi_regional - for frequently accessed data around the world as per serving website content, streaming videos, or gaming and mobile applications.
  • Regional - for frequently accessed data in the same region as your Google Cloud DataProc or the Google Compute Engine instances that use it, as per data analytics.
  • Nearline - for infrequently accessed data (data you expect to access no more than once per month).
  • Coldline - for infrequently accessed data (data you expect to access no more than once per year).
(none) --CloudVendor

The @CloudVendor argument specifies the name of the cloud service provider. The argument accepts one of the following values: "AmazonS3", "AzureBlob", "GoogleStorage" or "S3Compatible".

(none) --CloudEndpint

The @CloudEndpoint argument specifies the endpoint for S3 Compatible Storage and custom endpoint for Amazon S3 service (in case of VPC). Format: servername:port .Example values: "servername", "servername:port", "ip:port", "10.0.0.200:9021".

(none) --CloudAcceptAllCertificates

The @CloudAcceptAllCertificates argument instructs LiteSpeed accept self-signed certificates for S3 Compatible Storage. This argument accepts one of the following values:

  • 0—Accept verified certificates only (default)
  • 1—Accept self-signed certificates

Note: Delete backups is not supported in Maintenance Plans with this option.

(none) --GSProject

DEPRECATED LiteSpeed 8.8: Was used to store for the Google Cloud Storage project ID; the project ID is now obtained from login. This parameter is retained for compatibility with old backup/restore scripts.

(none)

--UseSSL

The @UseSSL argument specifies that the connection uses SSL security. This argument accepts one of the following values:

  • 0—Do not use SSL
  • 1—Use SSL (default)

Proxy-Specific Arguments

Proxy-specific arguments work in conjunction with the LiteSpeed arguments. See Syntax and Examples for more information.

-Argument

--Argument

Description

(none)

--ProxyHost

The @ProxyHost argument is optional and specifies the name of the proxy host name that is running the proxy server.

note: If the @ProxyHost argument is not defined, then the LiteSpeed core engine checks the local .ini files for the proxy parameters. If the proxy parameters are not detected, then the LiteSpeed core engine connects directly to the proxy servers.

(none) --ProxyLogin

The @ProxyLogin argument is optional and specifies the proxy server login credential.

note: If not defined, then the LiteSpeed core engine checks the local .ini files for the proxy parameters. If the proxy parameters are not detected, then the LiteSpeed core engine connects directly to the proxy servers.

(none) --ProxyPassword

The @ProxyPassword argument is optional and specifies the proxy server password credential.

note: If the @ProxyPassword argument is not defined, then the LiteSpeed core engine checks the local .ini files for the proxy parameters. If the proxy parameters are not detected, then the LiteSpeed core engine connects directly to the proxy servers.

(none) --ProxyPasswordEnc

The @ProxyPasswordEnc argument is optional and specifies the encrypted proxy server password credential.

note: If the @ProxyPasswordEnc argument is not defined, then the LiteSpeed core engine checks the local .ini files for the proxy parameters. If the proxy parameters are not detected, then the LiteSpeed core engine connects directly to the proxy servers.

(none) --ProxyPort

The @ProxyPort argument is optional and contains the port number of the proxy server. The TCP/IP port values can be 1-65535.

note: If the @ProxyPort argument is not defined, then the LiteSpeed core engine checks the local .ini files for the proxy parameters. If the proxy parameters are not detected, then the LiteSpeed core engine connects directly to the proxy servers.

Examples

  1. Backup the Northwind database using a trusted connection to the backup device c:\temp\Northwind.bak:

    sqllitespeed.exe -B Database -T -D Northwind -F "C:\temp\Northwind.bak"

  2. Backup the Northwind database, log errors (if any) to a specified directory:

    sqllitespeed.exe -B Database -D Northwind -F "C:\temp\Northwind.bak" -L1 --trace logpath="C:\backup_logs"

  3. Write a database backup where each failure can be retried once after a 30 second wait:

    sqllitespeed.exe -B database -D foo -F c:\test.bkp -X disk_retry_count=1 -X disk_retry_wait=30

  4. Back up to TSM with the Passwordaccess Generate option:

    sqllitespeed.exe -Bdatabase -DNorthwind -L1 -i"fsMH\nw\%D" -j"C:\TSM\baclient\dsm_pg.opt" -I -z"SPS_MGTD" -S"MyServer\Inst2" -U"sa" -P"***"

  5. Create a differential backup of the Northwind database:

    sqllitespeed.exe -Bdatabase -DNorthwind -i"fsMH\nw\%D-%T" -c"10.0.1.200" -k"password" -j"c:\program files\Tivoli\TSM\baclient\dsm.opt" -WDIFFERENTIAL -I -n"Northwind Diff Backup" -d"Differential Backup of Northwind on 4/12/2011 1:50:58 PM"

  6. Restore the Northwind database:

    sqllitespeed.exe -RDatabase -j"C:\TSM\baclient\dsm.opt" -i"fsMH\nw\Northwind" --TSMPointInTime "2011-04-12 16:57:22" -N1 -DNorthwind -WREPLACE -A0 -L1 -S"w2k3-22" -U"sa" -P"***"

  7. Restore the Northwind database from the backup device c:\temp\Northwind.bak using variables:

    sqllitespeed.exe -R Database -D Northwind -F "C:\temp\%D.bak"

  8. Restore the most recent full and drop database:

    sqllitespeed.exe -R Automated -D LiteSpeedLocal_TestRestore --DataFilePath "D:\DATA" --LogFilePath "D:\DATA" --DropDatabase 3 --BackupPath "D:\temp" --BackupExtension "" --CheckSubfolders 0 --SourceServer LITESPEED\SQL2005 --SourceDatabase LiteSpeedLocal --BackupType full -K ****** --WithReplace 1 --DropDatabaseOnFailure 1 --DropDatabaseOnSuccess 1 -S"LITESPEED\SQL2005" -T

  9. Restore the most recent full backup and related differential and transaction log backups following this full to a new database.

    sqllitespeed.exe -R Automated --DataFilePath "D:\DATA" --LogFilePath "D:\DATA" --BackupPath "D:\temp" --BackupExtension "" --CheckSubfolders 1 -D LiteSpeedLocal_Copy --SourceServer LITESPEED\SQL2005 --SourceDatabase LiteSpeedLocal --BackupType tlog -K ****** -S"LITESPEED\SQL2005" -T

  10. Restore the most recent Fast Compression backups.

    sqlLiteSpeed.exe -R Automated -D "LiteSpeedLocal_AutomatedRestore" --BackupPath "D:\temp\FC\" --BackupExtension "" --CheckSubfolders 0 -K "*******" --SourceServer "LITESPEED\SQL2005" --SourceDatabase "LiteSpeedLocal" --BackupType "diff" --JobP "5jzOEztgLxQ=" --WithReplace 1 -S "LITESPEED\SQL2005" -U "sa" -P "******"

  11. Restore the most recent striped backup.

    sqllitespeed.exe -R Automated -D "NEWDB" --DataFilePath "D:\DATA" --LogFilePath "D:\DATA" --BackupPath "D:\temp" --BackupExtension "stripe1" --CheckSubfolders 0 --BackupPath "E:\temp" --BackupExtension "stripe2" --CheckSubfolders 0 --SourceServer "LITESPEED\SQL2005" --SourceDatabase "FOX" --BackupType "full" -S "LITESPEED\SQL2005" -T

  12. View candidates for Automated Restore.

    sqllitespeed.exe -R Automated --BackupPath d:\temp\TEST --BackupExtension "bak,bkp" --CheckSubfolders 1 --SourceServer LITESPEED\SQL2005 --SourceDatabase "LiteSpeedLocal" --BackupType "diff" --DryRun "1" -S "LITESPEED\SQL2005" -T

  13. Restore attached files only:

    sqllitespeed.exe -R attachedfilesonly -F "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\CapacityManagerRepository_Full_200903012353_20091006124204.bak" -N 1 --attachedfile "'C:\temp\CProg—29-Sep-2009 19-22-51-233.txt' to 'C:\CProg.txt'" -S "spb9771" -T

  14. Encrypt a password for the restore operations.

    sqllitespeed.exe --EncRestoreKey -K "RF^t%7MF"

  1. Restore Objects using the UDT argument. Create table with native types, if possible; othervise (CLR UDT) create with UDT.

    olr.exe -F "C:\temp\FOX_full.bak" -K****** -N3 -C -Y Database -Q d:\temp\create_database_FOX.sql --UDT 0

Returns

0 (success) or 1 (failure)

 

Related Topic

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen