Forum Discussion

AndreyGo's avatar
AndreyGo
Level 3
5 years ago

Veritas 16 remote backups errors E000EF30 and E00084F8

Hi all, we are backing up two physical servers over a wan with two meraki MX-84 appliances between two sites and 100Mb/s fiber line. With a smaller in size domain controller back up we have no issu...
16
Windows Server 2012 R2
  • AndreyGo's avatar
    AndreyGo
    5 years ago

    I figured it out, we have a policy in our domain that blocks power shell access, it is enforced by a third party via Carbon

    Black AV mgmt console. I noticed in the event viewer in the application logs that beremote.exe was blocked from accessing

    the PS 3-5 minutes before each time backup would fail. Placing the server in a policy that allows the invocation and

    execution of PowerShell solved the issue. 

    Thanks

Gurvinder's avatar
Gurvinder
Moderator
5 years ago

It could be those devices disrupting the connection due to KeepAlivetime settings

Can you create a dword "KeepAliveTime" and set it to decimal value 5000 , reboot the BE server and check if it helps
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

  • AndreyGo's avatar
    AndreyGo
    Level 3
    5 years ago

    Thanks, added the registry key and running a full backup now, will update once completed

  • AndreyGo's avatar
    AndreyGo
    Level 3
    5 years ago

    Same error E00084F8 - The job failed with the following error: The network connection to the Backup Exec Remote Agent has been lost. Check for network errors.

    Stopped this time at 208Gb, about 1/3 of the full backup. Any other suggestions?

    Thanks!

    • AndreyGo's avatar
      AndreyGo
      Level 3
      5 years ago

      I figured it out, we have a policy in our domain that blocks power shell access, it is enforced by a third party via Carbon

      Black AV mgmt console. I noticed in the event viewer in the application logs that beremote.exe was blocked from accessing

      the PS 3-5 minutes before each time backup would fail. Placing the server in a policy that allows the invocation and

      execution of PowerShell solved the issue. 

      Thanks