Community in read only mode June 18 & 19
This community will be set in READ ONLY mode for a while on Tuesday June 18 into Wednesday June 19 while we import content and users from our Micro Focus Forums community site. MORE INFORMATION
Absent Member.. sihong Absent Member..
Absent Member..

(DP) Support Tip EADR related

CM & Client : Windows server 2008 R2 Service Pack1, 9.04 bundle patches was installe on both server.
OS : windows server 2008 R2


DP gets the error with CONFIGURATION objects:
The disaster recovery wizard was unable to get recovery information for the selected clients. This information can be restored from CONFIGURATION object, but there’s no appropriate backup.

Analysis and suggestions:

From session report:
1. From backup session report, customer do have a valid CONFIGURATION backup:

[Normal] From: "CONFIGURATION:"  Time: 4/1/2016 4:35:35 PM
   Successfully collected Automatic DR data.

2. From cell_info file (same also from GUICORE debug file):

-host "sct-ccp" -os "microsoft amd64 wNT-6.1-S" -mac 90b11c917686 -da A.09.00 -ma A.09.00 -cc A.09.00 -autodr A.09.00 -docs A.09.00 -ts_core A.09.00
-host "" -os "microsoft amd64 wNT-6.1-S" -mac 90b11c917686 -da A.09.00 -ma A.09.00 -cc A.09.00 -autodr A.09.00 -docs A.09.00 -ts_core A.09.00

There are two hostname for the same host imported.
Please add any, any user to admin group under Users context.
Export both clients from cell and import only one client name

If still failed, please:
1. Install the latest DP patches
2. Collect backup debug files and session report.(from both CM and client)
3. provide with AUTODR.log and AUTODR.old.log file from
4. SRD file located at cell manager at C:\ProgramData\OmniBack\Config\Server\dr\srd\<client>.local
5. Drecovery.ini file located at cell manager at C:\ProgramData\OmniBack\Config\Server\dr\p1s\<client>.local
6. Debug logs when creating EADR recovery image from cell, such as GUICORE, RESTORE, srdx.dll, MANAGER, DBSM, ... of the latest attempt to create EADR recovery image for client


After import only one client name, problem solved.

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.