DPX provides comprehensive backup solutions for SQL Server environments, enabling organizations to protect their critical data efficiently. With support for file-level and block-level backups, DPX ensures that your SQL Server databases are safeguarded against data loss. DPX extends its support to Microsoft SQL Server AlwaysOn Availability Groups for block-level backups, offering enhanced protection for high-availability configurations. Additionally, DPX facilitates instant availability and robust cluster support, accommodating both Active/Active and Active/Passive clusters.

Before you start your Microsoft SQL Server backup, ensure the following conditions are met:

• Ensure the DPX agent is installed on the SQL server.

• SQL Server node is visible in DPX.

• The user account used for DPX should have the necessary permissions, including SQL sysadmin privilege.

• Adequate backup storage is allocated and accessible for storing the Microsoft SQL Server backups.

Catalogic DPX delivers robust backup solutions tailored for Microsoft SharePoint Server environments, ensuring critical collaboration data is securely backed up and protected. With its support for block-level backups, DPX enables efficient safeguarding of SharePoint Server data, including support for recovery to alternate locations. DPX supports Microsoft SharePoint Server's high-availability features, including SQL Server AlwaysOn Availability Groups, ensuring continuous protection of your SharePoint environment. With farm configurations, Microsoft SQL Server can be any supported configuration, providing flexibility and compatibility with various SQL Server setups.

Before you start your Microsoft SharePoint Server backup, ensure the following conditions are met:

• Ensure the DPX agent is installed on the SharePoint server.

• Verify that the SharePoint server is properly registered within DPX.

• Adequate backup storage is allocated and accessible for storing the SharePoint Server backups.

Many database applications open their data files and leave the on-disk versions in an open, temporary, or inconsistent state until either the application synchronizes unwritten (cached) data, closes and saves the data file in use, or performs specific internal backup procedures. Similar situations can occur with applications that open and share data across a network; network-attached nodes will often cache data and not necessarily update the on-disk version until a later time. If you have backed up data from an application that was open and/or shared on the network, those files may not be usable on restore. To guarantee data consistency, it is good practice to perform cold backups or to ensure the corresponding jobs have appropriate pre-scripts. Pre-Scripts and Post-Scripts. A cold backup is a backup of any application data where the application has been closed down properly and its data backed up when the application is offline.

DPX provides a backup solution for a variety of enterprise applications, including database applications. DPX supports the following applications:

• Oracle Database

• Microsoft SQL Server

• SAP HANA

• SAP R/3

• Microsoft Exchange Server

• Microsoft SharePoint Server

• Micro Focus GroupWise

• HCL Notes and HCL Domino

Application backup in DPX functions similarly to block backup, with the system automatically detecting the application. On Windows, DPX detects SQL Server installations and other applications through registry settings and the Volume Shadow Copy Service (VSS) framework.

In the web interface, SQL Server backups are defined in the Job Manager section. In the desktop interface, block backups are implemented through a backup wizard.

Catalogic DPX offers a comprehensive backup and recovery solution for Oracle Database environments, ensuring the protection and availability of critical database information. By supporting both block-level and file-level backups, DPX facilitates efficient and reliable safeguarding of Oracle Database data, including support for Oracle Recovery Manager (RMAN) through the standard SBT API. With DPX, you can utilize Block and File Level backup and restore capabilities, including Bare Metal Recovery (BMR) and instant and full virtualization restore features.

Before initiating an Oracle Database backup with Catalogic DPX, it is crucial to ensure the following prerequisites are met:

• The DPX agent must be installed on the server hosting the Oracle Database.

• The Oracle Database must be properly registered within the DPX environment.

• Adequate backup storage should be allocated and accessible for storing the Oracle Database backups.

Catalogic DPX provides a comprehensive backup and recovery solution for SAP HANA environments, ensuring the protection and availability of critical database information. By supporting file-level backups through the Backint interface, DPX facilitates efficient and reliable safeguarding of SAP HANA data. With DPX, you can utilize file-level backup and restore capabilities, including support for SAP HANA multitenant databases and cluster configurations.

Before initiating a SAP HANA backup with Catalogic DPX, it is crucial to ensure the following prerequisites are met:

• The DPX client must be installed on the server hosting the SAP HANA database.

• The SAP HANA database must be properly registered within the DPX environment.

• Adequate backup storage should be allocated and accessible for storing the SAP HANA backups.

This chapter provides a comprehensive guide on how to perform backups for SAP HANA applications using the Catalogic DPX plugin. The Catalogic DPX plugin is easily installed and configured on the SAP HANA system using a script named dpxhdbinst. This script is available in the /opt/DPX/misc/ directory after the Catalogic DPX Client is installed on the SAP HANA system.

Prerequisites

Before running the installation and configuration script, ensure that you have the following information available from your environment:

• The hostname or IP of the DPX Master Server.

• The username of the DPX administrator account (default: dpxadmin).

• The password of the DPX administrator account (default: dpxadmin).

• The fully qualified path to the DPX root directory.

• The logical hostname of the SAP HANA node.

• The name of the DPX media pool that will be used.

• The name of the DPX device cluster that will be used as a backup target.

• The name of the DPX device that will be used as a backup target.

• The System ID (SID) of the SAP HANA database being installed and configured.

Installing and Configuring the DPX Plugin

To install and configure the DPX plugin, follow these steps:

1. Using the secure shell protocol (SSH), log in to the SAP HANA node host.

2. At the command line, navigate to the misc directory, using:

cd /opt/DPX/misc

1. Run the installation and configuration script to install the DPX plugin, using:

./dpxhdbinst

1. When prompted, enter the following information:

• The hostname or IP address of the DPX Master Server.

• The DPX administrator account username.

• The DPX administrator account password.

• The DPX root directory (default: /opt/DPX/).

1. Enter the System ID (SID) of the SAP HANA database. This will set the HDBbackint directory to /usr/sap/<xxx>/SYS/global/hdb/opt/, where <xxx> represents the SID of the SAP HANA database to be protected.

2. Proceed with installation of the DPX plugin, press 1. Installation will create a link and change permissions of three files and one directory as indicated on the screen.

3. To continue with configuration, press 2.

4. Enter the configuration information. When prompted, enter the following:

   • The logical name of the SAP HANA node.

   • The DPX tape pool to use with the SAP HANA database.

   • The DPX device pool to use with the SAP HANA database.

   • The DPX device to use with the SAP HANA database. During configuration, a template file is edited and copied to /opt/DPX/bin/dpxhdb.utl, a link is created, and the file /usr/sap/<SID>/SYS/global/hdb/custom/config/global.ini is updated, where <SID> is the System ID.

5. Press 3 to exit the script.

Configuring the SAP HANA System for Backup

To configure the SAP HANA system for backup, follow these steps:

1. Install the SAP HANA plugin for Eclipse IDE.

2. In Eclipse IDE, click Open Perspective > SAP HANA Administration Console.

3. Right-click on Systems tab and select Add system.

4. Add your SAP Hana database to Eclipse IDE, using the following settings:

   1. Host Name: Hostname of your SAP HANA machine

   2. Instance Number: SAP HANA instance number

   3. Mode: Multiple containers > System database

1. Click Next.

2. Select options:

   1. Authentication by database user and log in using username SYSTEM

   2. Enable SAP start service connection

1. Click Finish.

2. Log in to the database.

1. Double-click on Backup button.

2. Go to Configuration tab.

3. Expand section Backint Settings and change the following settings:

   • Backint Agent: /opt/DPX/bin/ssdpxhdb

   • Backint Parameter File: /usr/sap/<xxx>/SYS/global/hdb/opt/hdbconfig/dpxhdb.utl, where <xxx> represents the SID of the SAP HANA database

Running SAP HANA Backup

To perform backups, follow these steps:

1. Open Eclipse IDE and log in to the system database.

2. Right-click on the system database and select Backup and Recovery > Backup System Database.

1. Select Backint as the destination type.

2. Click Finish to start the backup.

Monitoring SAP HANA Backup Jobs in DPX

Once you created and ran SAP HANA Backup Job, you can monitor jobs using DPX:

1. In the main web interface view, go to Job Monitor in the sidebar.

2. You should see a new job with status Running, type Application Backup and Name containing the IP address of the SAP HANA node.

Backing up Oracle databases is essential for ensuring the availability and integrity of critical business data within an organization. Catalogic DPX offers a streamlined approach to backing up Oracle databases, leveraging its application-aware capabilities to facilitate the process.

Catalogic DPX delivers robust backup solutions tailored for Microsoft Exchange Server environments, ensuring critical communication data is securely backed up and protected. With its support for block-level backups, DPX enables efficient safeguarding of Exchange Server data, including support for recovery to alternate locations. DPX supports Microsoft Exchange Server's high-availability features, including Database Availability Groups (DAG) and IP-less DAG configurations, ensuring continuous protection of your Exchange environment.

Before you start your Microsoft Exchange Server backup, ensure the following conditions are met:

• Ensure the DPX agent is installed on the Exchange server.

• Verify that the Exchange server is properly registered within DPX.

• Adequate backup storage is allocated and accessible for storing the Exchange Server backups.

DPX supports backups and restores of OpenText GroupWise in a non-clustered environment. When you install a client on an OpenText Open Enterprise Server (OES) machine that GroupWise runs on, the GroupWise disks will be viewable in DPX.

The following is an extract from a File Backup window of a node that is running GroupWise 2014. This depicts a minimal GroupWise environment containing one GroupWise domain and one GroupWise post office. Additional GroupWise components would appear as additional volumes on the File Backup window. Note that the display may be different for other versions of GroupWise.

DPX supports GroupWise through the Target Service Agents (TSAs) recommended by OpenText for each OpenText and GroupWise platform. For more information on recommended TSAs and their required switches and flags, see the .

DPX supports GroupWise and OES as supported by OpenText. If you are using OpenText or Micro Focus software no longer supported by OpenText, our Technical Support assistance may be limited for functions dependent on that software. To address certain issues, the analyst may recommend you upgrade the relevant OpenText software.

For information about OpenText or GroupWise verification utilities, refer to your Micro Focus or GroupWise documentation.

GroupWise Backups and Restores – General Considerations

To define backups and restores of GroupWise components, use the web or desktop interface just as you would for any simple backup or restore.

The following capabilities apply to backup and restore of GroupWise components:

When restoring any files or components involving a GroupWise domain, including GroupWise post offices, you may need to bring down the MTAs, the POAs, the Micro Focus user interface, and Micro Focus Web Access. However, GroupWise DMS restores can occur while those agents are running.

Micro Focus Verification Utilities

To test basic backups on OES Linux, use the nbackup utility. To test the TSAFS connection on OES Linux, use the de utility. The de utility might not be included in a standard OpenText installation, but it can be acquired from OpenText.

GroupWise and DPX

GroupWise Structure

The following is a brief overview of GroupWise logical and physical layouts.

Each NDS tree in a network can have an associated GroupWise system. At a minimum, the GroupWise system has a primary domain and a post office. Like NDS, the logical framework of GroupWise is hierarchical, with GroupWise domains at the top level, post offices underneath, and libraries defined within the post offices. Further, storage areas can be created for libraries that store library documents in an area other than underneath the post office.

There is also a physical layout of a GroupWise system. GroupWise is flexible enough to allow each GroupWise system process to reside on a separate server. In most organizations, each post office has its dedicated server. Thus, a system with 3 domains, 6 post offices and 6 libraries (3 with separate storage areas) can involve 18 different servers. Additional servers may be used to house various gateway processes, but that is beyond the scope of DPX documentation (most gateways do not need to be restored, even in a disaster recovery scenario).

GroupWise services can be mixed and matched as well. For instance, on a server containing one domain and two post offices, one of the post offices may not be defined in that particular domain. However, Micro Focus strongly recommends that you run only one post office agent per server. It will be rare for more than one post office to run on a given server.

The following represents a typical GroupWise service scenario:

Usually, gateways appear under their own domains (logically) and on one server (physically).

For GroupWise resources, there is an NDS/system name for a resource, and a corresponding top-level directory. On the windows, the GroupWise resource is shown as [resource_type]directory_name: or numeric_prefix[resource_type]:, depending on GroupWise versions.

DPX supports GroupWise through the Target Service Agents (TSAs) recommended by OpenText for each GroupWise platform. As a general rule, the following TSAs support the functionality described.

• TSANDS, when running, allows the treename and Schema resources to be shown.

• TSAFS, when running, allows the server volumes to be shown.

• TSAFSGW, when running, allows GroupWise Domain and Post Office volumes to be shown. Note that TSAFSGW does not apply to GroupWise 2012 and later.

• GroupWise 2014 and GroupWise 2012 SP3 have been qualified for DPX with OES 11 SP2 x64.

Backing up Microsoft SharePoint Server is essential for preserving critical collaboration and content management data within an organization. Catalogic DPX offers a streamlined approach to backing up SharePoint Server, leveraging its application-aware capabilities to facilitate the process.

Backing up Microsoft Exchange Server is essential for ensuring the availability and integrity of email communications within an organization. Catalogic DPX offers a streamlined approach to backing up Exchange Server, leveraging its application-aware capabilities to facilitate the process.

The section below describes the scenarios for implementing DPX in a GroupWise environment.

Introduction to GroupWise Backup

Although standard file-level backups can back up GroupWise files, this method is not recommended. For such backups, from the normal directory view you would select the domain and post office directory.

Then you would define the backup as for any other file-level backup. However, standard file-level backups use the general TSA, are not GroupWise aware, and back up more data than is required. GroupWise support, on the other hand, uses the GroupWise TSA, is GroupWise aware, and backs up only the data necessary for GroupWise recoveries of accounts, users, and data.

The following sections explain how to implement GroupWise backups in Linux OES environments. The key is to ensure that TSAFSGW is running on the client node, where the source data resides. This is accomplished in two steps:

• Step 1: Load TSAFS with GroupWise functionality on Linux OES.

• Step 2: Load TSAFSGW on Linux OES. (This step does not apply to GroupWise 2012 or 2014.)

The backup scenario described below assume the following environment:

Node: oes-linux-test (this node is added to DefaultGroup) Root password: sysadmin edirectory tree: admin.abc Tree password: sysadmin GroupWise Domain Directory: oes-linux-test:/groupwise_message/ GroupWise Post Office Directory: oes-linux-test:/Post_Office/

Step 1: Load TSAFS with GroupWise functionality on Linux OES

To load TSAFS with GroupWise on Linux OES:

1. Verify that the daemon is running:

   /opt/Micro Focus/sms/bin/smsconfig –t

2. Make sure you are logged in as root.

3. Change to the directory where the SMS executables are located:

   cd /opt/Micro Focus/sms/bin

4. Stop TSAFS:

   ./smsconfig -u tsafs

5. Start TSAFS with GroupWise functionality:

   ./smsconfig -l tsafs –-EnableGW

6. Verify that TSAFS is running with GroupWise functionality:

   ./smsconfig –t

   The following is displayed:

   Copy

   The loaded TSAs are:
   tsafs –-EnableGW

7. Make GroupWise functionality the default by modifying the SMS configuration file, as follows:

   1. Change to the directory where the SMS configuration file is located:

      cd /etc/opt/Micro Focus/sms

   2. In a text editor, open the smdrd.conf file.

   3. Change autoload: tsafs to autoload: tsafs --EnableGW

   4. Save the file and exit.

8. Restart SMS services to ensure the changes made to the SMS configuration file smdrd.conf take effect:

   /etc/init.d/service Micro Focus-smdrd restart

Step 2: Load TSAFSGW on Linux OES

Because TSAFSGW depends on SMS, you use the smsconfig command in the /opt/MicroFocus/sms/bin directory with one or more home switches to specify the domains and post offices to back up. Note that this step does not apply to GroupWise 2012 or 2014.

To load TSAFSGW on Linux OES:

1. Make sure you are logged in as root.

2. Change to the directory where the SMS executables are located:

   cd /opt/Micro Focus/sms/bin

3. Use the following command to specify GroupWise locations to back up:

   ./smsconfig -l tsafsgw --home /domain_directory --home /post_office_directory

   For example:

   ./smsconfig -l tsafsgw --home /groupwise_message --home /Post_Office

4. Verify TSAs currently running:

   ./smsconfig –t

   The following is displayed:

   Copy

   The loaded TSAs are:
   tsafs –-EnableGW  
   tsafsgw --home /groupwise_message --home /Post_Office

5. Modify the SMS configuration file to establish the specified GroupWise locations as defaults for automatic backups in the future, as follows:

   1. Change to the directory where the SMS configuration file is located:

      cd /etc/opt/Micro Focus/sms

   2. In a text editor, open the smdrd.conf file.

   3. Locate the following line:

      autoload: tsafs –-EnableGW

   4. Add another line beneath it for TSAFSGW:

      autoload: tsafsgw --home /groupwise_message --home /Post_Office

   5. Save the file and exit.

   6. Restart SMS services to ensure the changes made to the SMS configuration file smdrd.conf take effect:

      /etc/init.d/service Micro Focus-smdrd restart

Running GroupWise Backups

After configuring the TSAFS with GroupWise functionality, open DPX and browse the node. You will see the following extra volumes under the node:

1[DOM]groupwise_message:  
2[PO]Post_Office:  
3[DMS]lib0001:

These volumes contain the GroupWise data that needs to be backed up. You can now select items to browse the volume and select items to back up.

To run backups of GroupWise:

1. On the desktop interface choose Backup > File.

2. Define a backup file of GroupWise volumes: 1[DOM]groupwise_message, 2[PO]Post_Office, 3[DMS]lib0001.

1. Run the saved backup job.

2. Verify the backup job.