Purging Maintenance on child NS - Parent Setting overwriting Child settings
|Article:TECH177378|||||Created: 2011-12-20|||||Updated: 2012-02-06|||||Article URL http://www.symantec.com/docs/TECH177378|
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.
Symantec Management Platform 7.1 SP1, SP2
This is working as designed.
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:
SET Attributes = 4 | Attributes
WHERE Guid = 'de4a3a7c-2147-463e-8a06-a23b6c6e719b'
Article URL http://www.symantec.com/docs/TECH177378