Installation and necessary file information for NCVU_WIN, the VERITAS NetBackup (tm) Configurarion Validation Utility binary executable version 5.1.1 for Windows platforms.

Article:TECH38337  |  Created: 2008-01-08  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH38337
Article Type
Technical Solution


Environment

Issue



Installation and necessary file information for NCVU_WIN, the VERITAS NetBackup (tm) Configurarion Validation Utility binary executable version 5.1.1 for Windows platforms.

Solution



 NetBackup Configuration Validation Utility for Windows (NCVU_WIN) 5.1.1 README for the "Download" included at the bottom of this TechFile.

Contents:

1.  General information
2.  Supported NetBackup versions
3.  Supported platforms
4.  What is new
5.  Known NCVU_WIN issues.
6.  Installation information
7.  Operation information
   A.  Space requirements
   B.  Command help information
8.  Troubleshooting information
   A.  Installation troubleshooting
   B.  Operation troubleshooting
9.  Legal disclaimer
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1.  GENERAL INFORMATION:

"NCVU_WIN" is a VERITAS support utility written in the PERL programming language.  It is used to validate NetBackup and associated operating system configurations and functionality.  

The NCVU_WIN deliverable consists of two files, this NCVU_WIN.README file and the NCVU_WIN.exe file.  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

2. SUPPORTED NetBackup Versions

"NCVU_WIN" supports NetBackup versions:

3.4, 4.5, 5.0 and 5.1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

3. SUPPORTED PLATFORMS

"NCVU_WIN" is supported on the following platforms:

Windows NT
Windows 2000
Windows 2003
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

4.  WHAT IS NEW

   A.  Support for NetBackup version 5.1.

   B.  Changes to NCVU_WIN functionality.  Including:

       1.  Added support for CRYPT_CIPHER and CRYPT_KIND bpgetconfig entries.

       2.  Added NetBackup policy include list Shadow Copy Components validation.

       3.  Enhanced the NetBackup Catalog backup paths configuration checks to include checking for files that are included in the catalog backup paths.

       4.  Enhanced debug filenames to include a timestamp.  They are now created with the same format as output files.

       5.  Enhanced the command line validation to include checking for duplicate command line options.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

5.  KNOWN NCVU_WIN ISSUES
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

6.  INSTALLATION INFORMATION:

Place a copy of the NCVU_WIN.exe program in the  

<install path>

directory on each NetBackup node to be validated.  

 *************************************************************************
 * NOTE:  On NetBackup nodes prior to NetBackup release 4.5, the script  *
 * named support must be temporarily renamed, the support directory      *
 * created and the support script moved into the new support directory.  *
 * If any other administration scripts call the support script, the path *
 * should be updated accordingly.                                        *
 *************************************************************************

This version of NCVU_WIN takes approximately 4.2 megabytes of space to install.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

7.  OPERATION INFORMATION

   A.  SPACE REQUIREMENTS:

       There are many items that contribute to the size of files that NCVU_WIN creates per instance.  Each installation has a different number of configuration items to be validated.  This can include such items as the number of NetBackup nodes, patches installed, bp.conf and vm.conf entries, storage units configured, and classes configured.  As the number of configuration items increase, so does the amount of items reported in the NCVU_WIN output report.  

       Running NCVU_WIN in debug mode (especially debug level 8 and higher) can create sizable debug files.  This is primarily due to the listing of the output from the various system and NetBackup commands that NCVU_WIN parses through.  The number of hostnames contained in the NetBackup configuration and the various operating system hostname resolution systems also has a large impact on the size of the NCVU_WIN debug files.

       The number of observations and warnings messages generated by NCVU_WIN also has a large bearing on the size of NCVU_WIN output and debug files as well.

       Typical file sizes in bytes running on the master server with minimal warnings are:

       NCVU_master.out = 30-50K

       NCVU_media.out for a media server = 75K with approximately 30-50K for each additional media server.

       Each media server generates an .input and an .output communication file.

       <media server>.input = 1.4-2K
       <media server>.output = 30-50K

       NCVU_client.out = 45K with 30K for each additional client.

       Each client generates a .input and a .output communication file.

       <client>.input = @3K
       <client>.output = @30K

       The minimum amount of free space required to run a single instance of NCVU_WIN for master, media servers and clients can be estimated with the following formula:

        master server .out  
media server .out
number of additional media servers X 102K
client .out
             + number of clients X 63K
                     -------------------------------------------
total space required

Using the above example for a site with 3 media servers and 10 clients:

       NCVU_master.out                                  30,000
       NCVU_media.out 75,000
number of additional media servers X 102K      204,000
NCVU_client.out                                          45,000
number of additional clients X 63K       567,000
             ---------
total space required       921,000

       Typical level 9 debug file sizes in bytes running on the master server with minimal warnings are:

       NCVU_master.debug = 275K

       NCVU_media.debug = 275K with approximately @100K for each additional  
       media server.

       Each media server generates an .output communication file.

       <media server>.output = @100K

       NCVU_client.debug = @235K with @35K for each additional client.

       Each client generates an .output communication file.

       <client>.output = @85K

       The minimum amount of free space required to run a single instance of NCVU_WIN for master, media servers and clients with debug level 9 enabled can be determined with the following formula:

Using the above example for a site with 3 media servers and 10 clients:

        NCVU_master.out  
        NCVU_master.debug  
NCVU_media.out
NCVU_media.debug
number of additional media servers X 200K
client .out
client .debug
             + number of clients X 120K
                     -------------------------------------------
total space required

Using the above example for a site with 3 media servers and 10 clients:

NCVU_master.out  30,000
NCVU_master.debug       275,000
NCVU_media.out       75,000
NCVU_media.debug       275,000
number of additional media servers X 200K      400,000
NCVU_client.out                                        45,000
NCVU_client.debug                                  235,000
number of additional clients X 120K     1,080,000
             -------------------
total space required     2,415,000

       Since each installation is different, the end user should formulate the typical sizes for the various NCVU_WIN files if free space is a concern.

   B.  COMMAND HELP INFORMATION:

       To obtain information on how to run "NCVU_WIN" issue the following help command which will output general information about the utility.

# ./NCVU_WIN -help

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

8.  TROUBLESHOOTING INFORMATION

   A.  INSTALLATION TROUBLESHOOTING:

       Problems pertaining to the proper installation of NCVU_WIN can be caused by but not limited to:

       - Incorrect file ownership or execution permissions due to installation methods.
   
   B.  OPERATION TROUBLESHOOTING

       Problems pertaining to the proper operation of NCVU_WIN can be caused by but not limited to:

       1.  Incomplete deployment of NCVU_WIN utility components to all NetBackup nodes being tested.
       2.  Erratic behavior on command line commands and utilities not returning information to the NCVU_WIN program.  Use debug modes to output information to the debug file for verification.
       3.  Utility execution times greater then the wait timeout period.  This could be caused by commands or utilities that get hung or do not return information in a reasonable amount of time.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
9.  LEGAL DISCLAIMER

Copyright © 2005 VERITAS Software Corporation. All Rights Reserved. VERITAS, VERITAS SOFTWARE, the VERITAS logo, Business Without Interruption, VERITAS The Data Availability Company, NetBackup, NetBackup DataCenter, NetBackup BusinesServer and VERITAS Storage Migrator for Unix are trademarks or registered trademarks of VERITAS Software Corporation in the US and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

Attachments

NCVU_WIN_276338.5.1.1.zip (1.7 MBytes)


Legacy ID



276338


Article URL http://www.symantec.com/docs/TECH38337


Terms of use for this information are found in Legal Notices