Re: Scheduled VMware routine timeout (VEPA hanging) (749 Views)
Reply
Collector
RomeroJunior
Posts: 1
Registered: ‎02-05-2014
Message 1 of 3 (778 Views)

Scheduled VMware routine timeout (VEPA hanging)

[ Edited ]

Hi folks,

 

Everytime the scheduled VMware backup job runs it results the error described below. However, when I run the very same job manually (right-click on the backup job followed by "Start backup...") it works perfectly. I'm currently using the HP Data Protector A.07.00 (Internal Build Version 103) and my virtual machines are hosted on ESXi 5.5 (vCenter Server 5.5.0 Build 1312298). I don't know if it might be relevant but both vCenter and Cell Manager are hosted on the same machine (Windows Server 2008 R2).

 

Has anyone been through this issue before? I've already searched about it but unfortunately I haven't found anything relevant yet.

 

Before any comment: Setting the timeout to a value above 600 seconds (10 minutes) is not a valid solution since it clearly works when started manually.

 

Here's the output:

 

[...]

 

[Normal] From: BSM@vcenter "vCenter"  Time: 04/02/2014 21:00:06
    Backup session 2014/02/04-7 started.

[Normal] From: BSM@vcenter "vCenter"  Time: 04/02/2014 21:00:06
    OB2BAR application on "vcenter" successfully started.

2014-02-04T21:00:11.817-02:00 [14448 info 'Default'] Initialized channel manager
2014-02-04T21:00:11.823-02:00 [14448 info 'Default'] Current working directory: C:\Windows\system32
2014-02-04T21:00:11.829-02:00 [14448 verbose 'ThreadPool'] TaskMax=10, IoMin=1, IoMax=21
[Normal] From: VEPALIB_VMWARE@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:00:14
    Resolving objects for backup on vCenter 'vcenter' ...

[Normal] From: VEPALIB_VMWARE@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:00:25
    Add Virtual Machine 'VMACHINE-01' to the backup ...

[Normal] From: VEPALIB_VMWARE@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:00:26
    Add Virtual Machine 'VMACHINE-02' to the backup ...

[Normal] From: VEPALIB_VMWARE@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:00:26
    Add Virtual Machine 'VMACHINE-03' to the backup ...

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:01:10
    Virtual Machine 'VMACHINE-01': Locking vMotion ...

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:01:10
    Virtual Machine 'VMACHINE-02': Locking vMotion ...

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:01:10
    Virtual Machine 'VMACHINE-03': Locking vMotion ... 

 

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:01:32
    Virtual Machine 'VMACHINE-01': Consolidating snapshots ...

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:01:32
    Virtual Machine 'VMACHINE-02': Consolidating snapshots ...

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:01:32
    Virtual Machine 'VMACHINE-03': Consolidating snapshots ...

 

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:09:04
    Virtual Machine 'VMACHINE-01': Backing up configuration file VMACHINE-01.vmx ...

 

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:09:04
    Virtual Machine 'VMACHINE-02': Backing up configuration file VMACHINE-02.vmx ...

 

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:09:04
    Virtual Machine 'VMACHINE-03': Backing up configuration file VMACHINE-03.vmx ...

 

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:09:24
    Virtual Machine 'VMACHINE-01': Creating snapshot ...

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:09:25
    Virtual Machine 'VMACHINE-02': Creating snapshot ...

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:09:25
    Virtual Machine 'VMACHINE-03': Creating snapshot ...

 

2014-02-04T21:09:40.496-02:00 [12380 trivia 'ThreadPool'] PrepareToWait: Starting new thread
2014-02-04T21:09:40.553-02:00 [07488 trivia 'ThreadPool'] PrepareToWait: Starting new thread
2014-02-04T21:09:40.553-02:00 [02144 trivia 'ThreadPool'] PrepareToWait: Starting new thread

 

[Major] From: BSM@vcenter "vCenter"  Time: 04/02/2014 21:10:11

[61:2052]     Bar backup session was started but no client connected in 600 seconds.
    Aborting session!

 

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:10:32
    Virtual Machine 'VMACHINE-01' (UUID '42179ee6-1f07-a67b-1b14-197fbb4b5386'): Starting full backup ...


[Major] From: OB2BAR_VEPA_BAR@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:10:47
    Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:10:56
    Virtual Machine 'VMACHINE-02' (UUID '4212eb70-4ac7-7d58-202b-1a06ec508915'): Starting full backup ...

[Major] From: OB2BAR_VEPA_BAR@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:10:56
    Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

[Normal] From: VEPALIB_VMWARE_THREAD@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:10:59
    Virtual Machine 'VMACHINE-02' (UUID '564dc53f-e9c0-244e-6ad4-dee42c336d90'): Starting full backup ...

[Major] From: OB2BAR_VEPA_BAR@vcenter "/COMPANY-NAME"  Time: 04/02/2014 21:10:59
    Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

[...]

HP Expert
Bob_Clark
Posts: 1,486
Registered: ‎08-14-2013
Message 2 of 3 (749 Views)

Re: Scheduled VMware routine timeout (VEPA hanging)

Unless someone else in the Forum has see this before, I think that you will probably need to open a case with the response center, and have them debug a scheduled backup.  If it was me handling the case, I would also debug an interactive backup to have a basis of comparison

HP Expert
DeDa
Posts: 17
Registered: ‎09-04-2014
Message 3 of 3 (306 Views)

Re: Scheduled VMware routine timeout (VEPA hanging)

Hi,

 

First of all DP 7.x does not support VMware 5.5 so you should consider upgrading. If you don’t get this init phase done in 600 s (create snaps / resolve vms) so no Starting Backup for ... you will get this abort. It depends on the load on vCenter and how much this takes. I would suggest that you increase this timeout in global file.

 

Best regards,

Damir

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.