KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : Unable to Import Virtual Machines when the FQDN of the Virtual Machines exceeding 64 characters

Last Update: 2016-11-23 16:59:21 UTC

Description:

Unable to Import Virtual Machines in HBBU to perform backups as the discovery fails if there are any Virtual Machine with FQDN Host Name exceeding 64 characters.

Products Affected:

CA ARCserve Central Host-Based VM Backup r16.0 , r16.5

Symptoms of the Problem:

1) The discovery of the virtual machines might appear to have completed while trying to import the node but nodes might be missing in the Node List.

2) When we look at the log for ARCserve Central Host based VM Backup a generic error message appears indicating that the discovery failed.

3) The following message is logged in ARCAPP.LOG in the directory

'X:\Program Files\CA\ARCserve Central Applications\VSphere\Logs\'

2013-03-20 13:36:21,493 pool-11557-thread-1 [DEBUG]                EsxDiscoveryService.getInstance(){}
2013-03-20 13:36:21,493 pool-11557-thread-1 [DEBUG]                EsxDiscoveryService.getDiscoveryMonitor(){}
2013-03-20 13:36:21,493 pool-11557-thread-1 [DEBUG]            EsxDiscoveryService.access$1(..){com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryService@64377607 [instance=com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryService@64377607,discoveryMonitor=com.ca.arcserve.edge.app.base.webservice.contract.node.DiscoveryMonitor@5e3366b [elapsedTime=19767,processedNodeNum=108,currentProcessNodeName=,discoveryPhase=DISCOVERY_PHASE_NODE [ ],discoveryStatus=DISCOVERY_STATUS_ACTIVE [ ],errorCode=null,uuid=fce0def2-7774-4bf7-85ab-e6c7570c9b29 ] ]}
2013-03-20 13:36:21,494 pool-11557-thread-1 [DEBUG]            EsxDiscoveryTask.updateDB(..){com.ca.arcserve.edge.app.base.webservice.contract.node.DiscoveryVirtualMachineInfo@582e3a10 [vmName=VM-Name,vmUuid=null,vmHostName=Virtual-Machine-FQDN-HOST-NAME,vmInstanceUuid=500642a3-71df-bf5d-cb1c-12fbe59b2073,vmEsxHost=VCENTER-ESX-ESXI-NAME,vmXPath=null,vmGuestOS=Microsoft Windows Server 2008 R2 (64-bit),vmIP=null,vmServerType=1 ],6,{1}}
2013-03-20 13:36:21,494 pool-11557-thread-1 [DEBUG]                EdgeCommonUtil.toUTC(..){2013-03-20 13:36:21.494 [nanos=494000000 ]}
2013-03-20 13:36:21,494 pool-11557-thread-1 [DEBUG]           
com.ca.arcserve.edge.app.base.serviceexception.EdgeServiceFault:
        at com.ca.arcserve.edge.app.base.serviceexception.EdgeServiceFault.getFault(EdgeServiceFault.java:24)
        at com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryTask.updateDB(EsxDiscoveryTask.java:317)
        at com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryTask.doDiscovery(EsxDiscoveryTask.java:157)
        at com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryTask.call(EsxDiscoveryTask.java:86)
        at com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryTask.call(EsxDiscoveryTask.java:1)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source).
2013-03-20 13:36:21,495 pool-11557-thread-1 [DEBUG]            EsxDiscoveryService.access$0(..){com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryService@64377607 [instance=com.ca.arcserve.edge.app.base.webservice.node.discovery.EsxDiscoveryService@64377607,discoveryMonitor=com.ca.arcserve.edge.app.base.webservice.contract.node.DiscoveryMonitor@40d11cf2 [elapsedTime=19769,processedNodeNum=109,currentProcessNodeName=,discoveryPhase=DISCOVERY_PHASE_NODE [ ],discoveryStatus=DISCOVERY_STATUS_ACTIVE [ ],errorCode=null,uuid=fce0def2-7774-4bf7-85ab-e6c7570c9b29 ] ],Error [value=4 ],Failed to discover virtual machines from ESX/vCenter server 'VCENTER-ESX-ESXI-NAME'.   }
2013-03-20 13:36:21,495 pool-11557-thread-1 [DEBUG]                EsxDiscoveryService.addActivityLog(..){Error [value=4 ],Failed to discover virtual machines from ESX/vCenter server 'VCENTER-ESX-ESXI-NAME'.  

Please locate the text vmHostName=Virtual-Machine-FQDN-HOST-NAME in the above log and the characters in the text retured for vmHostName would exceed 64 characters.

Cause of the Failure:

This problem occurs if there is any virtual machine with FQDN Name which is larger than 64 characters. CA is currently aware of the problem and working towards a permanent fix.

Suggested Workaround:

Install CA ARCserve D2D inside the guest virtual machine while a permanent fix is being developed. 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments