[Orca-users] Re: Orca problem

[Chris O'Regan]

Blair,

Is there a work-around for this?  On one of our system, we create a
volume snapshot of our database filesystems every night for backup
purposes.  This can take up to six hours to complete.  The snapshot
filesystems are not mounted while they are synchronizing.  As a
result, this is preventing all data from being plotted during this
time period, creating a virtual blackout.

The only thing I can think of doing is not defining "WATCH_DISK" in
orcallator.se, but that means I will not be able to watch the
performance of my database filesystems.


Thanks,

Chris

--- In orca-users at y..., Blair Zajac <blair at a...> wrote:
> Tomas,
>
> When orcallator.se sees a change in the system, say a filesystem
> is mounted or unmounted as you have done on your systems or an
> interface card is brought up or down, then orcallator.se will
> output data with a different number of columns then previously
> printed to the file to account for the new/deleted subsystems.
>
> When Orca sees a line in an input data file that does not have the
> same number of columns as defined at the top of the file, then Orca
> will complain and ignore the line.
>
> Regards,
> Blair