IBM®
Tivoli® Storage Manager V7.1.2 client messages are listed in
ascending numeric order. The complete message is documented, including message ID, message text,
explanation, system action, and user response.
ANS0101E
Unable to open English message repository file name.
ANS0102W
Unable to open the message repository file name.
The American English repository will be used instead.
ANS0103E
Error trying to read header record from message repository file
name.
ANS0105E
Error trying to read index for message number from
repository file name.
ANS0106E
Message index not found for message number.
ANS0107E
Error trying to read header for message number from
repository file name.
ANS0108E
Error trying to read text for message number from
repository file name.
ANS0109E
Insufficient memory for allocation of message structure.
ANS0110E
Unable to open error log file file name for output.
ANS0113E
Message repository file name has an invalid control
record.
ANS0118E
Unable to open schedule log file 'file name' for
output.
ANS0119E
Error trying to read response string for message number from
repository file name.
ANS0120E
Message number number contains an invalid multibyte
sequence for the current locale.
ANS0121W
Unable to open the iconv converter for the message repository file
name. The American English repository will be used instead.
ANS0348E
Operation failed because the copy continue option was
set to NO.
ANS0349E
Transaction failed because of a problem during a store
operation.
ANS0350E
The current client configuration does not comply with
the value of the DATAWRITEPATH or DATAREADPATH server option for this
node.
ANS0351E
The node or user does not have proper authority to perform
this operation
ANS0352E
The operation is not permitted due to server licenses
values.
ANS0353E
When
using useTsmBuffers, dataBlk must be NULL in calls to dsmSendObj and
dsmGetObj.
ANS0354E
Encryption
is not allowed when using useTsmBuffers.
ANS0355E
This
object cannot be restored/retrieved using useTsmBuffers, because it
is compressed.
ANS0356E
This
object cannot be restored/retrieved using useTsmBuffers, because it
is encrypted.
ANS0357E
When
using useTsmBuffers, a restore/retrieve with partial object restore
is not allowed.
ANS0358E
No
encryption key was found. If you are using -encryptkey=prompt make
sure there is a value in the encryptionPasswordP field and that bEncryptKeyEnabled
is set to true.
ANS0359E
Conflicting
encryption key options have been specified.
ANS0360E
The CAD cannot start because the value of the MANAGEDSERVICES
option is NONE.
ANS1024E
Failed to update backup attributes on server for 'backup
type' backup for 'filespace namepath-namefile-name',
object id 'object-id:object-id' return
code 'return code'.
ANS1034E
The
specified TCP/IP host name is unreachable
ANS1035S
Options
file 'file-name' could not be found, or it cannot be
read.
ANS1036S
The option 'option' or the value supplied
for it is not valid. It was found in options file 'file-name' at
line number: number The complete entry:
'entry'
ANS1047E
The destination file system is unavailable. The following
object was skipped: File space:'filespace-name'
Pathname:' path-name' Filename:'file-name'
ANS1052E
Direct connection to the Storage Agent is not allowed.
ANS1053I
Existing file space filespace-name has been
renamed to filespace-name
ANS1054E
Existing filespace filespace-name cannot be
renamed to new filespace filespace-name. TSM return
code = retcode.
ANS1055I
Trying to rename existing filespace filespace-name to
new filespace filespace-name, but drive letters
do not match, old=drive-letter, new=drive-letter.
Ignore the old filespace and backup to the new filespace.
ANS1056E
Share/network path share cannot be resolved.
Path does not exist.
ANS1057I
File space filespace-name cannot be renamed
to new file space filespace-name, because the
new file space already exists.
ANS1058E
The restore destination cannot be reached.
ANS1059E
Two inactive objects with the same image name were selected.
Process terminates
ANS1060E
The specified path is not a mounted filesystem
ANS1061E
The specified device corresponds to a mounted file system;
you must specify the file system by name.
ANS1062E
Only a single image may be selected when a destination is
entered.
ANS1063E
The specified path is not a valid file system or logical
volume name.
ANS1064E
An unexpected error occurred while processing the image operation.
ANS1065E
Library version of the image utility does not match that
of the TSM API
ANS1066E
The restore operation completed successfully, but the file
system could not be remounted.
ANS1067E
A call to a system function returned an unexpected error.
ANS1115W
File
'file-namefile-namefile-name'
excluded by Include/Exclude list
ANS1116E
The
process is running in a non-interactive mode, but requires user input.
ANS1117E
The PICK and LATEST options are not valid together
ANS1118I
Invalid file space number entered. Try again.
ANS1119I
Initiating the removal of 'filespace-name'
file space.
ANS1120E
Removal of file space 'filespace-name' failed
ANS1121I
A request for removal of file space 'filespace-name'
has been successfully sent to the server.
ANS1122W
File space 'filespace-name' does not exist
on the server. The file space might have been deleted by another
client using your client's node name or an administrator.
ANS1123E
The vertical screen dimension is too small to display the Help
directory. Increase your window height.
ANS1181E
There was a communication failure with the journal service.
ANS1183E
An unknown error occurred while processing system object
'sys-obj-name': MS API function 'func-name'
failed with error error (error)
ANS1184W
The command subcommand command
is not supported on this client.
ANS1185E
The help search argument you supplied "string"
is either too long or contains unmatched quotes.
ANS1186I
The help file contains no message help section. Requests
for message help will all result in topic not found. Enter
a section number, option name, command name, or a command and
subcommand. Otherwise press enter or 't' to display the table
of contents or 'q' to exit help:
ANS1187E
The named helpfile "filename" has invalid
content.
ANS1188E
The selected filesystem is managed by HSM, and therefore
is not a valid object for image operations
ANS1189E
The DIRSONLY and V2ARCHIVE options are not valid together
ANS1190E
Symbolic link 'linkname' to 'target'
was successfully deleted.
ANS1259E
The image snapshot operation failed. Diagnostic text: diag_text.
ANS1260E
File is being recalled or has been recalled.
ANS1261W
The archive description you specified is the empty string. TSM will
use the default description (Archive Date: current date).
ANS1262E
The password is not updated. Either an invalid current password
was supplied or the new password does not fulfill the server password
requirements.
ANS1263E
The active policy set does not contain any backup copy groups.
The backup operation can not continue.
ANS1264E
The active policy set does not contain any archive copy group.
The archive operation cannot continue.
ANS1265E
Encountered bad mount or filesystem, processing stopped.
ANS1266E
Encountered bad mount or filesystem, processing stopped.
ANS1267E
The management class for file file-name does
not allow migration. This file will not be migrated.
ANS1271E
The compressed file is corrupted and cannot be expanded
correctly.
ANS1272W
Adaptive subfile backup has been configured on the client
but the server doesn't allow this type of backup. Adaptive
subfile backup will not be used for this operation.
ANS1330S
This node currently has a pending restartable restore session. The
requested operation cannot complete until this session either completes
or is canceled.
ANS1331E
Only
a TSM authorized user can perform this Action.
ANS1332E
Run the '... for Administrators' version of the application.
ANS1334W
Volume mount point 'filespace namepath-namedir-name'
was not restored because the target directory is not empty.
ANS1335E
The RSM database files could not be restored.
ANS1336I
RSM service must be restarted for changes to become effective.
ANS1377W
The client was unable to obtain a snapshot of 'volname'.
The operation will continue without snapshot support.
ANS1378E
The snapshot operation failed. The SNAPSHOTCACHELocation
does not contain enough space for this snapshot operation.
ANS1379E
The snapshot operation failed. The percent of space to use
for the SNAPSHOTCACHELocation, specified via the SNAPSHOTCACHESize,
has been exceeded.
ANS1380W
The snapshot operation failed. The filesystem write activity
prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait
and SNAPSHOTFSIDLERetries options.
ANS1381W
On volumes that are RAW or formatted FAT32 the snapshot cache
location cannot be located on the same volume that is being backed
up.
ANS1382E
Server does not allow client-initiated connections for
this node.
ANS1441E
Keyword Expected after keyword 'keyword'.
ANS1442E
Extraneous argument 'input' after keyword
'keyword'
ANS1443E
Invalid argument 'input' after keyword 'keyword'
ANS1444E
An error occurred creating the Event Log backup directory
structure
ANS1445E
ERROR: could not create NAS image object.
ANS1446E
VSS ASR backup document (ASRBackupDoc.xml) not found.
ANS1448E
The command command is not supported by the
current server.
ANS1449W
A non-critical, unexpected error was encountered. Deletion
of a snapshot(Set/Volume) failed. Probable cause, snapshot does not
exists anymore. Continuing Process... TSM snapShot ID
: snapshot-id TSM function name : function-name
TSM function : function-desc TSM return
code : TSM-rc TSM file : file-name (line-number)
ANS1450W
The -FILENAME option was specified without a file name. Output
will be written to filename.
ANS1453W
The IMAGEGAPSIZE option is not supported for non-NTFS file
systems. The entire volume will be backed up.
ANS1454W
Used blocks information could not be obtained for name.
The entire volume will be backed up.
ANS1458I
OBF file for volume name is too small for
server-free data transfer.
ANS1459E
VSS Automated System Recovery (ASR) failed.
ANS1495S
Invalid virtual mountpoint filespace-name:
Other error, rc = return-code.
ANS1496W
Duplicate include/exclude option 'option file-name'
found while processing the client options file. This might
produce unexpected results.
ANS1497W
Duplicate include/exclude option 'option file-name'
found while processing the client options passed by the server. This
might produce unexpected results.
ANS1498E
The IIS services failed to stop. No files will be restored.
ANS1500E
Module dsmtca not found in secure directory.
ANS1501E
Trusted agent execution/owner permissions are invalid
ANS1502E
Access to system function required to run has been denied
ANS1503E
Valid password not available for server 'server-name'. The
administrator for your system must run TSM and enter the password
to store it locally.
ANS1504E
Error
starting the Trusted Communication Agent process.
ANS1505W
Performing image backup of the entire volume for volume
name. The IMAGEGAPSIZE option value of image gap size is
being ignored as this level of the operating system does not support
used block image backup. Please upgrade to AIX 5.3 Maintenance Level 7 or later in order to
perform used block image backup.
ANS1506E
The TSM Trusted
Communication Agent received an invalid request.
ANS1507E
This
action requires TSM administrative authority on this system.
ANS1519E
Your node does not have permission to delete backup files
ANS1520E
Failure writing to the Tivoli Storage
Manager error log: errno = errno-value,
ANS1521E
Failure writing to a Tivoli Storage
Manager log or log-related file: file-name, errno = errno-value, reason
ANS1522E
It is not possible to authenticate with the client node client-node ! The Space Management Agent version agent-version running
on client-node does not match with the Space
Management Console version console-version you
are running !
ANS1523E
An error occurred while connecting to TSA/SMDR service.
ANS1528I
TSM is converting the log-file from continuous
(pruning) mode to wrapping mode. This process may take several minutes.
ANS1529I
TSM is converting the log-file from wrapping
mode to continuous (pruning) mode. This process may take several minutes.
ANS1563W
The itsm.was.properties file does not exist.
ANS1565E
No WebSphere EARExpander
was found. Copy the EARExpander tool from the base WebSphere bin directory to
the instance bin directory, then run the restore operation again.
ANS1566E
The version of WebSphere on
the machine does not match the version of WebSphere that was backed up. These versions must
match for a WAS restore operation.
ANS1567I
A 5.2.2 or higher client is restoring data backed up from
a 5.2.0 client. No version check can be performed before the restore.
ANS1568E
The CAD attempted to register it's tcpport and tcpip address
without using the TCPCADADDRESS option.
ANS1569E
The CAD attempted to register it's tcpport and tcpip address
but the TCP/IP address resolved to the loopback address and was rejected
by the server.
ANS1570E
Registering this instance of the Cad with the server failed.
Cad process continues.
ANS1571E
The time-option option cannot be used without
specifying the date-option option
ANS1572E
An unexpected error was received from the server query, RC=re
tcode.
ANS1573E
FROMDATE and TODATE cannot be used with PITDATE.
ANS1576W
Space Management Agent version mismatch. The
Space Management Agent (hsmagent) version agent-version running
on 'client-node' client node does not match with the Space
Management Console (GUI) version console-version you
are running! To avoid compatibility problems, please
use the same version for the Space Management Console and
the Space Management Agent. Do you want to proceed?
ANS1577I
The Windows console
event handler received a 'event' console event.
ANS1578E
The specified path 'path' is not valid for
backup or archive.
ANS1579E
GSKit function func-name failed with error-code: session
ANS1580W
An Include.Fs statement with performance algorithm set already
exists for the drive specified. Do you want to replace the statement?
ANS1581W
'object-name' was restored as 'temp-name'.
A reboot is required to complete the restore.
ANS1583E
The Hardware Utility plug-in module was not found or could
not be loaded.
ANS1584E
Error loading system library 'libdevmapper.so' required for
image operations for LVM2 volumes.
ANS1587W
Unable to read extended attributes for object object-full-name due
to errno: errno-value, reason: errno-explanation
ANS1614E
The Domino plugin
'Try and Buy' license has expired.
ANS1615E
The Domino plugin
operation failed due to a license error.
ANS1616E
The Domino plugin
operation failed because the Lotus Domino API could not be loaded.
ANS1617E
The Domino plugin
operation failed because of a Data Protection for Domino API error.
ANS1618E
A Domino plugin
operation is already in progress. Please wait for operation to complete.
ANS1619E
The IBM Tivoli Storage Manager application client cannot work with the version
of the Domino plugin you
have installed.
ANS1621E
Failed to update backup attributes on server for local backup
for 'filespace namepath-namefile-name',
object id - 'object-id':'object-id'
return code 'return code'.
ANS1622I
Number of backup objects cleaned up on server: 'number'
number of local snapshot resources made available :'number'.
ANS1623W
Backup of NSF DB2 database
was skipped. NSF DB2 databases
not supported.
ANS1624E
'value' is an invalid value for option 'option'
for 'command' command
ANS1626E
An unexpected error was encountered when processing a TSM operation
using a hardware or snapshot function. TSM function
name : function-name TSM function
: function-desc TSM return code : TSM-rc
TSM file : file-name (line-number)
ANS1628E
The source v1 and target v2 virtual
disks are in different SVC clusters.
ANS1629E
The source v1 and target v2 virtual
disks are of different size.
ANS1630E
An error was returned calling an operation of the Common
Interface Model(CIM). TSM function name : function-name
TSM function : function-desc TSM CIM
return code: 0xCIM-rc TSM file
: file-name (line-number)
ANS1631E
A memory allocation error has occurred in file filename,
line number linenumber.
ANS1632I
'option name' not specified, defaults to 'deafult
value'
ANS1663W
The option fractional reserve on volume vol_name was
reduced to less than 100 percent.
ANS1664E
The snap restore for volume volname with snapshot
name snapname would destroy later snapshots that are
required for other applications or for volume clones.
ANS1665W
TSM for ACS did not find any snapshots for volume volname on
the N series filer.
ANS1666W
TSM for ACS did not find any information about the N
series volume volname.
ANS1667E
The snapshot name snapname for volume volname was
not found in the snapshot list on the N series filer.
ANS1669W
The command subcommand command
can only be run in Windows WinPE
mode.
ANS1670E
The file specification is not valid. Specify a valid Network
Appliance or N-Series NFS (AIX, Linux) or CIFS (Windows) volume.
ANS1671I
The cluster database has been restored. Restarting the cluster
services on all nodes. This will take a few minutes.
ANS1672I
Could not take the cluster resource resource name offline.
MS rc retcode. Error is ignored.
ANS1673W
Cluster service on node node name could not
be started. You must manually start the service.
ANS1674I
The cluster database has been restored but the cluster service
on some nodes could not be started. Use the Failover Cluster Management
tool to manually start the nodes.
ANS1675W
Unable to obtain a list of cluster nodes to restart after
the cluster database is restored. The call 'cmd' returned
with MS rc retcode. You must restart the cluster service
on all the nodes after the restore is finished.
ANS1676W
You are doing an authoritative cluster database restore.
The process may seem to be hang before and after the file is restored.
This is because it may need to start the cluster service if it is
not up and take all the resources offline. After the cluster database
is restored, the cluster service will be restarted for changes to
be in effect. The cluster service on all other nodes also have been
shutdown. They will be restarted. This may take a few minutes.
ANS1677W
Tivoli Storage Manager
failed to set the disks for quick formatting because of an error.
See the error log for more details. The disks will be slow formatted
which will cause a slower restore process.
ANS1679W
Updating the registry to identify which volumes have been
restored has failed. This does not affect the volumes that have already
been restored. See the error log for more details. The error is being
ignored and processing continues.
ANS1680W
Function refresh incremental FlashCopy cannot be accomplish because no consistency
group found for these volumes.
ANS1681E
DSM_DIR was not set and the ASRFILESPATH option was not specified.
ANS1682W
No FlashCopy relationships
found in the storage system.
ANS1683E
The state status of the consistency group
is bad to achive a valid disk backup.
ANS1684W
Disk Full Error Accessing Subfile Cache: exception-name
ANS1685E
Incremental backup operation using snapshot difference is
only available for N series/NetApp filer volumes, is
not a NetApp volume.
ANS1686I
Single Instance Store link 'file-name' will
be restored or retrieved as a normal file.
ANS1687E
VSS Instant Restore operation failed. Please examine the TSM client
error log file (DSMERROR.LOG), the Windows Application
Event Log, the Windows System
Event Log, and the VSS provider log file (if applicable) for more
details. Consult the VSS provider documentation for the meaning of
the error return code.
ANS1688I
Sparse attributes for 'file-name' cannot be
backed up correctly because the volume from which the file is backed
up does not support sparse files.
ANS1689E
The registry was not updated after VSS ASR restore.
ANS1690E
The list of volumes passed contain pairs which belong to
different consistency groups in the scope of one single cluster.
ANS1691I
The option 'option' that was found in the
options file 'file-name' at the line number: number is
not supported and will be ignored by the client.
ANS1707E
Hard link 'new-file-name' could not be created
for existing file 'exist-file-name'. Microsoft Windows return code: 'windows-return-code'
'windows-error-text'
ANS1708E
Backup operation failed. Only a root user can do this operation.
ANS1712I
Changed block tracking not supported for disk disk
name; Performing FULL backup of disk.
ANS1713W
There was a problem getting changed block tracking information
for disk disk name; Performing FULL backup of disk.
ANS1714I
No changed extents found for disk disk name -
skipping disk.
ANS1715E
A filespace already exists for virtual machine (VM_name),
but with a different virtual machine UUID (VM_UUID)
than the current virtual machine UUID (VM_UUID).
ANS1716E
A VMware vStorage web service task timed-out.
ANS1717E
A VMware vStorage web service task failed.
ANS1729E
The passed file list 'file-list' is not a
valid input file list. Pass standard file list or collection
file list to the dsmrecall command.
ANS1730E
The IBM Tivoli Storage Manager server query for ordering information failed.
ANS1731E
Tape optimized recall for file list 'file-list'
failed with rc = code.
ANS1732W
File 'file' is from a different file system.
writing file to list of unprocessed files: 'file-list'.
ANS1733I
A collection file was specified 'file-list'
The ordering process is skipped.
ANS1734W
The virtual machine 'VM-name' contains one
or more independent disks. Backups are not supported in this configuration.
Specify the '-vmprocessvmwithindependent=yes' option to exclude these
disks from the backup.
ANS1735W
The virtual machine 'VM-name' contains one
or more physical Raw Device Mappings (RDMs). Backups are not supported
in this configuration. Specify the '-vmprocessvmwithprdm=yes' option
to exclude these disks from the backup.
ANS1739E
Restore of a system drive is not permitted.
ANS1740W
Unable to read ACLs for object: file_system path name.
Check dsmerror.log for more information.
ANS1741W
Unable to read extended attributes for file_system path name.
Check dsmerror.log for more information.
ANS1742E
Expose Snapshot failed for backup 'backup-name'.
ANS1743E
Unexpose snapshot failed for backup 'backup-name'.
ANS1744E
One or more of the snapshots(volumes) needed for the restore
operation were not found. See dsmerror.log for further details.
ANS1745I
The virtual machine to restore has one or more distributed
port groups. Further configuration might be necessary to select a
port number after the restore is complete.
ANS1746E
No available LUNs were found. Confirm that the storage adapters
are configured correctly on the host and that the LUNs are not mapped
to another virtual machine.
ANS1747E
Encryption key password is not available.
ANS1748E
The virtual machine was stored with a Raw Device Mappings
disk backed by a LUN. The required LUN is missing or still mapped
to another virtual machine: LUN UUID lun.
ANS1749W
Object 'filespace-namehl-namell-name'
was backed up with invalid file system type attribute.
ANS1750I
Volume mount point 'volumemountpoint' is mounted
to volume 'volume'. Using snapshot volume for 'volume'
to backup.
ANS1751E
Error processing 'filespace name': The file
system can not be accessed.
ANS1753E
File space 'filespace name' was backed up
by an older client version, and cannot be restored with this client
version. The file space will be skipped.
ANS1754E
File space 'filespace name' cannot be restored
when ASNODENAME option is in affect. The file space will be skipped.
ANS1755W
An error communicating with Active Directory has occured.
USEDIRECTORY option will be ignored and processing will continue.
ANS1756W
The Journal for 'backup-specification' has
been reset: The server filespace was deleted since the last backup
completed.
ANS1757W
The Journal for 'backup-specification' has
been reset: The server filespace was deleted since the last backup
completed.
ANS1758W
The Journal for 'backup-specification' has
been reset: The server filespace was deleted since the last backup
completed.
ANS1759W
The Journal for 'backup-specification' has
been reset: The policy set was updated since the last backup completed.
ANS1760I
Journal for 'backup-specification' enabled
for node 'nodename' and server 'servername'
ANS1761I
Journal for 'backup-specification' will be
enabled upon successful completion of the backup.
ANS1763W
Unable to unmount snapshot mount point snapshot
mountpoint during cleanup of snapshot 'snapshot'
of volume 'volume'. Error is 'error'. Operation
will continue. Please manually unmount, remove the snapshot mount
point directory and delete the snapshot after backup is completed.
ANS1764W
Unable to remove the snapshot mount point directory snapshot
mountpoint during cleanup of snapshot 'snapshot'
of volume 'volume'. Error is 'error'. Operation
will continue. Please manually remove the snapshot mount directory
and delete the snapshot after backup is completed.
ANS1765W
Unable to delete the snapshot during cleanup of snapshot
'snapshot' of volume 'volume'. Error
is 'error'. Operation will continue. Please manually
delete the snapshot after backup is completed.
ANS1766W
Unable to remove the snapshot logical volume during cleanup
of snapshot 'snapshot' of volume 'volume'. Error
is 'error'. Operation will continue. Please manually
remove the snapshot logical volume after backup is completed.
ANS1767E
Unable to create a snapshot logical volume using command: 'cmd'. Error
is 'error'. Please ensure that the volume group
has sufficient free partitions to fulfill the allocation request.
ANS1768E
TSM was unable to find space for a new snapshot.
TSM function name : function-name TSM function
: function-desc TSM return code
: TSM-rc TSM file : file-name (line-number)
ANS1769E
NetApp file server 'server-name' at Data ONTAP
version 'version.modification.submodification'
is not supported for performing incremental backups using snapshot
difference.
ANS1784E
Incremental by snapshot difference cannot be performed on
'volume-name' as it is a vFiler volume.
ANS1787I
The virtual machine NIC is backed by a distributed virtual
port group but it is missing the portgroupKey attribute, The NIC cannot
be restored.
ANS1788I
The target ESX host is missing the required distributed virtual
port group, the virtual machine NIC cannot be restored. Use VMDEFAULTDVPORTGROUP
option to set to specify new port group. If target ESXi server does
not have any port groups, use VMDEFAULTNETWORK option.
ANS1789I
No Ddistributed virtual port group were found on the target
ESX host. The virtual machine NIC cannot be restored.
ANS1790E
Volume 'volname' cannot be backed up because
'nosnapdir=on' is set on the filer.
ANS1794I
The option 'cifs.enable_share_browsing = off' is set on the
filer 'filerName'.
ANS1795I
Operation will continue without using snapshot provider,
because file system 'volname' does not have write permissions.
ANS1796I
The short name for 'fullpath-name' could not
be set to original short name 'file-name': Windows function 'func-name'
failed with return code return-code, reason: 'error
text'
ANS1797E
Function function-name received an unexpected
error from the Microsoft API MS-function-name:
rc=error while attempting to access the object 'object-name'.
Error occurred in file file-name (line-number).
ANS1798W
An error occurred while accessing encrypted data of the object
'object-name', skipping object. Windows system error code error, reason
'error-reason'
ANS1799I
The last access date for 'fullpath-name' could
not be reset because the file is read-only.
ANS1800W
The last access date for 'fullpath-name' could
not be reset: function 'func-name' failed with return
code return-code
ANS1801E
Unable to register the new ID with server.
ANS1802E
Incremental backup of 'file-name' finished
with failCount failure(s)
ANS1803E
Archive processing of 'file-space name' finished
with failures.
ANS1804E
Selective Backup processing of 'file-space name'
finished with failures.
ANS1805E
Unable to restore symbolic link 'file-name'.
ANS1806W
Size exceeded the maximum file size limit on your system for
'filespace namepath-namefile-name'
of 'file-size'.
ANS1807E
Unable to recall file from server due to error from recall
daemon.
ANS1808E
The Logical Volume Snapshot Agent is not at the correct level.
It is possible that the Client was upgraded to a newer level but the
LVSA driver was not updated at the same time. Use the Setup Wizard
to configure either Online Image or Open File support and choose Update
the Logical Volume Snapshot Agent.
ANS1809W
A session with the TSM server has been disconnected.
An attempt will be made to reestablish the connection.
ANS1810I
A session with the TSM server has been reestablished.
ANS1827W
Directories cannot be selected with the table of contents
currently loaded on the server.
ANS1828E
Screen size is too small for using the PICK option.
ANS1831E
Password expired. The administrator for this system must
run TSM to update the password.
ANS1832W
The option 'option' is no longer supported
and will be ignored by TSM client in this release.
ANS1834S
Unable to write to 'file-name' for storing
password
ANS1835E
PASSWORDACCESS
is GENERATE, but password needed for server 'server-name'. Either
the password is not stored locally, or it was changed at the server.
ANS1836I
Unable to process Processor Value Unit hardware scan info
file 'file name', errno, cause.
ANS1837S
File space filespace-name is ignored. Processing
continues.
ANS1838E
Error opening user specified options file 'filespace-name'
.
ANS1852E
Server could not load the table of contents. Status: status reason: reason
ANS1853E
Server could not load the Table of Contents. Status: status
ANS1862W
No table of contents information is available on the server
for this volume.
ANS1865E
Session
rejected: Named Pipes connection failure.
ANS1867E
The server generated a CRC for verb type CRC verb which
does not match the received verb verb received.
ANS1871W
The server CRC version is server CRC version which
does not match the client version client CRC version.
ANS1873E
An unknown error occurred while processing system object
'sys-obj-name': utility function 'func-name'
failed with error error
ANS1877E
The parsed string is too long for TSM to process and
has been truncated to prevent a buffer overflow.
ANS1878E
An unknown error occurred while processing system object
'sys-obj-name': Service 'service-name'
and its dependent services could not be stopped.
ANS1882E
Unable to stop service 'service-name'; error error
ANS1891W
SUBDIR is not a valid option when using FILELIST, SUBDIR
will be ignored.
ANS1892W
Expire command is not allowed on the TSM journaled filespace
'filespace'.
ANS1895I
Highest macro return code was return code value.
ANS1945E
The long namespace has been removed from the local filespace.
If you wish to proceed with the backup/archive operation, rename your
filespace on the server.
ANS1989E
Initialization
functions cannot open the Error Log file specified.
ANS1990W
The 'filesystem name' volume mount point can
not be accessed. The TSM return code is 'rc'.
ANS1991E
An error occurred processing registry key 'key-name',
data value 'value-name'. See the client error log for
additional information about this error.
ANS1995W
Objects of different types cannot be deleted at the same
time.
ANS1996W
The volume mount points enumeration on 'filesystem
name' volume failed. Windows system
error code: error; reason: 'error-reason'.
ANS1997W
No files have been previously backed up for the VSS component
'component-name'.
ANS1998W
Transaction byte limit 'name' is not supported
by the server. Value reset to limit
ANS1999E
type of the operation processing of 'filespace-name'
stopped.
ANS2026W
Bad sectors were detected on the volume 'volname'.
ANS2032I
The client VM restore is skipping the unsupported Independent
disk : vmdk
ANS2036W
Pruning functions cannot open one of the Tivoli Storage Manager prune files: log-name.
errno = errno-value,
ANS2040E
While attempting to communicate with the remote client, a
version check reveals that the versions do not match. The version
is remoteversion but the expected version is localversion.
ANS2041E
Snapshot Differencing support is not available on the specified
NetApp filer.
ANS2042W
'symboliclink':is a symbolic link to a file
or directory in another filesytem. ACLs or extended attributes might
not be backed up.
ANS2043I
The virtual machine template 'name' has already
been backed up.
ANS2044E
The template virtual machine 'name' cannot
be restored when the Tivoli Storage
Manager data mover node on the vStorage Backup Server is connected
directly to an ESX/ESXi host.
ANS2045E
The VMENABLETEMPLATEBACKUPS option is not specified. The
virtual machine template 'name' can not be backed up.
ANS2046S
Error 'errtxt' (errno=errno)
occurred trying to write to audit log 'file-name'.
The audit log function is disabled.
ANS2047E
An unexpected error was encountered processing a system state/services
request. TSM function name : function-name
TSM function : function-desc TSM return
code : TSM-rc TSM explanation : TSM-msg
TSM file : file-name (line-number)
ANS2048W
Named stream of object 'object-namepath-name file-name'
is corrupt.
ANS2049W
Named stream of object 'object-name' may be
corrupt.
ANS2050E
TSM needs to prompt for the password but cannot prompt
because the process is running in the background.
ANS2051W
The local snapshot repository was not found on location.
ANS2052E
Information about the disk subsystem is missing.
ANS2053E
A memory allocation error has occurred in file filename,
line number linenumber.
ANS2054E
Operating system error errno: messagetext.
ANS2055I
The local snapshot manager could not be locked.
ANS2056I
Waiting maximal timeout seconds until the
lock is released by the other application.
ANS2067E
The exception CLsmException was thrown. Reason: txt.
ANS2068E
No target LUNs were found for the data container dcID in
the .fct file filename.
ANS2069E
Cannot read the file filename of the local
snapshot repository.
ANS2070E
The repository state file filename is empty
or has a wrong format.
ANS2071E
The data container dcID could not be inserted
in the local snapshot repository.
ANS2072E
An unexpected error was encountered processing a TSM operation
using a hardware or snapshot function. TSM function
name : function-name TSM function
: function-desc TSM return code : TSM-rc
TSM file : file-name (line-number)
ANS2073E
The file filename of the local snapshot repository
could not be opened for writing.
ANS2074E
Cannot open user input FlashCopy target
file 'fct_file'.
ANS2075E
There is no VTOC data available for the volume. The volume
cannot be backed up.
ANS2076E
program-name: Space Managment can not be added
for file system 'filesystem' The length of the file
system name exceeds the maximum length of 'maxlength'
which can be stored in a DMAPI attribute.
ANS2077E
program-name: Reconcile for file system 'filesystem' can
not be started for the selected mode in a non-scout environment. Please
use Two Way Orphan Check Reconcile instead.
ANS2078E
System state backup is not allowed CLUSTERNODE is set to
YES.
ANS2085E
The virtual machine is configured as a fault tolerant virtual
machine. As a result, it cannot be backed up.
ANS2088E
Session rejected: The client does not use unicode.
ANS2090I
The virtual machine folder could not be found in this path:
'name'.
ANS2091I
The virtual machine resource could not be found in this path:
'name'.
ANS2092I
The restore process will override the original inventory
path that was saved with this virtual machine.
ANS2093E
The remote file system agent is downlevel and does not support
this operation. NODENAME : node
MULTI-NODE NAME : multi-node hostname
: host TCP/IP address : tcpaddr:tcpport
version : version.release.level..mod
ANS2097E
Unable to establish a session with the TSM server as
target node 'target' using agent node 'agent'.
ANS2100E
Neither source volume id nor target volume id is in the volume
list.
ANS2104E
An error occured after processing the file list.
ANS2105I
File list entry not Processed: File List Entry
ANS2106I
Connection to primary TSM server primary server; failed
ANS2107I
Attempting to connect to secondary server secondary
server; at secondary server; : TCP/IP
Port;
ANS2108I
Connected to secondary server secondary server;.
ANS2110I
Connection to secondary server TSM secondary
server; failed
ANS2111E
The REPLSERVERNAME entry for the specified MYREPLICATIONSERVER
option was not found.
ANS2112I
Secondary server is configured as 'read-only'. Backup and
Archive operations are not supported when the secondary server is
in 'read-only' mode
ANS2113E
The Command; command is not enabled when connected
to the secondary server in failover mode.
ANS2114W
IBM Tivoli Storage Manager application protection did not copy the VSS Manifest
files from VM 'VM'.
ANS2115I
Replication server connection information saved: connection
information;
ANS2116W
IBM Tivoli Storage Manager application protection did not back up the VSS
Manifest files from VM 'VM'.
ANS2117E
Source volume is of subtype dev-type and destination
is of subtype dev-type. Destination must be larger
than source.
ANS2118I
A write failure occurred while attempting to save node replication
failover values to the options file.
ANS2119I
An invalid replication server address return code rc value
= rc-value was received from the server.
ANS2120W
The last store operation date reported by the server replication
server; of server commit date; UTC does not match
the last store operation date of client commit date; UTC
stored by the client.
ANS2121I
The file space on replication server; started
replication at server replication start date; The replication
completed successfully at server replication complete date;.
ANS2122I
The file space on replication server; started
replication at server replication start date;. The
replication did not complete successfully. The last successful replication
completed at server replication last successful date;.
ANS2123W
Issue the dsmc SET PASSWORD -type=VCD 'vCloud Director hostname'
'userid' 'password' command to save an encrypted password.
ANS2124W
Client node replication table is locked by another process.
ANS2126E
The Organization VDC node that contains snapshots of Organization
VDC 'org vdc name' of organization 'org name'
was not found.
ANS2127E
The snapshot data that is required to restore 'vapp
name' cannot be retrieved from the TSM Server.
ANS2128E
Failed in creating a restored version of vApp 'vapp
name'.
ANS2135E
The node on the TSM server is in read only mode.
ANS2136E
Operation not permitted. The secondary server reports the
primary server is available. Quit and restart the TSM client
and retry the command.
ANS2138E
Failed in restoring the vApp properties to vApp: 'vapp
name'.
ANS2143E
vApp verification failed. Data inconsistency was found.
ANS2145W
Warning - updating an existing virtual machine named 'name'.
The restore operation continues.
ANS2146E
The target vCenter or ESX/ESXi host is no longer supported,
for virtual machine backups, by this version of IBM Tivoli Storage Manager.
ANS2147E
The virtual machine named 'name' already exists
on the target system.
ANS2148I
Virtual machine templates cannot be backed up in incremental
mode, switching to full mode.
ANS2149E
The restore operation for this virtual machine to the target
ESX/ESXi host is not supported because virtual machine hardware version
is incompatible.
ANS2150E
Set HSMDISABLEAUTOMIGDAEMONS YES in the dsm.opt file to use
HSM multi-server functionality.
ANS2155W
Skipping file 'file-name'. File related to
'server-name'.
ANS2156E
The server 'server-name' was not added to
the environment.
ANS2157E
The server 'server-name' was not removed from
the environment.
ANS2158E
The server 'server-name' was not added to
the environment. You must first add the default IBM Tivoli Storage Manager server
('default-server-name') for this file system.
ANS2159I
The server 'server-name' was added to the
environment.
ANS2160I
The server 'server-name' was removed from
the environment.
ANS2161E
The server 'server-name' is not a valid IBM Tivoli Storage Manager server
for this environment.
ANS2162E
HSM cannot be removed from the file system. The IBM Tivoli Storage Manager multi-server
list is not empty.
ANS2163E
The default IBM Tivoli Storage Manager server ('server-name')
for the file system will be removed.
ANS2165I
The server 'server-name' is the default server
and has been removed last.
ANS2166I
The IBM Tivoli Storage Manager server 'server-name' is not
included in the multi-server environment.
ANS2169E
Skipping - Requested server is not included in multi-server
environment for filesystem 'file-system'.
ANS2170W
Skipping - file linked to another server.
ANS2171E
The DMAPI version 'dmapi-version' is not supported.
ANS2172E
Command not supported in HSMBACKENDMODE TSMFREE.
ANS2173E
Volume 'volume name' from vFiler 'vFiler
name' is mounted using AIX NFS
version 4. This configuration is not supported for snapshot difference
incremental backups.
ANS2174E
Conflicting options HSMLOGMAX and HSMLOGRETENTION were specified.
ANS2175I
Data from server 'server-name' should be recalled
using the script 'dsmMultiServerRemove.pl'.
ANS2176E
The sample journal configuration file '' could
not be copied to ''.
ANS2177E
The vCloud vApp named 'vapp name' already
exists on the target system.
ANS2183E
Organization 'Org name' not found in the vCloud
Director.
ANS2184E
Organization VDC 'Org vDC name' not found
in organization 'Org name'.
ANS2185E
Failed to log on to the vCloud Director on 'vCD
host name' with user name 'vCD user name': Authentication
failed.
ANS2186E
Failed to log on to the vCloud Director on 'vCD
host name' with user name 'vCD user name': User
not found.
ANS2187E
Failed to establish connection to the vCloud Director on
'vCD host name'.
ANS2188E
The vCloud protection runtime library is not installed or
failed to load.
ANS2189E
The vCloud protection runtime library cannot be initialized.
ANS2190E
The vCloud protection runtime library encountered an internal
error.
ANS2191E
An error occurred creating the default VSS staging directory
'path'.
ANS2192E
Failed to read the node configuration information from node
'node name'.
ANS2193E
The required filespace for the vApp 'vapp name'
backup does not exist.
ANS2194E
The snapshot data is incomplete for vApp 'vapp
name'.
ANS2195E
The number of VMs that are available for restore is different
from expected according to the vApp 'vapp name' metadata.
ANS2196W
An incompatible disk configuration is detected for the following
disk: 'disk name'. The individual database restore
for the following database is not supported:'database name'.
ANS2197E
The verification test of vApp 'vapp name'
indicates that VM data is incomplete in the vApp. The vApp cannot
be restored.
ANS2198I
Backup of VMware vCloud Director vApp 'vApp name'
in Organization VDC 'Org VDC name' of organization
'Org name' completed successfully. VMs: number
of VM backed up out of number of VMs in vApp VMs
backed up successfully.
ANS2206W
The user must have root authority to use the memory efficient
backup disk cache method. The operation will continue using memory
efficient backup method without disk caching.
ANS2213E
Error while querying volume properties of volume volserial. Please
verify that the volume specified in the target volumes file exists.
ANS2218I
The encryption key password for node node name and
server server name has been migrated.
ANS2219E
Cannot backup or archive files into filespace because
it is owned by a TSM API application.
ANS2220E
The cluster disk could not be put in maintenance mode.
ANS2221W
Java was not able to
resolve the IP address of your local machine due to network
misconfiguration problems! Please verify your network
and DNS configuration are setup correctly. Note that on UNIX machines the hostname must
be reported correctly (the same) for IPv4 and IPv6 communication
methods in the /etc/hosts configuration file. TSM processing
continues.
ANS2223W
Rejected unauthenticated server-initiated session from peer
name.
ANS2225W
User has specified 'SNAPSHOTROOT' option. snapshot
provider snapshot backup is not valid in conjunction with this
option. "SNAPSHOTROOT option will take precedence and processing
will continue without the use of a snapshot taken internally by TSM.
ANS2227W
Server option 'option-name' 'option-value'
has not been applied on the client due to the client option SRVOPTSETENCRYPTIONDISABLED.
ANS2228W
Backup of VMware vCloud Director vApp 'vApp name'
in Organization VDC 'Org VDC name' of organization
'Org name' completed. Some VMs were not backed up.
VMs: number of VM backed up out of number
of VMs in vApp VMs backed up successfully.
ANS2229E
Failed to initialize the vCloud protection environment. See
the local client error log for detailed error message information.
ANS2230E
Failed to create vApp list according to spec 'vApp
specification'
ANS2232E
Failed to retrieve the list of VMs for vApp 'vApp
name' from the vCloud Director.
ANS2236I
The virtual machine 'VM-name' contains one
or more disks that exceed the 2 TB maximum size limit. These disks
will be excluded from the backup.
ANS2238E
VCDHOST option must be set before running this operation.
ANS2239W
The annotations field contained too many characters and had
to be truncated.
ANS2240T
The basic verification of vApp 'vApp name'
succeeded.
ANS2241T
The extended verification of vApp 'vApp name'
succeeded.
ANS2242E
No nodes were found that matched the input specification: node
specification
ANS2244W
The virtual machine contains one or more disks that exceed
the maximum size limit. Specify the '-VMSKIPMAXVMDKS=yes' option
to exclude these disks from the backup.
ANS2245E
Virtual machine backups and restores are not supported on
32 bit data movers.
ANS2246W
Failed to disable maintenance mode for vApp vApp
name.
ANS2247E
ASNODENAME option must be specified when running this command.
ANS2248E
Failed to load or initialize the Java runtime library.
ANS2249W
A virtual machine named 'vmname' exists on
this system. Do you want to replace the existing virtual
machine?
ANS2250W
A TSM core file or crash report was found: filename
ANS2253W
The version of the message catalog, catalogversion,
in use by TSM does not match the version of TSM, clientversion
ANS2254E
program-name with session id sessid aborted
recall for token token. ERRNO errno : errno-text was
set. See message explanation.
ANS2315E
-PICK is not allowed for EXPIRE when -OBJTYPE=VM.
ANS2316E
Wildcards are not allowed in the VM name argument.
ANS2317E
Deletion of VM object VMname failed. Reason:
ANS2318E
Command with -OBJTYPE=VM requires exactly
one non-option argument
ANS2319W
DELETE BACKUP -OBJTYPE=VM finished with failures.
ANS2320I
DELETE BACKUP -OBJTYPE=VM finished without failures.
ANS2321W
EXPIRE with -OBJTYPE=VM finished with failures.
ANS2322I
EXPIRE with -OBJTYPE=VM finished without failures.
ANS2323E
The user ID and password for VMware vCloud Director 'vCD
host name' are not set.
ANS2324W
WARNING: The VMware vCloud Director user ID <hostuserid>
read from the password file is different from the VCDUser option value
<vmcuserid>. Using stored value.
ANS2325E
Error Accessing Snapshot Differential Change Log for filer
'' volume '', see client error log for
more information.
ANS2326W
Corrupt Snapshot Differential Change Log detected, change
log will be reset and a full progressive incremental will be performed.
ANS2329W
Down level Snapshot Differential Change Log detected, Change
Log will be reset and a full progressive incremental will be performed.
ANS2330E
Failed to unfreeze the VSS writers because the snapshot time
exceeded the 10 second timeout limitation.
ANS2331W
No match found on the server for the Hyper-V VM name
or VMList 'string' entered
ANS2332E
Failed to log on to the vCloud Director. Authentication failed.
ANS2333E
Failed to establish connection to the vCloud Director.
ANS2334E
An operation requiring the Windows Management
Instrumentation (WMI) service has failed with the error 'errorstring'.
Unable to connect to the Hyper-V namespace. Confirm that Hyper-V
is installed on the backup node.
ANS2335E
An operation requiring the Windows Management
Instrumentation (WMI) service has failed with the error 'errorstring'.
The WMI service is in the shutting down or shutdown state. Restart
the service and try again.
ANS2336W
TSM has detected that the following Hyper-V virtual machine
"virtual_machines" has an interrupted incremental backup
chain. Performing a full backup on the specified Hyper-V virtual machine.
ANS2337E
TSM was unable to take cluster resource 'resourcename'
offline. The current operation requires the resource to be offline.
Turning the cluster resource off failed with rc=rc.
ANS2338W
TSM has detected a request to backup a virtual machine
replica. The state of the replica 'vmreplicaname',
ID='vmid' may differ from the original virtual machine.
If the names of the original virtual machine and the replica are identical
the same filespace will be used. The data may become unrecoverable
because the state of the original virtual machine and the replica
may differ.
ANS2339W
The Hyper-V VM 'vmname' is in a "branch" state
compared to the last backup. Incremental Forever - Incremental backup
cannot be performed. An Incremental Forever - Full backup will be
performed instead.
ANS2340W
The target virtual machine 'VM-name' exists,
use the REPLACE option to overwrite.
ANS2341E
The target virtual machine 'VM-name' cannot
be restored: The guid differs from the backup copy.
ANS2342E
The specified restore target 'VM-name' is
ambiguous: Multiple virtual machines with the same name exist.
ANS2343E
A snapshot of Virtual machine 'vmname' cannot
be taken because a physical disk attached.
ANS2345W
The virtual machine named '' was found to
have an old snapshot ''. A command was sent to the
vCenter to remove it.
ANS2346E
Expiration of VM object VMname failed. Reason:
ANS2347E
IBM Tivoli Storage Manager application protection cannot be used. The correct Java Runtime Environment version
has not been detected on machine. A Java Runtime Environment version or
higher is required to run this program. If you have already installed
this level of Java version on
this machine, please ensure that the correct Java executable is on your PATH and start the program
again.
ANS2348E
Mount proxy host 'remoteversion' does not
have a supported operating system.
ANS2349W
The virtual machine named '' was found to
need snapshot consolidation. A command was sent to the VMware vCenter
to perform consolidation.
ANS2350E
Virtual machine 'VM name' will not be backed
up because it contains at least one of the following unsupported special
characters \ / : ; , * ? " ' < > |
ANS2351E
Duplicate virtual machine name 'vmname' was
detected in the same backup operation. Backups of a virtual machine
can not continue without a unique object name.
ANS2352E
Validation of virtual machine 'vmname' configuration
returned the following message from Hyper-V: hypervmessage This
message indicated that the virtual machine could not be restored until
the message from Hyper-V is addressed.
ANS2398I
The virtual machine 'VM-name' is configured
as a VMware Site Recovery Manager placeholder virtual machine on the
recovery site. As a result, the virtual machine will be skipped.
ANS2399I
The virtual machine is configured as a VMware Site Recovery
Manager placeholder virtual machine on the recovery site. As a result,
the virtual machine will be skipped.
ANS2408I
The virtual machine named 'VMNAME' is ready
for Instant Access
ANS2409E
The Instant Restore type was not identified.
ANS2410E
Instant Restore information for the specified virtual machines
was not found.
ANS2411E
Instant Restore/Access of virtual machine 'vmname'
failed with rc = return-code
ANS2412E
IBM Tivoli Storage Manager Recovery Agent is not installed.
ANS2413E
Cannot find the Recovery Agent shell command in the expected
installation path. Ensure that TSM for VE is correctly
installed and configured.
ANS2414E
An error occurred when the hostname for the local machine
was called.
ANS2415E
An error occurred when the machine address information was
called.
ANS2416E
An error occurred when the machine name information was called.
ANS2417E
Unexpected communication method. Only TCP and TCPv6 are accepted.
ANS2418E
Unable to read or write to the local instant restore data. filename File
cannot be accessed or is damaged.
ANS2419E
The datastore does not have enough free space for the instant
restore operation.
ANS2431E
Cannot find the temporary datastore 'TEMPDATASTORE'
on the ESX host 'ESXHOST'.
ANS2432E
The temporary datastore 'TEMPDATASTORE' is
the same as the target datastore 'DATASTORE'.
ANS2433E
The '-vmtempdatastore' option must be specified for an instant
restore operation.
ANS2434E
The datastore 'DATASTORE' was not found on
the host 'ESXHOST'.
ANS2444E
Cannot find the datacenter for host 'ESXHOST'.
ANS2445E
Virtual machine 'VM' is running. You cannot
delete this VM.
ANS2447E
Failed to delete VM 'VM' from the ESX host.
ANS2448E
Mount command failed. Command was COMMAND Shell command returned: RESULT
ANS2452E
num_discovered iSCSI devices were discovered
on the ESX host, while num_mounted were expected.
ANS2453E
An error occurred when the host bus adapter was scanned.
ANS2454E
An error occurred when the iSCSI target target_name was
disconnected from the ESX host bus adapter.
ANS2455I
The virtual machine has been started. You can use the machine
after it has booted, or you can connect to it and manage its settings
through the vCenter console.
ANS2462E
Unable to start the vMotion task for virtual machine 'vm_name'.
ANS2463W
Instant Restore information cannot be saved on the server.
ANS2464E
Unable to delete Instant Restore information from the server.
ANS2465E
An error occurred during a storage vMotion operation.
ANS2466W
If you continue you will lose all data created on this virtual
machine. The virtual machine will also be removed from the
ESXi host. Are you sure that you want to do this? Press Y the
virtual machine data and remove it from the ESXi host. Press
any other key to continue without deleting data or the VM.
ANS2467W
Unable to delete the snapshot that was created for the virtual
machine named 'vm_name'
ANS2468E
The necessary iSCSI targets could not be found on the ESX
host.
ANS2472E
Cannot detect the LUN for the attached RDM devices for virtual
machine named vmname'. The restore operation
for this virtual machine cannot be completed.
ANS2473E
Unable to create a Snapshot of the virtual machine named
'vm_name'.
ANS2474E
Unable to cleanup after an instant restore operation for
the virtual machine named 'vm_name', because vMotion
task is still running.
ANS2476E
A restore location must be specified via the TARGETPATH option
when restoring to a different virtual machine name.
ANS2484I
Virtual Machine 'vm_name' was successfully
restored
ANS2485E
Cannot query the Tivoli Storage
Manager server to get instant access information
ANS2515I
No additional information is available for this virtual machine.
The virtual machine was deleted or it has been renamed
ANS2516E
VMware storage vMotion operation failed. Restart the
storage vMotion operation manually, by using the vSphere web client,
to finish the restore operation. Refer to the documentation
to get details about the manual recovery process.
ANS2517E
Cannot query the Tivoli Storage
Manager server to get instant restore information
ANS2519E
The disk \"diskname\" is an iSCSI device with
an inactive path. Powering off the virtual machine will cause
the ESXi server to hang. The clean up operation has been stopped to
prevent this. Use the Query VM command with the -detail option
to obtain detailed status information about the virtual machine. Correct
the path so that the iSCSI state is active and then try running the
VMFULLCleanup operation again.
ANS2520E
The disk \"diskname\" is not a physical device. An
instant restore clean up was stopped because vMotion could not restore
all virtual machine data.. Use the Query VM command with the
-detail option to obtain information about state of the specified
disk. Use vMotion to manually migrate the virtual machine devices
and then try the clean up operation again.
ANS2521E
Instant restore operations require valid licenses for both
vMotion and storage vMothion.
ANS2522W
A user canceled the 'operationType' operation
.
ANS2523E
The virtual machine named vm cannot not be
restored to the same configuration it had when it was backed up. IBM Tivoli Storage Manager will
reconfigure the virtual machine to include only the most essential
configuration information and retry the restore operation.
ANS2524E
An attempt to mount a snapshot of VM 'disk'
from disk 'vm' failed. The volume might be mounted
from another operation and cannot be remounted.
ANS2525E
Unable to power on the created virtual Machine.
ANS2600S
Browser trying to establish connection to client; received
socket exception: exception-name
ANS2601S
Browser trying to establish connection to client; received
unknown host exception: exception-name
ANS2602S
Browser trying to establish connection to client; received
IO exception: exception-name
ANS2603S
Browser trying to establish connection to client; received
exception: exception-name
ANS2604S
The Web client agent was unable to authenticate with the
server.
ANS2605S
Browser could not re-establish connection to client; received
protocol error.
ANS2606S
An invalid password was sent to the server.
ANS2607S
Browser could not establish connection to client.
ANS2608S
Nothing was selected so no operation was performed.
ANS2609S
TCP/IP communications failure between the browser and the
client machine.
ANS2610S
TCP/IP communications failure between the client and the
server machine.
ANS2611S
An unknown error occurred in the browser.
ANS2612S
An unknown error occurred in the client Please check
the TSM Error Log for any additional information
ANS2613S
A communications protocol error occurred between the web
browser and the client.
ANS2614S
A protocol error occurred in communications between the client
and the server.
ANS2615S
The user ID entered does not match the node name configured
on the client machine.
ANS2616I
The machine must be rebooted for the changes to take effect
ANS2617S
The destination directory specified is invalid.
ANS2619S
The Client Acceptor Daemon was unable to start the Remote
Client Agent.
ANS2620W
The expand entire branch operation may take a long time, and
cannot be canceled once it has started. Are you willing
to wait for the operation to complete?
ANS2623S
Web Client applet level is out of sync with Web Client agent.
ANS2624E
This operation requires client owner authority.
ANS2625E
Node does not support this image operation.
ANS2626E
The Include-Exclude statement: ieStatement contains
invalid characters.
ANS2627W
The NTFS security attributes for object 'full-name'
could not be set. Windows system
error code: error; reason: 'error-reason'.
Default NTFS security attributes have been set.
ANS2628W
Failed to create named stream of object 'filespace
namepath-namefile-name'.
ANS2629I
Migration: The filespace will be migrated to the Incremental
Forever model.
ANS2666S
Source and/or target volumes are duplicated. The same volume
is mounted on more volume paths.
ANS2687W
The virtual machine 'VM-name' contains one
or more disks that exceed the maximum size limit. Specify the '-VMSKIPMAXVMDKS=yes'
option to exclude these disks from the backup.
ANS2688E
The restore of a Hyper-V virtual machine that was backed
up using incremental forever backup is not allowed on a Windows 2008 or Windows 2008 R2 host. The restore
operation must be completed on a Windows 2012
or later Hyper-V host
ANS2689E
A Hyper-V command subcommand command
was specified, but the Hyper-V role is not enabled on the host system
ANS2690E
A Hyper-V BACKUP VM command with mode IFFULL or IFINCR was
specified but the Data Protection for Microsoft Hyper-V license file does not exist or
is not valid
ANS2691E
A Hyper-V BACKUP VM command with mode FULL was specified
but the Data Protection for Microsoft Hyper-V
license file exists. Mode IFFULL or IFINCR must be specified
ANS2692E
An error occurred while registering the filespace for virtual
machine (VM_name).
ANS2693E
An error occurred while registering the filespace for virtual
machine (VM_name). There is a filespace with the same
name that is currently being deleted.
ANS2697E
The virtual machine cannot be restored because the datastore
named 'datastore' does not exist or is inactive.
ANS2699W
Importing VM 'vm name' failed for vApp 'vapp
name'.
ANS2700E
Restoring VM 'vm name' of vApp 'vapp
name' is not possible. There is no VM backup data.
ANS2701E
The attempted database operation was unsuccessful, check
the TSM error log for any additional information.
ANS2704E
Error: The vCenter server version is at a lower level than
the ESX host version, or the user ID specified by the VMCUser option
does not have sufficient permission to perform the operation.
ANS2705S
No DB2 UDB partitions
are available for restore.
ANS2711E
The snapshot of virtual machine 'VM-name'
was removed during the backup.
ANS2712W
The virtual machine 'name' has a VMware Tools
running, but VMware Tools is out of date.
ANS2713E
The virtual machine 'VM-name' is in an invalid
connection state 'state'. As a result, it cannot be
backed up.
ANS2714W
The management class 'mc' specified for the
'dest' backup destination is invalid. The default management
class will be used.
ANS2715E
The virtual machine 'VM-name' is configured
as a fault tolerant virtual machine. As a result, it cannot be backed
up.
ANS2716E
A background copy process is still pending on local hardware.
A restore operation cannot be initiated until the background copy
process is completed.
ANS2717E
The multi-node definition does not have permission to delete
its own backup files from the server.
ANS2718W
The virtual machine 'VM-name' requires snapshot
consolidation.
ANS2719E
A previous backup started on 'datetime',
is using the resources needed for new backup is still pending.
ANS2729E
Operating system command 'command' failed;
rc=rc.
ANS2730E
The primary and secondary copy service servers are down.
ANS2731E
Cannot open the ESS command output file v1 for
writing.
ANS2732E
The ESS LUN 'Serial number string' are already
in use.
ANS2733E
An operation requiring the Windows Management
Instrumentation (WMI) service has failed with the error 'errorstring'. TSM has
been denied access to a WMI system due to insufficient privileges.
ANS2734E
An operation requiring the Windows Management
Instrumentation (WMI) service has failed with the error 'errorstring'.
The application interface does not exist.
ANS2736E
An unexpected response was received from a remote TSM file
system agent. verb : verb
remote host : host return code : rc
reason code : rs msg. string : msg-string
ANS2737W
No disks from VM are mounted because all disks were excluded
during the backup.
ANS2744I
TESTFLAG DB2 enabled
with the value of 'value'.
ANS2745E
An assigned virtual disk to Hyper-V Virtual Machine 'virtualmachinename'
cannot be found.
ANS2746E
An assigned virtual disk to Hyper-V virtual machine 'virtualmachinename'
is a VHD or invalid format. Only virtual disks in VHDX format can
be backed up.
ANS2747E
An assigned AVHDX virtual disk to Hyper-V virtual machine
'virtualmachinename' cannot find the parent disk. Snapshots
can be taken only if the parent can be found.
ANS2748E
An assigned virtual disk to Hyper-V virtual machine 'virtualmachinename'
exceeds the maximum capacity limit. The IBM Tivoli Storage Manager client cannot backup
virtual machines with disks that exceed the limit of two terabytes.
ANS2749E
See Microsoft Technote
KB2771882. An assigned virtual disk to Hyper-V Virtual Machine 'virtualmachinename'
contains files that are on a Cluster Shared Volume and local volumes.
A snapshot of a Virtual Machine in this configuration cannot be taken.
ANS2750E
The Hyper-V Virtual Machine 'virtualmachinename'
is currently undergoing one of the following operations: *
Creating Local Snapshot * Applying Local Snapshot *
Deleting Local Snapshot * Exporting Virtual Machine *
Migrating Virtual Machine * Volume Snapshot Service (VSS) Snapshot *
Restore * Merging Differencing Disks The above operations
prevent a Hyper-V VSS snapshot from taking place. Wait for the operation
to finish or cancel to perform a backup.
ANS2753I
Establishing inter-client communication with node node(s).
ANS2785I
Gathering current DB2 configuration
for 'type' restore.
ANS2798E
Unable to start a session from client node 'nodename'
multi-node 'multi-node' to client at address 'ip-address:ip-port'.
The TSM return code is rc.
ANS2799E
An error was encountered during a session with another client. check
the TSM error log for any additional information
ANS2807E
An incorrect number of parameters was specified for the command-name command.
ANS2808W
Incremental by snapshot difference backup did not locate
the registered base snapshot 'regbase-name' on NetApp/N-Series
filer volume 'volume-name'. Snapshot 'olderbase-name'
is used as the base snapshot.
ANS2809E
The backupid 'backupid:' in the input file
does not match the vmname 'vmname:' being restored.
ANS2810E
The TSM for Virtual Environments Input File 'input
file:' appears to be empty.
ANS2811E
The TSM for Virtual Environments could not find a suitable
datamover agent for the DataCenter Node 'datacenter nodename'.
ANS2812E
The TSM for Virtual Environments could not find Datamover
node named 'datamover nodename' on the TSM Server.
ANS2813E
The TSM Server returned an empty network address or port
number for 'datamover nodename'.
ANS2814E
TSM for Virtual Environments detected an error while
parsing the Input File 'input file'. The 'specifier'
appears to be empty or invalid.
ANS2815E
TSM for Virtual Environments detected an error while
parsing 'read in line' from the Input File 'input
file'.
ANS2816E
TSM for Virtual Environments detected that the TSM Server
IP address was not specified.
ANS2817E
TSM for Virtual Environments detected that the vCenter
Command-Line interface node name was not specified.
ANS2818E
TSM for Virtual Environments detected that the TSM Server
port was not specified.
ANS2820E
An interrupt has occurred. The current operation will end
and the client will shut down.
ANS2821E
The function is not supported on the platform.
ANS2824E
TSM for Virtual Environments detected that the node name
representing the vCenter is not specified.
ANS2825E
TSM for Virtual Environments detected that the node name
representing the Datacenter is not specified.
ANS2826E
TSM for Virtual Environments detected that the node name
representing the vCenter Datamover is not specified.
ANS2827E
TSM for Virtual Environments detected that the input
file is not specified.
ANS2828E
Image operations are not supported for the specified file
system.
ANS2829E
Image operations are not supported for GPFS.
ANS2830E
An incorrect number of parameters was specified.
ANS2831E
Incremental by snapshot difference cannot be performed on
'volume-name' as it is of type 'type'
and is not a NetApp/N-Series 'fsType' volume.
ANS2832E
Incremental by snapshot difference failed for filespace
name. See the error log for details.
ANS2834E
You have to be a root user in order to perform incremental
backup using snapshot difference.
ANS2835E
Incremental backup using snapshot difference is not supported
on this platform.
ANS2836E
Incremental backup operation using snapshot difference is
only available for full volumes. is a partial
volume or qtree.
ANS2837E
Unable to access the required stored NetApp filer credentials
(user id and password) for filer ''.
Make sure the SET PASSWORD -TYPE=FILER command was specified correctly
to store the credentials.
ANS2838W
The file path 'filename' exceeds HSM maximaum
path length.
ANS2839E
Failed with ONTAPI error 'error_code' while
connecting to NetApp Filer 'filer_name' using user
id 'id_name'. You might have provided credentials
incorrectly for this Filer.
ANS2840E
Incremental backup using snapshot difference is not supported
for Data ONTAP file server version 'version.modification.submodification'.
Upgrade the file server 'file-server-name' to Data
ONTAP version '7.3' or later in order to perform incremental backup
operations using snapshot difference.
ANS2841E
Incremental by snapshot difference is only supported on AIX 64 bit and Linux 86 bit clients.
ANS2842E
TSM for Virtual Environments detected an error with the
createsnap: keyword. createsnap:yes is specified while also specifying
vmsnapname:VMWare Snapshot Name.
ANS2849E
Incremental backup operation using snapshot difference failed
because a snapshot matching 'snapshot name' could not
be located on volume NAS volume.
ANS2850E
Error Creating Snapshot: Volume NAS volume is
a snapmirror destination volume.
ANS2852W
Registered Base Snapshot '' no longer exists
on volume .
ANS2853E
Unable to establish base snapshot on volume .
ANS2854E
Unable to establish diff snapshot on volume .
ANS2855W
TSM for Virtual Environments detected an error while
parsing the Input File 'input file'. The 'specifier'
should not be specified when using 'specifier'. Option
will be ignored.
ANS2856E
TSM for Virtual Environments detected that the node name
representing the vCloud is not specified.
ANS2857E
TSM for Virtual Environments detected while parsing 'read
in line' from the input file 'input file' that
option 'specifier' is required for 'operation'
operation.
ANS2858E
Failed to get the list of available VMs for backup
ANS2859E
Failed to locate the Organization VDC node that is used to
store the backed up data.
ANS2860E
The PRESNAPSHOTCMD command failed. The snapshot differential
backup will not be executed.
ANS2862E
No entry found for the specified Storage Virtual Machine.
ANS2863E
The backup-archive client failed to load the vCloud protection
runtime library.
ANS2864E
A Hyper-V operation was attempted, but the Hyper-V role was
not detected on the host system.
ANS2865E
An error occurred creating or accessing a virtual disk for
virtual machine 'VM-name'.
ANS2866E
An error occurred creating virtual machine 'VM-name'.
ANS2867E
An error occurred querying virtual machine 'VM-name'.
ANS2868E
An error occurred removing virtual machine 'VM-name'.
ANS2869E
A virtual machine on the hypervisor has a different name
but the same ID as virtual machine to restore 'VM-name'
has. Restore not allowed.
ANS2870W
An incremental backup of virtual machine 'vmname'
was requested, but the virtual machine lacks an existing recovery
snapshot. A full backup will be taken to prevent data loss.
ANS2872E
TSM was unable to restore a virtual disk user metadata
entry of virtual machine 'vmname' to disk 'diskpath'.
ANS2873I
Virtual machine 'vmname' was successfully
restored. If this virtual machine was restored to a cluster, ensure
that the cluster settings enable the restored virtual machine to operate
in high availability mode. High availability settings, and the preferred
set of hypervisor nodes that can operate in high availability mode,
might not be set automatically.
ANS2876E
Unable to access the required stored NetApp Management Filer
credentials (user id and password) for filer '' associated
with storage virtual machine '' . Make sure
the SET PASSWORD -TYPE=FILER command was specified correctly to store
the credentials.
ANS2888E
Backup VM Full VM Incremental is unable to run. A
valid TSM for Virtual Environments license file (license-file)
cannot be located.
ANS2889I
The vApp 'vapp name' was successfully restored
under the name 'new vapp name'
ANS2891W
The vApp 'vapp name' was successfully restored.
However, failed vms num out of existing vms
num VMs were not restored.
ANS2900E
TSM for Virtual Environments detected that the scan domain
was not specified.
ANS2901E
TSM for Virtual Environments detected that the domain
user was not specified.
ANS2902E
Save domain password failed in function func-name with
return code return-code.
ANS2903E
Read domain password failed in function func-name with
return code return-code.
ANS2998I
The option 'option' that was found in the
include/exclude file 'file-name' at the line number: number is
not supported and will be ignored by the client.
ANS3000I
communication-type communications available
on port port-number.
ANS3002I
Session started for user userid (communication-method address).
ANS3011E
Previous changes have not been commited. The machine
must be rebooted before this operation can be performed
ANS3012E
The Logical Volume Snapshot Agent is not installed. Use the
Setup Wizard to configure either Online Image or Open File support
and choose the Logical Volume Snapshot Agent as the snapshot provider.
ANS3013E
The specified snapshot provider is not supported on this
version of the operating system.
ANS3014E
Expose snapshot failed for backup document 'xml-backup-doc-file'.
ANS3100E
Unable to get the iSCSI initiator name. The Windows error is (error)
ANS3101E
The mount operation for virtual machine 'vmname'
failed with rc = return-code
ANS3102I
'VMNAME' mounted successfully and is ready
ANS3103E
Unable to load the dynamic link library (iscsidsc.dll). The Windows error is (error)
ANS3104E
A target was not found on the iSCSI portal The missing
target is 'target'
ANS3105E
Unable to connect all targets on the iSCSI Portal The
target that is not connected is 'target'. Windows error is (error)
ANS3106E
Windows Configuration
Manager is unable to scan for new hardware. Windows error is (error)
ANS3107E
The attempt to retrieve information for disk 'disk'
failed with Windows error
(error).
ANS3108W
The disk with label='label' is not mounted
because it was excluded during the backup (Reason: 'reason').
ANS3110E
Unable to communicate with Windows device
'device'. The Windows error
is (error)
ANS3111E
Unable to mount the same dynamic disks mutliple times. The
disk 'disk' signature is the same as the disk signature
of another disk that is online.
ANS3112E
Windows Virtual
Disk Service is not able to detect all new devices.
ANS3113E
The virtual machine 'name' has at least one
mirror or RAID5 volume. Mirror and RAID5 support is disabled!
ANS3114E
The attempt to retrieve information for volume 'volume'
failed with Windows error
(error).
ANS3115E
The attempt to bring disk 'disk' online failed
with Windows error (error).
ANS3116E
The attempt to create directory 'dir' failed
with Windows error (error).
ANS3117E
The mount volume attempt at directory 'dir'
failed with Windows error
(error).
ANS3118E
Unable to determine the operating system type of the VM to
be restored.
ANS3119W
Operating system type "name1" is detected
but operating system type "name2" is specified.
ANS3122E
The Microsoft iSCSI
Initiator Service encountered an error. The Windows error is (error).
ANS3123E
Unable to read or write the local VM file-level restore data. filename File
cannot be accessed or is damaged.
ANS3125E
The local data for file-level restore mount with the ID: id and
virtual machine name 'name' cannot be found!
ANS3126E
The node name of the Linux mount
proxy partner could not be found.
ANS3127E
The IP address or port of the Linux mount
proxy partner could not be found.
ANS3128E
The node name of the Windows mount
proxy does not comply with TSM naming conventions.
ANS3129I
The mount cleanup of VM 'VMNAME' completed.
ANS3130E
The mount cleanup operation for virtual machine 'vmname'
failed with rc = return-code
ANS3131E
The operation to disconnect the iSCSI targets from the Windows data mover failed.
ANS3132E
The Windows iSCSI
Service is unable to get a list of all currently running sessions.
The Windows error is (error)
ANS3133E
The target 'target' could not be disconnected
by the iSCSI portal. The Windows error
is (error)
ANS3134E
The Windows iSCSI
Service is unable to get list of all currently available portals.
The Windows error is (error)
ANS3135E
The removal of iSCSI Portal 'target' failed
with a Windows error of (error)
ANS3136E
The mount ID was not specified in the cleanup operation.
ANS3146E
The cleanup operation to unmount the volume volume failed.
The mounted file system is busy.
ANS3147W
The iSCSI Target 'iscsi_target'was disconnected
successfully, but the attempt to delete the target failed.
ANS3148W
The iSCSI Target 'iscsi_target' was already
connected.
ANS3149E
The iSCSI target 'target' failed to disconnect
from the Linux machine. The
message from the iscsiadm command-line interface is: message_output
ANS3150W
The block device 'block_device' of type 'device_type'
failed to mount. The system message is: 'system_message'
ANS3151E
The initiator.iscsi file does not exist or cannot be opened.
ANS3152E
The initiator.iscsi file does not have a valid initiator
id entry.
ANS3153E
The mount cleanup completed with error for mount ID 'mountid'
of virtual machine 'VMNAME'; Error log 'errlog'
is available on 'machinename'.
ANS4016E
Error processing 'filespace namepath-namefile-name':
file is being executed; write permission denied
ANS4017E
Error processing 'filespace namepath-namefile-name':
too many symbolic links were detected while resolving name
ANS4018E
Error processing 'filespace namepath-namefile-name':
file name too long
ANS4019E
Error processing 'filespace namepath-namefile-name':
file system is locked by system
ANS4020E
The data format for object 'filespace namepath-namefile-name'
is unknown. The unknown format usually occurs when the file was backed
up or archived by a later version of IBM Tivoli Storage Manager.
ANS4021E
Error processing 'filespace namepath-namefile-name':
file system not ready
ANS4022E
Error processing 'filespace namepath-namefile-name':
file system is invalid.
ANS4050W
Scheduled action 'schedule-action' did not
execute for schedule 'schedule-name' as the TSM administrator
has been disabled from executing the scheduled action on the client.
ANS4051E
Error processing 'filespace namepath-namefile-name':
The decryption option is in effect, but the user ID under which back-up
or archive is being run is not authorized to decrypt this encrypted-file-system
(EFS) file.
ANS4052E
Error processing 'filespace namepath-namefile-name':
Encrypted-file-system (EFS) file cannot be restored, because file
system does not support restore from the raw-EFS back-up data, or
possibly because the restore function does not have write access to
the directory.
ANS4053E
Error processing 'filespace path filename':
The file cannot be restored because the file system or operating system
does not support the Encrypting File System (EFS) data.
ANS4054E
Error processing 'filespace namepath-namefile-name':
The encryption key is not loaded.
ANS4055E
Cannot update file space 'filespace-name':
the file space version on the TSM server is not compatible with
this client
ANS4056E
Object 'object-name' returned by the IBM Tivoli Storage Manager server
has a high-level name that exceeds the maximum length of 6000 characters.
The file or directory cannot be processed.
ANS4058I
A write failure occurred while attempting to save node replication
failover values to the options file.
ANS4059I
The option USEREPLICATIONFailover is set to NO. The node
will not fail over to the secondary server
ANS4061I
Connected to secondary server secondary server; in
fail over mode. Home server is: home server;
ANS4063W
IBM Tivoli Storage Manager application protection cannot copy the application
metafile 'App-Metadata-File-Name' from the following
VM: 'VM-Name'. Individual database restore from this
backup is not supported.
ANS4064I
Restoring vCloud Director vApp 'vapp name'
from Organization VDC 'org vdc name' from organization
'org name' Target vApp name is 'restored
vapp name' Restore VAPP command started. Total
number of vApps to process: vapps num to restore
ANS4065E
Proxy rejected: data mover node 'dm node'
has not been granted proxy authority for target node 'target_node',
associated with Organization vDC 'OVDC name' of Organization
'Org Name'.
ANS4066W
Snapshot operation attempt x of y for
the guest virtual machine 'VM' failed using "sType"
snapshot. Reattempting snapshot with "sType2"
snapshot.
ANS4067E
Snapshot operation attempt x of y for
the guest virtual machine 'VM' failed using "sType"
snapshot. Backup failed.
ANS4068I
Restored virtual machine 'VM' was backed up
using a "VMware Tools with file system quiescing and application quiescing
disabled" snapshot. This is equivalent to a "crash-consistent"
backup.
ANS4077E
File 'filespace namepath-namefile-name'
is encrypted by Microsoft EFS
and contains at least one sparse data stream. The operating system
does not support restore for this file so it is not backed up or restored.
ANS4081E
Error processing 'filespace-name': file space
type is not supported.
ANS4084E
Error processing 'filespace-namepath-namefile-name':
cannot get file status.
ANS4085I
Assigned 'number' objects from previous systemstate
backup to the new systemstate backup.
ANS4086W
Failed to assign unchanged objects from previous systemstate
backup to the new systemstate backup. Objects will be backed up.
ANS4087E
An attempt to load data for the wizard failed. For
more information, please see the log file.
ANS4089W
File server file-server-name has been upgraded
to Data ONTAP version 'version.modifcation.submodification'.
Perform a full incremental backup by specifying option createnewbase=migrate
as soon as possible.
ANS4090I
File server file-server-name has been upgraded
to Data ONTAP version 'version.modifcation.submodification'.
Perform a full incremental backup by specifying option createnewbase=migrate
as soon as possible.
ANS4092E
Data mover platform is not supported for instant access/restore
operations.
ANS4099E
The system volume cannot be identified. Therefore the system
state cannot be backed up.
ANS4137E
Error processing 'filespace namepath-namefile-name':
exceeded maximum number of links allowed
ANS4148E
Full VM backup of Virtual Machine 'vmname'
failed with RC rc
ANS4150E
Incremental backup of Virtual Machine 'vmname'
failed with RC rc
ANS4152E
Failure initializing VMware virtual machine environment.
RC=rc. Refer to IBM Tivoli Storage Manager error log for detailed error
messages.
ANS4153E
Hostname could not be found for Virtual Machine 'vmname'
ANS4154E
Possible cause Virtual Machine is not running and does not
have a static IP address.
ANS4155E
Virtual Machine 'vmname' could not be found
on VMware server.
ANS4156E
File level VM backup of virtual machine 'vmname'
not supported. File level VM backup not support on non Windows platform guest OS. Platform
type: 'platform'.
ANS4159E
Backup of Virtual Machine 'vmname' failed.
rc=rc.
ANS4160E
Proxy Rejected: Proxy authority has not been granted to Agent
Node: 'agent_node' for Target Node: 'target_node'.
ANS4161E
Duplicate virtual machine name 'vmname' was
detected in the same backup operation. Backup of virtual machine 'vmfullname'
can not continue without a unique object name.
ANS4162E
The virtual machine 'virtual-machine-name'
has not been previously backed up.
ANS4163I
Encryption is currently enabled, but the virtual machine
backup for 'virtual-machine-name' will not be encrypted.
ANS4164W
Compression is currently enabled, but the virtual machine
backup for 'virtual-machine-name' is not compressed
because client-side deduplication is not being used.
ANS4165E
Creating a Virtual Machine, but the hostname 'virtual-machine-name'
was not found.
ANS4166E
Creating a Virtual Machine, but the datacenter 'virtual-machine-name'
was not found. The name may be incorrect or may be located in a VMware
folder and require the folder name such as vmfolder/dcname.
ANS4167E
Creating a Virtual Machine, but the datastore 'virtual-machine-name'
was not found.
ANS4168E
VMware has reported an error via their SOAP interface. On
the Detailed Status Report panel, view the last error message reported.
Also check the error log for more information about the problem that
occurred.
ANS4169E
A write failure occurred on the local disk proxy used to
temporarily store the virtual machine virtual disk information. The
write failure can be caused by the lack of available disk space on
the drive used to store this information. The VMBACKDIR option can
be used to assign a different disk location for this purpose. Check
the drive being used and ensure that there is enough space available
for this operation.
ANS4170E
Can not create a Virtual Machine on VMware release 'release-version-target'
which was backed up from VMware release 'release-version-source'.
ANS4171E
Backup of virtual machine 'vmname' failed.
VM could not be contacted because of 'vmfullname'
connection state.
ANS4174E
Full VM backup of VMware Virtual Machine 'vmname'
failed with RC=rc mode=full_or_incr,
target node name='target_node_name', data mover node
name='data_mover_node_name'
ANS4177E
Full VM restore of VMware Virtual Machine 'vmname'
failed with RC=rc target node name='target_node_name',
data mover node name='data_mover_node_name'
ANS4178W
Compression is currently enabled, but the virtual machine
control files for 'virtual-machine-name' will not be
compressed because client-side deduplication is not being used for
the management class default or specified by the -vmctlmc option for
'vm-ctl-mgmt-class-name'.
ANS4179I
IBM Tivoli Storage Manager application protection did not truncate the Microsoft SQL Server logs on
VM 'VM'.
ANS4187W
CPU and Memory Resource Allocation configuration settings
cannot be restored when the IBM Tivoli Storage Manager data mover node is connected
directly to a Virtual Center managed ESX/ESXi host. These settings
have been skipped.
ANS4191E
Restore VM operation failed using 'san' transport mode. In
some cases switching from SAN to network-based VM restores can be
successful.
ANS4193E
vApp 'vApp name' cannot be processed because
data mover 'dm node' cannot connect to the target node
'target_node'.
ANS4194E
Encryption is currently enabled, but is not supported for
incremental forever backups of virtual machines (-MODE=IFFULL or -MODE=IFINCREMENTAL)
.
ANS4195E
The target node for Organization VDC 'OrgVDC name'
in Organization 'Org name' was not found. As a result,
vApp 'vApp name' cannot be backed up.
ANS4199W
File 'file name' is not backed up as part
of the system state because cluster disk 'volume name'
is not accessible.
ANS4202E
The Deployment Manager failed to install language pack: language
pack name. The Microsoft Installer
error code was error code.
ANS4293E
Backup of VMware vApp 'vApp name' in Organization
VDC 'Org VDC name' of organization 'Org name'
failed.
ANS4301I
IBM Tivoli Storage Manager detected Microsoft Active
Directory Domain Controller on virtual machine 'VM'.
ANS4302W
IBM Tivoli Storage Manager failed to detect if Microsoft Active Directory Domain Controller on virtual
machine 'VM'.
ANS4303E
The vCloud Director vApp 'vapp-name' has not
been previously backed up.
ANS4304I
IBM Tivoli Storage Manager could not detect the TSM for VE license. Active
Directory Domain Controller will not be protected on VM 'VM'.
ANS4305W
Backup of VMware vApp 'vApp name' in Organization
VDC 'Org VDC name' of organization 'Org name'
completed. Some VMs were not backed up. mode:
'Incremental Forever - full_or_incr' target
node name: 'target_node_name' data
mover node name: 'data_mover_node_name' VMs
backup status: number of VM backed up out of number
of VMs in vApp VMs backed up successfully.
ANS4308E
Full VM backup of 'hypervisor' Virtual Machine
'vmname' failed with RC=rc mode=full_or_incr,
target node name='target_node_name', data mover node
name='data_mover_node_name'
ANS4311E
Full VM restore of 'hypervisor' Virtual Machine
'vmname' failed with RC=rc target node
name='target_node_name', data mover node name='data_mover_node_name'
ANS4446E
A file-level restore mount operation for hypervisor
type Virtual Machine 'vmname' failed. The data
center node name is 'data center node name', the mount
proxy node name is 'mount proxy node name'
ANS4449E
A cleanup of the file-level restore of hypervisor
type Virtual Machine 'vmname' failed. The data
center node name is 'data center node name', the mount
proxy node name is 'mount proxy node name'
ANS4450E
Mount proxy platform is not supported for file-level restore
operations.
ANS4451E
The Windows iSCSI
service is not available.
ANS4900W
Schedule 'schedule-name' has opened a new
session with the server.
ANS4901E
The following object contains one or more unmatched quotation
marks and cannot be processed: 'filespace path filename'.
ANS4904E
Instant access of VMware Virtual Machine 'vmname'
failed. target node name='target_node_name', data mover
node name='data_mover_node_name'
ANS4907E
Instant restore of VMware Virtual Machine 'vmname'
failed. target node name='target_node_name', data mover
node name='data_mover_node_name'
ANS4910E
Cleanup of VMware Virtual Machine 'vmname'
failed. target node name='target_node_name', data mover
node name='data_mover_node_name'
ANS4915I
Object increased in size during compression: filespace pathfilename
ANS4942E
The file specification 'string' is invalid.
ANS4946W
Warning: virtual machine: 'vm-name' disk:
'disk-name' excluded by user, was not found.
ANS4947E
Error: virtual machine: 'vm-name' disk: 'disk-name'
included by user, was not found.
ANS4948E
A specified virtual disk was not found on the virtual machine.
ANS4972W
File server file-server-name has been upgraded
to Data ONTAP version 'version.modifcation.submodification'.
This version does not support unicode file names for snapshot difference
incremental backup. Upgrade to a version that supports unicode file
names as soon as possible.
ANS4973E
An error occurred accessing NTFS security information for
file 'filespace namepath-namefile-name'
ANS4974E
Error processing 'filespace namepath-namefile-name':
a required NT privilege is not held.
ANS4987E
Error processing 'filespace namepath-namefile-name':
the object is in use by another process
ANS4988W
File 'filespace namepath-namefile-name'
is currently unavailable on server and has been skipped.
ANS4989E
Error processing 'filespace namepath-namefile-name':
the directory is in use by another process. All objects in the directory
and any of its subdirectories are skipped.
ANS4991I
Application Type Application Message
Id Application Message
ANS4992W
Application Type Application Message
Id Application Message
ANS4993E
Application Type Application Message
Id Application Message
ANS4994S
Application Type Application Message
Id Application Message
ANS4997E
Error processing 'filespace namepath-namefile-name':
file system quota reached condition - no space left.
ANS4998E
Link information for file 'filename' could
not be obtained: access to the object is denied.
ANS4999I
The
following message was too long to log to the server: 'shortened
message with message number'
ANS5003S
The management class assigned to directories does not exist.
ANS5004S
There is no backup copy group in the management class used
for directories. See the error log.
ANS5005E
Table of contents information is not available for the selected
images.
ANS5006W
The policy set does not contain any backup copy groups. TSM is
unable to continue the backup.
ANS5007W
The policy set does not contain any archive copy groups. TSM is
unable to continue the archive.
ANS5093S
SLM_LICENSE_EXCEEDED: The client licenses for TSM are
exceeded. See your TSM administrator.
ANS5094E
Session Rejected. Sufficient server memory is not available.
ANS5122E
The specified filespace does not exist on the server. The
filespace might have been deleted by another client or an administrator.
ANS5123S
Open registration failed because the specified node name
is already defined in the server.
ANS5124S
Open registration failed because there is no default domain.
ANS5125S
Open registration failed because an invalid node name was
specified.
ANS5126S
Filespaces with duplicate names are not supported. Please
unmount the duplicate filespace.
ANS5127I
TSM has detected an incomplete setup! The
system options file 'dsm.sys' was not found, while the client options
file 'file-path' exists! The wizard
will guide you through the configuration process of the initial basic
TSM client options files replacing your current option file. Would
you like to continue?
ANS5128E
The management class for this file did not have a backup
copy group.
ANS5129E
The management class for this file did not have an archive
copy group specified.
ANS5139E
Your node does not have permission to delete archived files.
ANS5145W
Server cannot restart the last restore request. Do you want
to restore without restart?
ANS5146W
You cannot perform this operation while accessing data for
another node. Do you wish to switch back to accessing your own node?
ANS5148W
The server needs to do a one-time conversion of your archive
data before you can continue. This operation may take a long time,
and cannot be canceled once it has started. Are you willing to wait
for the conversion to complete?
ANS5150E
An active restore for the same source file specification
exists. Unable to continue with this request.
ANS5151S
This node currently has a pending restartable restore session.
The requested operation cannot complete until this session either
completes or is canceled.
ANS5152S
Session Rejected: The server is not licensed for this platform
type. See your TSM administrator.
ANS5153E
Session Rejected: The server does not allow a signon as a
Unicode enabled client.
ANS5155E
Valid password not available. The TSM administrator
for your system must run TSM and enter the password to store it
locally.
ANS5158S
Filespace deletion is in progress. Try again later.
ANS5164E
Backup or archive of drives with duplicate volume labels
is not allowed.
ANS5165E
Drive has no volume label. Backup/Archive not allowed.
ANS5166E
An error occurred while removing include-exclude statement
'statement'. Please try again.
ANS5176W
The requested virtual machine operation cannot be performed
because a virtual machine backup or restore operation is already in
progress. Please retry the operation after the first operation completes.
ANS5177E
Client-side deduplication and server-initiated sessions are
mutually exclusive.
ANS5178E
Restart of the RSM service failed. Restart the RSM service
manually.
ANS5179E
TSM is unable to continue. Exiting program.
ANS5181E
Invalid selection; A specific backup set must be selected.
ANS5182E
Multiple backup sets can not be restored at the same time.
ANS5183W
Objects of different types cannot be restored at the same
time.
ANS5184E
Illegal Operation On Following Object: object
ANS5186E
Server is downlevel, System Services and System State backup
disabled for this session.
ANS5187E
Unable to set SHAREAS extended attribute for file: 'pathname' Return
code: 'returncode' 'strerror' Reason
code: 'reasoncode'
ANS5191E
NT Active Directory is not online. Offline backup is not
supported.
ANS5192E
NT Active Directory is online. Online restore is not supported.
ANS5193E
Certificate Services is not online. Offline backup is not
supported.
ANS5194E
Certificate Services is online. Online restore is not supported.
ANS5211E
The cluster service is offline. The cluster service must
be online to perform an authoritative cluster database restore operation.
ANS5212E
An error occurred while trying to rename file space.
ANS5215E
function-type is not allowed on object 'object'. Object
is not sent to the server.
ANS5216E
Could not establish a TCP/IP connection with address 'tcp-addr:tcp-port'.
The TCP/IP error is 'tcp-err-string' (errno = errno).
ANS5217E
Your node does not have permission to delete backed up files.
ANS5219W
Objects of different groups cannot be restored at the same
time.
ANS5222E
The archive description exceeds 254 characters.
ANS5224W
Error error code encountered while reverting
to the restored snapshot.
ANS5225W
Error error code encountered while removing
the restored snapshot.
ANS5226E
The virtual machine backup operation failed.
ANS5227E
TSM detected an error where both a snapshot name was
specified, and a request to create a snapshot were specified.
ANS5228E
A backup VM operation failed because VMMAXPARALLEL was reduced
to 1 and the client still cannot obtain a server mount point.
ANS5229E
The Snapshot is already mounted for backup 'backup-name'.
ANS5230E
The Snapshot is already imported to the local system for
backup 'backup-name'.
ANS5231E
VMDK size reported by VMware vSphere API is different than
actual size of vmdk file. Reissue the restore command with the testflag
-VMRESTORE_INCVMDKSIZE.
ANS5232I
The virtual machine backup operation was skipped.
ANS5245W
TCPWINDOWSIZE optionCur is specified, but
exceeds the maximum value allowed by TSM. TCPWINDOWSIZE optionNew will
be used instead.
ANS5246W
TCPWINDOWSIZE optionCur is specified, but
exceeds the maximum value allowed by the operating system. TCPWINDOWSIZE optionNew will
be used instead.
ANS5249E
The virtual machine restore operation failed.
ANS5250E
An unexpected error was encountered. TSM function
name : function-name TSM function
: function-desc TSM return code : TSM-rc
TSM file : file-name (line-number)
ANS5251E
The snapshot provider is not available for this operation.
ANS5252E
TSM attempted to execute a system command which failed.
command : command rc : rc
ANS5253W
The system could not create Volume Shadow Copy Services staging
directory 'dir'.
ANS5254E
The Volume Shadow Copy Services snapshot plugin 'pivss.dll'
was not found.
ANS5255E
Unable to copy local file 'local-file' to
remote location 'remote-file'.
ANS5257E
The volume 'volume' does not support the requested
VSS operation.
ANS5258E
Microsoft volume
shadow copy snapshot initialization failed.
ANS5259W
Failed to update volume 'volume' for read-write
access used for 'volume'.
ANS5260W
Restore object 'volume' has volume either
source 'volume' or target 'volume' volume
that has already been selected for restore from a different snapshot
volumes. It will be restore using file-level copy.
ANS5261W
An attempt to create a snapshot has failed. Another
attempt will be made to create the snapshot in number seconds.
ANS5262I
Snapshot restore will failover to file-level copy from snapshot
volume.
ANS5263E
Snapshot module for 'snapshot provider' failed
with error 'error msg'.
ANS5264W
No snapshot plugin found for 'snapshot provider'
snapshot provider.
ANS5265W
Snapshot restore has already been initialized using 'snapshot
provider' provider module. Another module for 'snapshot
provider' provider can not be loaded at the same time for restore
of 'object name'.
ANS5266E
File-level copy restore of 'object name' failed.
ANS5267E
Disk Mapper module failed for the operation.
ANS5268W
The Microsoft Volume
Shadow Copy Services writer 'name' current state (state)
is not valid for the current operation.
ANS5269E
The Microsoft Volume
Shadow Copy Services writer 'name' current state (state)
is not valid for the current operation or cannot be determined. The
last error reported is 'error'.
ANS5270E
A VSS restore request with timestamp 'time1'
conflicts with a restore request with timestamp 'time2'
ANS5271E
A Microsoft Volume
Shadow Copy Services writer is in an invalid state before snapshot
initialization.
ANS5272E
A Microsoft Volume
Shadow Copy Services writer is in an invalid state after snapshot
initialization.
ANS5273E
A Microsoft Volume
Shadow Copy Services writer is in an invalid state after taking a
snapshot.
ANS5274E
A Microsoft Volume
Shadow Copy Services writer is in an invalid state after backup completion.
ANS5275E
A Microsoft Volume
Shadow Copy Services writer is in an invalid state before restore
initialization.
ANS5276E
A Microsoft Volume
Shadow Copy Services writer is in an invalid state after preparing
for a restore operation.
ANS5277E
A Microsoft Volume
Shadow Copy Services writer is in an invalid state after restore termination.
ANS5279E
Error processing 'filename': file not found.
ANS5280E
Object enumeration from a file set or file list failed.
ANS5281E
A remote backup failure has occurred. remote node
name : node remote address : address
multi-node name : multi-node error
message : msg return code : rc
ANS5284I
TSM has detected an incomplete setup! The
client options file 'dsm.opt' was not found, while the system options
file 'file-path' exists! The wizard
will guide you through the configuration process of the initial basic
TSM client options files replacing your current option file. Would
you like to continue?
ANS5285E
The Microsoft Volume
Shadow Copy Services (VSS) backup XML document is not valid for restore.
For more information, see the TSM client error log.
ANS5286I
The VSS Instant Restore operation was successful but some
existing VSS snapshots have been deleted by the VSS provider.
ANS5287W
VSS restore operation will be performed using VSS Fast Restore
because the XIV VSS Hardware
Provider is at level 2.2.2.
ANS5288W
Test flag DISCARDZEROFILEDATA enabled. Discarding data for
zero length object file-name
ANS5296I
The virtual machine 'vm-name' contains one
or more virtual disks that are of type Thick Eager Zero. Creating
disks of this type can take a long time. This restore operation might
time out before the disks are ready.
ANS5298E
A Flashcopy background copy is in progress between source
volume: and target volume: .
ANS5299E
A Flashcopy association exists between source volume: and
a different target volume: .
ANS5300E
Error detected in specified file list 'file list
name' during processing of line line number: found
an invalid external object ID / inode number / inode generation
number / restore order number / alias entry: 'invalid
entry'. Invalid line: 'invalid entry'
ANS5301E
Error detected in specified file list 'file list
name' during processing of line line number: found
an invalid ordering of external object IDs. ext. object
ID of previous file: previous external object ID ext.
object ID of current file: current external object ID
ANS5302E
File list stream error to file 'file list name'
detected during processing of line line number.
ANS5303I
***** date Processed count TSM server
and count file list objects *****
ANS5824E
Invalid Active Directory search specification.
ANS5825E
Reanimate 'tombstone-name' to 'distinguished-name'
failed. See the error log for more details.
ANS5826E
Restoring to a read-only domain controller is not allowed.
ANS5827E
A backup copy of the Active Directory database was not found.
ANS5828E
A system state file space was not found on the server. Active
Directory functions can not be executed.
ANS5829E
A system state backup on the specified date was not found.
Active Directory functions can not be executed.
ANS5830E
Restore of object 'tombstone-name' is not
allowed by Active Directory.
ANS5831E
Restore for this object is not allowed by Active Directory.
ANS5832E
Reanimate tombstone object failed. See the error log for
more details.
ANS5833E
This system is a Domain Controller but the Active Directory
service is stopped. You can not perform the operation unless the Active
Directory service is running.
ANS5834E
Unexpected LDAP error occurred. See the error log for more
details.
ANS5835E
An LDAP operation returned return code: 'error
string'
ANS5836W
One or more attributes were not restored. See the error log.
ANS5837W
'object name': attribute 'attribute
name' could not be restored.
ANS5838E
The utility dsamain.exe does not exist on the system. You
cannot perform the operation unless Tivoli Storage
Manager can launch this utility.
ANS5839E
The Active Directory object specification is not allowed.
ANS5840E
The current user is not a member of the Administrators group,
and cannot perform this function.
ANS5841E
Active Directory database could not be opened.
ANS5842E
'tombstone-name': object class violation.
ANS7641I
The user does not have administrative credentials to perform
a full system state backup.
ANS7642E
An error occurred creating the registry directory structure.
ANS7650E
The user does not have sufficient privileges to execute IBM Tivoli Storage Manager.
ANS7660E
An error occurred replacing one or more registry keys.
ANS7709E
Restore operation failed. Not all files were restored.
ANS7899E
The client referenced a deduplicated extent that does not
exist on the TSM server
ANS7900W
Deduplication cache has been reset because it is not synchronized
with the TSM server
ANS7901W
Client deduplication and option-name are mutually
exclusive.
ANS7902I
Client deduplication cache is full. Cache is reset.
ANS7903W
Client deduplication cache is locked by another process.
ANS7904E
Client deduplication and lan-free or subfile backup are mutually
exclusive.
ANS7906W
The current storage pool either ran out of space or the current
object exceeded the maxsize configuration parameter for the storage
pool, data will be stored into the next pool - deduplication is disabled.
ANS7907W
Connection to repository repos-name failed.
Retrying with repos2-name.
ANS7908E
Unable to mount FastBack snapshot policy 'Policy'
client 'Client' volume 'Volume'. Reason: reason
ANS7912E
FastBackMount or FastBackShell is not installed.
ANS7913E
The given branch was not found in the DR Hub repository.
ANS7914E
Incremental backup of FastBack client 'vmname'
failed with RC rc
ANS7915E
Failure mounting FastBack client 'vmname'
with FastBack command. RC=rc
ANS8046E
The client connection with the server has ended due to an
unexpected error.
ANS8047E
The client connection with the server has ended due to a
communications buffer overflow.
ANS8048W
Warning! Performing image restore of the Linux file system 'src' to an alternate
destination 'dest' is not recommended as this may result
in duplicate UUIDs leading to failed mounts after a successful restore.
ANS8049E
A connection with the server cannot be established due to
a communications time-out.
ANS8050E
The TSM server is not accepting administrative sessions
on the client port. You must use the port number designated
for administrative sessions.
ANS8052E
Unable to decrypt file 'filespace namepath-namefile-name' ....Please
try to restore this file individually
ANS8061E
Session Rejected: The server does not allow a signon as
a Unicode enabled administrative client
ANS8062E
Client-to-Client communication is not allowed to take place
when TSM Server authentication is turned off.
ANS8063E
The remote TSM Client Acceptor associated with Node 'name'
could not authenticate with the TSM Server.
ANS8064E
Communication timeout. Reissue the command.
ANS8103W
A command was not successful. command
: command TSM function name : function-name
error output : error-output return
code : return code TSM file
: file-name (line-number)
ANS8104W
Cannot determine EFS status of the file system 'file-system
name', errno='errnor number', processing data
normally.
ANS8105W
Unable to remove snapshot for volume 'filespace-name'.
ANS8106E
Support for multiple IBM Tivoli Storage Manager servers is enabled on this
node. The server name must be specified for this command.
ANS8201E
Windows Hyper-V
incremental backups require Windows 2012
or later.
ANS8503I
No matching option found for pattern: 'pattern'.
ANS8563E
Recall mode has an invalid value: invalidValue.
ANS8565W
ProgramName: list of recall IDs not found
in queue. These recalls are already finished:
ANS8776E
The IBM Tivoli Enterprise Space Management Console
cannot be started. Java Runtime
Environment version version by company has
been detected on machine. A Java Runtime Environment version or
higher is required to run this program. If you have already
installed Java version on
this machine, please ensure that the correct Java executable is on your PATH, otherwise you
can download it from 'webAddress' and start
the program again.
ANS8777E
The IBM Tivoli Enterprise Space Management Console
cannot be started. An error occurred trying to load Tivoli look
and feel. Verify that the product is correctly installed.
ANS8778E
A browser program cannot be found or cannot be started. An error occurred executing the command. command Verify that a browser is installed and works correctly on
your local machine.
ANS8779E
A browser program cannot be found or cannot be started. One of the following browsers is required: browser-list Verify that one of these browsers is installed and works
correctly on your local machine.
ANS8780E
A browser program cannot be found or cannot be started. Check the 'file-name' file on your local machine
for more information.
ANS8781E
The system could not log on to TSM client node node-name on machine-name. Make sure your data and password are correct and
that caps lock key is not on. The Space Management Agent must
be running at the specified port on the machine to which you
are attempting to log on to.
ANS8782E
An error occurred while loading file system information on
'fs-name'. Verify that the Space Management
agent is running on the client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8783E
An error occurred loading file system properties of fsName required
to show space usage graphical information. Verify that
the Space Management agent is running on the client node machine. Check
also the local-log-file file in the installation directory
of your local machine and the $DSM_DIR/error-file file
on machine if present. If this does not identify
the cause of the problem, contact your system administrator and/or TSM technical
support for further assistance.
ANS8784E
An error occurred initializing the client nodes table. Your local configuration file 'config-file'
might be corrupted. Remove it from your installation directory
and start the program again. Check also the log-file file
on your local machine for more information.
ANS8785E
An error occurred disconnecting the system from the client
node 'node-name'. The Client node is
being disconnected without deleting internal HsmSystem objects. Verify that the Space Management agent is running on the
client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8786E
An error occurred loading file system information from the
selected client node. Verify that the Space Management
agent is running on the client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file in the client node machine
if present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8787E
An error occurred loading file system information from nodename client
node. The client node is being disconnected. Verify
that the Space Management agent is running on the client node machine. Check
also the local-log-file file in the installation directory
of your local machine and the $DSM_DIR/error-file file
on machine if present. If this does not identify
the cause of the problem, contact your system administrator and/or TSM technical
support for further assistance.
ANS8788E
An error occurred starting manually threshold migration on file-system. Verify that the Space Management agent is running on the
client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8789E
An error occurred trying to deactivate all managed file systems
of client-node. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8790E
An error occurred trying to reactivate all managed file systems
of client-node. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8791E
An error occurred trying to add space management to fs-name file
system. Verify that the Space Management agent is running
on the client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8792E
An error occurred trying to remove space management from file-system file
system. Verify that the Space Management agent is running
on the client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8793E
An error occurred trying to deactivate file-system file
system. Verify that the Space Management agent is running
on the client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8794E
An error occurred trying to reactivate file-system file
system. Verify that the Space Management agent is running
on the client node machine. Check also the local-log-file file
in the installation directory of your local machine and the
$DSM_DIR/error-file file on machine if
present. If this does not identify the cause of the problem,
contact your system administrator and/or TSM technical
support for further assistance.
ANS8795E
An error occurred trying to save your settings to config-file configuration
file on your local machine. Check the log-file file
in the installation directory of your local machine for more
information.
ANS8809E
The LD_LIBRARY_PATH is either not set or is set incorrectly.
Ensure that the LD_LIBRARY_PATH environment variable contains the
installation directory path name.
ANS8810E
The LD_LIBRARY_PATH is either not set or is set incorrectly.
Ensure that the LD_LIBRARY_PATH environment variable contains the
installation directory.
ANS8811E
VMware operations can not be run when the hardware plugin
product TIVsm-BAhdw is installed and loaded. Please either uninstall
the hardware product TIVsm-BAhdw, or set the option DONTLOAD PIHDW
in the options file to prevent the hardware plugin from being loaded.
ANS8818E
An error occurred trying to apply your changes. Your
changes have not been applied to the system. Contact
your system administrator.
ANS8819E
The following trace flag(s) are not valid: trace-flag-list. Correct
them before continuing.
ANS8820E
The HSM System Object was not found on the Space Management
agent. The error occurred when calling function: function-name. The
last operation was not processed correctly.
ANS8821E
Unable to create requested HSM object on Space Management
agent. The last operation was not processed correctly. The
problem is caused from a memory problem. Try to free memory on
the system where the Space Management agent is running. Or
restart the Space Management agent.
ANS8822E
HSM File System Object was not found on Space Management
agent. The error occurred when calling function: function-name The
last operation was not processed correctly.
ANS8823E
A Protocol error occurred in communication with the Space
Management agent This error occurs when a session with the
Space Management agent was lost, or network error caused synchronization
problem between the Space Management console and the agent.
ANS8824E
A internal error occurred in the Space Management agent. The
error occurred in function : function-name
ANS8825E
The Space Management API was unable to locate option object The
error occurred in function : function-name
ANS8826E
The Space Management API was unable to query a HSM device. This
error occurs because the HSM kernel extension was not loaded correctly
ANS8827E
The Space Management API was unable to locate global control
block. The error occurred in function : function-name
ANS8828E
The Space Management API lost the session with the server. This
problem is caused by a connection failure with the server. Check
to see if your Space Management Client machine has a network connection to
the TSM server.
ANS8829E
The Space Management API was unable to initialize the HSM
system. The error is caused from a problem to initialize a
DMAPI session.
ANS8830W
Different server name stanzas (HSM-stanza and BA-stanza)
for file-system-name file system for space management
and backup-archive.
ANS8831E
The Space Management API could not find file system : function-name An
incorrect file system name was passed to the Space Management API.
Ensure that the file system that was selected in the file
system list is still valid. Refresh the file system view in
the Space Management Console by pressing F5 on your keyboard
or select 'Refresh` under the View menu.
ANS8832E
The Space Management API could not retrieve TSM policy
settings from the server.
ANS8833E
The Space Management API could not retrieve TSM policy
settings from the already loaded list.
ANS8834E
The Space Management API was unable to get file system information
for file system : filesystem-name.
ANS8835E
The Space Management API was unable to get file system status
for file system : filesystem-name. System
call to get file system status returned with error.
ANS8836E
An object creation error occurred in the Space Management
API The error occurred in function : function-name. The
problem is caused from a memory problem. Try to free memory on
the system where the Space Management agent is running. Or
restart the Space Management agent.
ANS8837E
The Space Management API was unable to get configuration
data from managed file system : filesystem-name. The
problem is caused from a error when reading dsmmigfs table entry.
ANS8838E
The Space Management API can not set HSM managed file system configuration
for file system : filesystem-name. The configuration
cannot be set because this file system is NOT HSM managed. Check to
see if the managed file system that was selected in the file system
list is still HSM managed. Refresh the file system view in
the Space Management Console by pressing F5 on your keyboard
or select 'Refresh` under the View menu.
ANS8839E
A wrong stub file size was passed to the Space Management
API for file system : filesystem-name. The
stub file size that was entered in the file system properties dialog
is not supported by this file system. Correct the stub file
size value in the file system properties dialog of the Space
Management Console.
ANS8840E
The maximum number of candidates that was specified for file
system : filesystem-name is out of range. The
maximum number of candidates value that was entered in the file system
properties dialog is out of range. Correct the maximum number
of candidates value in the file system properties dialog of
the Space Management Console.
ANS8841E
The server name that was specified for the file system : optfile-name is
not valid. Correct the server name value in the client node
properties dialog of the Space Management Console.
ANS8842E
The Space Management API was not able to modify system options
file : optfile-name because of insufficient
privilege. Use root user to change HSM managed file system
configuration.
ANS8843E
No correct include/exclude settings are found in system options
file : optfile-name. Correct the include/exclude
list in the system options file.
ANS8844E
A incorrect preferred node or server name was specified in
the HSM configuration for filesystem-name. Correct
the preferred node and server name value in the HSM configuration.
ANS8845E
A incorrect owner node or server name was specified in the
HSM configuration for filesystem-name. Correct
the owner node and server name value in the HSM configuration.
ANS8846E
The Space Management API was not able to update the HSM managed file
system : filesystem-name.
ANS8847E
The Space Management API was not able to obtain a lock on
SDR file for file system : filesystem-name.
ANS8848E
The Space Management API could not open file system status
file to retrieve managed file system statistics for : filesystem-name. Reason
could be insufficient permissions or that the file does not exist.
The managed file system statistics are not retrieved from the HSM
system.
ANS8849E
The Space Management API was not able to load HSM managed file
system statistics for : filesystem-name. Check
to see if the managed file system that was selected in the file system
list is still HSM managed. Refresh the file system view in
the Space Management Console by pressing F5 on your keyboard
or select 'Refresh` under the View menu.
ANS8850E
The Space Management API was not able to add HSM to file
system : filesystem-name. This error occurs
because selected file system is not mounted. You must mount
the file system before you can add HSM.
ANS8851E
The Space Management API was not able to add HSM to file
system : filesystem-name. This error occurs
because selected file system is not supported to add HSM.
ANS8852E
The Space Management API was not able to add HSM to file
system : filesystem-name. This error occurs
because selected file system is already HSM managed.
ANS8853E
The Space Management API was not able to add HSM to file
system : filesystem-name.
ANS8854E
The Space Management API was not able to remove HSM from file
system : filesystem-name. The error occurs
when the Space Management API tries to lock the SDR file and fails.
ANS8855E
The Space Management API was not able to start automatic migration
on the file system : filesystem-name.
ANS8856E
The Space Management API was not able to start reconciliation process
on the file system : filesystem-name.
ANS8857E
The Space Management API was not able to start scout process
on the file system : filesystem-name.
ANS8858E
The Space Management API was not able to migrate the
file : file-name. The error occurred in function
: function-name.
ANS8859E
The Space Management API was not able to recall the
file : file-name. The error occurred in function
: function-name.
ANS8939E
An unexpected error occurred trying to filter the directory
tree. rc=return-code
ANS8945E
An unexpected error occurred analyzing the directory tree. The
list of files matching your search criteria is not completed. rc=return-code
ANS9005W
program name: invalid 'parameter
name' value: value (must be in [minimum
value..maximum value]).
ANS9007W
program name: invalid 'parameter
name' value: value (must be in [minimum
value..maximum value]).
ANS9008W
Compression is enabled. Recall mode for file file-name cannot
be set to partial.
ANS9009E
program name: found invalid space management
configuration for 'filesystem'.
ANS9010E
program name: could not parse space management
configuration file 'configuration file' for filesystem.
ANS9011E
program name: could not write space management
configuration file 'configuration file' for filesystem.
ANS9012E
error-program: Command must be run by root
user.
ANS9016E
Cannot get space management migration status for path.
ANS9017W
error-program: Minimum number of recall daemons min-dsmrecalld cannot
be greater than maximum number of recall daemons max-dsmrecalld;
defaulting to minimum min-dsmrecalld and
maximum max-dsmrecalld.
ANS9020E
Could not establish a session with a TSM server or client
agent. The TSM return code is tsm-error;.
ANS9024E
Starting with this release all candidate processing is done internally
by the TSM monitor daemon. Thus -c is no longer a valid option
for dsmreconcile.
ANS9025E
The Data Protection for WebSphere plug-in
version and the backup-archive client version do not match. Please
upgrade your Data Protection for WebSphere plug-in.
ANS9028E
program name: could not acquire lock for filesystem.
ANS9029E
The WebSphere server
is running, but the server must be shut down for a restore operation.
Shut down the WebSphere server
and try the restore operation again.
ANS9030W
Cannot set conflicting attributes to file file-name.
ANS9057W
error-program: cannot get space information
for file-system: error.
ANS9059E
error-program: process cannot detach to become
a daemon.
ANS9060W
error-program: cannot get and increase limit
of open files.
ANS9062E
File 'filename' has changed during the backup.
ANS9063E
error-program: file system file-system is
out of inodes.
ANS9064E
error-program: Cannot fork a new process: error.
ANS9065E
File 'filename' or file 'filename2'
has been added or removed during the backup.
ANS9067W
error-program: error updating dsmmigfstab
file for file-system.
ANS9068I
program-name: dsmmigfstab file updated for
file system file-system.
ANS9069I
program-name: all file systems are reactivated
to previous states.
ANS9070I
program-name: space management is now deactivated
for all HSM file systems.
ANS9071W
program-name: error reactivating space management
for all HSM file systems.
ANS9072W
error-program: error deactivating space management
for all FSM file systems.
ANS9073W
program-name: error deactivating space management
for file system file-system.
ANS9074I
program-name: space management functions have
been locally deactivated for file system file-system.
ANS9075W
program-name: error reactivating space management
for file system file-system.
ANS9076I
program-name: space management functions have
been locally reactivated for file system file-system.
ANS9077I
program-name: removed space management from
file system file-system.
ANS9078W
Space management is not removed from file system file-system.
ANS9079W
program-name: no migrated files matching search
criteria found.
ANS9080E
program-name: not enough space in file system
or storage pool to recall all migrated files.
ANS9081W
program-name: orphaned stub file(s) detected
in file system file-system.
ANS9082W
program-name: error encountered while reconciling
file system file-system.
ANS9083W
program-name: cannot deactivate space management
on file system file-system.
ANS9084E
program-name: file-system is
not managed or not locally managed by space management.
ANS9085E
program-name: file system file-system is
not managed by space management.
ANS9086E
program-name: A DMAPI error occured adding
space management to file system file-system, It is
possible DMAPI is disabled on this file system. The system set the
error code: errno = errno-value
ANS9087I
Space management is successfully added to file system file-system.
ANS9088W
program-name: space management is already
active for file system filesystem.
ANS9089E
The group backup validation failed. One or more files were
added, removed, or changed during the backup.
ANS9090E
program-name: file-system is
not a valid file system name.
ANS9091E
The WebSphere backup
validation failed. One or more files were added, removed, or changed
during the backup.
ANS9092W
AES 128-bit Encryption is not being used.
ANS9093W
program-name: cannot update migration candidates
list file-name.
ANS9094W
program-name: no candidates found in file
system file-system.
ANS9098E
program-name: space management does not support
file system file-system.
ANS9099E
program-name: space management is not active
for file system file-system.
ANS9100E
Unable to open file 'filename' for output.
ANS9101E
Migrated files matching 'file-name' could
not be found.
ANS9117E
Virtual machine 'VM name' will not be backed
up because it contains at least one of the following unsupported special
characters special characters
ANS9151E
An unexpected program error was encountered . TSM function
name : function-name TSM function
: function-desc TSM return code : TSM-rc
TSM file : file-name (line-number)
ANS9152E
program-name: cannot deactivate space management
for whole system: error.
ANS9153E
program-name: cannot reactivate space management
for whole system: error.
ANS9154E
program-name: cannot deactivate space management
for file system file-system: error.
ANS9155E
program-name: cannot reactivate space management
for file system file-system: error.
ANS9159E
program-name: unable to create temporary file.
ANS9160E
program-name: cannot write to temporary file
or status filefile-spec: error.
ANS9161E
Invalid backupset file or device name entered.
ANS9162W
Object: 'dir-name' is skipped for recall:
It is a directory.
ANS9163W
program-name: Could not acquire the recall
daemon session id.
ANS9164W
program-name: Could not acquire the monitor
daemon session id.
ANS9165E
program-name cannot open directory directory-spec due
to the following error: error.
ANS9166I
A 'backup type' backup version backup date
'datetime' is not consistent with local
repository and has been deleted from the server (object name='filespace
namepath-namefile-name', ID = 'object-id:object-id').
ANS9167W
The client cache for adaptive subfile backup is corrupt and
cannot be used.
ANS9177W
All data events for remote recalls running on node: 'cluster
node ID', hostname: 'cluster node hostname' are
going to be aborted.
ANS9178E
program-name cannot open file file-spec due
to the following error: error.
ANS9179W
The operation completed successfully. However, some error
occurred on creation of the required vApps list.
ANS9180W
An entry in the password file could not be decrypted.
ANS9182W
Your customized client nodes list already contains this node. Would you like to update it?
ANS9183W
Removing Space Management from 'file-system'
file system means that all migrated data will be recalled
from TSM Server 'server-name' Make sure
that enough free space is present on this file system for the recalled
data. Do you want to remove Space Management from 'client-node'
now?
ANS9184E
program-name cannot allocate memory due to
the following error: error.
ANS9288W
File: file-name of logical size file-logical-size and
allocated size file-allocated-size is too small to
qualify for migration.
ANS9289W
Object: 'dir-name' is skipped for migration:
It is a directory.
ANS9290W
File: file-name is skipped for migration:
The file type is either unknown or unsupported.
ANS9291E
program-name: A conflicting space management
program is already running in the file-system file
system. Re-run this program later in this file system.
ANS9293E
TSM space management cannot access ERRORPROG error-program:error
ANS9294I
No files matching 'file-name' were found.
ANS9296W
Performing image backup of the entire volume for volume
name. The IMAGEGAPSIZE option and used block image backup is
not supported for non-JFS2 file systems on AIX.
ANS9297W
File file-name is skipped for migration: No
backup copy found.
ANS9298W
File file-name is skipped for migration: Backup
copy found is not current.
ANS9299I
Cannot get the number of migrated files for file system file-system.
ANS9300I
Migrated files found in file system file-system. Check
for any error encountered during recall.
ANS9301E
Full VM backup of Virtual Machine 'vmname'
failed with RC rc
ANS9302E
The Restore VM command does not support VMBACKUPTYPE=FILE
data. VM File level restore must be run from inside the virtual
machine or with the 'asnodename' option.
ANS9303E
Full VM restore of Virtual Machine 'vmname'
failed with RC rc
ANS9304E
VMware Converter tool not installed on system.
ANS9316T
File system 'file-system' undelete completed.
ANS9331W
VMware vCenter or ESX Server userid and password for VMC
Host <host> VMC Userid <userid>
could not be read from encrypted pwd file.
ANS9332E
VMware vCenter or ESX Server userid and password not set.
Use dsmc SET PASSWORD -type=VM 'vCenter hostname' 'userid' 'password'
to save encrypted password.
ANS9333E
Unable to re-create 'file-name' as a stub
file due to Unix-system-call() failure; errno: error;
reason: 'error-reason'.
ANS9334E
Wrong alias 'alias-name' received from the
server.
ANS9347W
Warning:'domain-keyword' specified on Domain
will be ignored when connecting to VMware ESX/ESXi host. Connect
to VMware vCenter to process this domain.
ANS9350E
Backup operation failed due to volume mixture. Please
refer to explanation section for additional information.
ANS9351E
Data was not available on server and was skipped.
ANS9352E
SAN or HOTADD was chosen as the transport for at least one
of the disks in the operation, but the SAN policy is not OnlineAll
for this datamover. SAN or HOTADD cannot be used unless the SAN policy
is OnlineAll.
ANS9354E
The node or owner name 'node' specified in
the SET ACCESS command exceeds the maximum allowed length (64).
ANS9355E
VMware vStorage VI Web Service API reported error message: vstor-api-msg
ANS9356E
A VMware vStorage API error was reported.
ANS9359W
program-name: file-system:
high threshold high-threshold exceeds recommended maximum max-threshold maximum
percentage.
ANS9360W
program-name: file-system:
configured low-threshold low threshold is below the
recommended minimum floor-percent low threshold.
ANS9361W
program-name: file-system:
the configured pre-mig premigration is greater than
the difference between the configured low-threshold low
threshold and the recommended-minimum size of the file system Min_size.
ANS9362W
program-name: file-system:
MAXFILES max-files is less than used inodes used
inodes in the file system. MAXFILES will be set to the minimum possible
value.
ANS9363W
program-name: file-system:
MAXFILES max-files is more than files total
available inodes in the file system. MAXFILES will be set to the maximum
possible value.
ANS9364E
Failure initializing virtual machine environment. Refer to
dsmerror.log for detailed error messages.
ANS9365E
VMware vStorage API error for virtual machine 'VM-name'.
TSM function name : function-name TSM file
: file-name (line-number)
API return code : TSM-rc API error message
: function-desc
ANS9368W
WARNING: VMware Host Userid <hostuserid>
read from pwd file different than VMCUSER option value <vmcuserid>.
Using VMCUSER option value.
ANS9369W
WARNING: VMware VirtualCenter or ESX Server User Password
for VMC Host <host> VMC Userid <userid>
set in options file.
ANS9370W
Use Preferences Editor or dsmc SET PASSWORD -type=VM 'VirtualCenter
hostname' 'userid' 'password' to save encrypted password.
ANS9371I
program-name: file-system:
The specified MAXFILES value is 0. The CFI size will be calculated
automatically now.
ANS9372E
Unable to create the virtual machine to be restored due to
an invalid host name, datacenter name, or datastore name.
ANS9373E
VMware vStorage API environment could not be found. Install
the VMware VDDK and copy VMware runtime libraries from the VDDK bin
directory to TSM baclient directory.
ANS9374E
VMware vStorage virtual storage driver service is not running
or could not be found. Make sure VMware 'vstor2-mntapi20-shared.sys'
service is installed and running. Install the VMware vStorage API
runtime files.
ANS9376E
The Backup VM command domain keyword 'domain-keyword'
was specified, but this domain does not contain any virtual machines.
This error can also occur if the value for the VMHOST parameter is
not specified as an IP address or as a fully qualified domain name.
ANS9377E
No virtual machine is specified on the string command
or the virtual machine domain list could not be processed.
ANS9378E
Unexpected error while fingeprinting the data
ANS9379E
Unexpected error while deduplicating the data
ANS9380E
The virtual machine that was specified on the string command
could not be found.
ANS9381I
The value set for vmlist option will be migrated
to the new domain option.
ANS9383E
Required files for VMware vStorage virtual machine backup
could not be found. Run the TSM install selecting the vmwaretools
feature or install the VMware VDDK.
ANS9384W
Unable to get VMware Changed Block Tracking(CBT) data for
virtual machine 'virtual machine name'. Full VM backup
continues, and includes both used and unused areas of the disk.
ANS9385W
Error returned from VMware vStorage API for virtual machine
'VM-name' in vSphere API function __ns2__QueryChangedDiskAreas.
RC=API return code, Detail message: API
message
ANS9386W
Changed block tracking is not supported for virtual machine
'virtual machine name'. A FULL backup of the disk will
be performed and will include both used and unused areas of the disk.
ANS9387W
An incremental backup for virtual machine 'virtual
machine name' is not possible because changed block information
cannot be obtained. A full VM backup is attempted instead.
ANS9388E
The management class 'management class name'
specified for the 'option name' option is invalid,
or does not have a backup copy group.
ANS9389W
The DEDUP backup attempt was unsuccessful for virtual machine
'virtual machine name'. Retry #retry attempt
number with DEDUP disabled.
ANS9390W
The DEDUP backup attempt was unsuccessful for virtual machine
'virtual machine name'. Retry #retry attempt
number with DEDUP still enabled.
ANS9391W
Linux guest OS with
EFI Boot enabled is not fully supported by TSM VMware backup. Manual
steps may be required following restore to enable the virtual machine
to power on correctly.
ANS9394W
No backupset file or device name entered.
ANS9395E
The filespace has been migrated to the incremental forever
model; MODE=FULL and MODE=INCR are not valid.
ANS9396W
Virtual machine 'VM' is not running. IBM Tivoli Storage Manager Application
Protection will not be used while backing up this VM.
ANS9397W
TSM application protection cannot protect this machine.
Virtual machine 'VM' does not have operating system
or applications supported by TSM application protection.
ANS9398E
IBM Tivoli Storage Manager application protection failed to initialize on
virtual machine 'VM'. See the error log for more details.
ANS9399W
program-name: lock file access error for operation value on
path value value with errno text value.
ANS9402E
program-name: Cannot notify process
name to recover HSM operations on a failing node.
ANS9404E
Error creating the specified Virtual Machine. See log files
for more information.
ANS9405I
program-name: The takeover of filesystem file
system started.
ANS9410W
VMware Tools are either not runnning or out-of-date on virtual
machine 'VM'. IBM Tivoli Storage Manager application protection cannot
be used.
ANS9411E
VSS provider registration failed. Command 'command'
failed with Windows RC=return
code
ANS9412E
program-name: Failover is disabled on the
local machine. Aborting failover ...
ANS9415E
Failed to copy 'source' to 'destination'
with VMware RC=rc on the virtual machine.
ANS9416E
Cannot create the directory 'source' on the
virtual machine with Windows RC=rc
ANS9417E
IBM Tivoli Storage Manager application protection could not freeze the VSS
writers on the virtual machine named 'VM'. See the TSM error
log for more details.
ANS9422I
program-name: The rollback of filesystem file
system started.
ANS9428E
program-name: The takeover of filesystem file
system failed to start.
ANS9431E
IBM Tivoli Storage Manager application protection failed to thaw VSS writers
on virtual machine 'VM'. See the TSM error log
for more details.
ANS9432W
IBM Tivoli Storage Manager application protection failed to truncate application
logs on virtual machine 'VM'.
ANS9433E
program-name: dm_send_msg failed with errno Errno.
ANS9443E
program-name: The operation cannot be executed
in a deactivated failover environment.
ANS9450W
program-name: No eligible filesystem for takeover.
ANS9451E
program-name: GPFS or
the SP switch is down locally. Aborting takeover activities ...
ANS9452E
program-name: The DMApi is not functional
locally. Aborting takeover activities ...
ANS9453E
program-name: Could not determine the GPFS storage pool id for file 'file-path'.
Reason: reason
ANS9457E
program-name: Could not determine the storage
pools of file system 'file-system'. Reason: reason
ANS9459E
Using the specified MAXCANDIDATES parameter would produce
an out-of-space condition in the parent filesystem of /etc/adsm/SpaceMan/candidatesPool.
Based on the current free space situation the maximum value
for the MAXCANDIDATES parameter is value.
ANS9462E
Failover functionality is not supported with this HSM release.
ANS9469E
Warning! Unable to write a complete migration candidate list
due to low space in the parent filesystem of name.
ANS9474E
program-name: Lost my session with errno:
errno . Trying to recover.
ANS9475W
IBM Tivoli Storage Manager application protection failed to cleanup after
a VSS backup on virtual machine VM.
ANS9476I
program-name: Recovered my DM session sid.
ANS9480E
program-name: The rollback of filesystem file
system failed to start.
ANS9487W
program-name: cannot query the right on session session for
file handle = filehandle token = token.
Reason : error
ANS9488E
Java Runtime Environment
(JRE) was not found. File VM does not exist.
ANS9489E
Java Runtime Environment
(JRE) was not found.
ANS9490E
Cannot find httpagent.jar in the TSM client installation
directory.
ANS9491E
The password credentials for virtual machine 'guest
VM name' could not be found. Use dsmc SET PASSWORD -type=VMGUEST
'VM guest name' 'userid' 'password' to save encrypted password.
ANS9493E
The credentials found for virtual machine 'guest
VM name' are incorrect. Verify the credentials and use dsmc SET
PASSWORD -type=VMGUEST 'VM guest name' 'userid' 'password' to update
the username and password.
ANS9494E
Command 'command' completed with RC=return
code on virtual machine 'guest VM name'.
ANS9495E
Failed to login to virtual machine 'guest VM name'
because the VMware Tools are not running in the guest machine. Verify
that the VMware tools are running and that no other program has access
or is making any changes to this VM.
ANS9496E
Unable to lock virtual machine VM for application
protection.
ANS9497W
Virtual machine 'VM' resides on an ESX Server
or vCenter that is not supported by TSM application protection. IBM Tivoli Storage Manager application
protection will not be used.
ANS9498W
A valid IBM Tivoli Storage Manager for Virtual Environments license file
(license-file) cannot be located. IBM Tivoli Storage Manager application
protection will not be used.
ANS9499W
VMware tools on virtual machine 'VM' need
to be updated. IBM Tivoli Storage Manager application protection will not be used.
ANS9500W
program-name: cannot disposition the mount
event. Reason: error
ANS9501W
program-name: cannot set event disposition
on session session for file system mountdir token
= token. Reason : error
ANS9502W
program-name: cannot remove event disposition
on session session for file system mountdir token
= token. Reason : error
ANS9503I
program-name: events have been set and dispositioned
on session session for file system filesystem-name
ANS9504W
program-name: The file system filesystem-name is
not mounted or is mounted with wrong options.
ANS9505E
program-name: cannot initialize the DMAPI
interface. Reason: error
ANS9506E
program-name: The provided filespace argument
'argument' has an invalid format.
ANS9507E
program-name: cannot request the right on
session session for file handle filehandle token
= token. Reason : error
ANS9508W
program-name: cannot release the right on
session session for file handle = filehandle token
= token. Reason : error
ANS9509W
program-name: received an unexpected event
of type event-type on session session.
ANS9510E
program-name: cannot get event messages from
session session, expected max message-length = msglen,
returned message-length = return-length. Reason : error
ANS9511E
program-name: cannot read DM attributes on
session session for file: name = name handle
= handle token = token. Reason
: error
ANS9512E
program-name: cannot set DM attributes on
session session for file handle = filehandle token
= token. Reason : error
ANS9513E
program-name: cannot remove DM attributes
on session session for file handle = filehandle token
= token. Reason : error
ANS9514E
program-name: cannot create a file handle
from path. Reason: error
ANS9515E
program-name: cannot set the migration information.
Reason: error
ANS9516E
program-name: cannot create an user event
message on session session. Reason: error
ANS9518E
program-name: cannot respond to an event message
on session session using token token Reason
: error
ANS9519W
program-name: cannot set eventlist for a file
system on session session token = token fs-handle
= fs-handle. Reason : error
ANS9520E
program-name: cannot set a managed region
on session session for file handle = filehandle token
= token. Reason : error
ANS9521E
program-name: cannot get the file attributes
on session session for file handle = handle token
= token. Reason : error
ANS9522E
program-name: can not create a file system
handle from path. Reason: error
ANS9523E
program-name: is unable to verify the stub
size for the file on session session file handle
= filehandle token = token. Reason : error
ANS9524W
program-name: adjusted stubsize to an allowed
value on session session file handle = filehandle token
= token old stubsize = old-size new
stubsize = new-size
ANS9525E
program-name: is unable to create a stub file
on session session for file handle = handle token
= token. Reason : error
ANS9526E
program-name: cannot open the state file filename for
writing. Reason: error
ANS9527E
program-name: cannot write to the state file filename.
Reason: error
ANS9528W
program-name: cannot read from the state file filename. .
The file is corrupted and will be recreated.
ANS9529W
program-name: cannot obtain the handle of
a file system state file
ANS9530W
program-name: cannot remove an entry for file-system from
the global state file.
ANS9531E
program-name: cannot create a DM session:
old session = oldsession session info = session-info.
Reason : error
ANS9532W
program-name: cannot destroy the session session.
Reason: error
ANS9533W
program-name: failed getting all sessions.
Reason: error
ANS9534W
program-name: cannot query a session. Reason: error
ANS9535E
program-name: a file handle could not be created
from the file descriptor file-descriptor. Reason: error
ANS9536E
program-name: cannot query an event message
on session session. Reason: error
ANS9537E
program-name: Invalid storage pool 'storagepool'
for file system 'filesystem'.
ANS9538W
program-name: request request for
DM file attributes not recognized
ANS9539E
program-name: cannot create a file system
handle from the file handle = filehandle. Reason
: error
ANS9542E
program-name: the file attributes could not
be set on session session for file handle = filehandle token
= token flag = flag Reason : error
ANS9543W
program-name: The TSM client needs blocks-num1 free
file system blocks to be able to handle the nospace condition on file
system filesystem-name, errno: error-num,
reason: error-str. Currently blocks-num2 blocks
with a block size of block-size bytes are available.
ANS9545E
program-name: cannot get a lock for lockdirlockfile to
continue processing.
ANS9546E
IBM Tivoli Storage Manager cannot perform instant restore because Microsoft Active Directory
Domain Controller was detected on virtual machine.
ANS9613E
program-name: Stub size of stubsize bytes
is not supported on filesystem.
ANS9616E
program-name: cannot get migration information
for migrated-file-alias on file-system-name
ANS9645W
The vApps backup operation completed. However, one or more
vApp backups failed.
ANS9669W
program-name: file-system CFI
is out of range.
ANS9674W
One or more of the required vApps could not be retreived.
ANS9733E
File: File-name excluded by the Include/Exclude
list
ANS9778E
Error(s) were detected in options file: ''
Do you want TSM to comment out the line with errors and continue?
ANS9779E
Unable to open options file '' for writing.
ANS9782S
The selected backupset was generated by a newer version of
the backup server, and the new backupset version is not supported
by this client; The backupset data cannot be restored by this version
of the client.
ANS9849W
Local backupset cannot be expanded; Only full backupset restore
is supported locally.
ANS9850E
Tape read error; Max Blocksize is blocksize.
Attempted to read blocksize blocksize. Run dsmmaxsg
to update scsi driver max blocksize allowed and retry operation.
ANS9857W
The restored HSM for Windows stub
file may be an orphan: stub file name
ANS9890W
program-name: The file system filesystem is
already owned by that node.
ANS9892E
Unable to find snapshot(s) in the local repository.
ANS9895W
Space management in file system file system is
not active.
ANS9916I
VMCUSER does not have one or more required vSphere privileges
to create/update/cancel Tasks in vSphere related to this operation.
The operation will continue.
ANS9918E
Cannot open migration candidates list for file-system.
ANS9919E
Failed to find the expected control files for vm
name.