Hi everybody:

At enterprise, we are working with 'Veritas NetBackup Datacenter 3.4GA' on a
IRIX master server.

We have several clients of different platfforms (NT, W2K, Solaris, IRIX)

Almost 99 % of backups are working correctly; however, we have noticed the
next error messages appearing when we executing the 'Report, Problems'
option at the GUI application (onto the 'Media Management' icon)

Basically, the question is: despite the final status backup is '0' or '1' in
almost of the cases, anybody kowns the meaning of none/ all of these error
messages?

Note none of the messages have relation among them, so are from several
clients.

Note it doesn't mean if you don't know the origin of all the errors, too; if
you know the response for just only one, it will be alright (better that
than nothing)

Many thanks in advanced!



06/20/2001 23:15:33 sbackup -  Bad image header: MSS_3_0991450818_FULL ===>
IS THE DATA CARTRIDGE SPOILED (BAD STATE)OR SOMETHING ELSE???


06/21/2001 00:11:01 sbackup opsb  from client opsb: WRN - Could not reset
access
                    time of /etc/mnttab


06/21/2001 02:01:30 sbackup lab-web-1b  from client lab-web-1b: WRN -
/empresa
                    is only being backed up as a symbolic link ===> IT MEANS
IS JUST BACKING UP THE LINK, AND NOT THE CONTENTS???


06/24/2001 21:12:34 sbackup desicom1b  backup of client desicom1b exited
with
                    status 134 (unable to process request because the server
                    resources are busy) ===> THIS ERROR IS VERY FREQUENT FOR
US. IT MEANS THE SERVER HAVE NOT ENOUGH RAM OR CPU POWER, MAYBE?


06/25/2001 06:38:34 sbackup bpexpdate  Could not update media list, file
read
                    failed


06/25/2001 20:24:06 sbackup analic  from client analic: WRN - Content
Indexing
                    Server: unable to pause catalog: System (some files may
                    not get backed up) ===> IS THIS ERROR CAUSED BY THE
"INDEXING SERVER" ON W2K? THE ERROR DISSAPEARS IF I STOP THE SERVICE?


06/29/2001 00:01:16 sbackup netra  from client netra: WRN - Unsupported
                    parameter: -use_otm ===> I DON'T KNOW WHY IS THIS ERROR
APPEARS IN A SOLARIS CLIENT!! (OTM JUSTS ACTIVATE ITSELF ON W2K CLIENTS!)


06/29/2001 22:08:35 sbackup analic  unable to obtain db handle for Media
Manager
                    query on host sbackup, network protocol error


06/29/2001 22:08:35 sbackup analic  backup by Administrator on client analic
                    using class SQL_ANALIC:  Media Manager volume daemon
(vmd)
                    is not active ===> THIS ERROR IS VERY FREQUENT ON W2K
CLIENTS. IT STOPS APPEARING IF THE SERVICE IS RESTARTED.


06/30/2001 06:00:54 sbackup plutonium  from client plutonium: WRN - attr_get
                    valuelength 3 != attr_list a_valuelen 17 for /ns/


07/01/2001 01:54:09 sbackup peterpan  from client peterpan: ERR - File
                    /nsr/index/netra/db/sr.0 shrunk by 309321728 bytes,
                    padding with zeros ===> IT MEANS SOME KIND OF SIZE
VARIATON BETWEEN THE SNAPSHOT TIME AND THE REAL BACKUP TIME?

07/08/2001 20:33:17 sbackup webn3b  from client webn3b: WRN - Removable
Storage
                    Management: unable to export database (WIN32 112: There
is
                    not enough space on the disk. ) ===> IT EXISTS ONLY ONE
PARTITION ON THE CLIENT, WITH NEARLY 17 GB HDD FREE!!

07/07/2001 20:26:32 sbackup desicom1b  from client desicom1b: FTL - tar file
                    write error (10053)


07/07/2001 20:26:34 sbackup -  cannot read from media socket 6
07/07/2001 20:26:35 sbackup -  Cannot read from parent socket 0, I/O error
(5)

07/08/2001 00:03:10 sbackup descal1b  from client descal1b: ERR - Cannot
write
                    to STDOUT. Errno = 32: Broken pipe


07/08/2001 00:03:11 sbackup -  could not write BACKUP START to media manager
                    socket



Mario Pareja Nieto
Área de Sistemas-OPENET
Iddeo-Retevisión I, S. A.
mailto:mpareja AT iddeo DOT es