Please enter search query.
Search <book_title>...
NetBackup IT Analytics Data Collector Installation and Configuration Guide for Veritas NetBackup
Last Published:
2025-03-04
Product(s):
NetBackup IT Analytics (11.5)
- Introduction
- Configure a NetBackup IT Analytics Distributed Data Collector on a NetBackup Primary Server
- Configure Data Collector on non-clustered NetBackup 10.4 and later primary server
- Configure Data Collector on non-clustered NetBackup 10.1.1, 10.2, 10.2.01, 10.3 or 10.3.0.1 primary server
- Configure a Veritas NetBackup Data Collector Policy
- Configuring file analytics in NetBackup Data Collector policy
- Installing the Data Collector software
- Configure SSL
- Centralized Data Collector for NetBackup - Prerequisites, Installation, and Configuration
- Step-1: Choose operating system and complete prerequisites
- Step-5: SSH/WMI
- Upgrading Data Collector Locally
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Install and configure NetBackup IT Analytics Data Collector on MSCS environment
- Data Collector Policy Migration
- Pre-Installation setup for Veritas NetBackup appliance
- Pre-installation setup for Veritas Flex Appliance
- Data Collector Troubleshooting
- Host resources: Check host connectivity using standard SSH
- Host resources: Generating host resource configuration files
- Configuring parameters for SSH
- Appendix A. Configure Appliances
- Appendix B. Load historic events
- Load Veritas NetBackup events
- Appendix C. Firewall configuration: Default ports
- Appendix D. CRON Expressions for Policy and Report Schedules
- Appendix E. Maintenance Scenarios for Message Relay Server Certificate Generation
Host resources: Check the status of the WMI proxy server
Use the following
utility 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
or must have been run before running . Otherwise, 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
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"; };