Jay_Son
16 years agoLevel 5
Out of FS space for /usr/openv (NBU Production Server)
I received an error from my Device Monitor - database system error. DSM is unable to connect to the DB, issue: connect - I have ran out of disk space and need to have our storage group "grow" more space for my FS. Netbackup 6.5.3 daemons are currently at a "stop" state (inc. Media Servers). I was told that there is a temp fix from my UNIX Admin. I am currently "mirroring" /usr/openv. Is it possible (i'm sure, not recommended) to remove this mirror for a quick fix and continue my backups? Will I need to "re-zone" all my drives? Re-configure the Robot?
Any insight would help.
Thank you
Any insight would help.
Thank you
- Anonymous16 years ago2 quick space savers on a master /usr/openv filesystem
- Unified logging files
- Old Update Packs
1. Unified logs. Turn logging down to a minimal and purge them.
Read this forum post for all the best ways to reclaim space.
https://www-secure.symantec.com/connect/forums/usropenvlogs-media-server-65
2. /usr/openv/pack/
In here you might find saved backups of previous updates or maintenance packs
Generally, I delete everything in here except any references to Prior Update Versions
You can reclaim a big chunk of space. If you updated to 6.5.1 then 6.5.2 then 6.5.3 etc you can clean out those folders by now as not needed.
Or back them up prior to deleting.
Folders with names such as
./NB_CLT_6.5.3
./NB_6.5.3
./NB_JAV_6.5.3
These contain backups of binaries prior to updating to 6.5.3
So if you were on 6.5.4 you could delete them, but leave the
./NB_CLT_6.5.4
./NB_6.5.4
./NB_JAV_6.5.4
directories in case you ever uninstall 6.5.4 and revert to previous 6.5.3 for example
Or if /usr/openv/ on a volume in a volume/disk group ask them to add a new disk into the volume group and extend the file system if possible,