Image duplications using Storage Lifecycle Policies are not starting

Article:TECH148656  |  Created: 2011-01-20  |  Updated: 2013-09-18  |  Article URL http://www.symantec.com/docs/TECH148656
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Environment

Issue



The nbstlutil stlilist -U command keeps shows images are not duplicated. The number of images in this state will continually increase.


Error



No error is shown.


Environment



One known cause of this issue is that the nbstserv process is not running on Unix or on Windows the NetBackup Storage Lifecycle Manager services is not running.

In such a situation, no error is reported on standard Activity Monitor or regular reporting information. Additionally, depending on the general Storage Lifecycle manager threshold, it may be many hours before the problem is detected. 


Cause



Without the nbstserv service, the expected image duplications and storage management does not occur, accumulating pending duplications and fulfilling the primary backup storage of all the SLP.

 


Solution



As a first step: Check the nbstserv status and stability.

Trying to execute the duplication with the nbstlutil active –backupid <BACKUPID> returns an error message:

Caught CORBA SystemException from SSmgrOperations: system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
OMG minor code (2), described as '*unknown description*', completed = NO

Then, try starting the nbstserv service and then try to perform duplication with the "nbstlutil active" command.

A known cause for the nbstserv startup failure has been the absence of the correct VXUL configuration for this service.

The file:

<install-path>\netbackup\nblog.conf  (Windows)
/usr/openv/netbackup/nblog.conf (Unix)

must contain the correct stanza for the originator 226. 

By default it appears like this:

226.L10nResource=nbstserv
226.NtEventLogSourceName=nbstserv
226.OIDNames=nbstserv


 

 

 

 




Article URL http://www.symantec.com/docs/TECH148656


Terms of use for this information are found in Legal Notices