Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
775 views

Vmware integration with DP 6.11

I am having problems getting a vstorage backup to run in DP 6.11.

I have installed the latest patches as of May-18-2011 (DPWIN_00494 included).

 

I can configure my vcenter (4.1) and the configuration checks out OK, but when I try and run a backup of anything on it,

I get the following error:

 

[Normal]

From: BSM@baksrv01.cyoptics.com "vm-test_0"  Time: 5/20/2011 4:27:59 PM

OB2BAR application on "baksrv01.cyoptics.com" successfully started.

[2011-05-20 16:27:59.295 05256 info 'App'] Current working directory: C:\Windows\system32

[2011-05-20 16:27:59.295 05256 warning 'ThreadPool'] Illegal stack size value '0' in configuration file, setting to default = 0

[Major]

From: BSM@baksrv01.cyoptics.com "vm-test_0"  Time: 5/20/2011 4:28:03 PM

[

61:3003]  Lost connection to OB2BAR Backup DA named "ERROR"

on host BAKSRV01.cyoptics.com.

Ipc subsystem reports: "IPC Read Error

System error: [10054] Connection reset by peer

"

 

Does anyone have any idea what could be wrong?

0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Hello Gmitchell

 

Please check that firewall is properly configured

 

Firewall configuration

Ensure that the following ports are open:

443 –

on backup hosts, ESX(i) Server systems, and vCenter Server systems

This is the default value used by VMware. If VMware uses a different port, ensure that this port is open.

5555 –

on all Data Protector clients (this is a prerequisite for the general Data Protector installation procedure)

0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

There is no firewall involved.  The two machines are in the same data center, connected to the sam switch.

0 Likes
Micro Focus Expert
Micro Focus Expert

Vcenter and ESX server has a firewall integrated, please open connections.

 

Resetting the ESX host firewall policy in ESX 4.x

You cannot stop the firewall service in ESX 4.x. If you try, you see the message:
 
Firewall can't be stopped.  To disable the firewall run, esxcfg-firewall --allowIncoming --allowOutgoing 
 
You can allow all packets through the firewall by running the command:
 
esxcfg-firewall --allowIncoming --allowOutgoing 
 
To return the firewall configuration to its previous settings, run the command:
 
esxcfg-firewall --blockIncoming --blockOutgoing
 
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

We are running Esxi 4.1 which does not have a firewall.

0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

We have version ESXi 4.1.0 320137.  Note the "i" in the name.  This version does not have a firewall.

The directory /etc/vmware/firewall does not exist.

 

 

0 Likes
Absent Member.
Absent Member.

Hi,

 

Can you check Windows Application log in the time of failure? Are there any records on this issue?

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.