Data Protector - Passion for Data Protection

data-protector.org

Home » HowTo » Virtual Environment Backups (VMware) to StoreOnce aborting randomly

Virtual Environment Backups (VMware) to StoreOnce aborting randomly

Posted on by 8 Comments

When backing up virtual machines using the Virtual Environment Integration (VE) to a Catalyst Gateway (StoreOnce), with Data Protector 7.01 (current patches) the VEPA backups might aborting randomly. The error message displayed:

[Major] From: BSM@server.demo.local "VE_Backup_VMware"  Time: 15/07/2013 10:03:03
[61:3003]      Lost connection to BMA named "StoreOnce_01_GW1 [GW 2296:4:26641437476]"  
        on host server.demo.local.
        Ipc subsystem reports: "IPC Read Error
        System error: [10054] Connection reset by peer

To fix the problem the omnirc parameter OB2D2D_BANDWIDTH_BUFF_SIZE=20 can be used on the Media Agent. The value for parameter is set to 10 by default in Data Protector 7.01, when using the value 20, the problem is not seen. In Data Protector 8.00 the problem is not seen, as the default value is already set to 20.

8 thoughts on “Virtual Environment Backups (VMware) to StoreOnce aborting randomly”

  1. Ich habe den gleichen Fehler.
    Leider kann ich den Wert bei mir unter dem Pfad C:\programdata\omniback\omnirc
    nicht finden.
    ich nutze HP DP 7.01

    • Hi Matthias,

      Die Datei gibt es dann wohl noch nicht, Schau mal nach der Template Datei.

      Grüße
      Daniel

  2. Hi Daniel
    Great Job and thanks for all your hard work that you have put into this site!!

    To add to your tip here a note I would like to add is that if this client was already on version 7.x and then upgraded to 8, the upgrade does not replace the omnirc or omnirc.tmpl with a new one. The old one stays in place so any customer that might be running into this error and had upgraded to 8 and still having the issue still needs to go and edit the parameter you listed in your tip because the default remains at 10.

    Thanks
    Geoff

    • Thx Daniel and Geoff

      We run into the same problem with DP8.1 and Geoff is right, even in DP8.1 the default value was 10. So we changed to 20 and the problem was solved.

      Regards
      Marco

  3. Hi..

    I am seeing this with a brand new installation of DP8.1 and ESX 5.5

    I’ll report back when I have implemented this fix..

  5. Hello, i have the same problem with ESXI 5.5 and DP8.10
    if you have a solution for this mess please post it here.

    thank you.

    • Hi Matan,

      maybe the last article – the customer advisory c04318203 helps.

      Best regards
      Daniel

Comments are closed.