Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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.
See also. For detailed information on compatible versions of your application and operating systems, see DPX 4.10 Compatibility Matrix.
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.
See also. For detailed information on supported SQL Server versions and operating systems, see DPX 4.10 Compatibility Matrix.
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.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Backup Job button in the upper right corner.
Specify the Job Name (this field may contain up to 16 characters). Add an optional, brief description (this field may contain up to 48 characters).
Select Job Type – Block and the Job Folder to store the job in. By default, all jobs are stored in the SS_DEFAULT folder.
Click Add Source in the SOURCES pane to specify which volumes you want to back up. DPX detects SQL Server installations through registry settings and the VSS (Volume Shadow Copy Service) framework. You will see a separate virtual object for every SQL Server database, indicating that DPX can perform application-consistent backups. Select your SQL Server and click Select.
Attention! When backing up an SQL object with DPX, all local volumes referenced by the SQL object will also be included in the backup. This may result in a larger backup size than initially anticipated.
Tip. You may view your current selection at any moment, using the Selected Items button next to the search field.
Click Set Destination in the DESTINATION pane to choose the destination for the backup.
You can also add a schedule in the SCHEDULES pane for the backup to be run regularly.
See also. For more details on scheduling options, Scheduling a Block Backup Job.
If you want to add an Archive to your backup job, click Add Archive in the ARCHIVE pane.
Select the Archive destination.
Determines whether a backup tape is stored offsite. DPX adds the Offsite status to the tape.
Toggle on
Indicates in the Catalog that the tape is stored offsite.
Toggle off
Indicates in the Catalog that the tape is stored onsite.
Determines if a backup tape with status Offsite can be appended to.
Toggle on
Tapes in the library with status Offsite can be appended to. The Append Offsite field in the Edit Media Pool dialog must also be set to Yes.
Toggle off
Tapes in the library with status Offsite cannot be appended to.
The Offsite status of a tape can be viewed through the Operate Tape Library function, the Configure Media function, or in the media volume report. Note that when you use the Operate Tape Library function to import a tape with status Offsite, the Offsite status is cleared and the tape becomes available for use.
Limits the number of storage devices valid for use with this job. Use this option if you want to stop DPX from using all the drives in the selected device cluster so that some drives will be available for other purposes.
This is an alternate location where backup data resides. This alternate location could be a replica of the original data using NetApp SnapMirror, copied through Data ONTAP commands, or restored from a tape backup. Data can be restored from an alternate secondary data source directly from the management console.
If the toggle is on, two additional drop-down selection fields are shown, requiring to specify the Alternate Secondary Node and Volume.
Add schedules for Base, Incremental, and Differential Archive backups according to your requirements.
Click Add to save the current schedule.
Multiple schedules may be added using the Add Another Schedule button which will be displayed upon adding the first schedule.
Specify Advanced Options. There are 2 SQL Server-specific options:
Tells DPX to run a consistency check on SQL Server before backing up a SQL Server database. The check runs three utilities that Microsoft recommends before a backup: DBCC CHECKDB, DBCC CHECKALLOC, and DBCC CHECKCATALOG.
Toggle on
Performs the consistency check.
Toggle off
Default option. Does not perform the consistency check.
This option controls the truncation of SQL Server Transaction Logs during a Block backup.
Attention! If you want to perform Point-in-Time restore, make sure to disable this option.
Toggle on
SQL Server transaction logs are truncated on the source database server after the backup completes. To find the backed up SQL logs, refer to the message “BACKUP LOG <database-instance> TO DISK...” in the Job Log or to Event 18265 in the Application Event Log.
Toggle off
SQL Server transaction logs are not truncated and will therefore continue to grow on the source database server. To truncate translation logs, run SQL Server maintenance on the source machine.
See also. To learn more about other available options, see Job Options for Block Backup.
Click Save.
Enter the retention period and choose whether to run the job immediately. Your job will be now available in the Job Manager section.
Go to the Backup tab.
From the Backup Modes section in the side panel, choose Block.
In the Job Tasks section of the task panel, find and click Block Backup Wizard.
The Block Backup Wizard window will appear:
By default, the creator allows you to select from the drop-down list and edit an already existing job. If you want to create a new block backup job, click the New Job button in the lower right corner.
In the Select Source screen, choose the SQL Server databases you want to include in the backup. Click Next.
In the Select Destination screen, choose the destination for the backup job. Click Next.
In the Job Options screen, define the job options for the backup job. There are 2 SQL Server-specific options available in the Application tab:
Tells DPX to run a consistency check on SQL Server before backing up a SQL Server database. The check runs three utilities that Microsoft recommends before a backup: DBCC CHECKDB, DBCC CHECKALLOC, and DBCC CHECKCATALOG.
Yes
Performs the consistency check.
No
Default option. Does not perform the consistency check.
This option controls the truncation of SQL Server Transaction Logs during a Block backup.
Attention! If you want to perform Point-in-Time restore, make sure to disable this option.
Yes
SQL Server transaction logs are truncated on the source database server after the backup is completed. To find the backed-up SQL logs, refer to the message “BACKUP LOG <database-instance> TO DISK...” in the Job Log or to Event 18265 in the Application Event Log.
No
SQL Server transaction logs are not truncated and will therefore continue to grow on the source database server. To truncate translation logs, run SQL Server maintenance on the source machine.
See also. For more information about block backup job options, see Job Options for Block Backup.
In the final Save screen, you must enter the Job Name (max. 16 characters) and specify the Job Folder to store the job in (the default folder is SS_DEFAULT). You may also add a comment to the job definition or set up a schedule (See Scheduling a Block Backup Job).
Note. If you select Cancel, the job will be saved anyway, it will not be run and the retention period will remain 90 days.
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.
See also. For detailed information on supported SharePoint Server versions and operating systems, see .
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.
See also. For detailed information on supported Exchange Server versions and operating systems, see .
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.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Backup Job button in the upper right corner.
Specify the Job Name (this field may contain up to 16 characters). Add an optional, brief description (this field may contain up to 48 characters).
Select Job Type – Block and the Job Folder to store the job in. By default, all jobs are stored in the SS_DEFAULT folder.
Click Add Source in the SOURCES pane to specify which volumes you want to back up. DPX detects Sharepoint Server installations through registry settings and the VSS (Volume Shadow Copy Service) framework. You will see a separate virtual object for the Sharepoint Server, indicating that DPX can perform application-consistent backups. Select your Sharepoint Server and click Select.
Attention! When backing up an Sharepoint object with DPX, all local volumes referenced by the object will also be included in the backup. This may result in a larger backup size than initially anticipated.
Tip. You may view your current selection at any moment, using the Selected Items button next to the search field.
Click Set Destination in the DESTINATION pane to choose the destination for the backup.
You can also add a schedule in the SCHEDULES pane for the backup to be run regularly.
If you want to add an Archive to your backup job, click Add Archive in the ARCHIVE pane.
Select the Archive destination.
Determines whether a backup tape is stored offsite. DPX adds the Offsite status to the tape.
Determines if a backup tape with status Offsite can be appended.
The Offsite status of a tape can be viewed through the Operate Tape Library function, the Configure Media function, or in the media volume report. Note that when you use the Operate Tape Library function to import a tape with status Offsite, the Offsite status is cleared and the tape becomes available for use.
Limits the number of storage devices valid for use with this job. Use this option if you want to stop DPX from using all the drives in the selected device cluster so that some drives will be available for other purposes.
This is an alternate location where backup data resides. This alternate location could be a replica of the original data using NetApp SnapMirror, copied through Data ONTAP commands, or restored from a tape backup. Data can be restored from an alternate secondary data source directly from the management console.
If the toggle is on, two additional drop-down selection fields are shown, requiring to specify the Alternate Secondary Node and Volume.
Add schedules for Base, Incremental, and Differential Archive backups according to your requirements.
Click Add to save the current schedule.
Multiple schedules may be added using the Add Another Schedule button which will be displayed upon adding the first schedule.
Specify Advanced Options.
Click Save.
Enter the retention period and choose whether to run the job immediately. Your job will be now available in the Job Manager section.
Go to the Backup tab.
From the Backup Modes section in the side panel, choose Block.
In the Job Tasks section of the task panel, find and click Block Backup Wizard.
The Block Backup Wizard window will appear:
By default, the creator allows you to select from the drop-down list and edit an already existing job. If you want to create a new block backup job, click the New Job button in the lower right corner.
In the Select Source screen, choose the Sharepoint databases you want to include in the backup. Click Next.
In the Select Destination screen, choose the destination for the backup job. Click Next.
In the Job Options screen, define the job options for the backup job.
Note. If you select Cancel, the job will be saved anyway, it will not be run and the retention period will remain 90 days.
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.
See also. For detailed information on supported Oracle Database versions and operating systems, see .
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.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Backup Job button in the upper right corner.
Specify the Job Name (this field may contain up to 16 characters). Add an optional, brief description (this field may contain up to 48 characters).
Select Job Type – Block and the Job Folder to store the job in. By default, all jobs are stored in the SS_DEFAULT folder.
Click Add Source in the SOURCES pane to specify which volumes you want to back up. DPX detects Oracle DB installations through registry settings and the VSS (Volume Shadow Copy Service) framework. You will see a separate virtual object for the Oracle DB application, indicating that DPX can perform application-consistent backups. Select your database and click Select.
Attention! When backing up an Oracle DB object with DPX, all local volumes referenced by the object will also be included in the backup. This may result in a larger backup size than initially anticipated.
Tip. You may view your current selection at any moment, using the Selected Items button next to the search field.
Click Set Destination in the DESTINATION pane to choose the destination for the backup.
You can also add a schedule in the SCHEDULES pane for the backup to be run regularly.
If you want to add an Archive to your backup job, click Add Archive in the ARCHIVE pane.
Select the Archive destination.
Determines whether a backup tape is stored offsite. DPX adds the Offsite status to the tape.
Determines if a backup tape with status Offsite can be appended.
The Offsite status of a tape can be viewed through the Operate Tape Library function, the Configure Media function, or in the media volume report. Note that when you use the Operate Tape Library function to import a tape with status Offsite, the Offsite status is cleared and the tape becomes available for use.
Limits the number of storage devices valid for use with this job. Use this option if you want to stop DPX from using all the drives in the selected device cluster so that some drives will be available for other purposes.
This is an alternate location where backup data resides. This alternate location could be a replica of the original data using NetApp SnapMirror, copied through Data ONTAP commands, or restored from a tape backup. Data can be restored from an alternate secondary data source directly from the management console.
If the toggle is on, two additional drop-down selection fields are shown, requiring to specify the Alternate Secondary Node and Volume.
Add schedules for Base, Incremental, and Differential Archive backups according to your requirements.
Click Add to save the current schedule.
Multiple schedules may be added using the Add Another Schedule button which will be displayed upon adding the first schedule.
Specify Advanced Options. There is 1 Oracle DB-specific option:
This option determines whether to synchronize the RMAN Catalog after the job completes. You have access to the following options:
Click Save.
Enter the retention period and choose whether to run the job immediately. Your job will be now available in the Job Manager section.
Go to the Backup tab.
From the Backup Modes section in the side panel, choose Block.
In the Job Tasks section of the task panel, find and click Block Backup Wizard.
The Block Backup Wizard window will appear:
By default, the creator allows you to select from the drop-down list and edit an already existing job. If you want to create a new block backup job, click the New Job button in the lower right corner.
In the Select Source screen, choose the Oracle databases you want to include in the backup. Click Next.
In the Select Destination screen, choose the destination for the backup job. Click Next.
In the Job Options screen, define the job options for the backup job. There is 1 Oracle DB-specific option available in the Application tab:
This option determines whether to synchronize the RMAN Catalog after the job completes. You have access to the following options:
Note. If you select Cancel, the job will be saved anyway, it will not be run and the retention period will remain 90 days.
Click Finish. The Final Job Run Settings dialog box will appear. You may choose to run the job immediately or save it without running. You may also change the retention period (default: 90 days).
See also. For more details on scheduling options, see .
See also. For more details on archiving options, see and .
See also. To learn more about available options, see .
See also. For more information about block backup job options, see .
In the final Save screen, you must enter the Job Name (max. 16 characters) and specify the Job Folder to store the job in (the default folder is SS_DEFAULT). You may also add a comment to the job definition or set up a schedule (See ).
Click Finish. The Final Job Run Settings dialog box will appear. You may choose to run the job immediately or save it without running. You may also change the retention period (default: 90 days).
See also. For more details on scheduling options, see .
See also. For more details on archiving options, see and .
See also. To learn more about other available options, see .
See also. For more information about block backup job options, see .
In the final Save screen, you must enter the Job Name (max. 16 characters) and specify the Job Folder to store the job in (the default folder is SS_DEFAULT). You may also add a comment to the job definition or set up a schedule (See ).
Click Finish. The Final Job Run Settings dialog box will appear. You may choose to run the job immediately or save it without running. You may also change the retention period (default: 90 days).
Toggle on
Indicates in the Catalog that the tape is stored offsite.
Toggle off
Indicates in the Catalog that the tape is stored onsite.
Toggle on
Tapes in the library with status Offsite can be appended to. The Append Offsite field in the Edit Media Pool dialog must also be set to Yes.
Toggle off
Tapes in the library with status Offsite cannot be appended to.
Toggle on
Indicates in the Catalog that the tape is stored offsite.
Toggle off
Indicates in the Catalog that the tape is stored onsite.
Toggle on
Tapes in the library with status Offsite can be appended to. The Append Offsite field in the Edit Media Pool dialog must also be set to Yes.
Toggle off
Tapes in the library with status Offsite cannot be appended to.
Toggle on
Synchronize the RMAN Catalog after the job completes.
Toggle off
Do not synchronize the RMAN Catalog after the job completes. If you choose this option, the job is not cataloged in RMAN.
Yes
Synchronize the RMAN Catalog after the job completes.
No
Do not synchronize the RMAN Catalog after the job completes. If you choose this option, the job is not cataloged in RMAN.
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.
See also. For detailed information on supported Oracle Database versions and operating systems, see DPX 4.10 Compatibility Matrix.
The section below describes the scenarios for implementing DPX in a GroupWise environment.
Note. The scenarios are for standalone nodes. GroupWise backups do not support clusters.
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/
Note. The procedures below are based on Micro Focus documentation. Since procedures may change, we recommend checking for current procedures at .
Verify that the daemon is running:
/opt/Micro Focus/sms/bin/smsconfig –t
Make sure you are logged in as root.
Change to the directory where the SMS executables are located:
cd /opt/Micro Focus/sms/bin
Stop TSAFS:
./smsconfig -u tsafs
Start TSAFS with GroupWise functionality:
./smsconfig -l tsafs –-EnableGW
Verify that TSAFS is running with GroupWise functionality:
./smsconfig –t
The following is displayed:
Make GroupWise functionality the default by modifying the SMS configuration file, as follows:
Change to the directory where the SMS configuration file is located:
cd /etc/opt/Micro Focus/sms
In a text editor, open the smdrd.conf file.
Change autoload: tsafs to autoload: tsafs --EnableGW
Save the file and exit.
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
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.
Make sure you are logged in as root.
Change to the directory where the SMS executables are located:
cd /opt/Micro Focus/sms/bin
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
Verify TSAs currently running:
./smsconfig –t
The following is displayed:
Modify the SMS configuration file to establish the specified GroupWise locations as defaults for automatic backups in the future, as follows:
Change to the directory where the SMS configuration file is located:
cd /etc/opt/Micro Focus/sms
In a text editor, open the smdrd.conf file.
Locate the following line:
autoload: tsafs –-EnableGW
Add another line beneath it for TSAFSGW:
autoload: tsafsgw --home /groupwise_message --home /Post_Office
Save the file and exit.
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
After configuring the TSAFS with GroupWise functionality, open DPX and browse the node. You will see the following extra volumes under the node:
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.
On the desktop interface choose Backup > File.
Define a backup file of GroupWise volumes: 1[DOM]groupwise_message, 2[PO]Post_Office, 3[DMS]lib0001.
Run the saved backup job.
Verify the backup job.
See also. For more information on defining file backup jobs, see .
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.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Backup Job button in the upper right corner.
Specify the Job Name (this field may contain up to 16 characters). Add an optional, brief description (this field may contain up to 48 characters).
Select Job Type – Block and the Job Folder to store the job in. By default, all jobs are stored in the SS_DEFAULT folder.
Click Add Source in the SOURCES pane to specify which volumes you want to back up. DPX detects Exchange Server installations through registry settings and the VSS (Volume Shadow Copy Service) framework. You will see a separate virtual object for the Exchange Server, indicating that DPX can perform application-consistent backups. Select your Exchange Server and click Select.
Tip. DPX supports backing up Exchange Server databases in both Active/Active and Active/Passive cluster configurations. This is particularly important for environments utilizing Database Availability Groups (DAGs) or IP-less DAG configurations, ensuring continuous protection for your data.
Attention! When backing up an Exchange object with DPX, all local volumes referenced by the object will also be included in the backup. This may result in a larger backup size than initially anticipated.
Tip. You may view your current selection at any moment, using the Selected Items button next to the search field.
Click Set Destination in the DESTINATION pane to choose the destination for the backup.
You can also add a schedule in the SCHEDULES pane for the backup to be run regularly.
See also. For more details on scheduling options, see Scheduling a Block Backup Job.
If you want to add an Archive to your backup job, click Add Archive in the ARCHIVE pane.
Select the Archive destination.
Determines whether a backup tape is stored offsite. DPX adds the Offsite status to the tape.
Toggle on
Indicates in the Catalog that the tape is stored offsite.
Toggle off
Indicates in the Catalog that the tape is stored onsite.
Determines if a backup tape with status Offsite can be appended.
Toggle on
Tapes in the library with status Offsite can be appended to. The Append Offsite field in the Edit Media Pool dialog must also be set to Yes.
Toggle off
Tapes in the library with status Offsite cannot be appended to.
The Offsite status of a tape can be viewed through the Operate Tape Library function, the Configure Media function, or in the media volume report. Note that when you use the Operate Tape Library function to import a tape with status Offsite, the Offsite status is cleared and the tape becomes available for use.
Limits the number of storage devices valid for use with this job. Use this option if you want to stop DPX from using all the drives in the selected device cluster so that some drives will be available for other purposes.
This is an alternate location where backup data resides. This alternate location could be a replica of the original data using NetApp SnapMirror, copied through Data ONTAP commands, or restored from a tape backup. Data can be restored from an alternate secondary data source directly from the management console.
If the toggle is on, two additional drop-down selection fields are shown, requiring to specify the Alternate Secondary Node and Volume.
Add schedules for Base, Incremental, and Differential Archive backups according to your requirements.
Click Add to save the current schedule.
Multiple schedules may be added using the Add Another Schedule button which will be displayed upon adding the first schedule.
Specify Advanced Options. There are 2 Exchange Server-specific options:
This option controls the truncation of Microsoft Exchange Logs during a Block backup.
Toggle on
Default option. After the backup is complete, DPX deletes the old Exchange logs.
Toggle off
DPX does not delete any Exchange logs.
Attention! If you want to perform Point-in-Time restore, make sure to disable this option.
This option is designed for use in environments where Exchange is deployed in a high-availability configuration, such as a Database Availability Group (DAG). In a DAG setup, there are multiple copies of the Exchange databases across different servers or nodes, which can be active (serving client requests) or passive (standby copies). Enabling this option reduces the resource load and potential performance impact on the active server, which is handling client requests.
See also. To learn more about other available options, see Job Options for Block Backup.
Click Save.
Enter the retention period and choose whether to run the job immediately. Your job will be now available in the Job Manager section.
Go to the Backup tab.
From the Backup Modes section in the side panel, choose Block.
In the Job Tasks section of the task panel, find and click Block Backup Wizard.
The Block Backup Wizard window will appear:
By default, the creator allows you to select from the drop-down list and edit an already existing job. If you want to create a new block backup job, click the New Job button in the lower right corner.
In the Select Source screen, choose the Exchange databases you want to include in the backup. Click Next.
In the Select Destination screen, choose the destination for the backup job. Click Next.
In the Job Options screen, define the job options for the backup job. There are 2 Exchange-specific options available in the Application tab:
This option controls the truncation of Microsoft Exchange Logs during a Block backup.
Yes
Default option. After the backup is complete, DPX deletes the old Exchange logs.
No
DPX does not delete any Exchange logs.
Attention! If you want to perform a Point-in-Time restore, make sure to disable this option.
This option is designed for use in environments where Exchange is deployed in a high-availability configuration, such as a Database Availability Group (DAG). In a DAG setup, there are multiple copies of the Exchange databases across different servers or nodes, which can be active (serving client requests) or passive (standby copies). Enabling this option reduces the resource load and potential performance impact on the active server, which is handling client requests.
See also. For more information about block backup job options, see Job Options for Block Backup.
In the final Save screen, you must enter the Job Name (max. 16 characters) and specify the Job Folder to store the job in (the default folder is SS_DEFAULT). You may also add a comment to the job definition or set up a schedule (See Scheduling a Block Backup Job).
Note. If you select Cancel, the job will be saved anyway, it will not be run and the retention period will remain 90 days.
Click Finish. The Final Job Run Settings dialog box will appear. You may choose to run the job immediately or save it without running. You may also change the retention period (default: 90 days).
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.
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.
To install and configure the DPX plugin, follow these steps:
Using the secure shell protocol (SSH), log in to the SAP HANA node host.
At the command line, navigate to the misc directory, using:
Run the installation and configuration script to install the DPX plugin, using:
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/).
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.
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.
To continue with configuration, press 2.
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.
Press 3 to exit the script.
To configure the SAP HANA system for backup, follow these steps:
In Eclipse IDE, click Open Perspective > SAP HANA Administration Console.
Right-click on Systems tab and select Add system.
Add your SAP Hana database to Eclipse IDE, using the following settings:
Host Name: Hostname of your SAP HANA machine
Instance Number: SAP HANA instance number
Mode: Multiple containers > System database
Click Next.
Select options:
Authentication by database user and log in using username SYSTEM
Enable SAP start service connection
Click Finish.
Log in to the database.
Double-click on Backup button.
Go to Configuration tab.
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
To perform backups, follow these steps:
Open Eclipse IDE and log in to the system database.
Right-click on the system database and select Backup and Recovery > Backup System Database.
Select Backint as the destination type.
Click Finish to start the backup.
Note. The backup log is located in the /opt/DPX/bin/dpxhdb.utl file. Make sure the backup log is the same as the one specified in the dpxhdb.utl file.
Once you created and ran SAP HANA Backup Job, you can monitor jobs using DPX:
In the main web interface view, go to Job Monitor in the sidebar.
You should see a new job with status Running, type Application Backup and Name containing the IP address of the SAP HANA node.
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 GroupWise Administration Guide.
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.
To define backups and restores of GroupWise components, use the web or desktop interface just as you would for any simple backup or restore.
Domain (DOM)
DPX has the ability to back up the entire GroupWise domain structure. DPX can restore entire domains or individual files to their original location or to an alternate location.
Post Offices (PO)
DPX can back up entire post offices or individual files within a post office. DPX can restore entire post offices or individual files to their original location or to an alternate location.
Documentation Management Services (DMS)
DPX can perform backups at the library level or at the file level. DPX can restore entire libraries or individual files to their original location or to an alternate location.
Binary Large Object (BLB)
Binary large objects (blobs) are the database structures for storing message attachments and DMS documents. Binary large objects may be stored separately from the post office. DPX can perform backups of GroupWise binary large objects and can restore entire binary large objects to their original location or to an alternate location.
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.
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.
The information in the remainder of this chapter assumes the reader has a strong grasp of OpenText GroupWise, including post offices, domains, libraries, and storage areas. A list of files needed for complete backup of these components can be found in the GroupWise Administration Guide available at http://www.Micro Focus.com/documentation. The reader is also assumed to have an understanding of GroupWise startup files.
Note. The discussions in the remainder of this chapter reflect GroupWise 7.0. They may be different in some details from other versions of GroupWise.
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:
GWServer1
GWDom1 and GWDom2
GWServer2
GWPO1
GWServer3
GWPO2
GWServer4
GWPO3
GWServer5
GWPO4
GWServer6
Storage areas for GWPO4 Library2
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.
Install the .
