Usability enhancements to Windows EADR

Usability enhancements to Windows EADR

Brief description:

The Windows EADR recovery media should be enhanced to provide better usability. So the recovery media and the wizard should:

  1. Include the source client certificate required for Secure Socket Communication (SSC) with the Cell Manager. It can be captured during the /CONFIGURATION backup and included in the media to make omnicc -secure_comm -configure_for_dr no longer necessary.
  2. Have a connectivity/requirement check to the Cell Manager so the user can do the required changes to the networking, UserList and Secure Socket Communication if required and re-validate again with the need to reboot server. Display what has failed and recommend corrective actions (e.g. INET port on CM is reachable, but not responding => run omnicc -secure_comm -configure_for_dr 
  3. Stop the Data Protector INET process after the recovery session ends (successful or unsuccessful). This makes sure that logs created are closed and can be copied to a remote system if needed.
  4. Have an automatic log bundle collection. Contain information on used settings, system configuration and session success. Useful for troubleshooting and documenting EADR activities (for compliance/audit needs). Save to local disk, network or via INET to the Cell Manager.

Benefit:

  • Implement end-to-end security even during disaster recovery.
  • Improves usability during disaster recovery workflow
  • Improved support experience by reducing manual steps
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.