This video covers the updated deployment topology for Linux-based environments, specifically allowing the search component to run on a dedicated worker node.
Learn the step-by-step process of extracting the installation package, modifying the configuration file for core and reporting components, and executing the installation on the manager node. The walkthrough also details retrieving initial login credentials and configuring the worker node to communicate with the manager node. Finally, see how to deploy and verify the search component on the separate worker node using both the command-line interface and the PowerProtect Data Manager UI.
Hello, I'm Idan from Dell Technologies, and in this demo I'll be showcasing a new capability in PowerProtect Data Manager 20.2, a new deployment topology for Linux based deployment mode. This enables to run the search component on a separate node. We'll start by logging into our manager node.
That's the node that runs a core component as well as reporting. I've already downloaded the installation package and now will extract it. As you can see, we have plenty of space in our directory /opt/ppdm. With that, let's create the installation configuration file using the PPDM admin configure create command. Now let's edit the config file to include only core and reporting components.
We'll save the file and kick off the installation using PPDM admin install. The installation can take a few minutes, so we'll fast forward through it. Great installation completely successfully. Let's verify all components are up and running by issuing PPDM admin status. As you can see both score and reporting are healthy. So we're good to go.
The first time password is based on the first eight characters of the machine ID, so let's retrieve that. Now let's head over to the PowerProtect Data Manager UI, which is available by navigating to Https and FQDN of the manager node. The initial password is change me at with a capital C, followed by the eight characters we copied earlier.
This password must be changed upon first login. For additional details, always refer to Protect Data Manager deployment guide. Great. As you can see, all components are healthy, including the reporting engine. Now, before we can install search on the dedicated worker node, we need to allow the worker node to communicate with manager node.
We'll go back to the manager node and ensure the admin allow list add command. With that done we're ready to deploy search on the worker node. Let's switch over. On the worker node. Installation package has already been downloaded and extracted and we have sufficient capacity in /opt/ppdm Let's create a configuration file using the PPDM admin configure create command this time including the manager node, FQDN and IP address.
Now let's edit and save the configuration file. We're ready to deploy the search component on the worker node. We'll do this using the PPDM admin install command with the search component parameter. Fantastic. The installation of the search component of the worker node completed successfully. Let's confirm using PDM admin status.
Now let's head back to the PowerProtect Data Manager UI where we can see that the search cluster is healthy. There you have it a new deployment topology for PowerProtect Data Manager Linux based deployments enabling search to run a dedicated worker node. Thanks for watching and see you in the next demo.
