> From: fx [François-Xavier Peretmere] [mailto:fx AT veritas DOT com]
> Sent: Tuesday 30 January, 2001 13:48

> > We have a 3.4 master/media set, and when backing up any 2.5.1
> > clients (using 3.2, latest patch, Veritas services built the
> > package for us, etc, etc), we get this error. Yet the backup
> > succeeds. Seems like either a program bug or documentation
> > bug that this gets thrown out to clients (Solaris) that
> > aren't capable of using OTM. Maybe it gets tacked onto all
> > backups with a yes/no at the end of the switch?

 ok, i remember now. i had this message for a Solaris client
with 3.2 client. problem was because of a failed patch install,
some binaries (bpbkar i believe) were still the old version,
and causing the problem. manually replacing the binaries solved
my problem.

 don't have time now but there should be a technote somewhere in
the support site i think.

 strings and grep for $Rev in the binaries to verify if everything
is up to date.

 fx

#include <std_disclaimer.h>

--
     fx AT veritas DOT com       | To have no errors
François-Xavier Peretmere | would be life without meaning.
 http://www.veritas.com/  | No struggle, no joy.