Hi Team,
We have recently upgraded our Master and Media servers to 7.6.0.2. Now we are targeting Netbakcup clients upgrade to 7.6.0.4 using Live Updade currently running with 7.6.0.2.
As mentioned in Live update technote, /tmp should have 4.5 GB available but during testing I realized something different. Apart from /tmp file system, live update uses /usr/openv for extracting the files and consume up to approx. 4.6 GB .
I tested RedHat Linux 5.2 clients running with 7.1.0.2 and upgraded to 7.6.0.1 and then 7.6.0.4 and assuming below steps does follow.
Steps
1. Binaries files gets copied in /tmp folder first.
2. It extract some of files in /usr/openv/tmp and build exact package in /tmp to upgrade.
Combining /usr/openv/tmp/nblu_31259/VrtsNB_CLT_7.6.0.2.Linux.tar.gz-plit.1of2 /tmp/1418248919730/1418248953006/VrtsNB_CLT_7.6.0.2.Linux.tar.gz-split.2of2 into VrtsNB_CLT_7.6.0.2.Linux.tar.gz
3. Binaries get extracted in /usr/openv/netbackup/client/Linux/ and start upgrade locally from here.
4. After installation /usr/openv/tmp/nblu_31259/VrtsNB_CLT_7.6.0.2.Linux.tar.gz and /usr/openv/netbackup/client/Linux/ folder get deleted.
5. After installation, it stores 7.6.0.1 and 7.6.0.4 uninstall binaries in /usr/openv/pack .
Below are the breakup of space requirement for /usr/openv and /tmp folder
/ and /tmp/ size before 7.6.0.1 upgrade
-bash-4.1$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
16G 6.7G 8.4G 45% /
/dev/mapper/VolGroup00-LogVol03
7.9G 147M 7.4G 2% /tmp
/ and /tmp size grows up to
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
16G 7.7G 7.4G 51% /
dev/mapper/VolGroup00-LogVol03
7.9G 1.5G 6.1G 20% /tmp
/ and /tmp/ size after 7.6.0.1 upgrade
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
16G 7.5G 7.6G 50% /
dev/mapper/VolGroup00-LogVol03
7.9G 147M 7.4G 2% /tmp
With above calculation, /usr/openv requires 0.8 GB and /tmp/ requires 1.5 GB for 7.6.0.1 upgrade.
/ and /tmp/ size before 7.6.0.4 upgrade
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
16G 7.5G 7.6G 50% /
/dev/mapper/VolGroup00-LogVol03
7.9G 147M 7.4G 2% /tmp
/tmp consume up to 2.1 GB
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
16G 8.5G 6.6G 57% /
dev/mapper/VolGroup00-LogVol03
7.9G 2.3G 5.3G 31% /tmp
/ consume up to 3.5 GB
-bash-4.1$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
16G 12G 3.8G 75% /
/dev/mapper/VolGroup00-LogVol03
7.9G 1.9G 5.6G 26% /tmp
/ and /tmp size after upgrade
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
16G 9.2G 5.9G 62% /
/dev/mapper/VolGroup00-LogVol03
7.9G 147M 7.4G 2% /tmp
With above calculation, 7.6.0.1 --> 7.6.0.4, / consumes up to 4.5 GB and finish with 1.8 GB consumption. /tmp consumes up to 2.1 GB
To upgrdade 7.1.0.2 --> 7.6.0.1 --> 7.6.0.4, /usr/openv requires approx. 5 GB which is nowhere mentioned in technote, only /tmp requirement of 4.5 GB is mentioned. We have palenty of /tmp space on all the Linux machines. Precheck script doesn't check /usr/openv space requirement before upgrade. Our 2 tests machines went down during upgrade due to / filesystem got full which is a risk.
We will have to collect the / file system size for all the machines and upgrade only those clients which have alteast 5 GB available.
Please correct me if somewhere I am wrong. If above is true, it is really difficult to plan if all information is not present in Technote which is basis of planning.