Litespeed full backups are causing large IO and slowness on the server after a large backup is completed (4239236)

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Litespeed full backups are causing large IO and slowness on the server after a large backup is completed
Description

At the end of full backups on very large databases, a large IO process runs and is very intensive, which causes the production server to hang. What is happening during this time, and can it be stopped?
Cause

If in the backup script OLRMAP=1 is set, this causes Litespeed to attach an "LSM" file to the backup once the backup itself has completed.
Resolution

If you set this parameter to OLRMAP=0, it prevents this issue from occurring.

Please note that this will not affect your ability to use Object Level Recovery (OLR).
It just places the creation of the LSM file at the back end of the OLR process. (IE: when OLR is actually run) rather than on the front end (IE: when the backup is created).

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title