Difference between revisions of "Manage Hosts"

From Tranzman Documentation
Jump to: navigation, search
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
 
+
__TOC__
−
{|style="padding: 5px; width: 85%;"
+
<br>
−
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:'''  This section is Applicable to migrations which involves NetBackup versions 8.1 and later.
 
−
|
 
−
|}
 
−
 
 
−
===Introduction===
 
−
 
 
−
NetBackup uses security certificates to authenticate NetBackup hosts. The security certificates conform to the X.509 Public Key Infrastructure (PKI) standard.
 
−
<br>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.
 
−
<br>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.<br>
 
−
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>.<br>
 
−
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.<br>
 
−
[[File:Hostmanagement_view.jpg | 700px]]
 
−
 
 
−
 
 
−
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.<br>
 
−
[[File:Hostmanagement_operations.jpg | 700px]]
 
−
 
 
−
These can be accessible under Host Management section and allows to -
 
−
* [[File:Hostmanagement_operations_commit.jpg | 15x15px ]] Commit and execute the selected actions
 
−
* [[File:Hostmanagement_operations_reset.jpg | 15x15px ]] Reset the all pending actions
 
−
* [[File:Hostmanagement_operations_hostadd.jpg | 15x15px ]] Add a new host.
 
−
* [[File:Hostmanagement_operations_download.jpg | 15x15px ]] Download the selected filter list of host management info
 
−
* [[File:Hostmanagement_operations_upload.jpg | 15x15px ]] Upload host lists, defining tags usefull for LARGE environments, and splits
 
−
* [[File:Hostmanagement_operations_notselected.jpg | 15x15px ]] Move selected hosts to/from <b>Not Selected</b> tab.
 
−
* [[File:Hostmanagement_operations_addserver.jpg | 15x15px ]] Adds additional SERVER entries (list of SERVERS) to all selected hosts when doing an <b>add destination as server</b> action.
 
−
* [[File:Hostmanagement_operations_token.jpg | 15x15px ]] Add destination server token to be used when doing certificate deployment. 
 
−
* [[File:Hostmanagement_operations_lightning.jpg | 15x15px ]] Option to bypass previously completed restore operation.
 
−
* [[File:Hostmanagement_operations_logs.jpg | 15x15px ]] To view the Origin and Destination logs for the last commit
 
−
* [[File:Hostmanagement_operations_tags.jpg | 15x15px ]] To show/hide the <b>Tag</b> column and use tags
 
−
 
 
−
===Host Management Actions===
 
−
Tranzman also provides ability to select specific actions to perform on the selected hosts.<br>
 
−
Actions are enabled if at least one host is selected. Some actions are available only for eligible Host.  <br>
 
−
For ex: Push Destination certificate is only available for servers on or above NBU 8.1
 
 
<br>
 
<br>
−
Detailed info on each Actions is available below:<br>
+
<div style="background-color:#edf7ff; padding: 1.5rem; border-radius:8px; max-width:80%; margin: 0 auto; margin-bottom:2rem;">
−
* Performs connectivity tests from origin master <-> hosts<br>
+
  <h1 style="border-bottom:none; font-size:2.5em; font-weight:bold; text-align:center;">Host Management</h1>
−
* Adds destination master name (and any additional SERVERS added) as SERVER entry on selected servers<br>
+
    <div style="background-color:#f8e2b3; padding:0.2rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); font-size:1em; margin: 0 auto;">
−
* Updates the accelerator tracklogs to point to the new Destination master name<br>
+
        <p>🛈 This section applies to migrations involving NetBackup versions 8.1 and later.</p>
−
* Uses the ORIGIN master to tell the HOST to request certificate from Destination<br>
+
    </div>
−
* Performs connectivity test from destination master <-> hosts.<br>
 
−
* Removes the origin SERVER entry from bp.conf/registry of selected servers. <br>
 
−
* Update the bp.conf/registry of selected servers with destination master as first SERVER entry and EMMSERVER entry (for media server)<br>
 
−
 
 
−
 
 
−
===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
+
    <p>NetBackup uses X.509 PKI certificates for host authentication. The master server acts as the Certificate Authority (CA) and issues digital certificates to hosts.<br>
−
If one or more hosts are selected then it allows to
+
    For catalog migrations, <b>CA Certificate</b> and <b>host ID certificates</b> must be deployed to all NetBackup hosts from the destination master server.<br>
−
Edit, to assign a tag to them
+
    Tranzman provides a fully automated and flexible <b>Host Management</b> feature to assist with certificate deployment and host configuration.
−
Delete, to remove a tag from them.
+
    </p>
−
Once tags have been added, the servers can be sorted or filtered by Tag.
+
</div>
  
 +
<div style="max-width:80%; margin: 0 auto;">
 +
  <div style="background-color:#fffbf4; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #ffe0b2; padding-bottom:0.5rem; font-size:1.5em;">Host Management Overview</h2>
 +
    <p style="font-size:1.1em;">
 +
      Host Management is available under <b>Actions &rarr; Host Management</b>.<br>
 +
      It provides a centralised interface to test connectivity, push SERVERs to host properties, and request certificates from the destination master.<br>
 +
      <div style="display:inline-block; box-shadow:5px 5px 10px grey;">[[File:Hostmanagement_view.jpg | 700px]]</div>
  
−
===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>.
+
      Additional options include updating Filesystem accelerator tracklogs, adding/removing origin or destination from host properties, and promoting destination as master server.</p>
−
e.g. Figure 1 shows all the NBU hosts including media servers.
+
  </div>
  
−
[[File:HostManagement1.JPG | border|1100x800px]]
+
  <div style="background-color:#fef3f7; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #f8bbd0; padding-bottom:0.5rem; font-size:1.5em;">Host Management Operations</h2>
 +
    <ul style="font-size:1.1em; margin-left:2em;">
 +
      <li>Commit and execute selected actions [[File:Hostmanagement_operations_commit.jpg | 15x15px ]]</li>
 +
      <li>Reset all pending actions [[File:Hostmanagement_operations_reset.jpg | 15x15px ]]</li>
 +
      <li>Add a new host [[File:Hostmanagement_operations_hostadd.jpg | 15x15px ]]</li>
 +
      <li>Download filtered host management info [[File:Hostmanagement_operations_download.jpg | 15x15px ]]</li>
 +
      <li>Upload host lists with tags for large environments/splits [[File:Hostmanagement_operations_upload.jpg | 15x15px ]]</li>
 +
      <li>Move selected hosts to/from <b>Not Selected</b> [[File:Hostmanagement_operations_notselected.jpg | 15x15px ]]</li>
 +
      <li>Add SERVER entries to selected hosts [[File:Hostmanagement_operations_addserver.jpg | 15x15px ]]</li>
 +
      <li>Add destination server token for certificate deployment [[File:Hostmanagement_operations_token.jpg | 15x15px ]]</li>
 +
      <li>Bypass completed restore operation [[File:Hostmanagement_operations_lightning.jpg | 15x15px ]]</li>
 +
      <li>View logs for last commit [[File:Hostmanagement_operations_logs.jpg | 15x15px ]]</li>
 +
      <li>Show/hide <b>Tag</b> column and use tags [[File:Hostmanagement_operations_tags.jpg | 15x15px ]]</li>
 +
    </ul>
 +
    <div style="display:inline-block; box-shadow:5px 5px 10px grey;">[[File:Hostmanagement_operations.jpg | 700px]]</div>
 +
  </div>
  
−
* Select all the eligible hosts and select <b> Actions -> Run origin connectivity test</b>. Confirm the Action by clicking on commit button.
+
  <div style="background-color:#eff8f0; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #c8e6c9; padding-bottom:0.5rem; font-size:1.5em;">Host Management Actions</h2>
 +
    <p style="font-size:1.1em;">
 +
      Actions are enabled when at least one host is selected. Some actions are available only for eligible hosts (e.g., Push Destination certificate for NBU 8.1+).<br>
 +
      <div style="display:inline-block; box-shadow:5px 5px 10px grey;">[[File:Hostmanagement_actions_view.jpg | 500x700px ]]</div></p>
 +
    <p> <b>Actions include:</b>
 +
    </p>
 +
    <ul style="font-size:1.1em; margin-left:2em;">
 +
      <li>Connectivity test from origin master to hosts [[File:Hostmanagement_actions_origintest.jpg|15x15px]]</li>
 +
      <li>Add destination master/server entries [[File:Hostmanagement_actions_add_destination.jpg|15x15px]]</li>
 +
      <li>Update accelerator tracklogs [[File:Hostmanagement_actions_update_accelerator.jpg|15x15px]]</li>
 +
      <li>Request certificate from destination [[File:Hostmanagement_actions_certificate.jpg|15x15px]]</li>
 +
      <li>Connectivity test from destination master to hosts [[File:Hostmanagement_actions_destintest.jpg|15x15px]]</li>
 +
      <li>Remove origin SERVER entry [[File:Hostmanagement_actions_remove.jpg|15x15px]]</li>
 +
      <li>Update bp.conf/registry with destination master/server [[File:Hostmanagement_actions_update.jpg|15x15px]]</li>
 +
    </ul>
 +
  </div>
  
−
* 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
+
  <div style="background-color:#fffbf4; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
−
[[File:GreenTick.JPG | 20x15px]] rather than [[File:RedTick.JPG | 20x20px]].
+
    <h2 style="border-bottom:2px solid #ffe0b2; padding-bottom:0.5rem; font-size:1.5em;">Status Bar & Host Properties</h2>
 +
    <p style="font-size:1.1em;">
 +
      The status bar shows port connectivity between server and origin/destination master, backup activity, policy accelerator status, and host properties.<br>
 +
      <div style="display:inline-block; box-shadow:5px 5px 10px grey;">[[File:Hostmanagement_status_bar.jpg |700px]]</div></p>
 +
      <p>
 +
      <b>Alias:</b> [[File:Hostmanagement_alias.jpg|15x15px]] icon shows Tranzman-detected aliases.<br></p>
 +
      <div style="display:inline-block; box-shadow:5px 5px 10px grey;">[[File:Hostmanagement_alias_status.jpg | 700px]]</div>
  
−
[[File:HostMgmtConnectivityTest.JPG | 1100x800px]]
+
      <p><b>Accelerator:</b></p>
 +
      <ul>
 +
        <li>[[File:Hostmanagement_cross.jpg|15x15px]] Not enabled</li>
 +
        <li>[[File:Hostmanagement_tick.jpg|15x15px]] Enabled</li>
 +
        <li>[[File:Hostmanagement_double_tick.jpg|15x15px]] Tracklog updated for destination</li>
 +
      </ul>
 +
      <p><b>Lookup:</b></p>
 +
      <ul>
 +
        <li>[[File:Hostmanagement_cross.jpg|15x15px]] Lookup failed</li>
 +
        <li>[[File:Hostmanagement_tick.jpg|15x15px]] Successful</li>
 +
        <li>[[File:Hostmanagement_exclamation.jpg|15x15px]] Multiple aliases found</li>
 +
      </ul>
 +
      <div style="display:inline-block; box-shadow:5px 5px 10px grey;">[[File:Hostmanagement_lookup_status.jpg|700px]]</div>
  
−
* 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>.
+
      <p><b>Port Connectivity:</b></p>
 +
      <ul>
 +
        <li>[[File:Hostmanagement_cross.jpg|15x15px]] Failed</li>
 +
        <li>[[File:Hostmanagement_tick.jpg|15x15px]] Successful</li>
 +
      </ul>
  
−
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.
+
      <p><b>Host History:</b></p>
 +
      <div style="display:inline-block; box-shadow:5px 5px 10px grey;">[[File:Hostmanagement_host_history.jpg|700px]]</div>
  
−
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
+
  </div>
  
 +
  <div style="background-color:#fef3f7; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #f8bbd0; padding-bottom:0.5rem; font-size:1.5em;">Tags & Grouping Hosts</h2>
 +
    <p style="font-size:1.1em;">
 +
      Tags help group hosts for easier management.<br>
 +
      <ul>
 +
        <li>Show/hide tags [[File:Hostmanagement_operations_tags.jpg | 15x15px ]]</li>
 +
        <li>Add tag [[File:Hostmanagement_operations_hostadd.jpg | 15x15px ]]</li>
 +
        <li>Edit tag [[File:Hostmanagement_tags_edit.jpg | 15x15px]]</li>
 +
        <li>Delete tag [[File:Hostmanagement_tags_delete.jpg | 15x15px]]</li>
 +
      </ul>
  
 +
      </p><p>Servers can be sorted or filtered by tag.</p>
 +
      <p>Refer to [[File:Tutorials]] for a demonstration.</p>
 +
  </div>
  
 +
  <div style="background-color:#eff8f0; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); margin-bottom:2rem;">
 +
    <h2 style="border-bottom:2px solid #c8e6c9; padding-bottom:0.5rem; font-size:1.5em;">Process Flow</h2>
 +
    <ol style="font-size:1.1em; margin-left:2em;">
 +
      <li>Perform Host Management 1-2 days after starting data transfer.</li>
 +
      <li>Go to <b>Actions &rarr; Host Management</b> when all NBU hosts are discovered.</li>
 +
      <li>Select eligible hosts and run <b>origin connectivity test</b> [[File:Hostmanagement_actions_origintest.jpg|15x15px]]. Confirm with [[File:Tranzman_commit_button.jpg|100x20px]].</li>
 +
      <li>Check results in <b>Views &rarr; Activity Monitor</b>. Columns should show [[File:Hostmanagement_tick.jpg|15x15px]].</li>
 +
      <li>Media servers move to <b>Media Server Management</b>; clients remain in <b>Client Management</b>.</li>
 +
      <li>All columns should show [[File:Hostmanagement_tick.jpg|15x15px]]. Refer to status bar for details.</li>
 +
      <li>Perform further actions as needed. See <b>Host Management Actions</b> for details.</li>
 +
    </ol>
 +
  </div>
 +
</div>
  
−
{| class="wikitable"  style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;"
+
<div style="display:flex; justify-content:space-between; margin-top:2rem; padding:1rem; background-color:#ffffff; max-width:90%; margin: 2rem auto 0;">
−
|-
+
  <div style="text-align:left;">
−
| [[Image:prev_icon.jpg|30px|link=Transition_Readiness]]
+
    [[Image:prev_icon.jpg|30px|link=Monitoring]] [[Monitoring|Previous]]
−
|| [[Image:next_icon.jpg|30px|link=Manage_Hosts]]
+
  </div>
−
|}
+
  <div style="text-align:right;">
 +
    [[Image:next_icon.jpg|30px|link=Reporting_and_Logging]] [[Reporting_and_Logging|Next]]
 +
  </div>
 +
</div>

Latest revision as of 07:04, 12 September 2025



Host Management

🛈 This section applies to migrations involving NetBackup versions 8.1 and later.


NetBackup uses X.509 PKI certificates for host authentication. The master server acts as the Certificate Authority (CA) and issues digital certificates to hosts.
For catalog migrations, CA Certificate and host ID certificates must be deployed to all NetBackup hosts from the destination master server.
Tranzman provides a fully automated and flexible Host Management feature to assist with certificate deployment and host configuration.

Host Management Overview

Host Management is available under Actions → Host Management.
It provides a centralised interface to test connectivity, push SERVERs to host properties, and request certificates from the destination master.

Hostmanagement view.jpg


Additional options include updating Filesystem accelerator tracklogs, adding/removing origin or destination from host properties, and promoting destination as master server.

Host Management Operations

  • Commit and execute selected actions Hostmanagement operations commit.jpg
  • Reset all pending actions Hostmanagement operations reset.jpg
  • Add a new host Hostmanagement operations hostadd.jpg
  • Download filtered host management info Hostmanagement operations download.jpg
  • Upload host lists with tags for large environments/splits Hostmanagement operations upload.jpg
  • Move selected hosts to/from Not Selected Hostmanagement operations notselected.jpg
  • Add SERVER entries to selected hosts Hostmanagement operations addserver.jpg
  • Add destination server token for certificate deployment Hostmanagement operations token.jpg
  • Bypass completed restore operation Hostmanagement operations lightning.jpg
  • View logs for last commit Hostmanagement operations logs.jpg
  • Show/hide Tag column and use tags Hostmanagement operations tags.jpg
Hostmanagement operations.jpg

Host Management Actions

Actions are enabled when at least one host is selected. Some actions are available only for eligible hosts (e.g., Push Destination certificate for NBU 8.1+).

Hostmanagement actions view.jpg

Actions include:

  • Connectivity test from origin master to hosts Hostmanagement actions origintest.jpg
  • Add destination master/server entries Hostmanagement actions add destination.jpg
  • Update accelerator tracklogs Hostmanagement actions update accelerator.jpg
  • Request certificate from destination Hostmanagement actions certificate.jpg
  • Connectivity test from destination master to hosts Hostmanagement actions destintest.jpg
  • Remove origin SERVER entry Hostmanagement actions remove.jpg
  • Update bp.conf/registry with destination master/server Hostmanagement actions update.jpg

Status Bar & Host Properties

The status bar shows port connectivity between server and origin/destination master, backup activity, policy accelerator status, and host properties.

Hostmanagement status bar.jpg

Alias: Hostmanagement alias.jpg icon shows Tranzman-detected aliases.

Hostmanagement alias status.jpg

Accelerator:

  • Hostmanagement cross.jpg Not enabled
  • Hostmanagement tick.jpg Enabled
  • Hostmanagement double tick.jpg Tracklog updated for destination

Lookup:

  • Hostmanagement cross.jpg Lookup failed
  • Hostmanagement tick.jpg Successful
  • Hostmanagement exclamation.jpg Multiple aliases found
Hostmanagement lookup status.jpg

Port Connectivity:

  • Hostmanagement cross.jpg Failed
  • Hostmanagement tick.jpg Successful

Host History:

Hostmanagement host history.jpg

Tags & Grouping Hosts

Tags help group hosts for easier management.

  • Show/hide tags Hostmanagement operations tags.jpg
  • Add tag Hostmanagement operations hostadd.jpg
  • Edit tag Hostmanagement tags edit.jpg
  • Delete tag Hostmanagement tags delete.jpg

Servers can be sorted or filtered by tag.

Refer to File:Tutorials for a demonstration.

Process Flow

  1. Perform Host Management 1-2 days after starting data transfer.
  2. Go to Actions → Host Management when all NBU hosts are discovered.
  3. Select eligible hosts and run origin connectivity test Hostmanagement actions origintest.jpg. Confirm with Tranzman commit button.jpg.
  4. Check results in Views → Activity Monitor. Columns should show Hostmanagement tick.jpg.
  5. Media servers move to Media Server Management; clients remain in Client Management.
  6. All columns should show Hostmanagement tick.jpg. Refer to status bar for details.
  7. Perform further actions as needed. See Host Management Actions for details.
   Prev icon.jpg Previous

   Next icon.jpg Next
Retrieved from "https://docs.stoneram.com/index.php?title=Manage_Hosts&oldid=3481"