Difference between revisions of "Manage Hosts"
| Line 5: | Line 5: | ||
|} | |} | ||
| − | == | + | ===Introduction=== |
NetBackup uses security certificates to authenticate NetBackup hosts. The security certificates conform to the X.509 Public Key Infrastructure (PKI) standard. A master server acts as the Certificate Authority (CA) and issues digital certificates to hosts. | NetBackup uses security certificates to authenticate NetBackup hosts. The security certificates conform to the X.509 Public Key Infrastructure (PKI) standard. A master server acts as the Certificate Authority (CA) and issues digital certificates to hosts. | ||
| − | NetBackup 8.1 and later hosts can communicate with each other only in a | + | NetBackup 8.1 and later hosts can communicate with each other only in a secure mode. NetBackup 8.1 hosts and later must have a <b>Certificate Authority (CA) certificate</b> and a <b>host ID-based certificate</b> for successful communication. For more details please refer the NetBackup Security and Encryption guide. |
| − | |||
So for catalog migrations between NetBackup 8.1 and later , <b>CA Certificate</b> and <b>host ID certificates</b> need to be deployed to all the NBU hosts from the destination master server. | So for catalog migrations between NetBackup 8.1 and later , <b>CA Certificate</b> and <b>host ID certificates</b> need to be deployed to all the NBU hosts from the destination master server. | ||
| − | Tranzman has | + | Tranzman has an inbuild feature, <b>Host Management</b> to assist deploy the certificates. The entire process is fully automated and flexible. |
| − | |||
| − | |||
| + | ===<b>Host Management</b>=== | ||
| + | Host Management is primarily for NetBackup certificate management.It is available under <b>Actions</b>-><b>Host Management</b>. | ||
| + | Tranzman provides a centralised place to test the connectivity, push SERVERs to host properties, and to make hosts to request certificates from the Destination master. | ||
| − | + | Additionally, it provides options to - | |
| + | * Update Filesystem accelerator tracklogs | ||
| + | * Add/Remove the origin or destination from server’s Host properties | ||
| + | * Promote destination as master server | ||
| − | === | + | ===Host Management Operations=== |
| − | + | In order to fully automate the host management process, Tranzman provides different operations. | |
| − | + | These can be accessible under Host Management section and allows to - | |
| + | * Commit and execute the selected actions | ||
| + | * Reset the all pending actions | ||
| + | * Add a new host. | ||
| + | * Download the selected filter list of host management info | ||
| + | * Upload host lists, defining tags usefull for LARGE environments, and splits | ||
| + | * Move selected hosts to/from “not selected” tab. | ||
| + | * Adds additional SERVER entries (list of SERVERS) to all selected hosts when doing an “add destination as server” action. | ||
| + | * Add destination server token to be used when doing certificate deployment. | ||
| + | * Option to bypass previously completed restore operation. | ||
| + | * To view the Origin and Destination logs for the last commit | ||
| + | * To show/hide the TAG column and use TAGs | ||
| − | + | ===Host Management Actions=== | |
| − | + | Tranzman also provides ability to select specific actions to perform on the selected hosts. | |
| + | Actions are enabled if at least one host is selected. Some actions are available only for eligible Host. | ||
| + | For ex: Push Destination certificate is only available for servers on or above NBU 8.1 | ||
| + | Detailed info on each Actions are available below: | ||
| + | Performs connectivity tests from origin master <-> hosts | ||
| + | Adds destination master name (and any additional SERVERS added) as SERVER entry on selected servers | ||
| + | Updates the accelerator tracklogs to point to the new destination master name | ||
| + | Uses the ORIGIN master to tell the HOST to request certificate from DESTINATION | ||
| + | Performs connectivity test from destination master <-> hosts | ||
| + | Removes the origin SERVER entry from bp.conf/registry of selected servers | ||
| + | Update the bp.conf/registry of selected servers with destination master as first SERVER entry and EMMSERVER entry (for media server) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| + | ===Host Management status bar=== | ||
| + | The status bar provides information on the status of ports connectivity between the server and Origin/Destination master. | ||
| + | Helps to verify if the server has an active backup in the last 7 days, if the server is part of any available policy with accelerator enabled. It also provides the ability to view the Host properties of a server. | ||
| + | Shows the Backup software version running on the server. | ||
| − | + | The TICKS and CROSSES are all clickable to view the output of the commands that was executed. | |
| − | + | If the ORIGIN cannot connect to a server, it is expected the same for the DESTINATION and so the host can be moved to “NOT SELECTED” tab. | |
| + | If the ORIGIN can connect but the destination cannot connect, verify the LOOKUP entry is ticked as this will show whether Destination is able to resolve the server name. | ||
| + | If the Destination can resolve the name, make sure the ports are open by verifying the TICKS for one or more of pbx/vnetd/bpcd columns. | ||
| + | If the Destination can still not connect, verify the output of the Test BPCD by clicking on its X | ||
| + | If the output identifies a Certificate issue, and was trying to push a certificate, click on the HOSTNAME, this will show the history of actions run for the client, along with output from the Commands run at the HOST end. This will help to identify if there is an issue with the name resolution, firewalls, or routing. | ||
| + | The Status column provides a means to sort client by common errors, clicking on the status will list the status for the Origin, Destination and the Host along with description. | ||
| + | ===Managing Hosts with Alias=== | ||
| + | Tranzman identifies if hosts point to the same client based on the CLIENT_NAME in the host properties | ||
| + | Tranzman will group any such hosts together | ||
| + | If an Yellow ! rather than a TICK or CROSS is shown,it means that the hosts are returning DIFFERENT results for the same CLIENT_NAME | ||
| + | If this happens check the host management section in NetBackup, ensure all MAPPING REQUESTS are approved. It may sometimes require to manually add a host mapping in NetBackup to fix the alias errors. | ||
| − | === | + | ===Host Management Tags=== |
| − | + | Tags can be Shown / Hidden by clicking on the icon. | |
| − | |||
| + | Add a new TAG | ||
| + | If one or more hosts are selected then it allows to | ||
| + | Edit, to assign a tag to them | ||
| + | Delete, to remove a tag from them. | ||
| + | Once tags have been added, the servers can be sorted or filtered by Tag. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | ===Host Management process flow=== | ||
| + | <b>Host Management</b> should be performed 1 or 2 day after starting datatransfer. This will give sufficient time for Destination to discover the Origin clients. | ||
| − | + | * Click on <b>Actions->Host Management</b> while Tranzman is in the data transfer stage and all the NBU hosts are discovered and displayed on the <b>Host Management</b> Page under <b>Client Mangement</b>. | |
| − | <b> | + | e.g. Figure 1 shows all the NBU hosts including media servers. |
| + | [[File:HostManagement1.JPG | border|1100x800px]] | ||
| + | * Select all the eligible hosts and select <b> Actions -> Run origin connectivity test</b>. Confirm the Action by clicking on commit button. | ||
| − | + | * A <b>CheckConn</b> task is created and viewed from <b>Views</b>-><b>Activity Monitor</b>. Upon completion of this task, the respective columns on the Host Management page should get populated with | |
| − | <b> | + | [[File:GreenTick.JPG | 20x15px]] rather than [[File:RedTick.JPG | 20x20px]]. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | [[File:HostMgmtConnectivityTest.JPG | 1100x800px]] | ||
| + | * After successful connectivity test on origin, Tranzman will identify the media servers and move it to the <b>Media Server Management</b> tab and only clients are left in <b>Client Management</b>. | ||
| − | + | It is expected to return a tick on all columns for the corresponding clients. Refer Host Management status bar section to understand the column information. | |
| − | + | Based on the test results, the other actions can be performed. To understand more about <b>Host Management</b> actions, refer Host Management Operations and Host Management Actions | |
Revision as of 10:04, 21 July 2023
 |
Note: This section is Applicable to migrations which involves NetBackup versions 8.1 and later. |
Contents
Introduction
NetBackup uses security certificates to authenticate NetBackup hosts. The security certificates conform to the X.509 Public Key Infrastructure (PKI) standard. A master server acts as the Certificate Authority (CA) and issues digital certificates to hosts. NetBackup 8.1 and later hosts can communicate with each other only in a secure mode. NetBackup 8.1 hosts and later must have a Certificate Authority (CA) certificate and a host ID-based certificate for successful communication. For more details please refer the NetBackup Security and Encryption guide.
So for catalog migrations between NetBackup 8.1 and later , CA Certificate and host ID certificates need to be deployed to all the NBU hosts from the destination master server. Tranzman has an inbuild feature, Host Management to assist deploy the certificates. The entire process is fully automated and flexible.
Host Management
Host Management is primarily for NetBackup certificate management.It is available under Actions->Host Management. Tranzman provides a centralised place to test the connectivity, push SERVERs to host properties, and to make hosts to request certificates from the Destination master.
Additionally, it provides options to -
- Update Filesystem accelerator tracklogs
- Add/Remove the origin or destination from server’s Host properties
- Promote destination as master server
Host Management Operations
In order to fully automate the host management process, Tranzman provides different operations. These can be accessible under Host Management section and allows to -
- Commit and execute the selected actions
- Reset the all pending actions
- Add a new host.
- Download the selected filter list of host management info
- Upload host lists, defining tags usefull for LARGE environments, and splits
- Move selected hosts to/from “not selected” tab.
- Adds additional SERVER entries (list of SERVERS) to all selected hosts when doing an “add destination as server” action.
- Add destination server token to be used when doing certificate deployment.
- Option to bypass previously completed restore operation.
- To view the Origin and Destination logs for the last commit
- To show/hide the TAG column and use TAGs
Host Management Actions
Tranzman also provides ability to select specific actions to perform on the selected hosts. Actions are enabled if at least one host is selected. Some actions are available only for eligible Host. For ex: Push Destination certificate is only available for servers on or above NBU 8.1
Detailed info on each Actions are available below: Performs connectivity tests from origin master <-> hosts Adds destination master name (and any additional SERVERS added) as SERVER entry on selected servers Updates the accelerator tracklogs to point to the new destination master name Uses the ORIGIN master to tell the HOST to request certificate from DESTINATION Performs connectivity test from destination master <-> hosts Removes the origin SERVER entry from bp.conf/registry of selected servers Update the bp.conf/registry of selected servers with destination master as first SERVER entry and EMMSERVER entry (for media server)
Host Management status bar
The status bar provides information on the status of ports connectivity between the server and Origin/Destination master. Helps to verify if the server has an active backup in the last 7 days, if the server is part of any available policy with accelerator enabled. It also provides the ability to view the Host properties of a server. Shows the Backup software version running on the server.
The TICKS and CROSSES are all clickable to view the output of the commands that was executed. If the ORIGIN cannot connect to a server, it is expected the same for the DESTINATION and so the host can be moved to “NOT SELECTED” tab. If the ORIGIN can connect but the destination cannot connect, verify the LOOKUP entry is ticked as this will show whether Destination is able to resolve the server name. If the Destination can resolve the name, make sure the ports are open by verifying the TICKS for one or more of pbx/vnetd/bpcd columns. If the Destination can still not connect, verify the output of the Test BPCD by clicking on its X If the output identifies a Certificate issue, and was trying to push a certificate, click on the HOSTNAME, this will show the history of actions run for the client, along with output from the Commands run at the HOST end. This will help to identify if there is an issue with the name resolution, firewalls, or routing. The Status column provides a means to sort client by common errors, clicking on the status will list the status for the Origin, Destination and the Host along with description.
Managing Hosts with Alias
Tranzman identifies if hosts point to the same client based on the CLIENT_NAME in the host properties Tranzman will group any such hosts together If an Yellow ! rather than a TICK or CROSS is shown,it means that the hosts are returning DIFFERENT results for the same CLIENT_NAME If this happens check the host management section in NetBackup, ensure all MAPPING REQUESTS are approved. It may sometimes require to manually add a host mapping in NetBackup to fix the alias errors.
Host Management Tags
Tags can be Shown / Hidden by clicking on the icon.
Add a new TAG
If one or more hosts are selected then it allows to Edit, to assign a tag to them Delete, to remove a tag from them. Once tags have been added, the servers can be sorted or filtered by Tag.
Host Management process flow
Host Management should be performed 1 or 2 day after starting datatransfer. This will give sufficient time for Destination to discover the Origin clients.
- Click on Actions->Host Management while Tranzman is in the data transfer stage and all the NBU hosts are discovered and displayed on the Host Management Page under Client Mangement.
e.g. Figure 1 shows all the NBU hosts including media servers.
- Select all the eligible hosts and select Actions -> Run origin connectivity test. Confirm the Action by clicking on commit button.
- A CheckConn task is created and viewed from Views->Activity Monitor. Upon completion of this task, the respective columns on the Host Management page should get populated with
rather than 
.
- After successful connectivity test on origin, Tranzman will identify the media servers and move it to the Media Server Management tab and only clients are left in Client Management.
It is expected to return a tick on all columns for the corresponding clients. Refer Host Management status bar section to understand the column information.
Based on the test results, the other actions can be performed. To understand more about Host Management actions, refer Host Management Operations and Host Management Actions