Forum Discussion

Do3e's avatar
Do3e
Level 3
13 years ago

BE 2012 Communication Stalled

Hi!

I just installed trial BE 2012 CAS on Windows 2008 R2 and installed one BE Managed Server on Win 2008 R2.

This servers in different subnets and connected via VPN.

I added Storage (local disk) on Managed Server and made a job on CAS, which is backuping Managed Server to localdisk.

After I started the job it is stopping with status "Commutication Stalled", then status changes on "Recovered".

When i made the same job on Managed Server, ran it - it is succesed.

So. What I did wrong?

 

Sry for my eng.

  • Found a solution...

    It is very stupid to allow to install Managed Server on remote server with FQDN like BEMS.subdomain1.domain.com. Cause Job engine cant communicate with BEMS via FQDN.

    (not sure you can understand me :) )

    So I just added BEMS.subdomain1.domain.com as BEMS to HOSTS file in C:\Windows\System32\drivers\etc dir.

    Now its working. 

5 Replies

  • In a CASO environment, communications that occur between managed Backup Exec servers and the central administration server can sometimes be disrupted even if network communications are normal. If job-related communication disruptions occur between a managed Backup Exec server and the central administration server, the managed Backup Exec server's communication status changes from Enabled to Stalled or No Communication. The jobs waiting to be processed by the managed Backup Exec server are held in the managed Backup Exec server's job queue until the communications are restored.

    You can set the amount of time that Backup Exec waits before changing the managed Backup Exec server's status if it becomes unresponsive. When a managed Backup Exec server's status changes to Stalled or No Communication, the central administration server changes how it handles current and future jobs delegated to the stalled managed Backup Exec server.

    For example, if communications from a managed Backup Exec server are not received at the central administration server after the set amount of time, the central administration server changes the Backup Exec server's communication status to Stalled. Job delegation to the managed Backup Exec server is suspended as it continues to wait for the managed Backup Exec server to return to an Enabled status. Jobs are delegated to other managed Backup Exec servers that are represented in the destination storage device or Backup Exec server pool.

    CASO continues to monitor the amount of time during which no communications are received from the managed Backup Exec server. After a set amount of time passes after a Stalled status appears, CASO changes the status of the managed Backup Exec server to No Communication. CASO marks the jobs as Failed, and then begins job recovery by invoking the custom error-handling rule Recovered Jobs for any job that is active at the time the No Communication status appears.

    Please refer to following Technote for more details ::

    http://www.symantec.com/docs/HOWTO73648 (What happens when CASO communication thresholds are reached)

    Hope this helps.

  • Thanks for you reply.

    Managed Backup Exec Server state is always online. Even if on the "Backup and Restore" tab job status is "Stalled", on the "Storage" tab server state is always Online.

    Also I can see remote storages properties in the CASO environment. But when i tried to change it properties I saw a storage icon changed with pencil crossed by red line and the state still "Online".

    I there a way to check the connection? Is it compatible with MS ISA Server? Asking cause VPN connected through ISA Server.

  • UPDATE.

    Found why icon changed. Its not a problem.

    But changed properties didnt migrate from CAS to Managed Server. State still "online"

  • No solution?

    Looks like I have to try other products...

  • Found a solution...

    It is very stupid to allow to install Managed Server on remote server with FQDN like BEMS.subdomain1.domain.com. Cause Job engine cant communicate with BEMS via FQDN.

    (not sure you can understand me :) )

    So I just added BEMS.subdomain1.domain.com as BEMS to HOSTS file in C:\Windows\System32\drivers\etc dir.

    Now its working.