DOCUMENTATION: Due to design changes in the Veritas NetBackup (tm) 6.0 Client Pack installer, the /usr/openv/pack/ directory may now consume a much higher amount of disk space on Master or Media Servers.

Article:TECH45476  |  Created: 2006-01-07  |  Updated: 2006-01-07  |  Article URL
Article Type
Technical Solution



DOCUMENTATION: Due to design changes in the Veritas NetBackup (tm) 6.0 Client Pack installer, the /usr/openv/pack/ directory may now consume a much higher amount of disk space on Master or Media Servers.


Manual:  Veritas NetBackup (tm) 6.0 Installation Guide for UNIX

Page: N/A

Modification Type:  Addition

In NetBackup 6.0, the UNIX Client packs now include all client install binaries.  This means that the size of the client pack will be comparable to that of the actual client install CD.

When initially installing NetBackup 6.0 on a Master or Media Server, some or all client install binaries may be chosen to be available for push install.  This copies those client (CLT) binaries to /usr/openv/netbackup/client.  When a CLT pack is later installed on a 6.0 Master or Media Server, the NB_CLT_60_x_M directory residing in /usr/openv/pack may be approximately 572MB or more in size, depending upon how many clients were selected during the initial NetBackup 6.0 installation.  This is due to the fact that the client pack installation creates the ability to rollback to a prior installed version by saving the "replaced" files in the /usr/openv/pack/NB_CLT_60_x_M directory.  

For example, if all client types were selected upon the initial installation of the Master or Media Server, the /usr/openv/pack directory could grow approximately 572MB in size each time a new CLT pack is installed on that NetBackup Master or Media Server.  If only 1 or 2 clients were selected upon initial NetBackup 6.0 installation, the /usr/openv/pack/NB_CLT_60_x_M directory created from a subsequent pack install will not be as large.

While this may not be an immediate concern as of 6.0 Maintenance Pack 1 (MP1), the number of CLT packs eventually installed could either reach or exceed the capacity of the disk partition that /usr/openv/pack exists on, if ample space is not available.  The /usr/openv/pack directory is in the same directory structure of which the NetBackup core is installed and operating in (by default).  If this file system reaches full capacity during normal backup operations, it can cause backup failures, possible image DB corruption (If disk space is exceeded on the Master Server), or other critical issues.

Note:  Since all client install binaries are included in NetBackup 6.0 Client pack installs, 1.5 - 2.0 GB of space combined may be needed for the installation process.  This includes the temporary space needed for the pack download and the space required to extract it.

Identify and address any space concerns by performing the following steps:
1.  List the contents of the /usr/openv/pack directory:

2. Note the "NB_CLT_60_x_M" pack directories listed.  Perform a du -ks command on a pack directory to determine how much disk space is consumed in kilobytes:  

Example:   du -ks /usr/openv/pack/NB_CLT_60_1_M

To free space on the volume, these "NB_CLT_60_x_M" directories can be moved to another volume or archived to tape or disk with NetBackup.  If it is not desired to maintain the ability to roll back to a previous pack, these "NB_CLT_60_x_M" directories may be removed.  Do not remove or archive the pack.history or pack.summary files, however.  These serve as a record for what packs have been installed on the system.

3. Going forward, the size of new NB_CLT_60_x_M pack directories can be reduced, depending upon the amount of client install binaries kept in the /usr/openv/netbackup/client directory.
The following is an example of a /usr/openv/netbackup/client directory with many client binaries.  This allows push installs to all of the following client types:

If push install support is not desired for some client types, their respective folders can be removed from /usr/openv/netbackup/client, allowing for future directories to be smaller when subsequent packs are applied.  This is because fewer files would be replaced when the pack is applied.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices