Avamar：ADME 备份错误 - 登录错误 74：在 Avamar 数据库中找不到帐户

Summary: Avamar Data Migration Enabler （ADME） 在导出时失败，因为域位置更改导致客户端具有无效的域路径。这会导致登录错误 74：在 Avamar 数据库中找不到帐户。

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

触发备份后，ADME 会在选择阶段立即失败： 

========================================== SELECTION - PHASE =========================================
ADMe is locked - retaining existing password...

ADMe session started...
Environment-1 is now locked by [ Batch-Owner=admbatch-OracleJob.cfg PID=13218 ]
User-Input: 1 -sid OracleGrp -select -d -butype cod mod nah
INFO-01A: Active-Auto Date Range - 2018-08-01 to 2018-08-10
Purging previous pseudo client backups from [/ADME/admepseudo]
avtar Error 5126: Login error 74: Account not found in the Avamar database
avtar FATAL 5308: Failed to initiate session with server
avtar Error 5126: Login error 74: Account not found in the Avamar database
avtar FATAL 5308: Failed to initiate session with server
avtar Error 5126: Login error 74: Account not found in the Avamar database
avtar FATAL 5308: Failed to initiate session with server
Scanning-Group [OracleGrp]-[cai-oracle.emc.com]...                                           
avtar Error 5126: Login error 74: Account not found in the Avamar database
avtar FATAL 5308: Failed to initiate session with server
INFO-07:  Configuration check succeeded
INFO-14:  Total backup count selected [0]

ERROR-04A Selection list is empty [ RC=1 ], this will impact continuing with a migration operation
Env- Session Complete: RC=1 08/09/18 16:52
ATO-BATCH-FAILURE: [-select] RC=[] Start-Time:09/08/18 16:52 End-Time:09/08/18 16:52 Elapsed-Time-HH:MM=n/a Env#:1

 

Cause

这是因为 ADME 找不到提到的客户端。一个可能的原因是客户端已从一个域移动到另一个域。

  • 检查客户端验证，我们可以看到 ADME 指出某些客户端已从其现有域中移出。
  • 这意味着 ADME 会看到旧的客户端路径，并且必须使用客户端移动到的新路径（域）进行更新。
ADME 客户端配置

Resolution

  • ADME 无法导出某些或特定客户端，因为它找不到客户端。
  • 原因是客户端已移动。
  • 必须使用正确的路径更新客户端。
  • 更新路径的步骤如下：
  1. 要更新客户端路径，需要从 ADME 交互式 CLI 执行以下步骤。
    1. 以 root 用户身份打开 Avamar Server，然后键入“adme”
    2. 选择第二个选项，您可以键入 2 或 C。
    3. 单击组对应的“G”。
    4. 选择拥有更改其域的客户端的组。
    5. 键入“M”表示“修改”。
    6. 您必须更新具有客户端域路径的第四个字段。
    7. 最后，在更新新客户端域后，必须键入“C”以提交更改。

旧路径：
ADME 交互式 CLI
新路径：
ADME 交互式 CLI 

Additional Information

  1. 打开 Avamar Server 并键入“adme”
  2. 选择第二个选项，您可以键入 2 或 C： 
    ==< cai-ave74 >================================
                                    |      ADMe Avamar Data Migration (Enabler)   |
                                    |                MAIN -  MENU                 |
                                    |                Version-4.1.11.45e
                                    ===============================================
                                    |        1. J) Job Policy Manager             |
                                    |        2. C) Client-Config Manager          |
                                    |        3. E) Environment-File Manager       |
                                    |        4. V) View Selection Worklist        |
                                    |        5. L) Event Log View                 |
                                    |        6. H) Help                           |
                                    |        7. R) Recovery Manager               |
                                    |        8. S) Interactive Selection          |
                                    |        9. M) Interactive Migration          |
                                    |       10. A) ADMe Administration            |
                                    |       11. G) ADMe Upgrade                   |
                                    |                                             |
                                    ===============================================
  3. 单击组对应的“G” 
    ==========================================================================================================< cai-ave74 >===============
 CONFIGURATION MANAGER [DOMAIN-VIEW]: <domain-name> [client-count]
====================================================================================================================================

 1)    /ADME [1]                            2)   /MC_RETIRED [8]                      3)   /NDMP [2]
 4)    /Oracle [1]                          5)   /REPLICATE/cai-ave.emc.com [1]       6)   /REPLICATE/cai-ave.emc.com/cai-vcen
 7)    /REPLICATE/cai-ave.emc.com/cai-vcen  8)   /REPLICATE/cai-ave.emc.com/cai-vcen  9)   /REPLICATE/cai-ave.emc.com/clients
 10)   /REPLICATE/cai-ave75.emc.com [1]     11)  /REPLICATE/cai-ave75.emc.com/cai-vc  12)  /VMWare [2]
 13)   /cai-vcenter.emc.com [3]             14)  /cai-vcenter.emc.com/ContainerClien  15)  /cai-vcenter.emc.com/VirtualMachine
 16)   /clients [4]                         17)  /clients/_DESACTIVATED [1]

====================================================================================================================================

 Config Options:

 [#=Domain I=Inhibit-Stats G=Group F=Refresh H=Search S=Status-All C=Cfg-View P=Cfg-Parse R=Report U=Cfg-Edit B=Build-CSV-Stats

 W=Col-Width Q=Quit] > G

  4. 选择具有更改其域的客户端的组：

    ==========================================================================================================< cai-ave74 >===============
 CONFIGURATION MANAGER [GROUP-VIEW]: <group-name> [client-count]
====================================================================================================================================

 1)    ADMEFull [1]                         2)   OracleGrp [1]                        3)   WindowsGrp [1]
 4)    lnxfs01 [1]                          5)   lnxfs02 [1]                          6)   winfs01 [3]
 7)    winfs02 [1]

====================================================================================================================================

 Config Options: [#=Group Z=Calculate-Aggregate-Size C=View-Cfg R=Report U=Cfg-Edit S=Status-All Def=Domain-View>] > 2
  5. 键入“M”表示修改： 
    ==========================================================================================================< cai-ave74 >===============
 CONFIGURATION MANAGER [GROUP-CLIENT-VIEW]: <client-name> [#Entries-state] Blue=Not-Config Green=Enabled Red=Disabled Yellow=Invalid
====================================================================================================================================

 1)    cai-oracle.emc.com [1-E]

====================================================================================================================================
  CLIENT-STATS-DISABLED:  Not-Configured=0    Disabled=0    Enabled=0    Invalid=0    Retired=0
====================================================================================================================================

 Config Options: [ D=Disable E=Enable M=Modify O=Remove R=Report T=Audit V=Quick-View Def=Group-View>] > M

 Enter a client# to add/modify or [ Press Enter to Return ]:> 1
DEBUG2 - Itemx=cai-oracle.emc.com Domainx=OracleGrp Mode=3

 Available Client Group-ID's:

 ADMEFull OracleGrp WindowsGrp lnxfs01 lnxfs02 winfs01 winfs02

 Client [cai-oracle.emc.com] is currently defined in groups:

 OracleGrp

 Ready to Modify client [/clients][cai-oracle.emc.com] in ADMe configuration.

 Enter An Existing or New Group-ID or [Def=OracleGrp] Q=Quit:
  6. 更新具有客户端域路径的第 4 个字段：
    ==================================================================
         Review All Fields to Establish Selected Client Entry
==================================================================

        Fld-1 ADMe Group-ID Name [OracleGrp]: >
        Fld-2 Start-Date [AUTO]: >
        Fld-3 End-Date [AUTO]: >
        Fld-4 Domain-Name [/clients]: >
        Fld-5 Client-Name [cai-oracle.emc.com]: >
        Fld-6 Avamar-Policy-Group-Name [n/a]: >
        Fld-7 Avamar-Retention-Type [daily]: >
        Fld-8 Exclude-Folders [/tmp/Oracle]: >
        Fld-9 Output-FIle [DEFAULT]: >
        Fld-10 Stage-Destination-Directory [/staging/OracleGrp]: >
        Fld-11 Migration-BU-Scripts [AUTO]: >
        Fld-12 Migration-Monthly-Policy [ORCLNWGRP]: >
        Fld-13 Migration-EOY-Policy [n/a]: >
        Fld-14 Migration-Server-Policy [n/a]: >
        Fld-15 Staging-Server-Type WINDOWS | UNIX [UNIX]: >
        Fld-16 Destination-Path-Suffix [n/a]: >
        Fld-17 Include-Folders [n/a]: >
        Fld-18 Incremental-Delete [n/a]: >


==================================================================

 Confirm Client Entry: [ C=Commit M=Modify Enter=Refresh Q=Quit]: >

 
==================================================================
 Enter All Fields to Modify a Client Entry, press enter to accept defaults
==================================================================

        Fld-1 ATO-Group-ID Name [OracleGrp]: >
        Fld-2 Start-Date [AUTO]:
        Fld-3 End-Date [AUTO]:
        Fld-4 Domain-Name [/clients]: > /Oracle
        Fld-5 Client-Name [cai-oracle.emc.com]: >
        Fld-6 Avamar-Policy-Group-Name [n/a]:
        Fld-7 Retention-Type [daily]:
        Fld-8 Exclude-Folders [/tmp/Oracle]:
        Fld-9 Output-FIle [DEFAULT]:
        Fld-10 Stage-Destination-Directory [/staging/OracleGrp]:
        Fld-11 Migration-BU-Scripts [AUTO]:
        Fld-12 Export-Policy-Client-Initiated [ORCLNWGRP]:
        Fld-13 Export-EOY-Policy-Client-Initiated [n/a]:
        Fld-14 Export-Policy-Server-Initiated [n/a]:
        Fld-15 Staging-Server-Type WINDOWS | UNIX [UNIX]:
        Fld-16 User-Defined-Destination-Path-Suffix [n/a]:
        Fld-17 Include-Folders [n/a]:
        Fld-18 Incremental-Delete [n/a]:


==================================================================

 Confirm Client Entry: [ C=Commit M=Modify Enter=Refresh Q=Quit]: > C
 
    7. 
  

  




        

        
        
Affected Products

        Avamar Data Migration Enabler
    
Products

        Avamar Client, Avamar Data Migration Enabler







                        

                            

    

        

            

                
                    
 Article Properties

                
            

            

                

                        
Article Number: 000052310

                

                
                

                        
Article Type: Solution

                

                

                        
Last Modified: 05 Sept 2025


                

                    

                            
Version:  5

                    


            


        

    

    

        

            

                
                    
Find answers to your questions from other Dell users

                
            

            

                

                    
                



            


        

    

    

        

            

                
                    
Support Services

                
            

            

                

                    Check if your device is covered by Support Services.