BackPak H4.00 Troubleshooting and Messages Manual

Messages
87 BackPak H4.00 Troubleshooting & Messages
Number Text Explanation Action
3334 Catalog type
discrepancy between
primary and secondary
domains for data store
%s. For this group,
volumes to import will
be cataloged in BackPak
catalog only.
The catalog type (NONE,
DSMTC, TMF, QTOS..) of
primary and secondary
volume groups does not
match.
The volume will be
imported in the list of
BackPak volumes, but
no action done in
DSM/TC.
3335 Invalid export id %s in
%s. File ignored.
The export-id (a
timestamp) read in an
export file is invalid.
This file looks corrupted
and is ignored.
Contact the Product
Support.
Re-execute export.
3336 FULL catalog import for
data store %s must be
executed. %s
Obsolete message Obsolete message
3337 Invalid content of
catalog export summary
file %s. (reason)
A summary file (UPDATE
or FULL) is invalid.
Examine the reason of
error included in the
message
3338 Invalid content of
catalog export volume
file %s. (reason)
A volume export file is
invalid.
Examine the reason of
error included in the
message
3339 (obsolete after 2.06)
Volume %s is cataloged
in volcat %s pool %s
with media type %s, but
registered in a BackBox
volume group
configured for type %s.
Volume loaded will
might not be accepted
by $ZSVR
Obsolete message Obsolete message
3340 Too many BBEXT timers,
%s %s timer not added.
The number of timers
managed by the EMS
Extractor for the domain
is too large.
Processing continues
without all timers.
Contact the Product
Support.
Monitor manually the
pending exports in the
PRIMARY data store
Catalog export status
page.
Eventually submit
manually export
updates