Our netbackup group is unable to push out the new 7.7 version to my 150+ linux servers, running 7.1.4.
According to the netbackup folks here, you need at least 1G of free space in /tmp. None of my servers have that kind of free space in /tmp. All of our servers have plenty of space in /usr. That has been our methodology of building servers.
Is there any kind of workaround here to get netbackup upgraded ?
Hi
Setting NB_TMPDIR=/usr/openv/tmp is the trick you are looking fore
On Unix systems, when applying 7.5.0.x patches, if insufficient space exists in /tmp, the patch process will abort leaving a master or media server with only the client binaries installed.
Thanks for the answer.
Where and how is this variable set ?
This is a remote upgrade initiated by the master netbackup process (I'm not familiar with the admin part of this, I am only a user with 150+ servers running netbackup 7.1.4).
Does the admin have to set this or do I have to somehow do this on all of my servers ?
Yes - bring the tech note to the master server admin. Its a variable in the update_clients scripts he/she is running.
Version 7.1 is old by now and may not have the NB_TMPDIR variable.
In that case you can use this (unsupported) hack :
http://www.mass.dk/netbackup-quick-hints/alternate-file-location-using-install_client_files/
