Quantcast
Channel: Software Communities: Message List - LiteSpeed for SQL Server
Viewing all 150 articles
Browse latest View live

Re: LiteSpeed impact on msdb database?

$
0
0

Let me add a few metrics that may help you size the LiteSpeed repository:

 

You can estimate about 15MB per 1,000 activity items.

 

So if you have an instance with 10 databases that each had daily full/diff backups and 30 minute t-log backups, you would have:

10 DBs * (1 Full/Diff + 48 T-Log) = 490 activity items – we’ll round this up to 600 activity items / day

 

Let’s assume you need 180 days of history: 180 * 600 = 108,000

 

108,000 / 1,000 * 15 MB = 1,620MB = 1.6 GB

 

For the central repository:

 

Add up all the local repository sizes (or assume they are all similar and multiple the above number by the number of instances)

 

But these are all estimates. Number could be higher or lower depending on different environmental factors related to backup and restore options selected.


LiteSpeed installation in Active Passive cluster environment

$
0
0

Do we need to have 2 licenses for both active and passive nodes ?  Any change in the installation steps ?

Re: LiteSpeed installation in Active Passive cluster environment

$
0
0

In an Active-Passive scenario, you would need a production license for the active node and a non-production license for any passive nodes. If this were an active-active cluster, you would require production licenses for each node. Non-production licenses are available from your sales rep at a 50% discount. Installation on clusters is covered in the Installation Guide. I would recommend you consider moving to LiteSpeed 7.1, which was released last week, as it includes improvements to the installation process.

Litespeed installation on cluster node

$
0
0

We are planning to setup active-passive failover cluster. Currently we are planning to install just the single node cluster and install the other node may a week or two later. In mean time we would like to take the backups using litespeed tool. My question over here is, does litespeed installation require a reboot of the server ?

Re: Litespeed installation on cluster node

$
0
0

No reboot required.

 

Thanks.

 

--

David Gugick

Product Management

Dell | Data Protection, Quest Software

Quest Software is now part of Dell

Re: Litespeed installation on cluster node

$
0
0

Thanks David. I just tested it on the VM server. Te installation process of LiteSpeed looks slightly different than on the stand alone servers. It prompted me for installation of msi files ? What are these msi files?

Re: Litespeed installation on cluster node

$
0
0

Deepak,

 

I'm not sure what you're referring to. The installation on physical or virtual should be the same. The installer, itself, is a Microsoft Installer .MSI file. It should only be prompting you for the installation location on disk before running Instance Configuration at the end of the install process.

 

Can you provide a screenshot of what you are seeing?

 

Thanks.

 

--

David

Re: Litespeed installation on cluster node

$
0
0

LS_1.JPGLS_2.JPG

 

LS_3.JPG

Here you go...

 

So David, when we install on the second node we have to probably follow the same steps.


Litespeed template does not save Process affinity

$
0
0

When i go to the advanced option of my litespeed template it will not save the processor affinity when I set it to 3 which is for threads 1 and 2.  It saves it for the other options. 

Re: Litespeed template does not save Process affinity

$
0
0

I was able to duplicate the issue and will notify the development team to have it fixed for the next release.

 

Just a note on Affinity: If you're looking to control the number of compression threads, you should use Threads instead. Affinity actually binds LiteSpeed compression threads to specific CPU Cores on the server. Using the setting in a Template could cause backup problems if the server being deployed to does not have the CPUs assigned or if those CPUs are busy with other operations. If you really want to restrict the number of compression threads, you should use Threads instead. By forcing LiteSpeed onto a specific CPU, you prevent Windows from properly handling multi-threading on the server. Meaning if another process on the server is running and Windows has assigned it to CPU 1 or 2, then the LiteSpeed backup will be CPU constrained even if there are other CPUs available on the server that have no activity. Affinity is an advanced option best used on specific servers where you really need to control on which CPUs the product runs.

 

Threads will control how much CPU can be used by LiteSpeed. For example, if you have 8 CPU Cores and back up using 2 Threads, then LiteSpeed could never use more than 25% of the CPU on the server (assuming the compression level really required that much). You are constraining LiteSpeed with only 2 threads since most servers have available CPU that could be used to better compress and process backups. One option might be to use Adaptive Compression (if you have LiteSpeed Enterprise) with the Speed option as that will allow LiteSpeed to adjust the compression level dynamically throughout the backup for best speed and best compression. If you use the default setting of (n – 1) threads, LiteSpeed will be able to back up fast, but likely with better compression that if you specified a thread limit. Having said that, if you really need to limit CPU utilization, then using 2 threads will do that on servers with more than 2 CPU Cores. But you may want to use a low compression level (1 or 2) to ensure the backups run as fast as possible.

 

Let me know if you have any further questions and thanks for reporting the issue.

 

 

--

David

Is there a way for Litespeed Compression to run without having to match an extension?

$
0
0

Hi

 

We use a third party software to run backups on our SQL Servers (HP Data Protector). The HP Dataprotector software starts a ordinary SQL Server backup, but I can't for some reason make it use the LiteSpeed engine.

 

HP Data Protector creates a backup with a long filename but witouth an extension, so I guess that is why the Litespeed engine isn't called.
When I start an ordinary SQL Backup with an extension specified in the settings, it use the Litespeed engine.

 

Is there a way for Litespeed Engine to run without having to match an extension? To have it run for every backup run on that sql server?

Re: Litespeed installation on cluster node

$
0
0

David, I have attached the screen shots. Please let me if I can move forward.

 

Thanks,

Re: Litespeed installation on cluster node

$
0
0

Apologies. My reply from a few days ago never posted.

 

It appears as though you are using a version of LiteSpeed prior to 7.1. In that case, you can select Manual to avoid installing LiteSpeed on the other nodes in the cluster. You can then install later on and select Manual again. You must install in the same folder on all nodes. The MSI is the MSI installer for LiteSpeed that will be pushed to the other nodes. If you are using Manual, I assume you don not need to provide the MSI. But if the installer keeps you from moving forward, then supply the MSI and the installer would then ignore it because Manual is selected.

 

In LiteSpeed 7.1, the Manual option was removed because many customers had issues around Manual installs. By default LiteSpeed installs to all nodes in the cluster. The option may show up again in the next release.

 

--

David

Re: Litespeed installation on cluster node

$
0
0

David,

 

We are planning to install the latest version of litespeed. Currently we are working on the single node cluster and planning to add the other node probably a week or two later. How to install the litespeed on the other node, as you said it will automaticall install on all the nodes.

 

The other question is , do we have to select local drive for installation or the shared drive ?

 

Thanks,

Re: Litespeed installation on cluster node

$
0
0

You cannot avoid installing LiteSpeed on the passive node in the new release. It will install automatically. If the node is offline, you may run into an install issue that was just reported by a custiomer. If you have a problem, you'll need to open a support case to get an updated binary. Please review the Install Guide for additional installation instructions. You install locally on each node.


Re: Litespeed installation on cluster node

$
0
0

I am not avoiding the installation of LiteSpeed on the other node. The cluster will have a single node for first two weeks. When the other node is ready we will add it to the cluster to make it active- passive. Probably we have to uninstall and reinstall it again to avoid issues. Thanks for the info.

Re: Litespeed installation on cluster node

$
0
0

Ok then, that should be fine. When you install on the second node, it will reinstall on the first one (that cannot be avoided in the new release). But that should not cause any issues from what engineering conveyed to me.

 

Thanks.

Re: new version LiteSpeed SQL SERVER 7.1 released?

$
0
0

When will 7.2 be released?  I thought it was scheduled for March... but now I'm seeing that 7.1 was just released.  Is 7.1 stable?  I was expecting 7.2 to clean up some bugs in 7.1.

 

Thanks,

Re: new version LiteSpeed SQL SERVER 7.1 released?

$
0
0

7.1 is new as of 2 weeks ago. What issues are you having with the new version?

 

--

David Gugick

Product Management

Dell | Data Protection, Quest Software

Quest Software is now part of Dell

Does LiteSpeed supports Partial Backups

$
0
0

We have a 2 TB database where most of the data is not modified. So we are planning to make some of the data files to read only. So that we don't have to backup all the data. Does litespeed support the partial backups?

Viewing all 150 articles
Browse latest View live