When System memory is above 170GB Media Server Deduplication configuration may fail due to spoold core dumping

Article:TECH159584  |  Created: 2011-05-09  |  Updated: 2013-01-17  |  Article URL http://www.symantec.com/docs/TECH159584
Article Type
Technical Solution


When trying to Configure a MSDP disk pool on a system with a large amount of physical memory an error is received during the 'Configuring Media server deduplication pool' stage of the wizard.  The issue occurs when spoold is initializing the cache with a bits setting that is higher than a support number.  Spoold currently supports a maximum of 28bits and in an environment with more than 170GB of RAM it is possible that spoold will use 29bits.



MSDP Configuration pop-up error:
Database system error . RDSM has encountered an STS error : failed to update storage server configuration due to unsupported platform ,invalid configuration or system error.

Starting spoold
Warning: manually modifying PureDisk services can cause unexpected behavior!
-n Warning: press CTRL+C to abort
Checking for PureDisk ContentRouter
-n Starting PureDisk ContentRouter: spoold
Segmentation Fault - core dumped
"/usr/openv/pdde/pdconfigure/etc/init.d/Solaris/pdde start spoold" failed (139)
Wed Oct 5 18:50:49 GMT 2011
ERROR: starting spoold failed

The following can be seen in a spoold trace:
# spoold -v --trace

Info: Auto-sized value for /Storage_path/etc/puredisk/contentrouter.cfg: section Cache, entry Bits to 29 bits

The maximum bits support currently is 28bits.

The following line will be see before spoold crashed:
Trace [1]: StorageDBOpen: done
Trace [1]: CacheInit: bits = 29
Segmentation Fault (core dumped)



Any media server with greater than 170GB of RAM.


The issue occurs because during setup Netbackup tries to configure a cache for MSDP based on the amount of physical RAM . If the System has a large amount of physical RAM the the cache initialization will fail. In this instance the customer had 256GB of RAM .

Trace log from spoold process on a Windows machine: 

April 14 11:07:36 TRACE: Loading Storage Index Manager Configuration.
April 14 11:07:36 TRACE: OSGetTotalRamValue: 262140 MB
April 14 11:07:36 INFO: Auto-sized value for f:\Storage\etc\puredisk\contentrouter.cfg: section Cache, entry Bits to 29 bits

Last line from trace log : 

April 14 11:07:36 TRACE [000000000267F8C0]: CacheInit: bits = 29



Remove the currently half configured MSDP environment.

Edit the following contentrouter.cfg script:
UNIX: /usr/openv/pdde/pdcr/etc/contentrouter.cfg
WINDOWS: <installpath>\VERITAS\pdde\contentrouter.cfg

Note: The contentrouter.cfg file may reside in a storage partition. To determine what file is being used, run -

/usr/openv/pdde/pdcr/bin/spoold --trace -v

Look for the following line -

Info: Auto-sized value for <Storage partition>/etc/puredisk/contentrouter.cfg: section Cache, entry Bits to 31 bits

This is the file that needs to be modified.


One way is to change Bits in the Cache section of contentrouter.cfg file to 28 -



Another way is to leave Bits at 0 and change the MaxCacheSize setting from 75% to a percentage of your memory that equivalent to 36GB of RAM.  For example if the MSDP environment is 32TB of disk space, then 32GB of RAM is sufficient for spoold.  In an environment where the system has 261GB of RAM, set the MaxCacheSize to 15% which is roughly 36GB of RAM for the spoold process.


During the next MSDP configuration, spoold should start-up without a problem.

You can run 'spoold --trace -v' to make sure the Bits has changed to 28.


Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec Corporation to be addressed in a forthcoming Maintenance Pack, Release Update, or version of the product.  Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Symantec's 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 refer to the maintenance pack readme or contact NetBackup Enterprise Support to confirm this issue (ET2566659) was included in the maintenance pack. 
As future maintenance packs and release updates are released, please visit the following link for download and readme information: 

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

Terms of use for this information are found in Legal Notices