Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Restores require a vMotion license and fully licensed ESXi host.
A backup of a VM with multiple disks succeeds and is cataloged if at least one disk is successfully backed up. When the VM is restored it may not be restored with all the disks present at the time of the backup; only the successfully backed up disks are restored. In this case, a warning message appears in the job log for each missing disk.
You can restore individual VMDKs. To restore a VM with multiple VMDKs, perform a restore for each VMDK.
For a VM restore, you can select an ESXi server as a restore target. However, for a VMDK restore, select an existing VM as the restore target.
Agentless VMware Backup does not currently support application-aware backup and recovery; however, it provides application consistent backups. Application-aware backup and recovery is accomplished through DPX Block Data Protection, which requires an agent in the VM that is backed up.
The most recent backup snapshot is identified in the restore tree as LATEST. This unique label enables you to define restore jobs that always restore from the most recent agentless snapshot. This is useful for maintaining disaster recovery environments and for backup verification.
LATEST snapshots are indicated for Instant VM Restore and Full VM Restore.
In the case of different backup jobs protecting the same VM, the LATEST snapshot is the most recent in the Catalog, regardless of the backup job that generated the snapshot.
For Instant VM or VMDK restore, no datastore selection is required.
For full VM or VMDK restore, if you restore to Original Location, no datastore selection is required. However, if you restore to a new location, you must select a datastore.
A temporary VMFS datastore is automatically created during the restore to store the VM, VMDKs, or both. The size of the datastore is equal to the VM memory plus 10 percent of total size of VMDKs. The temporary VMFS datastore is deleted automatically when the job completes.
Both VMFS and NFS datastores are supported.
To remove fully restored VMs and VMDKs, use vSphere Client.
VMware Virtual Volume (VVol) datastores are not supported with Agentless VMware backup to DPX Open Storage Server.
The VMDK is attached to the VM as an RDM LUN.
You can restore VMDKs to a VM that is running; that is, there is no need to power off the VM. However, in such cases DPX may use the cloning method, and you are not able to use the VM until the cloning completes.
DPX creates a unique disk name for the VMDK to be restored, restores the VMDK to the target datastore, and attaches it to the target VM.
For VMs running Windows, if the target machine is different than the source machine, the disk may appear as offline and you need to make it online. The offline condition does not appear if you restore to the original machine with Check this option to delete the virtual machine if it exists on the target host selected.
For VMs running older versions of Windows, drive letters may be automatically assigned to VMDK volumes if the Windows automount option is turned on. Otherwise, to access the volume data, manually assign a drive letter. To access data for multiple disk partitions, assign a drive letter to each partition.
For VMs running Linux, mount the VMDK via operating system partitioning tools.
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.
Instant Virtualization maps data from the snapshot (stored on the secondary) to the VM. Unlike Full Virtualization, Instant Virtualization does not physically transfer data to the VM and therefore requires minimal space on the datastore, and changes made to the mapped drive do not affect the backups.
All the source volumes will be virtualized as RDM disks, based on the snapshot image from the secondary storage system.
Important. VMs created with Instant Virtualization are considered temporary since they depend on snapshots that can expire or be deleted. Such temporary VMs may also run slower due to network communication constraints. Once a temporary machine is ready for production, it can be made available quickly by using RRP.
Restrictions. The Rapid Return to Production (RRP) functionality is currently only available through the desktop interface. See Rapid Return to Production (RRP).
See also. See the prerequisites before restoring your VMware assets that you backed up by using Catalogic DPX Agentless Backup: Restore Considerations for Agentless VMware Backup. In addition to virtual machines, you can also restore specific files or directories in them. For more details about restoring files, see Agentless File Restore.
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Instant VM Restore and click Next.
The VM object list shows all VMs that you backed up by using the DPX Agentless Backup. The available objects to restore can be sorted by Name, Type, associated Job Name, the Backup Date/Time, or by Size. Find the VM you want to restore. Click Next.
In the Recovery Points step, select the recovery point to restore. You can select the Latest Recovery Point or either one of the other recovery points in the list. 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 using toggles. See below.
Optionally, you can specify other job options (see below). If you wish to continue with default options, click Save.
You can create the VM in a location that is different from the location in which the source virtual machine exists. Select the Enterprise, VMware node, VMware ESXi host, VMware vCenter, and VMware folders in the navigation pane, and select the virtual machine. Review or change the Virtual Resources items (see below).
Select Node Name from the drop-down list.
Select a Host available within the Node from the drop-down list.
DPX will attempt connecting to the vCenter under the node name specified. Selections available in the following sections are imported from the vCenter.
Select Resource Pool or VApp.
Select the network you want to locate the new VM in.
Select the iSCSI Adapter.
Select the VM Folder where the new VM will be restored to.
Schedule the restore job. The time field is using your browser’s time zone. For example, if you have DPX in London and access the DPX web interface from New York, specify the time in US Eastern Time.
Important. When specifying a schedule, make sure the Delete the restore job on successful completion toggle is switched off. Otherwise, the job will be deleted upon its first successful completion.
Also please note that in the current version of DPX, restore jobs cannot be edited. This also includes job scheduling.
Click Save. A Run Job prompt will be shown.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager.
Warning! There is a file size limit for Agentless File Restore due to browser limitations. The maximum file size you can download is 2 GB or less, depending on your machine’s available RAM. You will encounter an error when attempting to download files that exceed this limit.
After backing up VMware or Microsoft Hyper-V virtual machines using the Catalogic DPX Agentless Backup, you can restore specific files or directories in these VMs.
See also. For an overview, see instructions about setup or backing up VMs by using the DPX Agentless Backup, see the following sections:
Ensure that your systems satisfy the following prerequisites when you plan to back up and restore files by using the DPX Agentless Backup:
The DPX master server must be version 4.8.0 or later.
The backup target storage must be Catalogic vStor 4.8.0 or later.
You cannot use the backup source storage formatted in Microsoft Resilient File System (ReFS).
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see the DPX 4.10 .
You can select files or directories in a VM backup snapshot, and download an archive file in .zip format that contains these restored files.
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Agentless File Restore and click Next.
The VM object list shows all VMs you backed up using the DPX Agentless Backup. The available objects to restore can be sorted by Name, Type, associated Job Name, the backup Date/Time, or by Size. Find the VM that contains the files or directories in the VM object list you want to restore. Click Next.
From the list of recovery points of the VM object, select the recovery point that contains the files or directories to restore. Click Next.
Click Mount Image. After DPX mounts the image, you can see the text label, Image Mounted, and click Next.
Tip. Mounting an image may take a few minutes to complete. If Catalogic DPX fails to mount the image, click Show Details, see the log messages, and troubleshoot.
In the File Browsing step, You can browse the partitions in the VM that you selected, as well as directories and child directories in the navigation tree. Select directories or files to restore in the main pane. Or, you can use the search field to search files or directories in the VM.
Click Restore to download the files that you selected. A dialog with a progress bar will appear.
When the download is finished, you will find the selected files or the .zip archive in your browser’s default download folder.
Tip. If you select multiple files to restore, you can download an archive file in .zip format that contains all files to restore.
Use the Absolute option to keep the original directory structure in the archive file.
Or use the Relative option to store all files in the root directory of the archive file.
For example, assume that you are restoring the file in your Linux system: /home/dee/invoice.txt and /home/cate/flower.jpg in Partition 2. With the Absolute option, the archive file includes these two files with the nested directories: disk2/dev.sda1/home/dee/invoice.txt and disk2/dev.sda1/home/cate/flower.jpg. With the Relative option, invoice.txt and flower.jpg are stored in the root directory of the archive file without making any child directories in it.
Close the file restore dialog using the “X” symbol in the upper right corner. You will be prompted to either keep the recovery point mounted until the expiration time or clean up right away.
You can select either to keep the mounted image for the recovery point until the expiration time or to remove the image immediately. If you select Keep, the recovery point will remain available from the Dashboard widget until it expires.
If you cannot see your Agentless File Restore mounting point, click Scan to refresh the view (item 1 below).
Within the expiry time, if you need to restore any other files or directories, click Browse next to the mounted image (item 2 below).
Note.
When a mounting point is not needed anymore, you can wait until it expires or click “X” to unmount it instantly (item 3 below).
Note. The mounted image’s default expiry time is 120 minutes. This setting depends on the vStor where the VM backup is stored and can be changed in the vStor’s System Settings.
Whenever you browse the mounted image, the expiry time is reset and the c
See also. See General Settings in vStor 4.10 Documentation.
Virtualization is the process of restoring Block backups by creating a separate virtual machine with the restored data. Such restore process requires BMR backups. The virtualization itself may be instant or full. Full Virtualization creates a production VM. Instant Virtualization creates a temporary VM, which is typically used for setup or testing purposes. In addition, you can convert the temporary VM that were created with Instant Virtualization into a production VM by using the Rapid Return to Production (RRP) feature.
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Virtualization and click Next.
The Object to Restore list shows all machines backed up using the DPX BMR Backup. The available objects can be sorted Name, Type, associated Job Name, or Backup Date/Size. Find the VM that contains the files or directories in the VM object list you want to restore. Click Next.
From the list of recovery points of the VM object, select the desired recovery point. By default, Latest Recovery Point is selected. Click Next.
Note. Both Instant and Full virtualization are based on a very similar flow, where a virtual machine is created within the specified location. The difference consists in how the VM will access the backup data:
Instant Virtualization – the BMR backup from vStor is mapped to the VM as an external volume; this method is intended for temporary access only due to potentially high latency;
Full Virtualization – the BMR backup from vStor is transferred to the VM’s internal volume; this method is fully reliable and the VM can be used in the production environment.
Specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.
Restrictions. The Job Name must be unique within your Enterprise.
Specify job options using toggles. See below.
Optionally, you can specify an Alternate Secondary Node.
Specify the Target Host, selecting Node Name and the Host available within this Node from respective drop-down lists.
Select the Target Resources for the new VM.
Select Resource Pool or VApp.
Select the network you want to use to connect to the new VM.
Select the iSCSI Adapter.
Select the VM Folder where the new VM will be located within the virtual machine manager.
Select Target Datastore. Use the Search input field or select one of the available datastores from the list.
Tip. You can control the Datastore view by ordering items by Name, Status, overall Capacity, Free space or Type, ascending or descending. Note also the Items per page value which can be useful when managing the display.
Specify the properties of the new virtual machine.
The Virtual Machine Name cannot exceed 256 characters and must be unique within the virtual machine manager.
Assign Virtual Machine Memory. You also need to specify whether the memory is thin-provisioned (only actually consumed memory is used by the VM) or thick-provisioned (the allocated amount of memory will be reserved for the VM’s exclusive use).
Select the virtualization proxy server. For more information, see DPX Proxy Server.
Indicate the Virtual ISO Location. You will need a virtualization ISO of the operating system required for your machine (Linux or Windows). Normally, you will obtain it from the appropriate MySupport DPX Virtualization Support section. If in doubt, contact our Technical Support team.
(Optional) By default, the Static Virtual Machine Network toggle is in the disabled position. When enabled, additional fields are shown.
Specify the static IP address for the machine.
Specify the subnet mask.
Specify the gateway.
Specify the DNS server. Additionally, you may specify the DNS search path. This field is optional.
After setting all the options, click Next. The Summary screen will be displayed.
Click Save. A Run Job prompt will be shown.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager. After a successful job run, the restored virtual machine will be visible in the vCenter:
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.
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.
This restore mode is used to restore files that were backed up using block backup. DPX displays your logical Enterprise tree structure. You can select and restore single or multiple files or directories protected by DPX agent workloads at the node group, node, drive, directory, or file level.
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Agent-Based File Restore and Click Next.
The Object to Restore view shows all nodes that you backed up using DPX Block Backup. 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 files or directories you want to restore. Click Next.
From the list of volumes within the object, select the volume that contains the files or directories to restore. Click Next.
In the File Browsing step, select either the entire Volume or specific files. If you select Files, the file manager will appear, allowing you to select specific files for restore; click the volume label in the left-hand pane to display items within the volume. Select all desired files or directories 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 using toggles. See below.
Optionally, you can specify other job options (see Advanced Job Options). If you wish to continue with default options, click Save. A Run Job prompt will be shown.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager.
By default, DPX will restore the files or volumes specified in the File Browsing step to their original location. You may override this setting by indicating a directory on the same or another node.
Specify the Node Name. This may be the same node the data were backed up from, or another machine.
Restrictions. Agent-Based File Restore only handles alternate destinations with similar operating systems. E.g. restoring Linux files on a Windows node or vice versa is not supported.
In all previous steps of creating a restore job, the available selections were based on the backup metadata stored on DPX. This means that DPX is aware of all backups made by the user and where they are stored. If, during backup or at a later stage, the backup data have been replicated to a secondary location and the primary location becomes corrupt or inaccessible, you can choose to restore your data from such secondary location using this option.
Select the Secondary Node from the drop-down list.
Select the volume where the alternate backup is stored.
DPX will attempt to identify the files or directories specified in previous steps. If this proves impossible, the following warning will be displayed:
See also. For more information, see Creating vStor Partnerships in vStor documentation.
Schedule the restore job. The time field is using your browser’s time zone. For example, if you have DPX in London and access the DPX web interface from New York, specify the time in US Eastern Time.
Important. When specifying a schedule, make sure the Delete the restore job on successful completion toggle is switched off. Otherwise, the job will be deleted upon its first successful completion.
Also please note that in the current version of DPX, restore jobs cannot be edited. This also includes job scheduling.
As with backup jobs, you can add script options for this restore job.
Enter the name of a script to execute prior to the actual job.
Basic usage: <script>@<node_name> <argument_list>
The action be taken if the Pre-Job Script fails to successfully complete:
Run Job/Run Post-Job Script
Skip Job/Run Post-Job Script
Skip Job/Skip Post-Job Script
The action to be taken if the Job fails to successfully complete:
Run Post-Job Script
Skip Post-Job Script
Enter the name of a script to execute after the actual job.
Basic usage: <script>@<node_name> <argument_list>
See also. For detailed information about pre- and post-job scripts, including all valid definitions, see Pre-Scripts and Post-Scripts.
Controls the routing of NDMP server-generated log messages to the job log file.
This option only takes effect when you restore an entire SnapVault filer-to-filer backup instance to its original location.
This option comes into play if a job does not get an indication of “active” status during the data transfer phase of the job. Catalogic DPX initiates job cancellation after this interval, specified in minutes, has lapsed.
Tells DPX how to behave if it finds a file at the destination with the same name as the file that it is restoring.
Controls how DPX behaves if it tries to restore a file to a directory and discovers that the directory does not exist
If the Enterprise has more than one domain controller, you can choose whether to replicate SYSVOL files and folders to the other controllers as part of the Windows 2000+ System State restore.
Attention! When there are replication partners, selecting Authoritative Restore can result in unexpected behavior. For more information, see Creating vStor Partnerships in vStor documentation.
To perform an authoritative restore on the Active Directory, you must run the Microsoft Ntdsutil utility after you have restored the System State data but before you restart the domain controller. For more information about the Ntdsutil utility and authoritative restore, refer to your Microsoft documentation.
If your Enterprise contains clusters, you can choose whether to restore the cluster quorums as part of the Windows 2000+ System State restore.
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.
Full Virtualization for VMware creates a new VM that contains a duplicate of the original server. Each partition of the snapshot is physically transferred to its disk volume on the new VM during virtualization. In other words, Full Virtualization creates a virtual disk with the same layout as the corresponding disk of the backed-up source machine and populates it with the backed-up data. This method is often used to create permanent VMs that can be put into production.
Tip. All the source disks will be created as .vmdk files on the specified datastore, based on the snapshot image from the secondary storage system.
See also. See the prerequisites before restoring your VMware assets that you backed up by using Catalogic DPX Agentless Backup: Restore Considerations for Agentless VMware Backup. In addition to virtual machines, you can also restore specific files or directories in them. For more details about restoring files, see Agentless File Restore.
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Full VM Restore and click Next.
The VM object list shows all VMs that you backed up by using the DPX Agentless Backup. The available objects to restore can be sorted by Name, Type, associated Job Name, the Backup Date/Time, or Size. Find the VM you want to restore. Alternatively, select Latest Recovery Point. Click Next.
In the Recovery Points pane, select the recovery point to restore. You can select the Latest Recovery Point or either one of the other recovery points in the list. The available recovery points can be sorted by Backup Date/Time, Job Name, or Secondary Node. Click Next.
In the Options pane, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.
Specify job options using toggles. See below.
Optionally, you can specify other job options (see below). If you wish to continue with default options, click Save.
You can create the VM in a location that is different from the location in which the source virtual machine exists. Select the Enterprise, VMware node, VMware ESXi host, VMware vCenter, and VMware folders in the navigation pane, and select the virtual machine. Review or change the Virtual Resources items (see below).
Select the Node Name from the drop-down list.
Select a Host available within the Node from the drop-down list.
DPX will attempt connecting to the vCenter under the node name specified. Selections available in the following sections are imported from the vCenter.
Select Resource Pool or VApp.
Select the network you want to locate the new VM in.
Select the iSCSI Adapter.
Select the VM Folder the new VM will be restored to.
Schedule the restore job. The time field is using your browser’s time zone. For example, if you have DPX in London and access the DPX web interface from New York, specify the time in US Eastern Time.
Important. When specifying a schedule, make sure the Delete the restore job on successful completion toggle is switched off. Otherwise, the job will be deleted upon its first successful completion.
Also please note that in the current version of DPX, restore jobs cannot be edited. This also includes job scheduling.
Click Save. A Run Job prompt will be shown.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager. After a successful job run, the restored virtual machine will be visible in the vCenter:
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 feature provides instant writable access to data and application recovery points. A DPX Block Data Protection snapshot is mapped as a network disk to a target client node where it can be accessed, copied, or put immediately into production use as needed. The recovery point itself is not affected by any changes made on the network disk.
Once Instant Access is activated, backup instances appear as local, fully accessible (read/write) drives. For quick recovery of individual files, users can easily copy from an Instant Access drive to another drive on the local node. However, Instant Access can be used in more sophisticated ways as part of a recovery strategy:
Files on the secondary are transparently available allowing you to continue to work while normal recovery runs in parallel to restore data to primary storage. (See in the DPX 4.9.x User’s Guide.) Since data can be modified while the Instant Access mapping is in effect, the modified data may need to be restored to complete the recovery process. Steps outside DPX can be used to recover the modified data. (See in the DPX 4.9.x User’s Guide.)
Instant Access can be used in conjunction with SnapMirror for uninterrupted access to mirrored Block backups. For example, you can mirror Block backups from a storage system to an alternate secondary, such as a high-performance offsite storage system, then use Instant Access to give users rapid access to data on the offsite system. (See in the DPX 4.9.x User’s Guide.)
Instant Access is an efficient backup verification tool since backup instances on the storage system are readily usable from a standby node. (See in the DPX 4.9.x User’s Guide.)
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Instant Access and click Next.
The Object to Restore view shows all nodes that you backed up using DPX Block Backup. 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 files or directories you want to restore. Click Next.
From this point on, the workflow is slightly different for Block backups from Linux and Windows machines.
From the list of volumes within the object, select the volume you want to mount as an Instant Access disk. Click Next.
In the Recovery Points step, select the recovery point to restore. The available recovery points can be sorted by Backup Date/Time, Job Name, Secondary Node or Secondary Volume. Click Next.
In the Mount Destination step, select the destination Node Name from the drop-down list. Only Windows nodes will be available for selection. Then, from the Path drop-down list, select the letter identifying the newly mounted disk. Click Next.
In the Options step, you can select the Alternate Secondary Node. This step is optional. You can skip it by just clicking Next. In all previous steps of creating a restore job, the available selections were based on the backup metadata stored on DPX. This means that DPX is aware of all backups made by the user and where they are stored. If, during backup or at a later stage, the backup data have been replicated to a secondary location and the primary location becomes corrupt or inaccessible, you can choose to restore your data from such secondary location using this option.
Select the Secondary Node from the drop-down list.
Select the volume where the alternate backup is stored.
DPX will attempt to identify the files or directories specified in previous steps. If this proves impossible, the following warning will be displayed:
In the Mounting Image step, wait for DPX to mount the selected volume.
After a while, the success screen will be shown.
Click Finish. To manage the items mounted by DPX, find the Active Restores widget on the Dashboard.
If you cannot see the freshly mounted volume in the Active Restores widget, click Scan and wait a few moments. DPX Master Server will communicate with the Clients to retrieve information about the mounted volume.
You can now access your IA-mounted volume on your Windows machine.
Note. Remember that by acting upon the IA-mounted volume, you are actually connecting to the vStor the backup is stored in (or the secondary node). This translates to a potentially high latency.
From the list of volumes within the object, select the volume you want to mount as an Instant Access disk. Click Next.
In the Recovery Points step, select the recovery point to restore. The available recovery points can be sorted by Backup Date/Time, Job Name, Secondary Node or Secondary Volume. Click Next.
In the Mount Destination step, select the destination Node Name from the drop-down list. Only Linux nodes will be available for selection. Then, type the mounting point for the newly mounted disk. For a new directory, type it at the end of the existing path. Click Next.
In the Options step, you can select the Alternate Secondary Node. This step is optional. You can skip it by just clicking Next. In all previous steps of creating a restore job, the available selections were based on the backup metadata stored on DPX. This means that DPX is aware of all backups made by the user and where they are stored. If, during backup or at a later stage, the backup data have been replicated to a secondary location and the primary location becomes corrupt or inaccessible, you can choose to restore your data from such secondary location using this option.
Select the Secondary Node from the drop-down list.
Select the volume where the alternate backup is stored.
DPX will attempt to identify the files or directories specified in previous steps. If this proves impossible, the following warning will be displayed:
In the Mounting Image step, wait for DPX to mount the selected volume.
After a while, the success screen will be shown.
Click Finish. To manage the items mounted by DPX, find the Active Restores widget on the Dashboard.
If you cannot see the freshly mounted volume in the Active Restores widget, click Scan and wait a few moments. DPX Master Server will communicate with the Clients to retrieve information about the mounted volume.
You can now access your IA-mounted volume on your Linux machine.
Note. Remember that by acting upon the IA-mounted volume, you are actually connecting to the vStor the backup is stored in (or the secondary node). This translates to a potentially high latency.
To unmount an Instant Access from a machine, go to the DPX Master Server dashboard and click the “X” symbol next to the Instant Access Mapping item to unmount it.
The volume will be unmounted from the machine and will disappear from the widget.
Important. Never unmount an Instant Access volume directly from the machine where it is mounted. This may result in inconsistent behavior.
This chapter details the various options available when configuring Restoring files protected by file backup jobs.
This option is enabled by default and allows files to be restored to the original device cluster from which they were backed up, ensuring data consistency.
Enabled by default, this option automatically generates a job name based on the Unix timestamp of the backup job.
This option enables encryption for data during the restore process, enhancing security, especially over unsecured networks.
Enabled by default, this setting automatically deletes the restore job from the system once the process is complete.
Configures the system to send an email notification upon the completion of the restore job.
The email address of the primary recipient of your message. Only one “To” address is permitted.
Carbon Copy. The email address(es) of the secondary recipient(s) of your message. Use a semicolon to delimit multiple email addresses.
Blind Carbon Copy. The email address(es) of the secondary recipient(s) not identified to other recipients. Use a semi-colon to delimit multiple email addresses.
The subject of your message. The subject line usually contains a combination of straight text and variable elements. Variables, which must begin with %, are replaced with actual corresponding values. If you enclose variables in double quotation marks, those variables are treated as literal values. You can embed the following variables:
%JOBNAME
%JOBID
%JOBTYPE
%RC
Use %RC to include the return code in the message for this run of the job, when applicable.
Allows the restoration of files to a different location than originally backed up, useful for testing or recovery scenarios where the original location is unavailable. If enabled, select the destination node and absolute path within the node from the dropdown menu.
Enables scheduling of the restore job to run at a specific time or regularly. The time field is using your browser’s time zone. For example, if you have DPX in London and access the DPX web interface from New York, specify the time in US Eastern Time.
Important. When specifying a schedule, make sure the Delete the restore job on successful completion toggle is switched off. Otherwise, the job will be deleted upon its first successful completion.
Also please note that in the current version of DPX, restore jobs cannot be edited. This also includes job scheduling.
This option compresses the data being restored, potentially reducing restore times and network load.
Controls tape drive usage to optimize the availability of drives for subsequent jobs:
Determines the handling of tapes post-job:
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.
Holds tasks within a job until the number of drives specified are available for each task to use.
The maximum number to check a tape in a standalone tape device.
The number of seconds to wait between checking the availability of a tape in a standalone tape device.
As with backup jobs, you can add script options for this restore job.
Specifies a script to run before the job starts, with options to handle scenarios where the script fails:
Run Job/Run Post-Job Script
Skip Job/Run Post-Job Script
Skip Job/Skip Post-Job Script
Specifies a script to run after the job completes, with options for handling job failure:
Run Post-Job Script
Skip Post-Job Script
Tells DPX how to behave if it finds a file at the destination with the same name as the file that it is restoring.
Controls how DPX behaves if it tries to restore a file to a directory and discovers that the directory does not exist.
Configures the restoration path for the files. This setting allows you to choose whether to preserve the original directory structure or to restore all files to a single specified directory.
Specifies the action to take with files that were not fully restored.
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 files.
Prepares the Microsoft SQL Server database to be restored in a standby/read-only mode. This is particularly useful for situations where the database needs to be online during the restore process but should not be modified.
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.
This setting governs the restoration of data from backups made through Windows 2000 volume mount points, detailing both the restoration location and the reassignment of mount points.
To ensure a mount point's content is backed up, activate the 'Back Up Content of Mounted Drive' option in the 'Set Job Source Options'. For instance, if C:\mnt\driveD is a mount point for D:, you would select C:\mnt\driveD for the backup instead of D:.
Note. if a directory was a mount point during backup but is now a standard directory with local files at the time of restoration, the mount point will not be recreated. Instead, the data will be restored to the directory that previously functioned as a mount point.
Note. Be aware that for Reconstructive Restores, DPX will default to the Restore Data and Mount Point; Replace Existing Mount Point option, regardless of the initially selected setting.
Using disk quotas, administrators can limit the amount of data each user can store on a Windows 2000 NTFS or NSS volume. This field determines whether to restore disk quotas.
Note. Backing up an entire volume is not a prerequisite for preserving disk quota settings. Any backup operation from a supported volume will automatically include this information. Similarly, when restoring, it is not mandatory to restore the entire volume to recover disk quota settings.
If the Enterprise has more than one domain controller, you can choose whether to replicate SYSVOL files and folders to the other controllers as part of the Windows 2000+ System State restore.
To execute an authoritative restore of the Active Directory, it is necessary to run the Microsoft Ntdsutil utility. This step should be performed after the System State data has been restored but before rebooting the domain controller. For detailed guidance on using the Ntdsutil utility and performing an authoritative restore, please consult the Microsoft documentation.
If your Enterprise contains clusters, you can choose whether to restore the cluster quorums as part of the Windows 2000+ System State restore.
Determines whether DPX restores security information associated with each file or folder.
Determines how to handle files that fail when you attempt to restore them. This applies only to Windows.
Full Virtualization for Hyper-V creates a new VM that contains a duplicate of the original machine. Each partition of the snapshot is physically transferred to its disk volume on the new VM during virtualization. In other words, Full Virtualization creates a virtual disk with the same layout as the corresponding disk of the backed-up source machine and populates it with the backed-up data. This method is often used to create permanent VMs that can be put into production.
Tip. All the source disks will be created as .vhdx files on the specified datastore, based on the snapshot image from the secondary storage system.
See also. In addition to virtual machines, you can also restore specific files or directories in them. For more details about restoring files, see .
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Full VM Restore and click Next.
The VM object list shows all VMs that you backed up by using the DPX Agentless Backup. The available objects to restore can be sorted by Name, Type, associated Job Name, the Backup Date/Time, or Size. Find the VM you want to restore. Alternatively, select Latest Recovery Point. Click Next.
In the Recovery Points pane, select the recovery point to restore. You can select the Latest Recovery Point or either one of the other recovery points in the list. The available recovery points can be sorted by Backup Date/Time, Job Name, or Secondary Node. Click Next.
In the Options pane, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and - _ characters.
Specify job options using toggles. See below.
You can create the VM in a location that is different from the location in which the source virtual machine exists. Select the Target Host and Virtual Machine Properties (see below).
Select Node Name from the drop-down list. This must be an existing Hyper-V machine added as a node to DPX.
Specify the Node Path or leave default. This is the location on the Hyper-V node where the data will be recovered to.
Specify the new virtual machine name.
Click Save. A Run Job prompt will be shown.
Click Yes to run the job immediately or No if you want to run it later from the Job Manager. After a successful job run, the restored virtual machine will be visible in the Hyper-V Manager:
DPX allows you to restore files or directories that have been protected by DPX agent workloads stored on tape or disk.
Before you proceed with the restoration process, ensure that the backup storage, whether on tape or disk, is accessible and in a healthy state.
Tip. Before starting a restore job, verify that the backup data is intact and that there are no issues with the backup media.
To begin the process of restoring files, follow these steps:
Go to Job Manager in the sidebar.
Click New Restore Job to open the New Restore dialog.
Select Restoring files protected by file backup jobs and click Next.
A list will appear showing all files and directories backed up by previous file backup jobs. Select the files or directories you wish to restore and click Next.
Specify job options. This job can be tailored to meet specific recovery needs through a variety of settings and parameters.
Attention! Restoring files to an alternate destination may require additional configuration to ensure that the restored data is usable in its new environment.
Review the summary of your job and click Run. 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.
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.
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.
Specify the absolute path within the node. If the specified path does not exist, DPX will create it. Alternatively, use the icon to open the tree view and select the target folder from the machine’s folder structure. Note that the tree view does not allow for creating new folders.
See also. For more information, see in vStor documentation.
See also. For more information, see in vStor documentation.
See also. For detailed information about pre and post-job scripts, including all valid definitions, see .
if you are restoring to a new location, disk quota settings will only be reinstated if the new location is the root directory of a similar volume, and the is configured to Absolute Path.
Attention! When there are replication partners, selecting Authoritative Restore can result in unexpected behavior. For more information, see in vStor documentation.
See also. To learn more about available options for this job, see .
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 newly restored virtual machine will be powered on when restore is completed.
Toggle off
The VM will be restored in the powered-off state.
Toggle on
Upon restore completion, DPX will attempt to delete the source virtual machine (if it exists and if DPX still has access to it).
Toggle off
The source VM will remain unchanged in its location. Note. If no alternate location was chosen for the restored VM, both VMs will exist simultaneously in the same location. The old machine will not be overwritten by the restore job.
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 newly restored virtual machine will be powered on when restore is completed.
Toggle off
The VM will be restored in the powered-off state.
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.
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
All NDMP server log messages will be routed to the master server’s job log file. Yes is the default.
Toggle off
The NDMP server log messages will be logged locally in the NDMP client node log file instead of in the master server’s job log file.
Toggle on
Immediately after restore, DPX resynchronizes the restored backup instance as the most recent backup.
Toggle off
Do not resynchronize the restore.
Skip Existing Files and Directories
Does not write over the existing file or directory if it has the same name as the one being restored.
Replace Existing Files
Restores the file to a temporary file, ensures that the restore is successful, and then writes over the existing file with the like-named file being restored.
Replace Existing Files and Directories
For existing directories, restores directory characteristics only, such as date, time, and owner. For existing files, restores file to a temporary file, ensures that the restore is successful, then writes over the existing file with the like-named file being restored.
Delete Existing Files Before Restore
Deletes the existing file before restoring the like-named file. Use this option when disk space limitations prohibit using Replace Files.
Rename Restored Files
Renames the file being restored to a name derived from the existing file. On NTFS and UNIX, DPX appends .R01 to the filename. If filename.R01 exists, DPX uses .R02 and so on. On FAT, a file extension of .R01 is used. For example, file ABCD.TXT is restored as ABCD.R01. If ABCD.R01 exists, ABCD.R02 is used, and so on.
Use Full Privileges
Uses the file privileges the file possessed when it was originally backed up.
Use Parent Privileges
Applies the file privileges of the parent directory into which the files are being restored.
Use Root Privileges
Applies the file privileges of the root directory into which the files are being restored.
Authoritative Restore
Restores SYSVOL files and folders in a primary manner and forces that data to be replicated to the other primary domain controllers.
Non-Authoritative Restore
Restores SYSVOL files and folders locally and allows that data to get updated via the normal replication process. Non-Authoritative Restore is the default.
Do Not Restore Cluster Quorum
DPX does not restore the cluster quorum. Do Not Restore Cluster Quorum is the default.
Restore Cluster Quorum
DPX restores the cluster quorum. However, if other cluster nodes are active or if the cluster quorum has changed since backup, the cluster quorum restore may terminate.
Restore Cluster Quorum (Force the Recovery)
DPX restores the cluster quorum even if other cluster nodes are active or if the cluster quorum has changed since backup. Any changes made to the cluster quorum after the backup will be lost.
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.
Toggle on
The newly restored virtual machine will be powered on when restore is completed.
Toggle off
The VM will be restored in the powered-off state.
Toggle on
Upon restore completion, DPX will attempt to delete the source virtual machine (if it exists and if DPX still has access to it).
Toggle off
The source VM will remain unchanged in its location. Note. If no alternate location was chosen for the restored VM, both VMs will exist simultaneously in the same location. The old machine will not be overwritten by the restore job.
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 tape drive is released after the current task with a tape drive finishes so that the next job can use the same tape drive before completing the entire job. |
Toggle off | The tape drive holds the tape drive until the entire job is completed. |
Rewind Tapes | For a standalone tape device, this option rewinds the tape and leaves it in the drive. For a tape library tape drive, this option rewinds, unloads, and returns the tape to its slot. |
Unload Tapes | For a standalone tape device, this option rewinds the tape and ejects it from the drive. For a tape library tape drive, this option rewinds, unloads, and returns the tape to its slot. For DiskDirectory, this option causes empty volsers to be used before new volsers. |
Leave Tapes | In the case of standalone tape drives, the tape remains wound to the point where the job ended and stays in the drive. However, for tape library drives, the tape is always attempted to be returned to its slot after the backup operation is completed. The next job attempts to use the tape in the drive instead of mounting a new tape. In the case of a standalone drive, if the currently mounted tape is unacceptable (for example, if the next backup requires a tape from a different media pool), the operator is prompted to mount another tape. In the case of a tape library, if the tape in the drive is rejected for any reason, it unloads the tape, returns it to its slot, and proceeds to select another tape. |
Export Tapes | Automates the export of tapes to an I/O port, eliminating manual processes and preparing tapes for their next destination. In environments with physical tape libraries, the availability of an empty I/O port is essential. The system will alert and will return an error code if no port is available, prompting user action. A rescan of ports is recommended to ensure availability. |
Skip Existing Files and Directories | Does not write over the existing file or directory if it has the same name as the one being restored. |
Replace Existing Files | Restores the file to a temporary file, ensures that the restore is successful, and then writes over the existing file with the like-named file being restored. |
Replace Existing Files and Directories | For existing directories, restores directory characteristics only, such as date, time, and owner. For existing files, restores file to a temporary file, ensures that the restore is successful, then writes over the existing file with the like-named file being restored. |
Delete Existing Files Before Restore | Deletes the existing file before restoring the like-named file. Use this option when disk space limitations prohibit using Replace Files. |
Rename Restored Files | Renames the file being restored to a name derived from the existing file. On NTFS and UNIX, DPX appends |
Use Full Privileges | Uses the file privileges the file possessed when it was originally backed up. |
Use Parent Privileges | Applies the file privileges of the parent directory into which the files are being restored. |
Use Root Privileges | Applies the file privileges of the root directory into which the files are being restored. |
Absolute Path | Maintains the original directory structure upon restoration. For instance, if you backed up from |
Relative Path | Strips the parent directories, placing the files directly into the new restoration directory. For example, backing up from |
Toggle off | Keep the partially restored file. |
Toggle on | Delete the partially restored file. |
Toggle off | Does not restore the SQL Server database to a standby server. |
Toggle on | Restores a SQL Server database to a standby server. |
Restore Data (no Mount Point) | Restores data to the current directory structure, regardless of previous mount points. If a directory was a mount point at backup and remains so at restoration, data is restored to the current volume it mounts. |
Restore Data and Mount Point; Skip Existing Mount Point | Reestablishes the mount point and restores data to the mounted volume unless the directory now mounts a different volume, in which case the mount point is not reestablished. |
Restore Data and Mount Point; Replace Existing Mount Point | Always reestablishes the original mount point and restores data to the mounted volume, even if the directory mounts a different volume at restoration. This setting is the default during reconstructive restores. |
Toggle off | Disk quota settings are not restored. |
Toggle on | Disk quota settings are restored. |
Authoritative Restore | Restores SYSVOL files and folders in a primary manner and forces that data to be replicated to the other primary domain controllers. |
Non-Authoritative Restore | Restores SYSVOL files and folders locally and allows that data to get updated via the normal replication process. This is the default setting. |
Do Not Restore Cluster Quorum | DPX does not restore the cluster quorum. This is the default setting. |
Restore Cluster Quorum | DPX restores the cluster quorum. However, if other cluster nodes are active or if the cluster quorum has changed since backup, the cluster quorum restore may terminate. |
Restore Cluster Quorum (Force the Recovery) | DPX restores the cluster quorum even if other cluster nodes are active or if the cluster quorum has changed since backup. Any changes made to the cluster quorum after the backup will be lost. |
Toggle off | Restores all security information associated with the files and directories, including NTFS security properties, UNIX/Linux ACLs, and trustee settings in NetWare or OES environments. This is the default setting. |
Toggle on | Does not overwrite security information in the restoration destination directories. |
No | Does not retry restoring files that failed during the initial attempt. This is the default setting. |
Retry Open File | Attempts to restore files that were open and failed in the initial restore attempt. A system reboot is required after the restore to access the files. |
Retry All Failure | Retries the restoration of all files that failed during the initial attempt, including open files. A system reboot is necessary post-restore to access the files. |
Toggle on | The newly restored virtual machine will be powered on when restore is completed. |
Toggle off | The VM will be restored in the powered-off state. |
Toggle on | Upon restore completion, DPX will attempt to delete the source virtual machine (if it exists and if DPX still has access to it). |
Toggle off | The source VM will remain unchanged in its location. Note. If no alternate location was chosen for the restored VM, both VMs will exist simultaneously in the same location. The old machine will not be overwritten by the restore job. |
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 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.
