NetBackup backups and/or duplications report status 129 'Disk storage unit is full' when targeting Windows-based Media Server Deduplication (MSDP).
|Article:TECH148008|||||Created: 2011-01-12|||||Updated: 2013-09-24|||||Article URL http://www.symantec.com/docs/TECH148008|
NetBackup backups and/or duplications to Windows-based MSDP diskpool fails with status 129 'Disk storage unit is full'.
status 129 'Disk storage unit is full'
NetBackup 7.0.x/7.1.x Windows-based NetBackup media server deduplication engine. NOTE: NetBackup 7.5 will already use the values outlined below.
NetBackup by design pads the deduplication diskpool storage percent used by 10% which can lead to NetBackup reporting a 'disk storage unit is full' condition when there is still space left on the diskpool.
Lower the threshold numbers in contentrouter.cfg on the NetBackup MSDP mediasvr.
On NetBackup MSDP mediaservers the contentrouter.cfg file is located within <dedup_path>\etc\puredisk
1. Save a copy of the existing contentrouter.cfg file
2. Edit the 'WarningSpaceThreshold, LowSpaceThreshold and VeryLowSpaceThreshold lines to look like:
3. (Optionally): set the high water mark (HWM) on the dedup diskpool to 100% via NetBackup administration console or via commandline on the NBU master:
nbdevconfig -changedp -stype PureDisk -dp <diskpool_name> -hwm 100
NOTE: in a future version of NetBackup, the contentrouter.cfg settings for Media Server Deduplication will use more appropriate default values for free/used space determination.
NOTE2: for UNIX/Linux based MSDP platforms and for PureDisk storagepools, do not modify the WarningSpaceThreshold, LowSpaceThreshold and VeryLowSpace thresholds to the aforementioned values due to the way non-Windows filesystems may reserve space. Doing so could cause corruption if the amount of used space exceeds the filesystem's internally controlled reserved space. Filesystems formatted with ext3 reserve 5% of blocks by default. This can be changed via 'tune2fs'. Consult the documentation for your operating system before changing the filesystem.
Article URL http://www.symantec.com/docs/TECH148008