NetBackup IT Analytics Data Collector Notes and Troubleshooting

Last Published:
Product(s): NetBackup IT Analytics (11.0)
  1. Data Collector Troubleshooting
    1.  
      Verify the Data Collector configuration
    2.  
      Verify Connectivity
    3.  
      Configuring web proxy updates
    4.  
      Collecting missed events for Veritas Backup Exec
    5.  
      Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
    6.  
      Useful Data Collection scripts for capacity
    7.  
      Host resources troubleshooting
    8.  
      Host resources: Check the status of the WMI proxy server
    9.  
      Host resources: Post-Installation verification
    10. Host resources: Check host connectivity using standard SSH
      1.  
        Checking Paths for SSH
      2.  
        Environment setting for bash users
    11.  
      Host resources: Check host connectivity
    12.  
      Host resources: Check host connectivity using Host Resource Configuration file
    13. Host resources: Generating host resource configuration files
      1.  
        Sample lines in an input file
    14.  
      Host resources: Check the execution of a command on a remote server
    15.  
      Host resources Data Collection
    16.  
      Host resources: Collection in stand-alone mode
    17. Configuring parameters for SSH
      1.  
        Configure channelWaitTime
      2.  
        Configure singleChannelSession
      3.  
        Configure sudoWithPassword
    18.  
      Identifying Windows file system access errors (File Analytics)
    19.  
      Collect from remote shares (File Analytics)
    20.  
      Adding a certificate to the Java keystore
  2. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports
  3. CRON Expressions and Probe Schedules
    1.  
      CRON expressions and probe schedules
  4. Clustering Data Collectors with VCS and Veritas NetBackup (RHEL 7)
    1.  
      Clustering Data Collectors with VCS and Veritas NetBackup (RHEL 7)
    2.  
      Prerequisites
    3.  
      Getting started with Data Collector clustering
    4.  
      Main.cf
    5.  
      Upgrading a clustered Data Collector
  5. Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
    1.  
      Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
    2.  
      Prerequisites
    3.  
      Getting with Started with Data Collector Clustering
    4.  
      Main.cf
    5.  
      Upgrading a Clustered Data Collector
  6. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports
  7. Maintenance Scenarios for Message Relay Server Certificate Generation
    1.  
      Regenerate authentication certificate nearing expiry (or already expired)
    2.  
      Recover inadvertently deleted aptare.ks file
    3.  
      Authenticate new database with existing SSL certificates
    4.  
      SSL certificate authentication for a new data collector

Host resources: Check the status of the WMI proxy server

Use the following checkwmiproxyutility to verify that the WMI Proxy Server is up and running.

The WMI Proxy logs are written to:

C:\Program Files\Aptare\WMIProxyServer\logs\aptarewmiserver.log
Prerequisites

Either checkinstall or updateconfig must have been run before running checkwmiproxy. Otherwise, checkwmiproxy will not have access to the proxy server settings that are saved in the collector configuration file.

Usage
checkwmiproxy.[sh|bat] [wmiProxyServer wmiProxyPort remoteWinHost DomainOfUserId UserId Password "Command"]

Where:

wmiProxyServer is the name of the WMI Proxy Server

wmiProxyPort is the proxy's port (default is 1248)

Simple usage
checkwmiproxy.[sh|bat]

By default, this utility will look for the WMI Proxy Server details in the Host Resources Collector section of the collector configuration file. If it does not find a Host Resources Collector section, the checkwmiproxy will terminate with an error and a recommendation to pass explicit parameters, as shown in the usage statement above.

Example 1:
[root@aptaredev3 bin]# ./checkwmiproxy.sh
MetaDataChildThread.init(). Going to initialize.
Will try to connect to the APTARE WMI Proxy at 172.16.1.152:1248
APTARE WMI Proxy Version: APTAREWMIServer 6.5.01 06/25/07 21:00:00
Connection to APTARE WMI Proxy server successfully validated.
Example 2: Remote WMI queries

This utility also can be used to execute remote WMI queries, as shown in the following example.

[root@aptaredev3 bin]# ./checkwmiproxy.sh 172.16.1.152
Administrator password 172.16.1.152 "select * from Win32_OperatingSystem"
MetaDataChildThread.init(). Going to initialize.
Will try to connect to the APTARE WMI Proxy at 172.16.1.152:1248
   APTARE WMI Proxy Version: APTAREWMIServer 6.5.01 06/25/07 21:00:00
   Connection to APTARE WMI Proxy server successfully validated.
   
   APTAREWMIServer Response:
   instance of Win32_OperatingSystem
   {
        BootDevice = "\\Device\\HarddiskVolume1";
        BuildNumber = "3790";
        BuildType = "Multiprocessor Free";
        Caption = "Microsoft(R) Windows(R) Server 2003, Standard Edition";
        CodeSet = "1252";
        CountryCode = "1";
        CreationClassName = "Win32_OperatingSystem";
        CSCreationClassName = "Win32_ComputerSystem";
        CSDVersion = "Service Pack 1";
        CSName = "APTARESTGRPT1";
        CurrentTimeZone = -420;
        DataExecutionPrevention_32BitApplications = TRUE;
        DataExecutionPrevention_Available = TRUE;
        DataExecutionPrevention_Drivers = TRUE;
        DataExecutionPrevention_SupportPolicy = 2;
        Debug = FALSE;
        Description = "aptarestgrpt1";
        Distributed = FALSE;
        EncryptionLevel = 168;
        ForegroundApplicationBoost = 2;
        FreePhysicalMemory = "160264";
        FreeSpaceInPagingFiles = "1967860";
        FreeVirtualMemory = "2084508";
        InstallDate = "20070212110938.000000-480";
        LargeSystemCache = 1;
        LastBootUpTime = "20080507115419.343750-420";
        LocalDateTime = "20080520142117.484000-420";
        Locale = "0409";
        Manufacturer = "Microsoft Corporation";
        MaxNumberOfProcesses = 4294967295;
        MaxProcessMemorySize = "2097024";
        Name = "Microsoft Windows Server 2003 R2 Standard
Edition|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1";
        NumberOfLicensedUsers = 10;
        NumberOfProcesses = 90;
        NumberOfUsers = 8;
        Organization = "Aptare";
        OSLanguage = 1033;
        OSProductSuite = 272;
        OSType = 18;
        OtherTypeDescription = "R2";
        PAEEnabled = TRUE;
        Primary = TRUE;
        ProductType = 3;
        QuantumLength = 0;
        QuantumType = 0;
        RegisteredUser = "Aptare";
        SerialNumber = "69712-OEM-4418173-93136";
        ServicePackMajorVersion = 1;
        ServicePackMinorVersion = 0;
        SizeStoredInPagingFiles = "2039808";
        Status = "OK";
        SuiteMask = 272;
        SystemDevice = "\\Device\\HarddiskVolume1";
        SystemDirectory = "C:\\WINDOWS\\system32";
        SystemDrive = "C:";
        TotalVirtualMemorySize = "3256472";
        TotalVisibleMemorySize = "1363400";
        Version = "5.2.3790";
        WindowsDirectory = "C:\\WINDOWS";
};