DPX offers a comprehensive restore solution for a variety of enterprise applications, ensuring that critical data and services can be quickly and effectively recovered in the event of data loss or system failure. DPX supports the restoration of 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
DPX can intelligently identify and restore application data to its original state or to a new location as required. This includes the ability to perform point-in-time restores, ensuring that applications can be rolled back to a specific moment before a data corruption or loss event occurs.
See also. For detailed information on compatible versions of your application and operating systems, see DPX 4.10 Compatibility Matrix.
This restore mode allows the restoration of Microsoft SQL Server databases from backups created with DPX. The restore process is designed to be flexible, allowing for the recovery of selected databases to their original location or a new one. With DPX, you can also perform point-in-time restores, leveraging SQL Server's transaction logs to recover databases to a specific moment before an incident occurred.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Restore Job button.
Select Application Restore and Click Next.
The Object to Restore view shows all Application nodes that you backed up. The available objects to restore can be sorted by Name, Type, associated Job Name, or the backup Date/Time. Find the Node that contains the SQL Server you want to restore and click Next.
Tip. Restoring a SQL object will include all local volumes referenced by the SQL object, potentially increasing the restore size.
Choose the appropriate recovery point from the available backups of the selected node.
In the File Browsing step, choose the specific databases you wish to restore. DPX allows for granular selection, enabling you to restore individual databases. Select all databases you want to restore and click Next.
In the Options step, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.
Specify job options. You can use the following options:
When this option is enabled, DPX will overwrite an existing database without performing the usual SQL Server pre-restore tests. This can be useful when you are certain that the restore should proceed, but it bypasses SQL Server's built-in safety checks, so use it with caution1.
This option allows you to restore the database to a different location than the original. It's essential when the original location is not available or when you want to restore the database for testing purposes.
If you're restoring the database to a new location and want to specify a different location for the transaction logs, use this option. This is particularly useful for separating data files from log files1.
This option enables you to restore the database to a specific point in time, using the transaction logs. Ensure that the necessary transaction log backups are available for the point in time you wish to restore to.
See also. To learn more about other available options, see Advanced Job Options.
Click Next. Review the summary of your job and click Save. You will see the Run Job prompt.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager.
Restoring a SAP HANA database is crucial for recovering data after an incident, ensuring the continuity and integrity of business operations. Catalogic DPX offers a flexible and efficient approach to SAP HANA database restores, supporting various recovery options to meet your specific needs.
To restore the SAP HANA database, follow these steps:
Open Eclipse IDE and log in to the system database.
Right-click on the system database and select Backup and Recovery > Recover Tenant Database (or Recover System Database).
Specify the tenant database to restore. Click Next.
Specify the recovery type. You can choose from:
Recover the database to its most recent state: This option restores the database to its most recent state, using the latest available backup.
Recover the database to the following point in time: This option restores the database to a specific point in time, allowing you to recover data up to a specific moment.
Recover the database to a specific data backup: This option restores the database to a specific backup, allowing you to recover data from a specific backup point.
Specify the location of the backup catalog. Make sure Recover using the backup catalog and Search for the backup catalog in Backint only are checked. Click Next.
If the database is running, you will receive a prompt to stop it. Click OK to proceed with stopping the database.
Select the backup to use for the restore. Click Next.
In the Other Settings step, make sure to tick Third-Party Backup Tool (Backint). This setting is crucial for enabling DPX to work. Click Next.
Review your settings to ensure everything is correct. Click Finish to start the restore process.
To monitor the restore job, follow these steps:
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.
Let me know if this is accurate and meets your requirements.
This restore mode allows the restoration of Microsoft SharePoint Server data from backups created with DPX. The process is designed to be flexible, enabling the recovery of entire SharePoint farms, individual site collections, or specific items to their original location or a new one.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Restore Job button.
Select Application Restore and Click Next.
The Object to Restore view shows all Application nodes that you backed up. The available objects to restore can be sorted by Name, Type, associated Job Name, or the backup Date/Time. Locate and select the node containing the Sharepoint Server you want to restore and click Next.
Tip. Restoring a Sharepoint object will include all local volumes referenced by the object, potentially increasing the restore size.
Choose the appropriate recovery point from the available backups of the selected node.
In the File Browsing step, choose the specific databases you wish to restore. DPX allows for granular selection, enabling you to restore individual databases. Select all databases you want to restore and click Next.
In the Options step, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.
Specify job options. You can use the following options:
Note. If restoring multiple content databases for the same web application, select them together when choosing to Create Web Application.
This option lets you configure how the restore job handles the SharePoint web application. You can choose from the following options:
Attention! The create operation will fail if a web application with the same settings already exists in the farm.
See also. To learn more about other available options, see Advanced Job Options.
Click Next. Review the summary of your job and click Save. You will see the Run Job prompt.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager.
Restoring an Oracle database is crucial for recovering data after an incident, ensuring the continuity and integrity of business operations. Catalogic DPX offers a flexible and efficient approach to Oracle database restores, supporting various recovery options to meet your specific needs.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Restore Job button.
Select Application Restore and Click Next.
The Object to Restore view shows all Application nodes that you backed up. The available objects to restore can be sorted by Name, Type, associated Job Name, or the backup Date/Time. Locate and select the node containing the Oracle DB you want to restore and click Next.
Tip. Restoring an Oracle DB object will include all local volumes referenced by the object, potentially increasing the restore size.
Choose the appropriate recovery point from the available backups of the selected node.
In the File Browsing step, choose the specific databases you wish to restore. DPX allows for granular selection, enabling you to restore individual databases. Select all databases you want to restore and click Next.
When browsing the file tree of a block backup for Oracle DB, you will see two separate directories: Physical View and Logical View. The physical view represents the actual physical implementation of the database on the storage system, while the logical view provides a structured representation of the database objects and their relationships.
In the Options step, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.
Specify job options. You can use the following options:
When performing Oracle logical view restores, you can choose from the following modes:
Specify a complete directory path to be used as the root directory for all mappings during a Quick Restore for Oracle. If this value is not set, it defaults to:
For Windows: product-directory/mount/BEXrmancat_jobid/nodename/dbname
For UNIX: /tmp/BEXrmancat_jobid/nodename/dbname
This option is used when cloning Oracle databases. Specify the Oracle_Home on the target node where the cloned database will reside.
When cloning Oracle databases on a UNIX target node, supply the user name of the owner of the Oracle installation on the restore destination node. If this field is not populated, the default value oracle will be used.
For cloning Oracle databases on a Windows target node, provide a password to create an Oracle instance on the target node. If this field is not populated, the default value sysadmin is used.
Note. The Oracle Instance Password may appear in clear text in certain files and modules. Once cloning is complete, the password must be changed by the user.
This option is used with the cloning of Oracle databases. It allows you to control whether the cloned Oracle database should be opened and in what mode. The available options are:
See also. To learn more about other available options, see Advanced Job Options.
Click Next. Review the summary of your job and click Save. You will see the Run Job prompt.
Click Yes to run the job immediately, or No if you want to run it later from the Job Manager.
Toggle on
The restore job defined in this process will be deleted upon successful completion. If the job fails, it will not be deleted.
Toggle off
The restore job will be saved and will be accessible later in Job Manager.
Toggle on
The notification is sent as specified below the toggle (additional fields will appear – see below).
Toggle off
The notification is sent to the default e-mail address configured in the Administrator E-mail Settings section.
Toggle on
The restore job defined in this process will be deleted upon successful completion. If the job fails, it will not be deleted.
Toggle off
The restore job will be saved and will be accessible later in Job Manager.
Toggle on
The notification is sent as specified below the toggle (additional fields will appear – see below).
Toggle off
The notification is sent to the default e-mail address configured in the Administrator E-mail Settings section.
Do Not Create Web Application
Restores the content database only, without creating or modifying the web application. This is the default setting.
Create Web Application
After restoring the content database, DPX will create a new web application using the original name and port number. If supported, it will attempt global provisioning. The application pool will be selected by SharePoint. You may need to reconfigure settings like the application pool after restore.
Delete and Create Web Application
Deletes any existing web application before creating a new one during the restore process. Use this if you encountered a "Failure to create web application" error previously.
Toggle on
The restore job defined in this process will be deleted upon successful completion. If the job fails, it will not be deleted.
Toggle off
The restore job will be saved and will be accessible later in Job Manager.
Toggle on
The notification is sent as specified below the toggle (additional fields will appear – see below).
Toggle off
The notification is sent to the default e-mail address configured in the Administrator E-mail Settings section.
Regular
This is the default mode. It performs a standard logical view restore.
Clone Database
This mode performs a cloning operation, recovering your backed-up data on an alternate node using Instant Access.
Quick Restore
This mode performs an Instant Access mapping to your backed-up data, allowing for rapid access and recovery.
Open Reset Logs
This is the default setting. Opens the Oracle database with the resetlogs option.
Open Read Only
Opens the Oracle database in read-only mode.
Do Not Open
Does not open the Oracle database, which can be useful if further recovery is needed.
This restore mode allows the restoration of Microsoft Exchange Server databases from backups created with DPX. The process is designed to be adaptable, allowing for the recovery of entire databases or individual mailboxes to their original location or a new one. DPX also supports point-in-time restores, leveraging Exchange Server's transaction logs to recover data to a specific moment before an incident occurred.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Restore Job button.
Select Application Restore and Click Next.
The Object to Restore view shows all Application nodes that you backed up. The available objects to restore can be sorted by Name, Type, associated Job Name, or the backup Date/Time. Locate and select the node containing the Exchange Server you want to restore and click Next.
Tip. Restoring an Exchange object will include all local volumes referenced by the object, potentially increasing the restore size.
Choose the appropriate recovery point from the available backups of the selected node.
In the File Browsing step, choose the specific databases you wish to restore. DPX allows for granular selection, enabling you to restore individual databases. Select all databases you want to restore and click Next.
In the Options step, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.
Specify job options. You can use the following options:
Enable this option to ensure the database is restored to its exact state at the backup time. DPX will clear existing transaction logs before the restore, preventing any post-backup changes from affecting the recovery.
Select from three choices to manage the restored database:
Commit Restore and Mount Database: Automatically commits and mounts the database, making it immediately accessible.
Commit Restore Only: Commits the restore but requires manual mounting of the database, allowing for additional checks.
Do Not Commit Restore: Restores data without committing, ideal for reviewing or validating data before it goes live.
Click Next. Review the summary of your job and click Save. You will see the Run Job prompt.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager.
Note. DPX emailing must be enabled when you first configure your Enterprise. At that time, you supply general system information, including SMTP Host Name and SMTP Port. See the section.
See also. To learn more about other available options, see .
Toggle on | The restore job defined in this process will be deleted upon successful completion. If the job fails, it will not be deleted. |
Toggle off | The restore job will be saved and will be accessible later in Job Manager. |
Toggle on | The notification is sent as specified below the toggle (additional fields will appear – see below). |
Toggle off |
The notification is sent to the default e-mail address configured in the section.
