Purging Maintenance on child NS - Parent Setting overwriting Child settings

Article:TECH177378  |  Created: 2011-12-20  |  Updated: 2014-06-24  |  Article URL http://www.symantec.com/docs/TECH177378
Article Type
Technical Solution


Environment

Issue



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.  


Environment



Symantec Management Platform  7.1 SP1, SP2, 7.5


Cause



This is working as designed.


Solution



This issue has been reported to Symantec Development team. This behavior will be reviewed to be changed or not in a future release.


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 statement:
 

--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')

On the Child  SMP, run the following query:

--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'

 


Supplemental Materials

SourceETrack
Value2641244

Legacy ID



nefi_garrido


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


Terms of use for this information are found in Legal Notices