Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
VolodymyrM Absent Member.
Absent Member.
1259 views

81-145 and 81:141 errors when trying to do DR backup

I've come across an issue w/ failing DR backup on WS2003 EE x64 server, which is a member of failover cluster and being active node.
 
Client ver.: HP DP A.06.20.0370
 
 
[Minor] From: VBDA@cluster-node-1 "cluster-node-1 [/CONFIGURATION]" Time: 2015-04-28 19:42:07
[81:145]
Automatic DR information could not be collected.
Aborting the collecting of system recovery data.

[Minor] From: VBDA@cluster-node-1 "cluster-node-1 [/CONFIGURATION]" Time: 2015-04-28 19:42:07
[81:141] \SystemRecoveryData
Cannot export configuration object: (Unknown internal error.) => backup incomplete.
 
 
I've tried renaming C:\Program Files\OmniBack\tmp folder.
LDM and LDM Administrative Service are set to Auto/Manual startup types accordingly.
No Daemon Tools are installed on it.
 
Here is the log details from AUTODR.log
 
20150428T174104 INFO svclist Keyboard layout: 00000409, KBDUS.DLL, C:\WINDOWS\system32\KBDUS.DLL
20150428T174104 WARN svclist Input method file not registered.
20150428T174206 INFO command Command: coolie (10, Inserting system registry into the Recovery Set archive.)
20150428T174206 ERROR regmgr User (DRM$ADMIN) already exists.
20150428T174206 ERROR regmgr User (DRMADMIN) already exists.
20150428T174207 ERROR regmgr User (DRM$ADM) already exists.
20150428T174207 ERROR regmgr User (DRMADM) already exists.
20150428T174207 ERROR regmgr User (DR$ADMIN) already exists.
20150428T174207 ERROR regmgr User (DRADMIN) already exists.
20150428T174207 ERROR regmgr User (DR$ADM) already exists.
20150428T174207 ERROR regmgr User (DRADM) already exists.
20150428T174207 ERROR regmgr None of the possible user names could be created.
20150428T174207 FATAL regmgr EXCEPTION at src\core\regmgr.cpp(115):
20150428T174207 FATAL regmgr class drm::internal_error(997): Couldn't create DRM admin user.
*** Stack traceback:
*** 10: void __cdecl drm::`anonymous-namespace'::account_manager::create_account(void) -- src\core\regmgr.cpp(73)
*** 9: void __cdecl drm::registry_manager::save_registry(void) -- src\core\regmgr.cpp(188)
*** 8: void __cdecl drm::`anonymous-namespace'::mkrset::save_system_files(void) -- src\coolie\mkrset.cpp(1424)
*** 7: class boost::shared_ptr<class drm::recovery_set> __cdecl drm::`anonymous-namespace'::mkrset::prepare_drm(void) -- src\coolie\mkrset.cpp(1749)
*** 6: class boost::shared_ptr<class drm::recovery_set> __cdecl drm::prepare_recovery_set(class boost::shared_ptr<class drm::recovery_info>,const class drm::upath &) -- src\coolie\mkrset.cpp(1978)
*** 5: void __cdecl drm::`anonymous-namespace'::rs_create_api::operator ()(class drm::command::command_data &) -- src\coolie\coolieapi.cpp(1031)
*** 4: void __cdecl drm::command_manager::handle_command(class drm::command::command_data &) -- src\core\cmdmgr.cpp(46)
*** 3: bool __cdecl drm::`anonymous-namespace'::handle_command(class drm::`anonymous-namespace'::api_manager &,class drm::command::command_data &) -- src\coolie\coolieapi.cpp(1308)
*** 2: void __cdecl drm::coolie_interactive(void) -- src\coolie\coolieapi.cpp(1375)
*** 1: void __cdecl drm::coolie(int,char *[]) -- src\coolie\coolie.cpp(157)
*** 0: int __cdecl wmain(int,wchar_t *[]) -- src\coolie\coolie.cpp(269)
20150428T174207 INFO command Result: DRM(-7):SYS(997) ()
20150428T174207 INFO command Command: ri_close (1)
20150428T174207 INFO command Result: DRM(0):SYS(0) ()
 
I see that the users listed above do exist in local users console, but how can I ignore the error, should the account be deleted?
 
What are they used for/?

0 Likes
8 Replies
Highlighted
Bob_Clark Absent Member.
Absent Member.

Re: 81-145 and 81:141 errors when trying to do DR backup

The most common reason for this error is that your system contains a drive without a designated drive letter.  Make sure that all drives have a drive letter, and try the backup of the /CONFIGURATION object again

 

also, if you are using Dynamic disks for software morroring, that will cause this serror

 

I saw several cases where this problem was resolved with a patch, but, your version of DP (6.2) is out of support, so that these are no longer available

 

 

 

 

0 Likes
Absent Member.. danielbraun Absent Member..
Absent Member..

Re: 81-145 and 81:141 errors when trying to do DR backup

Hi all,

 

as mentioned by Bob, please upgrade at least to DP 7.03+. Especially for W2K3 Clusters there are some fixes for EADR included.

 

Best regards

Daniel

-----------
Please assign Kudos - How to assign...
0 Likes
VolodymyrM Absent Member.
Absent Member.

Re: 81-145 and 81:141 errors when trying to do DR backup

Unfortunately, there is no chance to upgrade to a later version now.

 

Does anybody know whether this is safe to delete the aforementioned user accounts?

Admin Guide and google are not quite helpful on determining if this is Ok.

 

On the 2nd, not active node, the /configuration backup is running just fine and NO such DR$*** accounts exist there.

0 Likes
Absent Member.. danielbraun Absent Member..
Absent Member..

Re: 81-145 and 81:141 errors when trying to do DR backup

Hi,

 

without warranty... you should be able to delete these dr*** accounts. Normally they will required in restore scenario only... Have you enbled the option to create the full recovery set during backup? If yes, try to delesect this option... The alternative ist then to create the recovery set when executing the EADR process.

 

Best regards

Daniel

-----------
Please assign Kudos - How to assign...
0 Likes
VolodymyrM Absent Member.
Absent Member.

Re: 81-145 and 81:141 errors when trying to do DR backup

Hmm.., let's presume I will delete them and the accounts are then recreated during the next backup job, - then the question arises: will I be able to restore the old data with newly-recreated accounts?

 

New accounts means new SIDs, and no access to old data?

0 Likes
VolodymyrM Absent Member.
Absent Member.

Re: 81-145 and 81:141 errors when trying to do DR backup

I did delete these accounts on one old server and will check how it goes tonight.

 

0 Likes
VolodymyrM Absent Member.
Absent Member.

Re: 81-145 and 81:141 errors when trying to do DR backup

Good news! Server has been backed up successfully after removing local DR$**** accounts and no errors in AUTODR.log.

 

0 Likes
Absent Member.. danielbraun Absent Member..
Absent Member..

Re: 81-145 and 81:141 errors when trying to do DR backup

Hi,

 

good to know that it is now working again.

 

Best regards

Daniel

-----------
Please assign Kudos - How to assign...
0 Likes
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.