Version 6.7 went GA on November 20th with a great set of new features:
VMware’s product, Site Recovery Manager (SRM) manages replication between two sites and allows failover of VMs and datastores between sites all managed from vCenter.
SRM can use its own software replication but can also take advantage of array based replication if the datastores are hosted on capable hardware such as the Hitachi arrays. To enable this, we have provided a Site Recovery Adaptor (SRA) for HDID that uses the HDID API to perform the required actions.
SRA for HDID is shipped alongside HDID and has its own installer and release note. VMware will also host the adaptor on its website for download.
VMware vRO Integration
vRealize Orchestrator is a VMware tool that allows tasks to be automated using workflows. We have produced workflows that automate some HDID tasks such as backing up or restoring a VM. These workflows can be invoked from vSphere allowing a user to invoke HDID tasks straight from the VMware interface. These workflows will also be used by the Hitachi Enterprise Cloud (HEC) product offering data protection as a service.
The HDID vRO integration is shipped alongside HDID in the form of a plugin that is installed on the vRO server. It also has its own release note.
GAD 2DC Swap
HDID can now orchestrate swapping GAD replication on demand.
On demand LUN allocation
HDID is now able to add SVOLs it creates into host groups without having to perform a mount operation. When defining the dataflow additional host groups can be specified, it’s also possible to retrospectively add SVOLs into host groups from the storage screen.
Local Replication Revert
HDID can now use reverse copy to revert local replications (Shadow image and Refreshed Thin Image)
Online user guides
The user guides in html form are now part of the master installation. These user guides can be accessed from the user interface via the help menu. The online user guides are fully indexed and searchable.
Application Handler Improvements
Information about application assets such as databases is now cached on the master to provide a better user experience. The data will be refreshed automatically twice a day or when requested by a user.
This change does not affect backups which use wildcards, as this will still be evaluated at the beginning of the backup to get the latest information.
In addition to this, the application handler API has been reworked, adding consistency across applications and allowing API users to discover application details using the ApplicationNodeHandlers
Improved Oracle database point-in-time recovery
The Oracle database point in time recovery was improved based on the feedback we collected from the field. Here are some of the improvements available in this version:
- RMAN catalog credentials can now be specified directly in the recovery dialog
- A new option allowing you to specify if the database should be opened at the end of the recovery has been introduced. This allows the database administrator to make manual adjustments before the database is opened
- It is now possible to reset the databases memory settings on restore, allowing restores of big production databases to less powerful hardware
- More powerful prechecks for recovery
- More supported scenarios for different backup types
Microsoft SQL improvements
It is now possible to perform restores of host-based Microsoft SQL databases in a state which allow further recovery. Equivalent to what was already possible with hardware-based backups, the databases will be registered with an existing SQL Server instance and placed in the restoring state (analog to RESTORE DATABASE ... WITH NO RECOVERY). This will allow the Microsoft SQL administrator to manually apply transaction logs.
Reworked Microsoft Exchange connectivity
The logic how HDID communicates with Microsoft Exchange environments has been reworked. The new logic will be more stable and honor permissions and roles as they are defined in Exchange.
The new logic requires a valid Exchange user which is a member of the "View Organization Management" role.
NOTE: After the upgrade, you have to specify the credentials for your Microsoft Exchange application nodes, before you can compile and distribute your Exchange-related data flows. Unless this step is performed, updated clients will not be able to create new backups.