Forum Discussion

wilkill's avatar
wilkill
Level 2
14 years ago

backup exec 12.5 + vcb + vsphere 4.0 problème de connexion

Bonjour à vous,

Il y a peu un problème m'est apparu:

Catégorie d'erreur : Erreurs des ressources
Erreur : e0009541 - Impossible de se connecter au centre virtuel VMware ou au serveur ESX. Vérifiez les informations d'authentification fournies pour la connexion.

Cependant le login de connexion n'ayant pas changé, je n'explique pas ce problème.

Pouvez vous m'aider svp.

merci

backup exec version 12.5 rev 2213 (windows serveur 2003)

vcbmounter.exe Version 1.5.0.5584 (build-226297)  (installé sur le serveur ou il ya backup exec)

vsphere 4.0 avec 2 esx 4.0 (machine virtuel xp sur serveur ESX)

 

Cordialement.

 

Backup and Recovery
Backup Exec
Error messages

5 Replies

Sort By
  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    14 years ago

    I haven't translated your complete message above however if using vSphere then you should probably consider upgrading to Backup Exec 2010 (R2) so that you can take advantage of the abilities of the vStorage API mechanism instead of needing VCB.

     

  • wilkill's avatar
    wilkill
    Level 2
    14 years ago

    oui c'est peu être une solution.

    Cependant l'installation fonctionnait. Donc je n'ai pas trop envie d'investir pour le moment dans cette mise a jour.

     

    Cordialement.

  • wilkill's avatar
    wilkill
    Level 2
    14 years ago

    Donc qui pourrait me répondre sur se sujet?

    Quel est le protocole utilisé pour la connexion au virtual center.

    Y aurait-il un problème avec ma  machine virtual center (vsphere).

     

    Pour info l'utilisateur utilisé est administrateur et dispose de tous les droits sur les serveurs ESX4.

    Connexion ok avec le vi client de vmware.

     

    Cordialement.

  • wilkill's avatar
    wilkill
    Level 2
    14 years ago

    + info en mode debug live:

    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 FS_ResolveDevName: [VMVCB::\\******\Virtual Center]
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 MB2-Resolve returned 1
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 ADC_ResolveDeviceName: pid = 5892, checking VMVCB::\\*****\Virtual Center
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 Inside evFileSystem::EV_ResolveDeviceName
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 Inside evFileSystem::IsGoodEVName
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 evFileSystem::IsGoodEVName: GoodEvName failed for (VMVCB::\\******\Virtual Center)
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 evFileSystem::EV_ResolveDeviceName: IsGoodEVName failed for (VMVCB::\\*******\Virtual Center)
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33   VRTSRV:DeviceName VMVCB::\\******\Virtual Center
    BEREMOTE: [01/17/11 12:02:34] [0000]     [6112] 01/17/11 12:02:33 RPCDsSession::GetLoginCredentials: Connecting to BEM API as user: *****\Administrateur
    BESERVER: [01/17/11 12:02:34] [0000]     [0332] 01/17/11 12:02:33 -1 Client requested key (1295251511).
    BESERVER: [01/17/11 12:02:34] [0000]     [3096] 01/17/11 12:02:33 01 Server Configuration: Client added: 7
    BESERVER: [01/17/11 12:02:34] [0000]     [3096] 01/17/11 12:02:33 -1 Client 'RUN-BACKUP' connected('','******\Administrateur'): 0x1238bb0
    BESERVER: [01/17/11 12:02:34] [0000]     [0332] 01/17/11 12:02:33 01 Server Configuration: Client removed: 6
    BESERVER: [01/17/11 12:02:34] [0000]     [0332] 01/17/11 12:02:33 -1 Client 'RUN-BACKUP' Disconnected:0x1238bb0
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:33 System Directory (C:\WINDOWS\system32)
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:33   Filling file with test DWORD test data.
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34 hFile size:     524288
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34 Calling LaunchApplication( Administrateur PASSWORD ***** ManagedVmWrapper.exe
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34 MemoryMapperClient::LaunchApplication() starting as ******\Administrateur
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34 LaunchApplication() - OpenProcessToken() Failed with error (5).
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34   Attempting to launch the support application ""C:\Program Files\Symantec\Backup Exec\ManagedVmWrapper.exe" 1295251353"...
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34     Support application ""C:\Program Files\Symantec\Backup Exec\ManagedVmWrapper.exe" 1295251353" successfully loaded.
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34       PId:0x11c8 TId:0x1480
    MANAGEDV: [01/17/11 12:02:34] [0000]     BECRYPTO Base Address is 63100000
    MANAGEDV: [01/17/11 12:02:34] [0000]     BECryptoInit: Initialized locks for SSL callbacks
    MANAGEDV: [01/17/11 12:02:34] [0000]     BECryptoInit: BECrypto non-FIPS mode successfully enabled.
    BEREMOTE: [01/17/11 12:02:34] [0000]     [4608] 01/17/11 12:02:34 manVmWrapperClient::ProcessReply() VM_SET_TASK_TIMEOUTS. Successful
    BEREMOTE: [01/17/11 12:02:36] [0000]     [4608] 01/17/11 12:02:36 manVmWrapperClient::ProcessReply() VM_CONNECT_TO_VIRTUAL_CENTER. Got an error status(38209) reply for the request.
    BEREMOTE: [01/17/11 12:02:36] [0000]     [4608] 01/17/11 12:02:36 VM_VCBPROXY_FS::GenerateVCItemDles() Could not connect to the VC server '******'  User:'******\Administrateur'
    BEREMOTE: [01/17/11 12:02:36] [0000]     [4608] 01/17/11 12:02:36 VM_VCBPROXY_FS::GenerateVCItemDles() Could not delete the file C:\Program Files\Symantec\Backup Exec\Data\{CA75AC94-9C0C-4084-A6F1-E299F30BAF0C}.XML(0x2)
    BEREMOTE: [01/17/11 12:02:36] [0000]     [4608] 01/17/11 12:02:36 manVmWrapperClient::ProcessReply() CMD_END_PROCESS.
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 FS_ResolveDevName: [VMVCB::\\******\Virtual Center]
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 MB2-Resolve returned 1
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 ADC_ResolveDeviceName: pid = 5892, checking VMVCB::\\******\Virtual Center
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 Inside evFileSystem::EV_ResolveDeviceName
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 Inside evFileSystem::IsGoodEVName
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 evFileSystem::IsGoodEVName: GoodEvName failed for (VMVCB::\\********\Virtual Center)
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 evFileSystem::EV_ResolveDeviceName: IsGoodEVName failed for (VMVCB::\\******\Virtual Center)
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50   VRTSRV:DeviceName VMVCB::\\*******\Virtual Center
    BEREMOTE: [01/17/11 12:02:50] [0000]     [6112] 01/17/11 12:02:50 RPCDsSession::GetLoginCredentials: Connecting to BEM API as user: *******\Administrateur
    BESERVER: [01/17/11 12:02:50] [0000]     [0332] 01/17/11 12:02:50 -1 Client requested key (1295251528).
    BESERVER: [01/17/11 12:02:50] [0000]     [3936] 01/17/11 12:02:50 01 Server Configuration: Client added: 7
    BESERVER: [01/17/11 12:02:50] [0000]     [3936] 01/17/11 12:02:50 -1 Client 'RUN-BACKUP' connected('','*****\Administrateur'): 0x1238bb0
    BESERVER: [01/17/11 12:02:50] [0000]     [0332] 01/17/11 12:02:50 01 Server Configuration: Client removed: 6
    BESERVER: [01/17/11 12:02:50] [0000]     [0332] 01/17/11 12:02:50 -1 Client 'RUN-BACKUP' Disconnected:0x1238bb0
    BEREMOTE: [01/17/11 12:02:50] [0000]     [4608] 01/17/11 12:02:50 System Directory (C:\WINDOWS\system32)
    BEREMOTE: [01/17/11 12:02:50] [0000]     [4608] 01/17/11 12:02:50   Filling file with test DWORD test data.

     

     

    Can help me pleaze.

    thanks

  • herve_lequippe's avatar
    herve_lequippe
    Level 4
    14 years ago

    Vsphere 4 n'est pas supporté par BE 12.5. vous devez mettre a jour en BE 2010 (actuellement en version 2010 R2 SP1)