BackPak H4.00 Troubleshooting and Messages Manual

Messages
102 BackPak H4.00 Troubleshooting & Messages
Number Text Explanation Action
3421 DSM/TC must be
replicated to a dedicated
catalogue. %s %s
cannot be the replication
target for Volume group
%s %s, because it is
also updated by Volume
group %s. This check
can be disabled in the
'Catalog Sync Import'
page of the Data store
configuration.
The DSMCT volcat or
filecat configured for a
Secondary Data store or
associated Volume
group, is also used by
another secondary Data
store or by local
backups (i.e. Primary
Data store).
The different sources
updating this catalogue
creates a risk of collision
on TAPEVOLUME labels,
and even more on
TAPEFILE fileid, leading
to data corruption in
DSM/TC.
If the user is able to
manually control the
unicity of TAPEVOLUME
and TAPEFILE in the
merged catalogue,
this check can be
disabled in the
Catalogue Import
configuration of the
Data store by checking
“Allow to store
replicated DSM/TC
entries in a local
DSM/TC catalogue that
is not dedicated to this
replication (i.e. merged
with other replications
or with local backups)”
3422 Error %ld while opening
FULL file in the export
destination '%s'. Export
of data store %s
catalogs aborted.
Guardian rejects the
opening of the control
file in the export staging
area.
Check the Guardian
error code and the file
name (FULL qualified
by the export
destination).
The most common
error is the remote
export destination is
not available.
Wait for reconnectd
Expand to re-submit
FULL export.
3423 Data store %s has no
route with functional
encryption for Key
manager %s.
No VTC configured as a
route to the named Data
store can present a
virtual tape with
functional encryption.
Fix BackPak
configuration (or wait
for VTCs be started)
3424 VTC %s is not an active
route for any Volume
group referring the Key
manager %s. Key
manager client
connectivity from %s is
not needed to encrypt
new backups, but might
be required to decrypt
old volumes that were
encrypted with different
Volume group
configuration
A VTC is configured as a
client of the Key
Manager, but this client
is not needed for any
new backup in this
domain – but might be
needed for restore.
This might be a valid
intermediate while the
implementation of
encryption is not
completed.
Don’t forget to actually
enable the encryption
in the Volume groups.