The "partially online" state can be normal in certain cases. In the
ordinary course of events, like a catalog backup for instance we may
lose contact with one of the "collectors'. When this occurs we will
attempt to re-engage that collector in 10 minute intervals. During
this period of time no data should be lost.

There are a couple of issues that concern me however.

If you have partially online all the time and it doesn't clear up then
 there is an unresolved defect that we need to fix and you would need
to open a support case. Since I have heard periodic reports of this
happening in the field I am motivated to help support and engineering
get to the bottom of it. I would appreciate it if you would please
send me your support case number directly, so I can track this issue.

I also believe that if we need to be better about when we display
"partially online" because it is most often interpreted as a state
where action needs to be taken. If your cluster management software
said that a service group was "partially online" you would want to
take action and quickly. I'm working with engineering to make this
distinction crisper in a future release.

-- 
tim burlowski
Technical Product Manager
Symantec



On Wed, Nov 12, 2008 at 8:32 AM,  <mkgunderson AT mmm DOT com> wrote:
>
> Ed,
>
> I'm not sure the issue is latency between the master in India and the NOM
> server here.  I also have NOM server (6.5.2) running and for whatever
> reason, I will see that my two masters running at 6.5.2a will at times go
> into partially on-line and stay there.  I usually have to cycle it off-line
> and then bring it backup on-line to clear the partially on-line condition.
>  I also have the 6.5.2 binaries on the NOM server, but that hasn't solved
> the issue for me either.
>
>
> Mike
>
> ----- Message from "Ed Wilts" <ewilts AT ewilts DOT org> on Tue, 11 Nov 2008
> 12:24:33 -0600 -----
> To:
> "VERITAS-BU AT mailman.eng.auburn DOT edu" <veritas-bu AT mailman.eng.auburn 
> DOT edu>
> Subject:
> [Veritas-bu] NOM 6.5.2 and offline master server
>
> I've got 2 master servers configured in NOM.  One master is at 6.5.2 (as is
> NOM) and is working fine.  However, the other master - in India - is at
> 6.5.1 and initially comes up online, then partially online, then goes
> offline.  Are there any logs to tell me WHY it's going offline?  Is it
> because of the latency between the NOM server and the master?  Backups at
> the other master are working fine and Aptare StorageConsole isn't have any
> grief with it.
>
> Where can I go to look to see why NOM doesn't like it?
>
> Thanks,
>    .../Ed
>
> Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
> ewilts AT ewilts DOT org
>
>
> Michael Gunderson
> mkgunderson AT mmm DOT com
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu