Error Message

The System Event Log will record Event ID 7031 Errors related to the service termination;

Log Name:       System
Source:         Service Control Manager
Date:           xxx
Event ID:       7031
Task Category:  None
Level:          Error
Keywords:       Classic
User:           N/A
Computer:       xxx

Description:
The Veritas DLO Maintenance Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
 

The DLOMaintSvcu.log will also record;

01/25/24, 10:22:32:810, dlomaintsvcu.exe, 27004:, E>, deltamerge.cpp( 418 ), [EXTRA] DeltaMergeThread::AddForExSL() 75% of total physical memory is consumed 
01/25/24, 10:22:32:811, dlomaintsvcu.exe, 27004:, E>, deltamerge.cpp( 419 ), [EXTRA] DeltaMergeThread::AddForExSL() Restarting VeritasDLOMaintenanceSvc  
 

In previous versions of DLO, the DLO Maintenance process had been seen to consume high levels of system memory, impacting server performance.

The DLO 9.8.3 release incorporated code to help limit the memory usage, setting a threshold of 75% of the total system memory; i.e. if the total memory is 64Gb, 75% = 48Gb.

• If DLO detects that more than 75% memory is being used, a restart of the DLO Mainenance Service is then forced, to release any memory being used by it.

A situation can occur where DLO is not consuming the system memory, but some other application. DLO will still monitor for the 75% used threshold and if that is exceeded, it will force the DLO Maintenance Service to restart. The service terminates and is restarted automatically by the Recovery options for the service, but it can start up, detect that the memory is still over 75% used, as the other application is still using that amount and therefore force the service to be restarted again. It will stay in that loop until the memory drops below the 75% used threshold. 

Memory management for the DLO Maintenance Service is currently being investigated and may result in changes or improvements in the next release of DLO.

A supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix.

Veritas Technologies LLC currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.