The following instructions assume you have a dedicated virtual machine host and are not deploying on your personal computer, which is used only to deploy DPX on the host.

Deploying DPX Master Server with vSphere

1. Download the OVA file from the Catalogic MySupport page:

   1. Login to Catalogic MySupport using the provided credentials.

   2. From the product list, select DPX 4.10.

   3. Click DPX Server and Clients under Software.
   4. Click the link to start downloading the .OVA file.
2. Once the file is downloaded, log in to vSphere.

3. Right-click on the folder where you want to deploy your virtual machine.

4. Deploy OVF Template wizard will initiate.

Deploy OVF Template wizard consists of the following steps:

1. Select an OVF template In this step, provide the .OVA file destination, either as a URL to a remote server or by downloading the file. In our scenario, we’ve downloaded the file. In such case, select “Local file” and browse to the file location. Click Next.

2. Select a name and folder Specify the name for your virtual machine and its location. Please remember machine names on vCenter must be unique. Click Next.

3. Select a compute resource Select the computer resource that will be available to your virtual machine. Click Next.

4. Review details Verify the template details. Click Next.

5. License agreements In this step, you must accept the license agreements. Check the checkbox and click Next.

6. Select storage Define where the virtual machine’s disk will be stored, and choose between thin and thick provisioning. This setting determines whether all disk storage defined for the machine will be exclusively available (thick), or only the disk space actually occupied is used (thin). Click Next.

7. Select networks Select the network for your virtual machine. Click Next.

8. Customize template Here you are required to fill in some parameters.

   Hostname Configuration

   Hostname

   Please remember that hostname must be unique within the network, domain and Enterprise.

   Connection Configuration

   Provide all parameters for static IP address. Leave all blank in case of DHCP.

   Network IP Address

   Fill in, if you want to have a static IP address.

   Network Prefix

   If you want to have a static IP address, you must provide all connection parameters, including network prefix.

   Default Gateway

   The default gateway address for this VM.

   DNS Servers

   Comma-separated domain name servers for this VM.

   Keyboard Language Configuration

   Keboard Language

   Type in two-characer language code.

   Timezone Configuration

   Set to “America/New_York” by default. Can be changed afterwards.

   Click Next.

9. Ready to complete This screen contains a summary of the previous steps. Please review all the information before you click Finish.

You have now completed the deployment of DPX.

General overview

Catalogic DPX delivers unprecedented speed and savings with a single unified data protection solution making backup and disaster recovery smarter, faster, and more efficient. It is uniquely designed to handle the most common data protection use cases that are challenging for IT departments.

You can deploy Catalogic DPX quickly and it scales easily to match the needs of rapidly growing cloud infrastructures. Additionally, the software exploits modern server virtualization and is optimized for the backup and recovery of virtual systems.

Catalogic DPX Block Data Protection provides rapid and efficient backup, restore, Bare Metal Recovery, application protection and tape archiving. A complex backup environment can have multiple backup Enterprises, each with more than one secondary system, including NetApp storage and Catalogic DPX Open Storage.

Environment structure

A basic DPX environment consists of a DPX Master Server, a DPX Client and a storage device.

The master server is typically deployed on a virtual machine. It manages data transfer between the machines from which data are backed up, and the devices where backed up data are stored and where they are restored from.

The DPX Client is an agent deployed on the machine (either physical or virtual) containing data you are backing up. It allows the DPX Master Server to access the data on the machine to create backups and restore data.

There is also a method to back up virtual machines under a hypervisor without backup agents on the virtual machines. This backup method is called agentless.

Each machine, whether physical or virtual, is referred to as a node. The master server is a DPX node that contains DPX software, including the Catalog and modules that control scheduling, media management, and distributed processing. There is one master server per data protection Enterprise. Any machine the master server communicates with must be added to the Enterprise as a node. Nodes where DPX Client is installed are called client nodes. The master is also visible as a node and thus can back up data from itself.

User interfaces

The Catalogic DPX environment features two graphical user interfaces for managing backup and restore activities called jobs. One interface is a Java-based desktop application. To run it, you need to install the Java environment first. The other interface is an HTML5-based web application that does not require additional installation apart from a supported web browser.

The desktop interface provides access to most DPX features but is gradually replaced with the new web interface and will be deprecated in the future.

The web interface only requires a web browser to run. This interface covers most typical DPX functionalities and is continuously developed to finally replace the old desktop application.

Important considerations

Some features described in this guide are optional and separately licensable. For inquiries regarding licensing of optional features, contact your data protection account representative.

Catalogic DPX data protection software does not currently support Unicode for DPX-specific objects such as jobname, devicepath, qtree name, etc. Use the English character set only.

Currently, Catalogic DPX offers access either through the web (HTML5-based) interface from your browser or through the desktop (Java-based) application requiring a Java environment installed on the machine you are accessing the Catalogic DPX from. The desktop application is older and will be soon deprecated. The web interface is continuously developed and currently supports all typical Catalogic DPX functionalities, as well as some new features that will never be available using the desktop interface.

You may log in to the DPX Master Server through either of the user interfaces, as described below.

Launching the Catalogic DPX Master Server web interface

To launch the Catalogic DPX Master Server web interface, do the following:

1. Open a web browser on a machine with access to the same network the Master Server has been deployed in.

2. Type the Master Server IP address into the web browser’s address bar and press Enter.

1. In the login screen, enter the username and password for the Catalogic DPX Master Server. The default login credentials are:

1. Click the Login button. The DPX Master Server Dashboard will appear.

2. When logging in for the first time, you will be prompted to change the password. Your new password must:

   • contain from 6 to 48 characters,

   • contain at least 1 number and 1 letter,

   • not contain your username or the keyword admin.

   After changing the password, you won’t need to log in again; you will be taken to the DPX dashboard.

Launching the Catalogic DPX Master Server desktop interface

To launch the Catalogic DPX Master Server desktop interface, you need to have a Java environment installed on your machine. We recommend downloading the OpenWebStart framework to open the .jnlp file (see below).

1. If you are launching the desktop interface for the first time, select Run the DPX Java User Interface. This will start the download of the dpx.jnlp file which is used to launch the desktop interface app. If you already have the file downloaded, proceed to step 2.

1. Run the dpx.jnlp file. It is an executable file, so for security reasons, you may be prompted whether you still want to launch it. Select OK.

1. In the Connect to DPX window, enter the server name or IP address (you can also select it from the list, if you have logged into the server in the past), then provide the username and password for the Catalogic DPX Master Server.

   The default login credentials are:

   login

   sysadmin

   password

   sysadmin

2. Click the Login button. The DPX desktop dashboard will appear.

You can deploy the Catalogic DPX Master Server virtual appliance in the Microsoft Hyper-V environment.

Take the following steps to deploy the Catalogic DPX Master Server for Microsoft Hyper-V:

1. From your workstation, open a web browser and log in to the Catalogic website.

2. Go to the product page for DPX v.4.10 and see the section DPX Master Server appliance template. Download the Microsoft Hyper-V template file.

3. Log in to Microsoft Windows Server Hyper-V to deploy the Catalogic DPX Master Server virtual appliance. Copy the .ISO file to the system.

1. Verify the file integrity of the .ISO file by comparing the MD5 checksum values. Open either Microsoft PowerShell or Microsoft Windows PowerShell. You can use a command similar to the following example:

   Copy

   PS> Get-FileHash -Algorithm MD5 `
   -Path C:\Users\hyperv\Desktop\DPX-4.10-hyperv-installer.iso

   Compare this value with the original MD5 checksum value in the product page.

2. In Microsoft File Explorer, open the folder to which you downloaded the .ISO image file.

3. Right-click the .ISO image file and click Mount.

4. Open the disk image drive DPX, and open DPX-setup.exe as Administrator to open the DPX 4.10 Setup Wizard window. Click Next to proceed.

5. Read the Software License Agreement. If you accept this agreement, select I accept the agreement and click Next.

6. Ensure that the product directory is set to the default path: C:\Program Files\DPX\. Or select another empty folder to install the product.

7. Select one of the Virtual Switches in the list and click Next.

8. Configure the network settings of the virtual appliance.

   Field

   Description

   Example

   Click Next to proceed.

9. Specify the keyboard layout and time zone (TZ) of the Linux operating system for the Catalogic DPX Master Server.

   In the Keyboard Language field, enter either one of the available keyboard layouts for the Catalogic DPX Master Server: us for US English, uk for UK English, de for German, fr for French, pl for Polish, or cn for Chinese. Or leave the default value us.

   Enter the time zone (TZ) variable for the system. The default value is America/New_York for the US Eastern Time. You can use either one of the TZ values that are listed on the WorldTimeAPI website: .

   Click Next to proceed.

10. In the Ready to Install page, click Next to start installing the Catalogic DPX Master Server programs for Microsoft Windows.

Open Microsoft Hyper-V Manager. Ensure you can see the new VM for the Catalogic DPX Master Server virtual appliance.

The DPX Master Server is deployed as an Open Virtualization Format (OVF) template in a VMware environment. The recommended method for installing DPX Client and OSS is to download an .ISO file from the customer service website, mount the .ISO at a shared network location, open the .ISO file, and launch the appropriate installer. If an .ISO image is not suitable for you, request physical DVDs from the Catalogic Software Data Protection Technical Support.

Requirements

You can deploy the Catalogic DPX Master Server virtual appliance on either VMware or Microsoft Hyper-V by using the template file (.OVA or .ISO, respectively). The default deployment template will include the following configuration:

Deployment

DPX Master Server can be deployed either using VMware’s vSphere, or Microsoft’s Hyper-V solutions:

This Guide is for Catalogic DPX version 4.10.

For other Catalogic Software products, see:

• vStor 4.10 Documentation

• GuardMode 2024.1 Documentation

Or go back to the Catalogic Software Documentation Portal.

This Basic Configuration section will help you get started with setting up your DPX environment, understanding its key components, and configuring backup and restore operations.

Catalogic DPX Suite Components

1. Data Protection Management: DPX Master Server The central control unit for managing and monitoring all backup and restore operations. Typically, the DPX Master Server is deployed from an .OVA as a dedicated virtual machine.

2. Backup Agents/Connectors:

   1. DPX Client Agent software installed on the systems that are being backed up. DPX Client executes backup and restore tasks on the client machine.

   2. Hyper-V Agent Agent software installed on Hyper-V hypervisor to communicate with VMs during backup and restore tasks. With Hyper-V Agent, there is no need to install DPX Client software on individual Hyper-V machines.

   3. DPX Proxy Server A dedicated intermediary for backup and restore operations in VMware environments. The DPX Proxy Server helps in offloading tasks from the Master Server and optimizing data flow between backup sources and storage devices.

3. Storage: vStor vStor is a virtual storage appliance consolidating backup data into a scalable, efficient storage solution. vStor is smoothly integrated with the Catalogic DPX environment. It supports deduplication, compression and encryption, optimizing storage usage and data security. (other non-Catalogic storage solutions compatible with DPX are possible, such as tape libraries, DiskDirectory, cloud storage or NetApp)

4. Security: GuardMode Provides early detection of possible ransomware events and data anomalies to protect backups from being compromised. It monitors file systems on backup clients, identifying potential threats and alerting administrators to ensure the integrity of backup data, employing strategies such as blocklist monitoring, honeypot files, and threshold monitoring to detect and mitigate possible ransomware activities.

Backup Types and Requirements

File/NDMP/Image Backup

• DPX Master Server

• DPX Client on source machine

• Storage device (tape library or DiskDirectory)

Block Backup

• DPX Master Server

• DPX Client on source machine

• Storage device (vStor or NetApp)

Application Backup

• DPX Master Server

• DPX Client on source machine (DPX Client automatically detects supported applications)

• Storage device (tape library, Disk Directory, vStor or NetApp)

VMware Backup

• DPX Master Server

• VMware hypervisor (Agent installation not required)

• DPX Proxy Server

• Storage device (vStor or NetApp)

Hyper-V Backup

• DPX Master Server

• Microsoft Hyper-V Agent installed on the hypervisor

• Storage device (vStor or NetApp)

Other Requirements

Firewall Settings

Ensure ports required by DPX are open:

• 6123 on DPX Master Server, DPX Client, DPX Proxy Server for communication

• 9101 on DPX Master Server for autoupdates

• 9104, 9202 on DPX Client for autoupdates

Network Configuration

• Stable network connectivity between all components

• DNS resolution for all servers and clients (recommended)

Storage Configuration

• Sufficient storage space for backups

• Properly configured storage devices and pools

The Catalogic DPX Client is a component of the Catalogic DPX data protection solution. DPX Clients are installed on systems that need to be backed up. They allow users to define and run backup, copy, and restore jobs for these systems. DPX Client installed on destination machines also provides features for controlling tape devices, managing reports and logs, and performing maintenance tasks on the Catalog.

You can install the DPX Client on Microsoft Windows and Linux machines. There are separate releases of the DPX Client application for Windows and Linux operating systems. Before installing, make sure all necessary software and hardware requirements are met.

For details concerning the installation procedures for a specific operation system, see the appropriate sections below.

To uninstall the Catalogic DPX Client from your Microsoft Windows system, click Start in the taskbar, locate the program group for Catalogic DPX, click Uninstall, and follow the instructions in the subsequent dialog boxes.

Your DPX is ready to use the moment you log in to it for the first time. However, there are two things worth configuring, namely your password (if you haven’t changed it already) and e-mail settings.

To install the DPX Client for Windows, follow these steps:

1. Go to the Catalogic website and log in.

2. Navigate to the product page and go to Software Download > New installations or deployments > Client Software Installation.

3. Download the installation program (full or client-only) of the DPX Client for Windows.

4. Copy the installation program to the Windows system you want to protect.

5. Close all programs and ensure that the Windows Installer service is active.

6. Right-click the installation program and select Run as administrator.

7. Follow the instructions in the installation dialog window, including accepting the Software License Agreement.

8. If you are using the full version installer, you can select and install additional components, such as the Virtualization Proxy Server application or OSS Server.

9. In the Add Node to Enterprise page, select Yes, add this node to the Enterprise checkbox to register this client node to the Enterprise and thus make it visible for the DPX Master Server. If you are installing on a cluster node, note that each cluster requires a dedicated node group. Add a cluster node to its dedicated node group. Add only cluster nodes to a cluster node group. If you do not want to add the node to the Enterprise, clear the checked option. You can always add the node later from the Master Server interface. See .

   Leave the Logical Node Name which is the computer name of this Microsoft Windows system by default. Or, you can rename the logical node name in the input field.

   Leave the Node Group Name field DefaultGroup which is the default node group. Or enter a different node group name either to create a new node group in the Enterprise or to specify an existing node group with the same name. Click Next to proceed.

10. On the Master Server page, enter the Master Server Hostname. This is the resolvable name of the master server. Optionally, you can enter the Master Server IP address. Click Next.

1. Click Install to start the installation.

2. (Optional) If you are installing on a SharePoint node, a message alerts you to later complete the configuration of the SharePoint node by using the Configure function of the management console.

3. (Optional) If you are installing the DPX Client on a cluster node, the Cluster Setup dialog appears. A cluster dry run should be executed to run a test of the cluster configuration. Enter a Virtual Cluster IP and the appropriate Subnet IP. Cluster Dry Run. Enter the required information to define the cluster node.

   • Domain Administrator. Populate all information for the cluster domain administrator.

   • Cluster Name. Enter a unique name, up to 15 characters, for the virtual resource. This is the DNS name of the virtual node. This name must not be the Windows cluster name that appears under the field.

   • Physical Node IP. Select the IP address for the node.

   • Virtual Node IP. Enter the IP address for the virtual resource. This must be an available public network address different from the cluster IP address. When you install on other nodes in the cluster, supply this same IP for each node. This IP cannot be the Windows cluster IP or IP used by any other cluster service.

   • Subnet mask. Enter the subnet mask for the virtual resource. This field is enabled only for the final cluster node.

   • Cluster Network. Select the local network name to use. This field is enabled only for the final cluster node. Click Next.

4. In the Ready to Install Program dialog, click Install to start installing the DPX Client for Microsoft Windows. You may be warned that you do not have enough disk space to successfully install the software.

5. After the installation completes, the Completion dialog appears. Select the Read additional requirements and install summary check box. This instructs InstallShield to display a summary of the file instNote.txt, which can be found in the logs directory. This file and the summary contain important information about your installation, including any non-fatal errors during installation. Leave it checked and click Finish.

6. The file instNote.txt appears, along with a prompt to reboot the machine. Click Yes to restart Microsoft Windows immediately or No to restart later.

Prerequisites

For the installation of the DPX Client application, the minimum recommended version of Windows is Microsoft Windows 2012 R2. For details, see the DPX 4.10 .

The minimum hardware requirements are as follows:

Before installing the DPX Client for Microsoft Windows, review the following prerequisites:

• The “Windows Installer” service must be available. Go to the Start menu, search for the application called “Services” and open it. Ensure that “Windows Installer” is available on the list of local services and that the status of this service is either “Manual” or “Automatic”.

• Allow all required ports for the Catalogic DPX Client:

  • TCP: 3260, 6123, 6124, 9104, 9202, 10000, 10001, 10566, and 15660

  • UDP: 6123 and 6124.

Install the DPX Client on your client machines and register these client nodes with the DPX Master Server so that DPX will be able to protect data in these client nodes. Refer to this section to install the DPX Client on either one of the following UNIX and UNIX-like systems:

• Linux

• Novell (Micro Focus) Open Enterprise Server (OES)

• IBM AIX

For Microsoft Windows, see DPX Client for Microsoft Windows.

To install the DPX Client for Linux, follow these steps:

1. Go to the Catalogic MySupport website and log in.

2. Navigate to the product page and go to Software Download > New Installations or deployments > Client Software Installation.

3. Download the Linux ISO file to your workstation.

4. Copy the ISO image file to the client system, say, the home directory (~).

5. Verify the MD5 checksum value of the ISO image file by comparing it with the value on the product web page:

   Copy

   $ sudo md5sum ~/DPX_r410_linux.iso

6. Mount the ISO image file in the client system and go to this disk image. For example, use the following commands:

   Copy

   $ sudo mkdir /media/dpxclient/
   
   $ sudo mount ~/DPX_r410_linux.iso /media/dpxclient/

7. Run the installation program with the root privilege:

   Copy

   $ sudo /media/dpxclient/DPX-4.10.0-linux-installer.bin

1. The installation program prompts you to read the Software License Agreement; proceed to the next step if you agree.

2. Follow the instructions to set up the configurations:

   • Product directory to install the DPX Client application (default: /opt/DPX/)

   • DPX virtualization proxy server for VMware. Enter Y if you are using DPX on the VMware environment and you want to install this proxy server program on the client machine. (default: Do not install the proxy server.)

   • Logical node name (default: the hostname of the client system)

   • Host name or the IPv4 address of the client node (default: the IPv4 address of the client system)

   • Group name. Enter the name of an existing node group to add this client node to the node group. Or, enter a new node group name so that DPX creates a new node group with this name and adds the client node to this new node group. (default: DefaultGroup)

   • Registering this client node with the DPX Master Server as part of an Enterprise. If you answer 1 for Yes, enter the hostname of the DPX Master Server. (Default: Yes). You will need to provide the following node configuration details:

     • Logical Node name (specify the name of your choice);

     • Hostname or IP address of your machine;

     • Group name for the node: enter a name of an existing node group to add this client node to the node group. Or, enter a new node group name so that DPX creates a new node group with this name and adds the client node to this new node group. (default: DefaultGroup);

     • Hostname of master server (default: localhost);

     • Registering this client node with the DPX Master Server as part of an Enterprise. If you answer 1 for Yes, enter the hostname of the DPX Master Server. (Default: Yes)

   • For Micro Focus Open Enterprise Server: enter the root password, eDirectory user name, and eDirectory password. Enter the eDirectory distinguished user name and password which contain the context of the user object.

   • Block Data Protection to create block-level snapshot backups on this client node. (default: Enable)

Complete the installation. If you have not added the client node to the DPX Master Server, you can add the client node later from the Master Server interface (web or desktop), following the instructions in Adding a Client Node from the Master Server Level.

Take the following steps to uninstall DPX for Linux or UNIX:

1. Log in to a shell session of the Linux system that has DPX to remove, typically, by using an SSH client.

2. Run the uninstall script from <product-directory>/uninstall/uninstall_DPX with a root privilege. Typically, run the following shell command:

$ sudo /opt/DPX/uninstall/uninstall_DPX

The product version is now uninstalled.

Once installed and properly configured, the DPX Client does not require any further actions, such as logging in. If you have added your DPX Client as a node to the DPX Master Server during the installation process, you are ready to create your first backup job. If you do not have any client nodes added to your DPX Master Server yet, you can do it through the DPX web interface (recommended) or DPX desktop interface.

To launch the Master Server web (HTML5-based) interface, do the following:

1. Open your web browser and go to your Master Server’s IP address.

2. In the login box, enter the username and password for the Catalogic DPX Master Server.

1. Click the Login button. The DPX Master Server Dashboard will appear.

To launch the Master Server desktop (java-based) interface, do the following:

1. Ensure you have a Java environment on your computer to be able to run .jnlp files. If not, download Java or Open Web Start (recommended) and install the environment on your machine, following the provider’s instructions.

1. Open your web browser and go to your Master Server’s IP address.

2. At the bottom of the login box, click Run the DPX Java User Interface. This will download the dpx.jnlp file.

1. Run the downloaded dpx.jnlp file. The Connect to DPX dialog box will appear:

1. Make sure the Server Name or IP of your master server is correct, then provide the master server credentials to log in. The Catalogic DPX desktop interface opens.

From here, you have access to most Catalogic DPX functionalities, as described further.

Prerequisites

Before installing the DPX Client on Linux, review the following prerequisites:

• The minimum hardware requirements are as follows:

• Ensure your client system is included in the DPX 4.10 .

• The system resources and configurations of your client machine must meet the requirements as shown on the DPX product web page.

• Your client system must have the libnss3 plug-in. For example, you can install the libnss3 plug-in package in Red Hat Enterprise Linux 8 or supported variants of it by using the following command:

  Copy

  $ sudo yum install libnss3.so

• Your client system must have the iSCSI packages for the Instant Access (IA) mapping which is one of the features for the Block Backup of DPX. The package name and installation steps may vary. For example, you can install the iSCSI packages in Red Hat Enterprise Linux 8 or supported variants of it by using the following command:

  Copy

  $ sudo yum install iscsi-initiator-utils

• Allow all required ports for the Catalogic DPX Client:

• TCP: 3260, 6123, 6124, 9104, 9202, 10000, 10001, 10566, and 15660.

• UDP: 6123 and 6124.

Additional prerequisites

• The storage volume to install the DPX Client for Linux must be part of an LVM group.

• The physical extent (PE) of the LVM volume group to install the DPX Client for Linux must have free PE of at least 10%.

The DPX Hyper-V Agent is designed to facilitate efficient backup and recovery operations for virtual machines hosted on Microsoft Hyper-V servers. By integrating seamlessly with the Hyper-V environment, it provides robust data protection capabilities, including full VM backups and application-consistent snapshots. The agent ensures minimal disruption to running virtual machines while delivering reliable and quick restore options to meet diverse recovery requirements.

Installing DPX Hyper-V Agent on the Microsoft Hyper-V Host

Installing with Wizard

Before you back up any data from your Hyper-V VMs, you need to install the DPX Backup Agent on the host machine to enable agentless access to all VMs under this host.

1. From your Hyper-V host, go to Catalogic MySupport website. On the DPX 4.10 product page, under Software Download, find the Microsoft Hyper-V Agent installer and download it on your Hyper-V host machine.

1. Run the installer and go through the wizard steps.

1. In the Welcome step, click Next.

1. In the License Agreement step, read the entire License Agreement carefully. You must accept the terms to continue. Click Next.

1. In the Installation Directory step, specify the directory where the DPX Hyper-V Agent will be installed. The default directory is usually C:\Program Files\DPX\Hyper-V Agent. Click Next.

1. Leave default parameters and click Next.

1. Specify the Username and Password of an account with Domain Administrator Privileges on the Hyper-V Host. If the agent is installed on a cluster environment, this must be a domain account (user needs to have remote access between the nodes in a cluster). For a standalone machine, a local administrator account is fine. The Authorization Key is used for secure communication with the agent.

Click Next.

1. Review the details in the Summary screen and click Next.

1. The wizard is now ready to install the DPX Hyper-V Agent on your computer. Click Next to begin the installation.

1. The installation process will take a few minutes.

1. Click Finish to complete the process and exit the wizard. If the View Readme File box is checked, the readme file will be displayed in a separate window.

Upon successful installation, the DPX Hyper-V Agent service should be up and running on your Hyper-V host:

You should also be able to see a new firewall rule added for inbound traffic:

After successfully installing DPX Hyper-V Agent on the Hyper-V host, proceed with Adding a Configured Hyper-V Host as a DPX Node.

Installing via Powershell

If you prefer to install the Hyper-V Agent without using the Wizard and without any output, you can do it via powershell. The Hyper-V Agent installer requires the following parameters:

• --mode

• --password (Note: this is the authorization key)

• --adminUsername

• --adminPassword

& '.\DPX Hyper-V Agent-1.0-win-x64-installer.exe' --mode unattended --password 'secret' --adminUsername 'DOMAIN-NAME\user' --adminPass 'domainP@ss'

The installer also accepts the following optional parameters:

• --port – port number (default: 50881)

• --installDir – custom installation directory (default: C:\Program Files\DPX\Hyper-V Agent)

• --firewallRuleName – custom name for firewall rule added by the installer (default: DPX Hyper-V Agent)

Here is an example with all required and optional parameters:

& '.\DPX Hyper-V Agent-1.0-win-x64-installer.exe' --mode unattended --password 'secret' --adminUsername 'DOMAIN-NAME\user' --adminPass 'domainP@ss' --port 12345 --installDir "C:\custom\installation\directory" --firewallRuleName "Custom rule name" --unattendedmodeui minimal

If an additional parameter --unattendedmodeui minimal is used, a small dialog with a progress bar will be shown during the entire installation process.

When the installation is completed, you can add the Hyper-V as a node to DPX Master Server.

DPX Proxy Server is a component used in VMware environments for processing VMware backups without the need to install backup agents on VMs. It creates backup snapshots and transfers data to the specified destination, communicating with the master server. From version 4.8.1, it can be deployed as a virtual appliance. You can still use proxy server applications installed with the DPX Client on client nodes in the VMware environment, but it is recommended to deploy proxy servers for each vCenter as virtual appliances.

Unlike the application edition, the DPX Proxy Server virtual appliance includes a web interface, allowing the user to operate and monitor the proxy server from a web browser. You can also access the Linux shell in the web browser instead of using an SSH client.

Prerequisites for the DPX Proxy Server for VMware

Before deploying the OVF template for the DPX Proxy Server virtual appliance on your VMware environment, ensure that you have enough hardware resources in the VMware ESXi server. The following is the default configuration of the virtual appliance:

Default hardware configurations of the DPX 4.10 Proxy Server virtual appliance for VMware

This procedure describes adding an already existing DPX Client machine as a node to the DPX Master Server. This procedure is only possible if a DPX Client is already installed on the machine you want to add as a node. The DPX Client and the DPX Master Server must also be in the same network.

Before you start, make sure the following conditions are met:

• The Catalogic DPX Master Server is deployed and can be accessed through either web or desktop interface

• At least one Catalogic DPX Client is deployed within the same network

Procedure

The Catalogic DPX Proxy Server virtual appliance includes the web (HTML5-based) interface. It allows the user to operate and monitor the proxy server from the web browser. The user can also access the Linux shell in the web browser window instead of using an SSH client.

Connecting to the Linux Shell of the DPX Proxy Server

In most cases, you can access the Linux shell of the DPX Proxy Server from your web browser. Log in to the web interface as instructed in the and select Terminal from the side panel.

If you want to connect to the Linux shell via SSH, use the same credentials as for the web interface.

Connecting to the DPX Proxy Server web interface

After creating the Catalogic DPX Proxy Server virtual appliance in the VMware environment, you can access its web interface from your web browser.

From a web browser on your workstation, open the following URL:

https://<IPv4 address of the proxy server>:9090

On the log-in page, enter the default user name and password for the Catalogic DPX Proxy Server:

• User name: dpxadmin

• Password (only for the first time): dpxadmin

You can open the following pages from the navigation pane:

System

Overview

You can see the system information and resource monitors for the machine’s health, CPU utilization, system information, and configuration. You can also restart or shut down the system.

Logs

In the Logs page, you can view the records of the Linux system log (/var/log/messages). You can specify the time range, event severity, and service such as kernel and systemd.

Networking

Monitor the throughput of the sending packets and receiving packets. You can also see the Networking Logs for network-related services such as NetworkManager and firewall.

Do not enable the firewall from this page or you will lose access to the Cockpit interface immediately. To disable the firewall and regain access to the Cockpit interface, log in to the Linux shell and stop the firewall by using the following command:

$ sudo systemctl disable --now firewalld
$ sudo systemctl restart cockpit

Accounts

Manage accounts such as root and dpxadmin in this Linux system. You need to log in with the privileged access to use this page.

Services

View a list of system services that are usually managed by systemd. Click either service and you can see the details of this system service such as the status: active, inactive, and so on. You can also start, stop, or restart the system service.

Navigator

You can browse and view files in this Linux system.

Tools

Applications

See and manage all applications installed or available on this Linux system.

Diagnostic reports

You can download the system files and log files that are usually helpful to troubleshoot system issues. These files are archived and compressed in tar.xz format.

DPX Proxy

You can see the product information of the Catalogic DPX Proxy server application on this virtual appliance: the product version number, the patch level, and so on. In addition, you can check the server status, stop the server, and start it again.

Software updates

Check for system update status and automatic update settings.

Terminal

Access the Linux shell from your web browser without using the machine monitor or an SSH client.

Nodes other than DPX Client nodes must be added manually from the DPX Master Server. The procedure is similar to . There are differences in naming conventions and feature handling between the web interface and desktop interface.

Each machine, be it virtual or physical, server or client, is considered a node of the Enterprise’s network it belongs to. The master server is a DPX node that contains DPX software, including the Catalog and modules that control scheduling, media management, and distributed processing. There is one master server per data protection Enterprise.

In order for the DPX to be able to perform any backup or restore jobs, a logical relation must be established between the Master Server and other nodes, such as Client or storage nodes.

Typically, you will deploy the DPX Master Server first, providing its hostname, network IP address, credentials and several other parameters. In the second step, you will deploy a DPX Client on each machine you want to back up from. During this process, you will provide the DPX Master Server’s hostname or IP address and credentials, thus adding the Client as a node to the Master Server.

You may also deploy DPX clients first, and add the client nodes to the Master Server later, using either web or desktop interface.

Removing a Node

There are two versions of the Catalogic DPX Client installer for Microsoft Windows: the client-only version and the full version.

In most cases, the client-only version suffices. To protect VMs in a VMware virtual environment, deploy the Catalogic DPX Proxy Server virtual appliance in the same VMware environment. See DPX Proxy Server.

Instead of deploying the Catalogic DPX Proxy Server virtual appliance, you can install the proxy server as an application along with the Catalogic DPX Client on the same Microsoft Windows machine. In other words, if you are planning to deploy the proxy server virtual appliance in the VMware environment or if you are not using the VMware solution at all, use the client-only version.

A tape library device is a single media drive in a tape library (for example, a DLT drive). supports backups to tape libraries on LANs, WANs, or SANs. For information on adding standalone devices, see Adding a Device.

Guidelines for adding a tape library device:

• A tape library device always belongs to a previously defined tape library.

• A tape library device cannot belong to more than one tape library.

• All devices in a tape library must use the same media (for example, DLT).

• Tape drives must be capable of writing in variable block size mode. For some operating systems (for example, IRIX) the default device driver is for fixed block size; in such case, you must obtain and install a tape device driver with variable block size writing capability. These are often available from the manufacturers’ websites.

To define a new device:

1. Click Configure on the Function Tab bar of the window, then click Devices.

2. Open the Add Device dialog in the right pane by doing one of the following:

   • Right-click the tape library name or icon to display a context menu. The selection is indicated by the selection check box next to the tape library icon. Then select Add Device.

   • In the left pane, select the tape library to which you want to add the device and do one of the following:

     • From the menu bar, select Device > Add Device.

     • On the task panel, click Add Device.

   The Add Tape Library Device dialog appears.

3. Complete the active fields in the Add Device dialog:

Device Name Enter a name for the device (up to 48 alphanumeric characters, no spaces). This is a logical name used to conveniently refer to the device (for example, SALES_DRIVE1).

Logical Node Name (non-SAN device only)

Select the name of the node to which the device is attached (for example, SALES_SERVER1) from the pull-down menu. This node must have been previously defined (via the Configure Enterprise window). You can have multiple devices on a node, up to the limit the hardware supports.

On the Device Resource Tree, the non-SAN device appears as device_name@logical_node_name.

Device Number This field identifies a device within the tape library. The first storage device is usually 0. For each additional device, the Device Number increments (i.e., your second device would be 1).

There is a critical relationship between Device Number and Device ID for tape library devices. See Determining Device Number and Device ID.

Device ID (non-SAN device only)

For devices on UNIX, Linux and OES Linux, enter the path to the device file. For example, for Linux, the first storage device is usually /dev/nst0. For each additional device, the number in the path increments, thus your second device would be /dev/nst1.

The following table lists common Device ID nomenclature for various flavors of UNIX:

• For devices on supported versions of Windows, the first device is normally called \\.\Tape0. For each additional device, the number in the ID increments (i.e., your second device is \\.\Tape1). You can find this information displayed in Tape Devices in the Control Panel of the Windows node. To do so, go to the Control Panel, select Tape Devices, choose the Properties tab, select the device, and click Properties. The Device ID is referred to as the Device Map.

Unique ID

This optional field identifies a device uniquely. Generally, it is the hardware serial number.

Comment Enter an optional comment up to 48 characters.

1. Select Add on the task menu at the top right of the right pane. If you are unable to see the task menu, resize the right pane.

Storage devices (also referred to as “devices”) are physical or virtual drives on which media volumes, such as tape cartridges, are processed. Devices are grouped in clusters. To add a device, you need to have a device cluster defined first. Device clusters can only contain devices of similar type, e.g. LTO4 tape drives. See Adding a Device Cluster.

When you create a node group, you may specify the default device cluster or tape library for the group. Later, you can override this default when you define a backup or migrate job.

There are two types of storage device groupings, each having two setup variations. The groupings are device clusters and tape libraries. The variations are SAN (Storage Area Network) and non-SAN devices. A device cluster is a collection of devices logically grouped by the system administrator. A tape library is a collection of devices that are grouped physically. From a functional viewpoint, a tape library is analogous to a device cluster. Thus, tape libraries displayed in the desktop interface are often listed along with device clusters under the heading Device Cluster.

Media, or media volume, is a storage unit such as tape or Disk Directory

Media volumes are physical media, such as tape cartridges, or logical storage units, such as Disk Directories, to which data can be backed up or duplicated. Data can only be backed up or duplicated to volumes that have been defined.

A media volume has a unique volume name (also abbreviated to volser = volume serial number) and must be a member of a media pool. You can define media pools and their member media volumes, as well as modify and delete those definitions.

When creating a node group, specify, from the media pools you have created, a default media pool for the node group. Later, when you define a backup or migrate job, you can override this default. During a backup, DPX issues prompts to the media operator or media changer to mount media volumes from the default or specified media pool. The specific volume is chosen from the media pool by DPX and cannot be predicted.

This topic describes how to test communication between the tape library and the controller node containing the installed media changer device file. For DPX, verification is recommended if you installed your media changer device file by using the manual installation procedures described in Manual Tape Library Installation.

Testing the Tape Library Installation

The tape library media changer test program JItest.exe (or ./jitest* depending on platform) is used to test the tape library installation. The test program requires as an argument the media changer device file name created during the installation procedure in the preceding chapter. The example here uses a Windows device name. The only difference between this example and other platforms is the device name which can be /dev/sync_sa0, /dev/rchg/c000t0d0s0, etc. For UNIX and Linux environments, run ./bin/bexenv prior to running the jitest utility.

1. At the command line, type jitest sync_sa0 (or ./jitest /dev/sync_sa/0 for UNIX). This produces the following output: Please type the command.

2. Enter the command open to open communications. Sample output follows:

   Copy

   Device <<sync_sa0>> is opened.....
   do_inquiry().....
   Inquiry report
   ==========================================================
   Exist bar Code Label Scanner UNKNOWN.
   capabilities= 0xe0eee
   initr= Yes
   im/export= Yes
   support arm rotate= No
   need alignment= No
   need init after port is accessed = No
   Support Extend = No
   Support Retract = No
   Support AutoUL = No
   vid="STK "
   pid="9730 "
   fid="1102"
   misc="0x303f"
   NUM_ARMS=1 FIRST_ARM_ADDR=1000
   NUM_CARTS=30 FIRST_CART_ADDR=0
   NUM_DRIVES=2 FIRST_DRIVE_ADDR=1030
   NUM_XPORTS=1 FIRST_XPORT_ADDR=1010
   ==========================================================

   The output lists information about this particular tape library. An explanation of some of the parameters follows:

   NUM_ARMS

   Number of media changers and the address of the first media changer (FIRST_ARM_ADDR).

   NUM_CARTS

   Number of tape cartridges and the first cartridge (FIRST_CART_ADDR).

   NUM_DRIVES

   Number of tape drives and the first drive (FIRST_DRIVE_ADDR).

   NUM_XPORTS

   Number of CAPs (Cartridge Access Ports) and the first CAP (FIRST_XPORT_ADDR).

   In our example, the address of the first drive is 1030. The second drive therefore has an address of 1031. The same holds for the cartridges. The first cartridge has an address of 0, the second has an address of 1, and so on.

3. Type setup 0.

4. Type quit to quit JItest, or type help for other useful commands.

5. If the media changer accepts these commands without obvious error, the tape library is ready to be configured for use. Proceed to Manual Tape Library Configuration for the tape library configuration procedure.

A device cluster is a logical grouping of non-tape library (standalone) backup devices. For information about adding a tape library, see Adding a Tape Library.

Guidelines for adding a device cluster:

• Every device must be a member of one and only one device cluster.

• All devices in a cluster must use the same media. For example, devices that use disk directories and devices that use tape cannot be in the same device cluster.

• A single device cluster cannot contain both devices on a Storage Area Network (SAN) and devices directly connected to a server. They must be in separate device clusters.

Before adding a Hyper-V Host as a node to DPX, make sure you have a Hyper-V host with a DPX Hyper-V Agent installed. For details, see DPX Hyper-V Agent.

The procedure below describes adding a Hyper-V host as a node to the DPX Master Server.

1. Open the DPX Master Server web interface in a web browser.

2. In the left-hand side menu pane, go to the Nodes section.

3. Click the Add Node button in the upper right corner.

1. The Add Node dialog will open. As Type, select Hyper-V Host. Specify the name for the new node (it must be unique throughout the Enterprise), provide a valid resolvable hostname or IP address, and select the group for the node.

1. Click Save. The node is now added and is visible in the nodes list.

To manage your nodes better, you may organize them in node groups. To add a new node group, follow the procedure specific for the interface you are using.

For any cluster, it is highly recommended to create a separate node group.

Before adding a media pool, review the following prerequisites:

• It is desirable for media pools to correspond to logical groups, such as business components (SALES_POOL, MARKET_POOL, etc.) or physical locations (EAST_POOL, WEST_POOL, etc.).

• It is advantageous to locate a pool of media volumes near the backup devices where the volumes are mounted. This avoids the delay that can result when an operator must search elsewhere for the media volume requested by Catalogic DPX.

• If the media pool is used for multiple device clusters, the device clusters and the media pool must be near each other. As you cannot predict the media volumes in the pool for which Catalogic DPX prompts, all free volumes in a pool must be easily available to all device clusters that might need it.

To add a media pool in DPX, do the following:

For Disk Directory devices, adding more devices to a device cluster is not required, as devices perform only a logical function in backup and restore operations. For tape devices, the device cluster includes physical devices available for backup and restore operations within the cluster. See Adding a Tape Library Device for details.

For Windows non-clustered nodes, you can install DPX client software from a single point in your Enterprise rather than by running the installation program from the installation image on each remote machine. This single-point installation procedure is referred to as remote deployment.

Remote deployment automatically adds installed nodes to the Enterprise, with each node in a separate node group.

For database servers, you can install remotely, but you must install database support locally. For this reason, you may want to install locally for such servers just before installing the database support.

If you have Windows 10 clients, be aware of the following. The administrative account on Windows 10 is inactive by default and needs to be enabled before DPX can be installed via Remote Deployment. Therefore, if you run Remote Deployment from the master server, some Windows 10 client nodes might fail with “Access Denied” error. In that case, log into each of the Windows 10 client nodes that fail and enable the Administrator Account. Then rerun Remote Deployment from the master server.

Before defining a tape library to DPX, you must install the tape library driver on the node to which the tape library is attached. Follow the instructions in Chapter 33: Device Configuration Wizard in the DPX 4.9.x Reference Guide.

A single tape library cannot contain both devices on a storage area network (SAN) and devices directly connected to a server.

To define a new tape library:

1. Click Configure on the Function Tab bar of the window, then click Devices.

1. Open the Add Tape Library dialog in the right pane by doing one of the following:

   • Right-click the Enterprise name or icon to display the Enterprise context menu. The selection is indicated by the selection check box next to the Enterprise icon. Then select Add Tape Library.

   • In the left pane, select the Enterprise to which you want to add the tape library and do one of the following:

     • From the menu bar, select Device > Add Tape Library.

     • On the task panel, click Add Tape Library. The Add Tape Library dialog appears.

1. Complete the active fields in the Add Tape Library dialog:

Tape Library Name

Enter a name (up to 14 alphanumeric characters) for the tape library (for example, New Tape Library). No two tape libraries in the Enterprise can have the same name.

Storage Area Network Specify whether devices in the tape library are connected to a Storage Area Network (SAN). A tape library cannot contain both devices on a SAN and devices directly connected to a server.

Tape Library Type Select a tape library type (for example, EXB210) from the pull-down menu. (For an ADIC SDLC tape library, select ADIC_AML.)

If you select either ACSLS for a StorageTek Automated Cartridge System (ACS), ADIC_AML for an AML Automated Storage Library, IBMATL for an IBM Magstar 3494 Tape Library (IBM 3494), the Using Slot and Cleaning Slot fields disappear and the Storage Area Network field is forced to No.

If you select ACSLS, the Controller ID field disappears and the ACS Number field appears. If you select IBMATL, the Category field appears in the dialog. If you select ADIC_AML, the pull-down menu on the Device Type field is disabled.

Controller Node The controller node is a node that communicates with and controls the tape library media changer. The controller node is a special case of a device server. This is also the node where you have installed the tape library device driver. See Device Configuration Wizard.

Select the node name of the controller node (for example, SALES_SERVER_1). The controller node is connected to the tape library media changer either directly or over a SAN.

Although this node must be running one of the operating systems specified in Manual Tape Library Installation, tape library devices (tape drives) can be attached to any controller node or NDMP node in your regular network or SAN.

Controller ID Enter the complete path and name to the media changer device file on the controller node. The media changer device file contains the file handle for the tape library driver. For example, the media changer device file could be /dev/sync_sa/t0d0 for Sun or C:\backex\bin\JB\sync_sa0 for Windows. This file is created by DPX during tape library driver installation. See Device Configuration Wizard.

For IBM 3494, this is the logical name of the library control point that you specified when you first configured IBM 3494. This field does not appear if you choose ACSLS in the Tape Library Type field.

ACS Number This field only appears if you choose ACSLS in the Tape Library Type field. Enter the ACS Number. The ACS Number was specified in ACSLS when the ACS was first configured, and its valid range is 0-126. For more information on ACS, see Chapter 41: Using Oracle StorageTek Automated Cartridge System Library in the DPX 4.9.x Reference Guide.

Category This field appears if you choose IBMATL in the Tape Library Type field.

Device Type Select a device type (for example, 4 mm) from the pull-down menu. All devices in a tape library must be the same type. If you chose ACSLS from the Tape Library Type pull-down menu, the Device Type DLT appears in this field.

Using a Slot Enter the starting and ending slot numbers to use for media volumes. For example, entering 1 and 11 means for DPX that slot numbers 1 through 11 are reserved for media volumes.

Cleaning a Slot Enter the slot(s) used for the cleaning media. If there is only one cleaning slot, enter the slot number twice; for example, 0 through 0 indicates that slot number 0 contains a cleaning media (the default value). If there is no cleaning slot, enter -1 in each field.

Cleaning Threshold Enter the number of times a drive can be used before it is cleaned. An internal counter is incremented each time a media volume is inserted in the drive. For example, if you enter 50, a media volume can be inserted in the drive 50 times. Just before the next use, the cleaning media is inserted to clean the drive head. After the drive is cleaned, the counter is reset to 0.

Comment Enter an optional comment of up to 48 characters.

1. Select Add on the task menu at the top right of the right pane. If you are unable to see the task menu, resize the right pane. The new tape library name appears in the device resource tree in the left pane and is indicated by the selection check box. The add tape library dialog in the right pane becomes the edit tape library dialog for the new tape library.

A media volume is an individual backup medium, such as a tape cartridge. Each media volume is identified by volume name. Another term for volume name is volser (volume serial number).

Requirements for media volumes:

• A media volume must be a member of a media pool.

• A media volume cannot belong to more than one media pool.

• All media volumes in a media pool must be of the same type (for example, a 4 mm tape cartridge).

• Data can only be backed up to defined volumes. However, it can be labeled on the fly if you choose the global default option for doing so.

• For a media pool used with a StorageTek ACS, an IBM 3494, or an ADIC AML or SDLC, you do not use DPX to add media volumes to the pool. Instead, you add tapes through the hardware interface of the manufacturer. When you later perform a backup, DPX automatically adds the new media volumes to the appropriate media pools.

Prerequisites for Tape Library Deployment

A physical node in the Enterprise is available to control the tape library’s media changer. This can be a Windows server, Linux server, or the NetApp storage controller. A virtualized node cannot be used for media changer control. This controller node must have a host bus adapter. Note that a media changer is also referred to as a robotic arm and a host bus adapter is also referred to as an HBA.

Recommended Best Practices for Tape Libraries

• The media changer is attached to a SAN (storage area network) and zoned to the master server. Therefore the master server acts as the tape library’s controller node.

• The tape drives are attached to the SAN and zoned to the NetApp storage system. Therefore the NetApp storage system acts as the device server.

• The tape library is a modern, vendor-supported library with tape drives capable of writing in variable block size mode. The media changer is SMC-2 compliant and supports the DVCID option of the Read Element Status command. The tape drives are SCSI-2 compliant and support variable length records and extended file marks. The tape library and tapes support bar coding. Most modern tape libraries fit these requirements. DPX does not support libraries and tape drives currently unsupported by the device vendor.

• For DPX purposes, the media changer device and associated tape drives must belong to only one Enterprise controlled by a single master server. Tape library media changer control cannot be shared with other backup products and cannot be accessed by more than one master server.

Other Tape Library Setup Scenarios

If, in conjunction with the customer, a strategic determination is made to attach the media changer or tape drives differently, you can do so. However, the practices described in Recommended Best Practices for Tape Libraries are highly recommended to maximize reliability and minimize troubleshooting challenges.

There are several supported ways to attach the tape library’s media changer and tape drives to the Enterprise. They can be connected through a fiber channel SAN, iSCSI SAN, direct fiber channel attachment, or legacy parallel SCSI cable attachment.

If the connection is through a fiber channel SAN, the media changer must be controlled by a device server, not by a NetApp storage system, and the tape drives can be controlled by any node or NetApp storage system.

If direct attachment through a fiber channel or legacy parallel SCSI is required, it is highly recommended for the media changer and at least one tape drive to be attached directly to the master server to support media changer control and Catalog backups. If a tape drive cannot be connected or accessed through the master server, an alternate strategy must be used to move Catalog backups to a safe medium that can be recovered in the event of a site disaster.

iSCSI SAN connections are generally not recommended due to latency and connection reliability. If iSCSI is absolutely necessary, for example, if no physical server with HBA is available for media changer control, great care must be taken by the site administrators to ensure such connections are very reliable. Any disruption in connection will impact backup and media control operations.

Though it is possible to attach a tape library directly to a NetApp storage system for exclusive control of media changer and all tape devices, it is not recommended as an alternate strategy for Catalog backups is required. Additionally, media changer reliability and troubleshooting may be problematic, requiring moving the media changer device to a node with an HBA physical server. NetApp media changer control is also limited to tape libraries with 600 total slots or less; larger tape libraries do not work properly due to SCSI limitations.

General Overview

This topic describes the procedures required to set up an LTO4, 5, or 6 tape device for hardware encryption. The procedures that apply depend on the tape device manufacturer and operating system, as indicated in the following table:

Note the following:

• For HP and Quantum tape devices on Windows device servers, the Bexsptape device driver is required for hardware encryption. Implementing Bexsptape is done in .

• For IBM tape devices, Bexsptape is not needed. An IBM device driver supporting hardware encryption is required. Only applies to IBM drives.

• For Linux and UNIX operating systems, Bexsptape is not required.

Procedures for Setting up LTO Tape Drives for Hardware Encryption

Follow the procedures that apply to your tape device and operating system; thus, for IBM devices, skip to ; for Linux and UNIX device servers, omit .

Procedure 1. Enable Hardware Encryption

To enable hardware encryption using the Device Configuration Wizard:

1. Launch the Device Configuration Wizard.

2. In the Select Nodes to Scan dialog, select the node where the drive is installed, and then click Options. The Node Options dialog displays.

3. Select the check box Check here to enable DPX LTO Encryption options.

4. From the Please select drop-down menu, select Enable/Update.

5. Click OK.

6. If the drives are already added to the Enterprise, click Exit. If the drives are not added to the Enterprise, continue to use the Device Configuration Wizard to add them.

Procedure 2. Configure the Windows Device Sever to Use the Bextape Device Driver

To configure the device server for Bexsptape:

1. In the Windows Device Manager, locate the tape device to associate with the Bexsptape driver. Note the following:

   • If the tape device already has a driver associated with it, uninstall the driver. If a selection displays to permanently delete the driver, it is recommended to select it. This ensures that the driver is not available for the device in the future, eliminating possible conflict with Bexsptape.

   • Tape devices that do not have a driver associated with it are in the Other Devices container of the display.

2. Right-click the appropriate tape device, and then select Update Driver Software from the pop-up menu. The first page of a wizard appears.

3. You are asked how you want to search for driver software. Select Browse my computer for driver software.

4. On the next wizard page, select Let me pick from a list of device drivers on my computer. Click Next.

5. From the display list, select your device type, Tape drives. Click Next.

6. On the next page, enter the location of the Bexsptape device driver. Select Have Disk.

7. Browse to <product-directory>/bin/drivers/<Osver>, where <Osver> is specific to the version of Windows the device is installed on.

8. From the display list, select bexsptape. Click Open.

9. Select the tape drive manufacturer and model in the Model list. Click Next.

10. A success window appears, confirming that the driver software is updated. Click Close.

11. Confirm that the tape drive appears in the Tape drives container in the Windows Device Manager display.

Procedure 3. Run Detect

Run the Detect utility to record the device id and update your data protection Enterprise to use the Bexsptape driver.

The Bexsptape type of device file is formulated as: bexsptape_vp<0123456789>_cn or bexsptape_vp<0123456789>_n, where

• v and p are the first character of the vendor ID and product ID reported by the SCSI Inquiry command.

• <0123456789> is the ten-digit unit serial number reported from the tape device.

• n denotes no rewind.

• c denotes compression enabled.

Either device id format, ending in _cn or _n, may be used when configuring the tape device in your Enterprise.

Once the Detect utility completes, the tape device is available for hardware-encrypted tape backups.

A tape library is a hardware unit comprised of multiple physical or virtual tape drives and tape slots with a media changer for automatically inserting and removing tapes. The device is sometimes referred to as an automated tape library or jukebox.

Catalogic DPX supports tape devices and media changers compliant with the SCSI-2 standard. Tape drives must support variable-length records and allow a minimum transfer size of 32 KB. Additionally, media changer support on Microsoft Windows requires Microsoft Windows NT SCSI Pass-Through support from the HBA driver or a vendor-supplied media changer driver supporting Microsoft Windows NT SCSI Pass-Through.

Unless otherwise advised by Catalogic Data Protection Technical Support, the operating system of the Device Server that connects the tape or tape library device should have properly installed drivers as recommended by the device manufacturer.

Catalogic DPX treats a Virtual Tape Library (VTL) device as a regular tape library and supports it the same way it does for tape libraries.

Catalogic Software has qualified Catalogic DPX with the following tape media:

Catalogic Software has qualified Catalogic DPX with the following tape libraries:

Manual tape library installation involves creating, on the controller node, a device file for the tape library media changer. This media changer device file is a handle used by DPX to identify the hardware address of the media changer. It thereby allows communication with the media changer. Once that communication is established, the tape library driver controls the media changer.

This chapter explains how to manually install the media changer device file. This procedure is required if you are setting up your tape library using Manual Setup (Process B).

The manual installation procedure for the media changer device file varies according to the operating system installed on the controller node. To see specific installation instructions for a particular operating system, refer to the topic that applies to the controller node of your tape library:

Furthermore, if you are using third-party software no longer supported by the vendor, Catalogic Software Data Protection Technical Support may be limited for functions dependent on that software. To address certain issues, the analyst may recommend you upgrade the relevant software.

Tape Library Installation on Windows

This procedure explains how to install a tape library for a Windows controller node. Before you begin, make sure the tape library is in random mode (not sequential or stacker mode) and that the media changer is not claimed by the operating system. See .

DPX supports both 32-bit and 64-bit versions of Windows.

To install the media changer device file on your controller node, run detect -i at the command prompt. This will automatically generate media changer device files of the form sync_saX, where X is a non-negative integer starting with 0.

Device files are placed in the bin\JB folder. detect -i also creates a symbolic link for each sync_saX device, allowing it to be used as a native Windows device name.

Sample output for detect -i follows:

SCSI Devices found:

------------------

Device       Adapter     Target            Device

ID           ID      BUS ID     LUN STATUS Type                     String

------------ ------- --- ------ --- ------ ------------------------ -------------

\\.\Tape0    2       0   0      2   0      Sequential Access Device SONY    SDX-500C

\\.\Tape1    2       0   0      5   0      Sequential Access Device HP      Ultrium 1

\\.\sync_sa0 2       0   1      3   0      Media Changer Device     BHTi    216

\\.\Tape2    2       0   1      1   0      Sequential Access Device QUANTUM DLT8000

Device                    Serial / Unique                                    

ID                        Number / Id              World Wide Name           Auto

------------------------- ------------------------ ------------------------- ----

\\.\Tape0                 0000902585               20 0 0 50 13 b0 78 94     Yes

\\.\Tape1                 0000911832               20 0 0 50 13 b0 78 94     Yes

\\.\sync_sa0              216B10                                             Yes

\\.\Tape2                 PXB34P3669               20 0 0 50 13 b0 78 94     Yes

Tape Library Installation on Linux

This procedure explains how to install a tape library for a Linux controller node. You need to have Linux release 2.2.14 or later. The procedure below is for Linux on Intel-compatible architectures.

For Linux, device files of the media changers are generated by the operating system and are located in /dev/sgX, where X is a non-negative integer starting with 0. Device files of the tape drives are located in /dev/stX or /dev/nstX where X is a non-negative integer starting with 0. The tape drives must be set to no rewind and variable block size, which are commonly not the default. For more information, see the man pages for “st” and “stinit” in addition to consulting the drive manufacturer.

The following is the procedure for tape library installation on Linux:

1. On your controller node, run detect -q at the command prompt. detect -q displays the file names and other information about all SCSI devices accessible by the node on which you are running detect. If everything was connected properly, you will see a media changer device that represents your tape library. Sample output follows:

SCSI Devices found:

-------------------

Device       Adapter     Target            Device

ID           ID      BUS ID     LUN STATUS Type                     String

------------ ------- --- ------ --- ------ ------------------------ -------------

/dev/nst0    2       0   0      2   0      Sequential Access Device SONY    SDX-500C

/dev/nst1    2       0   0      5   0      Sequential Access Device HP      Ultrium 1

/dev/sg1     2       0   1      3   0      Media Changer Device    BHTi    216

/dev/nst2    2       0   1      1   0      Sequential Access Device QUANTUM DLT8000

Device                    Serial / Unique                                    

ID                        Number / Id              World Wide Name           Auto

------------------------- ------------------------ ------------------------- ----

/dev/nst0                 0000902585               20 0 0 50 13 b0 78 94     Yes

/dev/nst1                 0000911832               20 0 0 50 13 b0 78 94     Yes

/dev/sg1                  216B10                                             Yes

/dev/nst2                 PXB34P3669               20 0 0 50 13 b0 78 94     Yes

1. If you do not see any devices, ensure that the kernel has generic SCSI support and tape drive support installed. For more information, see the man pages for “sgen” and “mtx.”

2. If necessary, run detect -i from the bin/JB subdirectory to create any additional device mappings.

This chapter provides an overview of how to manually configure a tape library for DPX after the media changer device file is installed. The detailed instructions can be found in in the DPX 4.9.x Reference Guide. Manual configuration is not needed for tape libraries that were successfully set up using Automatic Setup (Process A). However, Automatic Setup does not configure media pools, assign media, or define backup jobs, all of which are also summarized at the end of this topic.

All the manual configuration steps are performed from the management console.

Defining Tape Libraries and Tape Drives

The following steps are required if you set up your tape library by using Manual Setup (Process B):

1. If you have not already defined your Enterprise, do so now.

2. If you have not already added your controller node(s) and device server nodes to your Enterprise, do so now.

Adding Tape Library and Tape Drives to the Enterprise

The following steps are required if you set up your tape library by using Manual Setup (Process B):

1. Add the tape library to your Enterprise. Use the Adding a Tape Library function in the management console. You need to supply information about the controller node. Follow the instructions in .

2. Assign the tape drives to the tape library.

To add the tape drives, use the Adding a Tape Library Device function in the management console. Follow the instructions in .

You need to supply information about the Device ID of the tape drive and the Device Number of the drive bay. See the following section for a discussion about Device ID and Device Number mappings.

Determining Device Number and Device ID

Each tape drive in a tape library resides in a unique drive bay. The tape library drive bay is designated by the Device Number and the tape drive driver is designated by the Device ID.

This mapping between the drive bay and tape drive driver is critical for proper tape library operation.

Generally, the first drive bay (Device Number 0) is mapped to the first tape drive. So for Windows, the mapping would be as follows:

\\.\Tape0 is mapped to Drive Bay 0 (Device Number 0) \\.\Tape1 is mapped to Drive Bay 1 (Device Number 1) etc.

Similarly, for Solaris, the mapping would be as follows:

/dev/rmt/0cn is mapped to Drive Bay 0 (Device Number 0) /dev/rmt/1cn is mapped to Drive Bay 1 (Device Number 1) etc.

To confirm this, configure the tape drives in this manner, then try to load and unload a tape.

If you determine that it is not the case that the drive bays are mapped to the tape drives in order, do the following to manually map the device bays to the tape drives:

1. Find out how the tape library numbers the drive bays internally. For example, top down, bottom up, or other. Consult the tape library documentation or manufacturer.

2. Load the tape drives with tapes (preferably scratch tapes).

3. Use the tapedump utility to acquire one of the tape drives and unload the tape. For example:

   $ ./tapedump tape /dev/rmt/0cn open rdonly unload

4. Look inside the tape library and determine which tape ejected. Make note of:

   • The tape library drive bay number (Device Number) of the tape that physically ejects.

   • The Device ID you used to acquire this tape drive (/dev/rmt/0cn in our example)

   • The device server node for this tape drive.

5. Quit tapedump and cycle through the device drivers on this and other device servers to map the tape library in its entirety.

Media Configuration

The following steps are required regardless of whether you set up your tape library using Automatic Setup (Process A) or Manual Setup (Process B):

2. Associate media volumes (tapes) with the media pools and label the media volumes. You usually want to add tape volumes in sets of consecutively named volsers. DPX provides several methods for assigning media volumes to media pools and labeling media volumes.

Backing up Data to the Tape Library

This procedure describes adding a client node to an already deployed Master Server within the same Enterprise. This procedure is only possible if the DPX Client is not yet installed on the machine you want to add as a node.

Before you start, make sure the following conditions are met:

• A Catalogic DPX Master Server is deployed within the same network

• The Master Server’s hostname / IP address and credentials are known

• The Catalogic DPX Client is not yet deployed on the machine you want to add as a node

Procedure

1. Download the Catalogic DPX Client installer for your platform and follow the installation instructions. For details, see DPX Client installation on or .

2. In the Add node to DPX Enterprise section, choose Yes to add this node to the Enterprise. You will need to provide the Master Server Hostname or IP address.

To deploy DPX Proxy Server virtual appliance for VMware, take the following steps.

1. Log in to the Catalogic website.

2. Go to the DPX 4.10 product page and download the OVA file for the DPX Proxy Server. The file name is structured as shown: dpx-proxy-<version-number>-<build-number>.ova

3. Once the file is downloaded, log in to vSphere.

4. Right-click on the folder where you want to deploy your virtual machine.

5. Follow the instructions in the Deploy OVF Template wizard. In the License Agreements page, read the Software License Agreement (SLA), select I accept all license agreements if you agree, and proceed to the next steps.

6. In the Customize template page, enter the following values:

   Hostname Configurations

   • Hostname: The hostname of this DPX Proxy Server virtual appliance. The hostname must be unique.

   Connection Configuration

   • Network IP Address: Enter the static IPv4 address of this virtual appliance. Or, leave it blank so that the dynamic IPv4 address is given via the DHCP.

   • Network Prefix: Enter 24 for the network prefix of this network interface if you are using the static IPv4 address.

   • Default Gateway

   • DNS Servers

   Keyboard Language Configuration

   • Keyboard Language: Select either one of the keyboard layouts for the Linux shell from US English (us), UK English (uk), German (de), French (fr), Chinese (cn), or Polish (pl). The default keyboard layout is US English.

   Timezone Configuration

   • Timezone: Enter the time zone (TZ) value for the Linux operating system. The default TZ is the US Eastern Time (America/New_York).

1. DPX Proxy Configuration

   • DPX Master FQDN/IPv4 Address

   • DPX Master Node Group: DefaultGroup

   • DPX Master UI Username: A user name of the DPX Management Interfaces. The user must be in the Administrator role. The default user is sysadmin.

   • DPX Master UI Password: The password for this user.

   Review the configurations and launch the deployment of the virtual appliance of the DPX Proxy Server for VMware. Ensure that the new VM for the DPX Proxy Server has been created in VMware vSphere Client. Click Next.

2. Review all the data in the final Ready to complete screen and click Finish.

3. Upon successful deployment, power on the DPX Proxy Server virtual appliance. The appliance should be visible as a node added to the Master Server specified in Step 7.

Introduction to Tape Library Setup

Catalogic DPX is designed with comprehensive tape library support in mind.

Tape library setup involves two major procedures: installation and configuration. Each of these procedures is described below.

• Tape Library installation entails creating the media changer device file needed to enable communication between DPX and the tape library media changer.

• Tape Library configuration entails defining the tape library properties so DPX can back up to and restore from media (tapes) accessible to the tape library.

For more information about tape libraries in the NetApp environment, read knowledge base article – Configuring Tape Library Connected to NetApp Appliance.

Tape Library Pre-Setup

Before beginning the tape library setup process, use the Detect utility to ensure DPX can communicate with the medium changer and that the medium changer status is zero.

The recommended starting point is Unknown Medium Changer disabled, which displays in the Windows Device Manager. If Detect can communicate with the medium changer, the status is zero. For each Detect attempt, the goal is to validate that Detect can see a medium changer and that the status is zero. If those states are not displayed, make a change and run Detect again.

Prepare to use Detect

Ensure the following conditions are met before using Detect:

• SCSI support and tape drive support are enabled on the operating system. Physically connect each tape library to its controller node and device servers. You can do this directly or through a SAN.

• The tape device drivers, which are supplied by tape drive manufacturers, are properly installed. Drivers are often available from the manufacturer’s website. Additionally:

  • Drivers are compatible with the operating system of the device server. Consult the documentation provided by your hardware vendor.

  • Tape drivers are capable of writing in variable block size mode.

• On Windows platforms, tape drives are visible in Device Manager and the drives are enabled.

• DPX client software is installed on controller nodes and device servers. Client software is installed on the master server by default.

• For controller nodes, the media changer is not claimed by the operating system or any other software. The media changer must be available for DPX to claim.

• The media changer device is disabled in the Device Manager. On Windows Server, the media changer is usually displayed in Device Manager as an Unknown Medium Changer.

To disable the media changer:

1. Use either of the following methods to navigate to Device Manager:

   • Click Start > Settings > Control Panel > Administrative Tools > Computer Management > Device Manager.

   • Right-click My Computer, then select Properties > Hardware > Device Manager.

2. Right-click on the media changer (usually Unknown Medium Changer). Select Disable.

If you see the message Disabling this device will cause it to stop functioning. Do you want to disable? Select Yes.

Note that disabling the device does not cause the tape library to stop functioning; rather, it removes control of the device by Windows. This enables DPX to claim, detect, and control the device.

Run Detect

Use the Detect utility to validate the status of the medium changer before using the DPX Device Control Wizard. For UNIX and Linux environments, run ./bin/bexenv before running the Detect utility.

To run Detect to validate medium changer status:

1. On the Controller node, click Start > All Programs > DPX Command Prompt (Run as Administrator).

1. From the DPX command prompt, navigate to <product-directory>\bin\JB.

2. Run detect -i.

   The expected result is Device ID \\.\sync_sa# and status 0.

   If the expected result is displayed, go to step 6.

   If the expected result does not display, enable the Unknown Medium Changer and proceed to the next step.

3. Run detect -i again.

   The expected result is Device ID \\.\sync_sa# and status 0.

   If the expected result is displayed, go to step 6.

   If the expected result does not display, install the hardware manufacturer driver for the arm of the tape library. This resolves the Device ID and status of the Medium Changer. Proceed to the next step.

4. Run detect -i again.

   The expected result is Device ID \\.\Changer# and status 0.

   If the expected result is displayed, go to step 6.

   If the expected result does not display, contact Catalogic Software Data Protection Technical Support.

5. If you have not already defined your Enterprise, do it now.

6. Add controller nodes and device servers to your Enterprise.

Device Configuration Wizard

The DPX Device Configuration Wizard allows you to bypass many of the manual steps otherwise required for setting up tape libraries.

When possible, the Device Configuration Wizard generates, maps and names device drivers for each tape drive and tape library media changer. It then adds the tape libraries and tape drives to the Enterprise.

You can apply the Device Configuration Wizard to an existing installation. If you do, the Device Configuration Wizard may update those devices for which it detects a Unique ID, which is the unique identifier assigned to a device by the vendor or agency, usually the device’s serial number.

Platform Considerations

The Device Configuration Wizard is supported by any DPX client running an operating system supported for DPX device servers. An exception is Linux OES, which does not support the wizard.

Tape libraries on platforms that do not support the Device Configuration Wizard must be set up manually, using the procedures described in this instruction set.

Devices Not Auto-Configurable

You should be aware of the following caveat before executing the wizard:

The Device Configuration Wizard may set up some, but not all of the tape drives and media changers in your Enterprise. For example, a device (tape drive or media changer) might not be configurable by the wizard if DPX cannot detect a Unique ID for that device.

Any device not completely set up by the Device Configuration Wizard should be set up manually, using the procedures described in the following sections.

Executing the Device Configuration Wizard

Before executing the Device Configuration Wizard, confirm that all pre-setup steps have been completed. The Device Configuration Wizard can be run from any machine that can ping your master server. Set the environmental variable SSICMAPI so that it points to the master server.

For example:

set SSICMAPI = -a 6123

or

setenv SSICMAPI "-a 6123"

Launching the Device Configuration Wizard

To launch the Device Configuration Wizard from Windows:

• Click Start > DPX > Device Configuration Wizard

To launch the Device Configuration Wizard from UNIX:

1. Change to the bin directory under the installation directory. In addition, you may need to set the DISPLAY environment variable to your local host.

2. Enter ./devconfwizard at the shell prompt.

The Device Configuration Wizard window is launched.

The wizard asks you to log into your Enterprise. Log into the master server as an administrator. After entering your credentials, click next.

Using the Device Configuration Wizard

The Device Configuration Wizard uses an intuitive graphical user interface to guide you through the device configuration process. The wizard probes your Enterprise and detects information about your nodes, devices, tape libraries, and connections.

The following is a sample session of the Device Configuration Wizard for illustrative purposes. This sample session sets up a SAN with three heterogeneous servers and one six-drive tape library, as depicted in the following diagram:

1. The wizard displays all nodes in the Enterprise that can serve as device controller nodes.

   Use the checkboxes to select one or more controller nodes for which you want to install and configure devices.

1. Clicking the Options… button will display a dialogue box with a list of configurable scan options.

The following options can be adjusted:

• Show all the nodes

  There may be nodes on the Enterprise whose configuration options indicate they are not compatible with scanning. By default, these nodes are not displayed in the list of potential device controllers. Selecting this option will include those nodes in the list.

• Concurrent Nodes to Scan

  This setting affects how many nodes the wizard will communicate with concurrently while performing the scan. This can affect scan speed.

• NDMP Port NDMP-capable. This setting allows you to set a port number for communicating with NDMP-capable NAS nodes.

• Check here to enable Catalogic DPX LTO Encryption Option Clicking this check box will activate the Please Select pull-down menu, which you can use to enable, update or disable LTO hardware encryption functionality. The Enable/Update option enables the encryption option for nodes that support this feature or updates the list of tape devices to which the node can encrypt data.

1. Click OK to confirm your options choice.

2. Clicking the Assign Peer Nodes… button displays any other nodes that can communicate with devices in the SAN. (These nodes are not running one of the supported platforms listed at the beginning of this chapter).

3. When finished configuring options and selecting devices, click next. At this point, the wizard scans the selected node(s) for SCSI devices.

When the nodes have been successfully scanned, “Done” appears in the status column, and the next button becomes enabled. Click next to continue.

1. The wizard displays all unconfigured tape libraries accessible by the selected nodes. In this example, there is only one tape library, and it is accessible by both nodes. Select the tape library that corresponds to the server (controller node) that will control the media changer. You can either click anywhere in the entry’s row and then click the Add to Enterprise button (which becomes enabled once a selection is made), or you click the entry’s associated check box, which will advance you to the next step without the need to click Add to Enterprise

2. The wizard requests information about the tape library you selected.

Complete the active fields in the dialog:

• Configure As SAN

  This check box gives you the option to configure the device as a SAN. The check box appears if the device is seen by only one node. If multiple nodes see the device, it is automatically configured as a SAN and the check box does not appear.

• Tape Library Name

  Enter a name (up to 14 alphanumeric characters) for the tape library (for example, DEC_TL810). No two tape libraries in the Enterprise can have the same name.

• Tape Library Type

  Select the tape library type (for example, DEC_TL810) from the pull-down menu. If your tape library type is not shown, select the type that most closely matches yours.

• Controller ID

  The Device Configuration Wizard generates a media changer device file and installs it on your controller node. The name of that file, assigned by DPX, is displayed in this field.

• Data Slots

  From the pull-down menu, select the starting and ending slot numbers to use for media volumes. Note that slot numbers start at zero (0). Thus, the first slot is slot number 0, and the final slot is slot number (n-1), where n is the number of slots in your tape library.

• Cleaning Slots

  From the pull-down menu, select the starting and ending slot numbers to use for cleaning tapes. To configure a single cleaning slot (typical setup), enter the slot number twice. If no cleaning slots exist, leave these fields blank.

• Device Type

  Select a device type (for example, LTO) from the pull-down menu. All devices in a tape library must be the same type.

• Cleaning Threshold

  Enter the number of times a drive can be used before it is cleaned.

• Comment

  Optionally enter an alphanumeric string of up to 48 characters.

When you have filled in all the required information, click next.

1. The wizard displays a list of devices attached to the newly added tape library. If you need to change the device names, you can do so on this screen. Click inside the device name field and enter a new one.

2. When you are finished changing device names, click next.

3. The wizard indicates that the tape library has been added by placing a checkmark in the box in the leftmost column on the New Tape Libraries window. If you have additional tape libraries to add to the Enterprise (in this case we do not), repeat steps 3 through 5 for each.

1. Click next when you are finished adding tape libraries. The wizard shows the devices that were added, as well as other detected devices that were not part of a configurable tape library. Use this window to add additional devices, as well as to remove any of the devices added in previous steps.

2. To add additional listed devices, select a device and click Add to Enterprise, assign the device to a tape library or device pool, then specify a device name. To remove a device you have already added, select the device and click Remove from Enterprise.

1. Click Exit to exit the Device Configuration Wizard.

2. Later, when you log into the management console and navigate to the Configure Devices window, you can open the device clusters to view all the devices and device paths for a given tape drive.

You can edit the information for any of these devices in the management console under Configure Devices.

Device Detection

General Remarks

If you set up your tape library using Manual Setup (Process B), detection is the first step. The DPX Detect utility is also a handy tool for troubleshooting down the road.

The Detect utility allows you to display and map media changers and tape drives accessible from a given device server or controller node. This utility is found in the /bin/JB subdirectory of the main directory.

Detect can be run from any machine on your network under an administrative User ID.

If you are using third-party software no longer supported by the vendor, Catalogic Software Data Protection Technical Support may be limited for functions dependent on that software. To address certain issues, the Catalogic Software Data Protection Technical Support may recommend you upgrade the relevant software.

The AIX platform offers limited support, meaning that the configuration phase is not supported and the detection phase may miss some properties such as the World Wide Name or Serial Number. Other platforms offer full support meaning that the Detect utility can detect devices and obtain their vendor ID, product ID, SCSI Target, LUN, etc., plus their World Wide Name and Serial Number. Besides the detection phase, this utility can create (configure) device files.

Some versions of UNIX detect require running in a shell that has the appropriate environment setup. For details contact Catalogic Software Data Protection Technical Support.

The detect -q Utility

You can use either detect -q or detect --query. They are different formats of the same command.

As the first step to every manual tape library installation on the above platforms, you should run the following on your tape library controller node:

detect -q

detect -q gathers and displays information about media changers and tape drives that are accessible from the node on which you are running Detect. detect -q does not create or install any new devices and does not modify any files. Thus, it is always safe to run Detect with the -q command line option. The following is an example of output from detect -q:

SCSI Devices found:

------------------

Device       Adapter     Target            Device

ID           ID      BUS ID     LUN STATUS Type                     String

------------ ------- --- ------ --- ------ ------------------------ -------------

\\.\Tape0    2       0   0      2   0      Sequential Access Device SONY    SDX-500C

\\.\Tape1    2       0   0      5   0      Sequential Access Device HP      Ultrium 1

\\.\sync_sa0 2       0   1      3   0      Media Changer Device     BHTi    216

\\.\Tape2    2       0   1      1   0      Sequential Access Device QUANTUM DLT8000

Device                    Serial / Unique                                    

ID                        Number / Id              World Wide Name           Auto

------------------------- ------------------------ ------------------------- ----

\\.\Tape0                 0000902585               20 0 0 50 13 b0 78 94     Yes

\\.\Tape1                 0000911832               20 0 0 50 13 b0 78 94     Yes

\\.\sync_sa0              216B10                                             Yes

\\.\Tape2                 PXB34P3669               20 0 0 50 13 b0 78 94     Yes

Note that the output contains two tables. The rows in both tables are identified by the Device ID field. The device representing the media changer is identified by Media Changer Device or simply Medium in the Device Type field. So, in the tables above, the third row (\\.\sync_sa0) is the row representing the media changer.

The output displayed above is for a Windows platform, but the content would be similar on any platform. (For Solaris, a freshly connected tape library might not be detected by detect -q, in which case you should use detect -i as described in the next chapter). The following describes the fields (columns) in the output from detect -q, specifically with regard to the media changer device:

Note that the Detect output does not have a specific field indicating whether the device is claimed. However, if the appropriate driver does not claim a device, its name will not appear in the Device ID column and -1 will appear in the status column.

More about the Detect Utility

Install Option: Overview

Debug Option

The Detect utility also has a debug option, -d.

For all platforms listed in the introduction to this chapter, there are three debug levels: 1, 2, and 3, with level 3 being the most comprehensive. For example, you can run:

detect -d 3 -q

detect -f

The Detect utility -f N options (where N is 1, 2, 3, or 4) allow you to bypass some operations of detect -q.

• detect -f 1 processes only media changer devices.

• detect -f 2 processes only sequential access devices (tape drives).

• detect -f 3 processes media changer and sequential access devices.

• detect -f 4 processes only devices that are not changers or tape drives.

In DPX, all standard users are referred to as administrators.

Administrators are the authorized users of a DPX Enterprise. Each administrator has a password which is used for authentication.

Administrators are organized under administrator groups. Each administrator is a member of one administrator group.

Resources are assigned to administrator groups.

Privilege Classes are assigned to administrators.

SYSADMIN and SYSADMIN Administrator Group

By default, a special administrator named SYSADMIN exists, who is a member of the SYSADMIN administrator group. The SYSADMIN administrator group is always present in DPX.

All members of the SYSADMIN administrator group are special administrators and are not restricted in any way in DPX. All resources are automatically assigned to the SYSADMIN administrator group and full privileges are automatically assigned to the system administrators in the SYSADMIN group.

The SYSADMIN administrator cannot be created or deleted by a user and it is not displayed on the Configure Administrators window as a member of the SYSADMIN administrator group. The password for the SYSADMIN administrator is determined in the Administrator Password field on the Configure Enterprise window when the Enterprise is added or edited.

Resources

For administrator configuration, there are several types of resources in DPX:

• Device Clusters

• Node Groups

• Job Folders

• Tape Libraries

• Media Pools

• Administrator Groups

• Keyrings

Each resource type can be viewed as a container containing objects in DPX. When you assign a resource, you are in fact assigning all the objects contained in it. For example, if you assign a node group called Sales to an administrator group, all the nodes within Sales will be assigned to that administrator group.

When a resource is assigned to an administrator group, each member of that group can potentially access that resource. However, the access may be restricted due to each member’s privilege classes.

If a new resource (such as a node group) is created by an administrator in an administrator group, that resource is automatically assigned to that administrator group. An existing resource may be assigned to additional existing administrator groups by an administrator with the appropriate privileges.

Privilege Classes

DPX comes pre-configured with the following default privilege classes:

Note that some privilege classes overlap in their privileges, but in general, they can be viewed as corresponding to different roles that a real user of DPX may play. Thus, one or more privilege classes should be assigned to each administrator.

It is possible to configure additional privilege classes in DPX, but this is only advisable for advanced users and with the help of Professional Services.

Example Configurations

The following are example configurations based on some common scenarios.

SYSADMIN Group Only

The easiest configuration is to have only the SYSADMIN group in your Enterprise. This may be appropriate if you have a small Enterprise. All the resources are automatically assigned to the SYSADMIN group. You may assign trusted users as administrators to the SYSADMIN group.

One Administrator Group

If your Enterprise is small enough that you do not want to break up the resource assignments, but you have untrusted users, then you should configure one administrator group. This may be appropriate for small to medium enterprises where operations-level personnel needs to interact with DPX to load and unload tapes, for example.

All the resources you have configured should be assigned to one administrator group, and administrators with varying privilege classes should be created within that administrator group.

Multiple Administrator Groups

If you have a large Enterprise where you need to distinguish resources due to geography or business needs, it is best to create multiple administrator groups, each corresponding to such a distinction. A resource can be assigned to more than one administrator group, enabling selected resources to be shared among administrator groups.

Hierarchical Administrator Groups

If you have a large Enterprise where you expect to have layers of administrators for DPX, you may want to create a hierarchy of administrator groups. For example, if you want to create an administrator group that is in control of two geographically isolated administrator groups (AGx and AGy), you can create a new administrator group (AGa) with both administrator groups assigned to it. Any resource that is assigned to either AGx or AGy is automatically assigned to the members of AGa.

This update method is performed by using an ISO image along with the accompanying update script. Both files can be downloaded from the Catalogic MySupport website after logging in with your user credentials.

Typically, both files will follow the same naming convention, i.e. dpx-master.core-<core_version_no>.svc-<microservices_version_no>.infra-<insfrastructure_version_no> followed by _update.sh or -update.iso. In the examples below, for the sake of clarity, they have been renamed to 4-10_update.sh and 4-10-update.iso accordingly.

The procedure described below assumes the 4-10_update.sh and the 4-10-update.iso files are available from within the DPX Master Server machine, in the same location.

1. Log in to your DPX Master Server via SSH. The login is dpxadmin and the default password is dpxadmin. If you logged into the same Master Server in the past, you may have been forced to change the password. In such case, provide the current password, not the default one.

   Copy

   PS C:\Users\i_am_the_admin_here> ssh dpxadmin@172.20.4.110
   dpxadmin@172.20.4.110's password:
   Last login: Thu Nov 30 12:22:18 2023 from 192.168.129.143

2. Use sudo su to gain root user permissions.

3. Change permissions to the 4-10_update.sh file:

   Copy

   chmod +x <file_path>/4-10_update.sh

4. Call the 4-10_update.sh script, specifying the 4-10-update.iso image file as argument:

   Copy

    ./4-10_update.sh 4-10-update.iso

   The following prompt will appear:

   Copy

    ==> Log file is in /tmp/3615430.update.log
    
   Catalogic Software recommends that no backup or recovery jobs are running during the update process and that a full virtual machine snapshot before running the upgrade process is taken. Are no backup or recovery jobs currently running and has a snapshot been taken (Yes/No)?

5. If you have no jobs running and wish to proceed with the update process, type Yes. The update procedure will start. This process may take a long while to complete. Some progress steps will be printed in the terminal.

6. Upon completion, the installer will ask if you want to reboot your master server. Select Y to reboot the master server now or N to do it later. This ends the updating procedure. Wait for your updated DPX Master Server to reboot, then you can resume using it.

The Catalogic DPX suite encompasses additional tools designed to enhance DPX’s data protection and management capabilities. These tools include vStor, which provides efficient backup and recovery options, and GuardMode, which offers advanced ransomware detection. Both are designed to seamlessly integrate with the DPX environment to ensure a comprehensive and secure data management solution.

vStor

Catalogic vStor, developed by Catalogic Software, is a robust server designed for efficient, safe, and versatile data protection and recovery. It is intended to serve as the primary backup destination for Catalogic DPX, connecting to disk storage pools. The vStor server can be installed on either a virtual or physical appliance at any stage post-deployment of the Catalogic DPX Master Server.

Catalogic vStor servers can be deployed:

• on a physical machine

• in a VMware environment

• in a Hyper-V environment

You can use vStor both for backup and recovery, with Block and Agentless backups. For File backups, a DPX Client must be installed on the target machine.