LiteSpeed® for SQL Server 8.5
Install Guide
Copyright
Copyright 2017 Quest Software Inc. ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a
software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written
permission of Quest Software Inc.
The information in this document is provided in connection with Quest Software products. No license, express or implied, by
estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software
products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR
THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED
OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT
SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR
INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS
INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT,
EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no
representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right
to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any
commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Quest Software Inc.
Attn: LEGAL Dept
4 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site (www.quest.com) for regional and international office information.
Patents
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current
information about applicable patents for this product, please visit our website at www.quest.com/legal.
Trademarks
Quest, Toad, Toad World, LiteSpeed and the Quest logo are trademarks and registered trademarks of Quest Software Inc. For a
complete list of Quest marks, visit www.quest.com/legal. All other trademarks and registered trademarks are property of their
respective owners.
Legend
WARNING: A WARNING icon indicates a potential for property damage, personal injury, or death.
CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions
are not followed.
IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.
LiteSpeedInstall Guide
Updated - December 2016
Version - 8.5
Contents
Copyright
2
Introduction
5
About LiteSpeed
5
LiteSpeed Architecture
5
LiteSpeed UI Console
6
LiteSpeed Server Components
6
Local and Central Repositories
6
Multiple Central Repositories
7
System Requirements
8
Software Requirements
8
Supported Cluster Environments
9
Supported Storage Appliances
9
VMWare and Hyper-V Environments
9
Hardware Requirements
9
Privilege and Grant Requirements
10
Installation Scenarios
12
Install LiteSpeed
12
Upgrade LiteSpeed
12
Uninstall LiteSpeed
13
Installation
14
Install LiteSpeed Locally
14
Configure Server Instances
15
Upgrade Repositories
17
Install LiteSpeed on Remote Server Instances
17
Install LiteSpeed Silently
21
Command-Line Parameters
21
Examples
22
To run a silent install
22
To register LiteSpeed on all* instances during install
22
To run an install with logging enabled
22
To run install, but not Instance Configuration
23
To uninstall LiteSpeed
23
Cluster Installation
23
Local Cluster Installations
23
LiteSpeed 8.5 Install Guide
3
Remote Cluster Installations
24
Using LiteSpeed Remote Deploy Tool
24
Using SCCM or LANDesk
24
License Registration
26
Configuration
27
Register Central Repositories
27
Select a Central Repository
28
Register Server Instances
28
Create Server Groups
30
About us
32
Contacting Quest
32
Third Party Contributions
33
LiteSpeed 8.5 Install Guide
4
1
Introduction
About LiteSpeed
LiteSpeed® for SQL Server, or LiteSpeed, is a fast and flexible backup and recovery solution that allows
database administrators to easily maintain complete control over the backup and recovery process. LiteSpeed's
low-impact, high-performance compression and encryption technology helps reduce storage costs and protect
data, while maintaining a high level of recoverability.
LiteSpeed Architecture
The diagram below shows how the 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.
LiteSpeed 8.5 Install Guide
Introduction
5
LiteSpeed UI Console
The LiteSpeed UI Console is a graphical user interface that maintains the accessibility of LiteSpeed
functionality. You need to install at least one LiteSpeed UI Console on the computer from which you want to
manage your SQL Servers and control backup and restore processes.
LiteSpeed Server Components
The core of LiteSpeed includes the LiteSpeed extended stored procedures, compression and encryption
engines and other components that provide command-line access to the product's functionality and support the
LiteSpeed UI Console.
You need to install LiteSpeed core components on all server instances where you want to benefit from
LiteSpeed's fast and flexible backup and recovery solutions.
NOTE: If you do not install LiteSpeed core components on the server instances, you can only conduct native
SQL Server backups.
Local and Central Repositories
LiteSpeed repositories collect and retain statistics on backup activity that occurs through LiteSpeed, including
backups conducted from the LiteSpeed UI Console, command-line, or using the extended stored procedures.
Repositories collect and present statistics for registered servers. They are not a list of servers. If a server goes
LiteSpeed 8.5 Install Guide
Introduction
6
offline you can use the central repository to find out information about it, such as the last time LiteSpeed backed
up the server.
LiteSpeed installs statistics databases through the Instance Configuration wizard. For more information, see
Configure Server Instances on page 15. LiteSpeed installs a local repository for each server instance you
select. Then, you create and select a central repository to gather the local repositories' statistics. LiteSpeed uses
the LiteSpeed Activity Service to transfer the statistics from each local repository to the central repository, so that
the central repository provides a complete picture of backups on all servers.
With the repositories, you can see backups that have failed or succeeded in the Backup Manager Overview tab.
LiteSpeed displays the statistics for the server group, category, server, or database that you select in the
navigation pane tree.
Multiple Central Repositories
LiteSpeed allows you to have multiple central repositories. For example, you may want to have one set of server
instances report to one central repository and another set to a second central repository. However, one local
repository cannot report to two central repositories.
If you want to use multiple central repositories, register each central repository, and then select the appropriate
central repository. For more information, see Register Central Repositories on page 27.
LiteSpeed 8.5 Install Guide
Introduction
7
2
System Requirements
Before beginning installation, review this section to ensure your system meets the following minimum hardware
and software requirements.
Software Requirements
Requirements
Details
Operating
System
Microsoft Windows Server 2003 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows Server 2003 R2 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows Server 2008 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows Server 2008 R2 64-bit (x64) (All Service Packs)
Microsoft Windows Server 2012 64-bit (x64) (All Service Packs)
Microsoft Windows Server 2012 R2 64-bit (x64) (All Service Packs)
Microsoft Windows Server 2016 64-bit (x64) (All Service Packs)
Microsoft Windows XP 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows Vista 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows 7 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows 8 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows 8.1 32-bit and 64-bit (x64) (All Service Packs)
Microsoft Windows 10 32-bit and 64-bit (x64) (All Service Packs)
Database
Software
SQL Server 2000 32-bit and 64-bit (All Service Packs)
SQL Server 2005 32-bit and 64-bit (x64) (All Service Packs)
SQL Server 2008 32-bit and 64-bit (x64) (All Service Packs)
SQL Server 2008 R2 32-bit and 64-bit (x64) (All Service Packs)
SQL Server 2012 32-bit and 64-bit (x64) (All Service Packs)
LiteSpeed 8.5 Install Guide
System Requirements
8
Requirements
Details
SQL Server 2014 32-bit and 64-bit (x64) (All Service Packs)
SQL Server 2016 64-bit (x64) (All Service Packs)
Additional
Software
.Net Framework 4.0 installed before you install the LiteSpeed UI Console.
.Net Framework 4.0 installed before you install LiteSpeed Core Cloud Components.
If using Tivoli Storage Manager (TSM), the TSM API and Backup/Archive Client version
5.3 or later should be installed.
Microsoft Internet Explorer 6.0 or later.
Adobe Reader 8 or later to view PDF guides.
Supported Cluster Environments
l
Microsoft Cluster Service 2003
l
Windows Server 2008 Failover Cluster
l
Windows Server 2008 R2 Failover Cluster
l
Windows Server 2012 Failover Cluster
l
Windows Server 2012 R2 Failover Cluster
l
HP PolyServe Matrix Sever 3.6.1
l
Veritas Storage Foundation HA for Windows 5.0
Supported Storage Appliances
LiteSpeed has been tested and is certified to work with Dell DR4100 and DR4000 Storage Appliances.
VMWare and Hyper-V Environments
LiteSpeed has been tested and is certified to work under VMware and Hyper-V environments.
Hardware Requirements
Requirements
Details
Processor
Follow the recommendations for the SQL Server version used.
Disk Space
250 MB of disk space for installation
NOTE: The disk space required may vary based on options selected during installation.
LiteSpeed 8.5 Install Guide
System Requirements
9
Requirements
Details
Memory
Follow the recommendations for the SQL Server version used.
NOTE: The memory required may vary based on the following:
Monitor
l
Applications that are running on your system
l
Size and complexity of the database
l
Amount of database activity
l
Number of concurrent users accessing the database
SVGA with a minimum resolution of 1024x768
Privilege and Grant Requirements
LiteSpeed requires the following privileges and grants:
Account
Requirement
User account that performs the
LiteSpeed installation
Windows administrator rights and DBA privileges required to
l
Install stored procedures and extended stored procedures
l
Create databases, tables, and indexes
l
Insert, update, and delete to/from the MSDB, LiteSpeedLocal and
LiteSpeedCentral databases
User account that runs the
LiteSpeed UI Console
Power User privileges (or some equivalent).
SQL Server service account
Sysadmin server role privileges required to
SQL Agent service account (or a
proxy account)
NOTE: When executing a Double Click Restore, Windows Vista,
Windows Server 2003, Windows Server 2008, and higher require that
the Windows user account is an administrator.
l
Push stats to local repository
l
Back up or restore using extended stored procedures
l
Execute a scheduled job
l
Start a job manually
TIP: The SQL service account needs at least read\write access to the
following directory and all its contents:
C:\ProgramData\Quest Software\LiteSpeed\SQL Server\
NOTE: SQL Server Configuration Manager should always be used when
changing SQL Server service accounts.
Windows or SQL Server accounts
specified during instance
configuration (Start | All
Programs | Quest Software |
If you select SQL Server authentication, the SQL Server account must
have sysadmin server role privileges, while the Activity Manager service
account must have the Log on as a service permission.
If you select the Windows authentication method for both the local and
LiteSpeed 8.5 Install Guide
System Requirements
10
Account
Requirement
LiteSpeed for SQL Server |
Instance Configuration)
central repository, then the Activity Manager service account specified
on the Service Account page must have the sysadmin privileges and the
Log on as a service permission.
NOTE: If the central repository is located on another server, the
LiteSpeed Activity Manager service account must have domain rights for
two-way communication between the local and central repositories.
Windows or SQL Server account
(Application Button | Repository
Registration...)
Db_owner of the central repository (required to retrieve data from the
central repository)
Windows or SQL Server account
(Application Button | SQL Server
Registration...)
Sysadmin server role privileges required to
TSM with LiteSpeed
l
Connect to SQL Server and retrieve SQL Server properties
l
Back up or restore
l
Execute procedures, retrieve MSDB history
l
Access repositories
If using TSM, its recommended that the following line be added to the
dsm.opt file used by LiteSpeed.
errorlogname "C:\ProgramData\Quest
Software\LiteSpeed\SQL Server\Logs\dsierror.log"
LiteSpeed 8.5 Install Guide
System Requirements
11
3
Installation Scenarios
Install LiteSpeed
1. Install LiteSpeed Locally.
2. Configure Server Instances.
3. Install LiteSpeed on Remote Server Instances.
4. Register Central Repositories.
5. Register Server Instances.
For information about configuring LiteSpeed for the first use, please refer to the User Guide.
Upgrade LiteSpeed
1. Make sure you have a license key for the new version of LiteSpeed for SQL Server.
For more information, see License Registration on page 26. about licensing LiteSpeed.
2. Disable LiteSpeed jobs.
Before installing a new version of LiteSpeed, disable any LiteSpeed jobs that are scheduled to run at the
time of upgrade on all servers where you plan to upgrade LiteSpeed.
To disable jobs on a server instance
a. Select a SQL Server instance in the Job Manager window.
b. CTRL+Click to select multiple LiteSpeed jobs.
c. Right-click anywhere in the selected area and select Disable Jobs.
NOTE: Instead of disabling LiteSpeed jobs, you can open SQL Server Configuration Manager, right-click
SQL Server Agent and select Stop. Be aware that no other SQL Server Agent jobs will be able to run.
SQL Server Agent jobs control backups, database maintenance, and other third-party application jobs.
Review the full list of jobs and their upcoming schedules to make sure no other products will be affected
during the upgrade.
LiteSpeed 8.5 Install Guide
Installation Scenarios
12
3. Upgrade LiteSpeed UI Console.
To upgrade the LiteSpeed UI Console, run the LiteSpeed installation. Install LiteSpeed Locally
4. Upgrade LiteSpeed on SQL Server instances.
To upgrade
LiteSpeed...
Locally
Complete the following steps...
a. Install LiteSpeed Locally.
b. Configure Server Instances.
Remotely
a. If the central repository is not installed or upgraded already (for
example, during a local install), run the Instance Configuration wizard
and select to configure the central repository. For more information,
see Upgrade Repositories on page 17.
b. Install LiteSpeed on Remote Server Instances.
NOTE: You must have the Complete installation on the machine from which
you wish to run the remote deploy.
On a cluster
Run local or remote cluster installation. For more information, see Cluster
Installation on page 23.
5. Enable LiteSpeed jobs.
After you upgraded LiteSpeed on all instances, enable jobs that were disabled before the upgrade.
To enable jobs on a server instance
a. Select a SQL Server instance in the Job Manager window.
b. CTRL+Click to select multiple LiteSpeed jobs.
c. Right-click anywhere in the selected area and select Enable Jobs.
NOTE: If you stopped SQL Server Agent instead of disabling the jobs, right-click SQL Server Agent and
select Start.
Uninstall LiteSpeed
To uninstall, reinstall or change LiteSpeed, right-click LiteSpeed for SQL Server from the Add or Remove
Programs option in the Control Panel and select an option.
TIPS:
l
l
If you select Change and then Remove, you can delete LiteSpeed Local repositories during
the uninstall.
LiteSpeed Central repository and Repository Cleanup job for the central repository are not part of the
uninstall. They will remain after the uninstall has completed.
LiteSpeed 8.5 Install Guide
Installation Scenarios
13
Installation
Install LiteSpeed Locally
To begin a local server installation of LiteSpeed, copy the appropriate LiteSpeed .msi file to the server on which
you will install.
To install LiteSpeed on... Use this installer...
32-bit Windows
LiteSpeed.msi
64-bit Windows
LiteSpeed-x64.msi
You may run the installer from a network device, but for performance and stability reasons Quest Software
recommends that the installer be run locally.
To install LiteSpeed using the Installation wizard
1. Double-click .msi to start the installation.
2. Use the following information to help guide you through the installation wizard:
Screen
Description
User
Information
Enter your user information. You will need to decide whether this application should be
added to the Windows Start menu for all users or only for the installation owner. Quest
Software recommends the default installation, for all users.
Destination
Folder
Select the install location. You may select any directory that meets the following criteria:
l
The destination cannot be shared.
l
The path must exist on all nodes.
The default install location is: C:\Program Files\Quest Software\LiteSpeed\SQL Server.
Installation
Type
Select Complete to install all features or Custom to install only selected features. If you
select Custom, the components you may install are:
l
LiteSpeed Help
l
LiteSpeed UI Console
l
License
Information
LiteSpeed Core—Installs LiteSpeed for SQL Server on each SQL Server
instance on which you plan to use LiteSpeed.
Select one of the following options:
LiteSpeed 8.5 Install Guide
Installation
14
Screen
Description
l
Run LiteSpeed in Trial Mode or Restore Only Mode
l
Register your copy of LiteSpeed
Enter your license key and site message obtained from Quest Software. Ensure
that the key does not contain any line breaks or trailing spaces.
NOTE: If you upgrade from a previous LiteSpeed version (versions 5.x or earlier), you
will need to provide a new license key. For more information, see License Registration
on page 26.
After the LiteSpeed program files are installed, the LiteSpeed Instance Configuration wizard will help you
complete the installation of LiteSpeed components into your SQL Server environment.
Configure Server Instances
In the LiteSpeed Instance Configuration wizard you will select the SQL Server instances that will use LiteSpeed
and install extended stored procedures that LiteSpeed needs to run on the instances. You must install the
extended stored procedures to take full advantage of LiteSpeed functionality on the selected instances.
In addition, you can configure activity logging using this wizard. Activity logging works by installing a local
repository on a server instance to record its activity, and then installing a central repository to consolidate
information from the local repositories. Quest Software recommends that you configure activity logging to benefit
fully from LiteSpeed's features.
To configure server instances on the local computer
1. Start the Instance Configuration wizard from Start | All Programs | Quest Software | LiteSpeed for SQL
Server | LiteSpeed Instance Configuration. In the installation scenario, the LiteSpeed Instance
Configuration wizard is launched automatically.
2. On the SQL Instances page, select the SQL Server instances on which you want to install the extended
LiteSpeed stored procedures. The default behavior is to install the procedures onto all instances. Also,
when you re-run the wizard to modify existing options, be sure to select Install.
Tip: If you do not want to install the procedures on an instance, click the action and change it to Ignore.
When you select Uninstall next to an instance, the wizard removes the LiteSpeed extended stored
procedures from the instance.
Verify the connection details for each server. To change login details, select Windows or SQL Server
authentication.
3. On the Activity Logging page, select whether you want to configure a central and a local repository, or
only a local repository.
LiteSpeed creates a local repository database to collect backup activity information. This database can
be a dedicated database or an existing database of your choice. You can create the central repository
once and point to it in subsequent installs.
If you decide to create and configure only local repositories during installation, you may define a central
repository later using the LiteSpeed UI Console to enable consolidated logging.
LiteSpeed 8.5 Install Guide
Installation
15
4. Complete the wizard.
Use the following information to help guide you through instance configuration:
Page
Description
Service
Account
Specify login information for the LiteSpeed Activity Manager service. This service runs on
each server and merges statistics from the LiteSpeed local repositories to the central
repository database. Typically the account is a Windows domain account. It must have
permissions to update the central repository database using Windows authentication (for a
cluster configuration, the Windows account must have permissions on all nodes). For more
information, see Privilege and Grant Requirements on page 10.
NOTE:
l
You should select Local system when the central repository is on the same server
as the local repository. If the central repository is on another server, the Activity
Service will not be able to use Windows authentication to access it. You will need to
provide SQL Server login and password on the Central Repository screen.
Local
Reposit
ory
LiteSpeed uses the login details you specify to connect to the server instance, create the
database, and add objects to it. This account must have the appropriate permissions.
Native
Backup
Activity
Select whether you want to update the local repository with information about native SQL
Server backup activity and view it in the LiteSpeed UI Console. Click Schedule to modify
the default schedule.
Central
Reposit
ory
Point to the server instance and database.
Reposit
ory
Update
Indicate when you want the central repository to be updated with backup and job statistics.
You can have LiteSpeed update the central repository:
NOTE: The local and central repositories must have the same version number in the
LiteSpeed version table.
l
Automatically after any LiteSpeed activity, such as after every backup/restore
operation (best for real time statistics).
l
Via a scheduled SQL Server job (best for minimal network traffic).
l
Manually.
NOTE: Quest Software recommends that you select Automatically after any LiteSpeed
activity for both selections.
Reposit Select to set repository maintenance, including when to delete old data from repositories,
ory
and how much of that data to delete. Old data can be deleted from the local repository,
Cleanup central repository, or both. The repositories are individually selected to remove activity
older than a user-selectable number of days, weeks, months, or years. Additionally, Edit
Schedule launches a screen where schedule information can be changed.
Tip: Further repository cleanup can be accomplished by using the Purge Repository
Data procedure.
Proxy
settings
Select Use proxy settings for cloud connections. When selected, you can add the proxy
address and port. Optionally, you can select to use authentication and then enter username
LiteSpeed 8.5 Install Guide
Installation
16
and password.
Summar
y
Displays a summary of instance configuration selections.
Upgrade Repositories
LiteSpeed automatically upgrades LiteSpeed repositories during local install. If you install LiteSpeed remotely,
the central repository is not installed or upgraded, you need to run the Instance Configuration wizard and select
to configure the central repository. You can run the Instance Configuration wizard from any machine where you
have an instance of SQL Server and the LiteSpeed UI Console installed, for example, from the same machine
from which you run the Remote Deploy.
If you install the new central repository, you need to register it in the LiteSpeed UI Console. For more
information, see Register Central Repositories on page 27.
If you have a LiteSpeed central repository that needs to communicate with a repository for a previous version of
LiteSpeed, do one of the following:
l
l
l
Upgrade the statistic agent that transfers information between them on the outdated server instance. To
do this, run the Remote Deploy Configuration wizard and select Statistics Agent Only on the Installer
Path page. For more information, see Install LiteSpeed on Remote Server Instances on page 17.
Upgrade both the server where the LiteSpeedLocal and LiteSpeedCentral to the same version of
LiteSpeed.
Rename the LiteSpeedLocal and LiteSpeedCentral databases and recreate them by running the
Instance Configuration wizard.
Install LiteSpeed on Remote Server
Instances
You can install LiteSpeed on multiple remote server instances using the Remote Deploy Configuration wizard.
NOTES:
l
l
l
l
Before you run the Remote Deploy Configuration wizard, you must run Complete installation on the
machine from which you wish to run the remote deploy.
If the central repository is not installed or upgraded already (for example, during a local install), run the
Instance Configuration wizard and select to configure the central repository. For more information, see
Upgrade Repositories on page 17.
Make sure you have a Windows domain user account with Administrator rights for the server instances
you want to install LiteSpeed on. The machines must be part of the same domain.
WMI Windows Installer Provider must be installed on the remote computer running Windows 2003.
LiteSpeed 8.5 Install Guide
Installation
17
To create and deploy installation files
1. Click the Application Button and select Remote Deploy...
2. On the Remote Deploy Task page, select one of the following tasks:
l
l
l
l
Generate Remote Deploy configuration file—To create the installation files and optionally deploy
them. If you select the Complete or Core Components Only installation and deploy the files, this
will also configure remote server instances.
Deploy existing Remote Deploy configuration files—To deploy the installation and configuration
files generated by the Generate Remote Deploy configuration file task.
Configure LiteSpeed using existing Remote Deploy configuration files—To configure remote
server instances. You can use this task to complete installation after you deployed LiteSpeed
using a deployment tool such as SCCM or LANDesk.
Validate existing Remote Deploy configuration files—To see if the configuration files are valid for
installation and review installation options and expected actions.
NOTE: To deploy or validate existing Remote Deploy configuration files, you only need to select the
main configuration file (usually, LiteSpeedRemoteDeploy_Configuration.xml). The wizard will
automatically validate all remaining server-specific configuration files.
LiteSpeed 8.5 Install Guide
Installation
18
3. If you selected the Generate Remote Deploy configuration file task, review the following for additional
information:
l
Select one of the following installation types:
l
l
l
l
l
Complete—Installs LiteSpeed for SQL Server, LiteSpeed UI Console, and statistics agent
(if you configured LiteSpeed to collect statistics).
Core Components Only—Installs LiteSpeed for SQL Server and statistics agent (if you
configured LiteSpeed to collect statistics), but not the LiteSpeed UI Console
Client Only—Installs the LiteSpeed UI Console only.
Statistic Agent Only—Installs/updates the service that transfers information between local
and central repositories.
If the current user account has Windows administrative rights but does not have access to the
server instances, select Use a different account for installation to specify an additional account.
LiteSpeed 8.5 Install Guide
Installation
19
l
Select the SQL Server instances on which to install LiteSpeed. Start by clicking the Refresh
button to see all the machines found on the network. Select servers in the Servers drop-down list,
confirm selection and click Add. If you prefer to add servers manually, enter server names
separated by commas in the Servers field and click Add. Alternately, you can import servers from
a text file (one server name or IP address per line).
Use the following information to help guide you through instance configuration:
Page
Description
Service
Accoun
t
Specify login information for the LiteSpeed Activity Manager service. This service
runs on each server and merges statistics from the LiteSpeed local repositories to
the central repository database. Typically the account is a Windows domain account.
It must have permissions to update the central repository database using Windows
authentication (for a cluster configuration, the Windows account must have
permissions on all nodes). For more information, see Privilege and Grant
Requirements on page 10.
NOTE:
l
You should select Local system when the central repository is on the same
server as the local repository. If the central repository is on another server, the
Activity Service will not be able to use Windows authentication to access it.
You will need to provide SQL Server login and password on the Central
Repository screen.
Local
LiteSpeed uses the login details you specify to connect to the server instance, create
Reposit the database, and add objects to it. This account must have the appropriate
ory
permissions.
Native
Backup
Activity
Select whether you want to update the local repository with information about native
SQL Server backup activity and view it in the LiteSpeed UI Console. Click Schedule
to modify the default schedule.
Central Point to the server instance and database.
Reposit
NOTE: The local and central repositories must have the same version number in the
ory
LiteSpeed version table.
Reposit Indicate when you want the central repository to be updated with backup and job
ory
statistics. You can have LiteSpeed update the central repository:
Update
l
Automatically after any LiteSpeed activity, such as after every backup/restore
operation (best for real time statistics).
l
Via a scheduled SQL Server job (best for minimal network traffic).
l
Manually.
NOTE: Quest Software recommends that you select Automatically after any
LiteSpeed activity for both selections.
Reposit Select to set repository maintenance, including when to delete old data from
ory
repositories, and how much of that data to delete. Old data can be deleted from the
Cleanu local repository, central repository, or both. The repositories are individually selected
p
LiteSpeed 8.5 Install Guide
Installation
20
to remove activity older than a user-selectable number of days, weeks, months, or
years. Additionally, Edit Schedule launches a screen where schedule information
can be changed.
Tip: Further repository cleanup can be accomplished by using the Purge
Repository Data procedure.
l
Proxy
settings
Select Use proxy settings for cloud connections. When selected, you can add the
proxy address and port. Optionally, you can select to use authentication and then
enter username and password.
Summa
ry
Displays a summary of instance configuration selections.
On the License page, if you select Register later, the installed LiteSpeed version will operate as
a trial on all instances, until you register it or the trial period expires.
4. On the Deploy LiteSpeed page, select whether you want to deploy the files immediately or run the
wizard later and select the appropriate option.
Caution: The Remote Configuration wizard does not prevent you from deploying the files if they
are not valid.
NOTE: The Simultaneous installs field determines how many servers to install simultaneously. For
example, if you select to install LiteSpeed on 50 servers and specify 10 simultaneous installs, then the
wizard would install LiteSpeed on 10 servers at a time until it has installed all 50 servers.
5. Complete the wizard.
Install LiteSpeed Silently
LiteSpeed may also be installed locally from the command line or remotely using the LANDesk, SCCM or WMI
deployment tools.
NOTE: The silent installation procedure requires the user running the installer be logged into the Windows
machine with Local Administrator level access.
The silent install requires the following:
l
l
LiteSpeed installer.
Server-specific .xml file containing information about the machine onto which LiteSpeedis being
installed. You can generate it using the RemoteDeploy.exe utility, supplied with LiteSpeed. For more
information, see Install LiteSpeed on Remote Server Instances on page 17..
Command-Line Parameters
NOTE: All paths in the msiexec string should be passed as fully qualified paths, including the drive letter.
Parameter
Description
/i
This is an installation.
LiteSpeed 8.5 Install Guide
Installation
21
Parameter
Description
/l*v
Invokes logging (The *v invokes verbose logging.) The path of the log file is
indicated by, "C:\logfile.txt").
/qn
Suppresses the graphic user interface.
SILENTPHASE=0
Runs Instance Configuration silently.
SILENTINSTALLXML
Indicates the fully qualified path to the .xml file for Instance Configuration. Must
be local to the system.
NOTE: Version 6.5 of LiteSpeed introduced the new improved XML file format.
Although the configuration files created by a LiteSpeed version prior to 6.5 can
be manually used with the current LiteSpeed installer, it is recommended, that
you generate the new files. For more information, see Install LiteSpeed on
Remote Server Instances on page 17.
LICENSEKEY
Passes the license key.
SITEMSG
Passes site message.
LICENSETYPE
Indicates the license type:
l
"LICENSE"
l
"RESTORE"—LiteSpeed will be installed in Restore Only mode.
ENGINEONLY=1
Installs LiteSpeed for SQL Server without the LiteSpeed UI Console.
CLIENTONLY=1
Installs only the LiteSpeed UI Console.
INSTALLDIR="D:\Program
Files\Quest Software"
Provides an alternate install destination to the default C:\Program Files.
Examples
To run a silent install
msiexec /i "c:\Litespeed.msi" SILENTINSTALLXML="C:\LiteSpeedRemoteDeploy_Server.xml"
SILENTPHASE=0 /qn
To register LiteSpeed on all* instances during install
msiexec /i "c:\LiteSpeed.msi" LICENSEKEY="C20TM3Q3K2HD74UDLBMHC6KYV6HZ3MQFNXZFB-12345678-34" SITEMSG="Trial Version" LICENSETYPE="LICENSE"
SILENTINSTALLXML="c:\LiteSpeedRemoteDeploy_Server.xml" SILENTPHASE=0 /qn
*—all
instances that were specified in the .XML file.
To run an install with logging enabled
msiexec /i "c:\LiteSpeed.msi" /l*v "c:\logfile.txt"
SILENTINSTALLXML="c:\LiteSpeedRemoteDeploy_Server.xml" SILENTPHASE=0 /qn
LiteSpeed 8.5 Install Guide
Installation
22
To run install, but not Instance Configuration
msiexec /i "c:\Litespeed.msi" SILENTPHASE=0 /qn
To uninstall LiteSpeed
msiexec /uninstall "c:\Litespeed.msi"
Cluster Installation
Before you begin the installation process, please review the following requirements:
l
l
l
For cluster installs, it is required that users log in and install with a user account that has Administrator
rights to all the nodes in the cluster.
You must select an unshared local drive for the LiteSpeed installation directory. This location should be
the same for all nodes of the cluster. For example, C:\Program Files\Quest Software\LiteSpeed.
The Remote Registry service should be running on all nodes involved in a cluster installation.
Review the following to select the installation type.
Feature
Local
Remote
Installs on multiple nodes at once
Yes*
Yes
Installs on multiple instances on
those nodes
Yes
Yes
Automatically upgrades LiteSpeed
during install
Yes
Yes
Requires logging into the cluster
node
Yes
No
Requires running the .msi on each
node
Yes**
Yes
*—To the other cluster nodes.
**—Install LiteSpeed to the active node first. That should install LiteSpeed to all nodes. If there are problems
with the automatic installation to remote nodes, then install to the remaining nodes for the local cluster
installations.
Local Cluster Installations
Use the following installation instructions for both active-passive and active-active Microsoft Cluster Service or
Failover installations.
l
l
The user you are logged in as needs to be a Domain User in the local administrators group on all the
nodes of the cluster.
On Windows 2003, you need to have the WMI Windows Installer Provider installed.
LiteSpeed 8.5 Install Guide
Installation
23
l
l
If you supply the license once during the local install on the first node and it will install that license on the
other nodes. If the first node was installed in demo mode then the other nodes will be as well.
Install LiteSpeed to the active node first and then to the remaining nodes.
To install LiteSpeed on a cluster
1. Launch the .msi file on one node in the cluster. This node must have an install of each SQL Server
instance on which you want to install LiteSpeed.
2. Choose “Install LiteSpeed to all nodes automatically” which is the default option. This is the
recommended option for doing an initial installation to the cluster configuration.
3. Complete the wizard.For more information, see Install LiteSpeed Locally on page 14.
To install LiteSpeed on a node only
1. If you have added a new node to an existing cluster configuration and want to install LiteSpeed to this
new node only, run .msi on this particular node and use the “Install LiteSpeed to this node only” option.
Instance Configuration uses WMI to deploy the .msi file to all nodes. You do not need to run the installation from
the passive nodes or failover any nodes of the cluster during the installation process. This process automatically
upgrades any old version of LiteSpeed on any node.
If you have issues while running the Instance Configuration Wizard during installation, cancel out of the wizard
and complete the installation without it. After the installation completes run the Instance Configuration Wizard
from the Start menu and complete it.
Remote Cluster Installations
Using LiteSpeed Remote Deploy Tool
You can install LiteSpeed on clustered instances with the Remote Deploy tool. LiteSpeed automatically
installs on the selected server instances. For more information, see Install LiteSpeed on Remote Server
Instances on page 17.
NOTES:
l
l
l
To install or upgrade LiteSpeed on HP Polyserve and Veritas Storage Foundation cluster, you may need
to manually add all the nodes you want to deploy LiteSpeed to.
When running Remote Deploy on an active node, you cannot use a different account for installation on
the current cluster. The solution includes using a third machine, using a passive node, or using any node
name instead of the cluster name on the step "SQL Servers."
An access is denied error can sometimes be displayed on the SQL Servers step when the user connects
to an active node of a cluster and then tries to add a cluster name using the Add Server step. The
solution includes running Remote Deploy from passive node, using an Administrator account to connect
to node, or running Remote Deloy from a third machine that is not in the cluster.
Using SCCM or LANDesk
LiteSpeed can also be deployed silently via a deployment tool such as SCCM or LANDesk. In a mass
deployment, the steps are as follows:
LiteSpeed 8.5 Install Guide
Installation
24
1. Deploy the MSI using a deployment tool.
2. Create the XML files for the servers.
3. Configure the instances.
Deploy the MSI using a deployment tool
To setup the package for deployment create a distribution package in your deployment tool.
In the command line, specify "silentphase=0" to cause Instance Configuration not to be run. You can customize
the installation by creating an MSI transform and by using the TRANSFORMS=MyTransformName.mst commandline parameter for MSI package.
The package should be set to run in silent mode with no user interaction and to suppress any reboot. Separate
packages need to be set up for x32, and x64 systems.
Once the package is setup create a distribution task and deploy the .msi to the cluster nodes.
Create the XML files for the servers
Use the Remote Deploy Configuration wizard to create the .xml files. For more information, see Install LiteSpeed
on Remote Server Instances on page 17.
Configure the instances
You can configure LiteSpeed on the remote server instances using the Remote Deploy wizard, or by logging
into the server and manually running Instance Configuration.
LiteSpeed 8.5 Install Guide
Installation
25
4
License Registration
You need to license LiteSpeed for SQL Server with a commercial key or a custom evaluation key to use many
advanced features for managing backup and restore processes.
Tips:
l
l
There is a way to manage licenses using Edit SQL Server Registration dialog. See Register Server
Instances.
You can set or change the license for any server registered in the LiteSpeed console by right-clicking
on the SQL Server instance, selecting the "LiteSpeed Instance Settings," and then selecting
"LiteSpeed License."
If you purchased LiteSpeed and have a valid license, you can register LiteSpeed during the installation or
upgrade, or any time:
l
Using the LiteSpeed UI Console (Help | License...)
note: This will only register a local copy of LiteSpeed
l
Using xp_sqllitespeed_licenseinfo
l
Using the LicenseInfoCmd command-line utility
note: For more information about the LiteSpeed extended stored procedures and command-line utilities,
please refer to the LiteSpeed User Guide.
If you want to purchase LiteSpeed or require a trial extension or have any other licensing questions
related to your purchase please contact your sales representative or go to
https://www.quest.com/company/contact-us.aspx.
LiteSpeed 8.5 Install Guide
License Registration
26
Configuration
Register Central Repositories
When you create or upgrade a central repository, you must register it in the LiteSpeed UI Console before you
can view its activity statistics.
Note: If the LiteSpeed install includes a central repository and the console, then LiteSpeed defaults the
console to use that central repository automatically without the need to manually register and select it in the
LiteSpeed console.
To register a repository
1. Click Repository Registration from the Application Menu.
Alternately you can click beside the Central Repository field at the bottom of the LiteSpeed UI
Console and select Select Repository.
2. Click
Add repository and complete the Register New Repository dialog fields.
Server name:
Enter the name of the server instance, or click
available server instances.
Display name:
Enter the name to display in the navigation pane tree.
Connect using:
Select the following options:
Windows
authentication
Select this option to connect to the SQL Server instance using Windows
authentication.
SQL Server
Authentication
Select this option to connect to the SQL Server instance using SQL Server
authentication. Complete the Login name and Password fields.
Additional Connection
Parameters
Enter additional connection string parameters.
Repository database:
Displays the name of the repository database selected.
Repository version:
Displays the version of the repository.
3. Click
to select from a list of
TIP: Use this selection as needed to include custom parameters such as
encryption, AlwaysOn and others to the SQL server connection string.
Test connection.
TIPS:
LiteSpeed 8.5 Install Guide
Configuration
27
l
l
Select add repository, edit connection, delete connection, test connection, import, and export by clicking
the corresponding button in the Edit Repository Registration dialog. Imports can be done from .csv files
and from LiteSpeed 4.x.
You can click the Display name, Authentication, Login, or Password fields in the grid to change
their value.
Select a Central Repository
The LiteSpeed UI Console displays the activity statistics in the Backup Manager Overview tab for the selected
central repository. You can register multiple central repositories in the LiteSpeed UI Console, but you can only
view activity for one at a time.
To select a central repository
Select Tools | Options and select the repository on the General tab.
Tip: You can also click beside the Central Repository field in the status bar of the LiteSpeed UI Console and
select the repository from the list.
Register Server Instances
You must register server instances before you can manage them in the LiteSpeed UI Console. You can also
register server instances that do not have LiteSpeed installed on them and perform native backups and restores
through the LiteSpeed UI Console.
NOTE: You need to register all SQL Server instances involved in log shipping in the LiteSpeed UI Console to
retrieve log shipping data for them.
Scenario
There are several server instances configured to report to a central repository and you need to register some
of them in your LiteSpeed UI Console.
To register server instances
TIP: From the Edit SQL Server Registration window you can add server, edit connection, display overview tab,
test connection, import and export. You can also edit credential information for each instance including display
name, server name, authentication, login, password, and parent group. You can also see information for each
instance including license, license type, and license expire date.
1. Select Home | SQL Server Registration | Manage.
2. Click Add server to add an individual server or Import to import server instances from a CSV file or the
LiteSpeed central repository.
NOTE: You can import instances from a central repository, if the central repository is configured and
selected for use.
Scenario: Click Import and then From Central Repository. Select the central repository to import server
instances from, review the list of servers, optionally deselecting those you do not want to be registered in
your LiteSpeed UI Console, click OK and continue with step 4.
LiteSpeed 8.5 Install Guide
Configuration
28
3. (If you selected to import servers from a CSV file) Review the following for additional information:
The first line of a valid CSV file contains the following column headers:
l
l
l
l
DisplayName—Specify how you want to display servers in the navigation pane tree.
ServerName—Computer name or IP address following by port number: <IP_address>,
<port_number>.
Authentication—Windows or SQL Server.
LoginName—User name that is used for the SQL Server connection. It can be a Windows login in
the following format: 'Domain\Username', or SQL Server login.
l
Password—Encrypted password for the login. May be blank.
l
LicenseInfo—License key information (Site Message).
l
LicenseType—Examples: Trial, Permanent, Term.
l
LicenseEdition—Style of license. Example: Enterprise.
l
Path—Server group location of the instance.
l
ExpireDate—Date that the LiteSpeed license expires.
Next lines contain server parameters, separated by semicolons (;), a separate line for a server. You can
omit the LoginName and Password parameters to complete them later in the LiteSpeed UI Console.
Example:
DisplayName;ServerName;Authentication;LoginName;Password;LicenseInfo
LicenseType;LicenseEdition;Path;ExpireDate
W2K3-14;W2K3-14;Windows;DOMAIN\Username;3w663k3E
spb9884_sql_auth;spb9884;SQL Server;sa;321
NOTE: If you export server instances to a CSV file, it will contain SQL logins and obfuscated passwords.
You need to manually edit the CSV file to remove the connection information before you import
instances from this file.
LiteSpeed 8.5 Install Guide
Configuration
29
4. Complete the fields as necessary. Review the following for additional information:
SQL Server
Connect using
Specify server name or IP address using the following format: <IP_address>,
<port_number>.
Select either Windows authentication or SQL Server authentication (enter the
user name and password).
NOTE: Microsoft recommends using Windows authentication when possible
because it is more secure than SQL Server authentication.
Additional Connection
Parameters
Enter additional connection string parameters.
Advanced>>Display
Name
Enter the name to display in the navigation pane tree.
Tip: Use this selection as needed to include custom parameters such as
encryption, AlwaysOn and others to the SQL server connection string.
Tips:
l
l
You can click the Display name, Authentication, Login, or Password fields in the grid to change
their value.
Click Display Overview Tab to see the Overview tab of the LiteSpeed UI Console window for the
selected instance. This will let you stay on the registration dialog and continue editing or
registering new server instances, but still see overview information of the various instances.
5. (Optional) In the Server tree, click and drag server instances to move them between groups.
Tip: In the Server tree, you can see registered SQL Server Instance nodes sorted alphabetically. To use a
custom sort order, select View | Sort Instances | Custom.
Scenario
There are several server instances configured to report to a central repository and you want a new colleague
to manage some of them in their LiteSpeed UI Console. Define which server instances are eligible for import.
By default, LiteSpeed allows all of the instances to be imported into other clients when you select to import from
a central repository, unless you specifically exclude instances.
To exclude a server instance from import
1. Right-click a server in the Server tree in the navigation pane and select Edit | SQL Server Registration.
2. Clear the Allow import of this instance... checkbox and click OK.
Create Server Groups
To create server groups
1. Select the Backup Manager pane (CTRL+1).
2. Group the Backup Manager tree by server group (View | Group Instances By | Server Groups).
LiteSpeed 8.5 Install Guide
Configuration
30
3. Select one of the following options:
Create a top-level server group
Right-click SQL Servers at the top of the navigation tree and select
New SQL Server Group.
Create a subgroup of an existing
server group
Right-click the group in the navigation pane tree and select New
SQL Server Group.
Tips:
l
l
l
To create multi-level groups, create the parent group first. When you create the subgroup, the parent
group will already be there for you to select.
To edit or delete a server group, right-click the group and select the appropriate option.
You can also group server instances by categories. To switch between server groups and categories,
select View | Group Instances By.
LiteSpeed 8.5 Install Guide
Configuration
31
About us
Ab o u t u s
We are more than just a name
We are on a quest to make your information technology work harder for you. That is why we build communitydriven software solutions that help you spend less time on IT administration and more time on business
innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise,
security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the
global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we
continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of.
We are challenging the status quo by transforming into a new software company. And as your partner, we work
tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we
are in this together. Welcome to a new Quest. You are invited to Join the Innovation.
Our brand, our vision. Together.
Our logo reflects our story: innovation, community and support. An important part of this story begins with the
letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in
the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.
Contacting Quest
For sales or other inquiries, visit www.quest.com/company/contact-us.aspx or call +1 949 754-8000.
LiteSpeed 8.5 Install Guide
About us
32
Third Party Contributions
This product contains some third-party components (listed below). Copies of their licenses may be found at
referencing http://www.quest.com/legal/license-agreements.aspx. Source code for components marked with an
asterisk (*) is available at http://opensource.quest.com.
Table 1: List of Third-Party Contributions
Component
License or acknowledgement
ActiPro
Syntax Editor
(for Windows
Forms) 4.0
ActiPro Syntax Editor (for Windows Forms) 4.0 license
Active
Directory
Common
Dialogs .NET
2.5.0
Ms-PL
AWS SDK for
.NET 3.3.2
AWS SDK for .NET Copyright 2009-2013 Amazon.com, Inc. or its affiliates. All Rights
Reserved.
********************** THIRD PARTY COMPONENTS **********************
This software includes third party software subject to the following copyrights: Json processing from LitJson –
All the source code and related files distributed with this software have been dedicated to the
public domain by the authors.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute the software, either in
source code form or as a compiled binary, for any purpose, commercial or non-commercial,
and by any means.
- Parsing PEM files from Bouncy Castle Copyright (c) 2000 - 2011 The Legion Of The Bouncy Castle (http://www.bouncycastle.org)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software
and associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
LiteSpeed 8.5 Install Guide
Third Party Contributions
33
Component
License or acknowledgement
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- Performing CRC32 checks from vbAccelerator.com
vbAccelerator Software License
Version 1.0
Copyright (c) 2002 vbAccelerator.com
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution. The end-user documentation included
with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by vbAccelerator ( http://vbaccelerator.com/)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such thirdparty acknowledgments normally appear. The names "vbAccelerator" and
"vbAccelerator.com" must not be used to endorse or promote products derived from this
software without prior written permission. For written permission, please contact vbAccelerator
through steve@vbaccelerator.com. Products derived from this software may not be called
"vbAccelerator", nor may "vbAccelerator" appear in their name, without prior written
permission of vbAccelerator.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL VBACCELERATOR OR ITS CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the
vbAccelerator. For more information, please see http://vbaccelerator.com/ .
The vbAccelerator licence is based on the Apache Software Foundation Software Licence,
Copyright (c) 2000 The Apache Software Foundation. All rights reserved.
- MD5 checks in the Windows Phone 8 variant of the SDK from Microsoft Corporation
Microsoft
LiteSpeed 8.5 Install Guide
Third Party Contributions
34
Component
License or acknowledgement
Public License (MS-PL)
This license governs use of the accompanying software. If you use the software, you accept
this license. If you do not accept the license, do not use the software.
1. Definitions
The terms "reproduce," "reproduction," "derivative works," and "distribution" have the
same meaning here as under U.S. copyright law.
A "contribution" is the original software, or any additions or changes to the software.
A "contributor" is any person that distributes its contribution under this license.
"Licensed patents" are a contributor's patent claims that read directly on its
contribution.
2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, including the license
conditions and limitations in section 3, each contributor grants you a non-exclusive,
worldwide, royalty-free copyright license to reproduce its contribution, prepare
derivative works of its contribution, and distribute its contribution or any derivative
works that you create.
(B) Patent Grant- Subject to the terms of this license, including the license conditions
and limitations in section 3, each contributor grants you a non-exclusive, worldwide,
royalty-free license under its licensed patents to make, have made, use, sell, offer for
sale, import, and/or otherwise dispose of its contribution in the software or derivative
works of the contribution in the software.
3. Conditions and Limitations
(A) No Trademark License- This license does not grant you rights to use any
contributors' name, logo, or trademarks.
(B) If you bring a patent claim against any contributor over patents that you claim are
infringed by the software, your patent license from such contributor to the software
ends automatically.
(C) If you distribute any portion of the software, you must retain all copyright, patent,
trademark, and attribution notices that are present in the software.
(D) If you distribute any portion of the software in source code form, you may do so
only under this license by including a complete copy of this license with your
distribution. If you distribute any portion of the software in compiled or object code
form, you may only do so under a license that complies with this license.
(E) The software is licensed "as-is." You bear the risk of using it. The contributors give
no express warranties, guarantees or conditions. You may have additional consumer
rights under your local laws which this license cannot change. To the extent permitted
under your local laws, the contributors exclude the implied warranties of
merchantability, fitness for a particular purpose and non-infringement.
** iOS4Unity - https://github.com/Hitcents/iOS4Unity/
** SQLitePCLRaw - https://github.com/ericsink/SQLitePCL.raw
LiteSpeed 8.5 Install Guide
Third Party Contributions
35
Component
License or acknowledgement
CMarkup
Developer
11.2
CMarkup Developer 1.0 license
Developer
Express
.NET
(DXperience)
13.2
Developer Express .Net (DXperience) 13.2 license
Json.net
7.0.1
Copyright (c) 2002 JSON.ORG
Permission is hereby granted, free of charge, to any person obtaining a copy of this software
and associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
The Software shall be used for Good, not Evil.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
THE USE OR OTHER DEALINGS IN THE SOFTWARE.
LibTomCrypt
1.17
LibTomCrypt 1.17 license
LZMA 4.65
Public Domain
Microsoft
Windows
Azure
Storage 6.1
Apache License Version 2.0, January 2004
QuickLZ 1.5
QuickLZ Commercial License 1.0
SharpZipLib
0.85.5.452
The library is released under the GPL with the following exception:
Linking this library statically or dynamically with other modules is making a combined work
based on this library. Thus, the terms and conditions of the GNU General Public License cover
the whole combination.
As a special exception, the copyright holders of this library give you permission to link this
library with independent modules to produce an executable, regardless of the license terms of
these independent modules, and to copy and distribute the resulting executable under terms
of your choice, provided that you also meet, for each linked independent module, the terms
and conditions of the license of that module. An independent module is a module which is not
derived from or based on this library. If you modify this library, you may extend this exception
to your version of the library, but you are not obligated to do so. If you do not wish to do so,
LiteSpeed 8.5 Install Guide
Third Party Contributions
36
Component
License or acknowledgement
delete this exception statement from your version.
Note The exception is changed to reflect the latest GNU Classpath exception. Older versions
of #ziplib did have another exception, but the new one is clearer and it doesn't break
compatibility with the old one.
Bottom line In plain English this means you can use this library in commercial closed-source
applications.
Task
Scheduler
Managed
Wrapper
2.5.21
Copyright (c) 2003-2010 David Hall
Permission is hereby granted, free of charge, to any person obtaining a copy of this software
and associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
THE USE OR OTHER DEALINGS IN THE SOFTWARE.
TimeSpan
Helper
Library 2.1.4
Copyright (c) 2009, CodePlex Foundation All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
l
l
l
Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
Neither the name of CodePlex Foundation nor the names of its contributors may be
used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
LiteSpeed 8.5 Install Guide
Third Party Contributions
37
Component
License or acknowledgement
WinForms
Group
Controls
1.5.3
This component is governed by the Apache License 2.0 (Apache)
Wizard .NET
Library 2.1.0
Copyright (c) 2013 David Hall
Permission is hereby granted, free of charge, to any person obtaining a copy of this software
and associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR
THE USE OR OTHER DEALINGS IN THE SOFTWARE.
LiteSpeed 8.5 Install Guide
Third Party Contributions
38
Index
installer files 14
.
instance configuration 15
.msi 14
L
A
license 26
activity logging 15
LiteSpeed architecture 5
Activity Manager service account 10
M
C
mass deployment 24
central repository 28
P
cluster installation 23
local 23
permissions 10
instance configuration 15
remote 24
remote deploy 17
command line (LiteSpeed)
remote install 17
silent install 21
privileges 10
R
configure activity logging 15
configure LiteSpeed server instances 15
register LiteSpeed 26
Copyright 2
register server instances 28
D
registration key See license
remote installation 17
DCR See Double Click Restore
cluster 24
Double Click Restore
standalone 17
requirements 10
remove LiteSpeed repositories 13
repositories 6
E
install 15
register 27
exe backup files See Double Click Restore
select 28
I
uninstall 13
upgrade 17
installation
cluster 23
local 14
remote 17
silent 21
installation requirements 8
installation scenario 12
requirements 8
S
server groups
create 30
server instances 28
LiteSpeed 8.5 Install Guide
39
silent installation 21
cluster 24
standalone 21
statistics
collect in repositories 6
T
trial key See license
trial mode See license
U
uninstall LiteSpeed 13
uninstall repositories 13
upgrade license key See license
upgrade LiteSpeed 12
upgrade repository 17
upgrade scenario 12
LiteSpeed 8.5 Install Guide
40