Purging Maintenance on child NS - Parent Setting overwriting Child settings

book

Article ID: 155630

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

Customer configured purge maintenance on the children separately from its configuration on the parent.  The reason for this was because with AMS and CMS residing on the same parent, they can not allow records to get purged from the parent DB.   
Customer reported that the purge maintenance settings on the parent replicate to the child servers, even if the settings are manually altered on the children.  They need to have  purge maintenance on the child enabled, and  purge maintenance on the parent disabled. But, because of replication the disabled purge setting on the parent, replicates to the children each night, disabling resource purging on the child NSs.

Cause

This is working as designed.

Resolution

Prior to SMP 7.5 SP1:
As workaround it was suggested to set NoReplication attribute for Purge Maintenance item.
After that this item will not be replicated to child anymore.
It can be done with following statements:

1. Set 'NoReplication' attribute for Purge Maintenance item

--On the Parent SMP, 0 rows affected is also ok.  It just means it was already set correctly
UPDATE Item
SET Attributes = Attributes + 4
WHERE Guid = 'de4a3a7c-2147-463e-8a06-a23b6c6e719b'
and Attributes & 4 <> 4

OR you could use the following query as well:

UPDATE Item
SET Attributes = 4 | Attributes
WHERE Guid = 'de4a3a7c-2147-463e-8a06-a23b6c6e719b'


Note: You can run the following query just to find out what are the current attributes for this object:

--See current attributes for the purging maintenance page
select * from fnGetItemAttributes ('de4a3a7c-2147-463e-8a06-a23b6c6e719b')

2. On the Child  SMP, run the following query in order to make changes to the policy:

--On the Child, this sets it to think it was imported locally
update ItemImportMethod
set ImportMethod = 0   --3 usually means that it was replicated
where Guid = 'de4a3a7c-2147-463e-8a06-a23b6c6e719b'

 

Post to SMP 7.5 SP1:

Starting with SMP 7.5 SP1 now you can change if these settings are replicated or not. On your Parent SMP go to Console>Settings>Notification Server Settings>Purging Maintenance. Right-click on it and select 'Hierarchy>Properties'. You will see under 'Hierarchy Properties' window 'Purge Data' and 'Purge Computers' checkboxes. Selecting 'Purge Data' will allow you to edit and keep the changes on the Child SMP for the 'Purge Legacy Saved Reports' and  'Purge Outdated Agent Registration Entries' sections under the 'Purging Maintenance' tab. Selecting 'Purge Computers' checkbox allows you to edit and keep the changes on the Child SMP under 'Purge computers managed by this NS, which have not reported data for: ' section.
 

Applies To

Symantec Management Platform  7.1 SP1, SP2, 7.5, 7.5 SP1