Pre-Installation Setup for Veritas NetBackup > Centralized or Distributed Deployment (Veritas NetBackup)
  
Version 10.2.01P10
Centralized or Distributed Deployment (Veritas NetBackup)
Prior to Release Version 9, collection of NetBackup data was accomplished by installing data collector software on the NetBackup Master Server.
Starting with Release Version 9, two upgrade/installation options are available. Choose the one that best meets your needs.
Centralized NetBackup Data Collection (Recommended)
Distributed NetBackup Data Collection
Centralized NetBackup Data Collection (Recommended)
Use a centralized Data Collector to collect data from multiple NetBackup Master Servers, without any APTARE software installed on the Master Servers, as illustrated below.
Requirements for Centralized Data Collection
 
Minimum Requirements: 64-bit OS, 2 CPUs or vCPUs and 32 GiB RAM.
If there is a firewall between the NetBackup Master Servers and the Data Collector Server, ensure that bi-directional port communication is open on ports 1556 and 13724.
For a NetBackup Centralized Data Collector (Linux or Windows OS), the Data Collector needs access to the Admin commands (CLI). This typically requires the NetBackup Master Server or Media Server binaries to be installed on the Data Collector server. The CLI is available only with the Master or Media Server binaries. Note that the installation of these binaries may require you to acquire a NetBackup Master or Media Server license from Veritas.
For Veritas NetBackup 8.1, see Veritas NetBackup 8.1 Requirements for Centralized Collection.
The NetBackup software version on the Data Collector must match the major and minor version of the NetBackup software that is installed on the Master or Media Server that is being probed. When the Data Collector starts, it checks versions and halts collection for the Master Server where the mismatch is found. Refer to the Veritas documentation for more information about major and minor version requirements.
If you are currently running version 9.0 with centralized NetBackup data collection, and if the NetBackup software versions don’t match, when you upgrade to APTARE Release Version 10 (or higher) data collection will cease for the Master Servers with the incompatible versions.
For SLP collection, a WMI Proxy Server is required. See Required Software. WMI uses DCOM for networking. DCOM dynamically allocates port numbers for clients. DCOM’s service runs on port 135 (a static port) and any client communicating with a host connects on this port. The DCOM service allocates the specific port for the WMI service. To set up a fixed port for WMI, see http://msdn.microsoft.com/en-us/library/bb219447%28VS.85%29.aspx.
Note: If all NetBackup Masters configured in the collection policy are using the Linux operating system, then a WMI Proxy is not required.
Veritas NetBackup 8.1 Requirements for Centralized Collection
Veritas NetBackup 8.1 introduces a series of changes to the way a NetBackup host (such as the APTARE Data Collector) communicates with NetBackup Masters. These changes incorporate an enhanced secured channel for communication and more sophisticated host identity verification.
These changes require installation steps on the centralized Data Collector system that are not required for collection from NetBackup Master Servers prior to version 8.1.
Requirements for successful collection from a NetBackup 8.1 system:
As with all centralized NetBackup Data Collectors post NetBackup v7.7.3, the NetBackup software version on the Data Collector must match the major and minor version of the NetBackup software that is installed on the Master or Media Server that is being probed.
After installing the correct Veritas software, the Data Collector server needs to be added as a trusted server to all NetBackup Master Servers from which you want to collect data. This is typically accomplished using the netbackup command nbcertcmd. If the Data Collector is NOT registered as a trusted server, collection will not work.
A CA root certificate and a host ID-based security certificate must be installed on the Data Collector Server for each Master Server that will be accessed for data collection. Refer to the Veritas NetBackup Security and Encryption Guide, Version 8.1 for information on how to deploy CA and host ID-based certificates.
The Data Collector Server must be added as a NetBackup Media Server in both NBDB and registry/bp.conf files, on each NetBackup Master that will be accessed for data collection. Refer to the Managing Media Servers section of the Veritas NetBackup Administrators Guide, Volume 1.
The NetBackup media server software daemons on the Data Collector Server must be active.
 
Required Software
NetBackup 7.6 or earlier
Centralized Data Collector
Windows Data Collector
Linux Data Collector
Windows NetBackup Master
NetBackup Windows Remote Administration Console (RAC) installed on the Data Collector server.
NetBackup Master or Media Server software installed on the Data Collector server.
If SLP collection is required, a WMI Proxy Server must be set up on a Windows server.
Linux NetBackup Master
NetBackup Windows Remote Administration Console (RAC) installed on the Data Collector server.
NetBackup Master or Media Server software installed on the Data Collector server.
 
NetBackup 7.7 or later
Centralized Data Collector
Windows Data Collector
Linux Data Collector
Windows NetBackup Master
NetBackup Windows Remote Administration Console (RAC) is no longer available in NetBackup 7.7. You must therefore have NetBackup Master or Media Server software installed on the Data Collector server.
NetBackup Master or Media Server software installed on the Data Collector server.
If SLP collection is required, a WMI Proxy Server must be set up on a Windows server.
Linux NetBackup Master
NetBackup Windows Remote Administration Console (RAC) is no longer available in NetBackup 7.7. You must therefore have NetBackup Master or Media Server software installed on the Data Collector server.
NetBackup Master or Media Server software installed on the Data Collector server.
 
Overview of Centralized Data Collector Steps
The following list provides an overview of the steps to be taken. Details are provided later in this guide.
1. Identify a Data Collector server for the installation of the collection software, based on Requirements for Centralized Data Collection.
2. For a NetBackup Centralized Data Collector (Linux or Windows OS), that is collecting from NetBackup Masters running v7.7 or later, the NetBackup Master Server or Media Server binaries must be installed on the Data Collector. The Data Collector needs access to the CLI, which is only available with the Master or Media Server binaries. Note that the installation of these binaries may require you to acquire a NetBackup Master or Media Server license from Veritas.
3. Verify connectivity and correct configuration. See Verify Remote Commands for Centralized NetBackup Data Collection.
4. The Data Collector server needs to be added to the list of servers allowed to access the NetBackup Master Server from which you want to collect data. See Enable Access to the Veritas NetBackup Master Server.
5. In the Portal, add a host entry for the NetBackup Master Server and select the type as Veritas NetBackup Master Server. See Adding or Editing NetBackup Master Servers.
6. In the Portal, add a NetBackup Data Collector Policy to an existing Data Collector or create a New Data Collector and then add a NetBackup Data Collector Policy. See Pre-Installation Setup for Veritas NetBackup.
7. (If changing from Distributed to Centralized NetBackup collection)
Un-install the APTARE NetBackup Data Collectors from all NetBackup Master Servers.
8. On the Data Collector server, run checkinstall. See Validation Methods.
9. Start the Data Collector.
Verify Remote Commands for Centralized NetBackup Data Collection
The NetBackup centralized Data Collector executes a number of NetBackup commands remotely using the NetBackup Remote Administrator Console software. Many commands query NetBackup Master Servers that are listed in the collection policy and so the NetBackup Master needs to be configured to accept these requests from the Data Collector. Some collection probes query NetBackup Media Servers and some probe NetBackup clients; therefore, network connectivity and NetBackup permissions need to be configured to allow these commands to return the correct output.
The following commands should execute without error and with data returned before the Data Collector can probe the systems.
 
Master Servers
bpgetconfig -L -s [server name]
bppllist -M [server name]
nbdevquery -liststs -U -EMM [server name]
Every Master and Media Server
/usr/openv/volmgr/bin/vmoprcmd -h [server name] -devconfig
Every Client
bpgetconfig -L -s [client name]
 
 
Distributed NetBackup Data Collection
APTARE Data Collector software is installed on each NetBackup Master Server.
The following list provides an overview of the steps to be taken. Details are provided later in this guide.
1. Verify the Data Collector server minimum requirements.
Minimum Requirements: 64-bit OS, 2 CPUs or vCPUs and 16 GB RAM.
2. For upgrades, a distributed Data Collector (Release Version 9.x+) installed on a NetBackup Master Server will be automatically updated to APTARE Release Version 10.x. You do not need to re-install the Data Collector.
3. For new installations, in the Portal, add a host entry for each NetBackup Master Server and select the type as Veritas Master Server. See Adding or Editing NetBackup Master Servers.
4. In the Portal, for each NetBackup Master Server, create one of each of the following:
New Data Collector - For distributed collection there must be one Data Collector entry on the Portal for each NetBackup Master Server.
NetBackup Data Collector Policy for the New Data Collector. See Pre-Installation Setup for Veritas NetBackup.
5. For both upgrades and new installations, install the Data Collector software on each NetBackup Master Server. See Installing Data Collectors.
6. On each NetBackup Master Server, run checkinstall. See Validation Methods.
7. Start the Data Collector.