Robot state - Disconnected - Veritas Backup Exec

This is a discussion on Robot state - Disconnected - Veritas Backup Exec ; Hi, I'm using netware 5.1 sp7 with veritas backup exec 9.10 revision 1152 on all my servers. My primary backup server has a HP ESL9326 tape library attached. I have around 6 remote servers that backup to this library. It's ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: Robot state - Disconnected

  1. Robot state - Disconnected

    Hi,

    I'm using netware 5.1 sp7 with veritas backup exec 9.10 revision 1152 on all
    my servers. My primary backup server has a HP ESL9326 tape library
    attached. I have around 6 remote servers that backup to this library. It's
    working fine except for two remote servers that suddenly come up with the
    Robot state disconnected in the drives\robots option in the Backup exec
    administration console. All the other servers have it enabled and all good.
    Does the primary server advertise this to the remote ones?? All servers can
    see each other via ping. I've tried unloading/reloading drivers etc.
    Rebooted primary and remote servers but still the remote servers see the
    robot as disconnected.
    Any ideas would be much appreciated.
    King regards,
    Mick.



  2. Re: Robot state - Disconnected

    First, I'm assuming that when you say "remotes" you mean "group
    servers" (secondary media servers) and not remote agents.

    On the BE Admin Console menu at the primary media server go to
    Options|Media Server|Shared Devices. Verify that the server is in fact
    the primary, and that your secondaries are listed as Backup Group
    Members.

    If everything looks good there, try changing one of the secondaries to
    be the primary and see if it all sorts out.

    -Barry.


  3. Re: Robot state - Disconnected

    Thanks Barry,
    Yes sorry about that, I do mean secondary servers. Yep they are listed as
    backup grp members.
    If I change a secondary to primary does this require a reboot and is it
    simple enough to swap back to the original primary?
    Reason I ask as it's a very ficle system and I've only been working here for
    a few days so not fully up to date on how it works.
    Thanks,
    Mick.


    "Barry St.John" wrote in message
    news:VA.0000004b.01bcda1c@adoanotfbugpme.org...
    > First, I'm assuming that when you say "remotes" you mean "group
    > servers" (secondary media servers) and not remote agents.
    >
    > On the BE Admin Console menu at the primary media server go to
    > Options|Media Server|Shared Devices. Verify that the server is in fact
    > the primary, and that your secondaries are listed as Backup Group
    > Members.
    >
    > If everything looks good there, try changing one of the secondaries to
    > be the primary and see if it all sorts out.
    >
    > -Barry.
    >




  4. Re: Robot state - Disconnected

    I've also gone into shared media in the admin console and tried to just make
    sure it's still set to secondary backup. Pressed f2 and get "unable to
    contact to the primary group server". It can ping the server ok so maybe
    its a Bexec protocol problem. Would this be NDMP??


    "Barry St.John" wrote in message
    news:VA.0000004b.01bcda1c@adoanotfbugpme.org...
    > First, I'm assuming that when you say "remotes" you mean "group
    > servers" (secondary media servers) and not remote agents.
    >
    > On the BE Admin Console menu at the primary media server go to
    > Options|Media Server|Shared Devices. Verify that the server is in fact
    > the primary, and that your secondaries are listed as Backup Group
    > Members.
    >
    > If everything looks good there, try changing one of the secondaries to
    > be the primary and see if it all sorts out.
    >
    > -Barry.
    >




  5. Re: Robot state - Disconnected

    Doesn't require a reboot, just BESTOP|BESTART. Best to do that on all
    servers in the group.

    It's very easy to change back, as well.

    -Barry.




  6. Re: Robot state - Disconnected

    As far as I know, it shouldn't be an NDMP issue as you don't typically
    have one media server back up another. NDMP mostly comes into play
    with the remote agents. Michael might be able to shed some more light
    on this.

    Go to your primary and look at the Shared Devices settings under
    Options|Media Server. Under Primary Group Information note the context
    and name of the BE_ESI group. Then check your secondaries that they
    have the same info. You might have inadvertently created a second
    group somewhere.

    Since this group object is a regular NetWare user group object, you
    can't add servers to the group membership using traditional tools like
    NWAdmin or ConsoleOne. This is because NetWare expect only users to be
    members of a group.

    So if all your media servers are pointing to the same group, but you
    are having group issues, the only way to fix it is the delete the group
    using NWAdmin, ConsoleOne, or iManager. Shut down all your media
    servers first. After you've delete the group object start your primary
    media server. BE will complain to you that you have SSO but it's not
    configured. So go to Options|Media Server|Shared Devices and configure
    the primary to be the primary. The fire up the secondaries and
    designate them as such in the same way. This process will recreate
    your BE_ESI group.

    BUT before you do any of that, I'm wondering if this isn't an SMDR
    issue. Unload BE and all of your TSAs. Then unload SMDR. If it won't
    unload because of a module dependency, unload those dependent modules,
    as well. Just keep track so you can reload then after. Once SMDR is
    unloaded, type SMDR NEW at the server console. You'll get some
    prompts. Depending on the version of SMDR the prompts could vary.
    Configure SMDR to have SLP enabled, NDS disabled, use TCP/IP instead of
    IPX/SPX. Whether or not to use HOSTS file for name resolution is up
    to you. If you have more than one network interface you should be able
    to select which one should be used for SMDR.

    Once you've answered all of the prompts SMDR is configured and loaded.
    You can now reload any of those dependent modules, TSAs, etc. Then
    BESTART. Can't hurt to do this on all of the media servers, just to be
    sure they're all using the same config options. There's no reboot
    required for this.

    If reconfiguring SMDR doesn't fix things, then go with the above steps
    for recreating your BE_ESI group.

    -Barry.


  7. Re: Robot state - Disconnected

    Barry,
    you're a genius. I checked the context in shared media and both the problem
    servers were pointing to a BE_ESI group in a different context to the rest.
    I checked the correct group and both problem servers are members of the
    group so I edited their context in shared media and all is good now. Don't
    know how they were set wrong or how they worked before, as I'm new in here.
    Delighted to get that fixed.
    Thanks again for the help.
    Mick.

    "Barry St.John" wrote in message
    news:VA.0000004e.00483052@adoanotfbugpme.org...
    > As far as I know, it shouldn't be an NDMP issue as you don't typically
    > have one media server back up another. NDMP mostly comes into play
    > with the remote agents. Michael might be able to shed some more light
    > on this.
    >
    > Go to your primary and look at the Shared Devices settings under
    > Options|Media Server. Under Primary Group Information note the context
    > and name of the BE_ESI group. Then check your secondaries that they
    > have the same info. You might have inadvertently created a second
    > group somewhere.
    >
    > Since this group object is a regular NetWare user group object, you
    > can't add servers to the group membership using traditional tools like
    > NWAdmin or ConsoleOne. This is because NetWare expect only users to be
    > members of a group.
    >
    > So if all your media servers are pointing to the same group, but you
    > are having group issues, the only way to fix it is the delete the group
    > using NWAdmin, ConsoleOne, or iManager. Shut down all your media
    > servers first. After you've delete the group object start your primary
    > media server. BE will complain to you that you have SSO but it's not
    > configured. So go to Options|Media Server|Shared Devices and configure
    > the primary to be the primary. The fire up the secondaries and
    > designate them as such in the same way. This process will recreate
    > your BE_ESI group.
    >
    > BUT before you do any of that, I'm wondering if this isn't an SMDR
    > issue. Unload BE and all of your TSAs. Then unload SMDR. If it won't
    > unload because of a module dependency, unload those dependent modules,
    > as well. Just keep track so you can reload then after. Once SMDR is
    > unloaded, type SMDR NEW at the server console. You'll get some
    > prompts. Depending on the version of SMDR the prompts could vary.
    > Configure SMDR to have SLP enabled, NDS disabled, use TCP/IP instead of
    > IPX/SPX. Whether or not to use HOSTS file for name resolution is up
    > to you. If you have more than one network interface you should be able
    > to select which one should be used for SMDR.
    >
    > Once you've answered all of the prompts SMDR is configured and loaded.
    > You can now reload any of those dependent modules, TSAs, etc. Then
    > BESTART. Can't hurt to do this on all of the media servers, just to be
    > sure they're all using the same config options. There's no reboot
    > required for this.
    >
    > If reconfiguring SMDR doesn't fix things, then go with the above steps
    > for recreating your BE_ESI group.
    >
    > -Barry.
    >




  8. Re: Robot state - Disconnected

    Glad to help!

    -Barry.


+ Reply to Thread