IBM Tivoli Storage FlashCopy Manager

Version 4.1.1

Messages


IBM Tivoli Storage FlashCopy Manager
Version 4.1.1

Messages


 Note:
Before using this information and the product it supports, read the information in “Notices” on page 581.

Second edition (September 2014)

This edition applies to version 4, release 1, modification 1 of IBM Tivoli Storage FlashCopy Manager (product
numbers 5641-A06, 5724-X94, 5608-ACB) and to all subsequent releases and modifications until otherwise indicated
in new editions.
© Copyright IBM Corporation 1995, 2014.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v Privacy policy considerations . . . . . . . . 583

About this publication . . . . . . . . vii Glossary . . . . . . . . . . . . . 585

Who should read this publication . . . . . . . vii
Publications . . . . . . . . . . . . . . vii

Chapter 1. Introduction to Tivoli Storage

FlashCopy Manager messages . . . . . 1
Tivoli Storage FlashCopy Manager message format . 1
Tivoli Storage FlashCopy Manager messages prefixes 2

Chapter 2. FMM messages . . . . . . . 3

FMM common messages . . . . . . . . . . 3
FMM messages for Microsoft Management Console 174
FMM messages for IBM XIV storage systems . . . 175

Chapter 3. FMF messages . . . . . . 181

Chapter 4. FMX messages . . . . . . 195

Chapter 5. FMY messages . . . . . . 223

Chapter 6. FMV messages . . . . . . 251

Appendix. Accessibility features for

the Tivoli Storage Manager product
family. . . . . . . . . . . . . . . 579

Notices . . . . . . . . . . . . . . 581
Trademarks . . . . . . . . . . . . . . 583

© Copyright IBM Corp. 1995, 2014 iii

iv IBM Tivoli Storage FlashCopy Manager: Messages
Tables
1. Messages prefixes by component . . . . . . 2

© Copyright IBM Corp. 1995, 2014 v

vi IBM Tivoli Storage FlashCopy Manager: Messages
About this publication
IBM® Tivoli® Storage FlashCopy® Manager provides the tools and information that
is required to create and manage volume-level snapshots on snapshot-oriented
storage systems while the applications that contain data on those volumes remain
online. Optionally, backups can be sent to Tivoli Storage Manager storage.

This publication contains explanations and suggested actions for messages that are
issued by all Tivoli Storage FlashCopy Manager components:
v Tivoli Storage FlashCopy Manager for UNIX and Linux
v Tivoli Storage FlashCopy Manager for VMware
v Tivoli Storage FlashCopy Manager for Windows
– Microsoft Management Console (MMC) Snap-in and Base System Services
– Volume Shadow Copy Service (VSS) Requester
v Tivoli Storage FlashCopy Manager for Microsoft Exchange Server
v Tivoli Storage FlashCopy Manager for Microsoft SQL Server

Who should read this publication

The target audience for this publication is system administrators who service IBM
Tivoli Storage FlashCopy Manager components. In this publication, it is assumed
that you have a working knowledge of Tivoli Storage FlashCopy Manager.

Publications
The Tivoli Storage Manager product family includes IBM Tivoli Storage FlashCopy
Manager, IBM Tivoli Storage Manager for Space Management, IBM Tivoli Storage
Manager for Databases, and several other storage management products from IBM
Tivoli.

To view IBM product documentation, see http://www.ibm.com/support/

knowledgecenter/.

© Copyright IBM Corp. 1995, 2014 vii

viii IBM Tivoli Storage FlashCopy Manager: Messages
Chapter 1. Introduction to Tivoli Storage FlashCopy Manager
messages
IBM Tivoli Storage FlashCopy Manager components issue messages with prefix
FMM, FMF, FMX, FMY, and FMV. The messages are listed and the format of the
messages is described.

Tivoli Storage FlashCopy Manager message format

Messages consist of the following elements:
v A three-letter prefix.
v A numeric message identifier.
v A one-letter severity code, also called the message type.
v Message text that is displayed on screen and written to message logs.
v Explanation, System Action, and User Response texts. These texts elaborate on
the message text, and are accessible only in documentation.

The image presents a typical message. The callouts on the right of the image
identify each element of the message.
Message Prefix
Message Number
Message Type*

FMM 50004 E
Unable To Obtain RSS Feed. Message Text

Explanation: An attempt to read an RSS feed Explanation

was made but could not be established.

System Action: Processing will continue. System Action

User Response: Ensure that there is an User Response

internet connection.

I = Information
* E = Error
S = Severe Error
W= Warning
The severity codes give an indication of the severity of the issue that generated the
message. The severity codes and their meanings are as follows:

Code Severity Meaning

S Severe The product or a product function cannot continue. User
response is required.
E Error An error is encountered during processing. Processing might
stop. User response might be required.

© Copyright IBM Corp. 1995, 2014 1

 Code Severity Meaning
W Warning Processing continues, but problems might occur later as a result
of the warning.
I Information Processing continues. User response is not necessary.

Message variables in the message text appear in italics.

On Tivoli Storage FlashCopy Manager for UNIX and Linux systems and in Tivoli
Storage FlashCopy Manager for VMware environments, some logs append an extra
prefix to the message.

In the detailed log, messages are prefixed with a timestamp and a session ID. The
session ID can help you determine whether the message was produced from the
application or the device. It can help you distinguish different application and
device nodes. For DB2® DPF databases, the session ID can help you to determine
which DB2 node or which storage cluster was responsible for producing the
message.

The following example contains a prefix:

15:41:07 (626) FMM8300I tsmACSPartition() returned with code 18.

In the summary log, there is an extra prefix that indicates what operation caused
the request.

Here is an example of the prefix in the summary log:

DB 00:16:48 (92e) FMM1510I New connection received.

Tivoli Storage FlashCopy Manager messages prefixes

Messages have different prefixes to help you identify the component that issues the
message. The table identifies the prefix that is associated with each component.
Table 1. Messages prefixes by component
Prefix Component
FMM Common to several components:
v Tivoli Storage FlashCopy Manager for
UNIX and Linux
v Tivoli Storage FlashCopy Manager for
Windows Microsoft Management Console
(MMC) Snap-in and Base System Services
v Tivoli Storage FlashCopy Manager for
VMware
FMF Tivoli Storage FlashCopy Manager for
Windows Microsoft Management Console
(MMC) Snap-in and Base System Services
FMX Tivoli Storage FlashCopy Manager for
Microsoft Exchange Server
FMY Tivoli Storage FlashCopy Manager for
Microsoft SQL Server
FMV Tivoli Storage FlashCopy Manager Volume
Shadow Copy Service (VSS) Requester

2 IBM Tivoli Storage FlashCopy Manager: Messages

Chapter 2. FMM messages
Messages with prefix FMM are issued by the following IBM Tivoli Storage
FlashCopy Manager components:
v Tivoli Storage FlashCopy Manager for UNIX and Linux
v Tivoli Storage FlashCopy Manager for Windows Microsoft Management Console
(MMC) Snap-in and Base System Services
v Tivoli Storage FlashCopy Manager for VMware

Messages with prefix FMM are also issued by the command-line interface (VMCLI)
of IBM Tivoli Storage Manager for Virtual Environments, Data Protection for
VMware.

FMM common messages

FMM messages in the range 0000-9999 are common messages. Common messages
are issued by the following IBM Tivoli Storage FlashCopy Manager components:
v Tivoli Storage FlashCopy Manager for UNIX and Linux
v Tivoli Storage FlashCopy Manager for VMware

Tivoli Storage FlashCopy Manager V4.1.1 common messages are listed in

ascending numeric order. The complete message is documented, including message
ID, message text, explanation, system action, and user response.

Please use 'file' or 'file_online'.

FMM0001E Profile not specified.
Explanation: Data Protection for SAP expects as the
Explanation: Cannot locate the profile.
backup type parameter only file or file_online.
System action:
System action:
User response: Ensure that a profile is available.
User response: If you start Data Protection for SAP
(Oracle) Note that the BACKINT call must have the
manually to do a backup, ensure that the type option
following form: backint –p init<SID>.utl .
(–t) receives the correct arguments (file or file_online).
If your Data Protection for SAP has been invoked by
FMM0004E Function not defined. [ function ] one of the SAP database utilities (for example,
**BRBACKUP**), ensure that the SAP backup profile
Explanation: BRTOOLS, BRBACKUP, or BRARCHIVE
init<SID>.sap is customized correctly.
passed an invalid argument to Data Protection for SAP.
System action:
FMM0007E Mode mode requires the environment
User response: Ensure that you have the correct variable environment variables to be set.
version of BR*Tools installed. Valid functions are: –f
Explanation: Not all environment variables required
backup or –f restore or –f password or –f delete or –f
have been set. At least environment variables are missing.
inquire.
System action:
FMM0005I Start of program at: time. User response: Set the missing environment variables.
Explanation: The operation started at the time
denoted. FMM0008E The environment variable name is not
set correctly. The current value is "value".
System action:
Explanation: The value of the environment variable
User response: None.
name is wrong.
System action:
FMM0006E Type for backup not defined [ type ].

© Copyright IBM Corp. 1995, 2014 3

FMM0009E • FMM0048E

User response: Set name to an appropriate value.

FMM0023I Time: current time Done: saved bytes
(percent) of bytes. Estimated end time: end
FMM0009E The option 'option' must be specified time.
after the '–t FAKE' option. This is true
Explanation: Finished saving a specific object at
for all fake relevant options.
current time. The saved bytes amount of the total number
Explanation: The attempt by the Administration of bytes have been saved. percent shows the percentage.
Assistant to start a backup or restore simulation failed. This call will be completed at the estimated end time.

System action: Processing ends. System action:

User response: Contact IBM support. User response: None.

FMM0010E The option 'option' contains an invalid FMM0024I Return code is: return code.
argument
Explanation: Finished saving a specific object at
Explanation: The attempt by the Administration current_time. The saved_bytes amount of the total
Assistant to start a backup or restore simulation failed. number of bytes have been saved. percent shows the
percentage. This call will be completed at the estimated
System action: Processing ends. end_time.
User response: Contact IBM support. System action:
User response: For return codes other than 0, check
FMM0011E Semantic errors were detected in the the run log for warnings or error messages.
fake definition: 'definition'
Explanation: The attempt by the Administration FMM0027I Time: current time Object: current number
Assistant to start a backup or restore simulation failed. of total number in process: file_name Size:
System action: Processing ends. size, MGMNT–CLASS: management class,
TSM–Server: server name .
User response: Contact IBM support.
Explanation: Data Protection for SAP started saving
current number files at current time. The total number of
FMM0012I command: 'command' files to save is total number. The file file name is
Explanation: A backup or restore simulation was currently being processed. The files are transferred to
started by the Administration Assistant. The command the Tivoli Storage Manager server server name, which
line options are shown in the message. stores them in the management class management class.

System action: Processing continues. System action:

User response: None. User response: None.

FMM0020I End of program at: time. FMM0032E Error opening file file name: system error
description
Explanation: The operation ended at the time
denoted. Explanation: A system error occurred during opening
of the file file name. system error description describes the
System action: error in more detail.
User response: None. System action:
User response: Read the system error description.
FMM0021I Elapsed time: elapsed time.
Explanation: The time needed for the complete FMM0048E No password for node node name on
operation was elapsed time. server server name given on command
System action: line. When entering passwords in batch
mode, you must supply values for all
User response: None. stanzas in the profile.
Explanation: The batch mode of the password
function requires a data set for all Tivoli Storage
Manager server stanzas in the profile.
System action:

4 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0049I • FMM0059E

User response: Check the profile for active server

FMM0054I Time: current time Object: current num of
stanzas. Use that information and try it again.
total num complete: file name with: bytes
restored with description object
FMM0049I Enter the password for node node name description .
on server server name:
Explanation: Data Protection for SAP completed
Explanation: The password for the node node name on restoring of current num file at current time. The total
the Tivoli Storage Manager server server name has to be number of files to be restored is total num. The file file
entered for storing it in the DP for SAP configuration name with the size bytes is restored with the description
file. object description.

System action: System action:

User response: Enter the password for the User response: None.
corresponding Tivoli Storage Manager server.
FMM0055I Object object name with size saved with
FMM0050I Enter password for node node name on description description.
server server name again:
Explanation: The object object name was saved
Explanation: In order to avoid typing errors, you have successfully.
to enter the password twice.
System action:
System action:
User response: None.
User response: Enter the password again.
FMM0056I Object object name with size restored with
FMM0051I Password successfully verified for node description description.
node name on server server name.
Explanation: The object object name was restored
Explanation: The password for the node node name on successfully.
the Tivoli Storage Manager server server name was
System action:
changed successfully.
User response: None.
System action:
User response: None.
FMM0057I Time: current time Object: object name
with: size saved with description
FMM0052E Password verification for node node name description.
on server server name failed.
Explanation: The object object name was saved
Explanation: The password you entered for the node successfully.
node name on the Tivoli Storage Manager server server
System action:
name was wrong.
User response: None.
System action:
User response: Enter the password again. If this error
FMM0058I Time: current time Object: object name
still exists, contact your Tivoli Storage Manager
with: size restored with description
administrator.
description.
Explanation: The object object name was restored
FMM0053I Time: current time Object: current number
successfully.
of total number complete: file name with:
bytes saved with description object System action:
description.
User response: None.
Explanation: Data Protection for SAP completed
saving current number file at current time. The total
FMM0059E Data Protection for SAP cannot find the
number of files to be saved is total number. The file file
client options file.
_name with the size bytes is saved with the description
object description. Explanation: Data Protection for SAP requires a client
options file (<server>.opt) for each Tivoli Storage
System action:
Manager server. The client options files must reside in
User response: None. the same directory. This directory must also contain a
client options file 'dsm.opt'. The environment variable

Chapter 2. FMM messages 5

FMM0060E • FMM0105I

DSMI_CONFIG must specify this directory.

FMM0065E The argument is missing for option
System action: 'option'.

User response: Set the environment variable Explanation: Every option requires an argument.
DSMI_DIR to the Tivoli Storage Manager API
System action:
installation path. Set the environment variable
DSMI_CONFIG to the path of the client options files. User response: Check the command syntax and
reenter the command.
FMM0060E The command parameter parameter is not
recognized. FMM0101I Enter 'cont' to continue or 'stop' to cancel.
Explanation: The command parameter parameter is not Explanation: If Data Protection for SAP is running in
recognized. unattended mode (profile keyword BATCH), it
terminates the current run if operator intervention is
System action:
required.
User response: Check the command syntax and
System action:
reenter the command.
User response: Enter 'cont' or 'stop'.
FMM0061W The output file file name is not valid.
FMM0102I Your reply: 'reply'.
Explanation: The specified output file file name could
not be created. Explanation: The reply you made is confirmed.
System action: System action:
User response: Check that file name is a valid file User response: None.
name on your operating system. Also check that the
application has the appropriate permissions to create
FMM0104I Deleting the data container 'dcid' from
the file within the specified directory. The directory
the backup 'snapid' in the repository.
must already exist. If the file already exists, rename the
IBM Tivoli Storage FlashCopy Manager
old one.
found that the volumes of this data
container do not contain a valid
FMM0062E The input file filename is not valid. snapshot in the storage system.
Explanation: Unable to read the input file file name Explanation:
correctly.
System action:
System action:
User response: None.
User response: Check the path and name of the input
file and the appropriate file access permission.
FMM0105I If the newest FlashCopy targets of the
mirror copy sources are space efficient
FMM0063E The UTL file file name is not valid. volumes, then they will grow up to the
size of the sources.
Explanation: Unable to read the input file file name
correctly. Explanation: Be aware that the AIX® LVM mirror
synchronization will change all the tracks of the mirror
System action:
copy.
User response: Check the path and name of the
System action: Processing continues.
profile (UTL file) and the appropriate file access
permission. User response: If you are using space efficient target
volumes for the mirror copy to be synchronized, then
verify the FlashCopy backups and provide enough
FMM0064E The option 'option' is not recognized.
storage for the growth. You can also evaluate to delete
Explanation: The option is not recognized. those backups. If multiple target sets are used, then all
the other in the chain have to be deleted as well.
System action:
User response: Check the command syntax and
reenter the command.

6 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0106I • FMM0138I

there are no longer any more dependencies on this

FMM0106I The newest snapshot of the mirror copy
backup.
will grow up to the size of the sources.
Explanation: Be aware that the AIX LVM mirror
FMM128E The 'disk names' virtual disk(s) of the
synchronization will change all the tracks of the mirror
virtual machine 'VM name' have a disk
copy.
type which is not supported by IBM
System action: Processing continues. Tivoli Storage FlashCopy Manager. The
virtual machine is not included in the
User response: Verify the snapshot backups and
backup.
provide enough storage for the growth. You can also
evaluate to delete those backups. Explanation: The specified virtual disks of the
specified virtual machine have a type which is not
supported by IBM Tivoli Storage FlashCopy Manager.
FMM0122I Backup ID: backup identifier
The specified virtual machine will not be included in
Explanation: The backup identifier uniquely identifies the backup and not be restorable.
the backup that has been created.
System action: Processing continues.
System action: Processing continues.
User response: Change the disk type to a type that is
User response: None. supported by IBM Tivoli Storage FlashCopy Manager.
Please refer to the User's manual or the Pre-Installation
checklist for details.
FMM0123E Option -i <backup_list> not specified.
Explanation: The function –f getresources requires the FMM129E The following error was returned by the
specification of the option –i <backup_list> too. VSphere API: 'vSphere error'.
System action: Explanation: The VSphere API issued the specified
User response: Ensure that you transfer the list of the error.
files to back up when you call the function –f System action: Processing ends.
getresources. Note that in this case the splitint call must
have the following form: <path>/splitint –p User response: Try to interpret the vSphere error
<path>/init<SID>.fcs –f getresources –i <backup_list>... message and to fix the cause of the issue.

FMM124E The LUN 'LUN name' on the datastore FMM0136I Start of the reconciliation between the
'datastorename' is not part of a storage IBM Tivoli Storage FlashCopy Manager
subsystem supported by IBM Tivoli repository and the storage system.
Storage FlashCopy Manager.
Explanation: IBM Tivoli Storage FlashCopy Manager
Explanation: IBM Tivoli Storage FlashCopy Manager is checking the validity of the backups listed in the
cannot backup the specified datastore because it repository in the storage system.
contains at least one LUN of a storage subsystem
System action:
which is not supported.
User response: None.
System action: Processing ends.
User response: At least one LUN of the specified
FMM0137I End of the reconciliation.
datastore is not part of a storage subsystem that is
supported by IBM Tivoli Storage FlashCopy Manager. Explanation: IBM Tivoli Storage FlashCopy Manager
Remove the LUN from the datastore. is finished checking the validity of the backups listed in
the repository in the storage system.
FMM0127E The backup corresponding to this System action:
consistency group cg cannot be deleted
User response: None.
as it is not the oldest in the cascade of
dependent flashcopy maps.
FMM0138I Time stamp: current_time.
Explanation: The specified backup is not the oldest in
a cascade of flashcopy maps and cannot be deleted as it Explanation: IBM Tivoli Storage FlashCopy Manager
has dependencies with the remaining maps in the performs several tasks in sequence (for example,
cascade. initiate the FlashCopy of source volumes on the
production system and mount file systems on the
System action: Process stops.
backup system). Tracking the various time stamps
User response: This operation can be retried when allows analysis of how long each task took.

Chapter 2. FMM messages 7

FMM0142I • FMM0151E

System action: Tivoli Storage Manager server caused Tivoli Storage

Manager for ERP to fail when running a backup.
User response: None.
Action: Depending on the error message, eliminate the
reason for not getting a successful backup to the Tivoli
FMM0142I Snapshot started ... Storage Manager server.

Explanation: The command with the 'flashcopy'

function has been issued on the production system, and FMM0147I The IDS control file exists and a new
the program splitint waits until this action has finished. backup cycle entry has been created.

System action: Explanation: At the start of the function –f

getresources, IBM Tivoli Storage FlashCopy Manager
User response: None. inserts a record in the IDS control file for the new
backup cycle. This record is updated as the status of
FMM0143I Snapshot successful. the new backup cycle changes (such as FlashCopy
target volumes/file systems being mounted or
Explanation: The command for the snapshot–based unmounted).
copy of the volume pairs has completed successfully on
the production system. System action:

System action: User response: None.

User response: None.

FMM0148E The backup ID was not passed by DP
for mySAP. This snapshot backup
FMM0144W Information from DP for mySAP was cannot be used for snapshot restore.
not found.
Explanation: Before this error, the warning IDS1041W
Explanation: The exchange data between IBM Tivoli is displayed. The backup ID is mandatory for using a
Storage FlashCopy Manager and Tivoli Storage snapshot backup for the restore.
Manager for ERP was not found. The information is
exchanged through the call of the IBM Tivoli Storage System action:
FlashCopy Manager's function ?set_bki_info? by User response: To use snapshot restore, ensure that
backint before the Tivoli Storage Manager backup. For you have installed DP for SAP (backint) version 3.3.10
older versions, the information is first exchanged after or higher.
the Tivoli Storage Manager backup during the
execution of the unmount function. Either the Tivoli
Storage Manager for ERP you have installed does not FMM0149E The IDS control file is corrupt!
support IBM Tivoli Storage FlashCopy Manager, or
Explanation:
Tivoli Storage Manager for ERP has failed after a
successful FlashCopy and mount. System action:
System action: User response:
User response: Check the run logs of tsm4acs. This
error could have various reasons and should be FMM0150I The IDS control file 'ids_control_file' does
resolved depending on the specific situation: Case 1: not exist, it will be created.
tsm4acs has finished successfully. Result: The backup
Explanation: IBM Tivoli Storage FlashCopy Manager
on disk (FlashCopy target volumes) as well as the one
writes the first record to the IDS control file specified in
done to the Tivoli Storage Manager server are valid.
the entry IDS_CONTROL_FILE of the profile.
However, IBM Tivoli Storage FlashCopy Manager
cannot show the backup ID in its report when using System action:
the function 'inquire'. Reason for warning: It is very
likely that Tivoli Storage Manager for ERP (AIX User response: None.
version) does not have IBM Tivoli Storage FlashCopy
Manager support (prior to version 3.1.0.3). Action: FMM0151E The IDS control file has no entry.
Install the appropriate Tivoli Storage Manager for ERP
version. Case 2: tsm4acs has terminated abnormally. Explanation: IBM Tivoli Storage FlashCopy Manager
Result: Carefully check the run log of tsm4acs for any has found the IDS control file, but it has no records.
FMM, ANS or ANR error messages. Most likely, the This error occurs when you start one of the functions
backup on disk (FlashCopy target volumes) is valid inquire, withdraw or unmount before you have run the
(check with splitint –f inquire whether PSI is 'flashcopy' function for the first time.
PSI_MOUNT_DONE or PSI_UNMOUNT_DONE), but System action:
the backup to the Tivoli Storage Manager server is
invalid. Cause: Problems with the network or on the User response: The problem is resolved after you run

8 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0152E • FMM0160I

at least one tsm4acs with a successful FlashCopy.

FMM0156I Delete backup cycle with BSEQ_N =
beseq_n and all the associated files ...
FMM0152E The IDS control file must be read or
Explanation: The program deletes the oldest record
inserted before update.
with the backup sequence number <bseq_n> because
Explanation: IBM Tivoli Storage FlashCopy Manager the maximum number of records has been reached. In
has detected a logical error when processing the IDS addition, the oldest reports and traces associated with
control file. that backup cycle are deleted.

System action: System action:

User response: Contact Tivoli Storage Manager for User response: None.
ERP support.
FMM0157W Directory Path 'directory' for the report
FMM0153W The value of the field 'field_name' in the files does not exist. Using the current
file 'file_name' is empty. directory.

Explanation: The program tsm4acs updates the IDS Explanation: The directory entry of the parameter
repository after the Tivoli Storage Manager backup but LOG_TRACE_DIR in the profile could not be found.
also in case of a disk–only backup. A temporary file is The current directory is used for the log and trace files.
created with the following format: >>> backint_data
System action:
BID <backup id> UTL <name of the application profile
used> INF <DPF backup ID> EBC <log directory> EBB User response: To avoid directories cluttered with
<backup type> EBR <first active log> <<< backint_data reports and traces, the parameter LOG_TRACE_DIR
>>> input_file <file list> <<< input_file If one of the should be used, or the directory it specifies must be
fields of the topic ?backint_data? is empty (that is, created if necessary.
missing), this message is displayed. If the backup ID is
empty, the process terminates with error IDS1036E.
FMM0158I Start of listing of importing volume
System action: groups/mounting file systems ...
User response: None. Explanation: After initiating the FlashCopy
source/target volumes on the production system, IBM
Tivoli Storage FlashCopy Manager makes the
FMM0154W Info data from DP for mySAP
corresponding target volumes available to the backup
/tmp/bki<SID>.ids cannot be read.
host. A list of mount points or volume groups is
Explanation: Before the unmount process, IBM Tivoli shown.
Storage FlashCopy Manager reads /tmp/bki<SID>.ids,
System action:
which contains information about the backup that was
done by Tivoli Storage Manager for ERP. Among the User response: None.
information read is: v Backup ID v Util file used for the
backup v A list of the files used for the backup v The
FMM0159I End of listing.
backup type This message is issued if Tivoli Storage
Manager for ERP terminated unsuccessfully for some Explanation: This message marks the end of the list of
reason. mount points or volume groups.
System action: System action:
User response: Ensure that Tivoli Storage Manager for User response: None.
ERP runs successfully.

FMM0160I The unmount process will be skipped

FMM0155I The maximum number of backup cycles because the progress status indicator
in the IDS control file has been reached. (PSI) has a value of 'psi'.
Explanation: The maximum number of backups Explanation: When the 'withdraw' function is started,
controlled via the parameter BACKUP_MAX will be the unmount process is performed only if the PSI has a
exceeded with the new inserted record. If the value of PSI_MOUNT_STARTED or
parameter is not set, the program uses the default PSI_MOUNT_DONE.
value of 30.
System action:
System action:
User response: The documentation shows the
User response: None. permissible functions depending on the backup
progress status indicator.

Chapter 2. FMM messages 9

FMM0162E • FMM0177E

User response:
FMM0162E The version of the splitint program
must be the same on the backup and
production system. FMM0167E The config file named 'config_file' could
not be opened. Please call 'splitint' with
Explanation: The version of IBM Tivoli Storage
the function 'password' to create this
FlashCopy Manager on the production system is
file.
different from the version on the backup system.
Explanation: IBM Tivoli Storage FlashCopy Manager
System action:
is unable to read the configuration file <config_file>.
User response: Ensure that you install the same
System action:
version of IBM Tivoli Storage FlashCopy Manager on
the production and backup systems. You obtain the User response: This error could have various reasons.
version number when you start splitint without Try the following: 1. Call splitint with the 'password'
parameters. function to create the file. 2. Check the path of the
configuration file. The path must be specified in the
profile (parameter CONFIG_FILE). 3. Make sure that
FMM0163I Enter the password for the user 'user ID'
the file access permissions are set correctly.
:
Explanation: The password for the user ID <user ID>
FMM0172I Start of listing of exported volume
has to be entered. It is encoded and stored in a file
groups/unmounting file systems ...
specified in the parameter CONFIG_FILE. Note that
this user ID and password must be the same on the Explanation: A list of unmount points or exported
production and backup systems. The IBM Tivoli disk groups is shown. Due to the use of the unmount
Storage FlashCopy Manager program splitint uses the function on the backup host, IBM Tivoli Storage
user ID to execute a remote shell on the production FlashCopy Manager unmounts the file systems and
system. export volume groups on the backup host that had
been imported or mounted when the IBM Tivoli
System action:
Storage FlashCopy Manager 'flashcopy' function was
User response: Enter the password for the executed.
corresponding user ID.
System action:
User response: None.
FMM0164I Enter the password for the user 'user ID'
again:
FMM0173I Start of withdraw of the target–source
Explanation: To avoid typing errors, you must enter
pairs ...
the password twice.
Explanation: The command with a withdraw has been
System action:
issued from the backup system to the primary Copy
User response: Enter the password again. Services server for the storage system.
System action:
FMM0165I The password entry does not match,
User response: None.
please try again.
Explanation: The two entered passwords are not
FMM0177E You cannot run the function 'function' if
identical. You must enter the password again.
the progress status indicator (PSI) has a
System action: value of 'psi'.
User response: Enter the password again. You are Explanation: The backup cycle was left in a state that
permitted three attempts before the program does not allow IBM Tivoli Storage FlashCopy Manager
terminates. to start the specified function.
System action:
FMM0166E No password stored.
User response: The documentation shows the
Explanation: The two entered passwords are not permissible functions depending on the backup
identical. You have tried three times, and the progress status indicator.
passwords were different in each case.
System action: You must start the splitint program
with the function -f password again. If no password is
stored, or it is invalid, splitint fails when the 'flashcopy'
function is used.

10 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0182E • FMM0190W

User response: Check for preceding errors. Check

FMM0182E The option –f flashback can only be
whether the backup to Tivoli Storage Manager ended
used on the production system.
successfully.
Explanation:
System action: FMM0187I Creating a semaphore for the critical
part of importing/exporting ...
User response:
Explanation: When multiple production systems run a
backup via a single backup system at the same time,
FMM0183E Topic named 'topicname' could not be
IBM Tivoli Storage FlashCopy Manager ensures that the
found in the file 'filename'.
critical parts of the code run for a single instance of the
Explanation: IBM Tivoli Storage FlashCopy Manager program at a time. These phases are: 1. When the
was able to read the file <filename> but the expected FlashCopy has been done and resources (volume
entry for the topic <topicname> was not found. groups and file systems) are being enabled 2. Before the
FlashCopy relationship is withdrawn and resources
System action: (volume groups and file systems) are being disabled.
User response: If the affected file is in the directory For this synchronization process, a semaphore with the
denoted by the parameter VOLUMES_DIR, check fixed key 0x88886666 is created
whether the topic name has the format: >>> System action:
volumes_set_# Where # is a placeholder for the volume
set number (1, 2, etc.) If the affected file is another file, User response: None.
you likely have another error prior to this one.
Otherwise, contact Tivoli Storage Manager for ERP
FMM0188I Trying to set the semaphore for the
support.
critical part of importing/exporting ...
Explanation: If the IBM Tivoli Storage FlashCopy
FMM0184E The source volume <serial number>
Manager semaphore is already allocated, the program
cannot be specified as a target volume
waits until it is released. Otherwise, the program sets it
in the .fct file.
and pass into the critical part of the run. Another
Explanation: IBM Tivoli Storage FlashCopy Manager instance arriving at this point now has to wait for the
found one of the source volumes in the list of target release of the semaphore.
volumes in the init<SID>.fct file.
System action:
System action:
User response: None.
User response: Ensure that the target volumes list in
init<SID>.fct does not contain any of the source
FMM0189I Semaphore released.
volumes.
Explanation: After the program has passed the critical
part of the run, the semaphore is released.
FMM0185E No target volumes were specified for
the set 'volumes_set_#' in the file System action:
'filename'.
User response: None.
Explanation: IBM Tivoli Storage FlashCopy Manager
has read file <filename> in the directory specified by
FMM0190W The semaphore could not be created.
VOLUMES_DIR. The format of the file is correct, but
System error sys_errno: sys_message
the list of target volumes is missing.
Explanation: If IBM Tivoli Storage FlashCopy
System action:
Manager could not create the semaphore, the system
User response: See the description of the target error number and message are issued as a warning.
volumes file in the documentation. The concurrent run of multiple production systems
with a single backup system will not work properly.
FMM0186E The backup ID (timestamp) is empty. System action:
This snapshot backup cannot be used
User response: Check the system error number and
for a snapshot restore.
message with the system administrator.
Explanation: Before this error, the warning IDS1041W
is displayed. The backup ID (timestamp) is mandatory
for using a FlashCopy backup for the restore. The
program tsm4acs was not able to generate a timestamp.
System action:

Chapter 2. FMM messages 11

FMM0191W • FMM203E

copies from the logical volumes v Remove the mirror

FMM0191W The semaphore could not be initialized.
physical volumes from the volume groups 3. Remove
System error sys_errno: sys_message
the volume group from the AIX ODM One or more of
Explanation: If IBM Tivoli Storage FlashCopy these operations have ended with errors. IBM Tivoli
Manager could not initialize the semaphore, the system Storage FlashCopy Manager issues a warning but the
error number and message are issued as a warning. snapshot restore continues.
The concurrent run of multiple production systems
System action:
with a single backup system will not work properly.
User response: None.
System action:
User response: Check the system error number and
FMM200E The following remote mirror
message with the system administrator.
relationships are not assigned to a
consistency group: 'list of rc relations'.
FMM0192W The semaphore could not be allocated.
Explanation: IBM Tivoli Storage FlashCopy Manager
System error sys_errno: sys_message
is configured to take the FlashCopy from the remote
Explanation: If IBM Tivoli Storage FlashCopy cluster. However the remote mirror relationships listed
Manager could not allocate the semaphore, the system in this message are not assigned to a consistency group.
error number and message are issued as a warning.
System action: The software process ends.
The concurrent run of multiple production systems
with a single backup system will not work properly. User response: Add the remote mirror relationships
identified in this message to the one unique consistency
System action:
group containing all the remote relationships.
User response: Check the system error number and
message with the system administrator.
FMM0201E The NLS catalog could not be loaded.
Make sure that the catalog
FMM0193W The semaphore could not be released. <fully_qualified_catalog_name> exists.
System error sys_errno: sys_message
Explanation: DP for Snapshot Devices uses an English
Explanation: If IBM Tivoli Storage FlashCopy NLS catalog for the LVM and storage–system parts of
Manager could not allocate the semaphore, the system the product. The installation process copies the catalog
error number and message are issued as a warning. to the displayed path.
The concurrent run of multiple production systems
System action:
with a single backup system will not work properly.
User response: Check for errors during the installation
System action:
procedure.
User response: Check the system error number and
message with the system administrator.
FMM0202E You cannot run the function 'function' if
the restore status indicator (RSI) on
FMM0196I This is your last chance to stop the target set 'id' has a value of 'RSI_START'.
Snapshot Restore. Enter 'c[ont]' to
Explanation: If the restore status RSI of the target set
continue, 's[top]' to cancel.
has a value of RSI_START, then a snapshot restore is
Explanation: IBM Tivoli Storage FlashCopy Manager still running in the background. You cannot start a
asks the user a last time before the program begins FlashCopy backup again until the background copy to
with the restore process. The original data is the database volume is finished. In this case the RSI
overwritten with the data of the snapshot backup. value is either RSI_DISKONLY or in case of LVM
mirroring RSI_DISKANDLVM.
System action:
System action:
User response: Be sure that you want to restore from
the FlashCopy backup. User response: Wait until the FlashCopy background
process is finished.
FMM0199W One or more errors were found
disabling the production system FMM203E The following Metro or Global Mirror
resources. target volumes are in different clusters:
'listOfVdisks'.
Explanation: Before the actual snapshot restore to the
database volume occurs, IBM Tivoli Storage FlashCopy Explanation: For a remote FlashCopy to be started,
Manager does the following: 1. Unmounts the database IBM Tivoli Storage FlashCopy Manager software
file systems 2. For LVM mirroring: v Remove the mirror requires the Metro Mirror or Global Mirror target

12 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM204E • FMM0212I

volumes to be in the same SVC cluster.

FMM208E The state 'cgstate' of the Metro Mirror
System action: The software process ends. consistency group 'cgname' is not valid
for a consistent FlashCopy backup.
User response: Move the Metro Mirror or Global
Mirror target volumes identified in this message to a Explanation: For a remote FlashCopy to be started,
unique target SVC cluster. IBM Tivoli Storage FlashCopy Manager software
requires the Metro Mirror consistency group to be in a
consistent synchronized state.
FMM204E Parameter TAKEOVER_HOST_NAME is
required in the storage section of the System action: The software process ends.
profile for a restore into the takeover
User response: The consistency group that contains
host.
the Metro Mirror relationships, between the source and
Explanation: For a remote restore on the takeover host target volumes, should be started before the FlashCopy
to be started, IBM Tivoli Storage FlashCopy Manager backup begins. In addition, the Metro Mirror
software requires the parameter consistency group should be in a consistent
TAKEOVER_HOST_NAME to be specified in the synchronized state.
section DEVICE_CLASS of the profile.
System action: The software process ends. FMM210W The following Global Mirror
consistency group is still copying:
User response: Specify the parameter 'cgname'.
TAKEOVER_HOST_NAME in the section
DEVICE_CLASS for remote FlashCopy backups using Explanation: For a remote FlashCopy to be started,
the same value as defined in the storage systems. IBM Tivoli Storage FlashCopy Manager software
requires the Global Mirror consistency group to be in a
consistent synchronized state.
FMM0205I The database is now ready for Snapshot.
System action: The software process continues.
Explanation:
User response: The consistency group that contains
System action: the Global Mirror relationships, between the source and
User response: target volumes, should be started before the FlashCopy
backup begins. In addition, the Global Mirror
consistency group should be in a consistent
FMM206E The source volumes are in multiple synchronized state.
remote consistency groups.
Explanation: The remote FlashCopy cannot start when FMM211I Waiting 'resttime' seconds, but not
the source and target volumes are in multiple remote exceeding the value TIMEOUT_FLASH
consistency groups. of 'timeout' seconds ...
System action: The software process ends without Explanation: For a remote FlashCopy to be started,
starting the remote FlashCopy. IBM Tivoli Storage FlashCopy Manager software
User response: Change the relationship between the requires the Global Mirror consistency group to be in a
source and target volumes. For the remote FlashCopy consistent synchronized state. When the consistency
to start, the source and target volumes must be in the group is still copying, IBM Tivoli Storage FlashCopy
same remote consistency group. Manager runs maximal the time specified by the
parameter TIMEOUT_FLASH to wait until the
consistency group becomes the state 'consistent
FMM207E The following source volumes are either synchronized'.
not in a remote mirror relationship or
not the master volume: 'list of volumes'. System action: None.

Explanation: IBM Tivoli Storage FlashCopy Manager User response: None.

is configured to take the FlashCopy from the remote
cluster. However the volumes listed in this message are FMM0212I New assigned Backup Sequence
not in a remote mirror relationship or they are not the Number backup sequence number
master volume in a relation.
Explanation:
System action: The software process ends.
System action:
User response: For the source volumes identified in
the message, place the volumes in a remote mirror User response:
relationship or define the source volume as the master
volume.

Chapter 2. FMM messages 13

FMM0213E • FMM218E

IBM Tivoli Storage FlashCopy Manager software

FMM0213E IBM Tivoli Storage FlashCopy Manager
requires the Global Mirror consistency group to be in a
does not overwrite the
consistent synchronized state. When the consistency
ACS_REPOSITORY repository path
group is still copying, IBM Tivoli Storage FlashCopy
created with Tivoli Storage Manager for
Manager waits, for the maximum amount of time
Advanced Copy Services as this would
specified by the parameter TIMEOUT_FLASH, for the
invalidate all FlashCopy backups
consistency group to change to the 'consistent
created with Tivoli Storage Manager for
synchronized' state. If the consistency group does not
Advanced Copy Services. If you specify
change to the 'consistent synchronized' state, this error
a different path for parameter
message is displayed.
ACS_REPOSITORY, you can continue to
restore FlashCopy backups created with System action: The software process ends.
Tivoli Storage Manager for Advanced
Copy Services until the target set is User response: The consistency group that contains
reused by IBM Tivoli Storage FlashCopy the Global Mirror relationships, between the source and
Manager. Optionally, you can remove target volumes, should be started before the FlashCopy
the current ACS_REPOSITORY if it is backup begins. In addition, the Metro Mirror
acceptable to lose FlashCopy backups consistency group should be in a consistently
created with Tivoli Storage Manager for synchronized state.
Advanced Copy Services. In either case,
backups to Tivoli Storage Manager FMM216E The state 'cgstate' of the Global Mirror
created by Tivoli Storage Manager for consistency group 'cgname' is not valid
Advanced Copy Services remain for a consistent FlashCopy backup.
available for restore.
Explanation: For a remote FlashCopy to be started,
Explanation: The value repository path for parameter IBM Tivoli Storage FlashCopy Manager software
ACS_REPOSITORY points to a repository that was requires the Global Mirror consistency group to be in a
created by Tivoli Storage Manager for Advanced Copy consistent synchronized state.
Services. Backups created with Tivoli Storage Manager
for Advanced Copy Services can not be restore with System action: The software process continues.
IBM Tivoli Storage FlashCopy Manager. User response: The consistency group that contains
System action: Processing stops. the Global Mirror relationships, between the source and
target volumes, should be started before the FlashCopy
User response: Specify a different path for the backup begins. In addition, the Global Mirror
ACS_REPOSITORY. The backups created with Tivoli consistency group should be in a consistent
Storage Manager for Advanced Copy Services will synchronized state.
remain intact and can be restored using Tivoli Storage
Manager for Advanced Copy Services. If all the
backups created with Tivoli Storage Manager for FMM217E The primary source volume with serial
Advanced Copy Services are no longer required please number 'sernumber' is attached to the
delete the entire directory and try again. local host. A remote backup can only be
restored on the takeover host.

FMM0214W The restore status indicator (RSI) has a Explanation: Remote restore cannot be performed
value of 'RSI_INVALID' on target set 'id'. from the host on the local site. Perform restore from the
takeover host on the remote site instead.
Explanation: If the restore status RSI of the target set
has a value of RSI_INVALID, this means that a System action: The software process ends.
snapshot restore was initiated but did not terminate. User response: Retry remote restore on the takeover
Nevertheless, IBM Tivoli Storage FlashCopy Manager host at the remote site.
issues this warning and continue with the FlashCopy
backup.
FMM218E The storage device has not the
System action: minimum required firmware version
User response: Check whether the FlashCopy backup 'version'.'release'.'revison' installed.
ended successfully. Explanation: For a remote FlashCopy to be started on
Global Mirror with Change Volumes, IBM Tivoli
FMM215E The state of the Global Mirror Storage FlashCopy Manager software requires a
consistency group has not become the minimum firmware level on the storage device.
value 'consistent synchronized' inside System action: Processing ends.
the required periode of time.
User response: Upgrade the firmware version on the
Explanation: For a remote FlashCopy to be started,

14 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM219E • FMM231W

storage device and try the operation again. in the backup and not be restorable.
System action: Processing continues but the specified
FMM219E A timeout occurred while waiting for datastores will not be included in the backup.
the 'cgname' consistency group that
User response: Correct the input file so that it
contains the Global Mirror relationships
contains a valid datastore URL if this datastore is to be
with Change Volumes to be
included in the backup.
synchronized on remote site.
Explanation: For a remote FlashCopy to be started on
FMM228E No virtual machines are available for
a Global Mirror with Change Volumes, IBM Tivoli
processing after the input file is
Storage FlashCopy Manager requires the Global Mirror
evaluated.
consistency group to be in a consistent synchronized
state. Explanation: After the input file has been evaluated,
there are no virtual machines that can be processed.
System action: Processing ends.
System action: Processing ends.
User response: The consistency group that contains
the Global Mirror relationships, between the source and User response: Verify that the input file contains all
target volumes, must be started before the FlashCopy the virtual machines that should be evaluated. Modify
backup begins. In addition, lower the Cycling Period your input file so that there are virtual machines to
time and try the operation again. process.

FMM220E The Global Mirror 'cgname' consistency FMM229E The datastore 'datastore name' contains
group must have change volumes LUNs from more than one storage
assigned. subsystem. IBM Tivoli Storage
FlashCopy Manager can support LUNs
Explanation: For a remote FlashCopy to be started on
from only one storage subsystem.
a Global Mirror, IBM Tivoli Storage FlashCopy
Manager requires that the Global Mirror consistency Explanation: The specified datastore contains LUNs
group has the change volumes function assigned. from different storage subsystems.
System action: Processing ends. System action: Processing ends.
User response: Create change volumes for the User response: Modify the datastore so that it
consistency group that contains the Global Mirror contains only LUNs from one storage subsystem.
relationships.

FMM230E The backup type 'backup type' is not

FMM0225I Enabling the volumes and filesystems ... valid.
Explanation: After the FlashCopy, the target volumes Explanation: The specified backup type is not valid.
attached to the backup machine are imported in the
operating system and the file systems are mounted. System action: Processing ends.

System action: User response: Change the value to a valid backup

type.
User response: None.
FMM231W The raw device-mapping disk(s) 'disk
FMM226E The following line could not be parsed: names' of the virtual machine 'VM name'
infile line are excluded from backup. A later
restore of the virtual machine is
Explanation: The specified line contains a syntax error.
possible, but the restore does not
It cannot be parsed.
include these disks.
System action: Processing ends.
Explanation: The specified virtual disk(s) of the
User response: Correct the syntax on the line and specified virtual machine are raw device-mapping disks
retry the operation. which are not included in the hardware snapshot
backup. Hence, a restore of the virtual machine only
restores its standard virtual disks but not the raw
FMM227E The address of the datastore 'datastore
device-mapping disks.
URL' is not valid. It is not part of the
backup. System action: Processing continues.
Explanation: The specified datastore that is part of User response: The raw device-mapping disks might
this input file cannot be found. It will not be included

Chapter 2. FMM messages 15

FMM232I • FMM238W

be re-added manually after the virtual machine has

FMM235I Stopping the remote mirror
been restored.
relationships for the consistency group:
'cgname'.
FMM232I Deleting the remote mirror relationships
Explanation: For a remote FlashCopy backup to be
for the consistency group: 'cgname'.
restored into the takeover host, IBM Tivoli Storage
Explanation: For a remote FlashCopy backup to be FlashCopy Manager software requires to stop the
restored into the takeover host, IBM Tivoli Storage remote copy relationships if the SVC version used is 6.2
FlashCopy Manager software requires to delete the or higher.
remote copy relationships if the SVC version used is
System action: The software process continues.
earlier than 6.2.
User response: None.
System action: The software process continues.
User response: None.
FMM0236I Disabling the volumes and filesystems
...
FMM233W For the virtual machine 'VM name' the
Explanation: Before the snapshot restore from the
backup mode SNAPSHOT_INCL_MEM
backup to the production volumes, the production
is changed to SNAPSHOT_EXCL_MEM
volumes and file systems are disabled. The following
because it has independent disk(s)
actions are started: v Unmount v Remove devices v
attached: 'disk names'.
Remove logical volumes v Vary off the volume group v
Explanation: In principle, VSphere does not support Export volume groups.
snapshots including the virtual machine's memory for
System action:
virtual machines with independent disks attached.
However, snapshots excluding the virtual machine's User response: None.
memory are supported. For the specified virtual
machine the snapshot mode is changed from including
FMM237I Starting the remote mirror relationships
to excluding memory to allow the backup process to
for the consistency group: 'cgname'.
proceed.
Explanation: For a remote FlashCopy backup to be
System action: Processing continues.
restored into the takeover host, IBM Tivoli Storage
User response: A snapshot that excludes the virtual FlashCopy Manager software requires to stop the
machine's memory is not as consistent as a snapshot remote copy relationships if the SVC version used is 6.2
that includes the virtual machine's memory. Snapshot or higher. After the restore is complete, IBM Tivoli
consistency also depends on the application and the Storage FlashCopy Manager will restart the remote
precautions in place to ensure a consistent state before mirror relationships.
the backup is performed. As an alternative, the backup
System action: The software process continues.
mode can be set to SUSPEND.
User response: None.
FMM234W The raw device-mapping disk(s) 'disk
names' of the virtual machine 'VM name' FMM238W The original resource pool path cannot
were excluded during backup. Thus the be found: 'resource pool name'. The virtual
restored virtual machine does not machine 'VM name' is restored to the
include these disks. root resource pool of the host 'host name'.
Explanation: The specified virtual disk(s) of the Explanation: The named virtual machine cannot be
specified virtual machine are raw device-mapping disks associated to the vApp or resource pool. The vApp or
that are not included in the snapshot backup. When the resource pool that it was associated to during the
virtual machine is restored those are removed from its backup process is not available at restore time. In the
configuration. intervening time between backup and restore, the vApp
was deleted, renamed, or moved.
System action: Processing continues.
System action: Processing continues.
User response: The raw device-mapping disks might
be re-added manually after the virtual machine has User response: After the restore process is completed,
been restored. the virtual machine can be reassigned to either the
appropriate resource pool or vApp.

16 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM239W • FMM0281W

System action: The old background monitor will be

FMM239W The raw device mapped disk(s) 'disk
shut down.
names' of the virtual machine 'VM name'
were excluded during backup. Thus, User response: Check your configuration. Only one
they have been removed from the background monitor should be running.
configuration of the attached virtual
machine.
FMM0266E The storage device <storage device> is not
Explanation: The specified virtual disk(s) of the supported.
specified virtual machine are raw device mapped disk
that are not included in the snapshot backup. When the Explanation:
virtual machine is attached those are removed from its System action:
configuration.
User response:
System action: Processing continues.
User response: Raw device mapped disks might be FMM267I Adding the remote mirror relationships
re-added manually to the attached virtual machine. to the consistency group: 'cgname'.
Explanation: For a remote FlashCopy backup to be
FMM0240E The parameter restored into the takeover host, IBM Tivoli Storage
HARDWARE_ID_LVM_MIRROR for FlashCopy Manager software requires to delete the
the target set 'target_set_id' is set in the remote copy relationships if the SVC version used is 6.1
.fct–file 'file_name', but the production or lower. After restore completes, IBM Tivoli Storage
logical volumes are not mirrored. FlashCopy Manager adds the remote mirror
Explanation: The HARDWARE_ID_LVM_MIRROR relationships to the consistency group.
parameter should only used in an LVM mirror System action: The software process continues.
environment.
User response: None.
System action:
User response: If you want to use this feature you FMM0268E The information of the source / target
need to mirror the production logical volumes on volumes could not be found.
source volumes residing on different hardware units.
Otherwise, remove the parameter Explanation: The executable file 'splitint' is started
HARDWARE_ID_LVM_MIRROR parameter from the automatically as a daemon (sometimes referred as the
.fct file. background monitoring process) to monitor the
background copy. An attempt to obtain the status of the
copy process has failed.
FMM0261I A disk–only backup (option –d) was
invoked, forcing the parameter System action:
'FLASHCOPY_TYPE' of the .fcs–file to User response: Check the error log file
'COPY'. splitint_[p|b]_runagent_jjjjmmddHHMMSS.log in the
Explanation: If you specified a disk–only backup via directory specified in the parameter LOG_TRACE_DIR
the parameter -d and the parameter of the .fcs file. Check the availability of the storage
'FLASHCOPY_TYPE' of the .fcs file has the value of system using the applicable tool (STORWATCH
NOCOPY, IBM Tivoli Storage FlashCopy Manager sets Specialist, DS Storage Manager, or SVC console). Check
the value to COPY. the parameters in the .fcs file: v
COPYSERVICES_PRIMARY_SERVERNAME v
System action: COPYSERVICES_SERVERPORT v
User response: None. COPYSERVICES_USERNAME Also verify the
availability of the CIM agent and its connection to the
storage system as described in the storage–system
FMM265W A new background monitor has been documentation.
started. The currently registered
background monitor will shut down
now and the new background monitor FMM0281W Warning: Could not connect to the
will be used for further processing. admin assistant.

Explanation: A second background monitor has been Explanation:

registered at the management daemon. Since only one System action:
background monitor is allowed to be registered the
currently registered background monitor will be shut User response:
down now.

Chapter 2. FMM messages 17

FMM0282E • FMM0313E

FMM0282E The incremental FlashCopy cannot be FMM0288I Not all source/target pairs are in an
refreshed. Possible reasons are: 1. You incremental FlashCopy relation.
added a new source volume 2. You tried
Explanation:
to start an offline FlashCopy Backup
after an online FlashCopy Backup System action:
Problem solution: Run the withdraw
function with option '–n TargetSetID' User response:
and afterwards restart the FlashCopy
Backup. FMM0309E Cannot read file: filename.
Explanation: Explanation: IBM Tivoli Storage FlashCopy Manager
System action: is unable to read the data file <filename>.

User response: System action:

User response: Check the access permissions of the
FMM0283E The incremental FlashCopy cannot be affected file and try again.
refreshed. The source/target pairs are
not in an incremental FlashCopy FMM0310E Cannot write file: filename.
relation. Problem solution: Run the
withdraw function with option '–n Explanation: IBM Tivoli Storage FlashCopy Manager
TargetSetID' and afterwards restart the is unable to write to the data file filename. The affected
FlashCopy Backup. files could be: v <LOG_TRACE_DIR>/splitint_b_
<date_time_stamp>.log v <LOG_TRACE_DIR>/
Explanation: splitint_p_ <date_time_stamp>.log v
System action: <LOG_TRACE_DIR>/splitint_b_
<date_time_stamp>.trace v <LOG_TRACE_DIR>/
User response: splitint_p_ <date_time_stamp>.trace v <config_file> v
<ids_control_file> v the field value EXCHANGE_FILE
in a backup cycle record.
FMM0285W All source/target pairs are in an
incremental FlashCopy relation. DP for System action:
Snapshot Devices will override the
value 'flashcopy type' of the parameter User response: Check the access permissions of the
FLASHCOPY_TYPE to 'INCR'. affected file and try again.

Explanation:
FMM0311E Request canceled by user
System action:
Explanation: (Oracle) BACKINT terminated at user's
User response: request. (DB2) Program terminated at user's request.
System action:
FMM0286I All source/target pairs are in an
incremental FlashCopy relation. User response: None.

Explanation:
FMM312E The 'datastore name' datastore is not
System action: attached to a host.
User response: Explanation: The specified datastore is not attached to
a host. The current operation cannot continue.
FMM0287I No source/target pairs are in an System action: Processing ends.
incremental FlashCopy relation.
User response: Exclude the datastore from the current
Explanation: operation or attach it to a host.
System action:
FMM0313E Environment variable env_var is not
User response:
correct!
Explanation: This error can occur when the
environment variable is set but contains a non–existent
directory path.
System action:

18 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0314E • FMM0325E

User response: Check the value of the environment .fcs file and v The directory containing the idssave file
variable and try again. specified by the parameter IDS_CONTROL_FILE in the
.fcs file. IBM Tivoli Storage FlashCopy Manager warns
you if the free space of these file systems falls below 50
FMM0314E File not found or not accessible:
MB. If it is under 5 MB an error is issued and the
'filename'.
program fails, throwing an exception.
Explanation: The file <filename> was not found or is
System action:
not accessible to IBM Tivoli Storage FlashCopy
Manager. User response: Ensure that the free space on these file
systems is large enough.
System action:
User response: Check path, name and the permissions
FMM0321E IBM Tivoli Storage FlashCopy Manager
of the file and try again.
requires a free space of at least 5 MB in
the file system containing the directory
FMM0315E The effective user ID of the process path.
could not be set to the user 'userid'.
Explanation: If the free space of the checked file
Explanation: One of the following cases can cause this systems (see the explanation for IDS1310W) is under 5
error: v The access rights for splitint are not set to 4750. MB this error message is issued and the program fails
Because the s–bit is not set, IBM Tivoli Storage throwing an exception.
FlashCopy Manager cannot switch between the users
System action: Processing stops.
'db2<sid>' and 'root' during the execution of the
program. v The file system that splitint is installed in User response: Ensure that the free space on the
was mounted with the NOSUID option. database file system is large enough.
System action:
FMM0322E The environment variable env var could
User response: v Check the splitint file in the directory
not be set!
/usr/tivoli/tsm/acssap/db2/x.y.z, and set the access
rights for splitint with chmod 4750 splitint. After the Explanation:
installation, the command ls –l splitint.... outputs a line
System action:
such as: -rwsr–x––– 1 root dba 1918611 Apr 11 17:09
splitint (This is what setup.sh would do if you had User response:
used it.) v If the file system that splitint is installed in
was mounted with the NOSUID option, mount the file
system with SUID allowed. FMM0323E File 'file' was not found on the target
disks.

FMM0318W Warningcolon; File 'file name' still exists Explanation:

on the backup system. System action:
Explanation: IBM Tivoli Storage FlashCopy Manager User response:
checks at the start of the function flashcopy if any of
the files passed in the file list still exist on the backup
system. If so, this warning is issued. Normally, none of FMM0324W Environment variable env var has value
the files should exist because the withdraw function, 'value'.
which should run before the FlashCopy, unmounts the Explanation:
files systems, varies them offline, exports the volume
groups, and removes the devices. System action:

System action: User response:

User response: Always run the function withdraw

before starting the FlashCopy again. FMM0325E Environment variable env var could not
be unset! Unset this variable and restart.

FMM0320W The free space in the file system Explanation:

containing the directory path is only System action:
amountMB.
User response:
Explanation: The existing free space of the file
systems containing the following directories is checked:
v The database home directory and v The directory
specified by the parameter LOG_TRACE_DIR in the

Chapter 2. FMM messages 19

FMM0326I • FMM348E

Storage FlashCopy Manager uses a lock mechanism.

FMM0326I Environment variable env var is
successfully unset. System action:
Explanation: User response: None.
System action:
FMM0332I Suspend the database activity.
User response:
Explanation:
FMM0327E Operating system error error_no: message System action:
text
User response:
Explanation: IBM Tivoli Storage FlashCopy Manager
encountered an unexpected–message error during the
execution of a system function. The corresponding FMM0340I The following backup items were not
operating system error and message text are displayed. assigned to corresponding snapshot
The message appears, for example, as a result of v An items: backup_items
incorrect user ID on the parameter Explanation: Backup items are storage elements such
LOGON_HOST_PROD in the .fcs file v An incorrect as LUN identifiers on storage area network (SAN) or
password given for the user ID on the parameter network share paths on network-attached storage
LOGON_HOST_PROD in the .fcs file v An incorrect (NAS). Backup items are identified by Tivoli Storage
TCP/IP name on the parameter LOGON_HOST_PROD FlashCopy Manager OS agent "acsgen" and are based
in the .fcs file (for example: connection timeout) v A on the backup procedure of the application that
failure allocating memory using the function malloc, requests the backup or restore operation. A snapshot
and the operating system cannot satisfy the request item is the smallest entity identifiable in a snapshot.
System action: Backup items either all or a subset are assigned to the
corresponding snapshot items. A subset is assigned in
User response: Check the specified error message. an AIX LVM mirroring or Oracle ASM environment.
System action: None.
FMM329E The LUN 'LUN name' is needed for this
operation but cannot be accessed. User response: Processing continues..

Explanation: The specified LUN is required for the

current operation but cannot be reached. FMM0341W The status information for the fsname
file system cannot be read. The
System action: Processing ends. following error message was generated
by the operating system: txtmsg.
User response: Verify that the LUN is attached to the
ESX host and that the connection is working correctly. Explanation: The system call "stat" was not successful
because of a specific error message.
FMM330E The datastore with the name System action: None.
'datastorename' was not found. It is not
part of the backup. User response: Evaluate the operating system-specific
warning message to resolve the problem.
Explanation: The specified datastore could not be
found but it is part of the input file. It will not be
included in the backup and not be restorable. FMM0347E The update of the IDS repository failed.

System action: Processing continues but the specified Explanation: IBM Tivoli Storage FlashCopy Manager
datastores will not be included in the backup. failed to update the backup or restore status indicator
(BSI/RSI) during the monitoring of the background
User response: Correct the infile so that it contains copy process.
valid datastore names if this datastore is to be included
in the backup. System action:
User response: Check the traces for details about this
FMM0331I The file 'filename' is locked, waiting one failure. One possible cause is a full file system.
second and retry!
Explanation: IBM Tivoli Storage FlashCopy Manager FMM348E The following auxiliary vdisk: 'aux vdisk'
saves control information for the FlashCopy process in is mapped to host 'host name'. It should
an internal repository that consists of several files. be mapped to takeover host 'takeover
Some of these files may need to be written concurrently host' only.
by several processes. To ensure consistency, IBM Tivoli Explanation: Auxiliary vdisks should be mapped only

20 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0349E • FMM0356E

to takeover host and not to any other hosts.

FMM0353E Background copy process on the oldest
System action: The software process ends. target set 'target set' still running.

User response: Remove all host maps for the auxiliary Explanation:
vdisks except the host map to the takeover host.
System action:
User response:
FMM0349E The target set 'targetSetID' does not
match the source volumes.
FMM0354E The copy type argument 'copy_type' is
Explanation: IBM Tivoli Storage FlashCopy Manager
not valid.
checks whether the target set for the FlashCopy backup
contains a target volume for each source volume, Explanation: The argument (FLASHCOPY_TYPE) of
located in the same hardware unit and with the same the command line option –C <FLASHCOPY_TYPE>
size. can have the following values: COPY, NOCOPY and
INCR. Any other value is not valid. Furthermore, INCR
System action:
is only valid for an SVC configuration with version
User response: Check the volume list of this target set 4.2.1 of the SVC master console.
and ensure that the volumes are in the same hardware
System action:
unit and have the same size as the source.
User response: Specify one valid value.
FMM0350E A background copy process of type
'CopyType' is still running on target set FMM0355E Unable to connect to the copy services
'targetSetID'. server 'csname'.
Explanation: IBM Tivoli Storage FlashCopy Manager Explanation: For a FlashCopy backup to be taken,
fails if a background copy is still running for the same IBM Tivoli Storage FlashCopy Manager software
logical FlashCopy group (see the documentation). requires to connect to the storage system using the
However, any target set (state AVAILABLE) that does parameter COPYSERVICES_PRIMARY_SERVERNAME
not yet belong to a logical FlashCopy group (state for a local backup and
AVAILABLE) can be selected. COPYSERVICES_REMOTE_SERVERNAME for a
remote backup.
System action:
System action: Processing ends.
User response: Check the backup status of the
FlashCopy backups that may be running. User response: Ensure to have LAN connection
between the host running the IBM Tivoli Storage
FlashCopy Manager software and the copy services
FMM0351I The target set with ID 'targetSetID' is
storage server.
selected for this run.
Explanation: IBM Tivoli Storage FlashCopy Manager
FMM0356E You cannot run a Snapshot restore from
use two procedures for the selection of a target set.
target set 'targetSetID from' if the sources
System action: are involved in a relationship of type
'copytype' with the target set 'targetSetID'.
User response: None.
Explanation: IBM Tivoli Storage FlashCopy Manager
exploits the feature ?Multiple Relationship FlashCopy?
FMM0352E No target set found to accept a backup of the storage system. This means that for IBM Tivoli
of type 'copy_type'. Storage FlashCopy Manager the source set of volumes
Explanation: If all the target sets are being used with can participate in multiple snapshot relationships with
the same type of logical FlashCopy group (either INCR several target sets of volumes. However, there are some
or COPY), you will not find a target set to make a limitations: v A source can have up to 12 targets v A
FlashCopy with a different copy type. target can only have one source v A target cannot be a
source at the same time
System action:
System action:
User response:
User response: To start a snapshot restore (in reverse,
from the target to the source volumes) you have to
withdraw the relationship with the specified target set.

Chapter 2. FMM messages 21

FMM0357I • FMM0389E

FMM0357I FlashCopy type is 'copy_type'. FMM367I The scope is being limited to the
following data center(s): 'dcnames'.
Explanation: IBM Tivoli Storage FlashCopy Manager
has detected a discrepancy in the FlashCopy Explanation: The input file defining the domains is
specification. being used. It limited the snapshot process to the scope
of these data centers.
System action:
System action: Processing continues.
User response: None.
User response: None.
FMM0358E An invalid value 'copy_type' has been
specified for the FlashCopy type in the FMM368I Stopping the consistency group 'cgname'
profile '.fcs file'. and all its older dependents.
Explanation: The parameter FLASHCOPY_TYPE of Explanation: Usually IBM Tivoli Storage FlashCopy
the IBM Tivoli Storage FlashCopy Manager profile (.fcs Manager re-uses the oldest set of target volumes for the
file) can have the following values: COPY, NOCOPY backup. However if for some reason it is not the case,
and INCR. Any other value is not valid. INCR is only IBM Tivoli Storage FlashCopy Manager will stop all the
valid for an SVC configuration starting with version older FlashCopy mappings than the one been used to
4.2.1 of the SVC master console. avoid that the space-efficient volumes grow up to its
defined virtual size.
System action:
System action: Processing continues.
User response: Specify one valid value.
User response: None.
FMM0361E The target set must be specified over the
option –n, if the parameter FMM0378E The value of the parameter
EXTERNAL_LVM_PLUGIN is set. 'parameter_name' in the device section of
the profile is invalid.
Explanation:
Explanation: This message is displayed when an
System action:
invalid value is found for one of the parameters of the
User response: device section of the profile.
System action:
FMM364E Parameter 'parameter ' is mandatory.
User response: Change the value according to the
Explanation: The specified parameter is missing. values explained in the section Parameters of the IBM
Tivoli Storage FlashCopy Manager.
System action: Processing ends.
User response: Specify the named parameter. FMM0384W The parameter
IGNORE_LVM_MIRROR_CHECK_ ERROR is set to
FMM365E The data center with the name 'dcname' YES. All errors on AIX LVM mirroring
was not found. checking will be ignored.

Explanation: The specified data center could not be Explanation:

found in the vCenter server. System action:
System action: Processing ends. User response:
User response: Specify a valid datacenter in the infile
defining the domains. FMM0389E Errors occurred during the deletion of
one (or more) backups.
FMM366E The following line in the domain input Explanation: One (or more) backups that were
file could not be parsed: 'inputline'. specified to be deleted could not be deleted.
Explanation: The input file defining the domains System action: Processing ends.
contains unexpected keywords.
User response: Review the preceding error messages
System action: Processing ends. for information about how to resolve this issue.
User response: Verify the format of the input file
defining the domains.

22 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM390E • FMM0397E

FMM390E The virtual machines with the specified FMM394E Redirected restores are not allowed for
instance UUIDs have not been found in distributed virtual machines. The virtual
the backup. Update the input file with machine 'VM name' spans multiple
valid instance UUIDs. Listing missing datastores and is distributed. Do not
UUIDs: instance uuids specify a target VM name or a target
datastore for the restore operation.
Explanation: Virtual machines with the instance
UUIDs specified in the input file were not found in the Explanation: Redirected restores are not allowed for
backup. distributed virtual machines. The specified virtual
machine spans multiple datastores and is thus
System action: Processing ends.
distributed. Please do not specify a target VM name or
User response: Replace the instance UUIDs in the a target datastore for the restore operation.
input file with valid values.
System action: Processing ends.
User response: Do not specify a target VM name or
FMM391E The 'datastore name' datastore could not
target datastore for the restore operation.
be attached to the 'hostname' host. Please
look up the message user response in
the users guide for a step-by-step guide FMM0395E This license does not allow to use LVM
how to solve this problem. mirrors.
Explanation: The specified datastore could not be Explanation: The use of DB2 ACS or IBM Tivoli
attached to the specified host. Please look up the Storage FlashCopy Manager in an LVM mirror
message user response in the users guide for a environment requires the extended license of IBM
step-by-step guide how to solve this problem. Tivoli Storage FlashCopy Manager. Starting with V5.5,
the DB2 version of IBM Tivoli Storage FlashCopy
System action: Processing ends.
Manager (DP for Snapshot Devices) is a licensed,
User response: Open the "Add datastore" wizard in functionally enhanced version of the DB2 Advanced
the vSphere Clients "Datastores" view. Select the ESX Copy Services (DB2 ACS) product initially provided
host which was specified in the raised error message. with DB2 Enterprise V9.5. Conversely, DB2 Advanced
Select "Disk/LUN" on the next page. On the "Select Copy Services can be regarded as a functionally
Disk/LUN" page select a disk whose VMFS Label restricted version of IBM Tivoli Storage FlashCopy
column contains the datastore name as specified in the Manager.
raised error message. On the next page select "Format
System action:
the disk". This will erase the backup contained on this
target disk! Specify an arbitrary datastore name on the User response: Contact IBM Tivoli support to acquire
"Properties" page. It will be overwritten by the next the required license.
FCM backup. Finish the wizard. Repeat this for all
disks whose VMFS Label column contains the datastore
FMM0396E This license does not allow to use JFS
name as specified in the raised error message. A new
file systems.
FCM backup can be performed afterwards.
Explanation: During a snapshot backup run, IBM
Tivoli Storage FlashCopy Manager detected that at least
FMM392E The 'datastore name' datastore could not
one file system is of type JFS. Because JFS file systems
be attached.
need to be verified on the offload system by the IBM
Explanation: The specified datastore could not be Tivoli Storage FlashCopy Manager device agent
attached. running with the -force mount– (–F) option, the IBM
Tivoli Storage FlashCopy Manager product must be
System action: Processing ends.
installed and licensed. The current snapshot backup
User response: Contact IBM support. run is deleted.
System action:
FMM393E The target instance UUID 'target instance
User response: Install and license IBM Tivoli Storage
uuid' specified in the input file cannot
FlashCopy Manager or change all file systems to type
be found. Add a valid target instance
JFS2 and restart the snapshot backup.
UUID to the input file.
Explanation: The target instance UUID specified in the
FMM0397E You cannot freeze filesystems of type
input file was not found.
JFS.
System action: Processing ends.
Explanation: This message may indicate, for example,
User response: Specify a valid target instance UUID. that profile parameter LVM_FREEZE_THAW is set to
YES but at least one of the file systems involved is a

Chapter 2. FMM messages 23

FMM0398E • FMM404I

JFS file system. The freeze/thaw feature is only

FMM0400I The process is waiting for BRBACKUP.
available for JFS2 file systems. It is used to suspend all
I/O on the file systems while taking a snapshot of Explanation: The process is waiting for BRBACKUP to
them. JFS file systems do not support the freeze/thaw set a table space in the begin/end backup mode.
feature. Therefore, the parameter LVM_FREEZE_THAW
System action:
is not allowed to be YES if any JFS file systems are
used. User response: None.
System action:
FMM401I The 'original VM name' virtual machine
User response: There are two options to resolve this
has been registered with the new name,
problem: 1. If you need to use JFS file systems, you
'new name'.
must explicitly set the profile parameter
LVM_FREEZE_THAW to NO in the CLIENT section of Explanation: The specified virtual machine in the
the profile. 2. Move the data from the JFS file systems backup has been made available with the specified new
to JFS2 file systems. The profile parameter name.
LVM_FREEZE_THAW can then be set to YES.
System action: Processing continues.

FMM0398E Consistency group cgname is not valid User response: No action is required.
(state: status) to perform a FlashCopy
restore. FMM402I The 'datastore name' datastore with the
Explanation: IBM Tivoli Storage FlashCopy Manager new datastore name 'new datastore name'
function restore requires the FlashCopy consistency was successfully attached to the 'ESX
group to be in an Idle_Or_Copied or Copying state in host name' ESX host.
order to be valid for restore. Explanation: A datastore from the backup has been
System action: Processing ends. made available on the specified ESX host.

User response: Try the restore operation again using a System action: Processing continues.
different backup version. User response: No action is required.

FMM0399W Timestamp –>timestamp<– cannot be FMM403I All the virtual disks (exclusive of RDM
converted. disks) on the virtual machine 'source vm
Explanation: The status of the background copy is name' are attached to the target virtual
written by the background monitoring process daemon machine 'target vm name'.
to a file named fc_exchange.'bseq_number' in the Explanation: All virtual disks (exclusive of RDM
directory that contains the IDSAVE specified by the disks) of the specified virtual machine have been
parameter IDS_CONTROL_FILE. The file attached to the specified target virtual machine.
fc_exchange.'bseq_number' has, for each volume pair,
the entry 'volume_pair: target source size state System action: Processing continues.
YYYY–MM–DD–HH.MM.SS YYYY–MM–DDHH. User response: No action is required.
MM.SS rate', where: v target is the serial number of the
target volume v source is the serial number of the
source volume v state can be 'active' if the background FMM404I The virtual disks on the virtual machine
copy is running or ' none' if the background copy is 'source virtual machine name' with the disk
finished v YYYY–MM–DD–HH.MM.SS represents keys 'diskkeys' are attached to the target
approximate times for the start and end of the virtual machine 'target virtual machine
background process (in seconds since 00:00:00 GMT, name'.
January 1, 1970, which is the time standard the Explanation: The specified virtual disks of the
operating system uses) v rate is the transfer rate within specified virtual machine have been attached to the
the storage system To calculate the transfer rate some specified target virtual machine.
conversion is needed. When doing this conversion, an
error occurred. The rate value is invalid. System action: Processing continues.
System action: User response: No action is required.
User response: Check the date and time setting of the
machine.

24 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0405I • FMM415E

FMM0405I The process waited num_sec seconds for FMM0410E Cannot open or delete switch file 'file
BRBACKUP in util_file_online name'. Check permissions.
communication.
Explanation: If Data Protection for SAP is not installed
Explanation: This message indicates the total amount correctly (as the root user on UNIX or Linux or
of time the process waited for BRBACKUP to set a administrator group on Windows) then Data Protection
table space in "begin backup" or "end backup" mode. for SAP is not able to open the necessary
The wait time given is the sum of the wait times for all communication file to the SAP system.
table spaces participating in the backup.
System action:
System action:
User response: Check the file permission.
User response: None.
FMM0411E Maximum time waiting for BRBACKUP
FMM406W The 'vm name' virtual machine is a expired.
distributed VM because the 'virtual disk
Explanation: The SAP database utilities did not
name' disk is located in the 'disk directory'
respond within the expected time.
datastore directory, which is not the
'working directory' VM working directory. System action:
Explanation: One of the disks within the virtual User response: Contact your SAP administrator.
machine is in a directory that is not the working
directory.
FMM0412E BRBACKUP wasn't able to switch
System action: Processing continues. requested tablespace in BEGIN/END
BACKUP mode.
User response: Be aware that the limitations of virtual
machines spanning multiple datastores apply. Explanation: Data Protection for SAP could not
continue the backup, because BRBACKUP was not able
to switch the requested table space in BEGIN or END
FMM407E The maximum number of SCSI targets
backup mode. This is necessary for locking the table
for a virtual machine is exceeded.
space.
Explanation: All SCSI targets are in use.
System action:
System action: Processing ends.
User response: Contact your SAP administrator.
User response: Remove some SCSI targets.
FMM0413E Error while requesting tablespace
FMM408E The disks with the 'diskkeys' disk keys switch.
cannot be found in the backup and are
Explanation: BRBACKUP could not switch table space
not attached.
in BEGIN or END backup mode.
Explanation: The specified disk keys cannot be found
System action: Contact your SAP administrator.
in the backup and are not attached.
User response:
System action: Processing ends.
User response: Specify valid diskkeys.
FMM0414E Error while requesting tablespace
switch.
FMM409E There is not enough free space available
Explanation: BRBACKUP reported an error while
in the 'datastore name' target datastore to
trying to switch a table space in BEGIN or END
complete this operation. space needed is
backup mode.
required to complete this operation.
space available is free. System action:
Explanation: Not enough free space is available in the User response: Contact your SAP administrator.
specified target datastore.
System action: Processing ends. FMM415E The 'datastore name' datastore cannot be
found. In the input file the named
User response: Choose another target datastore or
datastore is specified as a target
make more space available in the specified datastore.
datastore for the restore operation.
Explanation: The specified datastore has not been
found but is needed as a target datastore for the restore

Chapter 2. FMM messages 25

FMM416E • FMM0424I

operation. A backup with the specified ID cannot be

FMM420E The 'ESX hostname' ESX host supports
found.
the 'found API version' API version. The
System action: Processing ends. requested operation is available since
the 'needed API version' API version and
User response: Specify a valid target datastore in the is not supported by the ESX host.
input file.
Explanation: The requested operation is not available
in the API version supported by the specified ESX host.
FMM416E The 'vm name' virtual machine could not
be restored to the 'target datastore' System action: Processing ends.
datastore using 'target vm name' VM
User response: The requested operation cannot be
name. A VM with the same name
used with this ESX host If this operation is needed you
already exists in the datastore.
must upgrade the API.
Explanation: The specified virtual machine could not
be restored because another virtual machine with the
FMM421E The restore operation cannot be
same name already exists in the target datastore.
completed because the 'vm name' virtual
System action: Processing ends. machine with 'vm instance uuid' instance
UUID is not powered off.
User response: Specify another target datastore or
delete the existing virtual machine in the specified Explanation: The restore operation cannot be
datastore. completed because the specified virtual machine is not
powered off.

FMM417I The 'source vm name' virtual machine is System action: Processing ends.
successfully restored to the 'datastore
User response: Power off the specified virtual
names' datastore(s) and registered with
machine.
the name 'registered vm name'.
Explanation: The specified virtual machine has been
FMM422E A virtual disk was not found for the
successfully restored to the specified datastores.
'diskkey' disk key as specified in the
System action: Processing continues. input file.

User response: No action is required Explanation: No virtual disk was found for the
specified disk key.

FMM418I The attached virtual disk with the 'disk System action: Processing ends.
key' key is successfully detached from
User response: You must specify a valid diskkey.
the 'virtual machine name' virtual
machine.
FMM423I The 'diskname' virtual disk on the 'virtual
Explanation: The attached virtual disk with the
machine name' virtual machine was
specified key has been successfully detached from the
successfully restored.
virtual machine with the specified name.
Explanation: The specified virtual disk was
System action: Processing continues.
successfully restored.
User response: No action is required.
System action: Processing continues.
User response: No action is required.
FMM419E The configured vCenter server supports
the 'found API version' API version. The
requested operation is available since FMM0424I Start Snapshot backup destination backup
the 'needed API version' API version and type sid host productive host backup host list
is not supported by the configured sid list
vCenter server.
Explanation:
Explanation: The requested operation is not available
System action:
in the API version supported by the vCenter server.
User response:
System action: Processing ends.
User response: The requested operation cannot be
used with this vCenter server. If this operation is
needed you must upgrade the API.

26 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0425I • FMM436E

FMM0425I flashcopy type Start Snapshot background FMM432E The vmware snapshot operation for the
copy virtual machine with instance uuid
'instance uuid' failed: 'error'.
Explanation:
Explanation: The snapshot operation failed on the
System action:
specified virtual machine.
User response:
System action: Processing ends.
User response: Check the error message.
FMM426W The following virtual machine question
has been answered to with 'answer':
question FMM433W The vmware power on operation for the
virtual machine 'vmref' failed: 'error'.
Explanation: The specified question has been
answered with the specified value. Explanation: The operation power on after the power
off for the purpose of taking a snapshot failed on the
System action: Processing continues.
specified virtual machine.
User response: Nothing
System action: Processing continues.
User response: Check the vmware specific error
FMM0427I Stop Snapshot background copy
message.
Explanation:
System action: FMM434W The remove operation of the vmware
snapshot 'snapref' failed: 'error'.
User response:
Explanation: The snapshot remove operation failed.
FMM0428I Start Withdraw System action: Processing continues.
Explanation: User response: Check the vmware specific error
message.
System action:
User response: FMM435E The virtual machine 'VM name' can not
be restored because the backup is in use
FMM0429I Stop Withdraw by an offloaded TSM backup. The
restore of a distributed VM is not
Explanation: allowed if an offload TSM backup is in
System action: progress. Wait until the offload backup
is complete.
User response:
Explanation: The restore of a distributed VM is not
allowed if an offload TSM backup is in progress. Wait
FMM0430I Enabling the volumes and filesystems until the offload backup is complete.
finished
System action: Processing ends.
Explanation:
User response: Wait until the offload backup is
System action: complete.
User response:
FMM436E The virtual machine 'VM name' could
FMM431E One or more vmware snapshot not be restored because the backup is
operations failed. already in use by an other VM. The
restore of a distributed VM is not
Explanation: The snapshot operation for one or more allowed if the mounted datastore is
virtual machines failed. already in use by a VM. Detach this
backup. Try the operation again.
System action: Processing ends.
Explanation: The restore of a distributed VM is not
User response: Verify the log for preceding error
allowed if the mounted datastore is already in use by a
messages containing the specific name of the virtual
VM. Detach this backup. Try the operation again.
machines involved and the description of the error.
System action: Processing ends.

Chapter 2. FMM messages 27

FMM437E • FMM0458I

User response: Detach this backup. Try the operation or contact your IBM/Tivoli Sales Representative.
again.
FMM0453W This version of Data Protection for
FMM437E The virtual disks cannot be added or SAP(R) will expire in number days.
replaced on the 'vm name' virtual
Explanation: This is a test version with a time limit. It
machine with 'vm instance uuid' instance
will expire in number days.
UUID identifier. The specified virtual
machine is suspended. System action:
Explanation: The resource configuration of a virtual User response: Order a release version of the product
machine cannot be modified while it is suspended. or contact your IBM/Tivoli Sales Representative before
the version expires.
System action: Processing ends.
User response: Resume the specified virtual machine
FMM0454I *** This copy is NOT FOR RESALE. ***
then try again.
Explanation: This version is not for resale.
FMM438E The virtual disks cannot be removed System action:
from the 'vm name' virtual machine with
'vm instance uuid' instance UUID User response: None.
identifier. The specified virtual machine
is suspended. FMM0455E License file file name does not exist.
Explanation: The resource configuration of a virtual Explanation: The license file agent.lic was not found
machine cannot be modified while it is suspended. where expected.
System action: Processing ends. System action:
User response: Resume the specified virtual machine User response: Make sure that the agent.lic file resides
then try again. in the same directory as the init<SID>.utl file.

FMM439W The vmware snapshot operation for the FMM0456E Unable to access license file file name.
virtual machine with instance uuid
'instance uuid' failed: 'error'. The backup Explanation: The license file could not be accessed.
of this virtual machine will be crash System action:
consistent only.
User response: Make sure the access permissions
Explanation: The vmware snapshot operation failed allow read/write access.
on the specified virtual machine.
System action: Processing continues. FMM0457E License file file name contains invalid
User response: Check the error message. data/checksum.
Explanation: The license file is invalid.
FMM451E The disk with the 'diskkeys' disk key is a System action:
raw device-mapping disk which must
not be attached. User response: Make sure you have the right agent.lic
file for the right platform installed. agent.lic files are
Explanation: The specified disk is a raw platform dependent.
device-mapping disk which must not be attached to
another virtual machine.
FMM0458I Fake–Mode is activated.
System action: Processing ends with error.
Explanation: This message signals that the current
User response: Specify only diskkeys that represent operation is a simulated operation. Simulations can be
standard virtual disks. performed using the Administration Assistant.
System action:
FMM0452E This version of Data Protection for
SAP(R) has expired. User response: None.

Explanation: This is a test version that has expired.

System action:
User response: Order a release version of the product

28 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM459E • FMM0510E

FMM459E One or more suspend operations failed. FMM506I The 'vm name' virtual machine with the
'vm instance uuid' instance UUID is
Explanation: One or more suspend operations failed.
suspended.
System action: Processing ends.
Explanation: The specified VM is suspended.
User response: Check preceding error messages.
System action: Processing continues.
User response: No action is required.
FMM0460E No mux file is found with the name
name
FMM507I The software snapshot of the 'vm name'
Explanation: A mux file is a data structure holding
virtual machine with the 'vm instance
internal metadata needed for restore puposes. Each
uuid' instance UUID is removed.
backup image gets a mux file assigned.
Explanation: The software snapshot of the specified
System action:
virtual machine is removed.
User response: Check the logs for further information.
System action: Processing continues.
If the problem cannot be resolved contact your IBM
support personnel. User response: No action is required.

FMM0461I Created tracefile 'tracefile' for process ID FMM508E The 'vm name' virtual machine might be
'id'. the virtual machine containing IBM
Tivoli Storage FlashCopy Manager and
Explanation: The named trace file has been created.
cannot be part of the backup. Rename it
System action: or specify the virtual machine
containing IBM Tivoli Storage
User response: None. FlashCopy Manager in the 'profile
parameter name' profile parameter in the
FMM0503E Unexpected error occurred. profile.

Explanation: An unexpected error occurred. Explanation: The virtual machine that contains IBM
Tivoli Storage FlashCopy Manager cannot be part of a
System action: Processing ends. backup. The specified virtual machine might contain
User response: Gather information from the trace file IBM Tivoli Storage FlashCopy Manager.
and log file and contact your IBM service System action: Processing ends.
representative.
User response: Rename the specified virtual machine
or add the name of the IBM Tivoli Storage FlashCopy
FMM504I A software snapshot including memory Manager virtual machine to the profile.
is created of the 'vm name' virtual
machine with the 'vm instance uuid'
instance UUID. FMM0509E More than one instance of this
executable are running now.
Explanation: A software snapshot including memory
is created of the specified virtual machine. Explanation: You have to wait until previous backup
is done before you can run this backup.
System action: Processing continues.
System action: Processing ends.
User response: No action is required.
User response: Wait until previous backup is done
and try again.
FMM505I A software snapshot excluding memory
is created of the 'vm name' virtual
machine with the 'vm instance uuid' FMM0510E acsgen has to be started from the CLI
instance UUID. with the required '-D' parameter.

Explanation: A software snapshot excluding memory Explanation: acsgen requires the '-D' parameter to
is created of the specified virtual machine. start.

System action: Processing continues. System action: Processing fails.

User response: No action is required. User response: Retry the operation using the '-D'
parameter.

Chapter 2. FMM messages 29

FMM0511I • FMM0518E

FlashCopy Manager virtual machine in the profile.

FMM0511I ====>Performing IBM Tivoli Storage
FlashCopy Manager v1 command.
FMM0515E Filesystem consistency check failed.
Explanation: This message is displayed starting the
speicified function (BACKUP, WITHDRAW or Explanation: Filesystem consistency check on the
RESTORE) of DP for Snapshot Devices. filesystems processed by Flashcopy failed. This means
that there were some inode changes on the filesystem
System action: None.
when executing DP for Snapshot Devices backup on
User response: None. the production system.
System action: Please ensure that you do not make
FMM512E The virtual machine containing the any changes to the production system during
vCenter server cannot be part of the FlashCopy backup, that may cause changes to the
backup. The 'vm name' virtual machine inodes on the database filesystems. This will result in
is part of the backup but it is specified inconsistency in the database filesystems being
as the vCenter server virtual machine in processed by Flashcopy. Examples of operations
the 'profile parameter name' parameter in resulting in inode changes are: When a file is created or
the profile. deleted. When a write() call occurs to a file opened
with O_SYNC and the write causes a new disk block
Explanation: The virtual machine specified in the
allocation. When fsync() or sync() functions are called.
profile as vCenter server virtual machine has been
When a write causes an indirect or double-indirect
found to be part of the backup.
block to be allocated. Another way to get around this
System action: Processing ends. problem is to use raw logical volumes for your
databases.
User response: Rename the specified virtual machine
or change the specified name of the vCenter server User response: Please execute the backup command
virtual machine in the profile. again.

FMM513E The 'vm name' virtual machine might be FMM0516E The initialization of the ODM API
the virtual machine containing the failed with ODM error number
vCenter server and cannot be part of the odmerrno: description.
backup. Rename it or specify the virtual
Explanation: IBM Tivoli Storage FlashCopy Manager
machine containing the vCenter server
uses the ODM API library for the logical volume
in the 'profile parameter name' profile
manager. The specified error occurred when trying to
parameter in the profile.
initialize this library.
Explanation: The specified virtual machine is
System action: Processing stops.
suspected to contain the vCenter server and can thus
not be part of the backup. User response: Validate the specific error description.
System action: Processing ends.
FMM0517E Failed to get the ID of the volume group
User response: Rename the specified virtual machine
vgname using the AIX command:
or add the name of the vCenter server virtual machine
command.
to the profile.
Explanation: IBM Tivoli Storage FlashCopy Manager
uses the displayed command to get the volume group
FMM514E The virtual machine that contains IBM
ID. The command failed.
Tivoli Storage FlashCopy Manager
cannot be part of the backup. The 'vm System action: Processing stops.
name' virtual machine is part of the
User response: Check the state of the AIX ODM and
backup but it is specified as the virtual
of the volume group. Run this command from the AIX
machine containing IBM Tivoli Storage
command line.
FlashCopy Manager in the 'profile
parameter name' parameter in the profile.
FMM0518E Failed to get the ID of the logical
Explanation: The virtual machine specified in the
volume lvname using the AIX command:
profile as IBM Tivoli Storage FlashCopy Manager is
command.
part of the backup.
Explanation: IBM Tivoli Storage FlashCopy Manager
System action: Processing ends.
uses the displayed command to get the logical volume
User response: Rename the specified virtual machine ID. The command failed.
or change the specified name of the IBM Tivoli Storage
System action: Processing stops.

30 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0519E • FMM0545I

User response: Check the state of the AIX ODM and

FMM0524E The pathname directory path or fully
of the logical volume. Run this command from the AIX
qualified file name was not found in
command line.
any of the current active file systems.
Explanation: The backup process cannot find the
FMM0519E The volume with the serial ID serialid is
specific path from the list of files or directories that is
not assigned to the backup host.
specified when you start the backup operation.
Explanation: IBM Tivoli Storage FlashCopy Manager
System action: Processing ends..
imports the data from the target set volumes into the
backup system. This requires the SAN to assign the User response: Use the OS shell commands to check
volumes to the backup host. the status of this path. Ensure that the underlaying file
system is mounted and try the operation again.
System action: Processing stops.
User response: Make sure the target storage volumes
FMM0539E Either Oracle control file or redo log file
are assigned to the backup host.
is in the same volume group (v1) with
which Oracle datafiles are.
FMM0520W Trying to find the process that has
Explanation: Either Oracle control file or redo log file
locked the ODM ...
is in the same volume group with Oracle datafiles.
Explanation: IBM Tivoli Storage FlashCopy Manager
System action: Processing ends.
checks whether the AIX ODM is locked by other
processes on the host prior to making persistent User response: Make sure you don't have control files
changes. and redo log files in the same volume group with
Oracle datafiles.
System action: Processing continues.
User response: None.
FMM0540E A null logical volume has been detected.
Explanation: A null logical volume was detected.
FMM0521I Waiting the maximum seconds seconds
until the ODM lock is released by System action: Processing ends.
another application.
User response: Verify the target database information
Explanation: IBM Tivoli Storage FlashCopy Manager is specified correctly in the Setup File.
will retry to lock the ODM after the specified time.
System action: Processing continues. FMM0543I Mounting filesystem : fs1.
User response: None. Explanation: Currently attempting to mount the file
system.
FMM0522E The storage system ID could not be System action: None.
found for the volume volume.
User response:
Explanation: IBM Tivoli Storage FlashCopy Manager
was not able to find the storage ID for the specified
FMM0544E Serial number for the device v1 is not
volume.
found.
System action: Processing stops.
Explanation:
User response: Use the GUI or the command line to
System action: Processing ends.
verify that the volume exists.
User response:
FMM0523E The file systems needed for the mount
operation are missing. FMM0545I Trying to find new devices to match the
source device. This process will take
Explanation: IBM Tivoli Storage FlashCopy Manager
some time.......
was not able to find the file systems in the local
repository. Explanation: Currently trying to find a target device
to match with the source device.
System action: Processing stops.
System action: None.
User response: Use the inquire function to verify the
state of the backup to be mounted. User response:

Chapter 2. FMM messages 31

FMM0546I • FMM0554E

User response: Perform one of the following: a) If the

FMM0546I Removing device : parm1
hdisks with the same pvid belong to the same
Explanation: DP for Snapshot Devices will remove the multipath, convert the hdisk device volume group to a
logical devices from the Device Configuration database Subsystem Device Driver vpath device volume group.
(ODM) on the backup system after the backup ended b) If the problem is the result of a corrupt ODM,
and prior to the withdraw of the relationships of the consult the AIX Troubleshooting documentation c) If
volumes. the physical volume involved neither belongs to a
volume group nor it contains file systems to be
System action: None.
imported in the future, then you can clear the pvid by
User response: issuing the aix chdev command with the following
arguments:chdev -l hdisk# -a pv=clear

FMM0547I Configuring the target volume would

cause duplicate physical volume ID : FMM0551W The umount command failed with rc rc1
pvid1. for mount point mntpt1.

Explanation: A different set of target volumes that Explanation: An error occurred while trying to
were previously associated with the same source remove a mount point. Processing continues.
volumes was detected.
System action: Processing continues.
System action: Processing ends.
User response:
User response: Perform one of the following: Delete
the disk on the backup system only: 1. find the disk
FMM552E A backup with the 'backup_id' ID cannot
using the AIX lspv command 2. run smitty and choose
be found.
the following from the menu: devices- fixed disk-
remove a disk- select the disk to be removed 3. press Explanation: No backup with this ID exists.
return Clear the pvid of each physical volume hdisk by
System action: Processing ends.
issuing the aix chdev command with the following
arguments:chdev -1 (hdisk#) -a pv=clear User response: Specify a valid backup ID. Valid
backup IDs can be obtained by the inquire command.
FMM0548E Removing device parm1 failed.
FMM0553E Failed to suspend I/O on a logical
Explanation: DP for Snapshot Devices will remove the
volume device with errno errno for
logical devices from the Device Configuration database
logical volume: lv.
(ODM) on the backup system after the backup ended
and prior to the withdraw of the relationships of the Explanation: An error occurred while trying to
volumes. The rmdev command failed. suspend I/O on a JFS log logical volume device. I/O
on this logical volume will not be suspended while
System action: Processing ends.
establishing FlashCopy backup. This may result in an
User response: Check the specific error message. inconsistent database snapshot during backup.
Consult the AIX system documentation. Check if the However, processing will continue.
device is member of one active volume group. Check
System action: Processing continues.
for proceeding errors.
User response: Please contact AIX support to find out
why the suspend I/O on a logical volume device
FMM0549W Removing the mount point directory
failed.
mntpt1 failed with rc: rc1.
Explanation: An error occurred while trying to
FMM0554E Failed to resume I/O on a logical
remove a mount point. Processing continues.
volume device with errno errno for
System action: Processing continues. logical volume: lv.
User response: Explanation: An error occurred while trying to resume
I/O on a JFS log logical volume device.
FMM0550E The physical volume ID pvid1 is System action: Processing stops..
duplicate on the production machine.
User response: Try running the DP for Snapshot
Explanation: The output of the command lspv shows Devices "resume" command. If the failure persists,
that two logical devices (hdisk/vpath) have the same please contact AIX support to find out why the resume
physical volume id. I/O on a logical volume device failed.
System action: Processing ends.

32 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM555E • FMM0564I

FMM555E Multiple backup IDs were specified in FMM0560E Unsupported file system has been
the input file. You can specify only one detected.
backup ID in the input file.
Explanation: The file system that database allocated is
Explanation: More than one backup ID was specified an unsupported type.
in the input file.
System action: Processing ends.
System action: Processing ends.
User response: Make sure that the mount point exists
User response: Specify just one backup ID in the and the file system is supported.
input file.
FMM0561E The file or directory objname must not be
FMM0556I Flashcopy type is set to NOCOPY. located on the volume group v1.
Removing disk meta data for all target
Explanation: This volume group is not supported by
disks... This backup is NOT valid for a
IBM Tivoli Storage FlashCopy Manager. The file or
FlashCopy restore. Please restore from
directory displayed is located in this volume group.
TSM Server.
System action: Processing ends.
Explanation: Target PVIDs are cleared. This process
removes disk metadata for all target disks. These target User response: Make sure that volume group is not
volumes can now be used as targets for source volumes rootvg.
from multiple databases. However, this backup is not
valid for a FlashCopy restore. You can only restore
from TSM Server. FMM562E No backup ID was found in the input
file. Specify a valid backup ID in the
System action: None. input file.
User response: None. Explanation: No backup ID was specified in the input
file.
FMM0557W Removing the file system on the mount System action: Processing ends.
point mntpt1 failed with rc: rc1.
User response: Specify a valid backup ID in the input
Explanation: An error occurred while trying to file.
remove a file system during the FlashCopy restore.
Processing continues. The restore will repair this
problem. FMM0563E An physical disk for the volume group
v1 was not found.
System action: Processing continues.
Explanation: A physical disk from the specified
User response: None. database volume group was not found in the Device
Configuration database.
FMM0558I Flashcopy type is set to COPY or INCR. System action: Processing ends.
Leaving disk meta data intact for all
target disks... This backup is valid for a User response: Check the specific error message.
FlashCopy restore. Consult the AIX system documentation. Check if this
device is member of one active volume group. Check
Explanation: The target PVIDs are not cleared.This for proceeding errors.
process leaves disk metadata intact for all target disks.
This backup can be used for a FlashCopy restore.
FMM0564I Exporting volume group fnm1 failed.
System action: None.
Explanation: The specified volume group could not be
User response: None. exported after the vary off.
System action: None.
FMM0559E Command lslv failed for the logical
volume v1. User response: Check the error message displayed by
the operating system. Check that the volume group
Explanation: The LVM command lslv failed with the was vary off before the exporting.
specified logical volume.
System action: Processing ends.
User response: Try to run the same command from
the command line and verify that it works. Check that
the file system /tmp contains enough space.

Chapter 2. FMM messages 33

FMM0565I • FMM0575E

FMM0565I Importing volume groups now... FMM571E The vmcli executable file 'vmclipath' does
not exist. The installation seems to be
Explanation: Processing an importing volume group
corrupt.
command.
Explanation: The vmcli component cannot be found.
System action: None.
System action: Processing ends.
User response:
User response: Verify that the vmcli executable file
exists and is in the correct directory. Reinstall the
FMM0566I Newly imported volume group: vg1
product.
Explanation: DP for Snapshot Devices has successfully
imported this new volume group on the backup system
FMM0572E No volume group was found.
after the FlashCopy.
Explanation: The AIX command lsvg failed on the
System action: None.
backup system and the new added volume groups after
User response: the FlashCopy could not be figured out.
System action: Processing ends.
FMM0567E Logical Volume cannot be found for the
User response: Check the operating system error
file fnm1.
issued by lsvg. Consult the AIX documentation.
Explanation: An error has occurred determining the
logical volume of a file in the list of database files.
FMM0573E Volume group vg1 can not be found.
System action: Processing ends.
Explanation: The AIX command lsvg failed on the
User response: Check the specific error message. production system and the source volumes of the
Cosult the AIX system documentation. production database could not be found out.
System action: Processing ends.
FMM0568I Removing volume group fnm1 ....
User response: Check the operating system error
Explanation: Attempting to remove the identified issued by lsvg. Consult the AIX documentation.
volume groups.
System action: None. FMM0574E Quorum of the volume group vg1 must
be off.
User response: None.
Explanation: In a highly-available LVM mirror
environment, DP for Snapshot Devices requires that the
FMM0569I Varied off and exported volume group : quorum of the volume group is set to off. If a mirror is
fnm1 inactive due to a failure, the database should continue
Explanation: The specified volume group was varied working properly.
off and exported successfully. System action: Processing ends.
System action: None. User response: Set the quorum of the volume group
User response: None. off.

FMM0570I Finding the serial numbers ... FMM0575E Logical volume vg1 must have at least 2
copies.
Explanation: DP for Snapshot Devices get as input a
list of database files to be backed up and from them it Explanation: If the parameter for working with LVM
figures out the logical volumes, the volume groups and mirror is active, then DP for Snapshot Devices requires
the serial number of the physical volumes where the that two copy of each logical volume are existing.
production database is residing. System action: Processing ends.
System action: None. User response: Create a copy of each logical volume
User response: None. on separate hardware units. Ensure that you have for
each source volume a target volume for the FlashCopy
in the same hardware unit.

34 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0576E • FMM0584I

driver designed to support the multipath configuration

FMM0576E Logical volume vg1 must have the
environments in the storage system and is used to
parallel or striped scheduling policy.
enhance data availability. DP for Snapshot Devices will
Explanation: DP for Snapshot Devices requires the determine the number of multiple paths queryng the
parallel or striped scheduling policy. With the parallel Device Configuration database (ODM).
scheduling policy, there is no primary or secondary
System action: None.
mirror. All copies in a mirror set are just referred to as
copy, regardless of which one was created first. User response: If you want to use the advantage of
SDD, check the Subsystem Device Driver User's Guide
System action: Processing ends.
for a correct configuration.
User response: Set the scheduling policy of this logical
volume to 'parallel'.
FMM0581E Failure in changing the mount point mp,
return code rc from command chfs.
FMM0577E Logical volume vg1 must have mirror
Explanation: In a high-available LVM mirror
write consistency on.
environment, DP for Snapshot Devices will use the
Explanation: Mirror write consistency ensures data recreatevg command to create the volume groups after
consistency among mirrored copies of a logical volume the FlashCopy on the backup system. Because
during normal I/O processing. If a system or volume recreatevg inserts the prefix ./fs....at the begin of the
group is not shutdown properly, then mwc will identify mount point, DP for Snapshot Devices must remove it
which logical partitions may be inconsistent. DP for calling the command chfs.... to the original names.
Snapshot Devices requires that this capability be set for
System action: None.
the logical volumes of the production database.
User response: Check the specific error message.
System action: Processing ends.
Consult the AIX system documentation. Check for
User response: Set mirror write consistency on. proceeding errors.

FMM0578E None of the mirror copies of the logical FMM0582E The same hdisk vg1 can not be
volume lv resides completely on the associated with two different vpaths
specified hardware unit essid. (serial numbers vg2 and vg3). command
chfs.
Explanation: DP for Snapshot Devices requires that all
the partitions of one mirror set must be residing on Explanation: IBM Tivoli Storage FlashCopy Manager
physical volumes of one hardware unit. has encountered a corrupted configuration in your
system.
System action: Processing ends.
System action: None.
User response: You have to reconfigure the allocation
on the production system. User response: By issuing the command 'lsvpcfg' you
can identify that error. Check the Subsystem Device
Driver User's Guide for a correct configuration.
FMM0579E Some of the partitions of vg1 are stale
on the specified hardware unit identifier.
FMM0583E lsvg command failed.
Explanation: DP for Snapshot Devices checks first all
the logical volumes for stale partitions and issues first Explanation: DP for Snapshot Devices uses the
only a warning if it finds some. The mirror set that is command lsvg to determine the physical and logical
residing in the hardware unit that was chosen for the volume of the volume group. That command has failed.
FlashCopy on this specific run, have to be free from
System action: None.
stale partitions.
User response: Check the specific error message.
System action: Processing ends.
User response: Check the reason why you are having
FMM0584I Recreating the new volume groups....
stale partitions. Synchronize the logical volumes of the
production database. Explanation: In a highly-available LVM mirror
environment, DP for Snapshot Devices will use the
recreatevg command to create the volume groups after
FMM0580I Could not determine the number of
the FlashCopy on the backup system.
paths to target volumes. Using default
value of 1. System action: None.
Explanation: DP for Snapshot Devices supports SDD User response: None.
(Subsystem Device Driver). SDD is a pseudo device

Chapter 2. FMM messages 35

FMM0585E • FMM0599E

FMM0585E The command lvm_queryvg failed. FMM0591I Bringing up the volume groups...
Explanation: DP for Snapshot Devices uses the system Explanation: The new resources are being activated
routine lvm_queryvg to read information of the VGDA after the FlashCopy.
of the volumes.
System action:
System action: None.
User response: None.
User response: Check the specific error message.
Consult the AIX system documentation. Check for
FMM0592I Too many file systems located.
proceeding errors.
Explanation: The number of file systems exceeds the
4096 limit.
FMM0586E The number of new volume groups is
limited parm1. System action: Processing ends.
Explanation: DP for Snapshot Devices can support a User response: Reconfigure the production database.
database with maximum 256 volume groups.
System action: None. FMM0598E Although the pvid pvid is contained in
the descriptor area of the volume group
User response: You have to reconfigure your
vgname, no logical devices (hdisk/vpath)
production database.
has this on the production system.
Explanation: The output of the command lspv shows
FMM0587I Varying on volume group fnm1 failed.
that no physical volume hdisk/vpath exist with this
Explanation: Post to the importvg or recreatevg , DP pvid, although the pvid was found on the descriptor
for Snapshot Devices will vary on the database volume area of the volume group.
group on the backup system. The command varonvg
System action: Processing ends.
has failed.
User response: You very likely have an ODM
System action: None.
corruption for the involved volume group. Check this
User response: Check the specific error message. volume group with the command lsvg -l <vgname>
Consult the AIX system documentation. Check for and lsvg -p <vgname>. Depending on the error, you
proceeding errors. have to take different actions. Consult the AIX
troubleshooting documentation to repair the ODM.
FMM0588E Invalid option found in the Setup File.
FMM0599E Physical volume hdisk is in the
Explanation: The parameter value is invalid.
descriptor area of the volume group
System action: Processing ends. vgname but does not belong to this
volume group.
User response: Correct the value and restart the
processing. Explanation: The output of the command lsvg -p
<vgname> does not show that the hdisk/vpath belong
to this volume group, but its pvid is registried in the
FMM0589I Flushing the buffers to disk... descriptor area of the volume group.
Explanation: Currently synchronizing to force the System action: Processing ends.
buffers to disk.
User response: If the hdisks with the same pvid
System action: None. belong to the same multipath, convert the hdisk device
User response: volume group to a Subsystem Device Driver vpath
device volume group. If you have an ODM corruption,
check the involved volume group with the command
FMM0590I Unmounting the file system mntpt1... lsvg -l <vgname> and lsvg -p <vgname>. Depending
Explanation: Currently attempting to unmount the file on the error, you have to take different actions. Consult
system from the mount point. the AIX troubleshooting documentation to repair the
ODM.
System action: None.
User response:

36 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0600W • FMM0610I

System action: None.

FMM0600W The major number of the volume group
vgname could not be determined. User response: None.
Explanation: The command "getlvodm" used to
determine the major number of the specified volume FMM0605E Error freezing the file system fsname:
group failed. The option -V of the command importvg txtmsg.
will not be used on a FlashCopy restore of this backup.
Explanation: The function FREEZE on this file system
System action: None. failed.
User response: Check for error messages of the System action: Check the specific error of the
command getlvodm. operating system appended at the end of this message.
User response: None.
FMM0601W Major number major already exists on
the production machine. The system
will assign the next available major FMM0606E Error thawing the file system fsname:
number to the volume group vgname. txtmsg.

Explanation: DP for ESS found that the major number Explanation: The function THAW on this file system
of the given volume group is being used by another failed.
device. The importvg command will be issued without System action: Check the specific error of the
the option -V <major number>, then the system will operating system appended at the end of this message.
generate the next available major number automatically.
User response: None.
System action: None.
User response: Check the major numbers on the FMM0607I Freezing filesystem : fs1.
system with the command "ls -al /dev".
Explanation: Currently attempting to freeze the file
system.
FMM0602E Production database does not reside on
a LVM mirror environment. The profile System action: None.
parameter 'profile_param' is not allowed User response:
in an environment without LVM
mirroring.
FMM0608I Thawing filesystem : fs1.
Explanation: The LVM mirroring capability of DP for
ESS is on, but the database logical volumes do not have Explanation: Currently attempting to thaw the file
a mirror copy. system.

System action: None. System action: None.

User response: Set the parameter for LVM mirroring User response:
off or setup your system in an high-available LVM
mirror environment. FMM0609I Performing snaprestore of the source
volume srcvol to the snapshot snapid
FMM0603E Error reading the status information of (LUN lunpath).
the file system fsname: txtmsg. Explanation: The function snaprestore will revert the
Explanation: The system call stat failed. Check the source volume to the specified snapshot name. This
specific error message. In some cases the user will need message will appear for every LUN involved in the
administrator rights to execute that command. restore process. The snap restore is made based on the
volume.
System action: None.
System action: None.
User response: Check the specific error message.
Ensure that the user has enough rights. User response:

FMM0604W The file system fsname is not of type FMM0610I Performing snapshot of the source
jfs2. The freeze/thaw function will be volume srcvol (LUN lunpath).
applied only on file systems of type Explanation: A snapshot will be taken from this
jfs2. volume. This message will appear for every LUN
Explanation: The freeze/thaw function will be applied involved in the snapshot process, however when
only on file systems of type jfs2. several LUNs belong to the same volume, only one
snapshot of this volume is taken.

Chapter 2. FMM messages 37

FMM0611I • FMM0620E

System action: None.

FMM0615E Unable to open file file1.
User response:
Explanation: An error was detected when trying to
open the file. The file may not exist.
FMM0611I The snapshot snapid was generated for
System action: Processing ends.
the source volume srcvol (LUN lunpath).
User response: Make sure the file exists.
Explanation: A snapshot with the name displayed was
taken from this volume. This message will appear for
each LUN involved in the snapshot process, however FMM0616I Performing fctype FlashCopy of source
when several LUNs belong to the same volume, only volume src1 to target volume tgt1
one snapshot of this volume is taken.
Explanation: A FlashCopy from the source volume to
System action: None. the target volume was requested.
User response: System action: None.
User response:
FMM0612E File system fsname thawed automatically
because the specified timeout limit was
FMM617W The locale 'locale' for the host is not
exceeded. Specify the profile parameter
supported by the VCenter server. A
TIMEOUT_FLASH, to increase the
default locale will be used.
timeout limit. The default value of this
parameter is 120 seconds. Explanation: The specified locale is not supported by
the VCenter server.
Explanation: The THAW function on the file system
fsname failed because the file system thawed System action: Processing continues with the default
automatically after the timeout value specified by the locale.
TIMEOUT_FLASH parameter was already exceeded.
User response: Set the locale to setting supported by
System action: Processing stops. the VCenter server.
User response: Increase the timeout value for the
TIMEOUT_FLASH parameter. FMM618E The suspend operation for the virtual
machine with the instance UUID
'instance uuid' failed: 'error'.
FMM0613E File system fsname can not be freezed
because the timeout limit was exceeded. Explanation: The suspend operation failed on the
Specify the profile parameter specified virtual machine.
TIMEOUT_FLASH, to increase the
timeout limit. The default value of this System action: Processing continues.
parameter is 120 seconds. User response: Check the error message.
Explanation: The FREEZE function cannot be applied
to file system fsname because the timeout limit specified FMM0619I Performing FlashCopy withdraw of
by the TIMEOUT_FLASH parameter was already source volume src1 from target volume
exceeded. tgt1
System action: Processing stops. Explanation: A FlashCopy withdraw of the source
User response: Increase the timeout value for the volume from the target volume was requested.
TIMEOUT_FLASH parameter. System action: None.
User response:
FMM614E The process failed to update the
usability state of the snapshot backup.
FMM0620E No target volume is available.
Explanation: IBM Tivoli Storage FlashCopy Manager Terminating......
cannot update the IBM Tivoli Storage FlashCopy
Manager repository. Explanation: No target volume was found.

System action: Processing ends. System action: Processing ends.

User response: User response: Make sure the target volumes reside in
the same Logical Subsystem (LSS) as the source
volumes and that the target volumes are available to
the backup system. Also, make sure the syntax is
correct in the .fct file.

38 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0635E • FMM654E

not limited to) all filesystems and raw volumes on

FMM0635E A required parameter tgtv1 is missing in
them. Make sure all necessary data from the source
the Setup File.
LUNs is backed up, and restart the procedure.
Explanation: A required parameter in the Setup File
System action: System waits for a valid user response.
has not been specified. This may be caused by incorrect
syntax in the Setup File. User response: Please enter "Yes" to continue, or "No"
to abort the restore operation.
System action: Processing ends.
User response: Make sure all the required parameters
FMM0650I A Flashcopy Restore operation has been
are present in the Setup File and that no space exists
requested, with Prompt=No. All data on
between the parameter and the colon(:).
source volumes, including (but not
limited to) filesystems and raw volumes,
FMM0643I Executing system command 'parm1' will be lost. Continuing Flashcopy
Restore operation.
Explanation: IBM Tivoli Storage FlashCopy Manager
is performing the command parm1 and waiting for the Explanation: Flashcopy Restore overwrites any
results from the operating system. existing data on all the source LUNs, including (but not
limited to) all filesystems and raw volumes on them. It
System action: None.
is strongly recommended that this operation be
User response: None. performed with Prompt set to Yes. The user has chosen
to perform this operation with Prompt set to no.

FMM0644E Error on running command: parm1 System action: Restore operation continues.

Explanation: An error was detected while running a User response: None.

system command.
System action: Processing ends. FMM651E The 'prefix' prefix is not contained in the
string 'searchstring' in the input file.
User response: Gather log file information and contact
your IBM service representative. Explanation: A Syntax error occured in the input file.
System action: Processing ends.
FMM0647I User abort; Exiting Flashcopy Restore.
User response: The named prefix cannot be found in
Explanation: The user has chosen to terminate the the string. The prefix is required in the input file.
Flashcopy Restore operation.
System action: Restore processsing is terminated. FMM0652E Invalid license is detected.

User response: Flashcopy Restore overwrites any Explanation: An invalid license was found.
existing data on all the source LUNs, including (but not
System action: Processing ends.
not limited to) all filesystems and raw volumes on
them. Make sure all necessary data from the source User response: Check if there is a mismatch between
LUNs is backed up, and restart the procedure. the executables (for the production system and backup
system) and the license file(agent.lic).
FMM0648I User input was yes; Continuing
Flashcopy Restore. FMM653I The 'operation' request processed
successfully.
Explanation: The user has chosen to continue the
Flashcopy Restore operation. Explanation: This message is for informational
purpose only.
System action: Restore processsing continues.
System action: Processing continues.
User response: None.
User response: No action is required.
FMM0649I You are about to perform a Flashcopy
Restore operation. All data on the FMM654E The following instance UUIDs have not
source volumes, including (but not been found in the datastores that are
limited to) filesystems and raw volumes, included in the backup. They are not
will be lost. Do you want to continue? part of the backup.instance uuids
Please enter Yes or No.
Explanation: The specified instance UUIDs have not
Explanation: Flashcopy Restore overwrites any been found in the datastores that are included in the
existing data on all the source LUNs, including (but not backup. They are not part of the backup.

Chapter 2. FMM messages 39

FMM655E • FMM0675E

System action: Processing continues but the specified

FMM0667E Could not create the trace object.
instance uuid's are not part of the backup.
Explanation: There were some problems creating trace
User response: Specify valid instance UUIDs of virtual
class object.
machines that are listed in the input file.
System action: Processing terminates.
FMM655E The 'prefix' prefix in the input file is not User response: None.
allowed for single disk restore
operations.
FMM0668E Invalid trace flag: v1.
Explanation: A syntax error occured in the input file.
Explanation: Some invalid trace flags are defined in
System action: Processing ends. the setup file.
User response: Add the correct prefix to the input file. System action: Processing terminates.
User response: None.
FMM0656E An error has been detected when
running the TSM Backup Archive Client
FMM0672E Error while querying volume properties
command line interface.
of volume volserial. Please verify that the
Explanation: An error was detected when running the volume specified in the target volumes
TSM Backup Archive Client Client command line file exists.
interface.
Explanation: None.
System action: Processing ends.
System action: Processing stops.
User response: Make sure the TSM Backup Archive
User response: Contact the administrator of the
Client is correctly installed and that the environmental
storage subsystem with the information provided in
variables are set correctly.
this message.

FMM0657E A memory allocation error has occurred.

FMM0673E A Flashcopy background copy is in
Explanation: Enough memory was not available to progress between source volume: source
continue processing. volume and target volume: target volume.
System action: Processing ends. Explanation: A Flashcopy background copy from a
previous operation is not complete for the given source
User response: Ensure that your system has sufficient
and target volumes.
real and virtual memory. Close unnecessary
applications. System action: Command will fail.
User response: Please wait until the background copy
FMM665E There are multiple NFS servers is complete and retry the command.
involved: the NFS server 'nfsserver1' for
the file 'filename' is different from the
FMM0674E A Flashcopy association exists between
previous NFS server 'nfsserver2'.
source volume: source volume and a
Explanation: In NAS environments, the files passed different target volume: target volume.
from the application or database during the fist phase
Explanation: A Flashcopy association exists between
(partition) of the snapshot backup must reside in a
the source volume and a target other than the
single NAS storage system.
designated target volume.
System action: Processing stops.
System action: Restore command will fail.
User response: Move the file systems and files of one
User response: Please withdraw the Flashcopy
single application or database instance to a single NAS
association between the source volume and the target
storage system.
volume and retry the restore command.

FMM0666E Could not open trace file v1.

FMM0675E An unexpected error was encountered.
Explanation: There were some problems opening function name : function-name function :
tracefile. Please make sure you can open the trace file function-desc return code : rc file :
which was specified in the setup file. file-name (line-number)
System action: Processing terminates. Explanation: None.
User response: None. System action: Processing stops.

40 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0676E • FMM0741E

User response: Contact the administrator with the

FMM0728E Symbolic link 'linkname' to 'target' was
information provided in this message.
successfully deleted.
Explanation: Log 'linkname' cannot be a symbolic link.
FMM0676E program-name: cannot open file file-spec:
error. System action: The symbolic link 'linkname' is deleted,
the log is recreated, and processing stops.
Explanation: IBM Tivoli Storage FlashCopy Manager
cannot open the file. User response: Check the location of the new file. To
specify the location of log files, refer to the user's
System action: IBM Tivoli Storage FlashCopy
manual for the 'errorlogname' option, the
Manager cannot complete the requested operation.
'schedlogname' option, and the 'DSM_LOG'
User response: Retry the operation. If the problem environmental variable.
continues, check with your system administrator.
FMM0729E Unable to delete symbolic link 'link'.
FMM0710E Unable to close trace output file
Explanation: Log 'linkname' cannot be a symbolic link.
file-name.
System action: Processing stops.
Explanation: An error occurred during the closing of a
trace output file-name (for example, not enough disk User response: Delete the symbolic link 'linkname'.
space).
System action: Processing continues. FMM0739E Invalid trace keyword - 'keyword'
User response: Check the options.doc file for a Explanation: A TRACEFLAG option in the user
description of possible causes of the error, or see your configuration file or on the command line is incorrect.
system administrator.
System action: Client program did not initialize or
tracing was not enabled in the applet.
FMM0711E Unable to write to trace file tracefile.
User response: Correct the value. See the entry for
Tracing disable d.
TRACEFLAGS in the Trace Facility Guide document for
Explanation: An error occurred when writing to the a list of valid trace flags.
specified tracefile.
System action: Tracing is disabled. Processing FMM0740E Unable to open trace output file
continues. file-name.
User response: Ensure the device that contains the Explanation: A TRACEFILE option in the user
tracefile is available, has sufficient space for the tracefile configuration file or on the command line used a
and the user has write permission to the target directory path and file-name combination to which you
directory. Retry the command. do not have write access.
System action: Client program did not initialize.
FMM0712E Invalid trace file name (name too long).
User response: Change the TRACEFILE value so that
Explanation: A TRACEFILE option in the preferences it is a location to which you have write access.
files used a file name that is too long.
System action: Client program did not initialize. FMM0741E The physical volumes of the volume
group v1 were not found.
User response: Change the file name used as the
TRACEFILE so that it is equal to or less than 255 Explanation: DP for Snapshot Devices will issue the
characters in length. command 'lsvg -M <vgname>' in a LVM mirror
environment to determine on which physical and
logical volumes is residing the production database.
FMM0727E Specifying the trace file 'link' as a
This command failed.
symbolic link is not allowed.
System action: Processing ends.
Explanation: Trace file 'linkname' cannot be a symbolic
link. User response: Check the return code of lsvg. Consult
the AIX system documentation.
System action: The symbolic link 'linkname' is deleted,
the trace file is recreated, and processing stops.
User response: Specify the trace file location with the
'tracefile' option.

Chapter 2. FMM messages 41

FMM0742E • FMM0749I

the backup on an incorrect host - local backup on

FMM0742E Varying off volume group fnm1 failed.
takeover host or remote backup on local host.
Explanation: After the unmount of the database file
System action: Processing ends.
systems, DP for Snapshot Devices will vary off the
database volume groups on the backup system. The User response: Logon with the user root and issue the
command varoffvg has failed. command lsvpcfg. Check if the volume is displayed.
Use the storage-system user interface to find out to
System action: None.
which host this volume is attached. You will be able to
User response: Check the specific error message. restart the FlashBack restore anytime, as long as you
Consult the AIX system documentation. Check for have a valid disk backup on the target volumes.
proceeding errors during the unmount process.
FMM0747E The source volume with serial number
FMM0743I <fn1> VOLUME GROUP : fn2 COPIES : cmd belongs to another volume group.
fn3 SCHED POLICY : fn4 STALE PPs :
Explanation: The specified physical volume was
fn5 MIRROR WRITE CONSISTENCY:
found during the FlashCopy backup as part of the
fn6
database volumes on the production system. Now, on
Explanation: the FlashBack restore, DP for Snapshot Devices found it
as member of another volume group and can not
System action: None.
proceed with the restore.
User response:
System action: Processing ends.
User response: You must remove this volume from
FMM0744I <lvname><copy><pv><serialno><status>
the other volume group if you want to use the
Explanation: Finding the source volumes of the specified FlashCopy backup for the FlashBack restore.
production database in a LVM mirror environment, DP You will be able to restart the FlashBack restore
for Snapshot Devices will display a list of all the logical anytime, as long as you have a valid disk backup on
volumes with the number of copies, the physical the target volumes.
volumes, the serial number and the status. The status is
only displayed for the case of stale.
FMM0748W The logical volume lv on the mount
System action: None. point mp was renamed or newly added.
User response: None. Explanation: DP for Snapshot Devices found a
difference between the names of the logical volumes
which were on the production database at the time of
FMM0745W Logical volume vg1 has vg2 stale FlashCopy backup and the current logical volumes at
partitions. the time of the FlashBack Restore.
Explanation: DP for Snapshot Devices checks first all System action: None.
the logical volumes for stale partitions and issues first
only a warning if it finds some. The mirror set that is User response: DP for Snapshot Devices will ask you
residing in the hardware unit that was chosen for the during the FlashBack Restore if you are sure to
FlashCopy on this specific run, have to be free from continue, before all the file systems and logical volumes
stale partitions. are removed. After that, DP for Snapshot Devices will
only reconstruct the file systems which were backed up
System action: None. with FlahCopy. You have to add manually all the
User response: Check why you are having stale additional system changes that were made after the
partitions. If necessary, synchronize the logical volumes FlashCopy backup.
of the production database.
FMM0749I List of the current file systems on the
FMM0746E The source volume with serial number backed up volume groups ...
cmd is not attached to the production Explanation: Prior the start of the FlashBack restore,
system. DP for Snapshot Devices will display a list of all the
Explanation: The specified physical volume was file systems which are currently on production database
found during the FlashCopy backup as part of the system.
database volumes on the production system. Now, System action: Processing ends.
during the FlashBack Restore, it is no longer found on
the production system. User response: None.
One of the reasons this may occur is if you are in a
remote mirror environment and are trying to restore

42 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0750I • FMM0759E

have to add additional parameter to the commands to

FMM0750I List of file systems which will be
improve the performance of the synchronization.
restored...
Explanation: Prior the start of the FlashBack restore,
FMM0756E Error converting the hdisk device
DP for Snapshot Devices will display a list of all the
volume group vg to a Subsystem Device
file systems which were on production database system
Driver vpath device volume group.
at the time of the FlashCopy backup.
Explanation: On the function FlashCopy backup, DP
System action: Processing ends.
for Snapshot Devices will use the command hd2vp to
User response: None. convert the hdisk device volume group to a Subsystem
Device Driver vpath volume group. This will take effect
after the importvg and prior to the mount of the file
FMM0753W The newly added volume cmd will be
systems on the backup system.
deleted from the database volume group
rc. System action: Processing ends.
Explanation: The reducevg command removes User response: Check the return code and the error
physical volumes from a volume group. DP for message of the hd2vp command. Consult the AIX
Snapshot Devices will call this command during the system documentation.
FlashBack Restore to remove the physical volumes
added to the database volume groups after the
FMM0757W The rmlv command lv ended with return
FlashCopy backup.
code rc.
System action: Processing ends.
Explanation: For the function FlashBack Restore, DP
User response: None. for Snapshot Devices will use the command rmlv to
remove the logical volumes onto which the production
database should be restored. This will take effect after
FMM0754I Logical volume lv was removed during
the unmount and prior to the exportvg and the actual
Flashcopy Restore, because it was newly
FlashCopy.
added since last backup, needs to be
recreated manually. System action: Processing ends.
Explanation: DP for Snapshot Devices found a User response: Check the return code and the error
difference between the names of the logical volumes message of the rmlv command. Consult the AIX system
which were on the production database at the time of documentation. You will be able to restart the
FlashCopy backup and the current logical volumes at FlashBack restore anytime, as long as you have a valid
the time of the FlashBack restore. disk backup on the target volumes.
System action: None.
FMM0758E DP for Snapshot Devices encountered a
User response: DP for Snapshot Devices will ask you
problem when using the FlashCopy
during the FlashBack restore if you are sure to continue
function of the Copy Services.
before all the file systems and logical volumes will be
removed. After that, DP for Snapshot Devices will only Explanation: DP for Snapshot Devices requested for a
reconstruct the file systems which were backed up with set of source/target volume pairs a FlashCopy to be
FlahCopy. You have to add manually all the additional done by the Copy Services. If the request fails within
system changes that were made after the FlashCopy the storage system for one or more pairs with a
backup. non-zero return code, then DP for Snapshot Devices
will provide the return code and then terminate.
FMM0755I The following commands should be run System action: Processing ends.
after the FlashCopy process in
User response: In order to identify which volume(s)
background is finished to synchronize
were the cause of the problem you need to view the
the LVM copies:
Copy Services status log for failures, there you find the
Explanation: IBM Tivoli Storage FlashCopy Manager failing volume(s) along with details about possible
will not automatically synchronize the copies after the causes of the problem.
reconstruction of the LVM mirror. A basic command
will be created and printed out.
FMM0759E The file system fs already has an entry
System action: Processing ends. in the /etc/filesystems.
User response: You have to start the synchronization Explanation: On the backup system after the
of the LVM mirror manually after the FlashCopy FlashCopy, DP for Snapshot Devices found that the
process in background has finished. If necessary you specified file system still exist in the /etc/filesystems.

Chapter 2. FMM messages 43

FMM0760W • FMM0767W

System action: Processing ends. backup on the target volumes.

User response: Normally the command "exportvg"
will remove the corresponding file systems from the FMM0763I Removing copies from the logical
/etc/filesystems. Check for errors during the unmount volumes ...
and withdraw process.
Explanation: On the function FlashBack restore, DP
for Snapshot Devices will use the command rmlvcopy
FMM0760W The reducevg command cmd ended with to remove the copies of the logical volumes residing on
return code rc. the second hardware unit. This will take effect after the
unmount and prior to the exportvg and the actually
Explanation: The reducevg command removes
FlashCopy reverse.
physical volumes from a volume group. DP for
Snapshot Devices will call it 1. on FlashBack restore to System action: Processing ends.
remove the physical volumes added after the
User response: None.
FlashCopy backup. 2. on FlashBack restore with LVM
mirroring to remove the physical volumes which are
residing on the hardware unit that is not yet involved FMM0764I Removing physical volumes from the
in the FlashBack. 3. on FlashCopy backup with LVM volume groups ...
mirroring if the environment variable IMPORTVG is
set, to remove the physical volumes which are residing Explanation: On the function FlashBack restore, after
on the hardware unit that is not yet involved in the the rmlvcopy and prior to the exportvg and the
FlashCopy. actually FlashCopy reverse, DP for Snapshot Devices
will use the command reducevg to remove the physical
System action: Processing ends. volumes residing on the second hardware unit.
User response: Check the return code and the error System action: Processing ends.
message of the reducevg command. Consult the AIX
system documentation. User response: None.

FMM0761W The extendvg command cmd ended with FMM0765I Adding physical volumes to the volume
return code rc. groups ...

Explanation: The extendvg command adds physical Explanation: On the function FlashBack restore, after
volumes to a volume group. DP for Snapshot Devices the FlashCopy reverse and the import of the volume
will call it to add the volumes which are residing on groups, DP for Snapshot Devices will add the physical
the hardware unit that is not yet involved in the volumes residing on the second hardware unit to the
FlashBack to the database volume groups. database volume groups.

System action: Processing ends. System action: Processing ends.

User response: Check the return code and the error User response: None.
message of the extendvg command. Consult the AIX
system documentation. FMM0766I Adding copies to the logical volumes ...
Explanation: On the function FlashBack restore, DP
FMM0762W The mklvcopy command cmd ended for Snapshot Devices will use the command mklvcopy
with return code rc. to add the copies of the logical volumes on the second
Explanation: DP for Snapshot Devices will call the hardware unit. This will take effect after the importvg
command mklvcopy to add a copy of a logical volume and the extendvg.
on the physical volumes residing on the second System action: Processing ends.
hardware unit. This call will only take effect in a LVM
mirroring environment, after the FlashBack restore was User response: None.
initialized. The FlashBack restore and the recovery will
continue, but the second copy of the logical volumes FMM0767W The command cmd ended with return
will be missing. code rc.
System action: Processing ends. Explanation: The execution of the system command
User response: Check the return code and the error ended with the displayed return code.
message of the mklvcopy command. Consult the AIX System action: Processing ends.
system documentation. Check for errors during the
disabling process (unmount, rmfs, rmlv, varyoffvg, User response: Check the return code and the error
exportvg). You will be able to restart the FlashBack message of the specified command. Consult the AIX
restore anytime, as long as you have a valid disk system documentation.

44 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0768E • FMM0776I

FMM0768E Importing the volume group from hdisk FMM0772W The database volume groups do not
logdev failed. contain currently any file system.
Explanation: DP for Snapshot Devices will use the Explanation: This message will appear if running the
command "importvg" on the function FlashCopy function FlashBack restore, none file system was found
backup. This command will be issued on the backup on the original database volume group. Following that,
system after the actually FlashCopy and the run of the DP for Snapshot Devices will display a list of the file
configuration manager(cfgmgr). It takes a volumes system which are residing on the FlashCopy target
from each volume group building up the production volumes. These will be restored by means of FlashBack.
database, reads its VGDA and makes this information
System action:
available to the operating system.
User response: None.
System action: Processing ends.
User response: Check the return code and the error
FMM0773W One or more errors were found
message of the importvg command. Consult the AIX
disabling the production system
system documentation.
resources. However, the FlashBack
restore will continue.
FMM0769E Recreating the volume group from the
Explanation: This message will appear if, when
hdisks hdisks failed.
running the function FlashBack restore, an error occurs
Explanation: DP for Snapshot Devices will use the unmounting the existing file systems and removing the
command "recreatevg" on the function FlashCopy volume groups. However, DP for Snapshot Devices will
backup if the production database is residing on an continue with the FlashBack restore.
high-available LVM mirror environment. This
System action:
command will be issued on the backup system after the
actually FlashCopy and the run of the configuration User response: None.
manager (cfgmgr). The difference to the command
"importvg" is that recreatevg will create the volume
group only with the specified volumes. These are FMM774I The 'diskname' virtual disk on the 'virtual
building up exact the one copy on the hardware unit machine name' virtual machine is
where the FlashCopy was issued. successfully restored to the 'target virtual
machine' virtual machine and is added to
System action: Processing ends. its configuration.
User response: Check the return code and the error Explanation: The specified virtual disk has been
message of the recreatevg command. Consult the AIX successfully restored.
system documentation.
System action: Processing continues.

FMM0770I Removing the logical device logdev with User response: No action is required.
the same PVID pvid in the ODM.
Explanation: There is still another logical device FMM0775E The label of the logical volume lvname is
(hdisk or vpath) in the state defined with the same missing. Set it using chlv -L mountPoint
PVID as one of the source volumes. logicalVolume.

System action: Processing continues. Explanation: IBM Tivoli Storage FlashCopy Manager
requires the label of the logical volume to be set.
User response: None. Otherwise there will be an error importing the volume
groups on the backup system.
FMM0771I Could not mount all the filesystems System action: Processing stops.
originally present.
User response: Set the label of the logical volume
Explanation: This message will appear if running the using: chlv -L mountPoint logicalVolume.
function FlashBack restore, a file system was found that
was added after the FlashCopy backup.
FMM0776I Number of volumes to be processed by
System action: Flashcopy: v1
User response: The user is responsible for create the Explanation: Number of volumes to be processed by
new file system after the FlashCopy reverse, but before Flashcopy.
the recovery, if this file system was already used from
the production database. System action: None.
User response: None.

Chapter 2. FMM messages 45

FMM0777E • FMM0785W

User response: Please see section about the CIM

FMM0777E An unexpected error was encountered
return codes and its description in the manual.
processing a function. function name :
function-name function : function-desc
return code : rc file : file-name FMM0782E A memory allocation error has occurred
(line-number) in file filename, line number linenumber.
Explanation: None. Explanation: Enough memory was not available to
continue processing.
System action: Processing stops.
System action: Processing ends.
User response: Contact the administrator of the
storage subsystem with the information provided in User response: Ensure that your system has sufficient
this message. real and virtual memory. Close unnecessary
applications.
FMM0778E SVC virtual disk v1 is not valid. Please
verify that the volume specified in the FMM0783E The execution of command 'lscfg' failed.
target volumes file exists. Please verify that the command 'tset -I
-Q' is not set in the users environment
Explanation: The specified virtual disk is not found in
files .profile, .login
the list of virtual disks provided by the connected SVC
.dbenv_<hostname>.sh,
cluster.
.dbenv_<hostname>.csh and
System action: Process stops. .sapenv_<hostname>.sh,
.sapenv_<hostname>.csh.
User response: Ensure that of this virtual disk exists
in the SVC. Explanation: If the command 'tset -I -Q' is set in the
users environment files .profile, .dbenv_<hostname>.sh,
and .sapenv_<hostname>.sh, then the command 'lscfg'
FMM0779E The source v1 and target v2 virtual disks
will fail with the output 'Not a terminal' and will not
are in different SVC clusters.
return any configuration. This will cause the IBM Tivoli
Explanation: The SVC's source and target virtual disks Storage FlashCopy Manager script 'hdwmap.sh' to fail.
have to be assigned to the same SVC cluster for
System action: Process stops.
FlashCopy.
User response: Ensure that the command 'tset -I -Q' is
System action: Process stops.
not set in the users environment files .profile,
User response: Ensure that of the source and target .dbenv_<hostname>.sh, and .sapenv_<hostname>.sh .
virtual disks are in the same SVC.
FMM0784I The ONTAP filer version on this
FMM0780E The source v1 and target v2 virtual disks appliance is: n.
are of different size.
Explanation: None.
Explanation: The SVC's source and target virtual disks
System action: Process continues.
have to be of the same size for FlashCopy.
User response: None.
System action: Process stops.
User response: Ensure that of the source and target
FMM0785W The option fractional reserve on volume
virtual disks are in the same SVC.
vol_name was reduced to less than 100
percent.
FMM0781E An error was returned calling an
Explanation: N series extremely recommends that
operation of the Common Interface
when the fractional reserve is set to less than 100
Model(CIM). function name :
percent you actively monitor space consumption and
function-name received msg : function-desc
the rate of change of data in the volume to ensure you
CIM return code: 0xCIM-rc file : file-name
do not run out of space reserved for overwrites. In that
(line-number) If the received message
case, if you run out of overwrite reserve space, writes
contains 'CIM Error', then please collect
to the active file system fail and the host application or
the CIM Agent logs and send them to
operating system might crash.
CIM support.
System action: Process continues.
Explanation: A error occurred calling a CIM operation
of the disk subsystem. User response: Ensure that you monitor the space
consumption. Consult NetApp for tools to monitor
System action: Processing stops.
available space in your volumes.

46 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0786I • FMM0794E

FMM0786I Removing the snapshot snapshot name of FMM0791W Function refreh incremental FlashCopy
source volume source volume (LUN LUN cannot be accomplish because no
path) consistency group found for these
volumes.
Explanation: The removal of the specified snapshot of
the source volume was requested. Explanation: A refresh of the incremental FlashCopy
can only be done when the consistency group and the
System action: Processing continues.
correspondent FlashCopy relation were established
User response: None. previously.
System action: None.
FMM0787E The snap restore for volume volname
User response: None.
with snapshot name snapname would
destroy later snapshots that are required
for other applications or for volume FMM0792E The list of volumes passed contain pairs
clones. which belong to different consistency
groups in the scope of one single
Explanation: N series will delete newer snapshots of a
cluster.
volume when a specific snapshot is used for snap
restore. Explanation: IBM Tivoli Storage FlashCopy Manager
handles for each operation only one consistency group
System action: Process stops.
per cluster at the same time. If the set of volumes in a
User response: Prior a snap restore, ensure that newer backup or restere operation contain pairs that belong to
snapshots are not used in other applications or in different consistency group inside one single cluster,
volume clones. then the process of the operation will be stopped.
System action: Process stopped.
FMM0788W IBM Tivoli Storage FlashCopy Manager
User response: If you added volumes to the
did not find any snapshots for volume
production database or to the target set, ensure that
volname on the N series filer.
they are not in any FlashCopy relation.
Explanation: No snapshots for this volumes in the N
series filer found.
FMM0793W No FlashCopy relationships found in
System action: Process continues. the storage system.

User response: None. Explanation: The copy services server (mostly a CIM
Object Manager) does not have any FlashCopy relation
objects.
FMM0789W IBM Tivoli Storage FlashCopy Manager
did not find any information about the System action: Process may stop.
N series volume volname.
User response: This is not necessarily a message that
Explanation: Trying to get information about this implies the stop of the process.
volume did not return any data.
System action: Process continues. FMM0794E The state status of the consistency group
is bad to achive a valid disk backup.
User response: None.
Explanation: IBM Tivoli Storage FlashCopy Manager
function monitoring will expect that the FlashCopy are
FMM0790E The snapshot name snapname for volume in one of the state Idle_Copied or Copying.
volname was not found in the snapshot
list on the N series filer. System action: Process will stop.
Explanation: Snapshot identified by this name does User response: Verify using the storage GUI the state
not exist. of the FlashCopy. If this state was generated by an user
action, try to start the copy process through the storage
System action: Process stops. GUI, then re-start the IBM Tivoli Storage FlashCopy
User response: None. Manager moniotoring fuction.

Chapter 2. FMM messages 47

FMM0795E • FMM0808E

User response: Check that one of both primary or

FMM0795E Error initializing the connection to the
secondary copy services server and the CIMOM
copy services server.
running on it is up and running.
Explanation: IBM Tivoli Storage FlashCopy Manager
could not initialize the connection to the copy services
FMM0801W The FlashCopy direction in the
server.
consistency group cs_name is switched.
System action: Process will stop. A withdraw will be done prior to
continue.
User response: Check previous error to identify the
exact problem during the initialization. Explanation: The FlashCopy direction of source and
target volumes in the consistency group is switched.
This can be caused through the restore process. A
FMM0796I Trying to connect to primary copy
withdraw will be done prior to continue.
services server 'cs_primary'.
System action: Process will continue.
Explanation: None.
User response: None.
System action: Process will continue.
User response: None.
FMM0802E Neither source volume id nor target
volume id is in the volume list.
FMM0797I Trying to connect to primary 'cs_prim'
Explanation: None.
and/or secondary 'cs_sec' copy services
server. System action: Processing ends.
Explanation: None. User response: None.
System action: Process will continue.
FMM0805E The putenv command failed for path =
User response: None.
v1.
Explanation: None.
FMM0798I The primary copy services server
'cs_prim' is not responding. The System action: Process stops.
following CIM error was reported:
User response: *** NEED A BETTER EXPLANATION
cim_err_msg Working with secondary
***
copy services server 'cs_sec'.
Explanation: None.
FMM0806E Lun ID v1 is not valid.
System action: Process will continue.
Explanation: Length of LUN id must be 8 characters.
User response: None.
System action: Process stops.
User response: Make sure the length of LUN ID is 8.
FMM0799E The primary copy services server
'cs_prim' is not responding. The
following CIM error was reported: FMM0807E The jar file v1 cannot be found.
cim_err_msg
Explanation: None.
Explanation: IBM Tivoli Storage FlashCopy Manager
cannot connect to the primary copy services server. System action: Process stops.

System action: Process will stop. User response: *** NEED BETTER RESPONSE FOR
THIS ***.
User response: Check that the primary copy services
server and the CIMOM on it is up and running.
FMM0808E Operating system command 'command'
failed; rc=rc.
FMM0800E Neither the primary 'cs_prim' nor the
secondary copy services server 'cs_sec' Explanation: None.
are responding. The following CIM System action: Process stops.
error was reported: cim_err_msg
User response: Check the return code from the
Explanation: IBM Tivoli Storage FlashCopy Manager operating system for more information about the
cannot connect either to the primary nor to the failure. Issue the failing command manually to see if
secondary copy services server. the same failure occurs.
System action: Process will stop.

48 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0809E • FMM0841E

System action: The mentioned files will be contained

FMM0809E The primary and secondary copy service
in the backup.
servers are down.
User response: If you do not want these files to be
Explanation: None.
contained in the backup please remove them from the
System action: Process stops. diskgroup. If you want them to be included please add
them to the negative list.
User response: Start at least one of the copy service
servers.
FMM0839E The failure group 'failureG' which has
been specified in the profile is not a
FMM0810E Cannot open the command output file
valid failure group of diskgroup 'diskG'.
v1 for writing.
Explanation: One of the failure groups given in the
Explanation: Can't open this file for writing.
profile is not available in one diskgroup of the ASM
System action: Process stops. instance.

User response: Make sure you have enough space on System action: Processing ends.
your system and write permission to the file.
User response: Please check if the failure groups
specified in the profile exist for each of the diskgroups
FMM0811E The LUN are already in use. your database resides on.

Explanation: None.
FMM0840E Not enough failure groups for
System action: Process stops. redundancy type 'redType' in diskgroup
User response: Release LUN in order to reuse them. 'diskGroup'. 'foundFG' have been found
but 'neededFG' are needed for this
redundancy type. Please make sure that
FMM0812I The backup DB2 UDB preview the currently selected DEVICE_CLASS
command indicates there are sufficient contains enough failure groups for a
resources for a backup operation. consistent flashcopy and ensure that
Explanation: None. they are online.

System action: None. Explanation: There are not enough online failure
groups for the redundancy type of the diskgroup on
User response: None. the current storage device. The backup would not be
restorable.
FMM0836E Error while invoking the diskmapper. System action: Processing ends.
Explanation: Invokation of diskmapper failed. User response: Please make sure that the currently
System action: Processing ends. selected DEVICE_CLASS contains enough failure
groups for a consistent flashcopy and ensure that they
User response: Contact the administrator of the are online.
storage subsystem with the information provided in
this message.
FMM0841E Not all disks reside on the same cluster.
Disks were found on the cluster with id:
FMM0837E The path 'v1' is not a character device. 'first cluster id' and on the cluster with id
'second cluster id'.
Explanation: The path queried from the ASM instance
is not a valid character device. Explanation: The disks of the diskgroups needed for
the flashcopy do not reside on one storage device.
System action: Processing ends.
System action: Processing ends.
User response: Check the setup of you ASM instance.
User response: If you specified failure groups in the
profile ensure that the disks they are located on reside
FMM0838W The following files have been found in
on the same storage device. If you did not specify any
the diskgroup allthough they do not
ensure that all diskgroups needed for the flashcopy
belong to the database and are not
reside on the same storage device.
contained in the negative list: 'files'.
Explanation: Additional files have been found which
do not belong to the database and which are not
contained in the negative list.

Chapter 2. FMM messages 49

FMM0842E • FMM0849E

User response: Install SDDPCM or use MPIO only.

FMM0842E The ASM diskgroup 'diskGroup' could
not be dropped but is still available in
the ASM instance. Restore will be FMM0847E Error occured while checking the
stopped. 'db2nodes.cfg' on the production system
and on the clone system. The
Explanation: The specified diskgroup could not be
'db2nodes.cfg' on the production system
dropped but it is still available in the ASM instance. A
contains production system entries entries,
restore could lead to an inconsistent state of the
whereas the 'db2nodes.cfg' on the clone
diskgroup.
system contains clone system entries
System action: Processing ends. entries.
User response: Check the state of the specified Explanation: The DB2 partition configuration file
diskgroup and try to drop it manually. (db2nodes.cfg) on the production system has a different
number of partition configuration entries than its
counterpart on the clone system.
FMM0843E The ASM diskgroup 'diskGroup' could
not be unmounted and is still mounted System action: Processing ends.
in the ASM instance. Unmount will be
User response: Verify the number of partition
stopped.
configuration entries of the DB2 partition configuration
Explanation: The specified diskgroup could not be file (db2nodes.cfg) on the production system as well as
unmounted and is still mounted in the ASM instance. on the clone system. The number of entries within each
Continuing with the unmount operation could lead to of these files have to have identical.
an inconsistent state of the diskgroup.
System action: Processing ends. FMM0848E Error occured while checking the
'db2nodes.cfg' on the production system
User response: Check the state of the specified
and on the clone system. The database
diskgroup and try to unmount it manually.
partition partition number configured on
the production system is not configured
FMM0844E No target volume is available for serial on the clone system.
'serial'.
Explanation: The DB2 partition configuration file
Explanation: No target volume was found for the (db2nodes.cfg) on the production system has a partition
specified serial. configured which is not configured in the DB2 partition
configuration file (db2nodes.cfg) on the clone system.
System action: Processing ends.
System action: Processing ends.
User response: Ensure your backup system is in a
consistent state and that mapping new volumes to the User response: Verify that all partitions configured in
backup system works properly. the DB2 partition configuration file (db2nodes.cfg) on
the production system are configured denoted by the
same partition number on the clone system as well.
FMM0845E The volume manager of your profile is
not set to ASM, the found value is
'serial'. Ensure that you have set the right FMM0849E Error occured while checking the
volume manager in your profile. 'db2nodes.cfg' on the production system
and on the clone system. The hostname
Explanation: The value for volume manager in the 'host name' where partition partition
profile is wrong. number resides is contained in the
System action: Processing ends. 'db2nodes.cfg' on the production system
as well as on the clone system. Either
User response: Set the volume mangager in the profile the setup of the 'db2nodes.cfg' file on
to ASM. the clone system is wrong or the clone
system was configured on the same host
FMM0846E You have SDD installed on your system, as the production system.
but SDD is currently not supported by Explanation: The DB2 partition configuration file
this product when using Oracle ASM. (db2nodes.cfg) on the production system contains at
Explanation: The value for volume manager in the least for the named partition the same host entry like
profile is wrong. SDD is not supported for ASM, only its counterpart on the clone system.
SDDPCM and MPIO are supported for ASM. System action: Processing ends.
System action: Processing ends. User response: Verify that the DB2 partition
configuration file (db2nodes.cfg) on the clone system is

50 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM0850I • FMM0855E

valid. Further ensure, that the mount agent (process

FMM0853E During the mount operation IBM Tivoli
credentials: acsgen -D -M) is running on the clone
Storage FlashCopy Manager identified
system, which has to be a different host than the
that the following source volumes are
production system.
visible on the backup or cloning system
'host name'. This can be caused by
FMM0850I To synchronize the volume groups that misconfiguration in the storage system
have stale partitions you can use the or by misconfiguring the IBM Tivoli
following commands: Storage FlashCopy Manager backup or
cloning system to the same host as the
Explanation: IBM Tivoli Storage FlashCopy Manager production system. List of visible source
does not automatically synchronize the copies after the volumes: source volumes
reconstruction of the LVM mirror during a FlashCopy
restore. A basic command will be created and printed Explanation: The IBM System Storage DS8000 does
out. only support to have one incremetal FlashCopy relation
from a source to a target.
System action: Processing ends.
System action: Processing stops.
User response: You have to start the synchronization
of the LVM mirror manually for example after a User response: Use a different value for profile
FlashCopy restore when the background copy process parameter FLASHCOPY_TYPE (COPY or NOCOPY) or
in the storage system has finished. If necessary you reuse the existing incremental relations by using the
have to add or change parameters to the commands to same device class and target set for the restart of the
improve the performance of the synchronization. backup operation.

FMM0851E The copyservices timeout value of FMM0854E During the mount operation IBM Tivoli
fsname minutes was reaced while Storage FlashCopy Manager identified
waiting for an answer of the that the following target volumes are
copyservices CIM agent. Specify not visible on the backup or cloning
increase the value of the profile system 'host name'. List of missing target
parameter COPYSERVICES_TIMEOUT volumes: target volumes
in the DEVICE_CLASS section of the
Explanation: The IBM System Storage DS8000 does
profile, to increase the timeout limit.
only support to have one incremetal FlashCopy relation
The default value of this parameter is 6
from a source to a target.
minutes.
System action: Processing stops.
Explanation: The communication with the
copyservices CIM agent terminated after the timeout User response: Use a different value for profile
value specified by the COPYSERVICES_TIMEOUT parameter FLASHCOPY_TYPE (COPY or NOCOPY) or
parameter was already exceeded. reuse the existing incremental relations by using the
same device class and target set for the restart of the
System action: Processing stops.
backup operation.
User response: Increase the timeout value for the
COPYSERVICES_TIMEOUT parameter.
FMM0855E During the mount operation IBM Tivoli
Storage FlashCopy Manager identified
FMM0852E It is not allowed to establish a second that the following target volumes are
incremental FlashCopy relation from a not visible on the ESX host 'host name'.
source volume source volume to a target List of missing target volumes: target
volume target volume while another volumes Either the volumes could not be
incremetal FlashCopy relation from the assigned to the host correctly or you
same source volume to a different target used PRE_ASSIGNED_VOLUMES for
volume already exists. the TARGET_SETS parameter in your
Device Class section and the target
Explanation: The IBM System Storage® DS8000® does volumes are not assigned to this ESX
only support to have one incremetal FlashCopy relation host.
from a source to a target.
Explanation:
System action: Processing stops.
System action: Processing stops.
User response: Use a different value for profile
parameter FLASHCOPY_TYPE (COPY or NOCOPY) or User response: Check the error log for detailed
reuse the existing incremental relations by using the information.
same device class and target set for the restart of the
backup operation.

Chapter 2. FMM messages 51

FMM0856E • FMM1008E

FMM0856E The datastore 'datastore name' cannot be FMM1003W Please set redolog_copies to a number
attached to the ESX host: 'host name', the between min_copies and max_copies a.
datastore is already attached to another Now it is set to act_copies.
ESX host. You must detach the data
Explanation: Data Protection for SAP currently
store that is currently attached to the
supports 1 to 9 copies of offline (redo) log files.
ESX host and try the task again.
System action:
Explanation:
User response: Adapt the REDOLOG_COPIES settings
System action: Processing stops.
in the Data Protection for SAP profile.
User response: Check the error log for detailed
information.
FMM1004W You should specify the
BACKUPIDPREFIX before the
FMM0857E The virtual disks of the source virtual TRACEFILE statement. So that the
machine 'source vm name' cannot be BACKUPIDPREFIX can be used in the
attached because a disk is already tracefilename.
attached to a target virtual machine.
Explanation: The BACKUPIDPREFIX is used to build
Detach all virtual disks of the source
the Name of the tracefile. Therefore,
virtual machine and try the attach task
BACKUPIDPREFIX must be specified before the
again.
TRACEFILE statement.
Explanation: Because a virtual disk is already attached
System action:
to the target virtual machine, the virtual disks of the
source virtual machine cannot be attached. User response: Define a 6–character
BACKUPIDPREFIX in the Data Protection for SAP
System action: Processing stops.
profile (for example, SAP___, FMM___)
User response: On the target virtual machine, detach
all virtual disks. Try to attach the virtual disks from the
FMM1006E The SERVERNAME must be less than
source virtual machine to the target virtual machine
max_char characters.
again.
Explanation: You have used a SERVERNAME with
more than max_char characters.
FMM1000E syntax error in line line : 'statement'
System action:
Explanation: The statement statement in the Data
Protection for SAP profile is unknown or incorrect. User response: Use a shorter SERVERNAME.
System action:
FMM1007E The NODENAME must be less than
User response: Correct the error and try again.
max_char characters.
Explanation: You have used a NODENAME with
FMM1001E syntax error in file 'file name'. Exiting
more than max_char characters.
program.
System action:
Explanation: A syntax error has been detected in the
file file name and the action has been halted. User response: Use a shorter NODENAME.
System action:
FMM1008E The MANAGEMENTCLASSNAME
User response: Correct the error(s) in the file file name
must be less than max_char characters.
and try again.
Explanation: You have used a
MANAGEMENTCLASSNAME with more than
FMM1002E BACKUPIDPREFIX must be
max_char characters.
number_of_characters characters !
System action:
Explanation: The length of BACKUPIDPREFIX must
be number_of_characters characters. User response: Use a shorter
MANAGEMENTCLASSNAME.
System action:
User response: Enter a BACKUPIDPREFIX with the
required length (for example, SAP___, FMM___).

52 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1009W • FMM1022E

FMM1009W Please set MULTIPLEX to a number FMM1015E Operation function completed with error.
between 1 and max_multiplex. Now it is
Explanation: This information message in the
set to act_multiplex.
summary confirms that a requested operation failed.
Explanation: You have set multiplexing to an
System action: The operation failed.
unsupported number. Data Protection for SAP now
uses act_multiplex. User response: Check the summary log and the
detailed log used by the failed operation in order to
System action:
identify the failure.
User response: Set multiplexing to a number between
1 and max_multiplex.
FMM1016W The tracefilename 'file name' could not be
opened for writing!
FMM1011W The sortfilename 'sortfile_filename' should
Explanation: The trace file could not be opened for
be absolute!
writing.
Explanation: None.
System action:
System action:
User response: Ensure that you have specified a
User response: Specify an absolute file name, for correct path for the trace file.
example /oracle/C21/dbs/sortfile.
FMM1017E The server server is already defined.
FMM1012E Configfile not found or permission Please use another name or specify
denied: 'configuration_filename'. TCP_ADDRESS!
Explanation: Data Protection for SAP is unable to read Explanation: The named server was already defined
the file configuration_filename. in the profile. Server stanzas with identical names are
not allowed unless the keyword TCP_ADDRESS is
System action:
defined in one of them.
User response: This error could have various reasons,
System action:
try the following: 1. Check the path of the
configuration file. The path must be specified in the User response: Update the profile accordingly and try
profile (parameter CONFIG_FILE). 2. Make sure that again.
the file access permissions are set correctly.
FMM1019E Failed to respond to a message received
FMM1013E Profile not found or permission denied: from XINT.
'profile_filename'.
Explanation: This messages indicates an internal error.
Explanation: Data Protection for SAP is unable to
System action:
open the profile profile_filename.
User response: Contact IBM Support.
System action:
User response: (Oracle) Ensure that the SAP backup
FMM1021E component_name terminates the
profile init<SID>.sap contains a valid entry util_par_file
connection due to a previous error.
for the Data Protection for SAP profile. (DB2) Ensure
that the vendor environment file contains a valid entry Explanation: A serious error has occurred which
XINT_PROFILE. Furthermore, this file must be readable caused a shutdown of the communication channel
by Data Protection for SAP. between the component_name process and this
application.
FMM1014I Operation function was completed System action:
successfully.
User response: Look for previous error messages to
Explanation: This information message in the detect the root cause of the problem.
summary log indicates that the requested operation
completed.
FMM1022E component_name terminates the
System action: The operation was completed. connection due to a previous error.
User response: No action is required. Explanation: See message FMM1021E.
System action:
User response: See message FMM1021E.

Chapter 2. FMM messages 53

FMM1023W • FMM1030E

FMM1023W Could not establish connection to log FMM1027E The mount operation failed. Although
server log server name. an unmount operation can clean up the
backup system, in some cases this is not
Explanation: In the Data Protection for SAP profile,
possible and the cleanup must be
log server log server name is specified (keyword
performed manually. In this case, the
LOG_SERVER). However, a connection to the server
unmount operation should be started
named could not be established. No log records are
after cleanup in order to start another
sent to the log server.
mount operation.
System action:
Explanation: The mount operation failed. Although an
User response: v Check that the server name defined unmount operation can clean up the backup system, in
with keyword LOG_SERVER is spelled correctly in the some cases this is not possible and the cleanup must be
Data Protection for SAP profile. v Make sure there is a performed manually. In this case, the unmount
SERVER section in the profile for the log server defined operation should be started after cleanup in order to
with keyword LOG_SERVER. v Check the start another mount operation.
corresponding SERVER section and correct any setup
System action: Processing ends.
problems. v Make sure that the log server named is
available. User response: To cleanup your backup system, try to
unmount the backup using tsm4acs. If the unmount
operation does not succeed, clean up your backup
FMM1024E The file filename occurs twice in the
system manually and use tsm4acs again to unmount
<infile>
the backup.
Explanation: The named file name occurs multiple
times in the infile which is a violation of the interface
FMM1029W Device 'device' could not be opened.
specification.
Received error message from the
System action: operating system: 'error_message'. This
device might cause the current
User response: Check the logs for further information. FlashCopy Manager operation to fail.
If the problem cannot be resolved contact your IBM
support personnel. Explanation: The specified device could not be
opened.

FMM1025E You must use consistency groups when System action: Processing continues.
using ASM. Set the profile parameter
User response: Check the device for errors.
'profile param' accordingly.
Explanation: The profile specified that consistency
FMM1030E The operating system refused a request
groups should not be used. However, ASM requires the
for memory allocation.
use of consistency groups.
Explanation: IBM Tivoli Storage FlashCopy Manager
System action: Processing ends.
requires access to memory in order to store information
User response: Update your profile accordingly. as processing proceeds. In this case, more memory was
requested than the operating system would allocate.
Possible reasons include:
FMM1026E Writable snapshots must be used when
running in an LVM mirroring v The system is low on memory.
environment. Update the profile v The process in which the program runs has exceeded
parameter 'profile param' accordingly. the maximum memory that it is allowed to allocate.
Explanation: The profile specified that writable v Some other error condition occurred that caused the
snapshots should not be used. However, writable program to think it is out of memory.
snapshots must be used in LVM mirroring System action: IBM Tivoli Storage FlashCopy
environments. Manager cannot complete the requested operation.
System action: Processing ends. User response: Close all unneeded applications and
User response: Update your profile accordingly. try the operation again. If the operation still fails, try
dividing the task into several smaller units.
For UNIX systems that support resource limits, check
to see b if the memory resource limit is too low by
entering the following command: ulimit -a
Based on the resulting data, you can ask the UNIX
system root user to increase resource limits so that it

54 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1031I • FMM1044E

will override the current default. The UNIX system root

FMM1040E An exception occured in the operating
user has the authority to increase resource limits.
system adapter component, exception
text: extext.
FMM1031I The tape backup received this ID:
Explanation: An exception occured in the operating
'tape_backup_id'.
system adapter component.
Explanation: The tape backup received the specified
System action: Processing ends.
ID. The backup is available for restore from tape with
this ID as soon as the tape backup completed User response: Contact IBM support.
successfully.
System action: Processing continues. FMM1041E Failed to identify the default DB2
instance of user DB2 instance owner.
User response: No action required.
Please set the DB2 environment variable
DB2INSTANCE correctly.
FMM1032E The nodes of PARTITION_GROUP
Explanation: The default DB2 instance could not be
'partition_group_name' are associated with
identified.
multiple device classes: 'first_device_class',
'second_device_class' System action: Processing ends.
Explanation: Multiple device classes are used with the User response: The environment variable
same partition group. Only one device class can be DB2INSTANCE has to be set to a valid value.
used for all nodes that belong to one partition group.
System action: Processing ends. FMM1042E The entry in the FLASH_DIR_LIST file
is not a valid file or directory: entry.
User response: Use only one device class for the
specified partition group in the profile. Explanation: It is also possible to flash or clone non
database related files or directories. IBM Tivoli Storage
FlashCopy Manager checks whether the files or
FMM1033W The backup 'backup_id' is not expired
directories specified in the FLASH_DIR_LIST exist prior
because it is still valid in the repository.
the flash or cloning operation is started.
You can either manually delete this
backup or set the parameter System action: Processing ends.
MAX_VERSIONS to ADAPTIVE. Note
User response: Verify the reported invalid entry in the
that this parameter setting turns off
FLASH_DIR_LIST file and revise the entry accordingly.
snapshot expiration.
Explanation: The specified backup is still valid and
FMM1043E The environment is set up for the wrong
cannot be expired.
database instance: 'wrong instance'.
System action: Processing ends. Expected instance 'expected instance'.
User response: Manually delete the specified backup Explanation: The name of the instance returned by the
or set the parameter MAX_VERSIONS to ADAPTIVE. dbms does not match the expected instance name. The
Note that this parameter setting turns off snapshot expected instance name is taken either from the
expiration. environment variable ORACLE_SID or can be
overidden with the command line option '-d
<database_name>'.
FMM1039E Aborting backup. Another backup with
ID 'backup_id' is already mounted on System action: Processing ends.
backup server: 'host'.
User response: Make sure the environment variable
Explanation: After the backup completes, a mount ORACLE_SID is set correctly or specify the instance
operation is required to verify that it is a valid backup. name with the command line option '-d
Another backup with the same mountpoints is already <database_name>'.
mounted on the same backup server. As a result, the
mount operation is not attempted and the backup ends
FMM1044E The section CLONING is missing from
to prevent it from failing.
the profile.
System action: Processing ends.
Explanation: To perform any of the cloning realated
User response: You can either unmount the specified functions the section CLONING must be added to the
backup from the specified backup server, or if an IBM Tivoli Storage FlashCopy Manager profile.
automated tape backup is running, wait until it
System action: Processing ends.
completes.

Chapter 2. FMM messages 55

FMM1045E • FMM1053E

User response: Add the section CLONING to the IBM 'USE_FOR_CLONING' argument of the
Tivoli Storage FlashCopy Manager profile. DEVICE_CLASS parameter in the CLONING section of
your profile.
FMM1045E The parameter TARGET_SETS
VOLUMES_DIR must not be used for FMM1050E The mandatory argument argument as
cloning operations. part of the device class parameter device
class does not exist.
Explanation: TBD_AU
Explanation: For some operations, e.g. cloning, a
System action: Processing ends.
dedicated device class section must be specified in the
User response: TBD_AU IBM Tivoli Storage FlashCopy Manager profile. This is
done by attaching a special mandatory argument string
to the device class parameter.
FMM1046E FlashCopy Cloning is not supported
with FLASHCOPY_TYPE NOCOPY. System action: Processing ends.
Please specify COPY or INCR instead.
User response: Add the mandatory argument to the
Explanation: TBD_AU favoured device class section parameter.

System action: Processing ends.

FMM1051E The keyword 'use_for_cloning_keyword' is
User response: TBD_AU needed for the keyword
TARGET_NAMING in the device class
FMM1047E Expected keyword 'expected keyword' but 'device class' because this device class is
found 'wrong keyword'. used for cloning.

Explanation: During IBM Tivoli Storage FlashCopy Explanation: The keyword TARGET_NAMING
Manager profile parsing a wrong keyword was found requires the specified keyword if the device class is
whereas another keyword was expected. used for cloning.

System action: Processing ends. System action: Processing ends.

User response: Check the IBM Tivoli Storage User response: Specify the specified keyword for
FlashCopy Manager profile section containing the TARGET_NAMING.
wrong keyword and adjust it accordingly.
FMM1052E The parameter TARGET_NAMING of
FMM1048E Device section 'device section' can not be the device class 'device class' is not
used for cloning. Either add configured for cloning of the database
'USE_FOR_CLONING <SID>' to reserve instance 'instance'.
this device class for cloning operations Explanation: To be able to use a dedicated device
or choose another device class. class for cloning operations it has to have setup for that
Explanation: The referred device class cannot be used special type of operations. To mark it accordingly, the
for cloning operations. device class argument 'USE_FOR_CLONING' followed
by the name (or SID) of the database instance to be
System action: Processing ends. cloned has to have attached to the device class profile
User response: A possible solution is to either add parameter TARGET_NAMING.
'USE_FOR_CLONING <SID>' to reserve this device System action: Processing ends.
class for cloning operations or to choose another device
class instead. User response: Update the favoured device class
parameter in the IBM Tivoli Storage FlashCopy
Manager profile.
FMM1049E No DEVICE_CLASS found that can be
used for the current FlashCopy Cloning
operation with the clone database name FMM1053E Failed to identify the default DB2
specified with the command line option instance of user 'user name'. The
-C <Clone DBname>. environment variable DB2INSTANCE is
missing.
Explanation: No device class section in the IBM Tivoli
Storage FlashCopy Manager profile could be found Explanation: The default DB2 instance could not be
which is eligible for cloning operations. detected due to the required environment variable
DB2INSTANCE is not set.
System action: Processing ends.
System action: Processing ends.
User response: Check the value of the

56 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1054E • FMM1063E

User response: Set the DB2 environment variable

FMM1059E Recovery of the DB2 database 'database
DB2INSTANCE accordingly.
alias' failed.
Explanation: The database rollforward recovery failed.
FMM1054E Failed to attach to the DB2 instance
'instance'. System action: Processing ends.
Explanation: The process was unable to attach to the User response: Check the application logs as well as
specified DB2 instance. the DB2 diag log (db2diag.log) for further details.
System action: Processing ends.
FMM1060E Failed to set the DB2 database
User response: Check the application logs as well as
configuration for database 'database alias'.
the DB2 diag log (db2diag.log) for further details. If the
issue could not be resolved please contact your DB2 Explanation: The process was unable to set the DB2
administrator. database configuration.
System action: Processing ends.
FMM1055E Failed to get the DB2 database manager
User response: Check the application logs as well as
configuration.
the DB2 diag log (db2diag.log) for further details. If the
Explanation: The process was unable to get the DB2 issue could not be resolved please contact your DB2
database manager (instance) configuration. administrator.
System action: Processing ends.
FMM1061E Failed to get the DB2 database
User response: Check the application logs as well as
configuration for database 'database alias'.
the DB2 diag log (db2diag.log) for further details. If the
issue could not be resolved please contact your DB2 Explanation: The process was unable to get the DB2
administrator. database configuration.
System action: Processing ends.
FMM1056E Failed to detach from the DB2 instance
User response: Check the application logs as well as
'instance'.
the DB2 diag log (db2diag.log) for further details. If the
Explanation: The process was unable to detach from issue could not be resolved please contact your DB2
the specified DB2 instance. administrator.
System action: Processing ends.
FMM1062E Failed to mount the database on host
User response: Check the application logs as well as
'hostname'. This is the output of the
the DB2 diag log (db2diag.log) for further details. If the
failed command:output
issue could not be resolved please contact your DB2
administrator. Explanation: The process was unable to mount the
database instance.
FMM1057E Failed to query the DB2 client settings. System action: Processing ends.
Explanation: The process was unable to query the User response: Examine the output of the failed
DB2 client settings. command to get further details about the root cause of
this failure.
System action: Processing ends.
User response: Check the application logs as well as
FMM1063E Failed to identify the log path for
the DB2 diag log (db2diag.log) for further details. If the
partition partition number.
issue could not be resolved please contact your DB2
administrator. Explanation: The process was unable to detect the log
path for a dedicated database partition.
FMM1058E Failed to set the DB2 client parameters. System action: Processing ends.
Explanation: The process was unable to set the DB2 User response: Check the application logs as well as
parameters. the DB2 diag log (db2diag.log) for further details. If the
issue could not be resolved please contact your DB2
System action: Processing ends.
administrator.
User response: Check the application logs as well as
the DB2 diag log (db2diag.log) for further details. If the
issue could not be resolved please contact your DB2
administrator.

Chapter 2. FMM messages 57

FMM1064E • FMM1072E

FMM1064E Failed to identify the current working FMM1069E The clone instance on the clone system
directory. is not running.
Explanation: The process was unable to detect the Explanation: Actually, the clone instance on the clone
current working directory. An indication for that issue system is not running. Prior another operation can be
is that read or search permission was denied for a started the clone instance needs to be started.
component of the directory name.
System action: Processing ends.
System action: Processing ends.
User response: Start the clone instance.
User response: Check the application logs as well as
the access rights and permissions of the working
FMM1070E Due to a mount agent is already
directory.
registered on backup system 'backup
system' additional mount agents have to
FMM1065E Failed to change working directory to have registered using different device
'directory' Error: error number: error text. classes.
Explanation: The process was unable to change the Explanation: On the same backup system multiple
current working directory. Indicators for that issue are mount agents can only run on that sytem
that the search access is denied for the named directory, simultaneously if they are supporting different device
that the named directory does not exist or that the classes.
named directory is not a directory.
System action: Processing ends.
System action: Processing ends.
User response: Specify a not already used device class
User response: Check the application logs as well as using the '-s <device class>' option when starting the
the access rights and permissions of the new working mount agent on the backup system.
directory and whether the directory does exist.
FMM1071E A mount agent is already registered on
FMM1066E Failed to create symbolic link from backup system 'backup system' using the
'directory/new instance' to 'instance' Error: device class 'device class'. Additional
error number: error text. mount agents have to have registered
using different device classes.
Explanation: The process was unable to create a
symbolic link to the specified location. Indicators for Explanation: On the same backup system multiple
that issue are that an object of that name already exists, mount agents can only run on that sytem
that insufficient access rights and privileges prevent the simultaneously if they are supporting different device
creation of the link or there might be no free space left classes.
on the file system containing the directory.
System action: Processing ends.
System action: Processing ends.
User response: Specify a not already used device class
User response: Check the application logs as well as using the '-s <device class>' option when starting the
the access rights, privileges and free space of the file mount agent on the backup system.
system where the link is to be placed.
FMM1072E Due to another mount agent is already
FMM1067E Entry in the storage path file 'file' is not registered on backup system 'backup
a valid file or directory: 'directory'. system' using device class 'device class'
and node(s) 'list of nodes' additional
Explanation: TBD_AU
mount agents on host 'backup system'
System action: Processing ends. have to have registered using different
nodes instead of 'list of nodes'.
User response: TBD_AU
Explanation: Multiple mount agents on the same
backup system can run simultaneously only if they are
FMM1068E The clone instance on the clone system supporting different device classes. Multiple mount
is running. agents on different backup systems using the same
Explanation: Actually, the clone instance on the clone device class can run simultaneously only if they are
system is running. Prior another operation can be supporting different nodes.
started the clone instance needs to be stopped. System action: Processing ends.
System action: Processing ends. User response: Specify a not already used device
User response: Stop the clone instance. class, whereas all participating backup system have to

58 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1073E • FMM1081E

have considered, using the '-s <device class>' option User response: Please delete the FlashCopy backup
when starting the mount agent on the backup system. first.
If the same device class should be used on different
backup systems specify the nodes of the backup system
FMM1077E The target set 'target set' is used for a
using the the '-N <comma separated list of nodes>'
clone with ID 'backup ID'. It cannot be
option when starting the mount agent on the backup
used as target set for backup.
system.
Explanation: Target sets used for clones are not
eligible for FlashCopy backups.
FMM1073E The clone database name database name
commandline specified with the command System action: Processing ends.
line option -C does not match with the
database names database name User response: Please delete the clone first.
cloningsection specified in the
DEVICE_CLASS parameter of the FMM1078E The operation name cannot be started
CLONING section. due to the FlashCopy clone(s) 'target set'
Explanation: The database names specified with the is/are still copying data in the storage
command option -C and with one of the system from source to target.
DEVICE_CLASS profile parameters have to have Explanation: As long as a background copy process is
identical. running no other operations using the same target sets
System action: Processing ends. can be started.

User response: Correct either of the database names. System action: Processing ends.
User response: Either wait until the background copy
FMM1074E A FlashCopy clone was requested for in the storage system has finished or delete the clone(s)
clone database database name and device immediately and restart the operation.
class device class but the parameter
CLONE_DATABASE YES is not FMM1079E The data container 'container ID' is
specified in this device class section. already subject of the operation.
Explanation: For cloning operations the IBM Tivoli Explanation: This error is not expected.
Storage FlashCopy Manager profile parameter
CLONE_DATABASE set to YES has to have specified in System action: Processing ends.
the corresponding device class section. User response: Collect all IBM Tivoli Storage
System action: Processing ends. FlashCopy Manager logs and traces (from production
and backup system) and send them to IBM Tivoli
User response: Please use a device class that has support.
specified the parameter CLONE_DATABASE YES.

FMM1080E The database to be cloned has to have

FMM1075E A FlashCopy backup was requested for specified, because multiple databases
device class device class but the have been found within this instance.
parameter CLONE_DATABASE YES is
specified in this device class. Explanation: If multiple database instances found on
one system, the one to be cloned has to have specified.
Explanation: For FlashCopy backup operations the
corresponding IBM Tivoli Storage FlashCopy Manager System action: Processing ends.
profile device class section must not contain the User response: Specify the database to be cloned by
parameter CLONE_DATABASE set to YES. specifying the command option '-d' followed by the
System action: Processing ends. database name.

User response: Please use a device class that has not

specified the parameter CLONE_DATABASE YES. FMM1081E Unable to detect the database
environment.

FMM1076E The target set 'target set' is used for a Explanation: The operation requires special
backup with ID 'backup ID'. It cannot be environment settings, e.g. the database instance owner
used as target set for cloning. environment.

Explanation: Target sets used for FlashCopy backups System action: Processing ends.
are not eligible for cloning. User response: Please run the command as database
System action: Processing ends. instance owner.

Chapter 2. FMM messages 59

FMM1082E • FMM1091E

command to get further details about the root cause of

FMM1082E Checking the clone system status of the
this failure.
database 'database name' failed.
Explanation: Most of the cloning functions require
FMM1087E Failed to rename the database. This is
some state and integrity checks on the production
the output of the failed command:
system as well as on the backup/clone system prior the
'command output'
requested operation starts. The requested operation
continues if the integrated check routine succeeded. Explanation: During the rename of the database from
the production instance name to the clone instance
System action: Processing ends.
name an error has occured.
User response: Check the application logs for further
System action: Processing ends.
details.
User response: Examine the output of the failed
command to get further details about the root cause of
FMM1083E Flashcopy of the database failed with rc
this failure.
return code.
Explanation: The FlashCopy backup, part of the
FMM1088E For cloning functions the name of the
cloning workflow, failed.
clone database must be specified.
System action: Processing ends.
Explanation: For all cloning functions the name of the
User response: Check the application logs for further clone database must be specified.
details.
System action: Processing ends.
User response: Specify the option '-C <clone database
FMM1084E Database profile 'profile name' not found.
name>'.
Explanation: The named database profile does not
exist or is not accessible by the current user.
FMM1089E For cloning functions the name of the
System action: Processing ends. clone instance owner must be specified.
User response: The database profile name can be Explanation: For all cloning functions the name of the
specified in the profile for IBM Tivoli Storage clone instance owner must be specified.
FlashCopy Manager with the parameter
System action: Processing ends.
TARGET_DATABASE_PARAMETER_FILE. Verify that
the parameter is specified correctly and that the current User response: Specify the option '-u <clone instance
user has read permssions. The default for the value of owner>'.
this paraemeter (if not specified in the profile for IBM
Tivoli Storage FlashCopy Manager) is
$ORACLE_HOME/dbs/init$ORACLE_SID.ora. FMM1090E For the pre-processing function the
pre-processing configuration file must
be specified.
FMM1085E No database control file found.
Explanation: For the pre-processing function the name
Explanation: During the creation of a database clone of the pre-processing configuration file is required.
no database control file was found on the flashcopied
volumes. System action: Processing ends.

System action: Processing ends. User response: Specify the option '-X <configuration
file>'.
User response: Ensure that at least on control file
copy resides on the same volumes as the data file or
the online redo log files. FMM1091E For the post-processing function the
post-processing configuration file must
be specified.
FMM1086E Failed to start the database in nomount
mode. This is the output of the failed Explanation: For the post-processing function the
command: name of the post-processing configuration file is
required.
Explanation: The process was unable to start the
database instance without mounting the database files. System action: Processing ends.

System action: Processing ends. User response: Specify the option '-Y <configuration
file>'.
User response: Examine the output of the failed

60 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1092E • FMM1122E

FMM1092E Script terminated with errors. Return FMM1096E The script 'script name' is a symbolic
code is: return code link.
Explanation: The execution of a script terminated with Explanation: The named script entry in either the
an error. pre-processing or post-processing configuration file is a
symbolic link, which is not allowed.
System action: Processing ends.
System action: Processing ends.
User response: Check the application logs for further
details. User response: Ensure that any script entry in either
the pre-processing or post-processing configuration file
is not a symbolic link.
FMM1093E Script 'script name' could not assigned to
either shell scripts or SQL scripts.
FMM1097E The user 'user name' is not owner of the
Explanation: For FlashCopy cloning pre-processing
script 'script name'.
and post-processing tasks, either shell scripts or SQL
scripts can be used. These scripts will be entered either Explanation: If the named pre-processing or
in the pre-processing configuration file or in the post-processing script is owned by the root-user,
post-processing configuration file. The identifier anyone can execute that script. Further, if the named
whether it is a shell script or a SQL script is a pre-processing or post-processing script is not owned
dedicated suffix string of the script itself. Is the suffix by the root-user, it can only by executed by the user
string of type 'sh' then it is handled internally as a shell who owns that script.
script, whereas if the suffix string is of type 'sql' it is
System action: Processing ends.
handled internally as a SQL script. Other suffix strings
are not eligible. Such scripts will not be handled or User response: Check the ownership of the named
executed. script and if necessary adjust them accordingly.
System action: Processing ends.
FMM1098E The user 'user name' configured for script
User response: Check the script entries in either the
'script name' is actually not applied on
pre-processing or post-processing configuration file and
the system.
adjust the contained script names accordingly.
Explanation: The named user, who is configured to
execute the named script does not exist on the system.
FMM1094E Script file 'script name' not found.
System action: Processing ends.
Explanation: A script file to be executed as part of
either pre-processing or post-processing could not be User response: Check the applied user on the system
found. and either update the pre-processing or post-processing
configuration for a different existent user or add the
System action: Processing ends.
configured user credentials to the system.
User response: Check the script entries in either the
pre-processing or post-processing configuration file and
FMM1099E The pre-processing or post-processing
adjust the contained script names accordingly.
configuration file 'file name' is not found.
Explanation: The named pre-processing or
FMM1095E The physical location of the
post-processing configuration file is containing the
pre-processing or post-processing
scripts to be executed could not be found on the
configuration file and the script 'script
backup/clone system, where the pre-processing or
name' is different.
post-processing will be executed.
Explanation: The physical location of the
System action: Processing ends.
pre-processing or post-processing configuration file and
their containing scripts to be executed has to have User response: Check the name of the specified
identically.. pre-processing or post-processing configuration file and
check whether it exists on the backup/clone system.
System action: Processing ends.
User response: Ensure the pre-processing or
FMM1122E The pre-processing or post-processing
post-processing configuration file and their containing
configuration file 'file name' does not
scripts are stored under the same physical location.
contain any data record.
Explanation: The named pre-processing or
post-processing configuration file is empty which
means it does not contain any entry to be processed.

Chapter 2. FMM messages 61

FMM1123E • FMM1168I

System action: Processing ends.

FMM1163W Script terminated with warnings.
User response: Either specify the correct
Explanation: The execution of a script terminated with
pre-processing or post-processing configuration file or
one or multiple warnings. The overall operation might
add one or multiple valid data records (scripts) to it.
be finished successfully. Nevertheless, to avoid
subsequent more critical issues it is highly
FMM1123E Failed to open the database: output recommended to check and resolve the root cause of
the warning to guarantee the operational consistency of
Explanation: After creating a database clone IBM the system in the future.
Tivoli Storage FlashCopy Manager was not able to
open the database. System action: Processing continues.

System action: Processing ends. User response: Check the application logs for further
details.
User response: Examine the output of the failed
command to get further details about the root cause of
this failure. FMM1164I Renaming file system <old file system
name> to <new file system name>

FMM1154E The only valid profile values for the Explanation: The named file system is going to be
keyword 'keyword' are 'val1' and 'val2'. renamed.

Explanation: Invalid values were given in the profile System action: Processing continues.
for the specified keyword.
User response: None.
System action: Processing ends.
User response: Change the profile so that the FMM1165I Recovering the database database name.
recommended values for the specified keyword are
Explanation: The named database is going to be
valid.
recovered.
System action: Processing continues.
FMM1158T Service service not completed
User response: None.
Explanation:
System action:
FMM1166I Switching LOGRETAIN and USEREXIT
User response: off for database database name.
Explanation: The log archiving for the named
FMM1161E Failed to recover the database. This is database is switched off.
the output of the failed command:
System action: Processing continues.
Explanation: The recovery of the database has failed.
User response: None.
System action: Processing ends.
User response: Examine the output of the failed FMM1167I Creating relocate configuration file for
command to get further details about the root cause of database database name.
this failure.
Explanation: The relocate configuration file required
as input for the relocate database command is going to
FMM1162E Failed to determine the online redo logs. be created for the named database.
Output of the failed command: output
System action: Processing continues.
Explanation: IBM Tivoli Storage FlashCopy Manager
User response: None.
failed to detect the names of the online redolog files of
the database.
FMM1168I Creating the storage path directories for
System action: Processing ends.
database database name.
User response: Examine the output of the failed
Explanation: The storage paths for the named
command to get further details about the root cause of
database are going to be created.
this failure.
System action: Processing continues.
User response: None.

62 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1169I • FMM1181I

System action: Processing continues.

FMM1169I Relocating database partitions partition
list of database database name. User response: None.
Explanation: The named database partitions of the
specified database are going to be relocated. FMM1176I Restore control file file name.
System action: Processing continues. Explanation: The named control file is going to be
restored.
User response: None.
System action: Processing continues.
FMM1170I Cloning database database name. User response: None.
Explanation: The named database is going to be
cloned. FMM1177I Performing media recovery.
System action: Processing continues. Explanation: A media recovery is going to be started.
User response: None. System action: Processing continues.
User response: None.
FMM1171I No rename required.
Explanation: The original database name and the FMM1178I Opening the clone instance instance
cloned database name is equal. Therefore, no re-naming name.
of the cloned database name is required.
Explanation: The clone instance is going to be opened.
System action: Processing continues.
System action: Processing continues.
User response: None.
User response: None.

FMM1172I Preparing recovery of database database

name. FMM1179I Function 'function name' does not
consider the post-processing
Explanation: The named cloned database is going to configuration file.
be prepared for the recovery.
Explanation: The post-processing configuration file is
System action: Processing continues. not considered, e.g. if a pre-processing operation was
started.
User response: None.
System action: Processing continues.
FMM1173I Renaming database old database name to User response: None.
new database name.
Explanation: The cloned database is going to be FMM1180I Function 'function name' does not
renamed. consider the pre-processing
configuration file.
System action: Processing continues.
Explanation: The pre-processing configuration file is
User response: None.
not considered, e.g. if a post-processing operation was
started.
FMM1174I Checking the clone system status of the
System action: Processing continues.
database database name.
User response: None.
Explanation: The system status of the named database
is going to be checked, e.g. whether the database is
running. FMM1181I Executing script type script 'script name'.
System action: Processing continues. Explanation: The named script is going to be
executed. The type of the script is of either 'shell' or
User response: None.
'SQL'.
System action: Processing continues.
FMM1175I Successfully checked the clone system
status of the database database name. User response: None.
Explanation: The system status of the named database
was checked successfully. Operation can continue.

Chapter 2. FMM messages 63

FMM1182I • FMM1207E

(MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, and

FMM1182I Script terminated successfully.
MAX_RESTORE_SESSIONS). Any of the specific
Explanation: The script has terminated successfully. options can be specified in combination with
MAX_SESSIONS. Then, it overrides the value of
System action: Processing continues.
MAX_SESSIONS for the specific function.
User response: None.
FMM1203E Not enough sessions available (sessions
FMM1183E The parameter 'keyword' must have a required and max_sessions available).
length of 'length' characters. "
Explanation: The sum of available sessions specified
Explanation: An invalid length was specified in the in the various server statements (parameter SESSIONS)
profile for the value of the specified keyword. does not cover the required number of sessions
(parameter MAX_SESSIONS).
System action: Processing ends.
System action:
User response: Change the specified profile parameter
to an allowed length. User response: Change the values of the
corresponding parameters in the Data Protection for
SAP profile, so that the condition mentioned in the
FMM1200E Profile parameter 'keyword' is set to YES explanation is fulfilled.
but freeze/thaw is not supported by the
underlying file system.
FMM1205E If you want num_redo
Explanation: The freeze and thaw operation is not REDOLOGCOPIES you should give me
supported by the used file sytem but the profile at least num_mc different Archive
options specify that it be used. Management Classes.
System action: Processing ends. Explanation: Data Protection for SAP requires that the
User response: Change your profile so that it does not number of different Archive Management Classes
use freeze and thaw. (parameter BRARCHIVEMGTCLASS) on the Tivoli
Storage Manager servers is equal to or greater than the
number of redo log or log file copies (parameter
FMM1201E There are no Tivoli Storage REDOLOG_COPIES).
Manager–Servers available.
System action:
Explanation: Data Protection for SAP cannot locate a
Tivoli Storage Manager server. This may be due to a User response: Define at least as many different
configuration problem or to a problem while trying to Archive Management Classes as log file copies
connect to the Tivoli Storage Manager server. Most requested.
probably, a preceding error message points to the cause
of the problem. FMM1206W If you want num_redo
System action: REDOLOGCOPIES you should give me
at least num_mc different Archive
User response: Look for and respond to preceding Management Classes.
error messages. You may also want to check the Data
Protection for SAP profile and the IBM Tivoli Storage Explanation: The message appears during a
Manager client options and client system options files. BRBACKUP run. A BRARCHIVE run afterwards would
fail.

FMM1202E You must specify either System action:

MAX_SESSIONS, or all three specific User response: Define at least as many different
session options Archive Management Classes as log file copies
(MAX_ARCH_SESSIONS, requested.
MAX_BACK_SESSIONS, and
MAX_RESTORE_SESSIONS).
FMM1207E Directory backup not supported.
Explanation: Information on the number of Tivoli
Storage Manager client sessions to be established by Explanation: This option is not yet available.
Data Protection for SAP is missing from the profile.
System action:
System action:
User response: Wait for a future release of Data
User response: In the Data Protection for SAP profile, Protection for SAP, which supports this option.
either specify a value for keyword MAX_SESSIONS, or
specify values for the three specific session parameters

64 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1208W • FMM1217E

FMM1208W Retrying object: 'file name'. Retry count: FMM1213E The value 'wrongvalue' of the keyword
[retry_num]. 'keyword' is not allowed if
'dependentkeyword' is set to
Explanation: An error occurred while processing
'dependendvalue'. "
object file name. Data Protection for SAP is repeating the
action according to the number of retries specified in Explanation: The profile keyword and value depend
the profile. retry_num is the current retry count. on another profile keyword and value. The dependeny
is broken and needs to be fixed.
System action:
System action: Processing ends.
User response: If the problem persists check for and
respond to preceding error messages. User response: Change the profile value of the
specified keyword.
FMM1209E Object not found or not accessible:
'objectname'. FMM1214E TSM Error for session to server server
name: error text
Explanation: The object cannot be located.
Explanation: An error occurred from one of the TSM
System action:
Servers.
User response: The backup integrity is affected.
System action: Processing for the IBM Tivoli Storage
Contact SAP or IBM Support.
Manager Server specified stops. Processing on other
servers continues.
FMM1210E Input file not found or not accessible:
User response: Check the error text and IBM Tivoli
'file name'.
Storage Manager Server name stanza in the profile file
Explanation: Data Protection for SAP cannot locate the for the server name specified in the error.
temporary file named. This file contains the list of
Oracle objects to be backed up or restored. It is passed
FMM1215I Average transmission rate was gb per
to DP for SAP by one of the BR*Tools utilities.
hour GB/h (mb per second MB/sec).
System action:
Explanation: The average transmission rate is
User response: Ensure that you have the correct displayed.
version of BR*Tools installed. For details, check with
System action:
the release notes (RELNOTE).
User response: None.
FMM1211E There is something wrong with your
CONFIG_FILE 'file name'. FMM1216E There are no backup management
classes available.
Explanation: There is a problem with your Data
Protection for SAP configuration file setup. Explanation: The BRBACKUPMGTCLASSES you have
specified in your init<SID>.utl file are not correct.
System action:
System action:
User response: Check the file permission and the file
name specified in the Data Protection for SAP profile User response: Check the management classes on the
keyword CONFIG_FILE. TSM server and specify correct ones.

FMM1212W The file 'file name' is not found in the FMM1217E There are no archive management
manual sorting file. classes available.
Explanation: The file you want to back up was not Explanation: The BRARCHIVEMGTCLASSES you
found in the manual sorting file. have specified in your init<SID>.utl file are not correct.
System action: System action:
User response: Check and correct the manual sorting User response: Check the management classes on the
file so that it contains all the files you are backing up. TSM server and specify correct ones.

Chapter 2. FMM messages 65

FMM1218E • FMM1228W

FMM1218E Environment variable TEMP not set FMM1223W A Problem occurred during send of
performance data to the Administration
Explanation: The required environment setup is
Assistant.
incomplete.
Explanation: There was a problem sending the
System action:
performance data to the Administration Assistant over
User response: Set the environment variable TEMP the network.
and try again.
System action:
User response: Check your setup or contact IBM
FMM1219E The paths of the disks found in the
Support.
ASM instance indicate that the Oracle
ASMLib is not used. This setup is
currently not supported. FMM1224W Unable to initialize connection to
Administration Assistant.
Explanation: The ASM instance has not been set up
with ASMLib. This environment is currently not Explanation: No operational data could be sent to the
supported. Administration Assistant during database backup or
restore.
System action: Processing ends.
System action:
User response: Set up your ASM instance with disks
managed by ASMLib. User response: Check the logs for further information
and try again.
FMM1220E The execution of the system command
'syscommand' ended with a return code FMM1227I Average compression factor was number.
other than 0. The output of the
Explanation: The data transferred had been
command was: 'commandoutput'.
compressed by the factor number.
Explanation: A system command returned a non-zero
System action:
return code.
User response: None.
System action: Processing ends.
User response: Contact IBM support.
FMM1228W Server server name can not be used with
password access method GENERATE in
FMM1221E The parameter 'keyword' must have a this environment. The process is
value other than 'value' to be able to running with user ID userid but the
execute a mount operation. effective user ID is userid effective.
Explanation: The mount operation cannot be executed Explanation: The user ID and the effective user ID of
with the current settings in the profile. Please modify the process are different. In order to utilize the
your profile. password access method GENERATE the IDs must be
equal.
System action: Processing ends.
System action:
User response: Modify your profile according to the
message. User response: Under UNIX and Linux, change the
value of the "PASSWORDACCESS" parameter in file
dsm.sys from 'generate' to 'prompt'.. Under Windows,
FMM1222E Version mismatch error. Please check
change the value of the "PASSWORDACCESS"
setup (version_1:version_2).
parameter in file server name.opt from 'generate' to
Explanation: Different components with inconsistent 'prompt'.
versions are used.
Reset the node's password on the Tivoli Storage
System action: Manager server.

User response: Check your setup or contact IBM In an Oracle environment, run
Support.
backint -f password
In a DB2 environment run
backom –c password
This will prompt you for the TSM password and then
will encrypt it in the Data Protection for SAP configfile.

66 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1229E • FMM1239W

This step needs to be repeated each time your

FMM1233I Operation 'operation' completed.
password expires.
Explanation: The specified operation completed.
FMM1229E Value for parameter BUFFSIZE (actual System action: Processing continues.
cur_number, maximum max_number) is
User response: None.
too large for BUFFCOPY mode
PREVENT.
FMM1234E The directory 'directory' containing the
Explanation: To utilize the BUFFCOPY mode
XPYV components of the installation is
PREVENT the value for the parameter BUFFSIZE must
missing.
not be larger than max_number.
Explanation: A required component could not be
System action:
found. The installation seems to be corrupted.
User response: In the Data Protection for SAP profile,
System action: Processing ends.
specify a BUFFSIZE less or equal to max_number if you
need to prevent copying buffers when passing data User response: Reinstall. Your installation seems to be
between Tivoli Storage Manager components. If you damaged.
need large buffers you can set option BUFFCOPY to
SIMPLE or AUTO. As a consequence, buffers are
copied when data is passed between Tivoli Storage FMM1235E Logical volume 'logicalvolume' not
Manager components. available on system.
Explanation: A required logical volume was not found
FMM1230E The following file was not processed: on the system.
path. System action: Processing ends.
Explanation: The operation was terminated due to a User response: Contact IBM support.
previous error. As a consequence, the file named could
not be processed. The cause of the error should be
found in an earlier message. FMM1236E The section DB2STANDBY is missing
from the profile.
System action:
Explanation: To perform a DB2 standby backup or
User response: Check for and respond to preceding restore functions the section DB2STANDBY must be
error messages. added to the IBM Tivoli Storage FlashCopy Manager
profile.
FMM1231E Maximum number of retries for file System action: Processing ends.
filename exceeded.
User response: Add the section DB2STANDBY to the
Explanation: The number of retries configured in the IBM Tivoli Storage FlashCopy Manager profile.
profile keyword 'FILE_RETRIES' for the named file
were reached.
FMM1237E Unable to perform mount request. The
System action: requested mount point 'mountpoint' is
User response: Check the logs for further information already in use.
about the root cause of the retries. Resolve these issues Explanation: The attempt to mount a volume failed
and perform the operation again. since the required mount point is already in use.
System action: Processing ends.
FMM1232I Executing operation 'operation' on host
'host name'. User response: Unmount any filesystem that is
currently mounted at this mountpoint. Then retry.
Explanation: The specified operation on the named
host was started.
FMM1239W Logical volume 'logicalvolume' of volume
System action: Processing continues. group 'volumegroup' contains unmounted
User response: None. filesystem.
Explanation: This warning lists all filesystems of the
volume groups contained in the backup that are
currently not mounted. In case of a restore these
filesystems will be overwritten and all its data is
reverted to the point in time when the backup was
taken.

Chapter 2. FMM messages 67

FMM1240E • FMM1247E

System action: Processing continues. the DB2 HADR standby system.

User response: None. System action: Processing ends.
User response: Please verify that the DB2 alias
FMM1240E Unable to mount the following specified with the profile parameter DB2_ALIAS in the
filesystems: mointpoints DB2STANDBY section can be found in the DB2
database directory DB2 HADR standby system. Use the
Explanation: The listed filesystem could not be
'db2 list db directory' command to list the cataloged
mounted.
database aliases.
System action: Processing ends.
User response: Check why the listed filesystems could FMM1245E There is no mount agent suitable for
not be mounted, then issue the command again. cloning with device class 'device class'
started. Function cloning requires a
dedicated mount agent that was limited
FMM1241E Unable to unmount the following to a specific device class using the
filesystems: mointpoints option '-s <device class>'.
Explanation: The listed filesystem could not be Explanation: Function cloning requires a dedicated
unmounted. mount agent that was limited to a specific device class
System action: Processing ends. using the option '-s <device class>'.

User response: Check why the listed filesystems could System action: Processing ends.
not be unmounted, then issue the command again. User response: Make sure that mount agent was
started with option '-s <device class>'.
FMM1242E Error while parsing the profile: It is not
allowed to have an ORACLE section FMM1246E The database name has to have
without a CLIENT section. specified, because multiple databases
Explanation: It is not allowed to have an ORACLE have been found within this instance.
section without a CLIENT section. Explanation: If multiple databases found in one
System action: Processing ends. database instance, the one for that a snapshot backup
should be restored or deleted has to have specified.
User response: Just specify the missing profile
keyword. System action: Processing ends.
User response: Specify the database name of the
FMM1243E Only a single device class name is database for that a snapshot backup should be restored
allowed for the profile parameter or deleted by specifying the command option '-d'
parameter in combination with the followed by the database name.
keyword keyword.
Explanation: The profile parameter 'DEVICE_CLASS FMM1247E A FlashCopy Backup is not allowed
device_class_name USE_FOR_CLONING dbname' in because FlashCopy Clone(s) 'clones'
the CLONING section can only be assiged to one is/are active with FlashCopy Type
device class name. This is different to the usage of the NOCOPY.
DEVICE_CLASS parameter in the CLIENT section Explanation: You have created a FlashCopy Clone
where a list of device class names can be specified. For with the parameter ALLOW_NOCOPY_FLASHCOPY
Cloning this is not allowed. set to YES in the CLONING device class. With this
System action: Processing ends. settings it is no longer allowed to perform FlashCopy
Backups on the same SVC cluster.
User response: Only use a single device class name
with the DEVICE_CLASS parameter in the CLONING System action: Processing ends.
section. User response: If you want to start a new FlashCopy
Backup on the same SVC cluster it is required to delete
FMM1244E The DB2 alias 'alias' could not be found all FlashCopy Clone(s) that were created with
in the database directory. Please check FlashCopy Type NOCOPY first.
the value of the profile parameter
parameter.
Explanation: The DB2 alias specified with the profile
parameter DB2_ALIAS in the DB2STANDBY section
could not be found in the DB2 database directory on

68 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1248E • FMM1257E

FMM1248E A FlashCopy Clone with FlashCopy FMM1252I Deleting snapshot 'name of the snapshot to
Type NOCOPY is not allowed because delete' for volume 'name of the volume'
FlashCopy Backup(s) 'backups' is/are
Explanation: The snapshot that has been identified is
active.
going to be deleted because the corresponding backup
Explanation: You want to create a FlashCopy Clone has been deleted.
with the parameter ALLOW_NOCOPY_FLASHCOPY
System action: Processing continues.
set to YES in the CLONING device class. With this
settings it is not allowed to have FlashCopy Backups User response: None.
on the same SVC cluster.
System action: Processing ends. FMM1253E The 'target instance uuid' target instance
UUID that is specified in the input file
User response: If you want to start a new FlashCopy
cannot be found or the UUID is
Clone with the parameter
assigned to a template. Edit the input
ALLOW_NOCOPY_FLASHCOPY set to YES in the
file and specify a valid target instance
CLONING device class it is required to delete all
UUID.
FlashCopy Backup(s) on the same SVC cluster first.
Explanation: The target instance UUID specified in the
input file was not found.
FMM1249E The LUN's of the datastores requested
for backup are spread across multiple System action: Processing ends.
storage subsystems. IBM Tivoli Storage
FlashCopy Manager can support LUNs User response: Specify a valid target instance UUID.
from only one storage subsystem.
Explanation: The virtual machines selected for backup FMM1254I The 'snap name' snapshot of the fileset
are contained in datastores that are spread across 'fileset name' in the 'file system device name'
multiple storage subsystems. file system was created.

System action: Processing ends. Explanation: A GPFS™ snapshot with the specified
parameters was successfully created.
User response: Ensure the datastores and virtual
machines which have been selected for backup are all System action: Processing continues.
contained on one storage subsystem. User response: None.

FMM1250I The 'user name to log-in to the file server' FMM1255E The process cannot continue. Reverting
ID is connecting to the following file changes.
server: 'remote hostname of the file server' .
Explanation: An error occured. The changes that can
Explanation: For ID used to log on to the file server, be undone will be reversed now.
the name is provided. In addition, the remote hostname
of the file is provided. These values are stored in the System action: Processing ends.
following parameters for the configuration profile User response: None.
DEVICE_CLASS section:
COPYSERVICES_PRIMARY_SERVERNAME and
COPYSERVICES_USERNAME FMM1256I The 'snap name' snapshot of the fileset
'fileset name' in the 'file system device name'
System action: Processing continues. file system was restored.
User response: None. Explanation: The GPFS snapshot with the specified
parameters was successfully restored.
FMM1251I A snapshot is taken for the following System action: Processing continues.
volume: 'name of the volume'.
User response: None.
Explanation: The volume identified in this message is
going to be backed up with a snapshot. If multiple
volumes are going to be backed up with snapshots, FMM1257E The file server does not recognize the
each volume is identified in separate messages. volume with the following serial
number: 'identifier'.
System action: Processing continues.
Explanation: When the software attempted to back up
User response: None. the files, the file server specified with the
COPYSERVICES_SERVER_NAME parameter did not
find the volume with the serial number identified in

Chapter 2. FMM messages 69

FMM1258I • FMM1264W

the error message. The file server that hosts the volume System action: The operation stops.
is specified with the COPYSERVICES_SERVER_NAME
User response: None.
parameter in the DEVICE section. A possible
explanation is that the volume is stored locally and not
on the NetApp or N-Series file server specified with the FMM1262W The snapshot snapshot_name of the file
COPYSERVICES_SERVER_NAME parameter. system filesystem_name cannot be deleted
because the file system is not known to
System action: Processing ends.
the local cluster.
User response: Verify that the file server that is
Explanation: IBM Tivoli Storage FlashCopy Manager
specified in the configuration is the file server that
cannot delete the snapshot of the file system nor
hosts the volumes that are used for the current
determine whether the snapshot is still available
operation. To check the file server specified in the
because the file system is not known to the local
configuration, start the setup script or open the profile
cluster.
configuration file. In the DEVICE section, the
COPYSERVICES_SERVER_NAME parameter is used to System action: The meta-information on this snapshot
specify the file server. is kept in the repository. The snapshot is not listed in
the list of available snapshots unless the force option is
issued with the query command.
FMM1258I The following volume is offline: volume
name User response: To remove the record from the
repository without mounting the file system in the local
Explanation: Because the volume is already offline,
cluster use the delete-force option when issuing the
the volume cannot be taken offline.
delete request.
System action: Processing continues.
User response: There are no additional tasks or steps FMM1263W The snapshot snapshot_name of the file
to complete. system filesystem_name cannot be deleted
because the file system is not mounted.
FMM1259I The following clone volume already Explanation: IBM Tivoli Storage FlashCopy Manager
exists: volume name cannot remove the snapshot from the file system nor
determine whether the snapshot is still available in the
Explanation: Because the clone volume already exists,
file system because the file system is not currently
the clone volume cannot be created.
mounted in the local cluster.
System action: Processing continues.
System action: The meta-information on this snapshot
User response: There are no additional tasks or steps is kept in the repository. The snapshot is not listed in
to complete. the list of available snapshots unless the force option is
issued with the query command.

FMM1260E The GPFS file system 'device name' is User response: Issue the mount command to mount
currently mounted on the system at: the file system. The device agent removes the snapshot
'current mount point'. The GPFS file from both the file system and the repository.
system must be mounted at: 'default
To remove the record from the repository without
mount point', the default mount point.
mounting the file system, use the delete-force option
Explanation: Only the default mount points are when issuing the delete request.
supported for GPFS snapshot and restore functions.
System action: The operation stops and cannot FMM1264W The snapshot snapshot_name of the file
continue until this error is resolved. system filesystem_name cannot be deleted.
Error information: error_information
User response: To resolve this issue, mount the GPFS
file system without specifying the mount point Explanation: A request to delete the snapshot
argument. The GPFS file system is mounted at the snapshot_name of the file system filesystem_name cannot
default mount point. After you resolve this problem, be completed. An error occurred when processing the
run the backup again. delete command.
System action: The meta-information on this snapshot
FMM1261E Key value set for undefined key column is kept in the repository. The snapshot is not listed in
key_value. Command was: command the list of available snapshots unless the force option is
issued with the query command.
Explanation: The call to request output data of
command 'command' was set up incorrectly. If a key User response: Resolve any problems indicated by the
value is specified a key column must be defined, too. error_information error. After you resolve the issue, the

70 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1265W • FMM1272E

device agent removes the snapshot from both the file

FMM1268E A relative file name 'file name' was found
system and the repository.
in the infile. Relative file names are not
supported.
FMM1265W The filesystem_name file system is
Explanation: Replace all relative file names with
unknown to the local cluster. Therefore,
absolute file names in the infile.
IBM Tivoli Storage FlashCopy Manager
cannot run the reconciliation process for System action: The software process ends.
the following snapshots: list_of_snapshots
User response: Verify that only absolute file names are
Explanation: IBM Tivoli Storage FlashCopy Manager specified in the infile.
cannot find snapshots of the filesystem_name file system
because this file system is not known in the local
FMM1269E For GPFS snapshots, the value parameter
cluster.
value is not valid for the parameter name
System action: The meta-information for the parameter.
snapshots listed are stored in the repository.
Explanation: If IBM Tivoli Storage FlashCopy
User response: To remove the record from the Manager is configured for the General Parallel File
repository without mounting the file system, use the System (GPFS), the current value specified for the
delete-force option when issuing the delete request. parameter name parameter is not allowed.
System action: If this condition is detected during a
FMM1266W The filesystem_name file system is not backup operation, the operation stops.
mounted. Therefore, IBM Tivoli Storage
If this condition is detected while configuring IBM
FlashCopy Manager cannot run the
Tivoli Storage FlashCopy Manager, you are prompted
reconciliation process for the following
for a different value of the parameter name parameter.
snapshots: list_of_snapshots
User response: Specify a different value for the
Explanation: IBM Tivoli Storage FlashCopy Manager
parameter name parameter.
cannot find snapshots of the filesystem_name file system
because the file system is not currently mounted in the If the parameter name parameter is not specified in your
local cluster. profile, and the default value is used, explicitly set it to
a value different from parameter value.
System action: The meta-information for the
snapshots listed are stored in the repository.
FMM1270I The following volume is mapped to
User response: Issue the mount command to mount
initiator group: volume name.
the file system so that the reconciliation process can be
performed. Explanation: Because the volume is already mapped, a
new mapping is not created.
To remove the record from the repository without
mounting the file system, use the delete-force option System action: Processing continues.
when issuing the delete request.
User response: There are no additional tasks or steps
to complete.
FMM1267W IBM Tivoli Storage FlashCopy Manager
cannot determine whether the snapshot
snapshot_name snapshot of the file FMM1271I The following volume is online: volume
system filesystem_name is still available. name
Error information: error_information Explanation: Because the volume is already online, no
Explanation: During the reconciliation process, an actions taken and processing continues.
error_information error occurred when trying to System action: Processing continues.
determine whether the snapshot_name snapshot is still
available in the filesystem_name file system. User response: There are no additional tasks or steps
to complete.
System action: The meta-information for this snapshot
is kept in the repository.
FMM1272E The following VMs listed in the instant
User response: Resolve any problems indicated by the restore input file are not part of the
error_information error. After you resolve this issue, the backup: vms_in_infile
reconciliation will be run.
Explanation: The instant universal unique identifier
(UUIDs) listed in the instant restore input file are not
part of the backup.
System action: Processing stops.

Chapter 2. FMM messages 71

FMM1273E • FMM1501E

User response: Use only instant UUIDs in the input

FMM1276E Cluster cluster_name cannot mount the
file that are part of the backup.
file system filesystem_name in read/write
mode. If the file system is to be
FMM1273E The source volume with serial number mounted remotely, ensure that the
cmd is not attached to any known ESX mounting cluster has the correct
hosts. permissions to mount the file system in
the mode requested.
Explanation: The specified physical volume was
found during the FlashCopy backup as part of the data Explanation: The file system specified cannot be
store volume on the production system. Now, during mounted in read/write mode.
the instant restore, the volume is no longer found on
System action: Processing ends.
any of the ESX hosts.
User response: When you mount a file system
System action: Processing ends.
remotely, check that the cluster that is to mount the file
User response: Attach the missing volume to the system has been granted sufficient permissions to
correct ESX host on the storage system. mount the file system in read/write mode (command:
mmauth grant). Resolve the problem and try the
operation again.
FMM1274E The file system filesystem_name cannot be
mounted. If the file system is to be
mounted remotely, ensure that the FMM1278W The power on VM task for VM 'vmname'
mounting cluster has the correct failed.
permissions to mount the file system.
Explanation: The VM was selected to power on after
Additional information:
instant restore but a the power on VM task failed
command_and_command_output
during execution.
Explanation: The file system specified cannot be
System action: Processing stops.
mounted. Both the system command that is used and
the command output are listed. User response: power on the Virtual Machine
manually
System action: Processing ends.
User response: When you mount a file system
FMM1279E The 'volume name' LUN cannot be
remotely, check that the cluster that is to mount the file
mapped by using the initiator group
system is authenticated with the owning cluster
'initiator group': error message
(command: mmauth add). In addition, ensure that the
correct permissions to mount the file system are Explanation: The mapping cannot be created because
granted (command: mmauth grant). In DB2 pureScale® the initiator group does not exist.
environments, read/write permission is required.
System action: Processing ends.
Examine the command output to determine the cause
of the problem, resolve the problem, and try the User response: Ensure that the initiator group exists
operation again. on the storage system and try the operation again.

FMM1275E The ' vm_name' virtual machine is FMM1280E The mapping for the 'volume name' LUN
located on the following data stores : cannot be removed by using the
list_of_datastors. In the input file not all initiator group 'initiator group': error
of these data stores were specified. You message
must specify all listed data stores in the
input file or exclude this virtual Explanation: The initiator group that is used to
machine so that the instant restore can remove the mapping must be available and fully
continue. operational.

Explanation: The virtual machine is located on more System action: Processing ends.
than one data store. Not all of the data stores are listed User response: Ensure that the initiator group exists
in the instant restore input file. on the storage system and is fully operational.
System action: Processing stops.
User response: Add the missing data stores to the FMM1501E Only one LUN per ASM failure group is
instant restore input file or exclude the VM from the allowed with DS8000 storage. 'LUN
instant restore. count' LUN's have been found in failure
group 'failure group name' of diskgroup
'diskgroup name'.

72 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1502E • FMM1508E

Explanation: For DS8000, only a single LUN per

FMM1505E Operation aborted because a different
failure group is allowed. The specified failure group
operation by this database client is
consists of more than one LUN. This environment is
already running.
not supported.
Explanation: Different concurrent operations of the
System action: Processing ends.
same type were started for the same database. This is
User response: Reduce the number of LUN's in each not supported. The current operation is aborted. This
failure group to one. message is also issued when a cooperative operation of
two or more participating partitions was started, but
the profile settings used for the various partitions do
FMM1502E Oracle ASM with SVC is not supported not match.
with the setting 'profile_value' for the
profile parameter 'profile_param'. System action:

Explanation: Preassigned volumes cannot be used User response: Wait until the currently running
with SVC and Oracle ASM. operation has ended and try again. Make sure that
multiple operations are not started concurrently for a
System action: Processing ends. database. If this is a cooperative operation with two or
User response: Specify the name of the backup server more participating partitions, check that the profile
as defined in the storage subsystem for the specified settings of the various partitions (for example,
profile parameter. DEVICE_TYPE, MAX_VERSIONS, etc.) do not differ. If
they do, fix the profile settings, cancel the current
operation, and start the operation again. Also,
FMM1503E The single disk restore operation to the investigate the possibility of sharing the same profile
source virtual machine 'vm name' with among all partitions.
instance UUID 'source vm instance uuid' is
not possible since 'number snapshots'
VMware snapshots have been found on FMM1506E Error: 'description' on host 'hostname'
the source virtual machine but none are while executing command 'command'.
allowed. Explanation: The system tried to execute the
Explanation: The single disk restore operation to the command cited. During execution, an error occurred.
specified virtual machine is not possible since VMware The output received from the command shell is listed
snapshots have been found for this virtual machine. following the message.
This virtual machine must not have any snapshots for System action:
the single disk restore operation.
User response: Determine the cause of the problem
System action: Processing ends. from the command and the output listed in the
User response: Remove the VMware snapshots from message, and resolve the problem.
the specified virtual machine.
FMM1507E The process needs to run with root
FMM1504E The single disk restore operation of the authority.
virtual machine 'vm name' with instance Explanation: The current process requires root
UUID 'source vm instance uuid' is not authority.
possible since 'number snapshots'
VMware snapshots have been found for System action:
this virtual machine as it is contained in
User response: Start the process under an account
the backup but none are allowed.
with root authority.
Explanation: The single disk restore operation of the
specified virtual machine is not possible since VMware
FMM1508E The service service_name has terminated
snapshots have been found for this virtual machine.
due to a previous error. Please check all
This virtual machine must not have any snapshots at
logs for additional information.
the backup point in time to allow a single disk restore
operation to the source virtual machine. Explanation: The cited service is no longer available.
System action: Processing ends. System action:
User response: If a single disk restore to the source User response: Check the appropriate logs for the
virtual machine should be performed with this virtual cause of its termination.
machine a new backup needs to be created. The
specified virtual machine is not allowed to have
VMware snaphots during the creation of that backup.

Chapter 2. FMM messages 73

FMM1509E • FMM1520E

FMM1509E Authentication failure. The password FMM1515I Client is logging to file_name

specified is not authorized for accessing
Explanation: The client's log messages are written to
component. Please verify that the
the indicated file.
passwords specified in the password
files on the different production and System action:
backup/cloning systems are correct.
User response: None.
Explanation: To access the named component, a
password is required. However, the password provided
could not be verified. FMM1516I Deleting container container.

System action: Explanation:

User response: Make sure that the password files used System action:
by the different components of the system match. User response:

FMM1510I New connection received from host FMM1517I Deleting target data container defined
hostname. by container_description.
Explanation: The server received a new connection Explanation: The data in the container indicated is
request. removed.
System action: System action:
User response: None. User response: None.

FMM1512E An error occurred during shutdown: FMM1518E Internal error: The system is trying to
Error information use the same device agent, although the
Explanation: During shutdown of the component, a synchronization mode is not
problem occurred. The error information is given. PARALLEL.

System action: Explanation: The system has been told to use the
same device agent for multiple database clients, but the
User response: Resolve the problem indicated by the database indicated serial synchronization mode. This
error information. setup is not supported.
System action:
FMM1513I *****> Database client connected:
instance instance, database User response: Contact your IBM support personnel.
database_namepartition_numbernodename
Explanation: This message follows a message FMM1519E A failure occurred during initialization
FMM1511I and indicates the connection of one of the of one or more of the nodes
database clients taking part in the operation. A participating in this operation. Please
database client is an instance of the snapshot backup check the logs for more information.
library representing a single partition of the database. Explanation: Some problem occurred during the
System action: initialization of a new operation. The problem may be
with any component required for this operation.
User response: None.
System action:

FMM1514I *****> Device client connected. User response: Check the acsd log file for messages
FMM1515I to determine the log file names of the
Explanation: This message follows a message participating agents. Check the log files of each
FMM1511I and indicates the connection of one of the component for the cause of the problem.
device clients taking part in the operation. A device
client is an instance of the device agent for the storage
device. FMM1520E Volume volume_name is shared across
partitions. Volume sharing is not
System action: allowed.
User response: None. Explanation: At least two partitions own data residing
on the volume indicated. This setup is not supported.
System action:

74 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1521I • FMM1535E

User response: With the current disk layout of the to provide the profile to the current process. Start the
database, the requested function cannot be used. If you process again using a valid configuration file.
want to use the function, change the disk layout of the
database so that each data volume is dedicated to a
FMM1529E The device 'device_type' is not supported
partition.
by the wizard.
Explanation: The device type represents a certain type
FMM1521I Retaining number backups
of storage device. While using the setup wizard, a
Explanation: When enforcing profile parameter device type was entered that is not supported by the
MAX_VERSIONS, the indicated number of backups is current version of the wizard.
kept.
System action:
System action:
User response: Refer to your user documentation for a
User response: None. list of the device types that are supported by default.
Specify one of the supported types.
FMM1522E The requested meta–information
(subject="description") is not available. FMM1530E Failed to launch the device agent for
device_type. Please consult your user
Explanation: Some meta–information about each
documentation to make sure that all
backup is stored in the repository. An error occurred
requirements for the specified device
when trying to retrieve part of this information.
are met.
System action:
Explanation: The system was unable to launch the
User response: Contact your IBM support personnel. appropriate device agent for the type indicated because
some of its requirements are not met.

FMM1523W Warning: The following containers were System action:

reused without being explicitly released:
User response: Refer to your user documentation and
description
make sure that the system is set up correctly for the
Explanation: The containers defined by the specified device type.
description are used by the current backup. They were
used before by a different backup. This message is
FMM1534E Unexpected version actual_version of the
expected in SAN environments where data containers
repository located at path. Expected
are usually kept until they are reused. In this case, this
version: supperted_version
message does not indicate a problem.
Explanation: The server located the repository in the
System action:
path indicated. However, the version of the repository
User response: None. located on disk does not match the current version of
the server.

FMM1525E The process service_name is in an System action:

inconsistent state. Please check for
User response: Make sure to use the correct instance
previous errors and restart the process
of the server. Ensure that the path of the repository was
afterwards.
specified correctly. Refer to the release notes for a list of
Explanation: The process indicated cannot continue possible incompatibilities.
with inconsistent data.
System action: FMM1535E Unexpected characteristics
(bitwidth=bitwidth repository) of the
User response: Check the logs for messages pointing repository located at path. Expected
to the cause of the inconsistency. After resolving any bitwidth: bitwidth expected
problems, restart the process.
Explanation: The repository located in the path
indicated was saved to disk using a bit width different
FMM1526E A configuration file (profile) must be from the bit width the server is using to load the
provided. repository.
Explanation: An operation was started without System action:
providing a profile.
User response: Make sure to use the correct instance
System action: of the server. Ensure that the path of the repository was
User response: Check the user documentation on how

Chapter 2. FMM messages 75

FMM1536E • FMM1543E

specified correctly. Refer to the release notes for a list of Explanation: The command line generated by the
possible incompatibilities. setup function exceeds 127 characters. This situation
requires user intervention. The setup function did not
update /etc/inittab.
FMM1536E The repository located at path is not
valid. System action:
Explanation: A repository could not be found at the User response: Refer to your user documentation for
location indicated by path. information on what entries to add to /etc/inittab.
System action:
FMM1541E /etc/inittab was not updated because
User response: Ensure that the path of the repository
some of the processes have apparently
was specified correctly. Do not edit any files in the
been added. Please re–run the setup
repository path.
after calling the setup script with option
'–a disable' if you want to change to a
FMM1537E The repository located at path was standard setup.
written with an incompatible protocol
Explanation: During the automatic setup, entries for
(protocol_version incompatible). Expected
this product were detected in /etc/inittab. This is an
protocol: protocol_version expected
indication that the product was not previously
Explanation: The repository found at the location uninstalled.
indicated was written to disk using the protocol
System action:
version named. However, the server currently supports
the expected protocol version. User response: Run the setup with option '–a disable'
and then start the installation process again. If the
System action:
entries in /etc/inittab should be retained, refer to your
User response: Ensure that the path of the repository user documentation for information on how to
was specified correctly. Do not edit any files in the complete the installation manually.
repository path.
FMM1542E Failed to uninstall because some of the
FMM1538E Unexpected repository type. The path processes to be uninstalled are still
'path' does not point to a repository of listed in /etc/inittab. Please re–run the
type "protocol_type". setup after stopping the component by
calling the setup script with option '–a
Explanation: The repository located in the path stop'.
indicated was written to disk using a protocol different
from the protocol supported by the server process. Explanation: Before uninstalling the product, the
affected processes must be stopped. This is done by
System action: running the setup script with the option '–a stop',
User response: Make sure to use the correct instance which will remove the entries from /etc/inittab and
of the server. Ensure that the path of the repository was stop the processes.
specified correctly. Refer to the release notes for a list of System action:
possible incompatibilities.
User response: Refer to your user documentation for
information on the uninstall process. Run the setup
FMM1539E Root privileges required. Could not with the option '–a stop' and then continue
change user ID to root. uninstalling.
Explanation: The requested operation requires root
privileges. However, the process could not acquire FMM1543E The component is still referenced within
them. the /etc/inittab. In order to terminate the
System action: component re–run the setup script with
option '–a stop'.
User response: Make sure the appropriate privileges
(s–bit) are granted to the executable. Explanation: The setup utility detected that the
product is still active in the system. Apparently, its
entries in /etc/inittab are not yet removed.
FMM1540E /etc/inittab entries are limited to 127
characters. Please consult your user System action:
documentation for information on User response: Call this process again with the option
manually completing the installation '–f stop'.
procedure.

76 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1544E • FMM1554W

FMM1544E New entries cannot be added to FMM1548E Failed to monitor the data associated
/etc/inittab because it already contains with the deleted backup backup_id.
too many entries starting with 'ac'.
Explanation: A background daemon is supposed to
Please refer your user documentation for
monitor the states of backups in order to determine if
a manual setup of this package.
data needs to be deleted from the storage device.
Explanation: During setup, an unusually high number However, the monitor was not able to access the
of entries beginning with 'ac' were detected in appropriate data.
/etc/inittab. /etc/inittab was not modified.
System action:
System action:
User response: Look for a previous message pointing
User response: Determine if these entries are to the cause of the problem. Resolve any problems
expected, or if they were added due to a problem. If indicated there. Once the cause of this problem is
these entries are required, refer to your user resolved the daemon will take care of the deleted
documentation for information on how to complete the backups eventually.
installation manually.
FMM1549E Failed to load component_name
FMM1545E oldprod is currently running.
Explanation: The system was unable to load the
Explanation: This failure happens during named component of the product.
(de)installation and indicates that not all TSM for ACS
System action:
components could be stopped.
User response: Contact IBM Support.
System action:
User response: Check that no backup or restore is
FMM1550W Unable to perform background
currently running and retry the operation. If you have
monitoring for backup 'backup id' for
customized the process of starting TSM for ACS, it
time.
might be necessary to manually stop it by undoing
those customization steps. Explanation: Background monitoring for the named
backup id is suspended for the named period of time
due to it is locked or the background monitor is not
FMM1546E IBM Tivoli Storage Manager for Advanced
running.
Copy Services was not started.
System action:
Explanation: This failure happens during installation
and indicates that not all TSM for ACS components User response: Check if the background monitor is
could be started successfully. running.
System action:
FMM1553I Component_name is logging to path
User response: Check that all TSM for ACS
components have the appropriate access rights and Explanation: The file denoted is the log file of the
retry the operation. Contact the support function if the named component.
operation continues to fail.
System action:

FMM1547E Failed to remove the data associated User response: If you need to check the log of the
with the deleted backup backup_id. indicated component, look for this message to identify
the log file to examine.
Explanation: The backup named was deleted.
However, its data could not be removed from the
repository and from the storage device. FMM1554W The agent 'component_name' terminated
with exit code number.
System action:
Explanation: The process denoted ended with the
User response: Look for a previous message pointing given exit code.
to the cause of the problem. Resolve any problems
indicated there. Once the cause of this problem is System action:
resolved, the daemon will take care of the deleted User response: Check the agent's log for any messages
backups eventually. pointing to a problem. Resolve any problem indicated.

Chapter 2. FMM messages 77

FMM1555I • FMM1563I

log/trace file for errors and restart the snapshot backup

FMM1555I Profile successfully created.
after the problem is corrected.
Explanation: The profile wizard created a new profile.
System action: FMM1560E Not all file systems have been validated
by the mount agents!
User response: The setup script recognizes
components being restarted so that the new settings Explanation: During a snapshot backup run, TSM for
become active.. ACS detected that not all file systems could be
mounted successfully on the offload system. The
current snapshot backup run will be deleted.
FMM1556E Some data of backup backup_id are
unavailable. It is impossible to restore System action:
the data requested.
User response: Check the TSM for ACS device agent
Explanation: The system detected that some of the log/trace file for errors and restart the snapshot backup
data originally contained in the backup is no longer after the problem is corrected.
available. The occurrence of this message depends on
the type of storage device employed. For example, if an
FMM1561E Profile name profile_name does not point
earlier backup data was restored from an N–Series
to a file.
device, some data of a later backup will be destroyed.
Explanation: The profile specification should be a
System action:
fully qualified filename. Otherwise, it is assumed to be
User response: The backup is no longer complete and relative to the current directory of the command that
cannot be used for the requested operation. Try the issues the message, which may not be the desired
operation with a different backup. directory.
System action:
FMM1557I Device client is logging to path
User response: Correct the name.
Explanation: The device agent's log messages are
written to the file named.
FMM1562E Deleting the backup as requested is
System action: impossible while any part of it is
mounted.
User response: None.
Explanation: A request was sent to delete a backup.
However, some parts of the backup were still mounted.
FMM1558E There are no mount agents registered
Presumably, a restore operation or an off–loaded tape
for participant(s) participant_list
backup is pending or in progress. Please note that an
Explanation: During a snapshot backup run, TSM for offloaded tape backup requires the snapshot backups of
ACS detected that for the listed participant(s) no TSM all partitions of the database.
for ACS device agent was started with the 'force mount'
System action:
(–F) option. Typically, a participant corresponds to a
DB2 partition. The current snapshot backup run will be User response: Wait until the operation in progress
deleted. has ended, then issue the delete request again.
System action:
FMM1563I The snapshot backup defined by
User response: Make sure that for each participant
timestamp timestamp for instance
(DB2 partition) a TSM for ACS device agent is started
instance, database database_name, and
with the mount force option (–M) on the offload
partition partition_number cannot be
system.
restored.
Explanation: This message appears when backups are
FMM1559E Failed to verify consistency of
queried for a restore. It indicates that a snapshot
DataContainer (data_container)
backup was encountered that is not in a restorable
Explanation: During a snapshot backup run, TSM for state. For example, snapshot backups created with a
ACS detected that the listed data container (typically an FLASHCOPY_TYPE of NOCOPY are not restorable.
AIX volume group or an N Series volume) could not be When queried for restore, unrestorable snapshot
imported/mounted successfully on the offload system. backups are not returned to the caller and therefore
The current snapshot backup run will be deleted. cannot be selected for restore.

System action: System action:

User response: Check the TSM for ACS device agent User response: None.

78 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1564W • FMM1574I

because there is no corresponding backup in the

FMM1564W Backup id is marked for deletion. You
repository.
need to unmount before it can be
physically deleted. System action:
Explanation: A snapshot backup with the named id User response: Ignore the warning or try to delete the
can only be deleted if all of its assigned file systems are volume from the storage device manually.
unmounted successfully.
System action: FMM1571W The specified value for 'recon_interval' is
0. Be aware that every time a
User response: Issue the offload agent with the
background monitor is started a
command '–f unmount'. After all resources are freed,
reconcile will be scheduled so that other
the deletion of the snapshot backup will be started.
background operations will never be
scheduled. This should be used for
FMM1567I Reconciliation for device class 'device testing purposes only.
class' completed successfully.
Explanation: If RECON_INTERVAL is 0 every time a
Explanation: The reconciliation process for the background monitor is started it will start
specified device class was successful. The backup reconciliation. Other background operations as deletion
repository was synchronized with the existing backups or monitoring will never be scheduled.
on the storage device specified by the DEVICE_CLASS
System action:
parameter.
User response: Change RECON_INTERVAL to a value
System action: None.
greater than 0 if you want to avoid this behavior.
User response: None.
FMM1572I Starting reconciliation for device class
FMM1568I Removing backup backup_id from the 'device_class_name'
repository because it has not been found
Explanation: The reconciliation will be started for the
on the storage device during
device class device_class_name of the profile.
reconciliation.
System action:
Explanation: During reconciliation the backup with id
backup_id has not been found on the storage device. User response: None.
Therefore it is deleted from the repository to keep the
repository and the valid backups on the storage in
sync. FMM1573I The container 'volume_name' has been
successfully deleted from the storage
System action: box. It didn't belong to any backup in
the repository.
User response: None.
Explanation: The volume volume_name has been
successfully deleted from the storage box during
FMM1569I Updating backup backup_id in the
reconciliation because it didn't belong to any backup in
repository because some data was not
the repository.
found on the storage device during
reconciliation. System action:
Explanation: Backup data with the identifier backup_id User response: None.
is no longer available on the storage device. Depending
on storage device settings, the space from older
backups might be reused to create new backups. This FMM1574I Backup for hardware isolation key is
information is updated in the IBM Tivoli Storage created using DEVICE_CLASS device
FlashCopy Manager repository. class.

System action: Processing continues. Explanation: The current snapshot backup is using the
specified device class.
User response: None.
System action: None.

FMM1570W The following container could not be User response: None.

deleted from the storage box during
reconciliation: volume_name.
Explanation: The volume volume_name could not be
deleted from the storage box. It is not needed anymore

Chapter 2. FMM messages 79

FMM1575E • FMM1581E

FMM1575E product name cannot be used to perform FMM1578W A backup is skipped from expiration
dual backups. Update your profile to processing because of the following
perform either a disk–only backup or error:
use TSM for ERP to perform a dual
Explanation: A new backup request was started while
backup.
the specified backup is currently locked by another
Explanation: The backup cannot be started with the operation.
current configuration. TSM for ERP 6.1 or later is not
System action: None.
installed or configured in /usr/sap/<SID>/SYS/exe/
run. Instead, /usr/sap/<SID>/SYS/exe/run/backint User response: If you encounter an error message
points directly to the IBM Tivoli Storage FlashCopy FMM1579E after this warning message, wait until the
Manager backint. Offloaded backups from a snapshot operation that is locking the backup completes before
to IBM Tivoli Storage Manager is not allowed with this attempting a new backup. Otherwise, no action is
configuration. required as long a valid target set is specified for the
new backup.
System action: Processing ends.
User response: Update your profile to perform either
FMM1579E Failed to find a suitable target set for
a disk–only backup or use TSM for ERP to perform a
device class device class.
dual backup. .
Explanation: An available target set was not located
and an attempt was made to use the target set of the
FMM1576W The backup backup id is skipped from
oldest backup. However, this oldest backup target set is
expiration processing because it is
in a MOUNTING or MOUNTED state which prevents
mounted.
reuse. A target set containing a snapshot taken with the
Explanation: A new backup request was started while parameter TSM_BACKUP set to MANDATE will also
the specified backup is mounted on a backup system. prevent reuse, execpt when the Tivoli Storage Manager
The target set of the mounted backup cannot be reused backup is complete.
for a new backup.
System action: Processing stops.
System action: None.
User response: Make sure enough target sets are
User response: If you encounter an error message available and verify the state of the existing target sets.
FMM1579E after this warning message, unmount the
mounted backup before attempting a new backup.
FMM1580E Specifying a target volume serial
Otherwise, no action is required as long a valid target
number is mandatory for parameter
set is specified for the new backup.
'TARGET_VOLUME'.
Explanation: The parameter 'TARGET_VOLUME'
FMM1577W The backup backup id is skipped from
expects three values being defined. If these are not
expiration processing because a
present this error occurs.
mandatory Tivoli Storage Manager
backup from this image is pending. System action:
Explanation: A new backup request was started while User response: Specify the following values for
the specified backup is currently pending to be parameter 'TARGET_VOLUME': <target volume serial
offloaded to tape on a backup system. The backup number> <source volume serial number> <source
target set that is currently pending cannot be reused for volume size>. Only the first value is mandatory. If
a new backup. source volume information is omitted, dashes must be
entered in both fields as placeholders. Examples:
System action: None.
TARGET_VOLUME 401FCA90 40EFCA90 Size=2.0_GB
User response: If you encounter an error message TARGET_VOLUME 401FCA909 - -
FMM1579E after this warning message, start the
offloaded tape backup before attempting a new backup.
FMM1581E Error while parsing parameter
Otherwise, no action is required as long a valid target
TARGET_VOLUME target volume param
set is specified for the new backup. If you do not want
in volumes file: the parameter
to start the offloaded tape backup, update the usability
TARGET_VOLUME allows at most
state for this backup by issuing the tsm4acs -f
three parameters.
update_status command with the TSM_BACKUP=no
option. Explanation: The parameter 'TARGET_VOLUME'
expects three values being defined. If there are more
this error occurs.
System action:

80 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM1582I • FMM2000I

User response: Correct the specified values for

FMM1586E Not enough sessions available.
parameter 'TARGET_VOLUME' according to this
pattern: <target volume serial number> <source volume Explanation: The sum of available sessions specified
serial number> <source volume size>. Only the first in the various server statements does not cover the
value is mandatory. If source volume information is required numbe r of sessions.
omitted, dashes must be entered in both fields as
System action: Processing ends.
placeholders. Examples: TARGET_VOLUME 401FCA90
40EFCA90 Size=2.0_GB TARGET_VOLUME 401FCA909 User response: Change and adapt the values of the
-- corresponding parameters in the IBM Tivoli Storage
Manager for Enterpri se Resource Planning profile.
FMM1582I The target set target set will be used for
the current backup. FMM1588E The master password you provided does
not meet the minimum complexity
Explanation: IBM Tivoli Storage FlashCopy Manager
requirements. Acceptable master
allows to define target sets by a target set definition file
passwords are a minimum of minlength
(SVC and DS8000) or by a certain naming convention
characters and must contain at least one
by that IBM Tivoli Storage FlashCopy Manager
number and one letter.
determines the name of the target from the name of the
source volume and the name of the target set to be Explanation: For security reasons, the master
used for the current operation (SVC only). This password must meet minimum length and complexity
message reflects which target set is applied for the requirements. The master password must be a
current snapshot backup based on the given conditions. minimum of 8 characters and must contain at least one
number and one letter. The use of special symbols
System action:
increases the strength of the password.
User response: Specify means of target set selection by
System action: The password you provided is not
the profile parameter 'TARGET_SETS' and a target set
adopted.
definition file.
User response: Define a strong password that meets
the minimimum length and complexity requirements.
FMM1583W Backup agents were requesting
incompatible Tivoli Storage Manager
backup options. The composed states FMM1999E A restore operation is not allowed for a
are: 'states'. backup that was originally performed
with FLASHCOPY_TYPE NOCOPY
Explanation: A backup of a partitioned database was
from target volume targetVolume on San
attempted. Offloaded backups to Tivoli Storage
Volume Controller Version
Manager use options that are different from options
version.release.revision. Use San Volume
used with the partition backup. However, Tivoli
Controller Version 5.1 or later.
Storage Manager backup options for all partitions
should be identical. This can occur when different Explanation: A restore from backups performed with
device classes are used to back up different partitions, the FLASHCOPY_TYPE NOCOPY value is only
and those device classes are associated with different supported for San Volume Controller Version 5.1 or
Tivoli Storage Manager backup options. The product later.
automatically determines the correct Tivoli Storage
Manager backup options for this operation to prevent a System action: Command will fail.
failure. User response: Run the restore operation again with a
System action: The operation continues with warning. backup that was originally performed with
FLASHCOPY_TYPE INCR or FLASHCOPY_TYPE
User response: Update the configuration so that all COPY.
partitions use the same Tivoli Storage Manager backup
options during future operations.
FMM2000I Successfully connected to
component_name on port portnumber.
FMM1584E Snapshot backup referenced by ID
'backup id does not exist. Explanation: One of the Data Protection for SAP
modules BACKINT or theThe backup library libtdp_r3
Explanation: The specified backup ID was not found initiated a successful connection to the background
in the local snapshot repository. process component_name on port portnumber.
System action: Processing stops. System action:
User response: Use the inquire function to verify that User response: None.
the specified backup ID is valid.

Chapter 2. FMM messages 81

FMM2001E • FMM2010E

FMM2001E Socket error while connecting to FMM2006W The virtual machine 'vm name' with
component_name at host: reason. instance UUID 'source vm instance uuid'
will be processed without the requested
Explanation: The background process component_name
backup mode since fault tolerance is
is not running.
turned on.
System action:
Explanation: The specified virtual machine has fault
User response: Start component_name manually and try tolerance turned on. VMware is not able to
again. suspend/resume or create snapshots on virtual
machines with fault tolerance turned on. Thus this
virtual machine will be processed without doing so.
FMM2002E The group permissions of the user
'username' are not sufficient. The System action: Processing continues.
Oracle(R) executables have the group
User response: If the specified virtual machine backup
ownership 'group' but the specified user
mode should be processed as requested turn fault
does not belong to that group.
tolerance off for this virtual machine.
Explanation: The specified user has not enough
permissions to use the Oracle(R) executables.
FMM2007E Unknown Port: port
System action: Processing ends.
Explanation: The port specified for communication
User response: Add the specified group to the between component_name and BACKINT or the backup
specified user. library is unknown.
System action:
FMM2003I File file_name BID deleted.
User response: Check the port value specified when
Explanation: The file file_name with the backup ID component_name was started. Additionally, check the
<BID> was deleted from the Tivoli Storage Manager. environment variable PROLE_PORT for the BACKINT
environment. These two values must match.
System action:
User response: None. FMM2008E Unable to connect to component_name.
Explanation: Internal error.
FMM2004E Socket error while listen to port port
number - error: error text. System action:
Explanation: The application was unable to listen to User response: Contact IBM Support.
the port specified.
System action: Processing stops. FMM2009I Deleting backup version_number and all
older backups.
User response: Check if the process was already
started. Do not start a second instance of the same Explanation: All full database backups and their
process. Check if the port specified is in use by another corresponding log file backups will be deleted from
application and specifiy a different port number. Tivoli Storage Manager storage, if their version number
is less than or equal to version_number.

FMM2005W The virtual machine 'vm name' with System action:

instance UUID 'source vm instance uuid'
User response: None.
will be processed without the requested
backup mode since the 'device names'
devices are directly passed through to FMM2010E Error occurred processing FRONTEND.
the virtual machine.
Explanation: An error occurred during the frontend
Explanation: The specified virtual machine has processing.
passthrough devices, also known as VMDirectPath.
System action:
VMware is not able to suspend/resume or create
snapshots on such virtual machines. Thus this virtual User response: Check the frontend script/program
machine will be processed without doing so. and the settings in the Data Protection for SAP profile
(keyword FRONTEND) and try again.
System action: Processing continues.
User response: If the specified virtual machine backup
mode should be processed as requested remove the
passed through devices from this virtual machine.

82 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM2011E • FMM2023I

FMM2011E Error occurred processing BACKEND. FMM2018I The file system 'file system' was added
successfully to the remote cluster 'remote
Explanation: An error occurred during the backend
cluster name'.
processing.
Explanation: The specified file system was added
System action:
successfully to the remote cluster and is now ready to
User response: Check the backend script/program be mounted.
and the settings in the Data Protection for SAP profile
System action: Processing continues
(keyword BACKEND) and try again.
User response:
FMM2012E The specified user name or password is
not correct, authentication failed. FMM2019I The snapshot of file system 'file system'
was mounted successfully to 'path'.
Explanation:
Explanation: The specified snashot of the specified file
System action:
system was mounted successfully.
User response: Enter the correct user name and
System action: Processing continues
password.
User response:
FMM2013I Starting FRONTEND program.
FMM2020I The file system 'file system' was removed
Explanation: The frontend program is executing.
successfully from remote cluster 'remote
System action: cluster name'.

User response: None. Explanation: The specified file system was removed
successfully from the remote cluster.

FMM2014I FRONTEND program finished. System action: Processing continues

Explanation: The frontend program is finished. User response:

System action:
FMM2021I The file system 'file system' was
User response: None. unmounted successfully.
Explanation: The specified file system was unmounted
FMM2015I Starting BACKEND program. successfully.
Explanation: The backend program is executing. System action: Processing continues
System action: User response:
User response: None.
FMM2022E Unable to change mode of file file name:
FMM2016I BACKEND program finished. description

Explanation: The backend program is finished. Explanation: Unable to change mode of file file name.
description may contain the system error text.
System action:
System action:
User response: None.
User response: Check the description. If the error
persists, contact your service representative.
FMM2017I Blocksize is set to num_bytes bytes
Explanation: The operational blocksize is num_bytes FMM2023I The 'vm name' virtual machine with the
bytes. 'vm instance uuid' instance UUID is
System action: resumed.

User response: None. Explanation: The specified virtual machine is

resumed.
System action: Processing continues.
User response: No action is required.

Chapter 2. FMM messages 83

FMM2024E • FMM2088I

System action:
FMM2024E Error in connection to component_name.
User response: Contact IBM Support.
Explanation: The connection to component_name
terminated unexpectedly. This message might be
displayed due to previous errors or after an unexpected FMM2033E Cannot instantiate allocator of type
termination of the component_name process. allocator type with the following
additional properties: list of properties
System action:
Explanation: This is an internal error.
User response: Check for other error messages and
restart component_name if necessary. Try again. If the System action:
problem persists, contact IBM Support.
User response: Contact IBM Support.

FMM2025E Failed to respond to a message received

from component_name. FMM2086W The following failure groups were not
needed during the backup: serial. Either
Explanation: This is an internal error. they are misspelled in the profile or
they are not online. You might want to
System action:
check them.
User response: Contact IBM Support.
Explanation: The specified failure groups have not
been used for the backup. Either they have not been
FMM2026E Unexpected exception in handler: found or they are not online.
handler.
System action: Processing continues.
Explanation:
User response: You might want to check if the failure
System action: This is an internal error. groups you specified in the profile are spelled right. If
they are spelled right you might want to check if all of
User response: Contact IBM Support.
them are online.

FMM2027I Using TSM–API version your API version

FMM2087W The diskgroup 'dg' contains 'fg total'
(compiled with compiled with version).
failure groups, but currently only 'fg
Explanation: Version information about the TSM–API. online' of them are online. Just the
online failure groups can be included in
System action: the backup. During restore just the
User response: None. online failure groups would be restored
and the others would be dropped.

FMM2028W Unable to terminate a session due to the Explanation: Not all of the failure groups of the
following error: session. specified diskgroup are online. Just the failure groups
which are online can be included in the backup. During
Explanation: This is an internal error during cleanup a restore the failure groups included in the backup are
that has no effect on the success of the service. restored, the others are dropped.
System action: System action: Processing continues.
User response: None. User response: You might want to check if all failure
groups of the specified diskgroup are online and if not
FMM2029E Could not instantiate the buffer bring the online to include all of them in the backup.
allocator because of the following
incompatibility issue: expression. FMM2088I The diskgroup 'dg' and its online failure
Explanation: This is an internal error. groups: fg are now dropped.

System action: Explanation: The specified diskgroup and its failure

groups are dropped. Usually the customer will have to
User response: Contact IBM Support. recreate the failure groups which were not included in
the backup after having restored successfully.
FMM2031E A buffer allocator cannot System action: Processing continues.
simultaneously satisfy all of the
following properties: list of properties User response: After having restored you might want
to recreate the failure groups which have not been
Explanation: This is an internal error. restored.

84 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM2089W • FMM2094W

FMM2089W The diskgroup 'dg' contains failure FMM2092W A restore of the virtual machine 'vm
groups which are currently offline: fg. name' does not recover the existing
The diskgroup cannot be dropped from VMware snapshots because it has raw
these failure groups. Please ensure that device-mapping disks.
they do not become available during the
Explanation: In principle, raw device-mapping disks
restore process.
are not included in the IBM Tivoli Storage FlashCopy
Explanation: The specified failure groups are currently Manager backup. When you restore the virtual machine
offline. ASM cannot drop a diskgroup from failure it is not possible to revert to the existing VMware
groups which are offline. If these failure groups get snapshots. Because at the time when the VMware
online during the restore process this could result in an snapshots were taken, the raw device-mapping disks
inconsistent state. were still part of the virtual machine configuration.
System action: Processing continues. System action: Processing continues.
User response: Please ensure that the specified failure User response:
groups do not become online again during the restore
process.
FMM2093W The virtual machine 'vm name' has raw
device-mapping disks attached. When
FMM2090E The device 'dev' could not be removed. you restore this virtual machine from
Please ensure that you are not accessing the hardware snapshot the achieved
the ASM or database instance for consistency level is crash consistency
example by an open sqlplus console. only. This limitation does not apply
when you restore the virtual machine
Explanation: The specified device could not be
from the offloaded Tivoli Storage
removed from the OS because it is still in use. This
Manager backup.
might be caused by accessing the ASM or database
instance for example by an open sqlplus console. Explanation: In principle, raw device-mapping disks
are not included in the IBM Tivoli Storage FlashCopy
System action: Processing ends.
Manager backup. When you restore the virtual machine
User response: Please ensure that you don't access the from the hardware snapshot backup, it is not possible
database or ASM instance by any open SQL consoles. to revert to the VMware snapshot. Because at the time
when the VMware snapshot was taken, the raw
device-mapping disks were still part of the virtual
FMM2091W For the virtual machine 'vm name' the machine configuration. When the hardware snapshot
backup mode mode is changed to ASIS backup is offloaded to Tivoli Storage Manager and
because it has raw device-mapping restored from there, this limitation does not apply.
disks attached. As a consequence, the
backup of the specified virtual machine System action: Processing continues.
is only crash consistent.
User response: Restore the virtual machine from the
Explanation: In principle, raw device-mapping disks offloaded Tivoli Storage Manager backup to maintain
are not included in the IBM Tivoli Storage FlashCopy file system level consistency.
Manager backup. When you restore the virtual
machine, it is not possible to revert to the VMware
FMM2094W A file layout change was detected
snapshot. Because when the VMware snapshot was
during the backup of the virtual
taken, the raw device-mapping disks were still part of
machine 'vm name', this change was
the virtual machine configuration. The requested
probably caused by a VMware Storage
VMware snapshot is skipped before the actual
VMotion operation. The virtual machine
hardware snapshot is performed for this virtual
is excluded from the backup and cannot
machine.
be restored from this backup.
System action: Processing continues. The backup of
Explanation: A VMware Storage VMotion operation
the specified virtual machine is performed but with
might interfere with the snapshot backup process. It is
crash consistency only.
possible, that files are migrated to another data store
User response: To process the specified virtual that is not included in the backup while the backup is
machine backup mode as requested (including the in progress. As a result, these files cannot be restored at
VMware snapshot), remove the raw device-mapping a later time.
disks from the virtual machine configuration before the
System action: Processing continues.
backup.
User response: Ensure that a storage migration is not
occurring on the virtual machine and rerun the backup
task.

Chapter 2. FMM messages 85

FMM2095E • FMM4005E

User response: Check the error number error_num and

FMM2095E The backup is unusable because all the
the error description error_desc to avoid this problem in
virtual machines that it contains have
the future. An initial solution could be to set the
been invalidated due to an interfering
appropriate correct permission for the file file name
VMware Storage VMotion operation.
manually.
Explanation: A VMware Storage VMotion operation
might interfere with the snapshot backup process. It is
FMM4001E File 'file name' cannot be created. Reason:
possible, that files are migrated to another data store
errno(error_num) error_desc
that is not included in the backup while the backup is
in progress. As a result, these files cannot be restored at Explanation: The file file name to be restored could not
a later time. be created/written. It is possible, that you do not have
the appropriate rights for writing the file file name to
System action: Processing continues.
the destination path.
User response: Ensure that a storage migration is not
System action:
occurring on the virtual machines you selected for
backup and rerun the backup task. User response: Check the error number error_num and
the error description error_desc to avoid this problem in
the future. Furthermore, check the write permission of
FMM2096W The offload agent ('bexname') was not
the user who started the restore.
started. As a consequence, the snapshot
backup is not automatically offloaded to
IBM Tivoli Storage Manager. FMM4002E Error during write of file ' file_name'.
Reason: errno(error_num) error_desc
Explanation: The offload agent periodically checks for
new snapshot backups that are ready to offload to IBM Explanation: An error occurs during the restore
Tivoli Storage Manager. If the offload agent is not process of the file file name.
running as a daemon process, then the offload backup
is not automatically triggered. System action:

System action: Processing continues. User response: Check the error number error_num and
the error description error_desc to avoid this problem in
User response: Ensure that the offload agent is started the future.
by verifying that an entry is made to the inittab or by
configuring an upstart job. The setup scripts used by
IBM Tivoli Storage FlashCopy Manager can perform FMM4003E Operation mount will be aborted.
this task. Alternatively, you can manually trigger an Physical volume(s) with conflicting
offload backup or you can run a scheduled script to physical volume id(s) have been found
start the offload agent. For more information, see the on the target host 'host_name' list_of_pvids
IBM Tivoli Storage FlashCopy Manager Installation and Explanation: Physical volume(s) with one or more of
User's Guide. the physical volume id's which are part of this mount
operation do already exist on the target host.
FMM2913I The version delete setting is configured Continuing would cause conflicting physical volume
to retain number backup generations. id's.
Checking for expired backups. System action: Processing stops.
Explanation: The profile parameter MAX_VERSIONS User response: Cleanup the target system. Remove the
is configured to retain number backup generations. Data specified volume(s) containing the same physical
Protection for SAP is checking if surplus backups exist. volume id(s).
System action: Processing continues.
User response: None. FMM4005E Error allocating memory block for file
file name. BLOCKSIZE may be too large.

FMM4000W The attributes of file 'file name' cannot be Explanation: Unable to request new memory blocks
restored. Reason: errno(error_num) during the backup of file file name.
error_desc. System action:
Explanation: The file file name was restored User response: Verify that you have set a valid value
successfully but one or more file attributes (permission, for BLOCKSIZE. If you are not sure what value is
ownership, date/time) of the file file name cannot be valid, comment it out so the default value is used.
restored correctly. Furthermore, you can check if you have enough RAM
System action: available with your machine. Also, check the memory
usage during backup. It may be necessary to stop

86 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM4007E • FMM4017E

another application, increase memory, or change the

FMM4012E Unexpected EOF for file 'filename' after
configuration.
reading number Bytes.
Explanation: The end of file was reached
FMM4007E File 'filename' cannot be read Reason:
unexpectedly.
errno(error_num) error description
System action:
Explanation: Data could not be read due to some
system error. Check error description for further User response: Check the logs for further information.
information. If this error recurs, this might indicate If the problem cannot be resolved contact your IBM
some hardware problems. support personnel.
System action:
FMM4013I CreateFile() with
User response: Contact your system administrator.
dwFlagsAndAttributes='attribute'.
Explanation: A file with the nmed attribute was
FMM4008E File 'filename' cannot be opened. Reason:
created.
errno(error_num) error_text
System action:
Explanation: Could not open the file file name due to
some system specific problems. User response: None.
System action:
FMM4014E File 'filename' cannot be accessed.
User response: Contact your system administrator.
Reason: errno<(number) errormsg
Explanation: A named file could not be accessed
FMM4009E Not enough space to write File 'filename'.
either for reading or writing.
Possible reasons: disk full or ulimit
exeeded. System action:
Explanation: The system rejected a request to write User response: Check the file permissions and if
data into file file name. The storage media might not necessary adjust them accordingly. Try again.
have enough free space to keep the file or the system
rejected writing the file due to administrative resource
FMM4015E Failed to attach the volumes 'volumes' to
constraints such as ulimits.
the host 'hostname'.
System action:
Explanation: IBM Tivoli Storage FlashCopy Manager
User response: Contact your system administrator. was not able to attach these volumes to the host for
mount.
FMM4010E SAP requires the file filename to be a System action: Processing ends.
regular file.
User response: Verify the CIM error.
Explanation: To be able to support SAP environments
the named file has to be a regular file.
FMM4016W The mapping between volume 'vol' and
System action: the host 'hostname' was not found in the
CIMOM.
User response: Check the logs for further information.
If the problem cannot be resolved contact your IBM Explanation: IBM Tivoli Storage FlashCopy Manager
support personnel. did not found the map volume to host in the CIMOM.
System action: Processing continues.
FMM4011W The backup device type (filetype backup
User response: None.
devicetype backup devsubtype) differs from
the restore device type (filetype restore
descr1 descr2) for name. FMM4017E Failed to detach the volumes 'volumes'
from the host 'hostname'.
Explanation: A mismatch between the device types
during backup and restore was detected. Explanation: IBM Tivoli Storage FlashCopy Manager
was not able to detach these volumes from the host
System action:
after the unmount.
User response: Check the logs for further information
System action: Processing ends.
User response: Verify the CIM error.

Chapter 2. FMM messages 87

FMM4018E • FMM4176E

System action: Processing ends.

FMM4018E Parameter parameter name requires a
value in the range between min and max. User response: Identify the datastores that are
currently using these LUNs and delete the datastores in
Explanation: The value specified for the named
the vCenter Server, then retry the operation again.
parameter does not comply with the defined range of
values.
FMM4023E The new datastorename datastore, which
System action:
was identified to be overwritten by the
User response: Check the named profile keyword and instant restore, does not use all the
make appropriate adjustments. LUNs of the original datastore. Remove
this datastore and corresponding virtual
machines from the vCenter Server and
FMM4019E The hostname 'hostname' must be
retry the instant restore operation again.
defined as a host entry in the IBM SAN
Volume Controller. Explanation: After a backup the datastore was deleted
and some of the disks has been reused to create a new
Explanation: IBM Tivoli Storage FlashCopy Manager
datastore. This message is issued to alert you to the fact
was not able to find the hostname specified as a valid
that the newly created datastore and virtal machines
host entry in the IBM SAN Volume Controller. This
will be overwritten.
value is specified in the profile by the parameter
BACKUP_HOST_NAME. System action: Processing ends.
System action: Processing ends. User response: Delete the datastore that is named in
this error message from the vCenter Server, then try the
User response: Verify the value specified in the profile
instant restore operation again.
and ensure that it is a valid host in the IBM SVC
Volume Controller.
FMM4024E This backup version was created with a
previous version of the product that
FMM4021E The FlasCopy mapping for the source
does not support datastore restore
and target volumes 'src' and 'tgt' was
(instant restore). Create a new backup to
found, however the consistency group is
enable the instant restore function. You
missing.
can restore the backup by using a
Explanation: IBM Tivoli Storage FlashCopy Manager virtual machine restore operation.
was not able to find the consistency group for the
Explanation: The instant restore failed because the
existing mapping of the soruce and target volumes
backup version was old and does not support instant
specified.
restore. It is still possible to use a virtual machine
System action: Processing ends. restore function.

User response: The state found in the storage System action: Processing ends.
subsystem is not supported for a re-start of the
User response: Create a new backup of your
FlashCopy. The consistency group and the FlashCopy
datastores to enable instant restore for the datastores. It
mappings are created by IBM Tivoli Storage FlashCopy
is still possible to do a virtual machine restore from an
Manager and re-use during refreshing of the
old backup.
FlashCopy. A manually cleaup should be evaluated in
this case.
FMM4175E San Volume Controller VDisk vdisk is
not online. Please retry this command
FMM4022E The LUN serial numbers Lun serials that
after bringing this volume back online.
were used by the original datastore are
now in use by the following datastores: Explanation: Either the source or the target VDisk is
new datastore names Ensure that the LUNs no longer online.
are not in use by other datastores, by
System action: Command will fail.
removing the datastores that are
conained by these LUNs from the User response: Please retry the command after
vCenter Server. bringing the VDisk back online.
Explanation: After a backup the datastore was deleted
and the disks are reused to create new datastores. IBM FMM4176E A restore is not allowed from
Tivoli Storage FlashCopy Manager overwrites the space–efficient target volume
content of disks during an instant restore. Therefore, targetVolume on San Volume Controller
verify that the disks are not in use to ensure that the Version version.release.revision. Use San
instant restore can complete successfully. Volume Controller Version 5.1 or later.

88 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM4177E • FMM4186E

Explanation: Restore from Space–efficient target mirror remote copy relations is different from that at
volumes is only supported on San Volume Controller the time of backup.
Version 5.1 or later.
System action: Processing ends.
System action: Command will fail.
User response: Add the missing metro mirror or
User response: Run the restore operation with a global mirror remote copy relations to the consistency
backup that was performed using a full volume target. group. Try the operation again.

FMM4177E User specified copy type usrCopyType is FMM4183I Performing flashcopytype FlashCopy of
in conflict with the copy type fcCopyType source volume source to target volume
for the previously established target.
FlashCopy. Please retry the operation for
Explanation: Indicates which type of FlashCopy is
this copy type specifying a different
performed and which source and target volumes are
target set.
used.
Explanation: The previously established FlashCopy
System action:
maps are used for a specified copy type for all backups
that use the same copy type. User response: None.
System action: Command will fail.
FMM4184I CIM Agent version for hwType:
User response: Run the operation again with a
'version.release.revision'.
different target set in order to use this copy type.
Explanation: Provides the CIM Agent version.
FMM4178E The directory 'directory' containing the System action:
CIM components is missing.
User response: None.
Explanation: The CIM components (a collection of
different libraries) must reside in a directory within a
specific pegasus-directory. The directory has to be FMM4185E The mandatory source and target
created under the pegasus-directory where the device FlashCopy mapping source / target cannot
agent can be found. be satisfied because the volumes do not
match.
System action: Processing ends.
Explanation: The source to target mappings specified
User response: Make sure that the pegasus-directory in the target volumes file are invalid. Either the
is created under the location where the device agent volumes are located in different SAN Volume
exists. If this required pegasus-directory is not Controller clusters or the volume size does not match.
available, it can be manually copied from the default
FlashCopy Manager installation directory to the System action:
required location. User response: Correct the target volumes file and try
the operation again.
FMM4179E Metro mirror or global mirror remote
copy relations for source 'source vdisk' do FMM4186E For the sources source no matching target
not have a consistency group defined. LUN could be found in the selected
Explanation: Metro mirror or global mirror remote target set.
copy relations have not been added to a consistency Explanation: The selected target set from the target
group. volumes file has no matching volume for the source
System action: Processing ends. volume. Either the volumes are located in different
SAN Volume Controller clusters or the volume size
User response: Add the metro mirror or global mirror does not match.
remote copy relations to a consistency group. Try the
operation again. System action:
User response: Update the target volumes file to
FMM4180W The current number of metro mirror or provide target sets which have matching target
global mirror remote copy relations volumes for the source volumes.
'current num of rc relations' is different
from the number at the time of backup
'original num of rc relations'.
Explanation: The number of metro mirror or global

Chapter 2. FMM messages 89

FMM4187E • FMM4195I

FMM4187E The LUN with serial number 'serial' is FMM4190I All source/target pairs are in an
not known by the configured CIM incremental FlashCopy relation.
Agent 'primaryserver' of storage system
Explanation: The FlashManager device agent found
type 'hardwaretype'.
already established FlashCopy relations and will try to
Explanation: The device agent communicates with the re-use them.
storage CIM agent to get information about the LUNs.
System action: Processing continues.
However, the connected CIM Agent did not find
information for the LUN identified by this serial User response: None.
number. Verify that the correct device class is used, and
that the missing LUN resides on the specified CIM
agent of the specified storage system type. FMM4191I No source/target pairs are in an
incremental FlashCopy relation.
System action: Processing stops.
Explanation: The FlashManager device agent was not
User response: Verify with the storage GUI or CLI able to find FlashCopy relations for the volumes
that the CIM agent is working and the concerned LUN involved in this backup. The relations will now be
is available. Another cause of this error is when the established.
storage system of the disks are not of the type specified
by the parameter System action: Processing continues.
COPYSERIVICES_HARDWARE_TYPE. See the User response: None.
description of this parameter in the User's Guide. Use
AIX commands to figure out the type of the storage.
For example, lscfg -pvl 'hdisknnn' or lsdev -Cc disk. FMM4192I Not all source/target pairs are in an
Ensure that each copy of the database is residing on incremental FlashCopy relation.
disks of the same storage system type. Ensure that the Explanation: The FlashManager device agent found
right device class has been used and that the missing some of the FlashCopy relations established, some not.
LUN resides in the specified CIM agent of the specified The missing relations will be established.
storage system type.
System action:

FMM4188E The target volume named volname is not User response: None.
known by the CIM Agent in the cluster
cluster. FMM4193E The DB2 instance owner instanceowner
Explanation: The device agent communicates with the could not be found in /etc/passwd.
storage CIM agent to get information about the LUNs. Explanation: This function is only allowed for DB2.
However, the connected CIM Agent did not find Your DB2 instance must have the same name as the
information for the LUN identified by this volume DB2 instance owner as specified in /etc/passwd.
name and cluster name.
System action: Processing ends.
System action: Processing stops.
User response: Please make sure you start this
User response: Verify with the storage GUI or CLI function as DB2 instance owner.
that the CIM agent is working and the concerned LUN
is available.
FMM4194I All virtual machines that are located
within the 'datastore name' data store are
FMM4189E The cluster id clustername; specified by powered down and unregistered.
the parameter parname; is not known by
the CIM Agent. Explanation: All virtual machines that are located
within the specified data store are powered down and
Explanation: The FlashManager device agent unregistered.
communicates with the storage CIM agent to get
information about the LUNs. However, for the cluster System action: Processing continues.
identified by this id or name no information was found
User response: No action is required.
in the CIM agent current connected.
System action: Processing stops.
FMM4195I The 'vm name' virtual machine is
User response: Verify with the storage GUI or CLI successfully restored and registered at
that the CIM agent is working and the concerned the 'ESX host name' ESX host.
cluster is available.
Explanation: The specified virtual machine was
successfully restored and registered.
System action: Processing continues.

90 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM5000E • FMM5012E

User response: No action is required

FMM5006E Tivoli Storage Manager Error:
error_message
FMM5000E Tivoli Storage Manager Error:
Explanation: See FMM5001E.
error_message
System action:
Explanation: During a connection of Data Protection
for SAP to Tivoli Storage Manager server, a Tivoli User response: See FMM5001E.
Storage Manager error error_message occurred.
System action: FMM5007E Tivoli Storage Manager Error.
User response: Use the Tivoli Storage Manager Explanation: See FMM5001E.
Messages guide and correct the Tivoli Storage Manager
System action:
server error. Try your last action again.
User response: See FMM5001E.
FMM5001E Tivoli Storage Manager Error:
error_message FMM5008E Tivoli Storage Manager Error.
Explanation: During a connection of Data Protection Explanation: See FMM5001E.
for SAP to Tivoli Storage Manager server, a Tivoli
Storage Manager error error_message occurred. System action:

System action: User response: See FMM5001E.

User response: Use the Tivoli Storage Manager

Messages guide and correct the Tivoli Storage Manager FMM5009E Tivoli Storage Manager Error:
server error. Try your last action again. error_message
Explanation: See FMM5001E.
FMM5002E Tivoli Storage Manager Error during System action:
inquire of mux file backup_id:
error_message User response: See FMM5001E.

Explanation: See FMM5001E.

FMM5010E Tivoli Storage Manager Error:
System action: error_message
User response: See FMM5001E. Explanation: See FMM5001E.
System action:
FMM5003E Tivoli Storage Manager Error:
error_message User response: See FMM5001E.

Explanation: See FMM5001E.

FMM5011E Tivoli Storage Manager Error:
System action: error_message
User response: See FMM5001E. Explanation: See FMM5001E.
System action:
FMM5004W Tivoli Storage Manager Error:
error_message User response: See FMM5001E.

Explanation: See FMM5001E.

FMM5012E Cannot open Tivoli Storage Manager
System action: API message text file. Check if
User response: See FMM5001E. DSMI_DIR is set correctly. Current
value of DSMI_DIR is: dsmi dir

FMM5005E Tivoli Storage Manager Error. Explanation: The Tivoli Storage Manager API is
unable to open the message text file. This file is
Explanation: See FMM5001E. required in order to issue messages. By default, it
should reside in the Tivoli Storage Manager API
System action:
installation directory. If the Tivoli Storage Manager API
User response: See FMM5001E. is installed in another location, use the DSMI_DIR the
environment variable to specifiy the correct location.
System action: Processing stops.

Chapter 2. FMM messages 91

FMM5013E • FMM5022W

User response: Verify that the DSMI_DIR environment

FMM5018E The requested buffer has a size
variable points to the correct location and that the
(current_size bytes) that is smaller than
Tivoli Storage Manager API installation is complete.
requested requested_size.
Explanation: The request for a new buffer was
FMM5013E Value for name is too long. Current
successful. The buffer, however, does not have the
value: value
requested size.
Explanation: The value of the environment variable
System action:
name has too many digits.
User response: Check if the system is running low on
System action:
memory and retry the action. If the error occurs again
User response: Check if the variable is set correctly. contact IBM Support.

FMM5014E Tivoli Storage Manager Error: FMM5019E Error during delete of object filename:
error_message object

Explanation: See FMM5001E. Explanation: A named file could not be deleted from a
TSM server.
System action:
System action:
User response: See FMM5001E.
User response: Check the logs for further information.
If the problem cannot be resolved contact your IBM
FMM5015W Data description, file name could not be support personnel.
restored, because it was backed up with
a newer version (objInf_support
information). FMM5020E Error while deleting objects : objects
Explanation: The TSM server hosts backups (data Explanation: One or more named objects could not be
description) which were made with a new version of deleted from a TSM server.
backint or backom, which ignores this data in further
System action:
processing.
User response: Check the logs for further information.
System action:
If the problem cannot be resolved contact your IBM
User response: Upgrade the product. support personnel.

FMM5016I Time: current time New TSM session FMM5021W No data is deleted on the TSM Server
created: MGMNT–CLASS: because the environment variable
management_class, TSM–Server: "XINT_FUNCTION_DELETE" is set to
server_name, type: session_type "DISABLE".
Explanation: A new session to TSM server server_name Explanation: The delete function was disabled
has been established at current_time. Data will be stored temporarily.
in management class management_class.
System action:
System action:
User response: If the delete function has to be
User response: None. re–activated, unset the environment variable
XINT_FUNCTION_DELETE and try again.

FMM5017E Internal Tivoli Storage Manager Error:

Transaction succeeded although it was FMM5022W Error during version delete. Not all
expected to fail. backups that should have been expired
could be removed.
Explanation: An internal Tivoli Storage Manager error
occurred. Explanation: The database backup finished
successfully. Nevertheless, the deletion of expired
System action: backup sets failed.
User response: Retry the action. If the error occurs System action:
again contact IBM Support.
User response: Check the logs for further information.
If the problem cannot be resolved contact your IBM
support personnel.

92 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM5637I • FMM6206E

User response: Check the output of the failed

FMM5637I SAN Volume Controller CIM Agent
command for further information about the root cause.
version is: version.msgnl;
Resolve these issues and perform the operation again.
Explanation: The San Volume Controller CIM Agent
version.
FMM6201I Checking status of database.
System action: Processing continues.
Explanation: The actual status of the database will be
User response: None. checked to ensure a valid state for the subesquent
operation.
FMM5651E Incorrect copy type copyType has been System action:
specified for space–efficient target
User response: None.
volume targetVolume. Please retry this
command using NOCOPY copy type.
FMM6202E The log mode for this database is
Explanation: It is inefficient to perform COPY or
NOARCHIVELOG.
INCR type of flashcopy backup with space–efficient
target volumes as it will force the space–efficient Explanation: The log mode for this database is
volumes to grow to full size on the very first backup. NOARCHIVELOG.
Use NOCOPY copy type instead.
System action:
System action: Command will fail.
User response: Change the log mode for this database
User response: Please retry the command using to ARCHIVELOG.
NOCOPY copy type.

FMM6203E The Oracle database is currently in

FMM5667E A Flashcopy Restore operation is in read–only mode.
progress between source volume
sourceVolume and target volume Explanation: The Oracle database is currently
targetVolume. Please retry this command designated as read–only. Processing stops.
after the restore operation completes. System action:
Explanation: It is not possible to perform other User response: Remove the read–only mode of the
Flashcopy backup or restore operations using this Oracle database and try again.
source until the currently running FlashCopy restore
operation completes.
FMM6204E The Backup type is online but the
System action: Command will fail. mount mode is either nomount or
User response: Please retry the command after the startup restricted.
Flashcopy restore operation completes. Explanation: The Backup type is online but the mount
mode is either nomount or startup restricted.
FMM5668E The input target volume targetVolume is System action:
already in a flashcopy relationship with
a volume other than the input source User response: Change the mount mode to startup
sourceVolume. Please retry this command mount.
with a different target volume.
Explanation: It is not allowed to use a given volume FMM6205I Changing Oracle mode to: mode.
as the target for more than one flashcopy relationship. Explanation: The operational mode of the Oracle
System action: Command will fail. database is changed to the named mode.

User response: Please retry the command using a System action:

different target volume. User response: None.

FMM6199E Failed to determine the database id. FMM6206E No table space was found for the Oracle
Output of the failed command: output database.
Explanation: The attempt to determine the database id Explanation: No table space was found for the Oracle
was unsuccessful. Requirements for this operation are a database.
complete and functional database software installation
and a valid control file. System action:

System action: Processing stops.

Chapter 2. FMM messages 93

FMM6207E • FMM6217I

User response: Make sure the correct database system

FMM6212I Suspend database.
identifier (SID) is specified.
Explanation: The Oracle database to be flashed is
going to be supended.
FMM6207E Oracle database data files were not
found. More details: errormsg System action:
Explanation: IBM Tivoli Storage FlashCopy Manager User response: None.
was unable to determine the names of the data files
that are used by the database.
FMM6213E An error occurred while attempting an
System action: Processing stops. 'alter system suspend' action. More
details: errormsg
User response: Check the errormsg for more
information about the cause of this problem. Explanation: An error occurred while attempting an
'alter system suspend' action. Details can be found in
the named message.
FMM6208E Oracle database control files were not
found. System action:
Explanation: Oracle database data files were not User response: Make sure the Oracle database to be
found. backed up is running, then try to suspend the system
with a command line invocation. If the system
System action:
suspends successfully, run the operation again.
User response: Make sure the correct database system
identifier (SID) is specified.
FMM6214I Resume database.
Explanation: The Oracle database to be flashed is
FMM6209E The database failed to shutdown during
going to be resumed.
the flashcopy operation.
System action:
Explanation: The database attempted to shutdown
because the backup type parameter is set to offline. The User response: None.
database failed to shutdown.
System action: FMM6215E An error occurred while attempting an
'alter system resume' action. More
User response: Manually shutdown the database you
details: errormsg
are trying to back up, then run the operation again.
Explanation: An error occurred while attempting an
'alter system resume' action. Details can be found in the
FMM6210E Failed to open the output file: filename
named message.
Explanation: The named output file could not be
System action:
opened.
User response: Make sure the Oracle database to be
System action:
backed up is running, then try to resume the system
User response: Either the file doesn't exist or the with a command line invocation. If the system resumes
permissions are not sufficient for the requested successfully, run the operation again.
operation. Check that the directory exists where an
attempt is being made to access the output file and that
FMM6216E Failed to get Oracle version information.
sufficient permissions are granted. Try again.
Explanation: Failed to get Oracle version information
using sqlplus.
FMM6211E Failed to copy the database controlfile.
Please check log file 'filename'. System action:
Explanation: The Oracle database control file doesn't User response: Check the logs for further information.
exist. If the problem cannot be resolved contact your IBM
support personnel.
System action:
User response: Make corrective actions regarding the
FMM6217I Database switched to next logfile.
information to be found in the named log file and try
again. Explanation: The database switched to the next logfile.
System action:
User response: None.

94 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6218E • FMM6229I

FMM6218E Backup ID to delete not specified. FMM6224I Create control file copy: control file
Explanation: To delete a backup a valid backup id has Explanation: A named Oracle control file copy will be
to be specified. created.
System action: System action:
User response: Specifiy a valid backup id and try User response: None.
again.
FMM6225I Create database parameter file 'filename'
FMM6219I Backup to Tivoli Storage Manager: from SPfile.
filename
Explanation: A named Oracle database parameter file
Explanation: Backing up the named file to Tivoli will be created.
Storage Manager.
System action:
System action:
User response: None.
User response: None.
FMM6226E Default directory for database parameter
FMM6220E Another clone with clone database name file 'filename' not found.
'clone database name' is already mounted
Explanation: The name Oracle parameter file could
on a clone server using device class
not be found within the default directory.
'device classes'.
System action:
Explanation: The requested 'create_clone' command
cannot continue due to another clone with the specified User response: Ensure a valid Oracle parameter file
name is still mounted on a clone server using the exists in the default directory and try again.
specified device class(es).
System action: Processing ends. FMM6227I Parameter 'database_control_file_restore'
is set to yes in the profile. You will need
User response: Either issue explicitly the 'delete_clone'
to do the incomplete recovery after the
command to release resources on the clone server or, if
restore.
possible, issue the 'refresh_clone' command, which
implicitly triggers the deletion of a clone prior starting Explanation: The Oracle database control file is
a new one. requested for restore.
System action:
FMM6221I Database profile: filename
User response: None.
Explanation: Using the named database profile.
System action: FMM6228E The database seems to be running.
Restore not possible.
User response: None.
Explanation: A running Oracle database was detected
and therefore a restore is not possible.
FMM6222E Database profile 'filename' not found.
System action:
Explanation: The named database profile was not
found. User response: Check if the started restore operation
is valid. If yes, stop the running database and try again.
System action:
User response: Check if the named profile exists and
FMM6229I Restoring control file controlfile
try again.
Explanation: The named control file will be restored.
FMM6223I Detected control file: filename System action:
Explanation: The named Oracle control file was User response: None.
found.
System action:
User response: None.

Chapter 2. FMM messages 95

FMM6230I • FMM6241E

for further information. If the problem cannot be

FMM6230I Set table space files in backup mode.
resolved contact your IBM support personnel.
Explanation: The table space files of the participating
table spaces will be set in backup mode.
FMM6237E Backup failed. Please check RMAN log.
System action:
Explanation: The offloaded backup to Tivoli Storage
User response: None. Manager using RMAN failed.
System action:
FMM6231I End backup mode for table space files.
User response: Make corrective actions regarding the
Explanation: The backup mode for table space files of information to be found in the named log file and try
the participating table spaces will be reset. again.
System action:
FMM6238E Failed to switch logfiles. This is the
User response: None.
output of the failed command: output
Explanation: The command failed.
FMM6232I Looking for the latest backup.
System action:
Explanation: An attempt is being made to pick the
most current valid backup image for the requested User response: Check the logs and the named output
operation. for further information. If the problem cannot be
resolved contact your IBM support personnel.
System action:
User response: None.
FMM6239E Failed to detect read mode. This is the
output of the failed command: output
FMM6233I Restoring backup with ID id.
Explanation: The command failed.
Explanation: The backup with the named id will be
System action:
restored.
User response: Check the logs and the named output
System action:
for further information. If the problem cannot be
User response: None. resolved contact your IBM support personnel.

FMM6234E No backup found which could be FMM6240E Failed to create a pfile from spfile. This
restored. is the output of the failed command:
output
Explanation: There was no snapshot backup found
which can be restored. Explanation: The command failed.

System action: System action:

User response: Verify your environment. If one or User response: Check the logs and the named output
multiple valid snapshot backup exist and the restore for further information. If the problem cannot be
still fails, contact your IBM support personnel. resolved contact your IBM support personnel.

FMM6235I Deleting backup with ID id. FMM6241E The tablespace file 'filename' is a link but
not a real file.
Explanation: The named snapshot backup is going to
be deleted. Explanation: The named tablespace file has to be a
real file. Instead, a link was detected.
System action:
System action:
User response: None.
User response: Verify your environment. If the
problem cannot be resolved contact your IBM support
FMM6236E Failed to delete backup with ID id. personnel.
Reason: reason
Explanation: The snapshot backup with the named id
could not be deleted.
System action:
User response: Check the logs and the named output

96 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6242E • FMM6252E

FMM6242E Raw devices are not supported. FMM6248W No device has been found for the
('devicename') character device 'devicename' with major
number 'major' and minor number
Explanation: Raw devices are currently not supported.
'minor'.
System action:
Explanation: No corresponding device has been found
User response: For further details on this issue, for the character device with 'devicename'. That means
contact your IBM support personnel. that no corresponding hdisk has been found in the OS
for the ASM device which is matched using minor and
major number of the device.
FMM6243E Failed to excute sql cmd 'command' on
host 'hostname'. This is the output of the System action: Processing continues.
failed command: output
User response: Ensure that an hdisk exists in /dev
Explanation: The named sql command failed. which has the mentioned minor and major numbers.

System action:
FMM6249W The diskgroup 'dg' contains failure
User response: Check the logs and the named output groups which are currently offline: fg.
for further information. If the problem cannot be These failure groups cannot be included
resolved contact your IBM support personnel. in the flashcopy.
Explanation: The specified failure groups are currently
FMM6244I Received an information message from offline. They cannot be included in the flashcopy and
the adapter: info_message are thus not counted as valid failure groups.
Explanation: Indicates that this information message System action: Processing continues.
was received from a device adapter.
User response: If you have to less failure groups to
System action: perform a flashcopy you may want to bring these
User response: None. failure groups online so that they can be included in
the flashcopy.

FMM6245I source volume ID: serialnumber capacity:

size FMM6250E Error during initialization: descritpion

Explanation: The physical volume with the serial Explanation: An error resulting in the named
number shown has a capacity of size. description was detected during the initialization phase
of a snapshot backup.
System action:
System action:
User response: None.
User response: Check the logs for further information.
After resolving the issue try again.
FMM6246I Total managed capacity: size
Explanation: The total amount of all physical volumes FMM6251E Error during start of backup: description
protected by IBM Tivoli Storage FlashCopy Manager is
shown. Explanation: An error resulting in the named
description was detected during the start of a snapshot
System action: backup.
User response: None. System action:
User response: Check the logs for further information.
FMM6247W No serial number has been found for After resolving the issue try again.
device: devicename
Explanation: The serial number of the specified device FMM6252E Error during partitioning: description
could not be resolved.
Explanation: An error resulting in the named
System action: Processing continues. description was detected during the partitioning phase
User response: No serial number has been found for of a snapshot backup.
the specified device. Please ensure that is available on System action:
your host.
User response: Check the logs for further information.
After resolving the issue try again.

Chapter 2. FMM messages 97

FMM6253E • FMM6263E

FMM6253E Error during preparation of snapshot: FMM6258E Error during query–initialization:

description description
Explanation: An error resulting in the named Explanation: An error resulting in the named
description was detected during the preparation phase description was detected during the snapshot
of a snapshot backup. query–initialization phase.
System action: System action: Check the logs for further information.
After resolving the issue try again.
User response: Check the logs for further information.
After resolving the issue try again. User response:

FMM6254E Error during creation of snapshot: FMM6259E Error during retrieval of query
description information: description
Explanation: An error resulting in the named Explanation: An error resulting in the named
description was detected during the creation of a description was detected during retrieval of query
snapshot backup. information of a snapshot backup.
System action: System action:
User response: Check the logs for further information. User response: Check the logs for further information.
After resolving the issue try again. After resolving the issue try again.

FMM6255E Error during verification of snapshot: FMM6260E Error during end of query: description
description
Explanation: An error resulting in the named
Explanation: An error resulting in the named description was detected during the end of query for
description was detected during the verification phase snapshot phase.
of a snapshot backup.
System action:
System action:
User response: Check the logs for further information.
User response: Check the logs for further information. After resolving the issue try again.
After resolving the issue try again.
FMM6261E Error during start of restore: description
FMM6256E Error during write of meta–information:
Explanation: An error resulting in the named
description
description was detected during the start of the
Explanation: An error resulting in the named snapshot restore phase.
description was detected during write of
System action:
meta–information assigned to a snapshot backup.
User response: Check the logs for further information.
System action:
After resolving the issue try again.
User response: Check the logs for further information.
After resolving the issue try again.
FMM6262E Error during restore: description
Explanation: An error resulting in the named
FMM6257E Error during retrieval of meta data:
description was detected during the restore of a
description
snapshot backup.
Explanation: An error resulting in the named
System action:
description was detected during retrieval of meta data
assigned to a snapshot backup. User response: Check the logs for further information.
After resolving the issue try again.
System action:
User response: Check the logs for further information.
FMM6263E Error during end of restore: description
After resolving the issue try again.
Explanation: An error resulting in the named
description was detected during finishing of a snapshot
restore operation.
System action:
User response: Check the logs for further information.

98 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6264E • FMM6272I

After resolving the issue try again. storage device please ensure that is is available. If the
failure group is not contained on the currently selected
storage device you can ignore this message.
FMM6264E Error during start of delete: description
System action: Processing continues.
Explanation: An error resulting in the named
description was detected during the start of the User response: Ensure that the specified lun exists on
snapshot delete phase. the storage device if you expect the failure group to
reside on the currently selected DEVICE_CLASS in the
System action:
profile.
User response: Check the logs for further information.
After resolving the issue try again.
FMM6269I The diskgroup 'diskgroupname' with
'redundanctype' redundancy and
FMM6265E Error during end of delete: description 'failuregroupnumber' failure groups has
been partitioned with failure groups
Explanation: An error resulting in the named 'failuregroupnames'.
description was detected during finishing of a snapshot
delete operation. Explanation: The specified diskgroup has been
partitioned. In this message the found failure groups
System action: and the total number of failure groups is mentioned. It
User response: Check the logs for further information. can be used to check if all failure groups which were
After resolving the issue try again. expected to be included in the flashcopy are listed.
System action: Processing continues.
FMM6266E Restoring Oracle control files failed. User response: None.
Oracle control files are on raw volumes
in the production server and those are
supposed to be created manually on the FMM6270E INFILE name is required.
backup server. It failed because of either
Explanation: For this function an INFILE name has to
control files are not created on the
be specified either in the profile or via command line
backup server or created incorrectly.
parameter.
Please check log file 'filename'.
System action: Processing ends.
Explanation: On the production server the Oracle
control files reside on raw volumes. On the backup User response: Either specify an INFILE parameter in
server they need to be restored in order to perform the the client section of the profile or add parameter -I
backup to Tivoli Storage Manager. This process did fail. <infile name> to the command.
System action:
FMM6271W Specified partition(s) 'partition list'
User response: Examine the content of the filename. It
already offloaded to Tivoli Storage
contains the output from the Oracle RMAN. A possible
Manager.
reason could be that the raw devices for the control
files have not been created on the backup server. Explanation: The provided database partitions were
already offloaded to Tivoli Storage Manager. The
backup for those partitions will not be started again.
FMM6267E Restoring Oracle control files failed.
Please check log file 'filename'. System action: Processing continues.
Explanation: On the backup server the Oracle control User response: Provide different partitions to be
files need to be restored in order to perform the backup offloaded.
to Tivoli Storage Manager. This process did fail.
System action: FMM6272I Update snapshot backup with ID
'snapshot backup ID'.
User response: Examine the content of the filename. It
contains the output from the Oracle RMAN. Explanation: The usability state of the given snapshot
backup was updated successfully according the
provided state parameter.
FMM6268W The lun 'lunname' of failure group
'failuregroupname' has not been found on System action: Processing continues.
the storage device.
User response: None.
Explanation: The specified lun has not been found on
the currently selected storage device. If it is contained
in a failure group you expect to reside on the selected

Chapter 2. FMM messages 99

FMM6273E • FMM6280E

system(s). There must be a one to one relation between

FMM6273E Valid usability state values are 'yes' or
the mount agent and a dedicated partition.
'no'.
Explanation: An invalid value was specified for the
FMM6278E No mount agent on a backup server is
usability state.
set up to handle partition 'partition
System action: Processing ends. number' within the current operation.
Make sure that the mount agent is
User response: Specify either 'yes' or 'no' as a usability
started correctly and verify that the
state value. Upper or lower case letters are allowed.
hostnames listed in db2nodes.cfg match
with the hostname of the backup server.
FMM6274E Operation failed because a resource is If the hostnames do not match, start the
temporarily unavailable. Please restart mount agent with the -H hostname
the operation. option.

Explanation: The launchpad could not fulfil the Explanation: A partition was detected that will not be
service request due to unavailable resources. handled by the mount agent(s) on the participating
backup server(s). The mount agent(s) are set up by
System action: Processing ends. using the command option for partitions to be handled
User response: Ensure the launchpad was not stopped (-N). However, one (or more) partitions where not
in the middle of a running operation. Check the logs assigned to a corresponding mount agent. The
for additional hints regarding the failure. After corresponding mount agent is determined by
resolving the issue try again. comparing the hostnames from db2nodes.cfg file (in the
DB2 instance directory) with the hostname of the
backup server. This error message displays when these
FMM6275E The requested process can currently not hostnames do not match.
be started.
System action: Processing ends.
Explanation: The launchpad could not fulfil the
service request due to the requested process, either for User response: Check the environment on the backup
mount vs. unmount or for offloaded tape backup could system(s). Make sure the partition is only associated
not be started. with a single mount agent instance on the backup
system(s). If the hostnames in the db2nodes.cfg file (in
System action: Processing ends. the DB2 instance directory) do not match the hostname
User response: Check the logs for additional hints of the backup server, start the mount agent with the -H
regarding the failure. After resolving the issue try hostname option and specify the hostname listed in the
again. db2nodes.cfg file.

FMM6276E Another mount agent service is FMM6279E No mount agent is setup on a backup
currently running. server to handle the current operation.
Make sure that the mount agent is
Explanation: The requested action could not be started started correctly.
due to another mount agent service (mount, unmount,
tape backup) is currently running. Only one service at a Explanation: No mount agent (the process signature
time will be handled by a mount agent on a backup is: acsgen -D -M) on the participating backup server(s)
server. was detected that could handle the current operation.
This can also happen if the password for authentication
System action: Processing ends. to the ACS daemon was changed.
User response: Wait until the currently running System action: Processing ends.
service is finished and try again.
User response: Check the environment on the backup
system(s) and make sure that the mount agent is
FMM6277E Partition 'partition number' is already started correctly. If you change the password for
handled by the mount agent instance authentication to the ACS daemon at the prodruction
running on 'hostname'. host, then you have to change the password on the
Explanation: A partition can only be handled by a backup host as well to match to the prodution host.
single mount agent instance.
System action: Processing ends. FMM6280E A usability state argument is missing.

User response: Check the environment on the backup Explanation: The 'update_status' function requires a
system(s). Make sure the partition is only associated usability state argument.
with a single mount agent instance on the backup System action: Processing ends.

100 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6281E • FMM6502I

User response: Specify a usability state argument. User response: Just specify each clone database name
once for the specified profile keyword.
FMM6281E The usability state 'state' is unknown or
not supported. FMM6287E The keyword 'keyword1' instead of
'found_keyword' is needed for the
Explanation: The specified usability state to be
keyword 'keyword2'. "
updated is either unknown or not supported.
Explanation: The specified keyword has been
System action: Processing ends.
misspelled.
User response: Specify a valid usability state and try
System action: Processing ends.
again.
User response: Correct the specified keyword.
FMM6282E query archive unsuccessful.
FMM6288E The command line option –s
Explanation: The offload agent was unable to check
<DEVICE_CLASS> is not allowed for
for files that have already been archived before.
function function name.
System action: Processing ends.
Explanation: For this function the command line
User response: The offload agent calls the dsmc query option –s <DEVICE_CLASS> is not allowed.
archive command which fails. Check the setup of your
System action: Processing ends.
Backup Archive client and try again.
User response: Restart the command without
specifying the command line option –s
FMM6283E offloaded tape backup unsuccessful.
<DEVICE_CLASS>.
Explanation: At least one error message occured
during offloaded tape backup.
FMM6289I The 'datastore name' data store was
System action: Processing ends. successfully added to the 'ESX host name'
ESX host.
User response: Review the dsmerror.log file (and
dsmsched.log file for scheduled events) to check for Explanation: A data store was made available on the
error messages and their impact to the operation.. specified ESX host.
System action: Processing continues.
FMM6284W offloaded tape backup successful with
User response: No action is required.
warnings.
Explanation: At least one warning message occured
FMM6290I The 'datastore name' data store was
during offloaded tape backup.
successfully unmounted from the 'ESX
System action: none host name' ESX host.

User response: Review the dsmerror.log file (and Explanation: A data store has been detached from the
dsmsched.log file for scheduled events) to check for specified ESX host.
warning messages and their impact to the operation..
System action: Processing continues.
User response: No action is required.
FMM6285I Start saving file number files ...
Explanation: Tape backup processing started.
FMM6501I Initializing 'function' request.
System action:
Explanation: The offload agent will be initialized for a
User response: None. new function request.
System action:
FMM6286E The clone database name 'cloneSID' has
User response: None.
been specified multiple times in the
profile. Please check the values of the
keyword 'keyword'. FMM6502I Executing 'function' request.
Explanation: One clone database name has been Explanation: The offload agent is executing a function
specified multiple times for the specified profile request.
keyword.
System action:
System action: Processing ends.
User response: None.

Chapter 2. FMM messages 101

FMM6503I • FMM6515E

User response: Check the offload agent log as well as

FMM6503I Terminating 'function' request.
the DB2 diagnostic log (db2diag.log) for further details.
Explanation: The offload agent is terminating a
function request. This also includes a cleanup of
FMM6510I Partition(s) 'partition list' of database
required resources.
'database name' initialized successfully.
System action:
Explanation: The participating database partitions
User response: None. were initialized successfully.
System action:
FMM6504E The 'function' request failed.
User response: None.
Explanation: The request for the named function
failed unexpectedly.
FMM6512I The 'function' request for database
System action: Processing ends. 'database name' with partitions
(partition(s)) processed successfully.
User response: See the Tivoli Storage FlashCopy
Manager log files on the production and backup Explanation: The selected function for the
servers for further details. The log files are in the participating partitions of a database was processed
ACS_DIR/logs directory. After you resolve the successfully.
problem, start the operation again. and respond to any
System action:
error messages found there.
User response: None.
FMM6506I Backup backup id was created with
option TSM_ONLY. It is marked for FMM6513I The resources of database 'database name'
deletion after the first TSM backup with partitions (partition(s)) are already
attempt. mounted.
Explanation: The backup corresponding to <backup Explanation: All required file systems are already
id> has been deleted. This is because the backup was mounted on the target system.
made with TSM_BACKUP option TSM_ONLY and the
TSM backup associated with this snapshot image has System action:
recently completed (successfully or unsuccessfully). User response: None.
System action:
User response: None. FMM6514E The specified filter did not result in a
match in the snapshot repository.

FMM6507E Function 'function' is not supported. Explanation: The repository does not contain a
snapshot backup that can be associated with the given
Explanation: The function request is not supported by filter arguments.
the offload agent.
System action:
System action:
User response: Check all specified filter arguments
User response: Check the specified function. and try again.

FMM6508I Initializing partition(s) 'partitions(s)' of FMM6515E A snapshot backup currently offloaded

database 'database name' as type. to tape is no longer mounted.
Explanation: The participating database partitions will Explanation: A tsm4acs tape_backup workflow
be initialized on the target system. Valid initialization consists of the steps: mount, tape backup, unmount.
types are snapshot, standby and mirror. When entering the unmount–phase, tsm4acs could not
find the snapshot backup that was just backed up to
System action: None.
tape. In principle, the tape backup might have finished
User response: successfully but some kind of a failure was detected
that prevents the tape_backup cleanup phase from
completing.
FMM6509E Failed to initialize partition 'partition(s)'
of database 'database name'. System action:
Explanation: The offload agent was not able to User response: Check the tsm4acs log as well as the
initialize one or more database partitions. appropriate device agent log for further details.
System action:

102 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6516E • FMM6527E

FMM6516E Another 'function' request for a snapshot FMM6522W Database instance 'instance name' already
backup is already running. started.
Explanation: tsm4acs has detected that another Explanation: The database instance on the target
request, such as mount or tape_backup, for a snapshot system is already running.
backup is running.
System action:
System action:
User response: The offload agent workflow should
User response: A new tsm4acs request can only be not be affected. In general, no action is required.
started if the old request has finished.
FMM6523E Database instance 'instance name' could
FMM6517I A snapshot backup is already mounted. not be started.
Explanation: The tsm4acs mount–request will not be Explanation: The database instance on the target
executed due to an already mounted snapshot backup system could not be started.
on the offload system.
System action:
System action:
User response: Check the DB2 diagnostic log
User response: None. (db2diag.log) for further details.

FMM6518I No snapshot backup is currently FMM6524I Stopping database instance 'instance

mounted. name'.
Explanation: The tsm4acs unmount–request will not Explanation: The database instance on the target
be executed because there is currently no snapshot system will be stopped.
backup mounted on the offload system.
System action:
System action:
User response: None.
User response: None.
FMM6525I Database instance 'instance name' was
FMM6519I There is no snapshot backup currently stopped successfully.
pending to be offloaded to tape.
Explanation: The database instance on the target
Explanation: The 'tape_backup' request cannot be system was stopped.
executed because there is no snapshot backup in the
System action:
TAPE_BACKUP_PENDING state.
User response: None.
System action: Processing ends.
User response: No action is required.
FMM6526W Database instance 'instance name' already
stopped.
FMM6520I Starting database instance 'instance name'.
Explanation: The database instance on the target
Explanation: The database instance on the target system was already stopped.
system will be started.
System action:
System action:
User response: Check the DB2 diagnostic log
User response: None. (db2diag.log) for indication of whether an unexpected
failure was the cause. Also check the tsm4acs log for
indications that the workflow, which includes
FMM6521I Database instance 'instance name' was
shutdown of the database instance on the target
started successfully.
system, reported unexpected failures.
Explanation: The database instance on the target
system was started.
FMM6527E Database instance 'instance name' could
System action: not be stopped.

User response: None. Explanation: The database instance on the target

system could not be stopped.
System action:
User response: Check the DB2 diagnostic log

Chapter 2. FMM messages 103

FMM6528E • FMM6537I

(db2diag.log) for further details.

FMM6533E Failed to catalog database 'database name'
on path 'path'.
FMM6528E The file containing the list of partitions
Explanation: The database on the target system could
and hosts to be off–loaded could not be
not be cataloged.
created.
System action:
Explanation: The 'rah' host file is used by DB2 to
determine the database partitions that must be User response: Check the DB2 diagnostic log
processed in a DPF environment. By default, this file is (db2diag.log) for further details. Additionally, for a
'db2nodes.cfg'. tsm4acs uses a temporary 'rah' host file more detailed analysis enable the trace facility of the
to be able to handle only a subset of partitions. offload agent and re–execute the function.
System action:
FMM6534E A snapshot backup is already mounted.
User response: The temporary 'rah' host file used by
tsm4acs will be created under '$HOME/sqllib', where Explanation: A mount–request is not executed because
$HOME is the home directory of the DB2 instance a snapshot backup is already mounted on the offload
owner. Ensure that the appropriate permissions are set system.
and enough free space is available.
System action: Processing ends.
User response: Unmount the previously mounted
FMM6529I Database instance 'db instance' already
backup, then start the mount request again.
started.
Explanation:
FMM6535E The snapshot backup with ID 'identifier'
System action: does not qualify for restore operations.
User response: Explanation: Due to its characteristics the specified
snapshot backup can not be restored. Common reasons
are the copy type of the flashcopy is NOCOPY or the
FMM6530E The default database path could not be
background copy operation has not been finished yet.
determined.
System action: Processing ends.
Explanation: The value of the default database path
(DFTDBPATH) stored in the database manager User response: Use a different backup for the restore
configuration could not be retrieved. operation or wait until the background copy has been
completed or use the force option to enforce a reversal
System action:
of the direction of the copy relation (not supported by
User response: Check the DB2 diagnostic log all storage devices).
(db2diag.log) for details. Further, verify the database
manager configuration to be issued by the DB2 instance
FMM6536W The virtual machine 'vm name' will be
owner as follows: db2 get dbm cfg | grep
ignored and not be part of the backup
DFTDBPATH. Also for a more detailed analysis, enable
since it is not connected to the vCenter
the trace facility for the offload agent and re–execute
server.
the function.
Explanation: The specified virtual machine is not
connected to the vCenter server and cannot be included
FMM6531I Cataloging database 'database name' on
in the backup. It will not be restorable.
path 'path'.
System action: Processing continues.
Explanation: The database on the target system will
be cataloged. User response: Connect the virtual machine or
exclude it from the backup to get rid of this warning.
System action:
User response: None.
FMM6537I Database 'database name' on path 'path'
already cataloged.
FMM6532I Database 'database name' on path 'path'
Explanation: The database on the target system was
cataloged successfully.
already cataloged.
Explanation: The database on the target system was
System action:
cataloged successfully.
User response: None.
System action:
User response: None.

104 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6539W • FMM6549I

Explanation: The disks could not be attached to the

FMM6539W The retry threshold for the snapshot
specified target virtual machine.
backup was exceeded.
System action: Processing ends.
Explanation: If tsm4acs is running in the daemon
mode (–D), only one attempt will be made to offload a User response: Ensure to use the ESX host where the
tape from a snapshot backup. This restriction was specified target virtual machine is running as auxiliary
imposed to prevent an excessive number of offload ESX host.
retries for a snapshot backup.
System action: FMM6544I Snapshot backup suspend time: suspend
time
User response: A snapshot backup for which the retry
threshold was exceeded can only be offloaded to tape Explanation: The snapshot backup suspend time
using the manual mode of tsm4acs (–f tape_backup). specifies the minimum recovery time for all
participating partitions.
FMM6540I Start time: Starting backup of database System action:
'database name', partition(s) 'partition(s)'
with the following options: METHOD User response: None.
offload backup method SESSIONS number
of sessions OPTIONS options BUFFERS FMM6545I Write control file ctrlfile
number of buffers BUFFERSIZE buffer size
PARALLELISM degree of DB2 parallelism Explanation: The offload agent is writing the Oracle
control file to a local file system.
Explanation: The off–loaded tape backup was started
using the 'db2 backup database' command. The set of System action:
listed backup parameters gives a brief summary about User response: None.
the options and values that were used for the backup.
System action: FMM6546I Write database parameter file parameter
User response: None. file
Explanation: The offload agent is writing the database
FMM6541I End_time Instance Database Partition parameter file to a local file system.
Snapshot_ID Tape_backup_ID System action:
Explanation: The backup is finished. A backup result User response: None.
table for all participating partitions of the database will
be generated.
FMM6547I Do not overwrite database parameter
System action: file.
User response: None. Explanation: The offload agent will not overwrite the
database parameter file.
FMM6542I end timeinstance namedatabase System action:
namepartitionsnapshot idtape backup id
User response: None.
Explanation: One entry of the backup result table
reflects one partition of the database. The backup for a
database partition succeeded if a valid tape backup ID FMM6548I Start backup of database instance
(DB2 tape backup timestamp) was inserted. If the tape 'instance'.
backup for a partition failed, the tape backup ID is set Explanation: The offloaded tape backup of the named
to '–'. database instance was started.
System action: System action:
User response: None. User response: None.

FMM6543E The disks could not be attached to the FMM6549I Finished backup of database instance
requested target virtual machine: 'vm 'instance' successfully.
name'. Please make sure to use the ESX
host where the target virtual machine is Explanation: The offloaded tape backup of the named
running as auxiliary ESX host. ESX host database instance finshed successfully.
'esx hostname' has been used for this
System action:
operation.

Chapter 2. FMM messages 105

FMM6550I • FMM6561W

User response: None. or make the original virtual machine with the specified
instance UUID available.
FMM6550I Resetting the database logs to prepare
the change of the database id. FMM6555I Selected snapshot backup with ID 'id'.
Explanation: In order to enable the change of the Explanation: The snapshot backup with the named id
database id the database is brought into a consistent was selected to work with. The format of a snapshot id
state by resetting the logs. in that context is: <instance>,<database>,<timestamp>.
System action: Processing continues. System action:
User response: None. User response: None.

FMM6551I Changing the database id. This will stop FMM6556E Failed to retrieve meta data.
the database.
Explanation: The metadata assigned to a snapshot
Explanation: In order to create a unique clone of the backup could not be retrieved.
database the database id is going to be changed. After
System action:
this process the database will be stopped and may be
restarted by IBM Tivoli Storage FlashCopy Manager to User response: Check the logs for further information.
continue with further steps. If the problem cannot be resolved contact your IBM
support personnel.
System action: Processing continues.
User response: None.
FMM6557I The 'function' request for database
'dbname' processed successfully.
FMM6552I Successfully changed database id from
Explanation: The offload agent has completed the
old database id to new database id.
named function successfully.
Explanation: The database id has been changed as
System action:
part of the cloning operation. For reference the old and
new value are displayed. User response: None.
System action: Processing continues.
FMM6558I The resources of database 'dbname' are
User response: None.
already mounted.
Explanation: The offload agent has detected that all
FMM6553E Failed to changed database id. This is
required resources of the named database are already
the output of the failed command: error
mounted.
output
System action:
Explanation: The attempt to change the database id
has failed. The output of the operation is shown below User response: None.
this message.
System action: Processing ends. FMM6560E Backint could not be found at 'directory'.
User response: Check the output of the failed Explanation: The offload agent was unable to find the
operation to determine the root cause. Perform backint executable file needed for offloading the data to
corrective actions and try again. Tivoli Storage Manager.
System action:
FMM6554E The original virtual machine with
instance UUID 'target instance uuid' is User response: The offload agent expects the backint
needed for this single disk restore executable at the default TSM for ERP installation
operation but was not found. Please location. Ensure that backint can be found accordingly
specify a target virtual machine. and try again.

Explanation: The original virtual machine with the

specified instance UUID is needed for this single disk FMM6561W Failed to initialize partition 'partition(s)'
restore operation but was not found. of database 'database name'. Restore
remaining partitions.
System action: Processing ends.
Explanation: The offload agent was not able to
User response: Specify a valid target virtual machine initialize one or more database partitions.
System action: Processing continues.

106 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6562I • FMM6803E

User response: Restore the remaining partitions. If all only the options that are supported by the operation
partitions are restored and this warning persists check requested.
the offload agent log as well as the DB2 diagnostic log
(db2diag.log) for further details.
FMM6570E The 'name' name is reserved. You must
specify another name.
FMM6562I Changing the database shared memory
Explanation: The DEVICE_CLASS section name must
of partition(s) 'partitions(s)' of database
be unique therefore you cannot reuse the name of an
'database name' to size.
existing section.
Explanation: The size of the database shared memory
System action:
of the participating database partitions will be changed
on the target system. User response: Choose a different DEVICE_CLASS
section name.
System action: None.
User response:
FMM6600E Unexpected error during 'function'.
Explanation: The offload agent has terminated
FMM6563E Failed to change the size of the database
unexpectedly due to an internal error while executing
shared memory of partition 'partition(s)'
either a mount or an unmount request.
of database 'database name'.
System action:
Explanation: The offload agent was not able to change
the size of the database shared memory one or more User response: Check the logs of the involved
database partitions. components (management agent, offload agent, device
agent) for further details and descriptions regarding the
System action:
failure.
User response: Check the offload agent log as well as
the DB2 diagnostic log (db2diag.log) for further details.
FMM6801E DB2 Library not specified
Explanation: IBM Tivoli Storage FlashCopy Manager
FMM6564I Successfully changed the size of the
tries to load the DB2 API library specified by the
database shared memory of Partition(s)
DB2_LIBRARY parameter. However the value of the
'partition' of database 'database'.
parameter is empty or invalid.
Explanation: The size of the database shared memory
System action: Processing stops.
of the participating database partitions were changed
successfully. User response: Verify the value of the DB2_LIBRARY
parameter in the profile.
System action:
User response: None.
FMM6802E Failed to load DB2 library 'library name'
dlopen error: dlopen error
FMM6565E Another operation of IBM Tivoli Storage
Explanation: An error occured when loading the DB2
FlashCopy Manager is preventing
API library. A text description displays.
accesss to this backup.
System action: Processing stops.
Explanation: Another operation has the access to this
backup and it is preventing the current function to be User response: Verify that the DB2_LIBRARY profile
execut ed. parameter contains the fully qualified name of the DB2
API library. Evaluate the error description.
System action: Processing stops.
User response: Verify the summary log and retry the
FMM6803E DB2 Library 'library name' could not be
call of the function.
loaded.
Explanation: An error occurred when attempting to
FMM6566E The 'option' option is not supported by
load the DB2 API library. See the previous error.
the 'function' operation.
System action: Processing stops.
Explanation: An option that is specified in the
command line is not supported by the operation User response: See the previous error descriptions.
named.
System action: Processing ends.
User response: Check the command syntax and use

Chapter 2. FMM messages 107

FMM6804E • FMM6814I

problem. Try the operation again after resloving the

FMM6804E DB2 Library symbols 'library name' could
cause of the error.
not be loaded: rc _ return code
Explanation: IBM Tivoli Storage FlashCopy Manager
FMM6810I The production database 'database name'
was not able to load the API functions from the DB2
has been cataloged successfully as 'new
API library specified by the DB2_LIBRARY parameter.
database name'.
System action: Processing stops.
Explanation: The database 'database name' has been
User response: Verify that the DB2_LIBRARY cataloged as database 'new database name' successfully
parameter contains the correct DB2 API library. on the target system.
System action: Processing continues.
FMM6805I The production TCP/IP node 'tcp node'
User response: None.
will be cataloged.
Explanation: The production node directory was
FMM6811E Parsing error in file 'filename' at line 'line
cataloged because it was empty or it was not found.
number' at position 'position'. Expected
System action: Processing continues. one of 'valid possibilities' but found 'line'.
User response: None. Explanation:
System action: Processing ends.
FMM6806E Unable to catalog production TCP/IP
User response:
node 'tcp node' as 'node alias'.
Explanation: An error occurred while cataloging this
FMM6812E Unable to connect to the production
TCP/IP node using the specified node alias. Check the
database 'database name'.
db2diag.log file for more details.
Explanation: A connection to the production database
System action: Proccessing stops.
'database name' was not established. This can be caused
User response: Evaluate the error in the the by incorrect user rights or by the database instance not
db2diag.log file. being started.
System action: Processing ends.
FMM6807I The production TCP/IP node 'tcp node'
User response: Check the DB2 diagnostic log
has been cataloged successfully as 'node
(db2diag.log) for more information regarding this
alias'.
problem. Try the operation again after resloving the
Explanation: The node was cataloged successful. cause of the error.
System action: Proccessing continues.
FMM6813E Unable to disconnect from the
User response: None.
production database 'database name'.
Explanation: The product was unable to disconnect
FMM6808I The production database 'database name'
from the production database 'database name'.
will be cataloged.
System action: Processing ends.
Explanation: The production database 'database name'
will be cataloged in the database directory on the User response: Check the DB2 diagnostic log
system. (db2diag.log) for more information regarding this
problem. Try the operation again after resloving the
System action: Processing continues.
cause of the error.
User response: None.
FMM6814I A attachment to the production database
FMM6809E Unable to catalog production database instance 'database instance' has been
'database name' as 'new database name'. made.

Explanation: The database 'database name' could not be Explanation: The client has successfully attached to
cataloged as database 'new database name' on the target the production database instance 'database instance'.
system.
System action: Processing continues.
System action: Processing ends.
User response: None.
User response: Check the DB2 diagnostic log
(db2diag.log) for more information regarding this

108 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6815I • FMM6826E

FMM6815I A connection to the production database FMM6821E Attachment to the production DB2
'database name' has been made. instance for user user failed. Verify that
the database manager on the production
Explanation: The client has successfully connected to
system has started.
the production database 'database name'.
Explanation: The attachment of the instance user to
System action: Processing continues.
the production DB2 instance failed.
User response: None.
System action: Operation fails.
User response: Verify that the database manager on
FMM6816I TBS container name=tablespace container
the production system has started.
name
Explanation: The tablespace container 'tablespace
FMM6822E Some tablespace containers are in an
container name' was detected.
exception state.
System action: Processing continues.
Explanation: Some DB2 tablespace containers are in
User response: None. an exception state.
System action: Operation fails.
FMM6817E Tablespace container 'tablespace container
User response: Check the db2diag.log file for more
name' is in exception state.
details about this error. Try the operation again after
Explanation: The tablespace container 'tablespace the cause of this error has been corrected.
container name' is in a state (such as OFFLINE) that
prevents further processing.
FMM6823I The attachment to the production
System action: Processing ends. database instance 'database instance' has
been detached.
User response: Check the DB2 diagnostic log
(db2diag.log) for more information regarding this Explanation:
problem. Try the operation again after resloving the
System action:
cause of the error.
User response:
FMM6818I Set client connection to Node 'node
number'. FMM6824I The connection to the production
database 'database name' has been
Explanation: Connection settings for the client process
disconnected.
using node 'node number' are performed.
Explanation: The connection to the production
System action: Processing continues.
database has been disconnected.
User response: None.
System action: No specific system behavior.
User response: None.
FMM6819E No data was obtained from Database
Monitor.
FMM6825E A DB2 API call failed with the
Explanation: Snapshot information from the database
following error: error code
manager operational status was not collected.
Explanation: A call to the DB2 API failed. The error
System action: Processing ends.
code is given with this message.
User response: Check the DB2 diagnostic log
System action: Operation failed.
(db2diag.log) for more information regarding this
problem. Try the operation again after resloving the User response: Check the db2diag.log file for more
cause of the error. details and refer to the DB2 user manual regarding this
DB2 error code.
FMM6820E The 'hostname' ESX server has not been
found in the vCenter server. FMM6826E DB2 Library 'library name' could not be
unloaded.
Explanation: The specified ESX host cannot be found
in the vCenter server. Explanation: Unable to unload the DB2 library.
System action: Processing ends. System action: Operation fails.
User response: Specify another ESX host. User response: Check the application logs and

Chapter 2. FMM messages 109

FMM6827E • FMM6906I

db2diag.log files for more details about this error.

FMM6833E The RMAN executable was not found or
is not executable by the current user.
FMM6827E Tablespace 'tablespace' is in state 'state'. Could not verify the connection to the
Snapshot backup is not possible. Oracle catalog database.

Explanation: The current state of the tablespace does Explanation: Either the current user ID is not an
not allow a snapshot backup to occur. Oracle user or the Oracle environment variables are not
set correctly.
System action: Operation fails.
System action:
User response: Change the tablespace to a NORMAL
or BACKUP PENDING state and run the operation User response: Verify that you are logged in as the
again. database instance user and that your environment
variables are correctly specified.

FMM6828E Some tablespaces are not in 'NORMAL'

state. Snapshot backup is not possible. FMM6901I Response to Init request.

Explanation: A snapshot backup cannot be taken Explanation: This message indicates the progress of
unless some tablespaces are in a NORMAL state. the flow within the device agent.

System action: Operation fails. System action:

User response: Change the tablespaces to a NORMAL User response: None.

state and run the operation again.
FMM6902I Response to Partition request.
FMM6829I Connecting to the production database
Explanation: This message indicates the progress of
'database name' ...
the flow within the device agent.
Explanation: A connection to the production database
System action:
will be established.
User response: None.
System action: No specific system behavior.
User response: None.
FMM6903I Response to Prepare Flash request.
Explanation: This message indicates the progress of
FMM6830I Disconnecting from the production
the flow within the device agent.
database 'database name' ...
System action:
Explanation: Disconnecting from the production
database. User response: None.
System action: No specific system behavior.
FMM6904I Response to Restore request.
User response: None.
Explanation: This message indicates the progress of
the flow within the device agent.
FMM6831I Attaching to the production database
instance 'database instance' ... System action:
Explanation: Attaching to the production database User response: None.
instance.
System action: No specific system behavior. FMM6905I Response to Flash request.
User response: None. Explanation: This message indicates the progress of
the flow within the device agent.
FMM6832I Detaching from the production database System action:
instance 'database instance' ...
User response: None.
Explanation: The production database instance has
been detached.
FMM6906I Response to Verify request.
System action: No specific system behavior.
Explanation: This message indicates the progress of
User response: None. the flow within the device agent.
System action:

110 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6907I • FMM6917E

User response: None. System action:

User response: None.
FMM6907I Response to Complete Restore request.
Explanation: This message indicates the progress of FMM6913E Wrong parameter provided with option
the flow within the device agent. '–c'.
System action: Explanation: A program was called with an
unsupported parameter value.
User response: None.
System action:
FMM6908I Response to Expiration request. User response: If the program was called from the
command line or from a script, correct the call.
Explanation: This message indicates the progress of
Otherwise, contact your IBM support personnel.
the flow within the device agent.
System action:
FMM6914E Invalid option '–K' specified.
User response: None.
Explanation: A program was called with an
unsupported parameter value for the internal option
FMM6909I Response to Monitor request. '–K'.

Explanation: This message indicates the progress of System action:

the flow within the device agent.
User response: If the program was called from the
System action: command line or from a script, correct the call.
Otherwise, contact your IBM support representative.
User response: None.

FMM6915E Could not change directory to path.

FMM6910E Could not set user ID to userid. Error
error – errormsg. Explanation: An executable file needs to change to the
named working directory, however, changing to the
Explanation: The user id of the device agent process directory did not succeed.
could not be switched internally to the named user id.
System action:
System action:
User response: Make sure authorization is set
User response: Check the permissions of the binary correctly for the executable file to access the required
and try again. path.

FMM6911E The effective user ID userideff of the FMM6916E Program program, function function:
process could not be set to the user received signal signal, exiting.
userid. Error error – error_msg. Check that
the device agent executable has the s–bit Explanation: The program received a signal that forces
set. the operation to end.
Explanation: Due to insufficient permissions of the System action: Operation fails.
device agent executable, the user id of the device agent
User response: Run the last operation again.
process could not be switched internally to the named
user id.
FMM6917E Failed to find volume group for file:
System action:
path
User response: Check that the device agent binary has
Explanation: The file named could not be located. Its
the s–bit set and try again.
file system or volume group could not be determined.
System action:
FMM6912E Background operation shutting down in
order to give precedence to a concurrent User response: Make sure that the database meets the
operation. requirement for snapshot backups. Make sure that the
data is located on a file system under the control of the
Explanation: A background operation is ending
storage device.
because some interactive operation using the same
resources was started. Once the operation taking
precedence has ended, the background operation is
resumed.

Chapter 2. FMM messages 111

FMM6918E • FMM6929E

FMM6918E Error when reading the correlation list FMM6924E Failed to initialize object_name control
or during the FlashCopy of the volume object.
pairs.
Explanation: The internal control object could not be
Explanation: A problem occurred either while reading initialized.
the correlation list or while flashing the volume pairs.
System action:
System action:
User response: Check the log and trace files for
User response: Check the relations of the details.
(source/target) volume pairs.
FMM6925E Function call 'function_name' failed.
FMM6919E Failed to cancel the copy relationship of
Explanation: A call to the named internal function
volume pairs: rc=return_code.
failed.
Explanation: Withdrawing the copy relations of the
System action:
determined volume pairs failed.
User response: Check the log and trace files for
System action:
details.
User response: Check the log and trace files for
details.
FMM6926I Adding 'path' to the Disk Mapper input
list.
FMM6920E After 'withdraw done' was finished the
Explanation: The named file is added to the Disk
update of the IDS repository failed:
Mapper input list.
rc=return_code.
System action:
Explanation: The IDS repository could not be
updated. User response: None.
System action:
FMM6927E Failed to find N–Series volume for file
User response: Check the log and trace files for
'path'. Error: error_information.
details.
Explanation: The matching N Series volume for a
specified file could not be found due to an error.
FMM6921E Failed to monitor the FlashCopy.
System action:
Explanation: The task for monitoring the progress of
the background copy process of the volume pairs User response: Check the log and trace files for
failed. details.
System action:
FMM6928E File system not found. Failed to find
User response: Check the log and trace files for
NFS mount point for file: 'path'.
details.
Explanation: The file system base for a mount point of
a specified file could not be found.
FMM6922E Failed to allocate memory.
System action:
Explanation: Not enough memory was available to
continue processing. User response: Check the log and trace files for
details.
System action:
User response: Ensure that the system has sufficient
FMM6929E Not a file system of type NFS. Failed to
real and virtual memory. Close unnecessary
find N–Series volume for file: 'file'.
applications.
Explanation: The named file is not located on an NFS
mounted file system.
FMM6923I Object_name control object already
initialized. System action:
Explanation: The internal control object is already User response: Make sure that the database meets the
initialized and is used for the following process flow. requirement for snapshot backups. Make sure that the
data is located on a file system under the control of the
System action:
N Series storage device.
User response: None.

112 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6930E • FMM6942E

FMM6930E Volume information missing. Failed to FMM6936E Failed to unmount 'mount_point'.

find N–Series volume for file: 'path'.
Explanation: Failed to unmount the specified mount
Explanation: The volume information could not be point.
collected for the named file.
System action:
System action:
User response: Check the log and trace files for
User response: Check the log and trace files for details.
details.
FMM6937I Mounting 'mount_point'.
FMM6931E Function call 'function_name' failed.
Explanation: Mounting the specified mount point.
Error: error_information.
System action:
Explanation: A call to an internal function failed due
to the specified error. User response: None.
System action:
FMM6938E Failed to mount 'mount_point'.
User response: Check the log and trace files for
details. Explanation: Failed to mount the specified mount
point.
FMM6932E Function call 'function_name' failed with System action:
rc_return_code. Error: error_information.
User response: Check the log and trace files for
Explanation: A call to an internal function failed with details.
the specified return code due to the stated error.
System action: FMM6939I Prepare for snap restore, volume
'volume_id', snap ID _ snapshot_id.
User response: Check the log and trace files for
details. Explanation: Preparation for a snap restore of the
specified volume with the associated snap ID is being
performed.
FMM6933I Volume 'volume_id', snap ID _
snapshot_id. System action:
Explanation: The snap ID is associated with the User response: None.
specified volume.
System action: FMM6940I Prepare flash of group 'group_id'.
User response: None. Explanation: Preparation for a snapshot copy of a
group of the specified volumes is being performed.
FMM6934I The snapshot 'snapid' was generated for System action:
the source volume 'volname'.
User response: None.
Explanation: A snapshot with the name displayed was
taken from this volume. In a SAN environment, this
message appears for each LUN thhat is involved in the FMM6941I <server name><user name><separator><hw
snapshot process. However, when several LUNs belong nas nseries><timeout>
to the same volume, only one snapshot of this volume Explanation: A list of storage device parameters.
is taken.
System action:
System action:
User response: None.
User response: None.

FMM6942E The storage device 'number' is not

FMM6935I Unmounting 'mount_point'. handled by this device agent.
Explanation: Unmounting the specified mount point. Explanation: The specified storage device cannot be
System action: handled with this device agent.

User response: None. System action:

User response: Contact your IBM support.

Chapter 2. FMM messages 113

FMM6943I • FMM6952E

FMM6943I Hardware version installed: FMM6948E The container 'container' has already
version.information been created. Please specify another
name.
Explanation: The specified version of the installed
hardware is indicated. Explanation: A container with the specified name
already exists. Container names must be unique.
System action:
System action: Operation fails.
User response: None.
User response: Specify a unique container name.
FMM6944I NLS and tracing are already initialized.
FMM6949E Creation of the container 'container'
Explanation: The logging and tracing facilities are
failed because no preceding group has
already initialized and are used further internally.
been found, or the preceding group is
System action: not valid. Current group is: 'group'. First
specify a valid group using the
User response: None. 'command' command.
Explanation: Acsgen received a new container
FMM6945I File system 'PATH' was already message but did not receive the required GROUP
unmounted. information.
Explanation: The specified file system was already System action: Operation fails.
unmounted.
User response: Group information needs to be
System action: provided using the GROUP command before the
User response: None. container information is provided.

FMM6946E The environment variable 'ODMDIR' is FMM6950W The output file 'path' is not valid.
not specified. Verify that the DB2 Explanation: The device agent's log file could not be
registry parameter DB2ENVLIST created. The messages will be logged to STDOUT as
contains the value 'ODMDIR'. To set the well as to the acsd log file.
DB2ENVLIST you need to issue the
command: db2set -i <DB2 instance System action:
name> DB2ENVLIST='<current envlist>
User response: Check the permissions of the
ODMDIR'
directories and that there is enough free space in the
Explanation: The environment variable 'ODMDIR' file system. Check the acsd log and trace files for
must set in the user's environment where the snapshot details.
backup or restore is started. In general, this is the case
for default operating system installations.
FMM6951E Version mismatch error. Please check
System action: setup (version:information).
User response: allations. User response: Check the Explanation: The versions of acsd and the device
trace files where the runtime environment is written. If agent are different.
an entry for the ODMDIR environment variable cannot
System action:
be found, set it manually as described in the message
text. User response: Check the log and trace files for
details. If the problem cannot be resolved, contact your
IBM support.
FMM6947W File system 'mount_point' is already
mounted.
FMM6952E Error in connection to IBM Tivoli
Explanation: A file system that should be mounted is
Storage FlashCopy Manager
already mounted.
management agent.
System action: Operation continues.
Explanation: The IBM Tivoli Storage FlashCopy
User response: None. Manager management agent (acsd) could not be
reached from within the device agent.
System action:
User response: Check the log and trace files for
details.

114 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6953E • FMM6964I

FMM6953E Error while parsing path script. The FMM6959I Script 'path' returned with code
keyword 'keyword' is not supported return_code.
during function_name.
Explanation: The indicated script returned with the
Explanation: The script could not be parsed specified return code.
successfully due to an incorrect keyword for the given
System action:
action.
User response: None.
System action:
User response: Check the indicated script.
FMM6960E Non–zero return code from script 'path'.
Explanation: The script returned with a non–zero
FMM6954E Error while parsing script. The keyword
return code, which could indicate a warning or an
'keyword' is not supported.
error.
Explanation: The script could not be parsed
System action:
successfully due to an incorrect keyword.
User response: Check the log and trace files for
System action:
details.
User response: Check the indicated keyword.
FMM6961E Specify a script for removing data.
FMM6955E 'container_id' is not a valid container.
Explanation: To remove data, you must specify a
Please specify a valid container.
script.
Explanation: Error in communication protocol
System action:
between the device agent and the storage device
adapter. User response: Create and specify an appropriate
script.
System action:
User response: Contact your IBM support personnel.
FMM6962I Response to File System Service request
(request).
FMM6956E The usability state 'usability_state' is not
Explanation: A file system service request (request) is
supported.
handled by the device agent and a response message is
Explanation: Error in communication protocol sent back to the management agent.
between the device agent and the storage device
System action:
adapter. The given usability state <usablility_state> is
not valid. User response: None.
System action:
FMM6963I Performing snapshot of the source
User response: Contact your IBM support personnel.
volume 'source volume'.
Explanation: This message reports that a new
FMM6957E Script has continued without waiting.
snapshot operation is in progress.
Explanation: The script should wait before continuing
System action:
execution.
User response: Watch for additional messages
System action:
regarding the success of the snapshot operation.
User response: Check the log and trace files for
details.
FMM6964I Number of volumes to be processed by
snapshot: 'number'.
FMM6958I Output from script:
Explanation: The number of volumes to be processed
Explanation: The output of the script. by FlashCopy
System action: System action:
User response: None. User response: None.

Chapter 2. FMM messages 115

FMM6965I • FMM6973E

allow overwriting those files during restore they need

FMM6965I Snapshot started ...
to be added to a 'negative list' or the checking to
Explanation: The command with the 'flashcopy' prevent files from being overwritten needs to be
function has been issued on the production system, and disabled.
the program splitint waits until this action has finished.
System action:
System action:
User response: Edit the 'CLIENT' section of the
User response: None. profile. You can either set the parameter
'NEGATIVE_LIST' to 'NO_CHECK', to allow IBM Tivoli
Storage FlashCopy Manager to overwrite any file
FMM6966I Snapshot successful.
residing on a file system that will be restored, or you
Explanation: The command for the snapshot–based can set the parameter 'NEGATIVE_LIST' to point to a
copy of the volume pairs has completed successfully on file (the 'negative list') which contains a list of all files
the production system. and directories that are allowed to be overwritten. Any
directory you add to the 'negative list' is processed
System action: recursively.
User response: None.
FMM6970I Snapshot restore successful.
FMM6967E The directory directory has nested mount Explanation: The snapshot restore of a snapshot
points that are stored on more than one backup finished successfully.
volume group. This is currently not
supported. System action:
Explanation: The application sent a request to User response: None.
recursively backup all data stored beneath <directory>.
IBM Tivoli Storage FlashCopy Manager cannot fulfill
FMM6971E Adding the key 'key' to the container
this backup request because the data stored in this
'container' failed because it already
directory path resides on file systems that are stored on
exists. Please use the 'command'
multiple volume groups. This is currently not
command if you want to update the key.
supported.
Explanation: Error in communication protocol
System action:
between the device agent and the storage device
User response: Migrate the data underneath adapter.
<directory> to a single file system or migrate the file
System action:
systems mounted underneath this directory tree to a
common volume group. Note that the directory User response: Contact your IBM support personnel.
structure could also contain links to files residing in
other file systems. In this case you might be able to
FMM6972E Updating the key 'key' in the container
resolve this problem by simply removing those links.
'container' failed because it does not
exist. Please use the 'command' command
FMM6968E 'command_1' is not a valid keyword, if you want to add the key.
expected 'command_2'.
Explanation: Error in communication protocol
Explanation: Error in communication protocol between the device agent and the storage device
between the device agent and the storage device adapter.
adapter.
System action:
System action:
User response: Contact your IBM support personnel.
User response: Contact your IBM support personnel.
FMM6973E The group 'group' has already been
FMM6969E Found non–database files on the file created. Please specify another name.
systems to restore. Please provide a
Explanation: Error in communication protocol
negative list or perform restore with
between the device agent and the storage device
option 'no_check' to allow overwriting
adapter.
those files.
System action:
Explanation: Although the previously mentioned files
were not requested to be restored, they would be User response: Contact your IBM support personnel.
overwritten, because they reside on a file system that
will be entirely overwritten during restore. In order to

116 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM6974E • FMM6983E

FMM6974E 'group' is not a valid group. Please FMM6979E Script has continued without waiting.
specify a valid group. Expected output 'command' from script
but was: 'output'.
Explanation: Error in communication protocol
between the device agent and the storage device Explanation: Error in communication protocol
adapter. between the device agent and the storage device
adapter.
System action:
System action:
User response: Contact your IBM support personnel.
User response: Contact your IBM support personnel.
FMM6975E Adding the key 'key' to the group 'group'
failed because it already exists. Please FMM6980W Received a warning from the adapter:
use the 'command' command if you want warning
to update the key.
Explanation: A warning message has been received
Explanation: Error in communication protocol from the storage device with the parameters:
between the device agent and the storage device <warning>.
adapter.
System action:
System action:
User response: Check the content of the warning.
User response: Contact your IBM support personnel.
FMM6981E Received an error from the adapter: error
FMM6976E Updating the key 'key' in the group
Explanation: An error message has been received from
'group' failed because it does not exist.
the storage device with the parameters: <error>.
Please use the 'command' command if
you want to add the key. System action:
Explanation: Error in communication protocol User response: Check the content of the error
between the device agent and the storage device message.
adapter.
System action: FMM6982W The script 'adapter_name' returned with
code 1. The logfile might contain further
User response: Contact your IBM support personnel.
warnings.
Explanation: The storage device adapter had a return
FMM6977E The #'first_command' 'parameter' command
code of 1.
has to be preceeded by a
#'second_command' command. System action:
Explanation: Error in communication protocol User response: Please check the device agent logfile
between the device agent and the storage device for further warnings.
adapter.
System action: FMM6983E The following backup items were not
assigned to corresponding snapshot
User response: Contact your IBM support personnel.
items: backup_items
Explanation: Backup items are storage elements such
FMM6978E 'command' is not a valid keyword when
as LUN identifiers on storage area network (SAN) or
updates to containers and groups are
network share paths on network-attached storage
expected.
(NAS). Backup items are identified by IBM Tivoli
Explanation: Error in communication protocol Storage FlashCopy Manager OS agent "acsgen" and are
between the device agent and the storage device based on the backup procedure of the application that
adapter. requests the backup or restore operation. A snapshot
item is the smallest entity identifiable in a snapshot.
System action:
Backup items either all or a subset are assigned to the
User response: Contact your IBM support personnel. corresponding snapshot items. A subset is assigned in
an AIX LVM mirroring or Oracle ASM environment.
System action: Processing stops.
User response: Evaluate the storage adapter-specific
messages to resolve the problem.

Chapter 2. FMM messages 117

FMM6984E • FMM7053E

FMM6984E Error during prepare phase. Nothing FMM7049I The default for environment variable
known about group 'group_name'. It has PROLE_PORT will be used.
not been created in the partition phase.
Explanation: The port for the internal communication
Explanation: Error in communication protocol of Data Protection for SAP is set during installation.
between the device agent and the storage device The message indicates that this port is being used.
adapter.
System action:
System action:
User response: None.
User response: Contact your IBM support personnel.
FMM7050E The 'datastore name' datastore has not
FMM6985E Unable to connect to the copy services been found in the datacenters defined
servers 'server name' and 'backup server in the domain. It is not part of the
name'. backup.
Explanation: The attempt to connect to the storage Explanation: The specified datastore has not been
device failed for both the primary and the secondary found in the datacenters that are defined for the current
server. domain. It will not be included in the backup and not
be restorable.
System action:
System action: Processing continues but the specified
User response: Verify that the storage device is
datastores will not be included in the backup.
operational and accessible to the network. Make sure
there are no firewall issues. Verify that the profile User response: If the specified datastore is to be
settings for the included in the backup extend the domain to the
COPYSERVICES_PRIMARY_SERVERNAME and datacenter where it resides.
COPYSERVICES_SECONDARY_SERVERNAME
parameters are valid.
FMM7051E The environment variable
XINT_PROFILE is not set. It must be set
FMM6986E No matching target LUNs could be and contain the fully qualified path to
found in the selected target set for the the *.utl file to be used.
source volumes 'volume list' .
Explanation: The way Data Protection for SAP works
Explanation: is specified in a profile. When called, Data Protection
for SAP looks for the environment variable
System action:
XINT_PROFILE which must contain the fully qualified
User response: path to the profile.
System action:
FMM6988I Executed command: 'command'
User response: Check the environment for
Explanation: Shows the command executed in the log. XINT_PROFILE of the user who started Data Protection
for SAP.
System action: Processing continues.
User response: Not needed. FMM7052E Only one line of effective input is
allowed in the input file 'input filename'
FMM7048I The default port to connect to for the requested operation.
server_name will be used. Explanation: Only one line of effective input is
Explanation: A server port for the connection to the allowed in the input file for the requested operation.
named server was not explicitly specified. Therefore, System action: Processing ends.
the default port is used.
User response: Reduce the number of effective lines in
System action: the input file to one.
User response: Make sure the named server is
listening to the default port. In the case of connection FMM7053E Service setup failed due to previous
failures, specify the server port in the profile. error.
Explanation: Initialization of the product failed due to
previous errors.
System action:

118 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM7054I • FMM7062E

User response: Check the product log file for further User response: Check the product log file for further
detailed messages. detailed messages.

FMM7054I The datastore pattern 'datastore pattern' FMM7059E Service open failed because the file was
will be expanded within the defined not found.
domain.
Explanation: The command could not be started
Explanation: The specified datastore pattern will be because a file specified was not found.
expanded within the defined domain. Datastores that
System action:
match the pattern but are outside of the domain will
not be considered. User response: Check the product log file for further
detailed messages.
System action: Processing continues.
User response: Not needed.
FMM7060I Data Protection for SAP(R)
version.release.modification.level (build
FMM7055E Service open failed due to previous build_number)beta build_date session:
error in data mover. process id
Explanation: The command could not be started due Explanation: This message is to verify the version of
to previous errors. the shared library used for backup. On UNIX and
Linux systems this message will be written multiple
System action:
times into the log per backup depending on the RMAN
User response: Check the product log file for further setup. On Windows, it is written just once.
detailed messages.
System action:
User response: None, if the right version is used. If
FMM7056E Service open failed because configured
the version within the log does not match the installed
TSM server could not be accessed.
version, see 'RMAN Problem Resolution' in the Data
Explanation: The command could not be started Protection for SAP(R) Installation and User's Guide.
because the TSM server defined in the profile could not
be accessed.
FMM7061I Continuing to restore from next data
System action: copy.

User response: Check the product log file for further Explanation: A saved data copy could not be restored
detailed messages. from the primary data source. Due to multiple data
copies available, the unit will switch to the next
available data copy and continue to restore.
FMM7057E Service open failed because all
configured sessions are currently in use. System action:

Explanation: The command could not be started User response: Although the data could be restored it
because all configured sessions in the profile are should be investigated, why one of the data sources
currently in use. were not available.

System action:
FMM7062E To create number_copies redo log copies
User response: With Oracle RMAN the number of at least number_sessions sessions and
channels configured either in SAP profile or the RMAN number_mgmtclasses different
script must be less or equal to the maximum number of BRARCHIVE management classes are
allowed sessions (MAX_SESSIONS). If multiple servers required. But currently only
are used see the User's Guide for further details. Also configured_sessions sessions are available.
check the Data Protection for SAP log file for further
detailed messages. Explanation: If each redo log file should be stored
multiple times then for each copy a dedicated session
and management class at the Tivoli Storage Manager
FMM7058E Service open failed because more than server is required. Currently there are more redo log
one file was found with the same name. copies requested with the profile parameter
Explanation: The command could not be started REDOLOG_COPIES than sessions and/or management
because two or more files with the same name were classes are available.
found. System action: Processing ends.
System action: User response: Check the profile parameter

Chapter 2. FMM messages 119

FMM7063W • FMM7305E

MAX_ARCHIVE_SESSIONS or if not set check the User response: The absences of this files indicates a
value of parameter MAX_SESSIONS. Increase the value problem during the snapshot operation performed by
to be at least as large as number_copies. Ensure the Data Protection for Snapshot Devices for SAP(R). Please
overall number of sessions and management classes check the logs of DP for Snapshot Devices for SAP(R)
that are configured over all server stanzas in the Data to determine the cause of the problem and try again.
Protection for SAP profile is at least as large as
number_copies.
FMM7302W The 'vm template name' virtual machine
template with the 'vm instance uuid'
FMM7063W The profile parameter instance UUID is ignored and is not
BACKUPIDPREFIX is no longer valid part of the backup since it is a template.
for Data Protection for SAP HANA and
Explanation: The specified VM template is not part of
will be ignored.
the backup and will thus not be restorable.
Explanation: Starting with version 6.4.1.1 it is no
System action: Processing continues.
longer possible to specifiy the backup ID prefix for
Data Protection for SAP HANA. The first six characters User response: No action is required.
of the backup ID are now generated automatically.
System action: Processing continues. FMM7303W Profiles for Data Protection for Snapshot
Devices for SAP are different. backup:
User response: Remove the parameter
file name backup restore: file name restore
BACKUPIDPREFIX from the profile.
Explanation: During backup the profile used by DP
for Snapshot Devices can be determined automatically.
FMM7064W Seems the previous operation was not
For restore and inquire operations the profile for DP for
completed successfully. Cleaning up.
Snapshot Devices must be specified in the profile using
Explanation: Internal states indicate that an operation the parameter FCS_FILE. For restore DP for Snapshot
is still running while a new one has started. This may Devices must use the same profile as for backup.
be caused by database processes that did not terminate
System action:
correctly. Data Protection for SAP is going to clean up
these internal states to avoid potential problems. User response: Correct the entry for the FCS_FILE
parameter in the profile (init<SID>.utl).
System action: Processing continues.
User response: Check if any database processes from
FMM7304I Performing DISK ONLY backup.
previous backup or restore operations are still active.
Consult the users guide of the database about how to Explanation: The data for this backup is stored on
clean up such processes. snapshot–type disks only and will not be sent to TSM.
System action:
FMM7065W The executable 'executable_name' was
called using the obsolete function User response: None.
specification 'obsolete_function'. You must
use the updated function specification FMM7305E Error during call to Data Protection for
'-f function' instead. Snapshot Devices for SAP: error message
Explanation: An operation was started using an Explanation: DP for Snapshot Devices could not
obsolete function. The obsolete function is accepted, but process the requested operation successfully. Processing
it will be rejected in a future release of the product. may not stop at this point. Depending on the type of
System action: Processing continues. request (backup to both TSM and snapshot disks or to
snapshot disks only, restore of data which is available
User response: For future operations, use the updated in both modes) there are possibilities to recover from
function specification that is identified in the message. this error and continue operation.
System action:
FMM7301W Data exchange file from Data Protection
for Snapshot Devices for SAP, filename User response: Use the information from error message
does not exist. and the output of DP for Snapshot Devices to
determine the cause of the problem and try again.
Explanation: The referenced file is expected by Data
Protection for SAP(R) to exist and to contain
information from Data Protection for Snapshot Devices
for SAP(R) about the actual snapshot operation.
System action:

120 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM7307W • FMM7315W

FMM7307W Data Protection for Snapshot Devices FMM7311I Profile used by Data Protection for
for SAP reported an error during a Snapshot Devices for SAP: profile name.
snapshot–type operation. Do you want
Explanation: The message shows the name of the
to continue backing up to TSM?
profile used by DP for Snapshot Devices.
Explanation: The backup was requested to be stored
System action:
on both the TSM server and the snapshot–type disks.
The snapshot operation has failed. Backup can continue User response: None.
to save data on the TSM server only.
System action: FMM7312W Profile for Data Protection for Snapshot
Devices for SAP not specified in profile.
User response: Enter 'stop' if you want to solve the
For restore this must be specified.
cause of this error and to try again. Enter 'cont' if you
want to save this data on the TSM server only. Explanation: For restore and inquire operation in
conjunction with DP for Snapshot Devices this
parameter is mandatory. Without this parameter a
FMM7308E DISK ONLY backup has failed.
restore using DP for Snapshot Devices is not possible
Explanation: The current backup tried to store data on and Data Protection for SAP will continue to
snapshot–type disks only and did not finish inquire/restore from the TSM server only.
successfully.
System action:
System action:
User response: Add the parameter FCS_FILE to the
User response: Check the output from DP for Data Protection for SAP profile.
Snapshot Devices prior to this error message to detect
the root cause of this error and try again.
FMM7313W Inquire results from Data Protection for
Snapshot Devices for SAP are not
FMM7309W Data Protection for Snapshot Devices available.
for SAP reported an error during a
Explanation: Data Protection for SAP queried Data
snapshot–type operation. Do you want
Protection for Snapshot Devices for SAP for existing
to continue restoring from TSM?
snapshot backups. This query has failed.
Explanation: The data you wanted to be restored is
System action: Processing continues.
located on the TSM server and on snapshot–type disks.
The snapshot operation has failed. The process can User response: If Data Protection for SAP is running
continue to restore data from the TSM server. in unattended mode (profile parameter BATCH set to
YES), it immediately restores from tape when data is
System action:
available. Otherwise you are prompted whether to
User response: Enter 'stop' if you want to resolve the restore from tape.
cause of this error and to try again. Enter 'cont' if you
want to restore from the TSM server.
FMM7314E The data you want to restore is not
available on the TSM server.
FMM7310W Data Protection for Snapshot Devices
Explanation: Data Protection for SAP(R) was unable
for SAP reported an error during a
to retrieve information from DP for Snapshot Devices
snapshot–type operation. CAUTION:
about available backups on snapshot–type disks. This
Not all filesystems are available. Do you
message may be issued in consequence of message
want to retry the operation?
FMM7305E.
Explanation: In contrast to message FMM7309W not
System action:
all file systems are mounted. In this case it is not
possible to continue the restore from the TSM server. User response: Check the output from DP for
Snapshot Devices to determine the cause of the error
System action:
and try again.
User response: Enter 'stop' if you want to terminate
this restore process. Enter 'cont' if you want to retry the
FMM7315W The copy process for the files you want
snapshot process.
to restore is not finished. If you
continue the operation, the files will be
restored from the TSM server.
Explanation: The snapshot process running in the
background has not finished moving the files from the

Chapter 2. FMM messages 121

FMM7316I • FMM7324E

source to the target volumes. A snapshot restore of Devices for SAP profile v does not point to the same
these volumes is currently not possible. Data Protection for Snapshot Devices for SAP
configuration file which was used by the preceding
System action:
Data Protection for Snapshot Devices for SAP splitint
User response: After that message you will be asked if operation.
you want to continue or stop this operation. If you
System action:
want to wait until the snapshot process has finished
choose 'stop' and the restore attempt will terminate. If User response: You need v to correct the FCS_FILE
you choose 'continue' an attempt is made to restore the parameter in order to ensure that a valid Data
data from TSM if available. Protection for Snapshot Devices for SAP profile is used.
For example, select the same file Data Protection for
Snapshot Devices for SAP used when running its
FMM7316I The following backup types for the
snapshot function in the preceding brbackup task. The
BACKUPID backup id have been found:
file names are documented in preceding message
– TSM – Snapshot
FMM7303W) v to ensure that all SAP profiles used by
Explanation: The backup for the backup ID Backup ID Data Protection for Snapshot Devices for SAP point to
was stored on the Tivoli Storage Manager as well as on the same the same control file. The control file is
snapshot–type disks. For restore both data sources can defined by the value of the IDS_CONTROL_FILE
be used. parameter in the Data Protection for Snapshot Devices
for SAP profile.
System action:
User response: None. FMM7322E Request for a partial restore or restore
from snapshot with "brrestore –m all" is
FMM7318E The Data Protection for Snapshot not supported. In case of brrestore
Devices for SAP profile file name is not attempt rerun with –m full.
valid. Explanation: DP for Snapshot Devices can only restore
Explanation: The profile for DP for Snapshot Devices the whole content of a backup and not only a subset of
specified in init<SID>.utl could not be accessed. a disk backup as requested. Most likely this is caused
by running brrestore with the option '–m all'.
System action:
System action:
User response: Check the file name and the
permissions for this file and try again. User response: Restore complete backups only: run
brrestore with the option '–m full'.

FMM7319I Start TSM restore.

FMM7323W Request for a partial restore or restore
Explanation: The restore uses data from Tivoli Storage from snapshot with "brrestore –m all" is
Manager. not supported. If you want to restore the
System action: backup: – with FlashCopy restore enter
stop and rerun brrestore with "–m full"
User response: None. – from TSM enter cont
Explanation: This message has the same reason as
FMM7320I Start restore from snapshot. message FMM7322E, but in this case the data is also
Explanation: The restore is using data from available from the TSM server. So you may continue to
snapshot–type disks. restore this data without the snapshot functionality
from TSM server.
System action:
System action:
User response: None.
User response: Enter 'stop' if you want to try to
restore a different set of files. Enter 'cont' if you want to
FMM7321E The Data Protection for Snapshot restore this data from TSM server.
Devices for SAP profile file name found
in parameter FCS_FILE of the DP for
SAP(R) profile can not be used if you FMM7324E Restore of multiple backup ID's in one
need to restore this backup. run from a snapshot is not possible.

Explanation: In the Data Protection for SAP profile the Explanation: The data requested for this restore
FCS_FILE parameter is set, however the Data belongs to multiple backup IDs.
Protection for Snapshot Devices for SAP profile System action:
specified either v is not a Data Protection for Snapshot

122 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM7325E • FMM7546E

User response: Make sure the files you want to restore User response: Ensure the operation is performed by
belong to one single backup ID and try again. the Oracle database instance owner and verify that the
environment for this user is set correctly. Among other
environment variables that are required to run an
FMM7325E Redirected restore from a snapshot is
Oracle database the variable ORACLE_SID must be set.
not possible.
Explanation: A restore of a snapshot to a different
FMM7542I A level number incremental backup
location on the same host was attempted. This is not
using Oracle RMAN has started.
supported.
Explanation: Oracle RMAN will be started to perform
System action: Processing stops.
an incremental backup with the specified level.
User response: Either restore the snapshot to the
System action: Operation continues.
original location or restore from tape (if available).
User response: None.
FMM7535W Error while executing command. Reason:
errno(error number) explanation FMM7543I Recreate database control file 'file_name'.
Explanation: A command could not be executed Explanation: CURRENTLY UNUSED
successfully.
System action: Operation continues.
System action:
User response: None.
User response: Check the explanation explanation and
the preceding output of the command execution to
FMM7544E The copy of the database control file
detect the cause of the error.
'file_name' was not found.
Explanation: The current operation does expect a copy
FMM7536I Execute command 'command name':
of the database controlfile to be at the specified
Explanation: The command command name is executed location. This file is created by IBM Tivoli Storage
by the application. This message is followed by the FlashCopy Manager before Data Protection for SAP is
output of the command executed. started. But the file was not found.
System action: System action: Operation aborts.
User response: None. User response: Verify that the target directory does
exist and is not full. Make sure that the directory is not
cleaned automatically at the time of the operation.
FMM7540E None of the INCREMENTAL_LEVEL
parameters specified in the profile can
be used for the current operation. FMM7545I Please enter the password for the user
'user_name' to connect against the
Explanation: The application of a
recovery catalog database
'INCREMENTAL_LEVEL' entry within the profile can
'catalog_database_identifier':
be restricted by a number of optional conditions, e.g.
by time frame. If this error occurs none of the Explanation: Oracle RMAN stores information about
INCREMENTAL_LEVEL entries within the profile all backups in a recovery catalog database. The
matches the conditions currently given (current time, identifier to connect against this database and the user
given weekday). id for this connection must be specified in the profile.
The password for this connection must be specified
System action:
after this prompt. It is then stored encrypted in the
User response: Check the conditions specified for the configuration file.
'INCREMENTAL_LEVEL' entries within your profile. It
System action: Wait for user response.
needs to be ensured that exactly one entry matches any
imaginable condition at any time. User response: Enter the correct password.

FMM7541E The environment variable ORACLE_SID FMM7546E Failed to verify the password. This is
must be set. the output of the failed command:
Explanation: The current operation requires the Explanation: The verification of the password entered
environment of the Oracle database instance owner. has failed. This may be due to missconfiguration of the
Among other settings this includes the environment connection to the recovery catalog database or just by
variable ORACLE_SID. misstyping the password.
System action: Operation aborts. System action: Operation aborts.

Chapter 2. FMM messages 123

FMM7547E • FMM7556E

User response: Check the further ouput to find the message for more details about the root cause of this
root cause. Retry the operation and enter the correct error.
password.
FMM7552E Failed to determine the SCN:
FMM7547E Failed to verify the password. This is
Explanation: The process failed to determine the
the output of the failed command:
restore point in time in the recovery catalog database.
Explanation:
System action: Operation aborts.
System action: Operation aborts.
User response: Check the log output following this
User response: message for more details about the root cause of this
error.
FMM7548E Incremental backups require IBM Tivoli
Storage FlashCopy Manager V3.1 or FMM7553I Restoring files from backup with ID
higher. backup_ID using Oracle RMAN ...
Explanation: To perform offloaded backups using Explanation: Oracle RMAN was started to restore all
Oracle RMAN the offload operation must be performed datafiles from the backup identified by backup_ID.
using IBM Tivoli Storage FlashCopy Manager Version
System action: Operation continues.
3.1 or higher.
User response: None.
System action: Operation aborts.
User response: Ensure the required version of IBM
FMM7554E The password to connect against the
Tivoli Storage FlashCopy Manager is installed and
recovery catalog database 'identifier' is
configured.
not set.
Explanation: The password for the recovery catalog
FMM7549E Database 'identifier' is still running on
database was not found in the config file. It is stored in
host 'host_name'.
encrypted form in the config file. To store the password
Explanation: Another instance of the database was in the config file the function '$ndash;f
found to be running on the backup server where the catalog_password' must be used.
offloaded backup should be performed.
System action: Operation aborts.
System action: Operation aborts.
User response: Run 'backint –p <profile> $ndash;f
User response: Verify the configuration if the catalog_password' to store the password in the config
offloaded backup was attempted on the correct backup file. Then retry the operation.
server. Check if the running database instance is a
leftover from a previous backup attempt. In this case
FMM7555E Files from different RMAN backups can
manually shutdown the instance and retry.
not be restored within a single
operation.
FMM7550E Operation was cancelled by Oracle
Explanation: The current operation attempted to
RMAN. Please check the log for more
restore files that have been stored by RMAN in
details.
different backups. This type of restore is not supported.
Explanation: The operation was cancelled by Oracle
System action: Operation aborts.
RMAN.
User response: If files from different backups are
System action: Operation aborts.
required only the files from one backup can be restored
User response: Check the log output preceeding this at a time. Restore files from other backups in separate
message for more details about the root cause of this runs.
error.
FMM7556E Restore of RMAN backups to a different
FMM7551E Failed to determine the database ID: location is not supported.
Explanation: The process failed to determine the id of Explanation: The current operation attempted to
the database in the recovery catalog database. restore database files to a location that is different from
the location at backup time. This type of restore is not
System action: Operation aborts.
possible with backups that have been performed by
User response: Check the log output following this Oracle RMAN from a flashcopy backup.
System action: The operation stops.

124 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8201E • FMM8207E

User response: Restore the files to the same location also be specified in the device class.
from where they have been backed up. If you want
System action: Command will fail.
create a clone of the database, use the $longfcm;
cloning functionality. User response: In mirroring environments, add the
STORAGE_SYSTEM_ID parameter to the device class.
In non-mirroring environments, you can remove the
FMM8201E SIMULATION CANCELED BY
STORAGE_SYSTEM_ID parameter from the volumes
PRODUCTION OPERATION!!!
set definition.
Explanation: The current operation was a simulation
performed via the Administration Assistant. This
FMM8205E There are no target sets specified in the
simulation was canceled since a production operation
volumes file that can be used with device
(backup or restore) has been started.
section .
System action:
Explanation: The volumes file (specified with the
User response: Check your backup schedule and run VOLUMES_FILE parameter in the device section) does
simulations only when no other operations are not contain a target set definition.
scheduled.
System action: Command will fail
User response: Add target set definitions to the
FMM8202E There are no target sets specified in the
volumes file specified with the VOLUMES_FILE
volumes file that can be used with device
parameter.
section and parameter 'value'.
Explanation: The volumes file (specified with the
FMM8206W The parameter profile parameter refers to
VOLUMES_FILE parameter in the device section) does
the device class section(s) 'device class'
not contain a target set definition which can be used in
which do not exist currently in the
a context where parameter is set to value.
profile. Currently existing device class
System action: Command will fail. sections are: 'existing device class' If you
proceed the missing device class
User response: Add target set definitions to the
sections are added to the profile
volumes file (specified with the VOLUMES_FILE
automatically. If this is not intended,
parameter) that are appropriate for the context.
you must modify the specified device
class names.
FMM8203E There are no volume sets specified in
Explanation: The specified profile parameter is
the volumes file that can be used with
referring to one or multiple device class sections that
'device class' and STORAGE_SYSTEM_ID
are not specified in the profile.
set to 'hardware id'.
System action: Processing continues.
Explanation: The volumes file (specified with the
VOLUMES_DIR parameter in the device section) does User response: You must add the missing device class
not contain a volume set definition for a storage device section to the profile or adjust the specified profile
identified with hardware id. parameter.
System action: Command will fail.
FMM8207E Directory target dir does already exist. To
User response: Add an appropriate volume set
perform IBM Tivoli Storage FlashCopy
definition to the volumes file or update and identify an
Manager tape backup this directory
existing volume set for use with the specified hardware
must not exist. After deleting this
ID.
directory run an unmount and perform
the tape backup again.
FMM8204E All volume sets that are specified in the
Explanation: During tape backup process the path of
volumes file identified in 'device class'
this directory is required to set up backup DB2
require that the parameter
properly
STORAGE_SYSTEM_ID also be
specified in the device section of the System action:
profile.
User response: Delete the directory. Afterwards run
Explanation: A STORAGE_SYSTEM_ID is specified for fcmcli -f unmount to clean up the backup system. Start
all volumes sets in the volumes file (specified with the fcmcli -f tape_backup again.
VOLUMES_DIR parameter in device section). This is
typically the case in mirroring environments. In this
situation, the STORAGE_SYSTEM_ID parameter must

Chapter 2. FMM messages 125

FMM8268E • FMM8308E

FMM8268E The database resides on FMM8303E No segment_name section found for the
'database_volume_mgr' volumes but the instance 'id'.
profile specifies 'profile_volume_mgr' as
Explanation: An error was detected while parsing the
the volume manager.
named profile segment name section.
Explanation: The files to be backed up were found on
System action:
a volume manager that is different from the volume
manager specified in the profile. User response: Check the named profile segment
name section and make appropriate adjustments.
System action: Processing ends.
User response: Specify the correct volume manager in
FMM8304W The following error occured while
the profile.
verifying the configuration for section
'section':
FMM8300I Function_name returned with code
Explanation: An error was detected while parsing the
return_codereturn_information.
named profile section.
Explanation: This message indicates that the named
System action:
API function ended with the specified return
information. User response: Check the named profile section and
make appropriate adjustments.
System action:
User response: If the return information indicates a
FMM8305E Invalid option option in options string:
problem, look for preceding error messages in the log
'options_string'.
files. Otherwise, no response is required.
Explanation: An invalid option was found while
parsing the options string specified in the 'db2'
FMM8301E Product_name: Exception caught in
command.
function function_name. Error
information: 'error_information' System action:
Explanation: The named product implementing the User response: Correct the command and try again.
DB2 Advanced Copy Services API received an error in
the named API function. The error information is
shown. FMM8306E The keyword keyword is not allowed
multiple times within the profile.
System action:
Explanation: The keyword indicated was found more
User response: Analyze the error information to find than once in the profile. However, this keyword must
the cause of the problem. Resolve any problems not be specified multiple times.
indicated.
System action:

FMM8302E Product_name: Exception caught in User response: Correct the profile.

function function_name. More
information may be available in file FMM8307E The parameter keyword must be specified
log_file_name. Error information: in the profile.
'error_information'
Explanation: A required keyword is missing in the
Explanation: The named product implementing the profile.
DB2 Advanced Copy Services API received an error in
the named API function. The error information is System action:
shown. User response: Correct the profile.
System action:
User response: Analyze the error information and the FMM8308E Single argument required for parameter
appropriate log files to find the cause of the problem. keyword.
Resolve any problems indicated. Explanation: The keyword indicated requires a single
value. However, two or more values are found in the
profile.
System action:
User response: Correct the profile.

126 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8309E • FMM8319W

the current version of the library.

FMM8309E Missing argument for parameter
keyword. System action:
Explanation: In the profile, a value is missing for the User response: Contact your IBM support personnel.
named parameter.
System action: FMM8315E Function_name: The following object is
not under the control of product_name:
User response: Correct the profile.
path
Explanation: The named product implementing the
FMM8310E The keyword keyword is not allowed.
DB2 Advanced Copy Services API detected a problem
Explanation: An invalid keyword was detected in the in the named API function: The path passed by the
profile. database is not under the control of the product.
System action: System action:
User response: Correct the profile. User response: Make sure the database to be backed
up meets the requirements for employing snapshot
backups.
FMM8311E For parameter keywortd, both server and
port must be specified.
FMM8316E Product_name: interface problem in
Explanation: A value of the named parameter is
function function_name: Empty group list
missing from the profile.
passed by DB2.
System action:
Explanation: The named product detected an interface
User response: As the value for the specified problem in the named API function: The database
parameter, specify both server and port. passed a group list containing no elements.
System action:
FMM8312E Error while parsing parameter keyword.
User response: Contact your IBM support personnel.
In order for 'value1' to be valid 'value2' is
required to be an existing directory.
FMM8317W Product_name: Verification of
Explanation: Value1 was found to be an invalid value
configuration requested by user. No
for the parameter named. For this specific parameter, a
backup started.
file name can be specified whose path must already
exist in the system. Explanation: The user requested a verification of the
configuration. The backup flow continued without
System action:
errors up to the point where the snapshot would
User response: Specify the name of a file in an actually be done and was then cancelled. The system is
existing path. ready for a snapshot backup, but no action beyond
verification has been taken so far.

FMM8313E Product_name: interface problem in System action:

function function_name: Invalid value of
User response: None.
parameter: value
Explanation: The named product detected an interface
FMM8318E Product_name: interface problem in
problem in the named API function. An invalid value
function function_name: Not enough
was found for parameter in one of the API data
space provided to write meta data.
structures.
Explanation:
System action:
System action:
User response: Contact your IBM support personnel.
User response: Contact your IBM support personnel.
FMM8314E Product_name: interface problem in
function function_name: The session is FMM8319W Error while deleting old versions. This
already in use by a different operation. problem does not affect the new
backup. Error information:
Explanation: The named product detected an interface
'error_information'
problem in the named API function. Either the session
handle is used for various operations simultaneously, Explanation: After a successful backup, the system
or the functions are called in an order not supported by tries to remove older backups of the database according

Chapter 2. FMM messages 127

FMM8320I • FMM8328E

to the value of profile parameter MAX_VERSIONS. appropriate log files to find the cause of the problem.
However, a problem occurred while trying to remove Resolve any problems indicated.
expired backups. The new backup is not affected by
this problem.
FMM8324E Product_name: Problem occurred while
System action: processing function_name: Device agent
returned code return_information.
User response: Check the appropriate log files in
order to determine the cause of the problem. Resolve Explanation: The named product implementing the
any problems indicated. In case the storage device runs DB2 Advanced Copy Services API received an error
out of storage because outdated snapshot backups have from the device agent in the named API function. The
not been removed, delete these snapshot backups device agent's return information is given.
manually.
System action:
User response: Check the appropriate log files to find
FMM8320I Deleting full backup backup_id –
the cause of the problem. Resolve any problems
backup_key.
indicated.
Explanation: After a successful backup, the system
tries to remove older backups of the database according
FMM8325E Failed to determine hostname.
to the value of profile parameter MAX_VERSIONS.
During this process, the full backup listed is removed. Explanation: The system was not able to determine
the host name of the machine.
System action:
System action:
User response: None.
User response: Make sure the system setup allows for
querying the hostname via system function
FMM8321I Deleting partial backup backup_id for
gethostname(). Ensure that the requirements for doing
node host:partition_number.
snapshot backups are met.
Explanation: After a successful backup, the system
tries to remove older backups of the database according
FMM8326E Failed to create log directory path.
to the value of profile parameter MAX_VERSIONS.
During this process, the backup listed for the named Explanation: The log path indicated is not available in
partition is removed. the system and could also not be created.
System action: System action:
User response: None. User response: Check the properties of the path
indicated and make sure that its properties and the
properties of the parent directory are set accordingly.
FMM8322E Interface problem: Current database
Make sure all prerequisites for doing snapshot backups
partition number is not listed in the
are met.
partition list.
Explanation: The partition list passed by the database
FMM8327E Invalid value specified for parameter
does not contain the named partition participating in
keyword: value
an operation.
Explanation: A parameter value is not valid.
System action:
System action:
User response: Contact your IBM support personnel.
User response: In case the parameter was specified in
the profile correct the profile. In case the parameter was
FMM8323E Product_name: Problem occurred while
specified as a command line option, correct the entry.
processing function_name. Please check
log file log_file_name for more
information. Error information: FMM8328E Product_name must be licensed to set
'error_information' parameter keyword to a value of value.
Explanation: The named product implementing the Explanation: Selected functions are supported only
DB2 Advanced Copy Services API received an error in with a full TSM license.
the named API function. The error information is
shown. System action:

System action: User response: If you need the functionality

requested, obtain a full TSM license and install the
User response: Analyze the error information and the license file. Otherwise, in case the parameter was

128 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8330E • FMM8339E

specified in the profile, correct the profile or, in case the

FMM8335E Profile section section_name refers to a
parameter was specified as a command line option,
value for keyword that differs from the
correct the entry.
one used at backup time. Expected
value: value.
FMM8330E Parameter keyword requires 'YES', 'NO',
Explanation: The profile parameter named must not
or AUTO.
change its value between backup and restore. However,
Explanation: For the named parameter, only the in the named profile section, the parameter has a value
values, 'YES', 'NO' and 'AUTO' are accepted. different from the value it had at backup time. This
value is given in the message.
System action: Processing stops.
System action:
User response: Correct the profile or the call as
appropriate. User response: Correct the profile by setting the
indicated parameter to the value indicated in the
message.
FMM8331E The parameter keyword1 is not allowed if
keyword2 is set to value.
FMM8336E Invalid value specified for option
Explanation: There is a dependency between keyword: value
parameters keyword1 and keyword2. If the latter is set to
the value named, keyword1 must not be specified. Explanation: An option value is not valid.
System action: System action:
User response: Correct the profile or the call as User response: Correct the call.
appropriate.
FMM8337E Error while parsing profile: Missing
FMM8332E Failed to parse parameter keyword. File section name.
and path names in the profile need to
Explanation: The profile is organized into named
be fully qualified.
sections. However, a section name was not found.
Explanation: As the value of the parameter indicated,
System action:
a fully qualified file or path name is expected.
However, the specified value is not a fully qualified User response: Check that the profile name is
path. specified correctly or that the default profile is a valid
profile. Refer to your user documentation for the syntax
System action:
of the profile or use the profile wizard to create a new
User response: Correct the profile or the call as profile.
appropriate.
FMM8338E Error while parsing profile: Section
FMM8333E In order to enable the parameter section_name is not allowed to be nested.
keyword1 you need to set keyword2 to
Explanation: In the profile, the named section starts
value.
before the previous section ends. However, the section
Explanation: There is a dependency between in question cannot be nested.
parameters keyword1 and keyword2. If keyword1 is
System action:
specified, keyword2 must be given the specific value
indicated in the message. User response: Correct the profile.
System action:
FMM8339E Error while parsing profile: Profile
User response: Correct the profile or the call as
section section_name is not valid.
appropriate.
Explanation: An invalid section name was found in
the profile.
FMM8334E Profile section section_name is required
for function operation. System action:
Explanation: The specified profile section is required User response: Correct the profile.
in order to perform the requested operation. However,
it is not included in the profile.
System action:
User response: Correct the profile.

Chapter 2. FMM messages 129

FMM8340E • FMM8353E

FMM8340E Error while parsing profile: Profile FMM8349I Deleting incomplete backup backup_id –
section section_name must not be backup_key.
specified more than once.
Explanation: After a successful backup, the system
Explanation: In the profile, only a single section with tries to remove older backups of the database according
the name indicated can be specified. However, during to the value of profile parameter MAX_VERSIONS.
parsing, a second occurrence was detected. During this process, the incomplete backup listed is
removed. A backup becomes incomplete when parts of
System action:
its data expire. This can happen when a backup that is
User response: Correct the profile. marked 'destructively restorable' is restored.
System action:
FMM8341E Error while parsing profile: Profile
User response: None.
section section_name missing.
Explanation: The required profile section indicated
FMM8350E Parameter parameter requires 'NO',
was not found in the profile.
'TSM', or 'DP4SAP'.
System action:
Explanation: The value specified for the named
User response: Correct the profile. parameter does not comply with the defined range of
values.

FMM8343W The profile parameter keyword profile System action:

parameter of device type provile section has
User response: Check the named profile keyword and
changed its value from (original)value1 to
make appropriate adjustments.
(current) value2.
Explanation: The profile parameter named must not
FMM8351E Parameter parameter requires 'AUTO' or
change its value between backup and restore or delete.
a decimal value.
However, in the named profile section, the parameter
has a new value value2 different from the value value1 Explanation: The value specified for the named
it had at backup time. Both values are given in the parameter does not comply with the defined range of
message. values.
System action: System action:
User response: Check the log file for problems that User response: Check the named profile keyword and
may result from the change of parameter values. If so, make appropriate adjustments.
you may want to change the profile, restoring
parameter profile parameter keyword to the value it had
FMM8352E Parameter parameter requires a decimal
when creating the backup in order to perform a specific
value.
operation.
Explanation: The value specified for the named
parameter does not comply with the defined range of
FMM8344E Path path is listed more than once for
values.
partitioning.
System action:
Explanation: This is a DB2 – TSM interface problem.
User response: Check the named profile keyword and
System action:
make appropriate adjustments.
User response: Contact your IBM support personnel.
FMM8353E Parameter parameter requires a value
FMM8345E Error while parsing parameter keyword. greater than '0'.
'path' is required to be type_information.
Explanation: The value specified for the named
Explanation: A path of the type indicated in the parameter does not comply with the defined range of
message is expected as a value of the named parameter. values.
However, the specified path was not found to be of the
System action:
correct type.
User response: Check the named profile keyword and
System action:
make appropriate adjustments.
User response: Correct the profile or the call as
appropriate.

130 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8354E • FMM8362E

FMM8354E Parameter parameter requires 'NO' or FMM8359E The profile parameter parameter has the
'YES'. wrong value 'value profile'. The expected
value is 'value expected'.
Explanation: The value specified for the named
parameter does not comply with the defined range of Explanation: A profile parameter (or keyword) has a
values. wrong value assigned. An alternate value is expected.
System action: System action:
User response: Check the named profile keyword and User response: Check the named TSM for ERP profile
make appropriate adjustments. keyword and make appropriate adjustments.

FMM8355E Parameter parameter requires 'ALL' or a FMM8360E Invalid keyword specified in the profile.
comma separated list of decimal values.
Explanation: The value specified for a keyword is
Explanation: The value specified for the named either wrong or is missing.
parameter does not comply with the defined range of
System action:
values.
User response: Check the named TSM for ERP profile
System action:
keyword and make appropriate adjustments.
User response: Check the profile keyword
DBPARTITIONNUM and make appropriate
FMM8361E Found files on the file systems to
adjustments.
backup for which backup was not
explicitly requested. Please provide a
FMM8356E product_name: interface problem in negative list or clean your file systems.
function function: Invalid call sequence;
Explanation: Although the previously mentioned files
the library was not initialized.
were not requested to be part of the backup, they will
Explanation: An invalid internal call sequence was be copied because they reside on a file system that will
detected during execution of a dedicated function. be backed up in its entirety. In order to allow backing
up those files, they need to be added to a 'negative list'
System action:
or the checking for such files needs to be disabled.
User response: Check the logs for further information. Note that in case of a restore, these files would
If the problem cannot be resolved contact your IBM typically be restored, even if this was not desired.
support personnel.
System action:
User response: Edit the 'CLIENT' section of the
FMM8357E product_name: interface problem in
profile. You can either set the parameter
function function: Invalid call sequence;
'NEGATIVE_LIST' to 'NO_CHECK', to allow IBM Tivoli
the operation was not initialized.
Storage FlashCopy Manager to back up any file stored
Explanation: An invalid internal call sequence was in a file system that will be backed up, or you can set
detected during execution of a dedicated function. the parameter 'NEGATIVE_LIST' to point to a file (the
'negative list') that contains a list of all files and
System action: directories that are allowed to be processed during
User response: Check the logs for further information. backup. Any directory you add to the 'negative list' is
If the problem cannot be resolved contact your IBM processed recursively. Note that there is only one
support personnel. 'negative list' for backup and restore. See FMM6969E
for restore.

FMM8358E Parameter name requires 'ONLINE' or

'OFFLINE'. FMM8362E The trace parameters YES, NO, ON, and
OFF cannot be set in conjunction with
Explanation: The parameter name only accepts the other trace parameters.
values ONLINE or OFFLINE.
Explanation: The values YES, NO, ON and OFF in
System action: Processing stops. conjunction with the TRACE keyword do not allow
User response: Correct the value for the parameter further trace flags to be set. They are mutually
specified in the profile. exclusive.
System action:
User response: Check the TSM for ERP profile
keyword TRACE and make appropriate adjustments.

Chapter 2. FMM messages 131

FMM8363E • FMM8372E

FMM8363E The value value is not a valid trace flag. FMM8368E An invalid argument is specified for
keyword keyword.
Explanation: The value specified for the TRACE
keyword is invalid. Explanation: The specified argument could not be
converted into an equivalent integer value.
System action:
System action:
User response: Check the TSM for ERP profile
keyword TRACE and make appropriate adjustments. User response: Check the keyword argument and try
again. If the problem cannot be resolved contact your
IBM support personnel.
FMM8364E Error while parsing parameter
CONFIG_FILE. Directory 'directory' for
node 'node' does not exist. FMM8369E Failed to execute program. Reason: reason.
Explanation: The base directory containing the TSM Explanation: The execution of program failed.
for ERP configuration file(s) for any participating DB2
System action:
partition does not exist or cannot be accessed.
User response: Check the logs for further information.
System action:
If the problem cannot be resolved contact your IBM
User response: Ensure that the directory denoting the support personnel.
base part of the CONFIG_FILE value (left part of the
%DB2NODE substring) exists and has the right
FMM8370E The profile option
permissions.
TARGET_DATABASE_SUSPEND= OFFLINE is not
allowed for an online database backup.
FMM8365E The server stanza for LOG_SERVER
Explanation: A snapshot backup of a database that
'server' is missing.
was not suspended can only be done in offline mode.
Explanation: A TSM server stanza used by the
System action:
LOG_SERVER keyword is missing either in the option
file (dsm.opt) or in the system options file (dsm.sys). User response: Start the BRBACKUP utility with the
option '–t offline -d util_vol' and try again.
System action:
User response: Either the value of the LOG_SERVER
FMM8371E The profile parameter NEGATIVE_LIST
keyword in the TSM for ERP profile has to be adjusted
is not allowed. Use BR–TOOLS option
or an entry must be made or adjusted in the
"–n" to specify the negative list.
appropriate option file.
Explanation: The negative list value has to be
specified in the init<SID>.sap profile via the option
FMM8366E The values for parameter parameter are
'util_vol_nlist = (nfile_name1, nfile_name2, ...) |
expected to be in the range 0 to 6.
no_check'.
Explanation: The values of the keyword USE_AT have
System action:
to be in the range of 0 to 6.
User response: Adjust the init<SID>.sap profile
System action:
accordingly and try again.
User response: Check the TSM for ERP profile
keyword USE_AT and make appropriate adjustments.
FMM8372E The profile option
TARGET_DATABASE_SUSPEND=YES
FMM8367E You cannot freeze the filesystem requires a backup of type
without suspending or shutting down volume_online. To solve this problem
the database. either the profile parameter
TARGET_DATABASE_SUSPEND can be
Explanation: Check the TSM for ERP profile keyword
set to OFFLINE or NO or the brbackup
USE_AT and make appropriate adjustments.
backup device type should be set to
System action: util_vol_online. Keep in mind, when
you set the profile parameter
User response: Ensure either to suspend the database TARGET_DATABASE_SUSPEND to
or to bring the database offline and try to freeze the NO, the snapshot backup will be
filesystem again. mounted on a backup system to verify
its consistency. Make sure that a backup
system is configured in that case.

132 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8373W • FMM8382E

Explanation: A snapshot backup of a database that backup requests. This is currently not supported.
was suspended can only be done in online mode.
System action:
System action:
User response: Use backups stored on the TSM server
User response: Start the BRBACKUP utility with the to perform redirected restores or adjust the restore
option '–t online -d util_vol' and try again. command.

FMM8373W The operation will execute the force FMM8378E Redirected restore of volume backups is
option (–F). not supported yet.
Explanation: Start the BRBACKUP utility with the Explanation: TSM for ACS does not support restores
option '–t online -d util_vol' and try again. to an alternate data location. The restore always needs
to be made to the original data location.
System action:
System action:
User response: None.
User response: Use backups stored on the TSM server
to perform redirected restores.
FMM8374W Operation will terminiate with error,
because backint was executed with
verify option (–V). FMM8379E Infile contains an invalid value: 'value'
Explanation: The verify option simulates the Explanation: Each record of the infile has to start
requested option and does not create a valid backup or either with the string '#NULL' or with the backup Id.
restore. In order to prevent the calling process from
System action:
regarding the current operation as successful, the verify
option will always yield a nonzero return code. User response: Ensure each record of the infile
satisfies the requirements. If the problem cannot be
System action:
resolved contact your IBM support personnel.
User response: Do not use the verify option if you
want to create a backup or restore.
FMM8380E The profile option TSM_BACKUP=YES
requires a snapshot backup of all
FMM8375E The value of the environment variable partitions of the database.
ORACLE_SID is not allowed to have
Explanation: The profile option TSM_BACKUP=YES
more than number digits.
implies offloading a snapshot backup to TSM. If this
Explanation: The length of the ORACLE_SID value option is specified, all database partitions have to be
violates the defined range. part of the snapshot backup.
System action: System action:
User response: Check the current value of User response: Specify the 'ALL
ORACLE_SID and if necessary, correct it according to DBPARTITIONNUMS' clause as part of the DB2 backup
the allowed length. Try again. command and try again.

FMM8376E Verification of snapshot failed. Reason: FMM8381W The following error occured while
reason verifying the configuration for server
'server_name' in the profile:
Explanation: The snapshot backup could not be
verified successfully. Explanation: The profile section for server server_name
is not correct. The actual error is following this
System action:
message.
User response: Check the logs for further information.
System action:
If the problem cannot be resolved contact your IBM
support personnel. User response: Adjust the profile and correct the error
following this message.
FMM8377E Function function does not support
multiple backup ids within a single FMM8382E The previous error(s) can be prevented
operation. by executing restore with negative list
set to 'no_check'.
Explanation: TSM for ACS was requested to perform
a volume function operation simultaneously for a set of Explanation: An error occurred while inspecting file
objects that were backed up with multiple volume systems for files that should be excluded during the

Chapter 2. FMM messages 133

FMM8383E • FMM8388W

backup/restore operation. This error precedes the User response: Provide the application type when
current message. Note that the file system inspection invoking the wizard by using the options 'acsd –f
can be turned off by setting the parameter wizard –m <application type>'. Alternatively, you can
'NEGATIVE_LIST' to 'NO_CHECK'. use the database–specific version of the setup script
(setup_<database>.sh) to create a new profile and
System action:
configure TSM for ACS.
User response: Resolve the root cause for this problem
(previous error) or change the value of the parameter
FMM8386E Parameter parameter name requires a
'NEGATIVE_LIST' to 'NO_CHECK'. Depending on the
decimal value of 0 or greater.
application type, this can be accomplished by v (for
DB2 and native Oracle) editing the TSM ACS profile Explanation: The value specified for the named
and set the parameter 'NEGATIVE_LIST' to 'no_check' v parameter does not comply with the defined range of
(for SAP(R) for Oracle) editing the BR*Tools profile values.
*.sap and set the parameter 'util_vol_nlist' to 'no_check'
System action:
Note that changing 'NEGATIVE_LIST' to 'NO_CHECK'
implies that TSM for ACS would potentially backup all User response: Check the named profile keyword and
files residing on the requested file systems. This true make appropriate adjustments.
even if they were not explicitly requested and resided
on the requested file systems, and even if they were not
explicitly requested during the backup. At restore time FMM8387W The following extra files are found in
all of these objects would typically be restored. the directories to be backed up: 'filename'
Explanation: The extra files were not requested to be
FMM8383E BR–Tools are required to set the part of the backup. The files may be copied if they are
environment variable BI_RUN for located in a file system that is to be backed up in its
volume backups. entirety. If the files are in a file system that does not
participate in the backup they are not copied.
Explanation: This is a unique ID from a BR*Tools run
(normally it is the name of the BR*Tools log). If this System action:
variable is set then BACKINT recognizes that a call User response: To avoid generating this message, edit
from BR*Tools 7.10 or higher was triggered. the 'CLIENT' section of the profile. You can set the
System action: parameter 'NEGATIVE_LIST' to 'NO_CHECK'. Then,
IBM Tivoli Storage FlashCopy Manager backs up any
User response: Ensure that BR*Tools 7.10 or later is file that is stored in a file system participating in the
used and rerun the operation. backup. Alternatively, you can set the
'NEGATIVE_LIST' parameter to point to a file
('negative list') containing a list of all files and
FMM8384E Failed to determine the
directories that are allowed to be processed during the
APPLICATION_TYPE of the profile.
backup. Any directory that you add to the 'negative
Please invoke wizard with option –m
list' file is processed recursively. Note there can be only
<application type>.
one 'negative list' file for both backup and restore
Explanation: 'acsd –f wizard' was invoked to modify operations.
an existing profile, and the APPLICATION_TYPE could
To avoid false warnings for files in the nested file
not be identified by inspecting this profile. This is
systems that do not participate in the backup, add the
required in order to properly adjust the profile.
mount points of the nested file systems to the 'negative
System action: list' file.
User response: Provide the application type when To avoid false warnings for files or directories that are
invoking the wizard with options 'acsd –f wizard –m pointed to by symbolic links and that do not participate
<application type>'. The preferred method, however, is in the backup, add the file system mount points of
to call the setup script without options. these files to the 'negative list' file.
Note: FlashCopy Manager does not automatically
FMM8385E In order to create a new profile the include nested file systems and files pointed to by
wizard needs to be invoked with option symbolic links in the FlashCopy backup operation.
–m <application type>.
Explanation: 'acsd –f wizard' was invoked to create a FMM8388W Additional files to restore were
new profile. In this case it is required to specify the discovered on the file systems: 'file list'
application type with option –m.
Explanation: A FlashCopy restore operation is
System action: performed with the profile parameter NEGATIVE_LIST
set to WARN. This operation replaces complete file

134 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8389W • FMM8394E

systems with the content of the file systems at the time changing NEGATIVE_LIST to NO_CHECK implies that
of backup. Each file that currently resides on the file TSM for ACS would potentially backup all files
systems to be restored (but were not part of the residing on the requested file systems. This true even if
original backup) will be listed. they were not explicitly requested and resided on the
requested file systems, and even if they were not
System action: Processing continues.
explicitly requested during the backup. At restore time
User response: None. all of these objects would typically be restored.

FMM8389W The following volume groups / file FMM8391E 'bytes_requested' bytes were requested to
systems are currently not accessible: be read from the file 'filename' but only
volumegroups/filesystems 'bytes_read' bytes could be read.

Explanation: The listed volume groups or file systems Explanation: The specified number of bytes requested
are not accessible. TSM ACS tries to verify that only to be read from the specified filename could not be
database files reside in the volume groups or file read.
systems that will be restored. But it was encountered
System action: Processing ends.
that it was not possible to access the file systems (in the
volume groups) to verify the database files because the User response: Check if the file size is smaller than
file systems are not mounted or the volume groups are the number of requestd bytes.
not imported, or both. This warning message is
followed by message FMM9390E which gives more
FMM8392E An error occured while restoring the file
information.
'filename'
System action:
Explanation: The restore operation failed for the
User response: This is just a warning message. Follow identified file. The restore process continues with the
the instructions of the user response of FMM8390E. other files.
System action: Processing continues.
FMM8390E Failed to validate that only database
User response: A restore failure occurs for different
files will be overwritten during restore,
reasons. Please check for previous error messages that
because some of the database
provide more information about the reason.
filesystems are currently not accessible.
Please import volume groups and/or
mount all filesystems and restart the FMM8393E The keyword TARGET_SET requires a
restore. If you cannot mount the target set name as argument.
filesystems as a consequence of a
disaster or a failing previous restore Explanation: The keyword TARGET_SET specified
operation, this error can be prevented within the target set definition file needs to be followed
by executing restore with negative list by an argument defining the unique name of the target
set to 'no_check'. set.

Explanation: TSM ACS tries to verify that only System action: Please have a look into your target set
database files reside in the volume groups / file file (.fct) and correct the entry accordingly.
systems that will be restored. But it was encountered User response:
that it was not possible to access the file systems (in the
volume groups) to verify the database files because the
file systems are not mounted and/or the volume FMM8394E Error while parsing TARGET_SET target
groups are not imported. set name: Illegal number of arguments.

System action: Explanation: The keyword TARGET_SET specified

within the target set definition file needs to be followed
User response: There are two options to solve this by exactly one argument defining the unique name of
problem: 1. Import all volume groups and mount all the target set. No additional arguments are allowed.
file systems that contain database files. 2. If the first
option is not possible as a consequence of a disaster or System action:
a failing previous restore operation, the negative list User response: Please have a look into your target set
check cannot be performed at all and must be switched file (.fct) and correct the entry accordingly.
to 'no_check'. Depending on the application type, this
can be accomplished by v (for DB2 and native Oracle)
editing the TSM ACS profile and set the parameter
'NEGATIVE_LIST' to 'no_check' v (for SAP(R) for
Oracle) editing the BR*Tools profile *.sap and set the
parameter 'util_vol_nlist' to 'no_check' Note that

Chapter 2. FMM messages 135

FMM8395E • FMM8402E

FMM8395E Error while parsing TARGET_SET target FMM8398E Error while parsing statement 'parameter
set name in volumes file: A multi name' in profile. The statement 'from or
partition backup requires the use of the to' is required to be in the form hh:mm.
keyword PARTITION in the target set
Explanation: The optional conditions 'FROM' and 'TO'
section.
of the profile parameter 'parameter name' need to be
Explanation: On a partitioned DB2 environment, the followed by a time in the format 'hh:mm'.
TARGET_VOLUME entries within the target set
System action:
definition file need to be enclosed by nested
'PARTITION' sections to determine for which partition User response: Please check your profile and correct
this target volume(s) apply. the times accordingly.
System action:
FMM8399E The mode mode of parameter parameter is
User response: Modify your target set definition file
only supported for device_type .
accordingly. Example: >>> TARGET_SET SET_1 >>>
PARTITION NODE0000 TARGET_VOLUME 40913158 - Explanation: The requested mode mode is only
- TARGET_VOLUME 40A13158 - - <<< >>> supported for device_type.
PARTITION NODE0001 TARGET_VOLUME 40B13158 -
- TARGET_VOLUME 50913158 - - <<< <<< System action:
User response: Choose a supported mode..
FMM8396E Error while parsing TARGET_SET target
set name in volumes file: It is not FMM8400E Error while parsing statement 'device
allowed to specify a portion of a target class' in profile. The statement partition
set without keyword PARTITION, if number is required to be a number.
this keyword is used for other portitions
in the same target set definition. Explanation: The optional condition
'ON_PARTITIONN' of the profile parameter
Explanation: On a partitioned DB2 environment, the 'DEVICE_CLASS' needs to be followed by an integer
TARGET_VOLUME entries within the target set number.
definition file need to be enclosed by nested
'PARTITION' sections to determine for which partition System action:
this target volume(s) apply. As soon as embedded User response: Please check your profile and correct
PARTITION subsections are used this means that ALL the 'ON_PARTITIONN' entries accordingly.
TARGET_VOLUME entries need to be enclosed in
PARTITION subsections.
FMM8401E DEVICE_CLASS device class was
System action: encountered multiple times within a
User response: Correct your target set definition file single DEVICE_CLASS statement.
accordingly. Explanation: The parameter 'DEVICE_CLASS' of the
'CLIENT' section allows to enlist multiple device classes
FMM8397E Error while parsing TARGET_SET target which are then applied in a round robin process.
set name in volumes file: the parameter However, each enlisted device class must not occur
PARTITION requires exactly one multiple times within the same enumeration.
parameter. System action:
Explanation: On a partitioned DB2 environment, the User response: Please check your profile and correct
TARGET_VOLUME entries within the target set the 'DEVICE_CLASS' entries accordingly.
definition file need to be enclosed by nested
'PARTITION' sections. The keyword 'PARTITION'
needs to be followed by the unique name of the FMM8402E No DEVICE_CLASS found that can be
partition. used for the current operation.

System action: Explanation: The application of a 'DEVICE_CLASS'

entry within the 'CLIENT' section of the profile can be
User response: Check whether all PARTITION restricted by a number of optional conditions, e.g. by
subsections within your target set definition file have a time frame of DB2 partition number. If this error occurs
unqiue partition name and correct the entries if none of the DEVICE_CLASS entries within the profile
necessary. matches the conditions currently given (current time,
given partition, given weekday).
System action:

136 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8403E • FMM8411I

User response: Check the conditions specified for the

FMM8407E An illegal partition number has been
'DEVICE_CLASS' entries within your profile. It needs
specified for parameter candidate name.
to be ensured that exactly one entry matches any
imaginable condition at any time. Explanation: The parameter parameter expects integer
partition numbers as argument.
FMM8403E The keyword keyword was found System action:
multiple times without qualifier qualifier.
User response: Please check the parameter parameter
Explanation: If the parameter keyword is specified within your profile and correct it accordingly.
without additional qualifiers it is representing the
global default. This global default can be defined only
FMM8408E The parameter parameter is not allowed
once. All other entries of parameter keyword need to be
as a name for a target set.
restricted by additional conditions.
Explanation: One possible distinctness of the
System action:
parameter 'TARGET_SET' is to specify target set
User response: Please check your profile. The definitions via a naming convention instead of a target
parameter keyword must not occur multiple times set definition file (for SVC only). The argument
without additional conditions. parameter does not meet these naming conventions.
System action:
FMM8404E The following statement contains
User response: Please check the arguments of the
incompatible options statement.
parameter 'TARGET_SET' within your profile and
Explanation: The parameter statement within the correct them accordingly.
'CLIENT' section of the profile is followed by
additional options which are contradictory to each
FMM8409E The parameter TARGET_NAMING is
other.
required to contain the wildcards source
System action: and targetset.
User response: Please check the parameter statement Explanation: The parameter 'TARGET_NAMING'
within your profile. For example, it is not possible to needs to follow particular conventions including the
combine the options 'MANDATE' and 'TSM_ONLY'. wildcards source and targetset to be valid.
System action:
FMM8405E The following statement is missing
User response: Please check the arguments of the
mandatory options statement.
parameter 'TARGET_NAMING' within your profile and
Explanation: The parameter statement within the correct them accordingly.
'CLIENT' section of the profile must be followed by an
option defining the mode of how offline backups are
FMM8410I Invoking suspend script suspend script.
handled.
Explanation: The suspend script has been invoked.
System action:
This script suspends the application immediately before
User response: Please check the parameter statement the actual FlashCopy process is initiated.
within your profile. It needs to include either 'NO',
System action:
'YES', 'MANDATE', or 'TSM_ONLY' as an option.
User response: Watch for additional messages
regarding the success of the suspend operation.
FMM8406E There are two object type associated with
partition partition name.
FMM8411I Script returned with return code return
Explanation: The profile associates the same partition
code
with multiple objects of object type. The name of the
partition and of the object type are identified in this Explanation: A suspend or resume operation failed
message. and issued the corresponding error code.
System action: The operation fails. System action:
User response: Update the profile so that each User response: Please check for more information in
partition is listed as a member of only one object of the output that preceeds this message.
object type.

Chapter 2. FMM messages 137

FMM8412I • FMM8421I

requested files that are available.

FMM8412I Start resume script resume script.
User response: If you have provided the names of the
Explanation: The resume process has started.
files please check for wrong names in the input. If the
Applications which have been suspended immediately
restore was started by SAP BR*Tools the version of this
before the actual FlashCopy operation are resumed
file might have been deleted on the Tivoli Storage
after this process completes.
Manager server.
System action: Watch for additional messages
regarding the success of the resume operation.
FMM8418E The backup ID 'backup id' has not been
User response: found.
Explanation: The backup ID was not found in the
FMM8413I Continue script script to resume. backup repository. As a result, the requested backup
cannot be restored.
Explanation: The identified script is resuming the
operation. System action: Processing stops.
System action: User response: If you have provided backup ID please
check for wrong entries in the input. If the restore was
User response: Watch for successive messages
started by SAP BR*Tools this backup might have been
informing about the success of the resume operation.
deleted on the Tivoli Storage Manager server.

FMM8414E Error while parsing profile profile:

FMM8419E File 'file' was not found in the backup
Delimiter 'delimiter' missing.
identified with backup ID 'backup id'
Explanation: A syntax error has been detected within
Explanation: The specified file was not found in the
you profile.
backup and was removed from the list of files to be
System action: restored.

User response: Please check the syntax and format of System action:
your profile.
User response: None.

FMM8415E A size has been specified for the file

FMM8420E Full file-based backups into the
'file' in the infile, but the requested file
repository are not allowed when
is not a raw device.
'ALLOW_FULL_FILE_BACKUP' is set to
Explanation: A size was specified (in the infile) for the 'NO'.
stated file. However, the file does not refer to a raw
Explanation: If you want to use 'FlashcopyManager' to
device. A size specification is allowed for raw devices
perform a backup with options util_file or
only.
util_file_online, set the option
System action: ALLOW_FULL_FILE_BACKUP to YES in the profile.

User response: Verify that the correct entries are System action:
specified in the infile.
User response: Correct the setting for the parameter
within your profile. You can also change backup
FMM8416E The specified backup ID 'backup id' must options.
have 16 characters.
Explanation: The backup ID is expected to be exactly FMM8421I Modifying existing profile 'profile file' for
16 characters. application 'application type' ...

System action: Explanation: An existing profile was found by the

profile wizard and will be modified during subsequent
User response: Verify the given backup ID. If it configuration actions.
contains 16 characters, make sure that it does not
contain any special characters. System action:
User response: None.
FMM8417E File 'file' has not been found in any
backup.
Explanation: No backup version of the file to be
restored is available.
System action: Processing continues to restore other

138 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8422I • FMM8437I

FMM8422I Creating new profile 'profile file' for FMM8433E Wrong system mode: system mode
application 'application type' ... (supported: PS | BS | PSBS)
Explanation: No existing profile was found. The Explanation: The system mode specified in the profile
profile wizard will create a new profile. wizard is invalid. These three system modes are
supported: PS - the wizard creates a profile for the
System action:
Production System BS - the wizard creates a profile for
User response: None. the Backup System PSBS - the wizard creates profiles
for both the Production and the Backup System

FMM8424E Operation not allowed for this System action:

parameter.
User response: Issue the command again and specify
Explanation: An invalid value was entered for the a valid system mode. Supported system modes are PS,
current parameter. BS, PSBS.

System action:
FMM8435W Annotation file 'file' could not be loaded.
User response: Enter a valid value for this parameter.
View help for a parameter by entering a question mark Explanation: The annotation file is required by the
("?"). profile wizard for displaying more expressive prompts
and online help. However, if this file is missing the
wizard is still operational.
FMM8426I Saving profile 'profile' ...
System action:
Explanation: The profile wizard writes the profile to
the file system. User response: The annotation file is integral part of
the product. If it is missing this means your product
System action: installation is corrupt. Please perform a reinstallation. If
User response: None. the warning message still occures please contact your
support line.

FMM8428W No help available for this parameter

FMM8436W Problems occured on final validation of
Explanation: No help information is available for the profile. Incorrect parameters have been
current parameter. marked in the written profile. Please
System action: check.

User response: Check the product documentation for Explanation: Profile parameters for that a user-defined
help information about this parameter. value is obligatory have been skipped without
specifying a value.

FMM8431E Application Type 'application type' is not System action:

a valid type. User response: Please rerun the profile wizard for the
Explanation: An invalid application type was given profile and ensure you specify a valid value for
specified in the profile wizard command. each parameter marked with *input mandatory*.

System action:
FMM8437I Verifying password...
User response: Issue the command again using a valid
application type. Supported application types are DB2, Explanation: After a password has been entered the
SAP, ORACLE, SAP_ORACLE, GENERIC, and wizard is verifying it by performing a test connection
VMWARE. to the according entity.
System action:
FMM8432E Invalid function: function invalid User response: Wait for outcome of the verification. If
(supported: function supported) the verification is successfull the wizard proceeds with
Explanation: The function specified for the profile the next password or writes the password files. If the
wizard -f option is invalid. verification fails the user is asked whether he wants to
retry or ignore the issue.
System action:
User response: Issue the command again and specify
a valid function. The only supported function is
"password".

Chapter 2. FMM messages 139

FMM8439E • FMM8464W

FMM8439E Could not read password filename from FMM8446E The restore operation requires the
profile 'profile'. File does not exist. command line option -P <Partition
(Check options -p, -b) group> to be specified.
Explanation: If the filename for the password file is Explanation: For restore operations in DB2 DPF
not explicitly specified by the option '-b' the wizard environments where the profile parameter
tries to read this information from the profile. The PARTITION_GROUP is used, it is required to specify
profile being consulted is either the default profile the command line option -P <Partition group> on the
'profile' or the profile specified by option '-p'. If this restore command.
error occurs there is either no default profile available
System action:
or the profile specified by option '-p' does not exist.
User response: Issue the command again and specify
System action:
a valid partition group.
User response: Check options '-p' and '-b'.
FMM8448E Another device class already exists
FMM8440E 'number of disks' disks have been found under the given name 'name'. Please
for datastore 'datastore name'. Only one specify another name.
disk per datastore is supported for the
Explanation: DEVICE_CLASS sections must be named
following environments: IBM DS8000
unique. The specified name is already in use for
IBM NSeries NetApp.
another device class.
Explanation: The specified datastore cannot be backed
System action:
up by IBM Tivoli Storage FlashCopy Manager because
of environmental limitations. See error message for User response: Choose another device class name
more detail. which is not already in use by another device class
section.
System action: Processing ends.
User response: Reduce the number of disks of the
FMM8450E The entry in InFile is not a valid file or
datastores to include in the backup to one or use
directory: 'entry'.
consistency groups in case the IBM XIV® storage
system is used. Explanation: The files or directories specified in the
InFile have to exist prior the backup operation is
started.
FMM8441E Please specify either only backup id's or
only backup id's with files. System action: Processing ends.
Explanation: You specified some backup id's with files User response: Verify the reported invalid entry in the
and some backup id's without files. InFile and revise the entry accordingly.
System action:
FMM8464W The specified host name or IP address
User response: Please specify either only backup id's
'host' cannot be associated with a local
or only backup id's with files.
network interface on this system.
Explanation: The attempt to establish a listening
FMM8445E Invalid cloning mode: cloning mode
TCP/IP server socket failed for the given host/port
invalid (supported: cloning_only |
combination. The provided host name or address is
backup_cloning)
expected to resolve to a local network interface.
Explanation: The given cloning mode is invalid. These
System action:
two cloning modes are supported: cloning_only - for
pure cloning configurations backup_cloning - for User response: An attempt to bind a TCP/IP server
configuring a database instance for cloning and socket to the specified host on the specified port (or the
backup/restore default port if the port is not specified) was not
successful. This test is successfully only when the
System action:
specified host or IP address corresponds to a local
User response: Issue the command again and specify network interface.
a valid cloning mode.

140 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8465E • FMM8513W

User response: Check the IBM Tivoli Storage

FMM8465E The value value for parameter parameter
FlashCopy Manager requirements to ensure that you
is out of valid range (min - max).
use a supported storage device.
Explanation: The value specified for the named
parameter does not comply with the defined range of
FMM8507W The original data store cluster cannot be
values.
found: 'datastore cluster name'. The data
System action: store 'datastore name' is restored to the
root directory of data center 'data center
User response: Check the named profile keyword and
name'.
make appropriate adjustments.
Explanation: The named data store cannot be
associated to the specified data store cluster. The data
FMM8503E No ESX host that can be used for instant
store cluster that it was associated to during the backup
restore was found.
process is not available at restore time. In the
Explanation: No ESX host can be found. An ESX host intervening time between backup and restore, the data
is needed to add data stores and to register virtual store cluster was deleted, renamed, or moved.
machines as part of the instant restore operation.
System action: Processing continues.
System action: Processing ends.
User response: After the restore process is completed,
User response: Add an ESX host to your virtual the data store can be reassigned to the appropriate data
environment. store cluster.

FMM8504E The 'datastore name' data store cannot be FMM8511I The command is: command name
mounted on the following ESX hosts:
Explanation: This is an information message echoing
'ESX host list'. There are no other ESX
the command.
hosts to try.
System action:
Explanation: The specified data store cannot be
attached to any of the listed ESX hosts. The processing User response: None.
cannot continue.
System action: Processing ends. FMM8512I Return code is: return code
User response: Configure your storage and network Explanation: This message shows the return code of
so that the specified data store can be mounted on one the Backup Object Manager. Valid return codes: 0 The
of the specified ESX hosts. requested action was performed successfully. 1 The
requested action was performed successfully; however,
some warnings were issued. 2 or greater The requested
FMM8505E The 'data store name' data store is
action could not be performed due to errors. In this
mounted on the following disconnected
case, an error message should be logged, too.
ESX hosts: 'ESX host list'. The data store
cannot be unmounted when these ESX System action:
hosts are in the disconnected state.
User response: None if the return code is 0. If the
Explanation: The specified data stores are mounted at return code is greater than 0, analyze the error and/or
the specified ESX hosts. These ESX hosts are warning messages. Resolve errors before starting the
disconnected. Therefore the data stores cannot be action again.
unmounted and the instant restore operation cannot
proceed.
FMM8513W 'TDP_DIR' is not set. The temporary
System action: Processing ends. path will be used.
User response: Remove the specified ESX hosts Explanation: The environment variable 'TDP_DIR' is
completely from your vSphere environment or not set and therefore, the log will be written to the
reconnect them. system's temporary path instead.
System action:
FMM8506E The configured storage device cannot be
User response: Set the 'TDP_DIR' environment
used in a VMware NAS environments.
variable.
Explanation: The configured storage device cannot be
used in a VMware network-attached storage (NAS)
environment.
System action: Processing ends.

Chapter 2. FMM messages 141

FMM8514W • FMM8523E

FMM8514W 'TDP_DIR' is not set correctly. The FMM8518E Unable to stop db2.
temporary path will be used.
Explanation: A restore was started while the database
Explanation: The variable TDP_DIR is set but contains was still up and running.
an invalid path. All run logs will be written to the
System action: Operation will fail.
machines temporary directory instead.
User response: Stop the database and restart the
System action:
restore operation.
User response: Check and reset the environment
variable TDP_DIR.
FMM8519E Unsupported database / application
type.
FMM8515W Volume volume group is shared across
Explanation: The requested operation was
partitions. This might result in severe
implemented on an application that does not support
restrictions during the restore operation.
this operation.
Consult the manual for details.
System action: Operation will fail.
Explanation: The specified volume group contains
data from multiple partitions. As a consequence, User response: Consult the user manual on how to
individual database partitions cannot be restored. For perform the operation you requested.
DB2, this means that you cannot use the native DB2
restore and recovery commands. Instead, you must
restore your database using 'tsm4acs -f restore'. FMM8520E No command was specified.

System action: The operation continues. Explanation: backom was called without a command
line.
User response: No action is required for backup
operations. Restore operations need to be performed System action:
using 'tsm4acs -f restore' instead of using the native User response: Check the command syntax and
interface commands. correct the call.

FMM8516E The restore operation terminated FMM8521E Command option 'command option'
because more objects than requested requires an argument.
would have been restored.
Explanation: A command option requiring an
Explanation: Multiple partitions were residing on the argument was specified without an argument.
same volume group at backup time. A restore can only
be performed with 'tsm4acs -f restore'. Also, a partition System action: Check the command syntax and
group must be specified with this command. correct the call.

System action: The operation terminates. User response:

User response: Run the restore operation again using

'tsm4acs -f restore -P <partition group>'. FMM8522E Invalid command 'command'.
Explanation: backom was called with an invalid
FMM8517E Function 'name' cannot operate on command.
multiple partitions simultaneously. Run System action:
the operation again with a single
partition. User response: Check the command syntax and
correct the call.
Explanation: The operation started so that multiple
database partitions were used (for example tsm4acs
was started with option '-P <partition group> and the FMM8523E Error during action.
specified partition group was representing multiple Explanation: An error occurred while performing the
database partitions). This is not supported for the named action.
specified function.
System action:
System action: Operation will fail.
User response: Look for other error messages in order
User response: Run the operation again so that it uses to analyze the problem.
only one database partition.

142 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8524E • FMM8533E

FMM8524E An online restore of the Tablespace is FMM8529E Invalid log sequence number. Specify it
not allowed. in the format log sequence format.
Explanation: Either the database setup or the kind of Explanation: The information on the log sequence
backup prevents an online table space backup. number(s) does not comply with the expected format.
Accepted log sequence numbers are for example '123'
System action:
or 'S0000123.LOG'.
User response: If you need to do a table space restore
System action:
it must be done offline.
User response: Correct the log sequence number(s).
FMM8525E The DB2 instance name can consist of at
most characters characters. FMM8530E Profile 'file name' does not exist or cannot
be accessed.
Explanation: The name given for the DB2 instance
does not comply with the DB2 naming conventions. Explanation: Either an existing file could not be
opened, or a file could not be created.
System action:
System action:
User response: Correct the DB2 instance name.
User response: Check the attributes of the file and/or
its directory. For backup processing, read access is
FMM8526E The DB2 database alias can consist of at
required for the files to be backed up. For restore
most characters characters.
processing, write access is required for the target
Explanation: The name given for the DB2 alias does location of the files to be restored.
not comply with the DB2 naming conventions.
System action: FMM8531E Directory 'file path' does not exist or
cannot be accessed.
User response: Correct the DB2 alias name.
Explanation: A file path cannot be accessed.
FMM8527E Invalid node. Specify it in the format System action:
node format.
User response: Check the attributes of the file and/or
Explanation: The name given for the DB2 node does its directory. For backup processing, read access is
not comply with the DB2 naming conventions. Node required for the files to be backed up. For restore
numbers must be specified in the displayed format, for processing, write access is required for the target
example 'NODE0000' or '0000'. location of the files to be restored.
System action:
FMM8532E Invalid log chain number. Specify it in
User response: Correct the DB2 node number. the format log chain format.
Explanation: The information on the log chain
FMM8528E Invalid timestamp. Specify the format as number(s) does not comply with the expected format.
'yyyymmddhhmmss', wildcards '*' or '?' Accepted log chain number(s) are for example '123' or
are permitted. 'C0000123'.file path .
Explanation: Specify digits in the format System action:
'yyyymmddhhmmss' or mixed with wildcards '*' or '?'.
where: v yyyy is the year, specified as four digits, v mm User response: Correct the log chain number(s).
is the month, specified as two digits, with leading zero
for the months January to September, v dd is the day of
FMM8533E A timestamp range is not allowed for
the month, specified as two digits, with leading zero
command 'command'.
for days 1 to 9, v hh is the hour of the day, 00 to 23,
with leading zero for hours 0 to 9, v mm is the minutes Explanation: A timestamp range is not allowed for
of the hour, 00 to 59, with leading zero for minutes 0 to command restore database, restore tablespace, restore
9, v ss is the second of the minute, 00, to 59, with tablespace online and restore DB2 history file. Only a
leading zero for seconds 0 to 9. Any digits can be single timestamp argument can be used.
replaced by wildcards '*' or '?', where v * means any
System action:
number of any digits, v ? means exactly one digit of
any value. User response: Correct the timestamp command
option.
System action:
User response: Correct the timestamp.

Chapter 2. FMM messages 143

FMM8534E • FMM8544I

specified in the client section of the profile, but the

FMM8534E Command option 'command option' is
application is not a DB2 system running SAP.
missing.
System action: Operation will fail.
Explanation: A command was issued without
specifying a required command option. User response: You cannot use the parameter
PARTITION_GROUP in your environment. All database
System action: Check the command syntax and
partitions must reside on dedicated volume groups.
correct the call.
User response: Check the command syntax and
FMM8540I Using component_name at host name:port
correct the call.
Explanation: The component_name service named is
used for the current action.
FMM8535E Invalid output mode. Specify one of the
keywords keyword list. System action:
Explanation: Only the listed keyword values are User response: None.
allowed with the output mode command option –m.
System action: FMM8541I Using profile 'profile path'.
User response: Correct the output mode command Explanation: The profile named is used for the current
option. action.
System action:
FMM8536E Wildcard characters are not allowed for
command 'command'. User response: None.

Explanation: For the BackOM commands 'restore

database', 'restore tablespace', 'restore tablespace online' FMM8542E Profile 'profile path' cannot be read.
and 'restore DB2 history file' it's not allowed to specify Explanation: The Backup Object Manager tried to use
the wildcard characters '*' and '?' in a timestamp the profile named but the profile was not available or
command option. could not be read. The location of the profile is
System action: specified via command line as argument to option '–e'
or in environment variable 'XINT_PROFILE'.
User response: Correct the timestamp command
option. System action:
User response: Make sure that the profile is available
FMM8537E The path 'path' is not absolute. at the location specified in option '–e' on the command
line or in environment variable 'XINT_PROFILE'. Check
Explanation: A command line argument requires a the attributes of the profile and the corresponding
fully qualified path which was not given. directory and make sure that the file can be accessed.
System action:
FMM8543I Querying TSM for file(s) 'file list'.
User response: Specify the fully qualified path.
Explanation: The Backup Object Manager checks if the
files listed are available on the TSM server(s) specified
FMM8538E The Tablespace Definition Information
in the corresponding profile.
'file name' cannot be processed.
System action:
Explanation: The TDI file could not be parsed because
of errors. There are more specific parser error messages User response: None.
before this message occurs.
System action: FMM8544I Application agent is terminating.
User response: Check for and respond to preceding Explanation: An operation is entering the cleanup
error messages in the Backup Object Manager log. phase and application agents are disconnecting.
System action: No specific system behavior.
FMM8539E The parameter PARTITION_GROUP is
not allowed in the client section for User response: None.
non-SAP environments. The
DB2_WORKLOAD parameter must
specify SAP.
Explanation: The parameter PARTITION_GROUP was

144 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8545I • FMM8555E

User response: Specify an appropriate value for the

FMM8545I No image type image(s) found.
environment variable named, or remove the
Explanation: A request could not be satisfied because environment variable.
the files to be processed are not available on the TSM
server.
FMM8551E Not all data written to 'file path'.
System action:
Explanation: Restoring raw or DB2 log file data ended
User response: Check if the file(s) were specified before all data retrieved from TSM could be written to
correctly in the request. the file named. The file is incomplete. named.
System action:
FMM8546E Environment variable 'environment
User response: Make sure there is sufficient space for
variable' is not set or not set correctly.
the data to be restored.
Explanation: A required environment variable is not
set at all or has a value that is not allowed.
FMM8552E File 'file path' could not be closed.
System action:
Explanation: After restoring raw or DB2 log file data,
User response: Check the documentation for the the target file could not be closed.
appropriate values of the environment variable named
System action:
and set its value accordingly.
User response: Retry the action.
FMM8547E Nothing to restore.
FMM8553E The file 'filename' has not been found.
Explanation: A restore operation was started but no
This file is required for the device agent
data was found to restore. This typically occurs when
to function. Check your installation.
an invalid backup ID is used.
Explanation: One of the components that is required
System action: Operation will fail.
to be installed with the product is missing.
User response: Specify another backup to restore.
System action: Operation will fail.
User response: Install the product again.
FMM8548I Elapsed time: time value
Explanation: After restore and delete, the time elapsed
FMM8554E Unable to create directory for detailed
during the action is displayed.
logs: name of directory.
System action:
Explanation: The specified directory could not be
User response: None. created. Detailed log information for future operations
will not be available.
FMM8549E Unable to create file 'file name'. System action: The product continues to operate, but
detailed log information will not be written. This
Explanation: During restore, the file to be restored
reduces the capability to diagnose errors.
cannot be created in the target location.
User response: Create the specified directory
System action:
manually and start 'acsd' again.
User response: Check if there is sufficient space
available for the file to be restored. Check the attributes
FMM8555E Variable 'DB2DBDFT' or command
of the target directory; write access is required. If the
option 'alias' is required.
target file already exists, check that write access is
granted Explanation: The password command needs the
name/alias of the database, for which the Data
Protection for SAP configuration file has to be adapted.
FMM8550W Environment variable 'environment
variable' for output mode has wrong System action:
value. Using default.
User response: Either set the environment variable
Explanation: The default output mode can be DB2DBDFT or provide the command option 'alias' with
overridden by the named environment variable. the password command and try again.
Accepted values are "short", "normal", or "detailed".
The system default is "short" for actions on DB2 log
files, "normal" otherwise.
System action:

Chapter 2. FMM messages 145

FMM8556E • FMM8562E

password(s) for all partitions of the database.

FMM8556E Unable to get hostname.
Explanation: The machines hostname could not be
FMM8560E Partition 'partition number' not found in
determined.
the database configuration.
System action:
Explanation: The DB2 partition specified could not be
User response: Check the TCP/IP configuration of the found in the database configuration.
machine.
System action:
User response: Check the configuration of the DB2
FMM8557E The config file 'initfile name.bki' could
ESE(EEE) environment (db2nodes.cfg, environment
not be created.
variable DB2NODE) and try again.
Explanation: Data Protection for SAP tries to create
the configuration file named if it is not present at the
FMM8561W Database 'alias' not listed in the system
location specified by the Data Protection for SAP profile
database directory.
keyword CONFIG_FILE. However, the file cannot be
created. This may either be caused by an incorrect path Explanation: The database alias does not exist. Because
specified by keyword CONFIG_FILE, or the user may there is a dependency between the alias and the
not have the appropriate permissions for creating the settings for Data Protection for SAP there might be
file. problems during database backup or restore runs.
Nevertheless, the Data Protection for SAP configuration
System action:
file (initalias.utl) will be created and adapted.
User response: Make sure the path specified by
System action:
keyword CONFIG_FILE is correct and the permissions
are set appropriately. User response: Check if the alias specified does match
to an entry in the DB2 system database directory.
Further, check the argument for the Data Protection for
FMM8558I Setting TSM password for partition
SAP profile keyword CONFIG_FILE and if necessary
'partition number' on host 'host name'.
adapt it appropriately.
Explanation: The Data Protection for SAP TSM
password is set on the host named for the DB2
FMM8562E Target 'volume' is missing in the target
partition indicated.
set ('target set name') that has been
System action: specified for restore. Review the error
explanation for corrective actions.
User response: None.
Explanation: Prior to starting a restore, all target
volumes that contain backup data are checked to make
FMM8559W For partition 'partition number' switch to
sure they are still listed in the target set definition file.
host 'host name' and issue the command
The target set defintition file is specified in the profile
again.
with the VOLUMES_DIR or VOLUMES_FILE
Explanation: When verifying the TSM password, the parameter. This error might also occur if the backup
Data Protection for SAP configuration file is modified. was performed with the TARGET_NAMING parameter
If the Data Protection for SAP profile keyword specified.
CONFIG_FILE points to an NFS mounted (UNIX or
System action: The operation will fail.
Linux) or a shared (Windows) path accessible to all
hosts in a DB2 ESE (EEE) environment, for example the User response: Verify that all target volumes used for
instance home, all configuration files of the various the backup have not been used for other purposes.
partitions can be modified simultaneously. If, in Once you verify that the backup is still valid, set the
contrast, keyword CONFIG_FILE points to a local path, option RESTORE_FORCE to YES in the appropriate
only the configuration files of the local partitions can device section and run the operation again. This error
be modified. In this case, the password verification is now ignored for this operation. Alternatively you can
needs to be done from each host. The message indicates add the missing target volumes to the target set
the partitions whose associated configuration files are definition and run the restore operation again. Be
not accessible. In order to avoid this administrative aware that corrupt data might be restored if one of the
overhead, it is recommended to place the Data volumes within the target set was used for other
Protection for SAP configuration files in a file system purposes.
shared by all hosts hosting a partition of the database.
System action:
User response: Make sure to verify the TSM

146 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8563E • FMM8568I

FMM8563E The target name 'backup volume' could FMM8565E More than one DEVICE_CLASS
not be identified from source name statement is eligible for the current
'source volume' and target set 'target set' operation. This is not allowed.
using the current naming convention.
Explanation: Multiple DEVICE_CLASS statements are
Please review the error explanation for
specified in the CLIENT section. This is allowed only if
corrective actions.
each of those statements is restricted for use with
Explanation: You are attempting a restore operation different times and dates. For DB2, it is also possible to
with option TARGET_NAMING defined in the profile. restrict the use of a device class to a particular
Before the restore operation begins, all volumes that partition.
contain backup data are checked to make sure they are
System action: The operation fails.
still defined in the profile. If the naming convention
specified with option TARGET_NAMING changed after User response: Modify the USE_AT, FROM-TO, and
the backup was created, this checking action fails. ON_DBPARTITIONNUMS entries of the
DEVICE_CLASS statements in the profile so that at
System action: Operation will fail.
most, only one device class is used at a time.
User response: Verify that all target volumes used for
the backup have not been used for other purposes.
FMM8566E The specified DEVICE_CLASS
Once you verify that the backup is still valid, set the
statements are inconsistent. As a result,
option RESTORE_FORCE to YES in the appropriate
these pairs are ambiguous: pairs
device section and run the operation again. This error
is now ignored for this operation. Alternatively can Explanation: Multiple DEVICE_CLASS statements are
update the naming convention specified with option specified in the CLIENT section. This is allowed only if
TARGET_NAMING to its original form and run the each of those statements is restricted for use with
restore operatin again. Be aware that corrupt data different times and dates. For DB2, it is also possible to
might be restored if one of the volumes within the restrict the use of a device class to a particular
target set was used for other purposes. partition.
System action: The operation fails.
FMM8564E The backup selected for restore resides
on target set 'name'. Either this target set User response: Modify the USE_AT, FROM-TO, and
definition no longer exists in the profile ON_DBPARTITIONNUMS entries of the
or the manner in which the target sets DEVICE_CLASS statements in the profile so that at
were specified has changed. Please most, only one device class is used at a time.
consult the user manual for corrective
actions. FMM8567E A node configured in
Explanation: You have chosen to restore a backup PARTITION_GROUP is not present in
which resides on a target set that has been removed the db2nodes.cfg file or does not reside
from the target set definition prior to this restore on this host. To restore nodes that reside
operation. This occurs when you reuse the volumes on a different host you need to start the
associated with this target set for other purposes or by restore from this host directly.
accidentally changing the target set definition. Explanation: One of the specified nodes has not been
System action: The operation will fail found in the db2nodes.cfg file or does not reside on
this host.
User response: Verify that all target volumes (of the
specified target set) used for the backup have not been System action: Operation fails.
used for other purposes. Once you verify that the User response: Try the operation again with different
backup is still valid, set the option RESTORE_FORCE nodes specified on the command line or in the profile
to YES in the appropriate device section and run the or rerun the restore on the correct host. Also, check the
operation again. This error is now ignored for this settings in the db2nodes.cfg file.
operation. Alternatively, you can add the missing target
set to your target set definition file (when
TARGET_SETS is set to VOLUMES_FILE or FMM8568I All nodes from db2nodes.cfg will be
VOLUMES_DIR) or you can append the name of this restored.
target set to the list of target sets specified with the Explanation: All nodes that are specified in the
TARGET_SETS option. db2nodes.cfg file will be restored during this operation.
System action: No specific system behavior.
User response: None.

Chapter 2. FMM messages 147

FMM8569I • FMM8583E

FMM8569I Only some nodes specified in the FMM8575E In this command multiple passwords
db2nodes.cfg file will be restored were set for 'server'. Only one password
Additional restore operations might be can be set for each server.
required on other hosts.
Explanation: Each command can set a server
Explanation: Some nodes that are specified in the password only once.
db2nodes.cfg file will be restored during this operation.
System action: The password file is not updated.
System action: No specific system behavior.
User response: Check the command's list of
User response: None. server/password arguments for duplicates.

FMM8570E Unable to start db2. FMM8576E The profile section 'sectionname' does not
need a password.
Explanation: DB2 could not be started successfully.
Explanation: This profile section does not need a
System action: Operation fails.
password.
User response: Check the application logs and DB2
System action: The password file is not updated.
logs. Try this operation again when the cause of the
error is corrected. User response: Please check the arguments of your
command. In must not contain password definitions for
profile sections other than ORACLE, DB2STANDBY,
FMM8571E Unable to initialize db2.
and DEVICE_CLASS.
Explanation: The DB2 instance could not be
initialized.
FMM8577E The 'directory' file does not exist which
System action: Operation fails. is mandatory for the correct operation of
the related storage device adapter.
User response: Check the application logs and DB2
logs. Try this operation again when the cause of the Explanation: Storage device adapters based on the
error is corrected. generic device adapter framework are required to
provide a customparameters.cfg file. It is expected to be
bundled with the storage device adapter. If the file is
FMM8572I Output of db2inidb: output. missing this indicates a corrupted installation of the
Explanation: The db2inideb command output storage device adapter.
displayed. System action: Processing stops.
System action: No specific system behavior. User response: Ensure that the storage device adapter
User response: None. has been properly installed. If necessary, contact the
vendor of the storage device adapter.

FMM8573I The password file 'filename' has been

updated successfully. FMM8583E Multiple possible values for parameter
'INCREMENTAL_LEVEL' detected:
Explanation: The password file has been updated with ambigous statements
new or altered passwords.
Explanation: Multiple specifications of the parameter
System action: The password file is updated. 'INCREMENTAL_LEVEL' with overlapping time spans
User response: No action is required. have been detected in the profile.
System action: Processing stops.
FMM8574E Syntax error: syntaxerror User response: The parameter
Explanation: The syntax of this command is not valid. 'INCREMENTAL_LEVEL' can be specified multiple
times within the profile to use different values at
System action: The password file is not updated. different days of the week or different times during the
User response: Check the syntax of your command day. But these multiple definitions must not overlap.
including its arguments. The correct syntax is Correct the time specifications. Try the operation again.
documented in the User's Guide.

148 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8584I • FMM8610I

the absence of preceding error messages, contact IBM

FMM8584I Delete command completed successfully.
Support.
Explanation: The object(s) specified with the delete
command were successfully deleted from the TSM
FMM8596E The virtual machine 'vm name' with
server.
instance UUID 'source vm instance uuid'
System action: cannot be backed up because it is
distributed across multiple datastores.
User response: None.
Distributed virtual machines are not
supported for the following
FMM8585W Delete command completed successfully, environments: IBM DS8000 IBM
but had warning(s). NSeries NetApp.

Explanation: The object(s) specified with the delete Explanation: The specified virtual machine cannot be
command were deleted with warning(s) from the TSM backed up by IBM Tivoli Storage FlashCopy Manager
server. because of environmental limitations. See error message
for more detail.
System action:
System action: Processing ends.
User response: Check the Backup Object Manager log
file for further detailed messages and if required, do User response: Exclude the specified virtual machine
the requested interventions manually. from the backup or use consistency groups in case the
IBM XIV storage system is used.

FMM8586I Delete command was aborted.

FMM8601E The following device class sections are
Explanation: The delete command was aborted by the missing in the profile:
user. No object(s) were deleted from the TSM server.
Explanation: Some profile parameters refer to device
System action: class sections that are not specified in the profile.
User response: None. System action: The operation fails.
User response: Add the missing device class sections
FMM8587E Delete command failed due to an error. to the profile or adjust the specified profile parameters.
Explanation: The delete command failed during
execution. Not all objects were deleted from the TSM FMM8602E The parameter profile parameter is
server. referring to device class section 'device
System action: class' which does not exist in the profile.

User response: Check the Backup Object Manager log Explanation: The specified profile parameter is
file for further detailed messages and try to resolve the referring to a device class section that is not specified
error which led to the delete failure. Retry the action. If in the profile.
the error still exists, contact the IBM Support. System action: The operation fails.
User response: Add the missing device class section to
FMM8588E Delete command has not been started or the profile or adjust the specified profile parameter.
no delete result information is available.
Explanation: This message indicates that an operation FMM8603E Parameter illegal option is not a valid
did not complete successfully. Typically, some other parameter for keyword profile parameter.
error condition was detected before.
Explanation: One of the specified parameters is
System action: invalid.
User response: Contact the IBM Support. System action: The operation fails.
User response: Correct the invalid parameter in the
FMM8589E Query command failed due to an error. profile.
Explanation: The query command failed during
execution. Not all queried objects can be displayed. FMM8610I Restoring type ...
System action: Explanation: The restore of type has started.
User response: Check for and respond to preceding System action:
error messages in the Backup Object Manager log. In
User response: None.

Chapter 2. FMM messages 149

FMM8611I • FMM8623I

FMM8611I Do you want to overwrite the existing FMM8617I Restore command was aborted.
database (y/n)?
Explanation: The restore command was aborted by
Explanation: the user. No object(s) were restored from the TSM
server.
System action:
System action:
User response:
User response: None.
FMM8612I Continuing restore ...
FMM8618E Restore command failed due to an error.
Explanation: The database restore continues.
Explanation: The restore command failed during
System action:
execution. Not all objects were restored from the TSM
User response: None. server.
System action:
FMM8613E Terminating restore ...
User response: Check the Backup Object Manager log
Explanation: An error occurred, and the database file for further detailed messages and try to resolve the
restore terminates. error which led to the restore failure. Retry the action.
If the error still exists, contact the IBM Support.
System action:
User response: Check for and respond to preceding FMM8619E Restore command has not been started
error messages in the Backup Object Manager and the or no restore result information is
shared library run logs. Additional information may be available.
found in the DB2 diagnostic log (db2diag.log).
Explanation: This message indicates that an operation
did not complete successfully. Typically, some other
FMM8614E The virtual machines 'vm1' and 'vm2' error condition was detected before.
have the same UUID 'uuid'. UUID's need
to be unique within a backup run. System action:

Explanation: The two specified virtual machines have User response: Check for and respond to preceding
the same UUID. IBM Tivoli Storage FlashCopy error messages in the Backup Object Manager log.
Manager cannot process two virtual machines with the
same UUID.
FMM8621I Restoring file 'file name' ...
System action: Processing stops.
Explanation: The system started restoring the file
User response: Update the UUID of one of the virtual indicated.
machines.
System action:
User response: None.
FMM8615I Restore command completed
successfully.
FMM8622I Deleting type ...
Explanation: The object(s) specified with the restore
command were successfully restored from the TSM Explanation: The deletion of type has started.
server.
System action:
System action:
User response: None.
User response: None.
FMM8623I Deleting file 'file name' ...
FMM8616W Restore command completed
Explanation: The system started deleting the file
successfully with warnings.
indicated.
Explanation: The object(s) specified with the restore
System action:
command were restored with warning(s) from the TSM
server. User response: None.
System action:
User response: Check the Backup Object Manager log
file for further detailed messages and if required, do
the requested interventions manually.

150 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8626W • FMM8638I

System action:
FMM8626W The Tablespace Definition Information
'file name' could not be deleted. User response: Check the warning messages and take
corrective actions if necessary.
Explanation: The system tried to remove the TDI
image from TSM, but did not succeed.
FMM8633E The configured VCenter server is the
System action:
'found API version' version, which is not
User response: Try to remove the image manually supported by IBM Tivoli Storage
using the Backup Object Manager raw delete facility. FlashCopy Manager.
Explanation: The configured vCenter server has an
FMM8628E Found VM with name 'vmname' in unsupported API version.
datastore 'dsurl' but not in the backup or
System action: Processing ends;
in the infile.
User response: Use another vCenter server that has a
Explanation: All VMs included in the Datastore to
supported API version or upgrade this vCenter server
restore have to be part of either the VMs included in
to a supported API version.
the backup or the vms in the exclude list in the infile.
System action:
FMM8634E Backup command failed due to an error.
User response: Add the VM to the exclude list of the
Explanation: No backup was made due to previous
infile
errors.
System action:
FMM8629E The 'variable name' environment variable
is not set. User response: Check for and respond to preceding
error messages in the Backup Object Manager log.
Explanation: The specified environment variable is not
set, processing cannot continue for the requested
operation. FMM8635E The command option 'option' must be a
floating point number.
System action: Processing ends.
Explanation: An invalid argument was specified for
User response: Ensure that when you run the product
command option option.
that you use the correct user ID so that the
environment variable is set. System action:
User response: Correct the command syntax.
FMM8630E The command option 'option' must be a
number.
FMM8636E The command option 'option' must be
Explanation: An invalid argument was specified for one of values.
command option option.
Explanation: An invalid argument was specified for
System action: command option option.
User response: Correct the command syntax. System action:
User response: Correct the command syntax.
FMM8631I Backup command completed
successfully.
FMM8637I Type state backup of 'alias' started ...
Explanation: The backup operation completed
successfully; the backup image can be used for Explanation: A backup operation of database alias of
restoring. In the case of a full database backup, the TDI type type has started.
image was generated and stored to TSM, too. System action:
System action: User response: None.
User response: None.
FMM8638I Type state backup of tablespace(s)
FMM8632W Backup command completed tablespace#1,...,tablespace#n of 'alias' started
successfully with warnings. ...

Explanation: The backup operation completed Explanation: A backup operation of table space(s)
successfully; the backup image can be used for tablespace#1 ... tablespace#n of database alias of type type
restoring. However, some problems occurred. was started.

Chapter 2. FMM messages 151

FMM8639I • FMM8651W

System action: Processing continues.

FMM8648I number of files in this run file(s) were
User response: None. stored successfully in this run on the
'hostname' node. A total number of stored
number of files totally files out of total
FMM8639I Including log files in backup image ... number of files files are stored in the data
Explanation: The DB2 log files are stored as part of backup that is identified by the external
the backup image. 'backup id' backup ID.

System action: Explanation: This is a progress message.

User response: None. System action: Processing continues.

User response: N/A
FMM8640I Using number buffers with a size of size
... FMM8649E The automatic deletion of backups is
Explanation: For backup or restore operations, the not supported. Change the value of the
indicated number of buffers of the size displayed are parameter name parameter to 0.
used. Explanation: The automatic deletion of backups is not
System action: supported.

User response: None. System action: Processing ends.

User response: Ensure that the value of the specified
FMM8641I Using number session(s) ... parameter is set to 0. As a consequence, backups are
not automatically deleted.
Explanation: For backup or restore operations, the
indicated number of TSM sessions is used.
FMM8650E To restore from all found_copies detected
System action: redo log copies, required_sessions sessions
User response: None. must be opened. But currently only
configured_sessions are allowed.

FMM8642I Using a degree of parallelism of number Explanation: For the object that should be restored
... overall found_copies copies have been found on the
Tivoli Storage Manager server. To allow transparent
Explanation: For backup or restore operations, the failover to other copies in case of errors Data Protection
degree of parallelism is displayed. for SAP must be able to open required_sessions sessions.
System action: But the current configuration allows to open only
configured_sessions sessions.
User response: None.
System action: Processing ends.

FMM8643I Using vendor library at 'lib path' ... User response: Check the profile parameter
MAX_RESTORE_SESSIONS or if not set check the
Explanation: For backup or restore operations, the value of parameter MAX_SESSIONS. Increase the value
named vendor library is used. to be at least as large as found_copies. Ensure the overall
number of sessions that are configured over all server
System action:
stanzas in the Data Protection for SAP profile is at least
User response: None. as large as found_copies.

FMM8644W Offline backups cannot include log FMM8651W Your version of DB2 does not support
files. The option –L is being ignored. including log files. The option –L is
being ignored.
Explanation: An offline backup operation was started,
requesting the DB2 log files to be included. This is not Explanation: A backup was started, requesting the
possible with an offline backup. The backup is done DB2 log files to be included, but your version of DB2
without including DB2 log files. does not support this feature. For including DB2 log
files in the backup image, DB2 V.8.2 or later is required.
System action:
System action:
User response: Make sure to backup DB2 log files
separately. User response: Make sure to backup DB2 log files
separately.

152 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8652I • FMM8662W

partition 0 will be used by DB2 and by Backup Object

FMM8652I DB2 version 'version' with number bits
Manager.
detected.
System action:
Explanation: The indicated DB2 version was detected
by Backup Object Manager. User response: If your database is not partitioned do
not specify the partition number for further actions.
System action:
User response: None.
FMM8658E Number is not a partition number of the
database or does not denote a partition
FMM8653I Using autonomic buffer size and on this host.
number of buffers ...
Explanation: The partition number specified does not
Explanation: The buffer size and the number of denote a valid database partition or is not the partition
buffers used for backup or restore is automatically located on the system where Backup Object Manager is
determined by DB2. called. Backup Object Manager can only operate on
partitions residing on the same host.
System action:
System action:
User response: None.
User response: Either change number to a partition
number of a local partition, or start Backup Object
FMM8654I Using an autonomic buffer size with
Manager from the same host where the partition
number buffers ...
resides.
Explanation: The buffer size used for backup and
restore is automatically determined by DB2. The
FMM8659I Creating tablespace definition
number of buffers to be used was specified in the call
information ...
to the Backup Object Manager.
Explanation: The table space definition information
System action:
(TDI) is being created in memory.
User response: None.
System action:
User response: None.
FMM8655I Using an autonomic number of buffers
with a size of size ...
FMM8660I Saving tablespace definition
Explanation: The number of buffers to be used for
information ...
backup and restore are determined by DB2. The buffer
size to be used was specified in the call to the Backup Explanation: The table space definition information
Object Manager. (TDI) is being stored on the TSM server.
System action: System action:
User response: None. User response: None.

FMM8656I Using an autonomic degree of FMM8661W Could not create Tablespace Definition
parallelism ... Information.
Explanation: The number of DB2 processes (UNIX or Explanation: The system could not collect the table
Linux) or threads (Windows) used for reading or space definition information. The backup was made
writing data from/to table space containers during without TDI. As a result, the backup can be used for
backup and restore is determined by DB2. restoring the system, but it cannot be used for restoring
to a different location.
System action:
System action:
User response: None.
User response: Ensure that your database is enabled
to accept CLI connections.
FMM8657W Number is not a valid partition number
for a non–partitioned database.
Assuming partition 0. FMM8662W Could not save Tablespace Definition
Information.
Explanation: The partition number specified in the
call to Backup Object Manager does not denote a valid Explanation: The system could not save the TDI on
partition of the database. Therefore, the default TSM. The backup was made without TDI. As a result,
the backup can be used for restoring the system, but it

Chapter 2. FMM messages 153

FMM8663W • FMM8671I

cannot be used for restoring to a different location. to a location identical to the location in the original
system.
System action:
System action:
User response: Check for and respond to preceding
error messages in the Backup Object Manager log. User response: Make sure that the table space
mentioned can be restored to the original location. This
requires that the user initiating the redirected restore
FMM8663W The Tablespace Definition Information
has the appropriate permissions for placing the table
contains device containers of a type
space container in this location and that the table space
unsupported by BackOM redirected
can be restored without overwriting other data. In
restore.
order to avoid this situation in the future, the
Explanation: A backup of a database using device administrator of the source system may want to
containers was requested. The backup was successful, it recreate the table space according to the database
can be used to restore the system, but it cannot be used characteristics Backup Object Manager expects.
for restoring to a different location. Restoring to a
different location is not supported with device
FMM8668I Tablespace Definition Information
containers.
created successfully.
System action:
Explanation: The metadata concerning the phyiscal
User response: None. database layout necessary for automatic redirected
restores driven by BackOM were created successfully.

FMM8664E Connecting to 'alias' using CLI failed. System action:

The return code was return code.
User response: None.
Explanation: The system tried to connect to the
database named via the CLI. The operation did not
FMM8669I Free space of device with ID id
succeed and returned the error code indicated.
containing the container storage path
System action: 'storage_path' are free_space.

User response: Ensure that your database is enabled Explanation: After assigning a container storage path
to accept CLI connections. to a dedicated device the remaining free space is
calculated and returned to the user.

FMM8665I The backup timestamp is: timestamp System action:

Explanation: The DB2 backup finished successfully User response: None.

with the timestamp timestamp.
System action: FMM8670I Remaining free space of device with ID
'id' after assigning container
User response: None. 'container_name' of size size are free_space.
Explanation: After assigning or creating a tablespace
FMM8666I Redirecting container of tablespace table container on a dedicated device the remaining free
space with ID id. space is calculated and returned to the user.
Explanation: The named table space is restored to the System action:
location requested.
User response: None.
System action:
User response: None. FMM8671I Using automatic storage path(s)
storage_path.
FMM8667W Tablespace tablespace with ID id was not Explanation: A dedicated automatic storage path will
redirected because its container on be used.
source system SID is not located in a
path starting with 'path'. System action:
Explanation: The named table space of type SMS was User response: None.
not redirected because the definition of the table space
container in the source system does not match the
database characteristics that Backup Object Manager
expects and that are cited in the message. Therefore,
Backup Object Manager tries to restore the table space

154 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8672I • FMM8693E

User response: Ensure that the datastore is removed

FMM8672I Redefining container path(s) of
from the ESX host before you run the instant restore
automatic storage tablespace tablespace
operation.
with ID id.
Explanation: The path(s) an automatic storage
FMM8690E Free space check for container 'path'
tablespace uses as a starting point for the container(s)
failed. Only free bytes free space left on
will be redefined.
device with ID 'id' but required bytes
System action: required.
User response: None. Explanation: The system requires a table space
container of the size indicated at the path named, but
there is not sufficient free space available to create it.
FMM8673E The Datastore name 'dsname' is not
unique within one Backup. System action:
Explanation: The backup contains more then one User response: Try to make available the free space
Datastore with the same name required, for example by 1. Removing some files on the
volume or file system the container is to reside on. 2.
System action: Processing stops.
Increasing the size of the file system the container is to
User response: replace the Datastore name with reside on. 3. Shrinking the size of the container
Datastore URL in the infile requested so that it fits in the free space. Note: Backup
Object Manager assumes that a small part (0.05%) of
the free space will be required by the operating system
FMM8674E A syntax error was detected in the for administrative use. As a consequence, only 99.95%
filename file: token of the free space on the volume or file system is
Explanation: A syntax error was detected in the actually available.
specified file. This storage device adapter file cannot be
modified. If this file was not accidentally edited, this FMM8691E The password file 'file name' cannot be
error indicates that there is a version conflict between read.
IBM Tivoli Storage FlashCopy Manager and the storage
adapter in use. Explanation: The IBM Tivoli Storage FlashCopy
Manager password file is unusable.
System action: Processing stops.
System action: The operation exits without
User response: Verify that the specified file is not completing.
corrupted or modified. Also, verify that the storage
device adapter file is compatible with the version of User response: Check the file permission. If the file
IBM Tivoli Storage FlashCopy Manager that is installed. has been changed on the production system, make sure
the file has been copied to backup or clone systems. If
the problem persists, recreate the password file by
FMM8675E The default value for the parameter_name entering the command 'fcmcli –f password' on the
parameter in the filename file is missing. production system and copy it to backup or clone
Explanation: A default value is mandatory for the systems.
specified parameter in the specified file. This storage
device adapter file cannot be modified. If this file was FMM8692E The requested data could not be
not accidentally edited, this error indicates that there is retrieved.
a version conflict between IBM Tivoli Storage
FlashCopy Manager and the storage adapter in use. Explanation: The TDI data of a backup image could
not be retrieved and displayed.
System action: Processing stops.
System action:
User response: Verify that the specified file is not
corrupted or modified. Also, verify that the storage User response: Look for and respond to preceding
device adapter file is compatible with the version of error messages.
IBM Tivoli Storage FlashCopy Manager that is installed.
FMM8693E More than one Tablespace Definition
FMM8676E The 'datastore name' datastore already Information file matches your query.
exists on the datacenter.
Explanation: More than one TDI file matching the
Explanation: The datastore name is already defined on search criteria was found on TSM.
the ESX host and is unavailable.
System action:
System action: Processing ends.
User response: Specify additional BackOM command

Chapter 2. FMM messages 155

FMM8700E • FMM8710W

options to restrict the result set.

FMM8706E The container at 'path' is inappropriate
for tablespace tablespace.
FMM8700E Internal parser error in Tablespace
Explanation: The container at the location indicated
Definition Information parser.
cannot be added to the table space named because of
Explanation: An unexpected error occurred in the TDI incompatible properties.
parser.
System action:
System action:
User response: Check the properties of the container
User response: Contact IBM Support. and the table space. Ensure that the IDs of the
containers are unique for the table space named.

FMM8701E This parser cannot process Tablespace

Definition Information version version. FMM8707E Missing statement keyword in block block
name near line line number.
Explanation: The current version of Backup Object
Manager is not compatible with the version the TDI Explanation: A keyword is missing in the named
image was created with. As a consequence, the TDI block ending at the line given.
data cannot be processed.
System action:
System action:
User response: Insert the required statement in the
User response: Check the release notes for the block.
appropriate migration procedure.
FMM8708E The [TDI] header block must be the
FMM8702E Too many errors. Bailing out. first block.

Explanation: The TDI parser encountered a number of Explanation: The TDI image does not start with the
errors. Restoring is stopped. required header ([TDI] block). Only comments or
whitespace are allowed before this block.
System action:
System action:
User response: Check for and respond to preceding
error messages in the Backup Object Manager log. User response: Ensure that the [TDI] block is the first
block in the TDI image.
FMM8703E Out of memory.
FMM8709E The required block block name is
Explanation: The TDI parser encountered a token that missing.
cannot be read into the main memory. The TDI image
cannot be processed, and restoring is stopped. Explanation: The named block is missing in your TDI
image.
System action:
System action:
User response: Contact IBM Support.
User response: Insert the missing block using valid
values.
FMM8704E Error while reading input file.
Explanation: The TDI parser tried to read more data FMM8710W Duplicate block block name ignored at
from disk or from TSM, but did not succeed. line line number.
System action: Explanation: At the line indicated, a block begins
User response: Ensure that the TDI image to be whose name was encountered before. The system
processed exists at the expected location and that the ignores the duplicate block; it uses the data from the
system has sufficient privileges to read it. first occurrence of duplicate blocks.
System action:
FMM8705E Error in line line number. User response: Make sure that block names are
Explanation: The TDI parser encountered a syntax unique within a TDI image.
error in the line indicated. As a consequence, the TDI
image cannot be analyzed.
System action:
User response: Respond to the error message and
correct your TDI image.

156 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8711W • FMM8737E

FMM8711W Duplicate statement keyword ignored in FMM8731I Normalizing tablespace containers ...
line line number.
Explanation: All containers of a table space will be of
Explanation: At the line indicated, a duplicate the same size after redefinition.
statement was encountered within a block. The system
System action:
ignores the duplicate statement.
User response: None.
System action:
User response: Make sure to not specify duplicate
FMM8732E The Tablespace Definition Information
statements within a block.
used with the redirected restore
operation contains an invalid database
FMM8715E Failed to create directory 'path'. Reason: alias.
reason
Explanation: There is an invalid database alias
Explanation: The path indicated could not be created. specified in the alias statement of the TDI image.
System action: The operation stops. The operation System action:
cannot continue until the error is resolved.
User response: Provide a valid alias.
User response: Check the properties of the path
indicated and make sure that its properties and the
FMM8733E The Tablespace Definition Information
properties of the parent directory are set accordingly.
used with the redirected restore
operation contains an invalid instance
FMM8727E No instance found managing database name.
'database name'.
Explanation: There is an invalid database instance
Explanation: The DB2 instance, which manages the specified in the <instance> statement of the TDI image.
named database 'image_name' could not be detected.
System action:
System action: Processing ends.
User response: Provide a valid instance name.
User response: Contact your IBM support personnel.
FMM8734E The Tablespace Definition Information
FMM8728E Could not attach to instance 'instance'. used with the redirected restore
operation contains an invalid partition
Explanation: BackOM was not able to attach to the
number.
instance instance.
Explanation: There is an invalid partition number
System action:
specified in the <Node> statement of the TDI image.
User response: First, check the system environment
System action:
for possible instance candidates. Try the action again by
additionally specifying the BackOM command option User response: Provide a valid partition number.
'–i <instance name>'.
FMM8736E Tablespace tablespace must have at least
FMM8729I Checking system resources ... one container.
Explanation: Prior to starting the redirected restore by Explanation: The TDI image defines the table space
BackOM the existing system resources, e.g. free space named without containers.
of a file system will be checked.
System action:
System action:
User response: Ensure that there is at least one
User response: None. container associated with every table space.

FMM8730I Scaling tablespace containers to number FMM8737E Tablespace tablespace has containers with
percent ... the combined storage too small.
Explanation: All table space containers will be Explanation: The number of used pages of the table
increased by the percentage indicated during the table space named exceeds the combined size of its table
space container redefinition step. space containers defined in the TDI image.
System action: System action:
User response: None. User response: Ensure that every table space has

Chapter 2. FMM messages 157

FMM8738E • FMM8747E

containers of a combined size that is sufficient to hold

FMM8743I Local Tablespace Definition Information
the used pages of the table space.
check returned return code.
Explanation: The TDI with the target database table
FMM8738E The container at path has a page size
space definition was checked. If the return code given
that is incompatible with its tablespace.
does not equal 0 errors occurred.
Explanation: The container indicated does not have
System action:
the same page size as its table space according to the
definitions in the TDI image. User response: In the case of a non–zero return code,
contact IBM Support.
System action:
User response: Contact IBM Support.
FMM8744I Tablespace Definition Information
replacement check returned return code.
FMM8739E The type of the container at path is
Explanation: The system checked whether the table
incompatible with its tablespace.
space definitions of the target TDI can replace the
Explanation: The container indicated cannot be used definitions of the source TDI. If the return code given
with its associated table space according to the does not equal 0 the table space definitions of the
definitions in the TDI image. SMS table spaces can only target TDI are not valid.
have path containers, and DMS table spaces must have
System action:
file or device containers.
User response: In the case of a non–zero return code,
System action:
contact IBM Support.
User response: Ensure that the appropriate types of
containers are used with each table space.
FMM8745E The Tablespace Definition Information
is invalid.
FMM8740E The path path of a container must not be
Explanation: The TDI with the target table space
relative.
definitions is not valid. Restoring to a different location
Explanation: In the TDI image, the named path is stopped.
defining a container does not seem to be a fully
System action:
qualified path.
User response: Check the Backup Object Manager log
System action:
for the return code of the validation. Check for and
User response: Ensure that all paths in your TDI are respond to preceding error messages in the Backup
fully qualified. Object Manager log.

FMM8741E The container at path would overwrite FMM8746I The Tablespace Definition Information
existing files or directories. is valid.

Explanation: The TDI image contains the definition of Explanation: The TDI with the target table space
the container indicated whose location is already in definition is valid. Processing continues.
use. This is only allowed when restoring to the source
System action:
database. Restoring to a different location is stopped.
User response: None.
System action: Ensure that all path containers defined
in the TDI image point to non–existing paths and all
file containers point to non–existing files. FMM8747E Not all tablespaces of the original
database are contained in the Tablespace
User response:
Definition Information.
Explanation: At least one table space of the original
FMM8742E The container at path is a device
database is missing in the TDI definitions of the target
container which is not supported.
database. However, a new location must be given for
Explanation: In the TDI image, a device container is all table spaces of the original database. Therefore,
defined. However, device containers are not supported restoring to a different location is stopped.
by Backup Object Manager.
System action:
System action:
User response: Provide the information on the
User response: Do not use device containers. missing table spaces and their containers.

158 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8748E • FMM8758E

System action:
FMM8748E The Tablespace Definition Information
does not define enough storage to hold User response: Do not use the Backup Object
all the data of the original database. Manager's redirected restore facility for device
containers.
Explanation: The target TDI has at least one table
space whose containers are too small to hold the data
of the source database. FMM8753E A container cannot be created at path.
System action: Explanation: Either the location where the table space
container is to be created does not exist, or the
User response: Increase the container size or add
permissions of the user are not sufficient.
more containers to the table spaces.
System action:
FMM8749E The page size of a tablespace in the User response: Check the location and the
Tablespace Definition Information does permissions.
not match the one of the original
database.
FMM8755I Getting reference Tablespace Definition
Explanation: The target TDI contains at least one table Information from TSM ...
space with a matching ID in the source TDI, but their
page sizes do not match. Explanation: Retrieving the appropriate TDI to be
used by internal checking routines from the TSM
System action: server.
User response: Ensure that table spaces have the same System action:
page sizes in both the source and the target TDI.
User response: None.

FMM8750E The number of used pages of a

tablespace in the Tablespace Definition FMM8756W Could not get reference Tablespace
Information does not match the one of Definition Information from TSM. No
the original database. input validation is done.

Explanation: The target TDI contains at least one table Explanation: The system could not find a TDI image
space with a matching ID in the source TDI, but the matching the database backup to be restored on TSM.
number of used pages of the target table space does not The restore action will be continued, but the input data
match the number of used pages in the original cannot be validated before the restore starts.
database. System action:
System action: User response: None.
User response: Ensure that the number of used pages
of a table space is the same in both the source and the FMM8757I Performing redirected restore from
target TDI. 'source alias' to 'target alias' ...
Explanation: Redirected restore of source alias to target
FMM8751E The tablespace type in the Tablespace alias is starting.
Definition Information does not match
the one of the original database. System action:

Explanation: The target TDI holds at least one table User response: None.
space with a matching ID in the source TDI, but the
table space types are different. FMM8758E The Tablespace Definition Information
System action: does not contain data for tablespace
'tablespace'.
User response: Ensure that the type of a table space is
the same in both the source and the target TDI. Explanation: A definition of the table space named is
expected to be provided in the TDI, but could not be
found.
FMM8752E BackOM does not support redirected
restore with device containers. System action:

Explanation: The target TDI contains at least one User response: Ensure that all table spaces of the
definition of a device container. However, device source database are also defined in the target TDI.
containers are not supported by Backup Object
Manager's redirected restore function.

Chapter 2. FMM messages 159

FMM8759E • FMM8769E

FMM8759E Redirecting of at least one container FMM8765I Checking redirected restore from 'source
failed. alias' to 'target alias' ...
Explanation: The system tried to create the containers Explanation: The system is testing whether the
for a table space, but at least one of them could not be original database can be restored to the target location.
redirected to a different location. Usually, the location It checks whether v the file system where the table
of one of the table space containers is not allowed. A space containers are to be created has sufficient free
list of containers the system tries to create can be found space. (If specified, normalizing and scaling are also
in the Backup Object Manager log. One of them failed. considered.) v there are existing files and directories
identical to the containers defined for the target
System action:
database. This would indicate that a database of same
User response: Check for and respond to further error name and of same structure already exists, and data
messages in the Backup Object Manager log. could be overridden. v the structures of the source and
target databases (table space types, page sizes, extend
sizes) allow for a redirected restore.
FMM8760E Directory 'directory' could not be created.
System action:
Explanation: The system tried to create the directories
to place the containers in, but at least one failed. User response: None.

System action:
FMM8766I Check successful. Redirected restore
User response: Ensure that the system has sufficient possible with these settings.
privileges to create the directories at the desired
locations. Explanation: The redirected restore test finished
successfully. Thus, the redirected restore operation can
be started with the options specified for the test run.
FMM8761E The container at path does not have the
minimum size of two extends. System action:
Explanation: A table space container to be created User response: None.
must have at least the size of two extends.
System action: FMM8767W Warnings occurred.

User response: Correct the size of the container to be Explanation: The redirected restore test detected one
created. or more minor conflicts. These conflicts may or may
not prevent a successful redirected restore operation.
Nevertheless, it is recommended to resolve them.
FMM8762I Set tablespace container with ID id and
name 'tablespace_container'. System action:

Explanation: Backup Object Manager redirects a table User response: Check for and respond to preceding
space container to the ID and name indicated. warning messages in the Backup Object Manager log.

System action:
FMM8768E Check failed. Redirected restore not
User response: None. possible with these settings.
Explanation: The redirected restore test detected one
FMM8763E The extent size of a tablespace in the or more major errors which will prevent a successful
Tablespace Definition Information does redirected restore with these settings.
not match the one of the original
database. System action:
Explanation: The extend sizes of corresponding table User response: Check for and respond to preceding
spaces defined in the source and target TDIs must be error messages in the Backup Object Manager log.
equal. However, for at least one table space different
extend sizes are defined in the source and target
FMM8769E Found multiple Tablespace Definition
databases.
Information matching the given
System action: timestamp. Additional search conditions
needed.
User response: Define matching extend sizes for
corresponding table spaces. Explanation: More than one TDI file for a database
backup image was found on the TSM server. In such a
scenario, the integrity of the metadata assigned to a
database backup images is violated and prevents an

160 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8770I • FMM8803I

automatic redirected restore driven by BackOM.

FMM8798E Due to errors, you cannot continue the
System action: operation.

User response: Contact your IBM support personnel. Explanation: You tried to start a restore operation
after redefining the containers interactively, but errors
were detected in the input data. The operation cannot
FMM8770I Getting Tablespace Definition continue.
Information used with the redirected
restore operation from TSM... System action:
Explanation: The system is retrieving the TDI image User response: Check all table spaces with '!!' error
from the TSM server. marks in the list and correct the definitions of their
containers. Then continue.
System action:
User response: None. FMM8799E A container must have a size of at least
twice the extent size (minimum size for
FMM8771E The Tablespace Definition Information this tablespace).
used with the redirected restore Explanation: The container size specified is too small.
operation could not be retrieved. The minimum size of a container is twice the extent
Explanation: The TDI image specified could not be size.
found. System action:
System action: User response: Correct the container size.
User response: Provide the correct location of the TDI
image. FMM8800I The command is: command
Explanation: Displays the command that was issued.
FMM8772E The selected database has a structure The following commands are possible: Backup, Restore,
that prevents automatic cloning. Archive/Retrieve.
Explanation: You tried to clone an SAP database using System action:
redirected restore, but the database does not have the
default directory structure of an SAP database. The User response: None.
cloning facility of Backup Object Manager redirected
restore cannot be used for this system.
FMM8801I Time: time ––– PID: PID_Number
System action:
Explanation: Displays the process id of the DB2
User response: You may use either the interactive or process which called the shared library.
the batch mode of Backup Object Manager redirected
System action:
restore.
User response: None.
FMM8773E The interactive modification of the
containers failed. FMM8802I Found number type image(s) on TSM
server.
Explanation: You tried to interactively change the
location of containers, but this operation failed. Explanation: For restore and delete operations Data
Protection for SAP queries TSM for backup images by
System action: Processing ends.
means of a timestamp and shows the number of found
User response: Contact IBM Support. images.
System action:
FMM8776E You are not allowed to delete this
User response: None.
container.
Explanation: You tried to delete the last container of a
FMM8803I The DB2 image size for this session is
table space. However, at least one container must be
about 'size'.
available to every table space.
Explanation: The estimated size of the data to be
System action:
backed up is displayed.
User response: Make sure that there is at least one
System action:
container defined for every table space.
User response: None.

Chapter 2. FMM messages 161

FMM8804W • FMM8817I

FMM8804W The recovery log could not be written. FMM8812I Committed TSM sessions of this backup
run will be deleted.
Explanation: After every backup or restore, Data
Protection for SAP writes a record into the recovery log Explanation: During a backup with multiple sessions,
file tdprlf.<SID>.node_name.log. It is located in the path an error occurred. The backup operation is stopped.
pointed to by environment variable TDP_DIR. TSM sessions already committed during this operation
are being deleted from the TSM server in order to
System action:
prevent them from being considered restorable.
User response: Check, if the permissions are set
System action:
correctly and if there is sufficient free space in your file
system. User response: None.

FMM8805I The restore was cancelled by the user. FMM8813E Error deleting committed TSM sessions.
Existing data not overwritten.
Explanation: One or more committed TSM sessions
Explanation: The existing database is still operational. could not be deleted during the postprocessing of the
failed backup run.
System action:
System action:
User response: None.
User response: Use the Backup Object Manager to
delete the file(s) manually.
FMM8806I product version.release.modification.level
(build_numberbeta) build_date
FMM8814I Inquired TSM with mask 'search mask'.
Explanation: Writes version information into the
product log file. Explanation: The string denoted is used to inquire
TSM for backup images.
System action:
System action:
User response: None.
User response: None.
FMM8807I Archive log file 'log number' of chain 'log
chain number'. FMM8815I Information for Log Manager:
DB2_instance DB2_database_name
Explanation: Writes information about the log file to
DB2_database_alias
be archived into the product log file.
log_and_log_chain_number partition
System action:
Explanation: The information listed is provided to the
User response: None. DB2 Log Manager.
System action:
FMM8808I Retrieve log file 'log number' of chain 'log
User response: None.
chain number'. Seeking for TSM image
'image'.
FMM8816I DB2 version 'version' detected.
Explanation: Writes information about the log file to
be retrieved into the product log file. Explanation: TSM for ERP is running on a system
where DB2 version version is set up.
System action:
System action:
User response: None.
User response: None.
FMM8810I Cleaning up resources of process
'PID_number'. FMM8817I No corresponding committed TSM
session(s) found. Nothing will be
Explanation: All resources used by the product will be
deleted.
released.
Explanation: The cleanup of a failed TSM for ERP
System action: Processing continues.
database backup could not find any partial TSM
User response: None. backup image of that run already stored on the TSM
server for deletion.
System action:
User response: None.

162 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8818W • FMM8833W

FMM8818W Invalid value specified for FMM8823W Configuration parameter

BACKOM_LOCATION. SRC_DB_ALIAS requires parameter
SRC_DB_INSTANCE and vice versa.
Explanation: The BackOM executable was not started
for collecting database metadata due to an invalid Explanation: To be able to recover a database after a
specification. redirected restore using the built–in DB2 rollforward
command, TSM for ERP needs both SRC_DB_ALIAS
System action:
and SRC_DB_INSTANCE.
User response: Check the value of the TSM for ERP
System action:
configuration parameter BACKOM_LOCATION. The
parameter can be found in the vendor environment file User response: Include both parameters
and must contain the fully qualified name of the SRC_DB_ALIAS and SRC_DB_INSTANCE in the TSM
BackOM executable. for ERP vendor environment file and retry the database
recovery.
FMM8819I The TSM objects matching with mask
'search mask' will be deleted. FMM8831E The properties of the virtual machine
'vm name' could not be fetched through
Explanation: The cleanup of a failed TSM for ERP
the vSphere API because they are not
database backup will delete any partial TSM backup
set.
image of that run already stored on the TSM server and
matching search mask . Explanation: The properties of the virtual machine
could not be fetched through the vSphere API because
System action:
they are not set on the corresponding object.
User response: None.
System action: Processing ends.
User response: Check if the according auxiliary ESX
FMM8820E No valid TSM session found.
host is in an operational state.
Explanation: A running TSM for ERP workflow could
not continue due to a missing TSM session.
FMM8832I Note: The GSKit installation is not
System action: removed from ${HOSTNAME} because
it might be in use by other IBM Tivoli
User response: Contact your IBM support personnel. Storage FlashCopy Manager instances. If
needed, the GSKit can be manually
FMM8821I Using option(s) 'options'. uninstalled. For more information, see
the Installation and User's Guide.
Explanation: The options string specifies vendor
options that DB2 provides to the TSM for ERP library Explanation: GSKit is remotely installed on the
as part of the calling function. These could be options backup or cloning system by using SSH. Multiple
directly provided as part of the database backup or instances of IBM Tivoli Storage FlashCopy Manager
restore command or options made persistent in the might exist on the remote system so GSKit is not
database configuration, here the parameters uninstalled to avoid breaking other instances of IBM
VENDOROPT, LOGARCHOPT1 or LOGARCHOPT2. Tivoli Storage FlashCopy Manager.

System action: System action: Processing continues. GSKit remains

installed on the backup or cloning system.
User response: None.
User response: GSKit can be manually uninstalled on
the backup or cloning systems if needed. The user
FMM8822I Configuration parameter(s): parameters guide provides details about the necessary steps.
Explanation: The list specifies a set of runtime
parameters that the TSM for ERP library is using for FMM8833W The environment variable
the calling workflow. 'SHLIB_PATH' does not include the path
System action: '/usr/lib' which is required for the
correct operation of GSKit. Ensure that
User response: None. the path is added to allow the correct
operation of IBM Tivoli Storage
FlashCopy Manager.
Explanation: The environment variable 'SHLIB_PATH'
must include the path '/usr/lib' to ensure that the
GSKit libraries are found.

Chapter 2. FMM messages 163

FMM8834E • FMM8842W

System action: Processing continues but IBM Tivoli

FMM8838I Starting synchronous delete operation.
Storage FlashCopy Manager might be non-operational.
Explanation: The delete process is started and the
User response: Add the path '/usr/lib to the
processing waits until the delete has finished.
environment variable 'SHLIB_PATH'.
System action: Processing waits until delete has
finished.
FMM8834E An earlier version of GSKit is running:
'version'. This version cannot be used for User response: No action is required.
Transport Layer Security (TLS) version
1.2.;
FMM8839I The delete operation has finished.
Explanation: In a DB2 application environment, IBM
Explanation: The delete process has finished and the
Tivoli Storage FlashCopy Manager application agent
processing will continue.
uses the GSKit libraries that are shipped with DB2. For
older versions of DB2 this GSKit version might be older System action: Processing will continue.
than the one that is shipped with IBM Tivoli Storage
FlashCopy Manager. Earlier versions of GSKit do not User response: No action is required.
support TLS version 1.2 and therefore TLS version 1.2
protocol cannot be enforced. FMM8840I The synchronous delete operation has
System action: IBM Tivoli Storage FlashCopy terminated. Normal processing
Manager cannot operate when you use this continues.
configuration. Explanation: The delete process has terminated with
User response: Either upgrade your DB2 installation error. The processing will continue. The delete process
to use a newer GSKit version, the minimum version is will be restarted later. The IBM Tivoli Storage
8.0.14.21 or set the ENFORCE_TLS12 profile parameter FlashCopy Manager repository may contain invald
to "NO". Run the setup script to configure this backup entries until the next delete process is
parameter. scheduled.
System action: Processing will continue.
FMM8835I Starting synchronous reconcile User response: No action is required.
operation.
Explanation: The reconciliation process is started and FMM8841W No IBM Tivoli Storage FlashCopy
the processing waits until the reconciliation has Manager offload daemon was running
finished. in the last minutes minutes. Make sure
System action: Processing waits until reconciliation that the IBM Tivoli Storage FlashCopy
has finished. Manager offload daemon process is
running.
User response: No action is required.
Explanation: The IBM Tivoli Storage FlashCopy
Manager offload daemon was not running on the IBM
FMM8836I The reconcile operation has finished. Tivoli Storage FlashCopy Manager host since the
specified time interval. This offload daemon process is
Explanation: The reconciliation process has finished
required if IBM Tivoli Storage FlashCopy Manager
and the processing will continue.
snapshot backups should be sent to Tivoli Storage
System action: Processing will continue. Manager.
User response: No action is required. System action: Processing will continue. But the
offloaded backup to Tivoli Storage Manager may not
start.
FMM8837I The synchronous reconcile operation has
terminated. Normal processing User response: Verify that the IBM Tivoli Storage
continues. FlashCopy Manager offload daemon process is running.
Restart this daemon process if it is not running.
Explanation: The reconciliation process has terminated
with error. The processing will continue. The
reconciliation process will be restarted later. The IBM FMM8842W The 'lunserial' Logical Unit Number
Tivoli Storage FlashCopy Manager repository may (LUN) was added to the 'dsName'
contain invald backup entries until the next datastore after the backup was
reconciliation process is scheduled. completed. This LUN will be detached
from the vSphere environment.
System action: Processing will continue.
Explanation: One or more LUNs was added to the
User response: No action is required.

164 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM8843E • FMM9009W

datastore after the backup operation was completed.

FMM9004E Location of the message catalog could
Tivoli Storage FlashCopy Manager detaches these
not be figured out.
LUNs from the ESX host to mount the datastore when
you perform an instant restore of this datastore. Explanation: Data Protection for SAP locates the
message catalog over the install directory. When Data
System action: Processing will continue.
Protection for SAP is exploited through a library like
User response: No action is required. DB2 or Oracle/RMAN, then the environment variable
XINT_NLS_CATALOG_PATH is mandatory.

FMM8843E The virtual machine could not be System action: Processing stops.
restored using 'target vm name' VM
User response: The environment variable
name. A VM with the same name
XINT_NLS_CATALOG_PATH may be required..
already exists in the datacenter.
Explanation: The specified virtual machine could not
FMM9005E A not supported by B
be restored because another virtual machine with the
same name already exists in the datacenter. Explanation: The installed version of product B does
not support product A. Most likely you need to
System action: Processing ends.
upgrade product B.
User response: Specify another virtual machine name
System action:
or delete the existing virtual machine in the vCenter.
User response: Contact the IBM Support.
FMM8899E Interface problem in function function:
Value 'value' of parameter 'parameter' is FMM9006E Internal error while reading
not supported with DB2 version 'version'. environment variable: variable
Explanation: An unknown action code during the Explanation: This is an internal error.
program execution was encountered.
System action:
System action:
User response: Contact IBM Support.
User response: Contact your IBM support personnel.
FMM9007W An error occurred while terminating the
FMM9001E Internal error: error application: the error
Explanation: The following internal error: error has Explanation: While terminating the application, an
been encountered. error occurred. This has no impact on the success of the
operation.
System action:
System action:
User response: Contact IBM Support.
User response: None.
FMM9002E Parameter 'all' is not supported.
FMM9008E This product requires at least version
Explanation: The provided parameter is not
number of product name to be installed.
supported. This error can be caused by nodes that are
specified without being separated by commas. Explanation: The version of the application product
name is not supported by this application. Most likely
System action: Processing ends.
application product name needs to be upgraded.
User response: Make sure the specified nodes are
System action:
separated by commas, then try the command again.
User response: Contact IBM Support.
FMM9003E Incompatible components installed:
component name one, component name two FMM9009W The following products are not
compatible: product name first (product
Explanation: The components mentioned in the
version first) and product name second
message text can not be used together. This may be the
(product version second).
result of an incomplete upgrade.
Explanation: This message is similar to FMM9008E.
System action:
But in this case it's not obvious which one of the
User response: Contact IBM Support. products needs to be upgraded.
System action:

Chapter 2. FMM messages 165

FMM9010E • FMM9199E

User response: Contact IBM Support.

FMM9015E Failed to locate functions in library:
library reason: reason
FMM9010E Could not determine installation
Explanation: One or more functions could not be
directory for program. Please restart the
found in the ACS library.
process using a fully qualified name.
System action:
Explanation: The name of the path where a given
program is located could not be determined. User response: Contact your IBM support personnel.
System action:
FMM9016E The Database needs to be mounted.
User response: Contact your IBM support personnel.
Explanation: The Databse needs to be mounted to be
able to perform the pre-installation Checker.
FMM9011E There was no response received within
number seconds; timeout is expired. You System action: Processing ends.
can increase the timeout by specifying
User response: Mount the database.
the profile parameter timeoutphase for the
current phase of the backup or restore
operation. FMM9198E While processing path path_name, an
error occurred. The following error
Explanation: The communication between two
information was received:
program components was suspended or stopped,
detailed_error_information
which can lead to a timeout.
Explanation: This message indicates that a problem
System action:
occurred while processing the following path:
User response: Increase the timeout by specifying the path_name. If you are protecting data for DB2
profile parameter TIMEOUT_<PHASE> for the current applications, this path contains one or more of the
phase of the backup or restore operation. If this does database files to be included in the operation. If you
not solve the probblem please contact your IBM are protecting data for Oracle databases or the Custom
support personnel. Application Agent, this path was provided in the in-file
specified with the flag "-I <infile_name>" in the
command.
FMM9012E One of the requested data containers is
already the subject of a restore. System action: The operation stops. The operation
cannot continue until the error is resolved.
Explanation: A restore of the same data has already
been requested. User response: To help resolve the problem the
detailed_error_information is available. After you resolve
System action: Processing stops.
the issue, enter the command again.
User response: Multiple restore operations are usually
prevented by the database system. If there are no
FMM9199E The following command returned with
multiple restore operations performed concurrently,
an error: command The return code from
then contact IBM support for this problem.
this command is return_code The
following command output was
FMM9013E Concurrent restore of objects being received: command_output Additional
backed up with multiple device agents support information: An exception was
is not supported. thrown at position: position(line).

Explanation: This special restore scenario is Explanation: This message indicates that the command
unsupported. returned with the error indicated by return_code. Any
additional command_output is provided.
System action:
System action: The operation stops. The operation
User response: Contact your IBM support personnel. cannot continue until the error is resolved.
User response: To help resolve the problem the
FMM9014E Failed to load library: library reason: command_output is available. After you resolve the
reason issue, enter the command again.
Explanation: The ACS library could not be loaded.
System action:
User response: Contact your IBM support personnel.

166 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM9200E • FMM9210E

FMM9200E Additional support information: An FMM9205E Additional support information: Unable

exception was thrown at position: to instantiate name at file(line).
position(line).
Explanation: This error message typically follows a
Explanation: This error message typically follows a previous error. If so this error message can be ignored.
previous error. If so this error message can be ignored. Otherwise contact IBM Support.
Otherwise contact IBM Support.
System action:
System action:
User response: Contact IBM Support.
User response: Contact IBM Support.
FMM9206E Additional support information: Unable
FMM9201E Additional support information: An to use actual when expecting expected at
exception was thrown at position: file(line).
position(line).
Explanation: This error message typically follows a
Explanation: This error message typically follows a previous error. If so this error message can be ignored.
previous error. If so this error message can be ignored. Otherwise contact IBM Support.
Otherwise contact IBM Support.
System action:
System action:
User response: Contact IBM Support.
User response: Contact IBM Support.
FMM9207E Additional support information: An
FMM9202E Additional support information: An exception was thrown at position:
exception was thrown at position: file(line).
position(line).
Explanation: This error message typically follows a
Explanation: This error message typically follows a previous error. If so this error message can be ignored.
previous error. If so this error message can be ignored. Otherwise contact IBM Support.
Otherwise contact IBM Support.
System action:
System action:
User response: Contact IBM Support.
User response: Contact IBM Support.
FMM9208E System error errno: errno text at position:
FMM9203E Additional support information: An file(line).
exception was thrown at position:
Explanation: A system call failed with errno.
position(line).
System action:
Explanation: This error message typically follows a
previous error. If so this error message can be ignored. User response: Check errno and errno text with you
Otherwise contact IBM Support. system administrator. If you cannot resolve the
problem, contact IBM Support.
System action:
User response: Contact IBM Support.
FMM9209E Additional support information: No
handler registered for message type
FMM9204E Additional support information: An message. Thrown at position: file(line).
exception was thrown at position:
Explanation: This error message typically follows a
file(line) (text_description).
previous error. If so this error message can be ignored.
Explanation: This error message typically follows a Otherwise contact IBM Support.
previous error. If so this error message can be ignored.
System action:
Otherwise contact IBM Support.
User response: Contact IBM Support.
System action:
User response: Contact IBM Support.
FMM9210E ESD_AbortDispatchingException thrown
at position: file(line).
Explanation: An internal error occurred.
System action:
User response: Contact IBM Support.

Chapter 2. FMM messages 167

FMM9211E • FMM9221E

FMM9211E Additional support information: An FMM9216E Additional support information: An

exception was thrown at position: exception was thrown at position:
file(line). (State state) file(line).
Explanation: This error message typically follows a Explanation: This error message typically follows a
previous error. If so this error message can be ignored. previous error. If so this error message can be ignored.
Otherwise contact IBM Support. Otherwise contact IBM Support.
System action: System action:
User response: Contact IBM Support. User response: Contact IBM Support.

FMM9212E Additional support information: No FMM9217E Additional support information: An

handler registered for message type exception was thrown at position:
(message_type, classname). Thrown at file(line).
position: file(line).
Explanation: This error message typically follows a
Explanation: This error message typically follows a previous error. If so this error message can be ignored.
previous error. If so this error message can be ignored. Otherwise contact IBM Support.
Otherwise contact IBM Support.
System action:
System action:
User response: Contact IBM Support.
User response: Contact IBM Support.
FMM9218E Additional support information: An
FMM9213E A memory allocation request failed at exception was thrown at position:
position: file(line). file(line).
Explanation: This error message indicates an Explanation: This error message typically follows a
out–of–storage condition. It may occur due to a previous error. If so this error message can be ignored.
previous error, or it may be owed to a large size of the Otherwise contact IBM Support.
internal buffers.
System action:
System action:
User response: Contact IBM Support.
User response: Check for and respond to preceding
error messages. You may also want to reduce the size
FMM9219E Additional support information: Invalid
of the internal buffers (keyword BUFFSIZE in the Data
error type type encountered.
Protection for SAP profile).
Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
FMM9214E Additional support information: An
Otherwise contact IBM Support.
exception was thrown from a destructor.
System action:
Explanation: This error message typically follows a
previous error. If so this error message can be ignored. User response: Contact IBM Support.
Otherwise contact IBM Support.
System action: FMM9220E Additional support information: Second
call of call.
User response: Contact IBM Support.
Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
FMM9215E The maximum string length supported
Otherwise contact your IBM Support.
for name is length.
System action:
Explanation: The supported string length of a system
component, e.g. file name or hostname has been User response: Contact your IBM Support.
violated.
System action: FMM9221E The operation ended prematurely with
return code rc. An exception was thrown
User response: Check the components involved in the
at position: file(line).
operation. If the problem cannot be resolved contact
your IBM support personnel. Explanation: An operation could not be finished
successfully due to an unexpected termination.
System action:

168 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM9222E • FMM9231E

User response: Check the logs for further information. System action: Processing ends.
If the problem cannot be resolved contact your IBM
User response: Check if the ASM instance with the
support personnel.
specified SID is available and started.

FMM9222E A snapshot–type operation was

FMM9227E The ASM diskgroup 'diskgroup' has not
interrupted, Additional support
been found. Ensure that it is available.
information: An exception was thrown
at position: file(line). Explanation: The specified diskgroup is needed for
the backup but it has not been found in the ASM
Explanation: A snapshot operation could not be
instance.
finished successfully due to an unexpected interruption.
System action: Processing ends.
System action:
User response: Please ensure that the diskgroup is
User response: Check the logs for further information.
available in your ASM instance and that it is mounted.
If the problem cannot be resolved contact your IBM
support personnel.
FMM9228E Excpected ASM file but found file: 'file'
FMM9223E The operation will be aborted. Explanation: ASM files were expected, but a non-ASM
file has been found. This might occur if your database
Explanation: An internal error during an operation
resides on ASM and non-ASM files.
leads to an abort of that operation.
System action: Processing ends.
System action:
User response: Please ensure that you do not have a
User response: Check the logs for further information.
mixed environment with ASM and non-ASM files.
If the problem cannot be resolved contact your IBM
support personnel.
FMM9229E Excpected file but found ASM file: 'file'
FMM9224E The operation will be aborted. Check Explanation: Non-ASM files were expected, but an
for other error messages in the log files. ASM file has been found. This might occur if your
database resides on ASM and non-ASM files.
Explanation: An internal error during an operation
leads to an abort of that operation. System action: Processing ends.
System action: User response: Please ensure that you do not have a
mixed environment with ASM and non-ASM files.
User response: Check the logs for further information.
If the problem cannot be resolved contact your IBM
support personnel. FMM9230E The SSL/TLS certificate provided by the
server is missing a valid subject DN or
issuer DN field.
FMM9225E The keyword 'keyword' has not been
found in the line 'line' of the file Explanation: The subject DN or issuer DN field of the
'file_name'. Please change it back to the certificate provided by the server is missing. Both fields
original value if you modified it. are mandatory fields to allow a validation of the
certificate.
Explanation: Occurs for example if the entries in the
file /etc/inittab have been modified before a second System action: The task stopped before successfully
installation. completing.
System action: User response: Import a valid server certificate to the
key ring database 'fcmcert.kdb'.
User response: Change the modified line in the
file_name back to the original value, keyword gives a hint
to what is expected. FMM9231E The SSL/TLS certificate provided by the
server is not proving its supposed
identity.
FMM9226E The ASM instance with SID='instance id'
is not available. Please check if the Explanation: The SSL/TLS certificate provided by the
ASM_INSTANCE_ID is set to the right server is not issued for the server that was supposed to
ASM instance, if yes start it and check connect. The alternative name or subject CN field of the
the availability. certificate does not match the hostname or IP address
of the server that was actually connected.
Explanation: The ASM instance with the specified SID
could not be accessed.

Chapter 2. FMM messages 169

FMM9300E • FMM9312E

System action: The task stopped before successfully Explanation: The product failed to load the
completing. appropriate winsock dll.
User response: Revalidate the correctness of the System action:
certificate that has been imported to the key ring
User response: Contact your system administrator.
database 'fcmcert.kdb'. Its alternative name or subject
CN field needs to match the hostname or IP address as
stated in the IBM Tivoli Storage FlashCopy Manager FMM9308E A socket request timed out after
profile (GLOBAL section, parameter ACSD). processing number of bytes bytes. file(line).
Explanation: A socket request was issued with a
FMM9300E Additional support information: timeout and the requested action could not be
Aborting 'send' operation. See previous completed within the time specified. It was cancelled
error. after processing number of bytes bytes.
Explanation: This error may have been caused by System action:
previous errors.
User response: If you need to call IBM Support,
System action: provide the information given in this message together
with the error information.
User response: Check for previous errors and correct
them.
FMM9309E Operation terminated due to an explicit
abort request.
FMM9301E Additional support information: State
state does not match state pattern pattern. Explanation: An operation was terminated due to
customer intervention.
Explanation: This error message typically follows a
previous error. If so this error message can be ignored. System action:
Otherwise contact IBM Support.
User response: None.
System action:
User response: Contact your IBM Support. FMM9310E Could not add backup_id to the
repository at path.
FMM9302E Additional support information: A Explanation: The system was not able to add
process ended unexpectedly. Check information on the named backup to the repository
previous error messages. located in the path indicated.
Explanation: This error message typically follows a System action:
previous error. If so this error message can be ignored.
Otherwise contact your IBM Support. User response: Make sure the repository path is set
correctly. If you need to correct the repository location,
System action: Processing ends restart the server executable afterwards. If the problem
persists contact your IBM support personnel.
User response: Contact your IBM Support.

FMM9311E Could not find backup_id in the

FMM9306I Dumping callstack.
repository at path.
Explanation: This message is always preceded by an
Explanation: Information on the backup denoted by
error message indicating the problem. It provides
the backup ID could not be found in the repository
additional information that might help IBM Support to
located in the path indicated.
analyze the cause of the problem.
System action:
System action:
User response: Make sure the repository path is set
User response: If you need to call IBM Support,
correctly. If you need to correct the repository location,
provide the information given in this message together
restart the server executable afterwards. If the problem
with the error information.
persists contact your IBM support personnel.

FMM9307E Did not find a winsock dll compatible

FMM9312E backup_id is currently locked in the
with version major_winsock_version.
repository at repository.
minor_winsock_version. Version found is
low_byte_available Explanation: The information on the backup denoted
version.high_byte_available_version. by the backup ID is currently locked by a different

170 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM9313E • FMM9327I

process. Make sure to run only a single operation using User response: Correct the profile or the call as
a specific backup at a time. appropriate.
System action:
FMM9317E The specified backup id 'backup_id' must
User response: Wait for the other operation to finish
have char_count characters. If the
or abort this operation. Then start again. If the problem
specified amount of characters exists,
persists contact your IBM support personnel.
make sure there are no special
characters.
FMM9313E Failed to update backup_id in the
Explanation: The length of the specified backup id is
repository at path.
incorrect.
Explanation: The information on the named backup
System action:
could not be updated in the repository located at the
path named. User response: Correct the length of the backup id to
match the specified length.
System action:
User response: Check the logs for other messages
FMM9318E The file 'filename' has not been found. It
pointing to the cause of this problem. Resolve any
is required for the device agent to
problems indicated. If the problem persists contact your
function. Check your installation.
IBM support personnel.
Explanation: The specified file has not been found
even though it was included in the installation.
FMM9314E Could not remove backup_id from the
repository at path. System action:
Explanation: An attempt to remove the information User response: Check that the specified file is
on the backup named from the repository located at the available in the specified location. Consider installing
path indicated failed. the product again in order to make the file available.
System action:
FMM9319E Operation is terminated.
User response: Check the logs for other messages
pointing to the cause of this problem. Resolve any Explanation: The current operation is stopped. See
problems indicated. If the problem persists contact your other errors in the log file.
IBM support personnel.
System action: The operation stops.
User response: Check for other errors in the log file. If
FMM9315E Could not access the repository at 'path'
no other errors are found, contact your product support
because it is currently locked by another
team.
process.
Explanation: When starting up, the server tried to
FMM9320W Warning: Backup of previous profile
load the repository located at the path named.
version failed (file access error).
However, the repository was locked by a different
process. This can happen if two server processes try to Explanation: Before writing a new version of the
use the same repository. This is not supported. profile, the previous version is renamed into
<profilename>.bck. Due to an error renaming failed so
System action:
that the original profile is just overwritten by the new
User response: Make sure each instance of the server revision. As a consequence, no backup of the previous
uses its own repository. version is available.
System action: None.
FMM9316E The name 'name' refers to an existing file
User response: Ensure the backup variants of your
or directory, but it does not appear to be
profile (extensions .bck and .bck2) are writable.
a valid repository. In order to continue
you need to specify either a non existing
directory or the path of an existing valid FMM9327I Note: No FCM server certificate found
repository. in key database and no self-signed
certificate file
Explanation: The server could not locate its repository
${GSKIT_SELFSIGNED_CERT_FILENAME}
when it started.
found to be imported. If not using CA
System action: signed certificates, import self-signed
certificate from Production System (PS).
For details, refer to the User's Guide.

Chapter 2. FMM messages 171

FMM9328E • FMM9335E

Explanation: Except when using CA signed certificates

FMM9331E Error: Invalid User name. The user name
the public part of the self-signed server certificate needs
must be longer than min but cannot
to be imported to the key database of the IBM Tivoli
exceed max characters. The current
Storage FlashCopy Manager installation on backup and
length is len.
cloning system nodes (BS/CS).
Explanation: The user name specified in the profile is
System action: If a CA signed certificate is installed to
not valid.
the key database on production system (PS), the
message can be ignored; IBM Tivoli Storage FlashCopy System action: Processing will end.
Manager correctly operates. If no CA signed certificate
User response: Correct the user name specified in
is installed on PS, IBM Tivoli Storage FlashCopy
your profile.
Manager fails to operate until the self-signed server
certificate has been deployed to the backup and cloning
system nodes. FMM9332E Error: Invalid User password. Run
'fcmcli -f password' to create the
User response: Copy the self-signed server certificate
password. The password must be longer
file 'fcmselfcert.arm' from the IBM Tivoli Storage
than min but cannot exceed max
FlashCopy Manager instance installation path on
characters. The current length is len.
production system (PS) to the IBM Tivoli Storage
FlashCopy Manager installation path on your backup Explanation: The specified password is not valid.
or cloning system. Rerun the setup script to
automatically import the file to the key database. System action: Processing ends.
User response: Run 'fcmcli -f password' to set the
FMM9328E An error occurred in the secure correct password.
communication layer when running the
following function: function. GSKit FMM9333E Error: Invalid Secondary Server name.
return code: numeric return code. GSKit The server name cannot exceed a length
error: return value. of max characters. The current length is
Explanation: Information about the error is provided len.
in the return value. Explanation: The Secondary Server name specified is
System action: The task stopped before successfully not valid.
completing. System action: Processing will end.
User response: Resolve the problem identified in the User response: Correct the Secondary Server name
return value. Try the operation again. specified in your profile.

FMM9329E An error occurred when the software FMM9334E Error: Invalid Server installation
tried to link the SSL Implementation to directory. The path to install directory
GSKit. GSKitWrapper error: 'linker error' cannot exceed a length of max
Explanation: Information about the error is provided characters. The current length is len.
in linker error. Explanation: The Server install directory is invalid.
System action: The task stopped before successfully System action: Processing ends.
completing.
User response: Correct the Server install directory.
User response: Resolve the problem identified in the
linker error. Try the operation again.
FMM9335E Error: Invalid Java home directory. The
path to the Java Home directory cannot
FMM9330E Error: Invalid Server name. The server exceed a length of max characters. The
name must be longer than min but current length is len.
cannot exceed max characters. The
current length is len. Explanation: The Java™ Home directory is invalid.

Explanation: The server name specified in the profile System action: Processing ends.
is not valid. User response: Correct the Java Home directory.
System action: Processing ends.
User response: Correct the servername specified in
your profile.

172 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM9336E • FMM9342E

can have situations where you cannot always reuse the

FMM9336E Error: Invalid Port number. The port
oldest target set for a new operation. For example you
number cannot be higher than max. The
have started a FlashCopy Backup on space efficient
current port is port.
target set T1 on Monday and you started a FlashCopy
Explanation: The specified port is invalid. Cloning on a full target set T2 on Tuesday. Now you
need to restart the FlashCopy Cloning in the same
System action: Processing will end.
target set T2. This will result in the above error
User response: Correct the port number in your situation where you would destroy the FlashCopy
profile. Backup from Monday. FlashCopy Manager has
implemented this error handling so that you cannot
destroy FlashCopy Backups by accident. If you need to
FMM9337W The given port number port is already in restart the FlashCopy Cloning operation urgently and
use by another process. you accept to loose FlashCopy Backups, then you can
Explanation: The specified port is currently occupied start the FlashCopy Cloning operation with the force
by another process. The port might be still occupied option [-F] which will destroy the FlashCopy Backups
during later operation which will cause the product is and allows the FlashCopy Cloning operation to run
not able to operate properly. successfully.

System action: System action:

User response: Change port number in your profile. User response: You can either wait until the older
FlashCopy mappings are in state idle_or_copy or you
can start the Cloning operation with the force flag [-F]
FMM9339E The specified device class name is which will force the older FlashCopy mappings to be
already in use by section section. stopped. In the latter case you will loose your older
Explanation: The specified device class is already FlashCopy Backups or Clones.
referenced by a section of another type. A given device
class may be used exclusively either by a CLIENT or a FMM9341E The name of the clone database is
CLONING section missing.
System action: Explanation: The device class that is associated with
User response: Choose another device class name the clone database requires at least one database name
which is not in use by another section type. to be specified.
System action:
FMM9340E The FlashCopy Cloning operation failed User response: Specify one (or more) database names.
because the FlashCopy mappings used If more than one database name is specified, separate
for Cloning are dependent on older each name with a space.
FlashCopy mappings from older
FlashCopy Backup or Cloning
operations. You can either wait until the FMM9342E Unmounting of file system 'filesystem' at
older FlashCopy mappings are in state backup system does not work.;
idle_or_copy or you can start the Explanation: The GPFS command mmumount -force
Cloning operation with the force option was not able to unmount the file system.
[-F] which will force the older
FlashCopy mappings to be stopped. In System action: Processing ends.
the latter case you will loose your older
User response: Check what prevents the unmount of
FlashCopy Backups or Clones.
the remote GPFS file system. Solve this issue and call
Explanation: When you perform FlashCopy Backup the IBM Tivoli Storage FlashCopy Manager unmount
and Cloning operations of the same production command again.
database to multiple FlashCopy target sets then you

Chapter 2. FMM messages 173

FMM50001E • FMM50009E

FMM messages for Microsoft Management Console

FMM messages in the range 500000-50099 are issued by IBM Tivoli Storage
FlashCopy Manager for Windows. The messages concern the Microsoft
Management Console (MMC).

Tivoli Storage FlashCopy Manager V4.1.1 messages that concern Microsoft

Management Console are listed in ascending numerical order. The complete
message is documented, including message ID, message text, explanation, system
action, and user response.

FMM50001E The product license could not be FMM50006E Email must configured before mail can
opened. be sent.
Explanation: At least one license is required. If this is Explanation: One or more email settings is not
a PTF package ensure that it is being installed over an configured.
existing package.
System action: Processing will continue.
System action: Processing ends.
User response: Click Settings... to configure email.
User response: Install the product again by running
SetupFCM. SetupFCM is located in the root of your GA
FMM50007I Windows PowerShell is not installed.
media. SetupFCM stores the media location in the
registry when it is run. This will help to ensure that the Explanation: Windows PowerShell is required to run
correct licenses can be found. the selected script.
System action: The selected script will not be run.
FMM50002E The product registry key could not be
opened. User response: Install Windows PowerShell.
PowerShell is included with Windows Server 2008 and
Explanation: The product registry key is missing. above but must be enabled as a feature using Windows
Server Manager. For earlier versions of Windows,
System action: Processing ends.
PowerShell can be obtained from the Microsoft
User response: Reinstall the product to create the download site.
required registry keys.
FMM50008E The application cannot run in safe
FMM50003E Unable to connect to the TSM server. mode.
Explanation: Communication with a TSM server could Explanation: The application requires either Services
not be established using the specified settings. or Drivers that are not available when running in safe
mode.
System action: Does not connect to the TSM server.
System action: The application processing stops.
User response: Update TSM server settings as needed.
Review the TSM BA client dsmerror.log file for details. User response: Restart the system using the normal
startup. When the system is started, run the
application.
FMM50004E Unable To Obtain RSS Feed
Explanation: An attempt to read an RSS feed was
FMM50009E Windows PowerShell 3.0 or above, a
made but could not be established.
prerequisite for Tivoli Storage
System action: Processing will continue. FlashCopy Manager, is not installed.
Install the prerequisite software before
User response: Ensure that there is an internet running Tivoli Storage FlashCopy
connection Manager.
Explanation: Microsoft Windows PowerShell 3.0 or
FMM50005E No RSS items were available. above is a prerequisite for Tivoli Storage FlashCopy
Explanation: An RSS feed was read but no items were Manager. This prerequisite is not met so the Tivoli
available. Storage FlashCopy Manager software is not going to
run.
System action: Processing will continue.
System action: Install the prerequisite software before
User response: Try the operation again at a later time.

174 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM50010E • FMM18005E

installing and running Tivoli Storage FlashCopy Explanation: {0} was started with a parameter in the
Manager. command line that specifies a file that does not exist.
File -> {1}
User response: Microsoft Windows PowerShell is
available for download from the Microsoft Windows System action: Start {0} with valid parameters.
web site.
User response: Ensure the command line parameters
are correct and try again.
FMM50010E
Explanation: Can not connect to the computer. {0} FMM50013E
System action: Application processing continues. Explanation: When starting the software, a parameter
in the command line specified a SQL Server instance
User response: Ensure that the computer name and
that does not exist. The SQL Server instances that are
credentials are specified correctly and try again.
not found are: '{0}'. The available SQL Server instances
are: '{1}'
FMM50011E {0} will not start with invalid
System action: Start {0} by referencing an available
parameters.
SQL Server instance.
Explanation: {0} was started with a bad parameter in
User response: Review the command line parameters
the command line. Bad argument -> {1}
to ensure there are no typographical errors. You can
System action: Start {0} with valid parameters. also test the connection the SQL Server instance that is
being called, but is not found.
User response: Ensure the command line parameters
are correct and try again.

FMM50012E {0} will not start with invalid

parameters.

FMM messages for IBM XIV storage systems

FMM messages in the range 18000-18199 are issued by IBM Tivoli Storage
FlashCopy Manager components that use the IBM XIV Storage System.

Tivoli Storage FlashCopy Manager V4.1.1 messages that concern the IBM XIV
Storage System are listed in ascending numerical order. The complete message is
documented, including message ID, message text, explanation, system action, and
operator response.
in more detail. For more information, see the specified
FMM18000E FcmParserException thrown.
trace file for detailed information about the conditions
Explanation: The generic command parser of the that caused this problem.
storage device adapter failed because an exception
Operator response: The occurrence of this error
occurred. This error message is preceded by another
message indicates that an internal error occurred. This
error message that specifies the root cause of the issue
error might be caused by an installation of Tivoli
in more detail.
Storage FlashCopy Manager that installed with errors
Operator response: The occurrence of this error or a recent product update that was interrupted during
message indicates that an internal error occurred. This the installation. Reinstall the product to ensure that all
error might be caused by an installation of Tivoli of its components are at the same version level.
Storage FlashCopy Manager that installed with errors
or a recent product update that was interrupted during
FMM18005E No value is specified for the mandatory
the installation. Reinstall the product to ensure that all
parameter_key parameter.
of its components are at the same version level.
Explanation: The generic command parser of the
storage device adapter fails because no value is
FMM18003E FcmParserException thrown, see trace_file
provided for the parameter with the specified key. This
for details.
error is probably caused by a configuration problem.
Explanation: The generic command parser of the
Operator response: Rerun the setup routines and the
storage device adapter failed because an exception
Tivoli Storage FlashCopy Manager profile configuration
occurred. This error message is preceded by another
wizard to ensure that the profile is consistent and
error message that specifies the root cause of the issue

Chapter 2. FMM messages 175

FMM18006W • FMM18014E

complete. Also, verify that the configuration of your Tivoli Storage Manager profile configuration wizard to
target set files is correct if applicable. ensure that the profile is consistent and complete.

FMM18006W The logfilename log file cannot be FMM18011E Unable to read from the standard input
created. (STDIN).
Explanation: The log file cannot be created at the Explanation: The generic command parser of the
specified location because the path does not exist or storage device adapter failed after receiving messages
write permissions are not assigned to the directory. from Tivoli Storage FlashCopy Manager.
Operator response: The log file is created in the logs Operator response: The occurrence of this error
subfolder in the ACS_DIR directory as specified in the message indicates that an internal error occurred. This
profile configuration file. Ensure that this folder exists error might be caused by an installation of Tivoli
and that the correct access rights are assigned to the Storage FlashCopy Manager that installed with errors
directory. Reconfigure the ACS_DIR parameter in the or a recent product update that was interrupted during
GLOBAL section of the profile if appropriate. the installation. Reinstall the product to ensure that all
of its components are at the same version level.
FMM18007W The message_received message is
received but the message_expected FMM18012E The key key is not allowed after message
message is expected. message.
Explanation: The generic command parser of the Explanation: The generic command parser of the
storage device adapter received a message that it storage device adapter did not receive the message as
cannot handle in its current state. This message is expected according to its internal state machine.
ignored.
Operator response: The occurrence of this error
Operator response: No action is required. message indicates that an internal error occurred. This
error might be caused by an installation of Tivoli
Storage FlashCopy Manager that installed with errors
FMM18008E The key parameter is not present in the
or a recent product update that was interrupted during
profile.
the installation. Reinstall the product to ensure that all
Explanation: The specified parameter is missing in the of its components are at the same version level.
profile configuration or no value is assigned to this
parameter.
FMM18013E FcmStorageDeviceException thrown, see
Operator response: Rerun the setup routines and the trace_file for details.
Tivoli Storage FlashCopy Manager profile configuration
Explanation: The generic storage device adapter layer
wizard to ensure that the profile is consistent and
received an exception from the storage adapter
complete.
implementation. This error message is preceded by
other error messages that specify the root cause of the
FMM18009E FcmStorageDeviceException thrown. issue in more detail. The specified trace file provides
more detailed information about the conditions that
Explanation: The generic storage device adapter layer lead to this issue.
received an exception from the storage adapter
implementation. This error message is preceded by User response: This error is specific to the device
other error messages that specify the root cause of the adapter implementation or the storage device it
issue in more detail. interacts with. Review the preceding error message and
the specified trace file to identify the root cause as the
Operator response: This error is specific to the device source can result from various areas.
adapter implementation or the storage device it
interacts with. Review the preceding error message to
identify the root cause as the source can result from FMM18014E FcmProfileException thrown, see
various areas. TraceFile for details.
Explanation: The generic command parser of the
FMM18010E FcmProfileException thrown. storage device adapter failed because an exception
occurred. This error message is preceded by another
Explanation: The generic command parser of the error message that specifies the root cause of the issue
storage device adapter failed because an exception in more detail. For more information, see the specified
occurred. This error message is preceded by another trace file for detailed information about the conditions
error message that specifies the root cause of the issue that caused this issue.
in more detail.
Operator response: Rerun the setup routines and the
Operator response: Rerun the setup routines and the Tivoli Storage FlashCopy Manager profile configuration

176 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM18016W • FMM18025E

wizard to ensure that the profile is consistent and

FMM18021E When starting the function function, the
complete.
list of snapshot items that are received
from Tivoli Storage FlashCopy Manager
FMM18016W The logdir log directory cannot be OS agent is empty.
created.
Explanation: The snapshot item list is empty.
Explanation: The log file directory cannot be created
Operator response: Issue the inquire function to verify
at the specified location. This issue can arise because
that this backup is valid for the named operation.
write permissions are not assigned to the directory.
Operator response: The log file directory is created as
FMM18022E No response received from the storage
a subfolder in the ACS_DIR directory as specified in
device adapter.
the profile configuration file. Ensure that this directory
exists and that the correct access rights are assigned to Explanation: The response data that is expected from
the directory. Reconfigure the ACS_DIR parameter in the requested call to the storage device adapter is not
the GLOBAL section of the profile if appropriate. present.
Operator response: Verify the installation and
FMM18017E The Message message received, ends the configuration of the specific storage device adapter.
current operation.
Explanation: This error message indicates that the FMM18023W When invoking the function function,
storage device adapter was instructed by Tivoli Storage the list of snapshots that was received
FlashCopy Manager to end the current operation. from Tivoli Storage FlashCopy Manager
OS agent is empty.
Operator response: This message is resulting from an
internal control flow mechanism. This flow is triggered Explanation: A request for the specified function was
by an aborted operation at a higher level that is received. However, the list of snapshots is empty.
triggered by a user or an error condition. No action is
Operator response: This message is a warning
required.
message and depending on the context no action might
be required.
FMM18018E The message message is not allowed in
this context.
FMM18024E The storage adapter implementation did
Explanation: The generic command parser of the not provide a complete set of
storage device adapter received an unexpected message capabilities. The missing keys are:
that is not allowed in this context and therefore cannot missing_keys
be handled.
Explanation: Each storage device adapter
Operator response: The occurrence of this error implementation is expected to provide information
message indicates that an internal error occurred. This about its specific capabilities. Tivoli Storage FlashCopy
error might be caused by an installation of Tivoli Manager must have a fixed set of capabilities that are
Storage FlashCopy Manager that installed with errors required for handling the storage device according to
or a recent product update that was interrupted during its specific characteristics. Some or all of these
the installation. Reinstall the product to ensure that all capabilities are not provided by the storage adapter
of its components are at the same version level. implementation.
Operator response: Verify the installation and
FMM18020E No additional messages are allowed configuration of the specific storage device adapter.
after the #END tag. The message message Ensure that it is compatible with the version of Tivoli
might belong to the next section. Storage FlashCopy Manager that you are using.
Explanation: The generic command parser of the
storage device adapter received an unexpected message FMM18025E The storage adapter implementation did
that is not allowed in this context and therefore cannot not provide the expected monitoring
be handled. The occurrence of this error message information for the snapshot_name
indicates an internal error. snapshot.
Operator response: The occurrence of this error Explanation: Some storage device types perform
message indicates that an internal error occurred. This background copy operations that must be monitored by
error might be caused by an installation of Tivoli Tivoli Storage FlashCopy Manager. During monitoring,
Storage FlashCopy Manager that installed with errors the storage device adapter is periodically polled to
or a recent product update that was interrupted during provide an update on the status of the copy operation.
the installation. Reinstall the product to ensure that all This monitoring information was not provided by the
of its components are at the same version level. storage adapter implementation as expected.

Chapter 2. FMM messages 177

FMM18026E • FMM18033E

Operator response: Verify the installation and

FMM18030E The backup ID provided by Tivoli
configuration of the specific storage device adapter.
Storage FlashCopy Manager must
Ensure that it is compatible with the version of Tivoli
contain a value.
Storage FlashCopy Manager that you are using.
Explanation: When Tivoli Storage FlashCopy Manager
requests a new backup, the generic device adapter
FMM18026E The parsed value [value] has an invalid
layer expects a backup identifier to be passed as a
format that cannot be parsed.
parameter. This identifier is not present.
Explanation: The specified value has an unknown
Operator response: The occurrence of this error
format that cannot be handled by the parser of the
message indicates an internal error. This problem might
generic storage adapter layer.
be caused by an installation of Tivoli Storage
Operator response: The occurrence of this error FlashCopy Manager that installed with errors or a
message indicates an internal error. This problem might recent product update that was interrupted during the
be caused by an installation of Tivoli Storage installation. Reinstall the product to ensure that all of
FlashCopy Manager that installed with errors or a its components are at the same version level.
recent product update that was interrupted during the
installation. Reinstall the product to ensure that all of
FMM18031E The mandatory attribute [attribute] is
its components are at the same version level.
missing.
Explanation: The generic command parser of the
FMM18027E The [target_volume] target volume is
storage device adapter received a data structure which
specified multiple times.
is missing the specified attribute. The attribute is
Explanation: For the specification of target volumes, mandatory for successfully processing the current
each target volume can be specified only once. The request or response to a request.
provided target set contains duplicated target volumes.
Operator response: The occurrence of this error
Operator response: Review your target set definition message indicates that an internal error occurred. This
file and ensure that each target volume occurs only error might be caused by an installation of Tivoli
once. Storage FlashCopy Manager that installed with errors
or a recent product update that was interrupted during
the installation. Reinstall the product to ensure that all
FMM18028E The [source_volume] source volume is of its components are at the same version level.
specified multiple times.
Explanation: For explicitly mapping source volumes FMM18032E The adapter implementation did not
to target volumes, each source volume can be specified provide a result for the delete request of
only once. The provided target set contains duplicated snapshot [snapshot].
source volumes.
Explanation: The adapter implementation is expected
Operator response: Review your target set definition to provide an indication how it processed the snapshots
file and ensure that each specified source volume that were requested to be deleted. The adapter
occurs only once. implementation did not provide a result for the
specified snapshot.
FMM18029E The global unique identifier that is Operator response: The occurrence of this error
provided by Tivoli Storage FlashCopy message indicates that an internal error occurred. This
Manager must contain a value. error might be caused by an installation of Tivoli
Explanation: When Tivoli Storage FlashCopy Manager Storage FlashCopy Manager that installed with errors
requests a new backup, the device agent API expects a or a recent product update that was interrupted during
global unique identifier to be passed as a parameter. the installation. Reinstall the product to ensure that all
This identifier is not present. of its components are at the same version level.

Operator response: The occurrence of this error

message indicates an internal error. This error might be FMM18033E The storage device adapter did not
caused by an installation of Tivoli Storage FlashCopy accept the provided target set.
Manager that installed with errors or a recent product Explanation: The storage device adapter must
update that was interrupted during the installation. explicitly accept the target set that is provided by Tivoli
Reinstall the product to ensure all that all of its Storage FlashCopy Manager. Target set definitions
components are at the same version level. might not be supported or do not apply to this kind of
storage device adapter.
Operator response: Verify the installation and
configuration of the storage device adapter. Ensure that

178 IBM Tivoli Storage FlashCopy Manager: Messages

 FMM18034E • FMM18036E

the adapter supports the target set definitions and is

compatible with the version of Tivoli Storage
FlashCopy Manager that you are using. If the storage
device adapter does not support target sets, verify that
no target set is specified in the Tivoli Storage
FlashCopy Manager profile.

FMM18034E The storage device adapter

implementation requires a newer
version of the device agent API
(expectedVersion > actualVersion).
Explanation: The storage adapter implementation was
developed with a newer version of the device agent
API than the one that is installed. Since this
combination is potentially incompatible, processing
cannot continue.
Operator response: The storage adapter was deployed
to an old version of Tivoli Storage FlashCopy Manager.
Exchange the storage adapter with an older version
that is compatible with your Tivoli Storage FlashCopy
Manager version or upgrade to the latest version of
Tivoli Storage FlashCopy Manager.

FMM18035E The storage device adapter

implementation expects an invalid
version of the device agent API: version.
Explanation: The storage adapter implementation
expects a version of the device agent API that is not
valid or no version information is provided.
Operator response: This error indicates an issue with
the storage adapter. Contact the storage adapter
vendor.

FMM18036E The device agent API version is not

valid: version.
Explanation: The device agent API reports a version
that is not valid or is unknown.
Operator response: This error message indicates that
an error occurred. This error might be caused by an
installation of Tivoli Storage FlashCopy Manager that
installed with errors or a recent product update that
was interrupted during the installation. Reinstall the
product to ensure that all of its components are
installed properly.

Chapter 2. FMM messages 179

180 IBM Tivoli Storage FlashCopy Manager: Messages
Chapter 3. FMF messages
Messages with prefix FMF are issued by the IBM Tivoli Storage FlashCopy
Manager for Windows Microsoft Management Console (MMC) Snap-in and Base
System Services component. Tivoli Storage FlashCopy Manager V4.1.1 FMF
messages are listed in ascending numerical order. The complete message is
documented, including message ID, message text, explanation, system action, and
user response.

FMF0003S An internal processing error has FMF0055E Write failure on license file (licensefile).
occurred.
Explanation: An attempt to write to the license file
Explanation: An internal processing error has failed.
occurred.
System action: Processing ends.
System action: Processing ends.
User response: Make sure enough space exists on the
User response: Retry the operation. If this error workstation to write to the license file. If enough space
persists, contact your service representative. exists, run the command again.

FMF0004E An unknown error has been detected. FMF0056E Data in the license file (licensefile) is not
in a valid format.
Explanation: An internal processing error has
occurred that prevents the generation of a message for Explanation: An attempt to read information from the
a return code. license file failed.
System action: Processing continues. System action: Processing ends.
User response: Retry the operation. If this error User response: Install the product again.
persists, contact your service representative.
FMF0057E The checksum in the license file
FMF0005E Out of memory. Stop other processes (licensefile) does not match the license
and try the operation again. string text.
Explanation: The machine has run out of memory. Explanation: An attempt was made to read
information from the license file. The checksum was
System action: Processing continues.
not valid so it appears that the license file is not at the
User response: Close unnecessary processes and try correct level.
the operation again.
System action: Processing ends.
User response: Reinstall the product.
FMF0053E License file (licensefile) could not be
opened.
FMF0058E The 'Try and Buy' license has expired.
Explanation: An attempt to read from the license file
failed. Explanation: This 'Try and Buy' license that was
detected has expired.
System action: Processing ends.
System action: Processing ends.
User response: Install the product again. This ensures
that the correct license file is installed. User response: This product is no longer valid for use.
A valid license must be obtained before running the
product.
FMF0054E Read failure on license file (licensefile).
Explanation: An attempt was made to read from the
FMF0100E Incomplete command:
license file. This attempt failed.
Explanation: This message displays the incomplete
System action: Processing ends.
command that was entered.
User response: Reinstall the product. This will ensure
System action: Processing ends.
that the correct license file is installed.

© Copyright IBM Corp. 1995, 2014 181

FMF0101E • FMF0152I

User response: Re-enter the complete command. display with this message to determine the problem.

FMF0101E Invalid argument: FMF0133W Could not locate installation directory.

Attempting to continue...
Explanation: This message displays the command that
was entered, up to and including the invalid command Explanation: An attempt was made to read the
or option argument that was detected. registry to determine where the Tivoli Data Protection
application client was installed. This attempt failed.
System action: Processing ends.
System action: Processing will continue with the
User response: Re-enter the command specifying a
command entered.
valid argument for the command or option.
User response: There should be other messages along
with this one. Refer to the other messages to determine
FMF0102E Invalid command:
the problem. If the problem can not be determined, it
Explanation: This message displays the invalid may be necessary to reinstall the application client
command that was entered. code. This will ensure that the registry entries are set
up correctly.
System action: Processing ends.
User response: Re-enter a valid command. FMF0134W Could not locate log directory.
Processing will continue...
FMF0103E Invalid option for the specified Explanation: An attempt was made to read the
command: registry to determine where the Tivoli Data Protection
Explanation: This message displays the command that application client log is located. This attempt failed.
was entered, up to and including the option that was System action: Processing will continue with the
detected as invalid for the command. command entered.
System action: Processing ends. User response: There should be other messages along
User response: Re-enter the command specifying valid with this one. Refer to the other messages to determine
command options. the problem. If the problem can not be determined, it
may be necessary to reinstall the application client
code. This will ensure that the registry entries are set
FMF0104E Invalid option: up correctly.
Explanation: This message displays the command that
was entered, up to and including the invalid option FMF0150I Operation canceled by user.
that was detected.
Explanation: The user has requested that the IBM
System action: Processing ends. Tivoli Storage Manager application client end by
User response: Re-enter the command specifying valid entering ctrl-C.
command options. System action: Processing ends.
User response: None
FMF0105E Missing argument:
Explanation: This message displays the command that FMF0151E Errors occurred while processing the
was entered, up to and including the command or request.
option whose required argument is missing.
Explanation: Attempting to process the request
System action: Processing ends. entered, an error occurred.
User response: Re-enter the command specifying a System action: Processing ends.
valid argument for the command or option.
User response: Attempt to determine the source of the
errors from viewing the log file. Correct the problems
FMF0132W Tracing could not be started. Processing and try running the command again.
will continue.
Explanation: A problem prevented tracing from FMF0152I Performance stats: seconds seconds spent
beginning. in apicall API calls
System action: Processing will continue with the Explanation: The indicated number of seconds were
command entered. spent making API calls for the indicated system.
User response: Refer to the other messages that System action: Processing continues.

182 IBM Tivoli Storage FlashCopy Manager: Messages

 FMF0153I • FMF0200E

User response: None

FMF0160E An authentication error occurred with
your stored FlashCopy Manager
FMF0153I Performance stats: seconds seconds spent password.
in function
Explanation: You were unable to log on to the
Explanation: The indicated number of seconds were FlashCopy Manager server due an authentication error.
spent the named function.
System action: Processing stops.
System action: Processing continues.
User response: The stored FlashCopy Manager
User response: None password may have become corrupted. Contact your
FlashCopy Manager server administrator.

FMF0154E The IBM Tivoli Storage Manager

application client cannot work with the FMF0161E Authentication error. The password
version of the FlashCopy Manager API entered is not valid. You are not logged
you have installed. Please install version on to the FlashCopy Manager server.
version.release.level or greater.
Explanation: An incorrect password was entered.
Explanation: The version of the FlashCopy Manager
System action: Processing stops.
API currently installed on the system is older than the
version used to build the IBM Tivoli Storage Manager User response: Enter the correct FlashCopy Manager
application client. password and try again.
System action: Processing ends.
FMF0162E The passwords entered do not match.
User response: Install a version of the FlashCopy
Please enter them again.
Manager API at or later than the indicated level. A
copy is distributed with the IBM Tivoli Storage Explanation: An incorrect password was entered.
Manager application client.
System action: Processing stops.
User response: Enter the passwords again.
FMF0155E The IBM Tivoli Storage Manager
application client cannot work with the
release of FlashCopy Manager API you FMF0163E The directory path needs to be
have installed. Please install release fully-qualified.
version.release.l evel or greater.
Explanation: The /intopath option was specified
Explanation: The release of the FlashCopy Manager without a fully-qualified path.
API currently installed on the system is older than the
release used to build the IBM Tivoli Storage Manager System action: Processing stops.
application client. User response: Enter the command again and specify
System action: Processing ends. a fully-qualified path in the /intopath option.

User response: Install a release of the FlashCopy

Manager API at or later than the indicated level. A FMF0167E The fully-qualified file name is too
copy is distributed with the IBM Tivoli Storage long.
Manager application client. Explanation: An attempt was made to use a
fully-qualified file name that was too long. This
FMF0156E Could not load the FlashCopy Manager attempt failed.
API. System action: Processing ends.
Explanation: The FlashCopy Manager API could not User response: None
be loaded.
System action: Processing ends. FMF0200E File (filename) could not be opened for
User response: Ensure the FlashCopy Manager API is reading.
correctly installed. Run the IBM Tivoli Storage Manager Explanation: An attempt was made to open a file for
application client with the /TRACEFLAGS=API reading. This attempt failed.
/TRACEFILE=filename options and view the tracefile
to determine why it could not be loaded. Another System action: Processing ends.
possible cause is that the TSMAPI.DLL does not exist in User response: None
the system directory. Re-install the FlashCopy Manager
API, if this is the case.

Chapter 3. FMF messages 183

FMF0201E • FMF0213E

FMF0201E File (filename) could not be opened for FMF0208E There is not enough disk space for the
writing. operation attempted.
Explanation: An attempt was made to open a file for Explanation: An attempted operation required more
writing. This attempt failed. disk space than was available. The attempt failed.
System action: Processing ends. System action: Processing ends.
User response: None User response: None

FMF0202E Read failure on file (filename). FMF0209E The rename of file (filename1) to
(filename2) failed.
Explanation: An attempt was made to read from a
file. This attempt failed. Explanation: An attempt was made to rename a file.
This attempt failed.
System action: Processing ends.
System action: Processing ends.
User response: None
User response: None
FMF0203E Write failure on file (filename).
FMF0210E The FlashCopy Manager high level
Explanation: An attempt was made to write to a file.
qualifier is too long.
This attempt failed.
Explanation: An attempt was made to use a
System action: Processing ends.
FlashCopy Manager high level qualifier that was too
User response: None long. This attempt failed.
System action: Processing ends.
FMF0204E File (filename) could not be closed.
User response: None
Explanation: An attempt was made to close a file.
This attempt failed.
FMF0211E The FlashCopy Manager low level
System action: Processing ends. qualifier is too long.

User response: None Explanation: An attempt was made to use a

FlashCopy Manager low level qualifier that was too
long. This attempt failed.
FMF0205E File (filename) statistics could not be
obtained. System action: Processing ends.
Explanation: An attempt was made to obtain file User response: None
statistics. This attempt failed.
System action: Processing ends. FMF0212E The FlashCopy Manager filespace name
is too long.
User response: None
Explanation: An attempt was made to use a
FlashCopy Manager filespace name that was too long.
FMF0206E Directory (directory) could not be created. This attempt failed.
Explanation: An attempt was made to create a System action: Processing ends.
directory. This attempt failed.
User response: None
System action: Processing ends.
User response: None FMF0213E The maximum number of objects
allowed per FlashCopy Manager
FMF0207E Directory path (directorypath) is too long. transaction is too small.

Explanation: An attempt was made to use a directory Explanation: In order to maintain backup data
path that was too long. This attempt failed. integrity, multiple backup objects are sent to the
FlashCopy Manager server in a single transaction. The
System action: Processing ends. FlashCopy Manager server has indicated that the
User response: None maximum number of objects allowed per transaction is
less than the minimum required by the IBM Tivoli
Storage Manager application client.
System action: Processing ends.

184 IBM Tivoli Storage FlashCopy Manager: Messages

 FMF0214E • FMF0259E

User response: Increase the maximum number of

FMF0219E The FlashCopy Manager low level
objects allowed per transaction on the FlashCopy
qualifier is invalid.
Manager server and retry the operation.
Explanation: The low level qualifier name or directory
delimeter is invalid.
FMF0214E The backup object's management class
backup copy group does not exist. System action: Processing ends.
Explanation: The FlashCopy Manager server has User response: Check that the low level qualifier
indicated that the backup object's management class name length, characters, and directory delimeters are
backup copy group does not exist. valid.
System action: Processing ends.
FMF0256E The password in your FlashCopy
User response: Contact your FlashCopy Manager
Manager options file has expired. Please
server administrator.
change your password on the FlashCopy
Manager server using the 'change
FMF0215E All backup objects do not have the same password' command and then either
management class backup copy change or remove the password value in
destination. your options file.

Explanation: In order to maintain backup data Explanation: Your FlashCopy Manager password has
integrity, multiple backup objects are sent to the expired. You need to change your password.
FlashCopy Manager server within a single transaction.
System action: Processing ends.
All backup objects within a single transaction are
required to have the same management class backup User response: Obtain a new password for your
copy destinations. FlashCopy Manager server; node using the change
password command or by asking your FlashCopy
System action: Processing ends.
Manager Administrator to change your password.
User response: Contact your FlashCopy Manager
server administrator.
FMF0257E Your password has expired.
Explanation: Your FlashCopy Manager password has
FMF0216E Unable to obtain space information for
expired. A new password needs to be obtained.
volume (volumename).
System action: Processing ends.
Explanation: An attempt was made to obtain space
information for a volume. This attempt failed. User response: Obtain a new password for your
FlashCopy Manager node using the change password
System action: Processing ends.
command or by asking your FlashCopy Manager
User response: None Administrator to change your password.

FMF0217E The FlashCopy Manager filespace name FMF0258E You did not enter a valid password.
is invalid. Processing ends.

Explanation: The filespace name or directory Explanation: The password that was entered was not
delimeter is invalid. a valid password.

System action: Processing ends. System action: Processing ends.

User response: Check that the filespace name length, User response: Re-enter the command specifying a
characters, and directory delimeters are valid. valid password.

FMF0218E The FlashCopy Manager high level FMF0259E The password you entered for
qualifier is invalid. verification does not match the
password you entered for your new
Explanation: The high level qualifier name or password. Your password will not be
directory delimeter is invalid. changed.
System action: Processing ends. Explanation: The password you entered for
User response: Check that the high level qualifier verification of your new password does not match the
name length, characters, and directory delimeters are new password that was entered.
valid. System action: Processing ends.

Chapter 3. FMF messages 185

FMF0260I • FMF0301E

User response: Try again to change your password User response: It is possible that a default browser is
being sure to enter the same password for the new not defined for the system. This is okay. An attempt
password and for the verification password. will be made to use Microsoft Internet Explorer.

FMF0260I Password successfully changed. FMF0265E Could not find Internet Explorer.
Explanation: The change password command Explanation: An attempt was made to read the
completed successfully registry to determine where Microsoft's Internet
Explorer was installed. This attempt failed.
System action: Processing ends.
System action: Processing ends.
User response: None
User response: Make sure that the registry is set up
correctly for Internet Explorer.
FMF0261I There are no backups for the server
named servername.
FMF0266E Could not find the FlashCopy Manager
Explanation: There are no backups on the FlashCopy
HTML books.
Manager server for the specified server name.
Explanation: An attempt was made to read the
System action: Processing ends.
registry to determine where the Tivoli Storage Manager
User response: None books were installed. This attempt failed.
System action: Processing ends.
FMF0262E Errors occurred while processing the
User response: It may be necessary to reinstall the
VSS operation. Examine the Windows
application client code. This will ensure that the
Event Logs and DSMERROR.LOG for
registry entries are set up correctly.
additional details.
Explanation: While attempting to process a VSS
FMF0267E The verify password entered does not
operation, an unexpected error occurred.
match the new password entered.
System action: Processing ends.
Explanation: The verify password does not match the
User response: Attempt to determine the source of the new password.
error by examining the FCM for Windows log file, the
System action: Processing ends.
FCM Client error log file (DSMERROR.LOG), the
Windows Application Event Log, the Windows System User response: Retry the command with a matching
Event Log, and the VSS provider log file, if applicable. verify password.
Additional instructions for Windows VSS operations
are located in the TSM Problem Determination Guide.
FMF0292E An unknown error has been detected. rc
Correct the problem and retry the operation. If this
= rc
error persists, contact your service representative.
Explanation: An error occured without an error
message. The return code, rc, is displayed.
FMF0263E Failed to start Web browser with a
return code of returncode. System action: Processing ends.
Explanation: An attempt was made to start the web User response: Retry the operation. If this error
browser to view the FCM HTML b ook. This attempt persists, contact your service representative.
failed.
System action: Processing ends. FMF0300E Invalid restore type.
User response: Start your web browser manually and Explanation: The type of restore requested is invalid.
point it to bookfrm.htm in the agent htm directory.
System action: Processing ends.

FMF0264I Could not find the default browser User response: Re-enter the command specifying a
defined. An attempt will be made to use valid restore type.
Microsoft Internet Explorer.
Explanation: An attempt was made to read the FMF0301E Invalid backup type.
registry to determine the default browser. However, a Explanation: The type of backup requested is invalid.
default browser is not defined. A determination will be
made where Microsoft Internet Explorer is installed. System action: Processing ends.

System action: Processing continues.

186 IBM Tivoli Storage FlashCopy Manager: Messages

 FMF0351E • FMF0488E

User response: Re-enter the command specifying a

FMF0383E Specifying the trace file 'link' as a
valid backup type.
symbolic link is not allowed.
Explanation: Trace file 'linkname' cannot be a symbolic
FMF0351E Invalid trace keyword - 'keyword'
link.
Explanation: A TRACEFLAG option in the user
System action: The symbolic link 'linkname' is deleted,
configuration file or on the command line is incorrect.
the trace file is recreated, and processing stops.
System action: Client program did not initialize or
User response: Specify the trace file location with the
tracing was not enabled in the applet.
'tracefile' option.
User response: Correct the value.
FMF0384E Symbolic link 'linkname' to 'target' was
FMF0357E Unable to open trace output file successfully deleted.
file-name.
Explanation: Log 'linkname' cannot be a symbolic link.
Explanation: A TRACEFILE option in the user
System action: The symbolic link 'linkname' is deleted,
configuration file or on the command line used a
the log is recreated, and processing stops.
directory path and file-name combination to which you
do not have write access. User response: Check the location of the new file. To
specify the location of log files, refer to the user's
System action: Client program did not initialize.
manual for the 'errorlogname' option, the
User response: Change the TRACEFILE value so that 'schedlogname' option, and the 'DSM_LOG'
it is a location to which you have write access. environmental variable.

FMF0366E Unable to close trace output file FMF0385E Unable to delete symbolic link 'link'.
file-name.
Explanation: Log 'linkname' cannot be a symbolic link.
Explanation: An error occurred during the closing of a
System action: Processing stops.
trace output file-name (for example, not enough disk
space). User response: Delete the symbolic link 'linkname'.
System action: Processing continues.
FMF0476E program-name: cannot open file file-spec:
User response: Check the options.doc file for a
error.
description of possible causes of the error, or see your
system administrator. Explanation: FCM cannot open the file.
System action: FCM cannot complete the requested
FMF0367E Unable to write to trace file tracefile. operation.
Tracing disabled.
User response: Retry the operation. If the problem
Explanation: An error occurred when writing to the continues, check with your system administrator.
specified tracefile.
System action: Tracing is disabled. Processing FMF0487E Specifying the error log 'link' as a
continues. symbolic link is not allowed.
User response: Ensure the device that the tracefile Explanation: Error log 'linkname' cannot be a symbolic
access is available and has sufficient space for the link.
tracefile. Retry the command.
System action: The symbolic link 'linkname' is deleted,
the error log is recreated, and processing stops.
FMF0368E Invalid trace file name (name too long).
User response: Check the location of the new error
Explanation: A TRACEFILE option in the preferences log. To specify the location of the error logs, refer to the
files used a file name that is too long. user's manual for the 'errorlogname' option and
'DSM_LOG' environmental variable.
System action: Client program did not initialize.
User response: Change the file name used as the
FMF0488E Initialization functions cannot open the
TRACEFILE so that it is equal to or less than 255
error log: log-name. errno = errno-value,
characters in length.
Explanation: The file log-name could not be opened
during initialization. The system set the error code
errno-value. If the reason given is "access denied," the

Chapter 3. FMF messages 187

FMF0495E • FMF0517I

current user does not have permission to write to the

FMF0498I count log records processed.
log in the directory specified. It is also possible that no
space is available at the given log location. Explanation: This is just a progress report to let you
know the process is still ongoing.
System action: Processing terminates.
System action: Transition processing continues.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory into which the User response: None.
current user can write. You may also use the
ERRORLOGNAME option to specify a file to which the
FMF0501E Invalid Proxy Configuration Detected:
current has write permission.
Target Node 'targetnode' is not listed as a
valid node to proxy to for Node Name
FMF0495E Failure writing to a Tivoli Storage 'nodename'.
Manager log or log-related file: file-name,
Explanation: The proxy node configuration on the
errno = errno-value, reason
FCM Server is not correct to support this VSS
Explanation: A failure was encountered when writing operation.
to one of the log files or a related file named file-name.
System action: The VSS operation stops.
The system set the error code errno-value. reason is the
system explanation of that error code. Among other User response: Contact the FCM Server administrator
things, it is possible that no space is available at the to have the correct FCM Server GRANT PROXY
given log location. commands issued to enable proxy authority for the
nodes. If the error persists, contact your service
System action: Processing terminates.
representative.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory with adequate
FMF0515E Invalid DSMAGENT Node
space to write the log data.
configuration found for node
'dsmagentnode'.
FMF0496I FCM is converting the log-file from
Explanation: The DSMAGENT Node specified is not
continuous (pruning) mode to wrapping
configured properly.
mode. This process may take several
minutes. System action: The VSS operation stops.
Explanation: The log-file was previously in continouos User response: Verify that the DSMAGENT Node
mode where the only size control was through the use specified is correct and that the Client Acceptor
of ERRORLOGRETENTION or Daemon (CAD) is running for the DSMAGENT Node.
SCHEDLOGRETENTION option. This is the first If the error persists, contact your service representative.
occasion where ERRORLOGMAX or SCHEDLOGMAX
is specified for this log, so its format must be changed
and old data saved. FMF0516I The Windows console event handler
received a 'event' console event.
System action: Transition processing continues.
Explanation: A console event was received by one of
User response: None. the IBM Tivoli Storage Manager processes or programs.
The following events can be recevied:
FMF0497I FCM is converting the log-file from v Ctrl-C - This indicates either the user entered the
wrapping mode to continuous (pruning) ctrl-c sequence or that one of the Windows services
mode. This process may take several was stopped.
minutes. System action: None.
Explanation: The log-file was previously in wrapping User response: None.
mode where the size control was through the use of the
ERRORLOGMAX or SCHEDLOGMAX option. This is
the first occasion where ERRORLOGMAX or FMF0517I An unexpected error was encountered.
SCHEDLOGMAX is not specified for this log, so its FCM function name : function-name FCM
format must be changed and old data saved. function : function-desc FCM return code
: TSM-rc FCM file : file-name (line-number)
System action: Transition processing continues.
Explanation: None.
User response: None.
System action: Processing stops.
User response: Contact the FCM administrator with
the information provided in this message.

188 IBM Tivoli Storage FlashCopy Manager: Messages

 FMF0518E • FMF0571E

user id is performing pruning at the same time.

FMF0518E Backups selected for restore must have
the same backup location (TSM or System action: Pruning stops, processing continues.
LOCAL).
User response: Set the DSM_LOG (or DSMI_LOG)
Explanation: A VSS restore operation was submitted environment variable to a directory into which the
that specified multiple backup objects. The backup current user can write.
objects chosen had different backup locations. This is
not allowed. All backup objects submitted in the same
VSS restore operation must have the same backup FMF0522E DIAG:
location, either TSM or LOCAL, but not both. Explanation: The message text is provided for
System action: The VSS restore operation stops. diagnostic purposes and is meant to provide
information to IBM support in problem determination.
User response: Retry the VSS restore operation
specifying one backup object at a time. System action: None.
User response: None.
FMF0519E The VSS operation failed with rc =
returncode. FMF0524S Error 'errtxt' (errno=errno) occurred
Explanation: There was a failure when FCM trying to write to audit log 'file-name'.
performed the VSS operation. The audit log function is disabled.

System action: The VSS operation stops. Explanation: There was an error encountered writing
to the audit log (for example, there is not enough space
User response: Verify that the FCM Client Acceptor on the disk).
Daemon (CAD) is installed, configured, and running
properly on the machine. Retry the operation. If the System action: Audit logging is disabled for the rest
error persists, contact your service representative. of the operation. The return code for the operation is
set to 12 to indicate that the contents of the audit log
are incomplete.
FMF0520E Failed to connect to Local DSMAGENT
Node 'localdsmagentnode' at address:port User response: If this is an out of space condition
'address:portnumber'. Verify that the TSM either free up space on the volume or try to write the
Client Acceptor Daemon (CAD) is audit log to a volume with more space.
installed, configured, and running
properly. FMF0555E Invalid number of snapshots:
Explanation: An attempt was made to connect to the Explanation:
TSM Client Acceptor Daemon (CAD) running on the
local machine. A communication error occurred when System action: Policy was not created.
this connection was attempted. User response: Specify a number in the range: range:
System action: The operation stops. 1...9999 or NOLimit

User response: In order to perform VSS operations,

you must have a TSM Client Acceptor Daemon (CAD) FMF0556E Invalid number of days:
and a TSM Remote Client Agent Service (DSMAGENT) Explanation:
installed and configured properly. In addition, the TSM
Client Acceptor Daemon (CAD) must be running. System action: The Policy was not created.
Verify that the TSM Client Acceptor Daemon (CAD) is User response: Specify a number in the range: range:
installed, configured, and running properly on the local 0...9999 or NOLimit
machine. If the error persists, contact your service
representative.
FMF0571E The specified policy was not found:
'policy'
FMF0521E Pruning functions cannot open one of
the Tivoli Storage Manager prune files: Explanation:
log-name. errno = errno-value,
System action:
Explanation: The file "log-name" could not be opened
User response: Please make sure that the specified
during pruning. The system set the error code
policy exists.
errno-value. If the reason given is "access denied," the
current user does not have permission to write to the
file in the directory specified. It is also possible that no
space is available at the given file location or another
Tivoli Storager Manager process started by different

Chapter 3. FMF messages 189

FMF0572E • FMF0588E

FMF0572E The specified policy already exists: FMF0583E Invalid name of policy specified. Valid
'policy' input characters include alphanumeric
charaters and underscore.
Explanation:
Explanation:
System action: Policy was not created.
System action: Policy was not created.
User response: Enter a different name for the policy.
User response: Please specify a valid name.
FMF0573E The specified policy could not be
updated: 'policy' FMF0585E Unable to connect to the TSM Client
Acceptor Daemon (CAD).
Explanation: This is due to a problem in virtual server
database. Explanation: Possible causes of this message include:
The TSM Client Acceptor Daemon (CAD) is not
System action:
running. The VSSALTSTAGINGDIR option setting in
User response: Make sure that FCM is configured the TDP option file is not set to the same value as the
correctly. VSSALTSTAGINGDIR option setting in the IBM Tivoli
Storage Manager Remote Client Agent Service
(DSMAGENT) option file. They must be set to the same
FMF0574E The specified policy could not be value for successful TDP operations.
deleted: 'policy'
System action: The VSS operation stops.
Explanation: This is due to a problem in virtual server
database. User response: Ensure that the TSM Client Acceptor
Daemon (CAD) is running. Ensure that the
System action: VSSALTSTAGINGDIR option setting in the TDP option
User response: Make sure that FCM is configured file is set to the same value as the
correctly. VSSALTSTAGINGDIR option setting in the IBM Tivoli
Storage Manager Remote Client Agent Service
(DSMAGENT) option file. After correcting the
FMF0575E The specified policy could not be VSSALTSTAGINGDIR option inconsistency, retry the
created: 'policy' TDP operation.
Explanation: This is due to a problem in virtual server
database. FMF0588E The value for the BACKUPDESTination
System action: option is not allowed. IBM Tivoli
Storage Manager is only licensed to run
User response: Make sure that FCM is configured data protection operations to a
correctly. FlashCopy Manager server. It is not
licensed to backup or to restore locally
FMF0576I There were no items found. managed snapshots.

Explanation: The query completed successfully, but no Explanation: The value for the configuration option is
results were found. not allowed. The only allowed value is TSM. IBM
Tivoli Storage Manager is only licensed to run data
System action: None. protection operations to a FlashCopy Manager server. It
is not licensed to backup or to restore locally managed
User response: Change the specified search criteria.
snapshots.
System action: Processing ends.
FMF0581E Volume volume-name could not be
locked. User response: Set the backup destination to TSM. In
order to create and restore local VSS backups it is
Explanation: The system call to lock the volume
required to use and install a fully-featured valid license
failed.
or to purchase an upgrade, and install Tivoli Storage
System action: Processing stopped. FlashCopy Manager. If you use IBM Tivoli Storage
Manager for Copy Services it is also required to
User response: Please verify that no other application
purchase and install IBM Tivoli Storage Manager for
is accessing the volume. During restore of an image
Copy Services.
FCM must have exclusive use of the volume.

190 IBM Tivoli Storage FlashCopy Manager: Messages

 FMF0589E • FMF0599E

User response: In order to perform offloaded VSS

FMF0589E You are not allowed to set
backups install a valid fully-featured license. If you use
REMOTEDSMAGentnode option. IBM
IBM Tivoli Storage Manager for Copy Services it is also
Tivoli Storage Manager is not licensed
required to purchase and install IBM Tivoli Storage
to perform offloaded VSS backups.
Manager for Copy Services. Contact your service
Explanation: The REMOTEDSMAGentnode option is representative to find out purchase details.
used to perform offloaded VSS backups.
System action: The operation stops. FMF0594E You cannot perform offloaded VSS
backups in TSM Server independent
User response: In order to perform offloaded VSS
environment.
backups install a valid fully-featured license. If you use
IBM Tivoli Storage Manager for Copy Services it is also Explanation: OFFLOAD option is not available in
required to purchase and install IBM Tivoli Storage TSM Server independent environment.
Manager for Copy Services. Contact your service
System action: The operation stops.
representative to find out purchase details.
User response: In order to perform offloaded VSS
backups you have to configure Tivoli Storage
FMF0590E A Data Protection communication error
FlashCopy Manager to manage snapshot backups using
with the Tivoli Storage Manager server
a Tivoli Storage Manager server. To do this you can use
has occurred.
Tivoli Storage Manager configuration wizard.
Explanation: Communications with the Tivoli Data
Protection server has been lost.
FMF0595E The options file 'optfile' does not exist. It
System action: The operation stops. is required for proper operation.
User response: Correct the TCP/IP communications Explanation: The specified TSM API options file could
error with the Tivoli Storage Manager server and retry not be found. It is required in order to complete the
the operation. command.
System action: Processing ends.
FMF0591I Data Protection communications with
User response: Make sure to complete FlashCopy
the Tivoli Storage Manager server has
Manager configuration and try the operation again.
been successfully recovered.
Explanation: Communications with the Tivoli Data
FMF0598E The application cannot run in safe
Protection server has been successfully recovered.
mode.
System action: None.
Explanation: The application requires either Services
User response: Continue with normal operations. or Drivers that are not available when running in safe
mode.
FMF0592E The Data Protection TCP/IP session System action: The application processing stops.
with the Tivoli Storage Manager server
User response: Restart the system using the normal
was canceled.
startup. When the system is started, run the
Explanation: The Data Protection TCP/IP session with application.
the Tivoli Storage Manager server was cancelled.
System action: The operation stops. FMF0599E The application cannot establish a
remote powershell connection.
User response: Correct the reason the Tivoli Storage
Manager server administrator cancelled the session and Explanation: The application attempted to establish a
retry the operation. remote powershell connection. The operation failed.
System action: The application processing stops.
FMF0593E IBM Tivoli Storage Manager is not
User response: Verify you are using the correct
licensed to perform offloaded VSS
credentials. For more information, see the Microsoft
backups.
about_Remote_Troubleshooting Help topic.
Explanation: Currently installed license does not allow
to perform offloaded VSS backups. In order to use this
feature it is necessary to install a valid fully-featured
license.
System action: The operation stops.

Chapter 3. FMF messages 191

FMF0601E • FMF5976E

FMF0601E There is a problem that causes FMF5817E The volume/mount point specified in
processing to stop. To identify the the INTO option is not valid.
source of the problem and the solution,
Explanation: The INTO option was specified with an
look for details in the service level trace
invalid value.
file.
System action: The restore operation is canceled.
Explanation: This problem occurs when either the
local or remote Powershell cmdlet or script reports an User response: Retry the VSS restore INTO operation
error. Details about the error are not available until specifying a valid INTO value.
more trace file information is analyzed.
System action: Application processing stops. FMF5945E The following mount point is used as a
mapped network share for 'share-name':
User response: To identify the problem, look for
'drive-letter'.
information in the service level trace files. For more
information about viewing trace files, see the Explanation: When a backup is mounted over a
Troubleshooting section of the technical documentation mapped network drive letter, the files on the mounted
provided with the software. snapshot cannot be accessed using that drive letter.
System action: The operation stops.
FMF5814E Invalid command. FCM for Windows
does not support OFFLOAD with the User response: Specify an unassigned drive letter or
combination specified for backup mount point directory.
destination and version of Windows.
Explanation: The OFFLOAD option was specified FMF5956I The logfile log file could not be pruned.
with an unsupported backup destination. FCM for Processing will continue.
Windows only supports offload with a backup Explanation: An attempt to prune the log was
destination of TSM, or if running on a Windows Server unsuccessful.
2008 or later, backup destination TSM or BOTH.
System action: Processing continues.
System action: The backup operation is canceled.
User response: The log file may not exist. If the log
User response: Retry the VSS offloaded backup file exists, view the log for indications of possible
operation specifying a valid backup destination. problems.

FMF5815E Invalid command. FCM for Windows FMF5957I The logfile log file was pruned
does not support INTO option with the successfully.
specified backup destination of LOCAL.
Explanation: The log file mentioned pruned
Explanation: The INTO option was specified with an successfully.
unsupported backup destination. FCM for Windows
only supports INTO with a backup destination of TSM. System action: Processing continues.

System action: The restore operation is canceled. User response: None.

User response: Retry the VSS restore into operation

specifying a valid backup destination. FMF5970I The operation was canceled by the user.
Explanation: The user has requested that the
FMF5816E Invalid command. The INTO option operation be canceled.
only supports one restore component System action: Processing ends.
per command.
User response: None
Explanation: The INTO option was specified with
multiple restore components. FCM for Windows only
supports INTO with a single restore component. FMF5976E An error was encountered with
FlashCopy Manager API initialization,
System action: The restore operation is canceled. rc = returncode. Examine the dsierror.log
User response: Retry the VSS restore into operation for more information or determine if the
specifying only one restore component. FCM API is installed properly.
Explanation: An attempt was made to run setup for
the FCM API. However, errors were encountered.
System action: Processing continues.

192 IBM Tivoli Storage FlashCopy Manager: Messages

 FMF5989E • FMF6018E

User response: Examine the dsierror.log file to

FMF6014E Unmount backup command failed.
determine the problem. If this file does not exist, it is
Please refer to dsmerror.log for further
possible that the FCM API is not installed properly. If
details.
this is the case, reinstall the FCM API and try running
the command again. Explanation: The unmount backup command failed.
The backup specified may not be mounted.
FMF5989E No components were found that match System action: Processing stops
the criteria specified.
User response: Check to make sure that the backup
Explanation: None of the items specified match the specified is mounted.
components found on this machine.
System action: Processing ends. FMF6015E Invalid component list. Qualified and
non-qualified objects can not be
User response: Correct the component specification
specified on the same command.
and try the operation again.
Explanation: A command was specified with a
component list that contained qualifed and
FMF5990E There were no backups found that
non-qualified objects. This is not valid.
match the criteria specified.
System action: The operation stops.
Explanation: There are no backups found on the
FlashCopy Manager server for the specified criteria. User response: Enter the command again with a
component list that contains all qualified or all
System action: Processing ends.
non-qualified objects.
User response: Correct the backup specification and
try the operation again.
FMF6016E Conflicting arguments found. Point in
Time options can not be specified on
FMF6011E The configuration file specified cannot the same command as qualified objects.
be found.
Explanation: A command was specified with the point
Explanation: The file specified in the /configfile in time option and a component list that contained one
parameter cannot be found. or more qualifed objects. This is not valid.

System action: Processing stops. System action: The operation stops.

User response: Ensure the correct file name is User response: Correct the syntax and retry the
specified. operation.

FMF6012I The configuration file specified cannot FMF6017E An invalid duplicate object, 'object', was
be found. Creating configuration file found in the component list. This is not
'configfile' with default settings. valid on a RESTORE operation.

Explanation: The file specified in the /configfile Explanation: A command was specified with a
parameter cannot be found. The file specified gets component list that contained duplicate objects.
created with default settings. RESTORE operations do not support this.

System action: Processing continues. System action: The operation stops.

User response: None User response: Correct the syntax and retry the
operation.

FMF6013E Mount backup command failed. The

mount point and or backup specified is FMF6018E FlashCopy Manager was not able to
invalid. Please refer to dsmerror.log for obtain VSS component information.
further details.
Explanation: An error occurred when attempting to
Explanation: The mount backup command failed. The enumerate the VSS components for the operation. This
backup specified may already be mounted and or the could be the result of a VSS Requestor or VSS Writer
drive to map to may already be in used error.

System action: Processing stops System action: The operation stops.

User response: Check to make sure that the backup User response: Stop the TSM Remote Client Agent
specified is not already mounted and that the drive to Windows service then stop and restart the TSM Client
map to is available. Acceptor Windows service. After that, retry the

Chapter 3. FMF messages 193

FMF6019E • FMF6031E

operation. If the problem persists, refer to the store your password.

dsmerror.log file, the dsierror.log file, and/or the
Explanation: The PASSWORDACCESS option is set to
Windows Event Log for further details on the error.
generate in the client options file. However, no
password is stored. An initial password needs to be
FMF6019E In the component list that is specified, stored.
the following object is not valid: 'object'.
System action: Processing ends.
Explanation: The command that is entered includes a
User response: Invoke the command again using the
component list. The list of components contains one or
-TSMPassword option. Any subsequent commands
more invalid objects. For example, when entering a
should now complete without specifying a password.
BACKUP or RESTORE command, if the component list
includes a volume or mount point that is not valid or is
not eligible for back up, this message is displayed. In FMF6030E The FlashCopy Manager VSS Fast
addition, the GUID volume name cannot be specified. Restore operation failed to restore the
For RESTORE, MOUNT BACKUP, or DELETE volume. Examine the FCMFSFR.LOG
BACKUP commands, this message is displayed if the file for more details on the failure.
component list contains a backup specification that is
not found in the backup inventory. Explanation: FlashCopy Manager attempted to
perform a file-level copy of all files from the snapshot
System action: The operation stops. backup to the original source volume. There was a
failure during the file-level copy operation. This can be
User response: Verify the correct syntax is used when
caused by locked files or files that are in use by the
entering the command. If the message is displayed
operating system.
again, verify the volume and mount point names are
correctly identified. A misspelling can trigger this System action: Processing ends.
message.
User response: Examine the FCMFSFR.LOG file that is
located in the FlashCopy Manager installation directory
FMF6020I The configuration file cannot be read. for specific details on the error. If you are not able to
Creating configuration file 'configfile' perform the VSS Fast Restore operation successfully,
with default settings. access the backup using the FCMCLI MOUNT
command or the equivalent function in the MMC
Explanation: The file specified gets created with
interface. After mounting the backup, use Windows
default settings.
Explorer or other operating system commands to copy
System action: Processing continues. the needed files.
User response: None
FMF6031E The option /BACKUPDESTINATION is
invalid when performing data protection
FMF6021E The value for the preference preference is
operations using a FlashCopy Manager
not valid. See the FCMCLI HELP
virtual server.
UPDATE/INSERT output or the User's
Guide for valid command parameters. Explanation: Data protection commands default to
/BACKUPDESTINATION=LOCAL when performed
Explanation: The preference being set is not valid.
against a FlashCopy Manager virtual server. The
System action: Processing ends. FlashCopy Manager supports no other values for this
option. As a result it is no longer necessary to specify
User response: You can either run the command this parameter. For compatibility with other products
"fcmcli help update" or view the User's Guide for valid values for /BACKUPDESTINATION can be specified
UPDATE command parameters. as long as this is set to its only valid value. This means
that /BACKUPDESTINATION option can only be set
FMF6026E PASSWORDACCESS is Generate. Either to LOCAL value.
the stored password is incorrect or there System action: The operation stops.
is no stored password. If you do not
have a stored password, use the User response: Retry the command removing the
-TSMPassword=xxx option to set and /BACKUPDESTINATION option.

194 IBM Tivoli Storage FlashCopy Manager: Messages

Chapter 4. FMX messages
Messages with prefix FMX are issued by the IBM Tivoli Storage FlashCopy
Manager for Microsoft Exchange Server. Tivoli Storage FlashCopy Manager V4.1.1
FMX messages are listed in ascending numerical order. The complete message is
documented, including message ID, message text, explanation, system action, and
user response.

FMX0003S An internal processing error has FMX0055E Write failure on license file (licensefile).
occurred.
Explanation: An attempt to write to the license file
Explanation: An internal processing error has failed.
occurred.
System action: Processing ends.
System action: Processing ends.
User response: Make sure enough space exists on the
User response: Retry the operation. If this error workstation to write to the license file. If enough space
persists, contact your service representative. exists, run the command again.

FMX0004E An unknown error has been detected. FMX0056E Data in the license file (licensefile) is not
in a valid format.
Explanation: An internal processing error has
occurred that prevents the generation of a message for Explanation: An attempt to read information from the
a return code. license file failed.
System action: Processing continues. System action: Processing ends.
User response: Retry the operation. If this error User response: Install the product again.
persists, contact your service representative.
FMX0057E The checksum in the license file
FMX0005E Out of memory. Stop other processes (licensefile) does not match the license
and try the operation again. string text.
Explanation: The machine has run out of memory. Explanation: An attempt was made to read
information from the license file. The checksum was
System action: Processing continues.
not valid so it appears that the license file is not at the
User response: Close unnecessary processes and try correct level.
the operation again.
System action: Processing ends.
User response: Reinstall the product.
FMX0053E License file (licensefile) could not be
opened.
FMX0058E The 'Try and Buy' license has expired.
Explanation: An attempt to read from the license file
failed. Explanation: This 'Try and Buy' license that was
detected has expired.
System action: Processing ends.
System action: Processing ends.
User response: Install the product again. This ensures
that the correct license file is installed. User response: This product is no longer valid for use.
A valid license must be obtained before running the
product.
FMX0054E Read failure on license file (licensefile).
Explanation: An attempt was made to read from the
FMX0100E Incomplete command:
license file. This attempt failed.
Explanation: This message displays the incomplete
System action: Processing ends.
command that was entered.
User response: Reinstall the product. This will ensure
System action: Processing ends.
that the correct license file is installed.
User response: Re-enter the complete command.

© Copyright IBM Corp. 1995, 2014 195

FMX0101E • FMX0152I

FMX0101E Invalid argument: FMX0133W Could not locate installation directory.

Attempting to continue...
Explanation: This message displays the command that
was entered, up to and including the invalid command Explanation: An attempt was made to read the
or option argument that was detected. registry to determine where the Tivoli Data Protection
application client was installed. This attempt failed.
System action: Processing ends.
System action: Processing will continue with the
User response: Re-enter the command specifying a
command entered.
valid argument for the command or option.
User response: There should be other messages along
with this one. Refer to the other messages to determine
FMX0102E Invalid command:
the problem. If the problem can not be determined, it
Explanation: This message displays the invalid may be necessary to reinstall the application client
command that was entered. code. This will ensure that the registry entries are set
up correctly.
System action: Processing ends.
User response: Re-enter a valid command. FMX0134W Could not locate log directory.
Processing will continue...
FMX0103E Invalid option for the specified Explanation: An attempt was made to read the
command: registry to determine where the Tivoli Data Protection
Explanation: This message displays the command that application client log is located. This attempt failed.
was entered, up to and including the option that was System action: Processing will continue with the
detected as invalid for the command. command entered.
System action: Processing ends. User response: There should be other messages along
User response: Re-enter the command specifying valid with this one. Refer to the other messages to determine
command options. the problem. If the problem can not be determined, it
may be necessary to reinstall the application client
code. This will ensure that the registry entries are set
FMX0104E Invalid option: up correctly.
Explanation: This message displays the command that
was entered, up to and including the invalid option FMX0150I Operation canceled by user.
that was detected.
Explanation: The user has requested that the Data
System action: Processing ends. Protection for Microsoft Exchange Server application
User response: Re-enter the command specifying valid client end by entering ctrl-C.
command options. System action: Processing ends.
User response: None
FMX0105E Missing argument:
Explanation: This message displays the command that FMX0151E Errors occurred while processing the
was entered, up to and including the command or request.
option whose required argument is missing.
Explanation: Attempting to process the request
System action: Processing ends. entered, an error occurred.
User response: Re-enter the command specifying a System action: Processing ends.
valid argument for the command or option.
User response: Attempt to determine the source of the
errors from viewing the log file. Correct the problems
FMX0132W Tracing could not be started. Processing and try running the command again.
will continue.
Explanation: A problem prevented tracing from FMX0152I Performance stats: seconds seconds spent
beginning. in apicall API calls
System action: Processing will continue with the Explanation: The indicated number of seconds were
command entered. spent making API calls for the indicated system.
User response: Refer to the other messages that System action: Processing continues.
display with this message to determine the problem.
User response: None

196 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX0153I • FMX0200E

FMX0153I Performance stats: seconds seconds spent FMX0160E An authentication error occurred with
in function your stored Tivoli Storage Manager
password.
Explanation: The indicated number of seconds were
spent the named function. Explanation: You were unable to log on to the Tivoli
Storage Manager server due an authentication error.
System action: Processing continues.
System action: Processing stops.
User response: None
User response: The stored Tivoli Storage Manager
password may have become corrupted. Contact your
FMX0154E The Data Protection for Microsoft
Tivoli Storage Manager server administrator.
Exchange Server application client
cannot work with the version of the
Tivoli Storage Manager API you have FMX0161E Authentication error. The password
installed. Please install version entered is not valid. You are not logged
version.release.level or greater. on to the Tivoli Storage Manager server.
Explanation: The version of the Tivoli Storage Explanation: An incorrect password was entered.
Manager API currently installed on the system is older
System action: Processing stops.
than the version used to build the Data Protection for
Microsoft Exchange Server application client. User response: Enter the correct Tivoli Storage
Manager password and try again.
System action: Processing ends.
User response: Install a version of the Tivoli Storage
FMX0162E The passwords entered do not match.
Manager API at or later than the indicated level. A
Please enter them again.
copy is distributed with the Data Protection for
Microsoft Exchange Server application client. Explanation: An incorrect password was entered.
System action: Processing stops.
FMX0155E The Data Protection for Microsoft
Exchange Server application client User response: Enter the passwords again.
cannot work with the release of Tivoli
Storage Manager API you have FMX0163E The directory path needs to be
installed. Please install release fully-qualified.
version.release.l evel or greater.
Explanation: The /intopath option was specified
Explanation: The release of the Tivoli Storage without a fully-qualified path.
Manager API currently installed on the system is older
than the release used to build the Data Protection for System action: Processing stops.
Microsoft Exchange Server application client. User response: Enter the command again and specify
System action: Processing ends. a fully-qualified path in the /intopath option.

User response: Install a release of the Tivoli Storage

Manager API at or later than the indicated level. A FMX0167E The fully-qualified file name is too
copy is distributed with the Data Protection for long.
Microsoft Exchange Server application client. Explanation: An attempt was made to use a
fully-qualified file name that was too long. This
FMX0156E Could not load the Tivoli Storage attempt failed.
Manager API. System action: Processing ends.
Explanation: The Tivoli Storage Manager API could User response: None
not be loaded.
System action: Processing ends. FMX0200E File (filename) could not be opened for
User response: Ensure the Tivoli Storage Manager API reading.
is correctly installed. Run the Data Protection for Explanation: An attempt was made to open a file for
Microsoft Exchange Server application client with the reading. This attempt failed.
/TRACEFLAGS=API /TRACEFILE=filename options
and view the tracefile to determine why it could not be System action: Processing ends.
loaded. Another possible cause is that the TSMAPI.DLL User response: None
does not exist in the system directory. Re-install the
Tivoli Storage Manager API, if this is the case.

Chapter 4. FMX messages 197

FMX0201E • FMX0213E

FMX0201E File (filename) could not be opened for FMX0208E There is not enough disk space for the
writing. operation attempted.
Explanation: An attempt was made to open a file for Explanation: An attempted operation required more
writing. This attempt failed. disk space than was available. The attempt failed.
System action: Processing ends. System action: Processing ends.
User response: None User response: None

FMX0202E Read failure on file (filename). FMX0209E The rename of file (filename1) to
(filename2) failed.
Explanation: An attempt was made to read from a
file. This attempt failed. Explanation: An attempt was made to rename a file.
This attempt failed.
System action: Processing ends.
System action: Processing ends.
User response: None
User response: None
FMX0203E Write failure on file (filename).
FMX0210E The Tivoli Storage Manager high level
Explanation: An attempt was made to write to a file.
qualifier is too long.
This attempt failed.
Explanation: An attempt was made to use a Tivoli
System action: Processing ends.
Storage Manager high level qualifier that was too long.
User response: None This attempt failed.
System action: Processing ends.
FMX0204E File (filename) could not be closed.
User response: None
Explanation: An attempt was made to close a file.
This attempt failed.
FMX0211E The Tivoli Storage Manager low level
System action: Processing ends. qualifier is too long.

User response: None Explanation: An attempt was made to use a Tivoli

Storage Manager low level qualifier that was too long.
This attempt failed.
FMX0205E File (filename) statistics could not be
obtained. System action: Processing ends.
Explanation: An attempt was made to obtain file User response: None
statistics. This attempt failed.
System action: Processing ends. FMX0212E The Tivoli Storage Manager filespace
name is too long.
User response: None
Explanation: An attempt was made to use a Tivoli
Storage Manager filespace name that was too long. This
FMX0206E Directory (directory) could not be created. attempt failed.
Explanation: An attempt was made to create a System action: Processing ends.
directory. This attempt failed.
User response: None
System action: Processing ends.
User response: None FMX0213E The maximum number of objects
allowed per Tivoli Storage Manager
FMX0207E Directory path (directorypath) is too long. transaction is too small.

Explanation: An attempt was made to use a directory Explanation: In order to maintain backup data
path that was too long. This attempt failed. integrity, multiple backup objects are sent to the Tivoli
Storage Manager server in a single transaction. The
System action: Processing ends. Tivoli Storage Manager server has indicated that the
User response: None maximum number of objects allowed per transaction is
less than the minimum required by the Data Protection
for Microsoft Exchange Server application client.
System action: Processing ends.

198 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX0214E • FMX0259E

User response: Increase the maximum number of

FMX0219E The Tivoli Storage Manager low level
objects allowed per transaction on the Tivoli Storage
qualifier is invalid.
Manager server and retry the operation.
Explanation: The low level qualifier name or directory
delimeter is invalid.
FMX0214E The backup object's management class
backup copy group does not exist. System action: Processing ends.
Explanation: The Tivoli Storage Manager server has User response: Check that the low level qualifier
indicated that the backup object's management class name length, characters, and directory delimeters are
backup copy group does not exist. valid.
System action: Processing ends.
FMX0256E The password in your Tivoli Storage
User response: Contact your Tivoli Storage Manager
Manager options file has expired. Please
server administrator.
change your password on the Tivoli
Storage Manager server using the
FMX0215E All backup objects do not have the same 'change password' command and then
management class backup copy either change or remove the password
destination. value in your options file.

Explanation: In order to maintain backup data Explanation: Your Tivoli Storage Manager password
integrity, multiple backup objects are sent to the Tivoli has expired. You need to change your password.
Storage Manager server within a single transaction. All
System action: Processing ends.
backup objects within a single transaction are required
to have the same management class backup copy User response: Obtain a new password for your Tivoli
destinations. Storage Manager server; node using the change
password command or by asking your Tivoli Storage
System action: Processing ends.
Manager Administrator to change your password.
User response: Contact your Tivoli Storage Manager
server administrator.
FMX0257E Your password has expired.
Explanation: Your Tivoli Storage Manager password
FMX0216E Unable to obtain space information for
has expired. A new password needs to be obtained.
volume (volumename).
System action: Processing ends.
Explanation: An attempt was made to obtain space
information for a volume. This attempt failed. User response: Obtain a new password for your Tivoli
Storage Manager node using the change password
System action: Processing ends.
command or by asking your Tivoli Storage Manager
User response: None Administrator to change your password.

FMX0217E The Tivoli Storage Manager filespace FMX0258E You did not enter a valid password.
name is invalid. Processing ends.

Explanation: The filespace name or directory Explanation: The password that was entered was not
delimeter is invalid. a valid password.

System action: Processing ends. System action: Processing ends.

User response: Check that the filespace name length, User response: Re-enter the command specifying a
characters, and directory delimeters are valid. valid password.

FMX0218E The Tivoli Storage Manager high level FMX0259E The password you entered for
qualifier is invalid. verification does not match the
password you entered for your new
Explanation: The high level qualifier name or password. Your password will not be
directory delimeter is invalid. changed.
System action: Processing ends. Explanation: The password you entered for
User response: Check that the high level qualifier verification of your new password does not match the
name length, characters, and directory delimeters are new password that was entered.
valid. System action: Processing ends.

Chapter 4. FMX messages 199

FMX0260I • FMX0300E

User response: Try again to change your password System action: Processing continues.
being sure to enter the same password for the new
User response: It is possible that a default browser is
password and for the verification password.
not defined for the system. This is okay. An attempt
will be made to use Microsoft Internet Explorer.
FMX0260I Password successfully changed.
Explanation: The change password command FMX0265E Could not find Internet Explorer.
completed successfully
Explanation: An attempt was made to read the
System action: Processing ends. registry to determine where Microsoft's Internet
Explorer was installed. This attempt failed.
User response: None
System action: Processing ends.
FMX0261I There are no backups for the server User response: Make sure that the registry is set up
named servername. correctly for Internet Explorer.
Explanation: There are no backups on the Tivoli
Storage Manager server for the specified server name. FMX0266E Could not find the Tivoli Storage
Manager HTML books.
System action: Processing ends.
Explanation: An attempt was made to read the
User response: None
registry to determine where the Tivoli Storage Manager
books were installed. This attempt failed.
FMX0262E Errors occurred while processing the
System action: Processing ends.
VSS operation. Examine the Windows
Event Logs and DSMERROR.LOG for User response: It may be necessary to reinstall the
additional details. application client code. This will ensure that the
registry entries are set up correctly.
Explanation: While attempting to process a VSS
operation, an unexpected error occurred.
FMX0267E The verify password entered does not
System action: Processing ends.
match the new password entered.
User response: Attempt to determine the source of the
Explanation: The verify password does not match the
error by examining the Data Protection for Exchange
new password.
log file, the TSM Client error log file
(DSMERROR.LOG), the Windows Application Event System action: Processing ends.
Log, the Windows System Event Log, and the VSS
User response: Retry the command with a matching
provider log file, if applicable. Additional instructions
verify password.
for Windows VSS operations are located in the TSM
Problem Determination Guide. Correct the problem and
retry the operation. If this error persists, contact your FMX0292E An unknown error has been detected. rc
service representative. = rc
Explanation: An error occured without an error
FMX0263E Failed to start Web browser with a message. The return code, rc, is displayed.
return code of returncode.
System action: Processing ends.
Explanation: An attempt was made to start the web
browser to view the TSM HTML b ook. This attempt User response: Retry the operation. If this error
failed. persists, contact your service representative.

System action: Processing ends.

FMX0300E Invalid restore type.
User response: Start your web browser manually and
point it to bookfrm.htm in the agent htm directory. Explanation: The type of restore requested is invalid.
System action: Processing ends.
FMX0264I Could not find the default browser User response: Re-enter the command specifying a
defined. An attempt will be made to use valid restore type.
Microsoft Internet Explorer.
Explanation: An attempt was made to read the
registry to determine the default browser. However, a
default browser is not defined. A determination will be
made where Microsoft Internet Explorer is installed.

200 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX0301E • FMX0487E

TRACEFILE so that it is equal to or less than 255

FMX0301E Invalid backup type.
characters in length.
Explanation: The type of backup requested is invalid.
System action: Processing ends. FMX0383E Specifying the trace file 'link' as a
symbolic link is not allowed.
User response: Re-enter the command specifying a
valid backup type. Explanation: Trace file 'linkname' cannot be a symbolic
link.
FMX0351E Invalid trace keyword - 'keyword' System action: The symbolic link 'linkname' is deleted,
the trace file is recreated, and processing stops.
Explanation: A TRACEFLAG option in the user
configuration file or on the command line is incorrect. User response: Specify the trace file location with the
'tracefile' option.
System action: Client program did not initialize or
tracing was not enabled in the applet.
FMX0384E Symbolic link 'linkname' to 'target' was
User response: Correct the value.
successfully deleted.
Explanation: Log 'linkname' cannot be a symbolic link.
FMX0357E Unable to open trace output file
file-name. System action: The symbolic link 'linkname' is deleted,
the log is recreated, and processing stops.
Explanation: A TRACEFILE option in the user
configuration file or on the command line used a User response: Check the location of the new file. To
directory path and file-name combination to which you specify the location of log files, refer to the user's
do not have write access. manual for the 'errorlogname' option, the
'schedlogname' option, and the 'DSM_LOG'
System action: Client program did not initialize.
environmental variable.
User response: Change the TRACEFILE value so that
it is a location to which you have write access.
FMX0385E Unable to delete symbolic link 'link'.
Explanation: Log 'linkname' cannot be a symbolic link.
FMX0366E Unable to close trace output file
file-name. System action: Processing stops.
Explanation: An error occurred during the closing of a User response: Delete the symbolic link 'linkname'.
trace output file-name (for example, not enough disk
space).
FMX0476E program-name: cannot open file file-spec:
System action: Processing continues. error.
User response: Check the options.doc file for a Explanation: DP cannot open the file.
description of possible causes of the error, or see your
System action: DP cannot complete the requested
system administrator.
operation.
User response: Retry the operation. If the problem
FMX0367E Unable to write to trace file tracefile.
continues, check with your system administrator.
Tracing disabled.
Explanation: An error occurred when writing to the
FMX0487E Specifying the error log 'link' as a
specified tracefile.
symbolic link is not allowed.
System action: Tracing is disabled. Processing
Explanation: Error log 'linkname' cannot be a symbolic
continues.
link.
User response: Ensure the device that the tracefile
System action: The symbolic link 'linkname' is deleted,
access is available and has sufficient space for the
the error log is recreated, and processing stops.
tracefile. Retry the command.
User response: Check the location of the new error
log. To specify the location of the error logs, refer to the
FMX0368E Invalid trace file name (name too long).
user's manual for the 'errorlogname' option and
Explanation: A TRACEFILE option in the preferences 'DSM_LOG' environmental variable.
files used a file name that is too long.
System action: Client program did not initialize.
User response: Change the file name used as the

Chapter 4. FMX messages 201

FMX0488E • FMX0517I

System action: Transition processing continues.

FMX0488E Initialization functions cannot open the
error log: log-name. errno = errno-value, User response: None.
Explanation: The file log-name could not be opened
during initialization. The system set the error code FMX0498I count log records processed.
errno-value. If the reason given is "access denied," the
current user does not have permission to write to the Explanation: This is just a progress report to let you
log in the directory specified. It is also possible that no know the process is still ongoing.
space is available at the given log location. System action: Transition processing continues.
System action: Processing terminates. User response: None.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory into which the FMX0501E Invalid Proxy Configuration Detected:
current user can write. You may also use the Target Node 'targetnode' is not listed as a
ERRORLOGNAME option to specify a file to which the valid node to proxy to for Node Name
current has write permission. 'nodename'.
Explanation: The proxy node configuration on the
FMX0495E Failure writing to a Tivoli Storage TSM Server is not correct to support this VSS
Manager log or log-related file: file-name, operation.
errno = errno-value, reason
System action: The VSS operation stops.
Explanation: A failure was encountered when writing
to one of the log files or a related file named file-name. User response: Contact the TSM Server administrator
The system set the error code errno-value. reason is the to have the correct TSM Server GRANT PROXY
system explanation of that error code. Among other commands issued to enable proxy authority for the
things, it is possible that no space is available at the nodes. If the error persists, contact your service
given log location. representative.

System action: Processing terminates.

FMX0515E Invalid DSMAGENT Node
User response: Set the DSM_LOG (or DSMI_LOG) configuration found for node
environment variable to a directory with adequate 'dsmagentnode'.
space to write the log data.
Explanation: The DSMAGENT Node specified is not
configured properly.
FMX0496I DP is converting the log-file from
continuous (pruning) mode to wrapping System action: The VSS operation stops.
mode. This process may take several User response: Verify that the DSMAGENT Node
minutes. specified is correct and that the Client Acceptor
Explanation: The log-file was previously in continouos Daemon (CAD) is running for the DSMAGENT Node.
mode where the only size control was through the use If the error persists, contact your service representative.
of ERRORLOGRETENTION or
SCHEDLOGRETENTION option. This is the first FMX0516I The Windows console event handler
occasion where ERRORLOGMAX or SCHEDLOGMAX received a 'event' console event.
is specified for this log, so its format must be changed
and old data saved. Explanation: A console event was received by one of
the Data Protection for Microsoft Exchange Server
System action: Transition processing continues. processes or programs. The following events can be
User response: None. recevied:
v Ctrl-C - This indicates either the user entered the
ctrl-c sequence or that one of the Windows services
FMX0497I DP is converting the log-file from
was stopped.
wrapping mode to continuous (pruning)
mode. This process may take several System action: None.
minutes.
User response: None.
Explanation: The log-file was previously in wrapping
mode where the size control was through the use of the
FMX0517I An unexpected error was encountered.
ERRORLOGMAX or SCHEDLOGMAX option. This is
DP function name : function-name DP
the first occasion where ERRORLOGMAX or
function : function-desc DP return code :
SCHEDLOGMAX is not specified for this log, so its
TSM-rc DP file : file-name (line-number)
format must be changed and old data saved.

202 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX0518E • FMX0556E

Explanation: None.
FMX0521E Pruning functions cannot open one of
System action: Processing stops. the Tivoli Storage Manager prune files:
log-name. errno = errno-value,
User response: Contact the DP administrator with the
information provided in this message. Explanation: The file "log-name" could not be opened
during pruning. The system set the error code
errno-value. If the reason given is "access denied," the
FMX0518E Backups selected for restore must have current user does not have permission to write to the
the same backup location (TSM or file in the directory specified. It is also possible that no
LOCAL). space is available at the given file location or another
Explanation: A VSS restore operation was submitted Tivoli Storager Manager process started by different
that specified multiple backup objects. The backup user id is performing pruning at the same time.
objects chosen had different backup locations. This is System action: Pruning stops, processing continues.
not allowed. All backup objects submitted in the same
VSS restore operation must have the same backup User response: Set the DSM_LOG (or DSMI_LOG)
location, either TSM or LOCAL, but not both. environment variable to a directory into which the
current user can write.
System action: The VSS restore operation stops.
User response: Retry the VSS restore operation FMX0522E DIAG:
specifying one backup object at a time.
Explanation: The message text is provided for
diagnostic purposes and is meant to provide
FMX0519E The VSS operation failed with rc = information to IBM support in problem determination.
returncode.
System action: None.
Explanation: There was a failure when TSM
performed the VSS operation. User response: None.
System action: The VSS operation stops.
FMX0524S Error 'errtxt' (errno=errno) occurred
User response: Verify that the TSM Client Acceptor trying to write to audit log 'file-name'.
Daemon (CAD) is installed, configured, and running The audit log function is disabled.
properly on the machine. Retry the operation. If the
error persists, contact your service representative. Explanation: There was an error encountered writing
to the audit log (for example, there is not enough space
on the disk).
FMX0520E Failed to connect to Local DSMAGENT
Node 'localdsmagentnode' at address:port System action: Audit logging is disabled for the rest
'address:portnumber'. Verify that the TSM of the operation. The return code for the operation is
Client Acceptor Daemon (CAD) is set to 12 to indicate that the contents of the audit log
installed, configured, and running are incomplete.
properly.
User response: If this is an out of space condition
Explanation: An attempt was made to connect to the either free up space on the volume or try to write the
TSM Client Acceptor Daemon (CAD) running on the audit log to a volume with more space.
local machine. A communication error occurred when
this connection was attempted.
FMX0555E Invalid number of snapshots:
System action: The operation stops.
Explanation:
User response: In order to perform VSS operations,
System action: Policy was not created.
you must have a TSM Client Acceptor Daemon (CAD)
and a TSM Remote Client Agent Service (DSMAGENT) User response: Specify a number in the range: range:
installed and configured properly. In addition, the TSM 1...9999 or NOLimit
Client Acceptor Daemon (CAD) must be running.
Verify that the TSM Client Acceptor Daemon (CAD) is
FMX0556E Invalid number of days:
installed, configured, and running properly on the local
machine. If the error persists, contact your service Explanation:
representative.
System action: The Policy was not created.
User response: Specify a number in the range: range:
0...9999 or NOLimit

Chapter 4. FMX messages 203

FMX0571E • FMX0588E

FMX0571E The specified policy was not found: FMX0581E Volume volume-name could not be
'policy' locked.
Explanation: Explanation: The system call to lock the volume
failed.
System action:
System action: Processing stopped.
User response: Please make sure that the specified
policy exists. User response: Please verify that no other application
is accessing the volume. During restore of an image DP
must have exclusive use of the volume.
FMX0572E The specified policy already exists:
'policy'
FMX0583E Invalid name of policy specified. Valid
Explanation:
input characters include alphanumeric
System action: Policy was not created. charaters and underscore.

User response: Enter a different name for the policy. Explanation:

System action: Policy was not created.
FMX0573E The specified policy could not be
User response: Please specify a valid name.
updated: 'policy'
Explanation: This is due to a problem in virtual server
FMX0585E Unable to connect to the TSM Client
database.
Acceptor Daemon (CAD).
System action:
Explanation: Possible causes of this message include:
User response: Make sure that FCM is configured The TSM Client Acceptor Daemon (CAD) is not
correctly. running. The VSSALTSTAGINGDIR option setting in
the TDP option file is not set to the same value as the
VSSALTSTAGINGDIR option setting in the Data
FMX0574E The specified policy could not be Protection for Microsoft Exchange Server Remote Client
deleted: 'policy' Agent Service (DSMAGENT) option file. They must be
Explanation: This is due to a problem in virtual server set to the same value for successful TDP operations.
database. System action: The VSS operation stops.
System action: User response: Ensure that the TSM Client Acceptor
User response: Make sure that FCM is configured Daemon (CAD) is running. Ensure that the
correctly. VSSALTSTAGINGDIR option setting in the TDP option
file is set to the same value as the
VSSALTSTAGINGDIR option setting in the Data
FMX0575E The specified policy could not be Protection for Microsoft Exchange Server Remote Client
created: 'policy' Agent Service (DSMAGENT) option file. After
Explanation: This is due to a problem in virtual server correcting the VSSALTSTAGINGDIR option
database. inconsistency, retry the TDP operation.

System action:
FMX0588E The value for the BACKUPDESTination
User response: Make sure that FCM is configured option is not allowed. Data Protection
correctly. for Microsoft Exchange Server is only
licensed to run data protection
FMX0576I There were no items found. operations to a Tivoli Storage Manager
server. It is not licensed to backup or to
Explanation: The query completed successfully, but no restore locally managed snapshots.
results were found.
Explanation: The value for the configuration option is
System action: None. not allowed. The only allowed value is TSM. Data
Protection for Microsoft Exchange Server is only
User response: Change the specified search criteria.
licensed to run data protection operations to a Tivoli
Storage Manager server. It is not licensed to backup or
to restore locally managed snapshots.
System action: Processing ends.
User response: Set the backup destination to TSM. In

204 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX0589E • FMX0598E

order to create and restore local VSS backups it is

FMX0593E Data Protection for Microsoft Exchange
required to use and install a fully-featured valid license
Server is not licensed to perform
or to purchase an upgrade, and install Tivoli Storage
offloaded VSS backups.
FlashCopy Manager. If you use Data Protection for
Microsoft Exchange Server it is also required to Explanation: Currently installed license does not allow
purchase and install IBM Tivoli Storage Manager for to perform offloaded VSS backups. In order to use this
Copy Services - Microsoft Exchange VSS Integration feature it is necessary to install a valid fully-featured
Module. license.
System action: The operation stops.
FMX0589E You are not allowed to set
User response: In order to perform offloaded VSS
REMOTEDSMAGentnode option. Data
backups install a valid fully-featured license. If you use
Protection for Microsoft Exchange
Data Protection for Microsoft Exchange Server it is also
Server is not licensed to perform
required to purchase and install IBM Tivoli Storage
offloaded VSS backups.
Manager for Copy Services - Microsoft Exchange VSS
Explanation: The REMOTEDSMAGentnode option is Integration Module. Contact your service representative
used to perform offloaded VSS backups. to find out purchase details.
System action: The operation stops.
FMX0594E You cannot perform offloaded VSS
User response: In order to perform offloaded VSS
backups in TSM Server independent
backups install a valid fully-featured license. If you use
environment.
Data Protection for Microsoft Exchange Server it is also
required to purchase and install IBM Tivoli Storage Explanation: OFFLOAD option is not available in
Manager for Copy Services - Microsoft Exchange VSS TSM Server independent environment.
Integration Module. Contact your service representative
System action: The operation stops.
to find out purchase details.
User response: In order to perform offloaded VSS
backups you have to configure Tivoli Storage
FMX0590E A Data Protection communication error
FlashCopy Manager to manage snapshot backups using
with the Tivoli Storage Manager server
a Tivoli Storage Manager server. To do this you can use
has occurred.
Tivoli Storage Manager configuration wizard.
Explanation: Communications with the Tivoli Data
Protection server has been lost.
FMX0595E The options file 'optfile' does not exist. It
System action: The operation stops. is required for proper operation.
User response: Correct the TCP/IP communications Explanation: The specified TSM API options file could
error with the Tivoli Storage Manager server and retry not be found. It is required in order to complete the
the operation. command.
System action: Processing ends.
FMX0591I Data Protection communications with
User response: Make sure to complete Tivoli Storage
the Tivoli Storage Manager server has
Manager configuration and try the operation again.
been successfully recovered.
Explanation: Communications with the Tivoli Data
FMX0598E The application cannot run in safe
Protection server has been successfully recovered.
mode.
System action: None.
Explanation: The application requires either Services
User response: Continue with normal operations. or Drivers that are not available when running in safe
mode.
FMX0592E The Data Protection TCP/IP session System action: The application processing stops.
with the Tivoli Storage Manager server
User response: Restart the system using the normal
was canceled.
startup. When the system is started, run the
Explanation: The Data Protection TCP/IP session with application.
the Tivoli Storage Manager server was cancelled.
System action: The operation stops.
User response: Correct the reason the Tivoli Storage
Manager server administrator cancelled the session and
retry the operation.

Chapter 4. FMX messages 205

FMX0599E • FMX5053E

System action: The operation stops.

FMX0599E The application cannot establish a
remote powershell connection. User response: In order to create and restore local VSS
backups it is required to purchase and install a
Explanation: The application attempted to establish a
fully-featured valid license. NOTE: If you use Data
remote powershell connection. The operation failed.
Protection for Microsoft Exchange Server it is also
System action: The application processing stops. required to use and install IBM Tivoli Storage Manager
for Copy Services - Microsoft Exchange VSS Integration
User response: Verify you are using the correct
Module or to purchase an upgrade, and install Tivoli
credentials. For more information, see the Microsoft
Storage FlashCopy Manager. If IBM Tivoli Storage
about_Remote_Troubleshooting Help topic.
Manager for Copy Services - Microsoft Exchange VSS
Integration Module is installed, there will be a license
FMX0601E There is a problem that causes file, \"acsexc.lic\", in the Data Protection for Microsoft
processing to stop. To identify the Exchange Server installation directory.
source of the problem and the solution,
look for details in the service level trace
FMX5050I A new configuration file has been
file.
created.
Explanation: This problem occurs when either the
Explanation: The /configfile value specified a file
local or remote Powershell cmdlet or script reports an
name that does not exist. A new file has been created.
error. Details about the error are not available until
more trace file information is analyzed. System action: Processing continues.
System action: Application processing stops. User response: None.
User response: To identify the problem, look for
information in the service level trace files. For more FMX5051I The configuration file cannot be found,
information about viewing trace files, see the using default settings.
Troubleshooting section of the technical documentation
Explanation: The /configfile value specified a file that
provided with the software.
cannot be found. Default settings will be used.
System action: Processing continues using default
FMX0602E While attempting to communicate with
settings.
the remote client, a version check
reveals that the versions do not match. User response: Ensure that the configuration file
exists, and enter the command again.
Explanation: During initialization between the local
client and the remote client, version checking reveals
that the versions do not match. This is usually the FMX5052E An error occurred trying to set the
result of an upgrade of one client module without preference preference.
upgrading other client modules that are part of product
solution. Explanation: An error occurred while writing to the
preferences file.
System action: The calling procedure returns and
control is passed back the user. System action: Processing ends.

User response: Check the versions of all TSM Client User response: View any other messages that were
products that communicate with each other and ensure displayed. Fix any of the problems indicated and enter
that they are all at the same version, release, and level. the command again.

FMX3528E Data Protection for Microsoft Exchange FMX5053E The value for the preference preference is
Server is only licensed to run data not valid. See the TDPEXCC HELP SET
protection operations to a Tivoli Storage output or the User's Guide for valid SET
Manager server. It is not licensed to command parameters.
back up or to restore using locally Explanation: The preference being set is not valid.
managed snapshots.
System action: Processing ends.
Explanation: Currently installed license allows to
create and restore only TSM VSS backups. In order to User response: Run the "tdpexcc help set" command
create backups and to restore local VSS backups, Data or see the User's Guide for valid SET command
Protection for Exchange verifies that the Exchange parameters.
Server supports VSS backup (that is, it is at least
Exchange Server 2003), and that a valid fully-featured
license is installed.

206 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX5054I • FMX5063E

FMX5054I The preference has been set FMX5059W The logfile log file cannot be opened for
successfully. writing. There will be no logging of
events.
Explanation: The preference was set successfully.
Explanation: The specified log file could not be
System action: Processing ends.
opened for append and logging of events will not
User response: None occur. The log file may be read-only or the log file
name is not valid.

FMX5055E The Microsoft Exchange API could not System action: Processing continues without logging.
be loaded.
User response: Determine why the log could not be
Explanation: If running on Microsoft Exchange 5.5, opened. You may need to ensure that the log file is not
the dll that is attempting to load is edbbcli.dll. If read-only, or ensure that a valid drive or partition is
running on a later version of Microsoft Exchange, the specified in the log file name.
dll that is attempting to load is esebcli2.dll.
System action: Processing ends. FMX5060E A Tivoli Storage Manager API error has
occurred.
User response: Ensure that the Microsoft Exchange
Server has been correctly installed. Explanation: A Tivoli Storage Manager API api error
has occurred.

FMX5056I The logfile log file could not be pruned. System action: Processing ends.
Processing will continue.
User response: Try the operation again. If the error
Explanation: An attempt to prune the log was persists, contact your service representative.
unsuccessful.
System action: Processing continues. FMX5061E A Microsoft Exchange api error has
occurred.
User response: Ensure that the log file name is valid
and that the log file exists. If a valid log file name was Explanation: A Microsoft Exchange api error has
specified, view the log for indications of what the occurred.
problem may be.
System action: Processing ends.
User response: Try the operation again. If the error
FMX5057I The logfile log file has been pruned
persists, contact your service representative.
successfully.
Explanation: The specified log file was pruned
FMX5062E The version of Microsoft Exchange that
successfully.
is running is not a supported version for
System action: Processing continues. IBM Tivoli Storage Manager for Mail.

User response: None. Explanation: IBM Tivoli Storage Manager for Mail has
detected a version of Microsoft Exchange Server that is
not supported.
FMX5058W The length of the logf ile name is
greater than the maximum allowed. System action: Processing ends.
Processing will continue using a log file
User response: Refer to the software requirements
name of logfile in the current directory.
section of the product documentation to view a list of
Explanation: The log file name entered was not fully the supported versions of Microsoft Exchange Server. If
qualified. When the fully qualified log file name was the version of Microsoft Exchange Server running is a
created, it was longer than the maximum allowed supported version, try the operation again. If the error
length for a log file name. persists, contact your service representative.

System action: Processing continues creating and

using a log file in the current directory. FMX5063E An error occurred trying to get the
Microsoft Exchange version information.
User response: Update the log file name using a fully It could be a problem with the registry.
qualified path. Or, a Microsoft Exchange Server is not
installed on this machine.
Explanation: An attempt was made to read the
registry to determine the level of Microsoft Exchange
that is currently running. This attempt failed.

Chapter 4. FMX messages 207

FMX5067E • FMX5140I

System action: Processing ends. dismounted databases are skipped.

User response: Determine if the registry has been User response: Ensure that the database you want to
corrupted. Also, ensure that the Microsoft Exchange back up is mounted.
Server is installed on this machine.
FMX5073E None of the databases are backed up.
FMX5067E The specified databases do not exist or
Explanation: The request to back up a set of databases
have not been dismounted.
could not be completed because at least one of the
Explanation: The mailbox databases that were entered following conditions is true: 1) all of the databases are
either do not exist on the Microsoft Exchange Server or dismounted 2) a backup is in progress on another
have not been dismounted. replica 3) a backup has been made more recently than
specified by the /MINimumbackupinterval parameter
System action: Processing ends.
System action: Processing stops.
User response: Verify that the mailbox databases exist
and that the databases have been dismounted before User response: Ensure that the database you want to
starting the restore. back up is mounted, or another backup is not in
progress, or change the /MINimumbackupinterval
parameter.
FMX5068W The database <databasename> does not
exist in the storage group <storagegroup>.
FMX5074E The databases entered do not exist, or
Explanation: The database that was entered does not
were entered with the wrong
exist in the storage group that was entered.
capitalization.
System action: Processing ends.
Explanation: A request was made to back up a set of
User response: Enter the command again specifying a databases that do not exist, or the database names
valid database name that exists in a valid storage might not have been entered using the correct
group. capitalization.
System action: Processing stops.
FMX5069W The database <database> in the storage
User response: Check the capitalization and spelling
group <storage group> is not dismounted.
of the databases and enter the backup command again.
Explanation: While examining the list of databases to
restore, it was determined that not all of the databases
FMX5087E The PASSWORDACCESS parameter is
within the specified storage groups were dismounted.
set to GENERATE, but either the stored
System action: Processing continues skipping over the password is incorrect or there is no
listed databases and storage groups. stored password. If you do not have a
stored password, use the
User response: Ensure that the databases are -TSMPassword=xxx option to set and
dismounted and enter the command again. store your password.
Explanation: The client options file has the
FMX5070W The Directory Service is not running. PASSWORDACCESS option set to GENERATE.
The Directory will not be backed up. Currently, there is no password stored. An initial
Explanation: A request was made to backup the password must be stored.
Directory service. However, the Directory service needs System action: Processing stops.
to be running in order to do the backup.
User response: Enter the command again using the
System action: Processing ends. -TSMPassword option. After doing so,subsequent
User response: Start the Directory service and enter commands will not require a password.
the backup command again.
FMX5140I Database <database> does not exist -
FMX5072W Database <component name> is skipping.
dismounted -- skipping. Explanation: The database that was specified by the
Explanation: A request was made to back up a set of user is not found on this Exchange server.
databases. However, some databases are not mounted. System action: This database is skipped.
The databases need to be mounted for the backup to
proceed. User response: Ensure that the database name is
spelled correctly and enter the command again.
System action: Processing continues, but the

208 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX5142E • FMX5350E

FMX5142E The requested database was not found. FMX5239E Unable to retrieve the component
information.
Explanation: The databases could not be found on this
Microsoft Exchange server. Explanation: An attempt was made to retrieve the
storage group or mailbox database information for the
System action: Processing stops.
Microsoft Exchange Server. This attempt failed.
User response: Ensure that the database names are
System action: Processing ends.
spelled correctly and enter the command again.
User response: Ensure that the Microsoft Exchange
Server is running properly.
FMX5209I There are no backups matching the
server name servername and the
following filespecs:filespecs. FMX5240E Unable to retrieve database information.
Explanation: There are no database backups on the Explanation: Data Protection for Exchange tried to
Tivoli Storage Manager server for the specified server retrieve database information from Microsoft Exchange
name. Server, but this attempt failed.
System action: Processing stops. System action: Processing stops.
User response: None if there are no backups; User response: Ensure that Microsoft Exchange Server
otherwise, check your spelling and try again. is running properly.

FMX5228I The LOCALDSMAgentnode preference FMX5241E The Microsoft Exchange Information

is not set correctly. Store is currently not running.
Explanation: Data Protection for Exchange has not Explanation: Data Protection for Exchange tried to
been configured to perform VSS operations. The retrieve information about the Microsoft Exchange
LOCALDSMAgentnode preference is not set correctly. Server Information Store, but this attempt failed.
System action: Processing stops. System action: Processing stops.
User response: Ensure that the User response: To retrieve the Microsoft Exchange
LOCALDSMAgentnode preference is set correctly. This Server information, the Microsoft Exchange Information
preference can be set by running the configuration Store must be running. Start or restart this service to
wizard. get the requested information.

FMX5229E An error occurred while obtaining VSS FMX5304E Unable to open a Microsoft Exchange
information from the following Local service to determine if it is running.
DSMAgent Node: 'localdsmagentnode'.
Explanation: An attempt to open a service failed.
Explanation: Data Protection for Exchange attempted
System action: Processing stops.
to obtain VSS information through the specified
LOCALDSMAgentnode, but failed. The specific error User response: Check your Microsoft Exchange
message encountered is also displayed. services and ensure that they are running properly.
System action: VSS information is not displayed.
FMX5305E Unable to query service information.
User response: Refer to the error message displayed
along with this message. Explanation: An attempt to query specific service
information failed.
FMX5237E Unable to communicate with the System action: Processing stops.
Microsoft Exchange Server.
User response: Check your Microsoft Exchange
Explanation: An attempt was made to communicate services and ensure that they are running properly.
the with the Microsoft Exchange Server that was
entered. This connection attempt failed.
FMX5350E An unknown Exchange error has
System action: Processing stops. occurred.
User response: Ensure that the name of the Microsoft Explanation: An Exchange error has occurred. The
Exchange Server that was entered is valid. Also, ensure Windows Event Log may contain more information.
that the Microsoft Exchange Server is running and that
the Exchange services are started. System action: Processing stops.
User response: If the Windows Event Log does not

Chapter 4. FMX messages 209

FMX5351E • FMX5360E

help resolve the problem, verify the Exchange Server System action: Processing stops.
installation and retry the operation.
User response: Ensure that the database exists and is
spelled correctly with proper capitalization, and retry
FMX5351E The Exchange server application is not the operation.
registered for backup.
Explanation: The Exchange server application must be FMX5356E The database file name is undefined.
registered for backup with the Windows Server. The
Explanation: Every Microsoft Exchange database must
Windows NT event log may contain more information.
specify a database file name.
System action: Processing ends.
System action: Processing stops.
User response: If the Windows NT event log does not
User response: Verify the database properties and
help resolve the problem, verify the Exchange Server
retry the operation.
installation and retry the operation. If the error persists,
contact your service representative.
FMX5357W The truncation of the transaction log
failed.
FMX5352E The Exchange server application is not
registered for offline restore. Explanation: The truncation of the transaction log
failed.
Explanation: The Exchange server application must be
registered for offline restore with the Windows Server. System action: Processing continues.
The Windows NT event log may contain more
information. User response: Refer to other messages that are
displayed to determine the problem.
System action: Processing ends.
User response: If the Windows NT event log does not FMX5358E A Microsoft Exchange API protocol error
help resolve the problem, verify the Exchange Server has occurred.
installation and retry the operation. If the error persists,
contact your service representative. Explanation: An unrecoverable Microsoft Exchange
API protocol error has occurred.

FMX5353E The Exchange server application is not System action: Processing ends.
registered for online restore. User response: Contact your service representative.
Explanation: The Exchange server application must be
registered for online restore with the Windows Server. FMX5359E Unable to get the TEMP environment
The Windows NT event log may contain more variable. Ensure that the environment
information. variable is set and retry the operation.
System action: Processing ends. Explanation: An attempt was made to get the TEMP
User response: If the Windows NT event log does not environment variable for this system. This attempt
help resolve the problem, verify the Exchange Server failed.
installation and retry the operation. If the error persists, System action: Processing stops.
contact your service representative.
User response: Ensure that the environment variable
is set and retry the operation.
FMX5354E The database was not found.
Explanation: The specified database name was not FMX5360E The /RECOVer=APPLYRESToredlogs
found. option is not allowed during a partial
System action: Processing ends. restore.

User response: Verify the command input and retry Explanation: A partial restore was requested with the
the operation. If the error persists, contact your service /RECOVer=APPLYRESToredlogs option. The
representative. /RECOVer=APPLYRESToredlogs option is not allowed
during a partial restore.

FMX5355E The database was not found. Ensure System action: Processing ends.
that the database exists and is spelled User response: Enter the command to restore the
correctly with proper capitalization. entire component or enter the command without the
Explanation: The specified database name was not /RECOVer=APPLYRESToredlogs option.
found.

210 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX5361E • FMX5800E

FMX5361E It is invalid to have an '*' within a FMX5705W An error was encountered with Tivoli
database name. Storage Manager API initialization, rc =
returncode. Examine the dsierror.log for
Explanation: An attempt was made to backup a
more information or determine if the
database that contains an '*'. It is invalid to have an '*'
TSM Client is installed properly.
in a database name.
Explanation: An attempt was made to run setup for
System action: Processing continues, but this database
the Tivoli Storage Manager API. However, errors were
will not be backed up.
encountered. The API is a component of the
User response: Rename the database, otherwise this backup-archive client, which is also known as the VSS
database cannot be backed up. Requestor.
System action: Processing continues.
FMX5362W The filespace <filespace> in an invalid
User response: Examine the dsierror.log file to find
filespace name.
out more information about the problem. If this file
Explanation: The filespace displayed in the message does not exist, it is possible that the TSM API is not
exists, but is an invalid filespace. installed properly. If this is the case, uninstall the TSM
Client and re-run the configuration wizard.
System action: Processing continues, but this filespace
will not be used.
FMX5706I The logfile_name log file did not need
User response: Ensure that the database name does pruning.
not contain invalid characters. Refer to the Microsoft
Exchange documentation for the list of invalid Explanation: The log file specified did not exceed the
characters. maximum log size and did not need to be pruned.
System action: The log file is not changed.
FMX5500E The MultiByteToWideChar() function
User response: The log file will automatically be
failed.
pruned at a later date. If the log file is too large now,
Explanation: An internal error occurred. lower the number of days the log entries are retained.

System action: Processing stops.

FMX5798E MS Exchange API api name failed with
User response: Retry the operation. HRESULT: api retcode. Check the
Windows Application Event log for
FMX5501E The WideCharToMultiByte() function more details.
failed. Explanation: A Microsoft Exchange API error occurred
Explanation: An internal error occurred. during an operation. The specific API function that
failed, along with the HRESULT code of the failure and
System action: Processing ends. possible message associated with that error, is
User response: Retry the operation. If this error displayed.
persists, contact your service representative. System action: Processing stops.
User response: If the Windows Event Log does not
FMX5502E The restore destination directory path help to resolve the problem, stop and restart the
needs to be fully-qualified. Enter the Exchange Information Store and retry the operation.
command again and specify a
fully-qualified path for the /INTO
option. FMX5800E The backup is corrupt. See log file for
additional information.
Explanation: The /INTO option was specified without
a fully-qualified path. Explanation: When attempting to process an Exchange
backup on the Tivoli Storage Manager Server, not all
System action: Processing stops. required objects were present. The operation cannot
User response: Enter the command again and specify proceed. The specific backup affected is logged.
a fully-qualified path for the /INTO option. System action: Processing stops.
User response: Retry the operation with a different
backup.

Chapter 4. FMX messages 211

FMX5805E • FMX5819E

persist, verify that the Client Acceptor Daemon (CAD)

FMX5805E The restore failed. The file already
is installed, configured, and running properly on the
exists. Delete the existing files or
machine. If necessary, uninstall the TSM Client and
specify a different restore (/INTO) path.
re-run the configuartion wizard to reinstall the Client
Explanation: The specified file already exists in the Acceptor Daemon.
restore (/INTO) path. The RESTOREFILES command is
designed not to overwrite existing files.
FMX5816E Data Protection for Exchange is not able
System action: The restore operation fails and to run VSS operations. You must be
processing ends. running Exchange Server 2010 or later.
User response: If you want to restore the specified Explanation: In order to perform VSS operations, Data
file, you must first delete the file that exists in the Protection for Exchange verifies that the Exchange
restore (/INTO) path and retry the operation or specify Server level is at least Exchange Server 2010.
a different restore (/INTO) path and retry the
System action: The operation stops.
operation.
User response: Verify that the prerequisites identified
above are met and retry the operation.
FMX5811E Invalid command. Data Protection for
Exchange invalid backup type for a VSS
backup request. Supported types are FMX5817E Missing, blank, or invalid Local
full, copy, diff, and incr. DSMAGENT Node Name is not
allowed.
Explanation: An invalid backup type was specified on
the VSS backup request. Refer to your Data Protection Explanation: To run VSS operations, Data Protection
for Exchange User's Guide for supported backup types. for Exchange verifies that the Local DSMAGENT Node
Name is specified and valid. This error indicates that
System action: The backup operation is canceled.
the Local DSMAGENT Node Name is missing, blank,
User response: Retry the backup operation specifying or invalid.
a supported VSS backup type. Supported types are full,
System action: Processing stops.
copy, diff, and incr.
User response: Set the Local DSMAGENT Node
Name to a valid value and retry the operation.
FMX5814E Invalid command. Data Protection for
Exchange does not support OFFLOAD
with the combination specified for FMX5818E Invalid command. Data Protection for
backup destination and version of Exchange only supports restoring VSS
Windows. backup types of full, copy, diff, and incr.
Explanation: The OFFLOAD option was specified Explanation: An invalid backup type was specified on
with an unsupported backup destination. Data the VSS restore request. Data Protection for Exchange
Protection for Exchange only supports offload with a supports restoring backups of type full, copy, diff, and
backup destination of TSM or if running on a Windows incr.
System 2008 or later, backup destination LOCAL, TSM
or BOTH. System action: The restore operation is canceled.

System action: The backup operation is canceled. User response: Retry the restore operation specifying
a supported VSS backup type.
User response: Retry the VSS offloaded backup
operation specifying a backup destination of TSM.
FMX5819E Multiple backup objects were found for
the specified components and backup
FMX5815E The VSS operation failed with rc = destination. Use the /OBJECT= and
returncode. Check the dsmerror.log file /BACKUPDESTINATION= options to
and the Windows Event log for more identify which specific backup object to
details. The VSS Provider logs might restore.
also contain more information.
Explanation: The backup object specified for the VSS
Explanation: There was a failure when Data Protection restore operation was not specific enough to be unique.
for Exchange performed the VSS operation. More information is required to restore the correct
backup object.
System action: The VSS operation stops.
System action: The restore operation is canceled.
User response: Check the dsmerror.log file and the
Windows Event log for more details. The VSS Provider User response: Retry the restore operation specifying
logs might also contain more information. If problems

212 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX5820E • FMX5909E

the /OBJECT= and /BACKUPDESTINATION=

FMX5902E mapi32.dll has version version.release.
parameters.
Expected expected version.expected release
or higher. Download and install the
FMX5820E There were no Exchange backups found latest Microsoft MAPICDO download
on the Tivoli Storage Manager server and retry the operation.
matching the specified criteria.
Explanation: The correct version of Messaging
Explanation: A query was issued to the Tivoli Storage Application Programming Interface (MAPI) library
Manager server to find the Data Protection for mapi32.dll is required for mailbox restore operations.
Exchange backups that match the specified search
System action: The mailbox restore operation has
criteria. No backups were found.
failed.
System action: None.
User response: Verify that the correct version of
User response: Retry the operation using different mapi32.dll is installed on the system. Run the
criteria. command again.

FMX5839E Alternate or recovery database you are FMX5906E Loading the MAPI dynamic load library
restoring to does not exist. has failed. If necessary, reinstall the
Microsoft MAPICDO download.
Explanation: The alternate or recovery database that
was specified does not exist on the Microsoft Exchange Explanation: The mapi32.dll is required for mailbox
Server. restore operations.

System action: Processing stops. System action: The mailbox restore operation fails.

User response: Verify that the target database exists User response: Verify that the mapi32.dll is installed
and the database has been dismounted before retrying on the system. Run the command again.
the restore.
FMX5907E Initializing the MAPI subsystem failed.
FMX5843I No backups were found for the database Verify that the mapi32.dll is installed on
<database> that match the specifications the system and that MAPI is enabled for
entered. Check that the database name, your mailboxes.
backup destination, and OBJECT
Explanation: The MAPI subsystem is necessary for
parameters are correct.
mailbox restore operations.
Explanation: No backups found for the specified
System action: Processing stops.
database that match specified backup destination or
OBJECT (if any). User response: Verify that the mapi32.dll is installed
on the system and that MAPI is enabled for your
System action: This database is skipped.
mailboxes. Run the command again.
User response: Ensure that the database name is
spelled correctly, backup destination and OBJECT (if
FMX5908E Creating the MAPI profile has failed.
any) are specified correctly and enter the command
Ensure that you have Organization
again.
Management privileges, and that you
have an active mailbox.
FMX5901E mapi32.dll does not exist. If necessary,
Explanation: MAPI requires a user with an active
reinstall the Microsoft MAPICDO
Exchange mailbox and Organization Management
download.
privileges to perform mailbox restore operations.
Explanation: The Messaging Application
System action: Processing stops.
Programming Interface (MAPI) library mapi32.dll is
required for mailbox restore operations. User response: Either log on as a user with
Organization Management privileges, or add an active
System action: The mailbox restore operation fails.
mailbox for the current user.
User response: Verify that the mapi32.dll file is
installed on the system. Run the command again.
FMX5909E The MAPI subsystem logon has failed.
Check that you have an active mailbox
and Organization Management
privileges for this operation.
Explanation: Mailbox restore operations require a user

Chapter 4. FMX messages 213

FMX5910E • FMX5917I

with Organization Management privileges, and an

FMX5911E The MAPI subsystem has experienced a
active Exchange mailbox.
network failure. Verify that you are
System action: Processing stops. accessing the correct Exchange server,
and that the Exchange server has the
User response: Either log on as a user with Client Access Role installed. Also check
Organization Management privileges, or add an active that the /CLIENTACCESSSERVER
mailbox for the current user. parameter is correct.
Explanation: Data Protection for Exchange tried to
FMX5910E Opening a MAPI mailbox has failed. connect to Exchange, but experienced a network failure.
Explanation: Data Protection for Exchange attempted System action: Processing stops.
to open a mailbox using MAPI, but the operation
failed. The MAPI mailbox was not opened. User response: Verify that you are accessing the
correct Exchange server, and that the Exchange server
System action: Processing stops. has the Client Access Role installed. Also check that the
User response: The following causes are some of the /CLIENTACCESSSERVER parameter is correct.
more common causes of this error:
v Mailbox does not exist Resolution: Create the FMX5912E The MAPI subsystem has experienced a
necessary mailbox. failure.
v Mailbox has never been sent to or logged in to Explanation: The MAPI subsystem has experienced an
Resolution: Ensure that the mailbox is active by unknown error.
logging in to it or by sending at least one message to
the mailbox. System action: Processing stops.
v Mailbox database is not mounted Resolution: Verify User response: The problem is most likely a problem
that the mailbox is mounted, and mount it if it isn't with the configuration of the recovery user's mailbox or
already mounted. the MAPI configuration on your system. Verify that
v Insufficient privilege to access mailbox Resolution: both meet the requirements specified in your user
Ensure that the administrative ID that you are using documentation.
to restore data has the correct privileges, and has an
active mailbox on the system. Microsoft Exchange
FMX5915W Unable to obtain the Microsoft
2003 requires Exchange Administrators and Local
Exchange Server version running on
Administrators permissions, and Microsoft Exchange
your system. Microsoft Exchange 2010 is
2007 requires Exchange Organization Administrators,
being assumed. Unexpected results may
Local Administrators. Microsoft Exchange 2010
occur.
requires Organization Management and Local
Administrators permissions to resolve this issue. Explanation: An attempt was made to determine the
v Exchange server where mailbox database is located is level of Microsoft Exchange Server running on the
not available or down Resolution: Verify that access current system. This attempt failed.
to Exchange Server using Exchange Management System action: Processing continues. However,
Console (Exchange 2007) or Exchange System unexpected results may occur.
Manager (Exchange 2003).
User response: If the operation fails or produces
v Microsoft Information Store service is not running
unexpected results, verify that Microsoft Exchange
Resolution: Verify that Microsoft Exchange
Server is correctly installed on the system, and retry the
Information Store service is running through
operation.
computer management Services. Start the service if it
is not running.
v Microsoft Exchange System Attendant service is not FMX5917I The mailbox history has been
running Resolution: Verify that Microsoft Exchange successfully updated on the TSM
System Attendant service is running through Server.
computer management Services. Start the service if it Explanation: The mailbox location history stored on
is not running. the TSM Server was compared to the current mailbox
location information in the Active Directory and
updated accordingly. This operation is performed to
help facilitate individual mailbox restore operations.
System action: None
User response: None

214 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX5918W • FMX5930E

Directory or in the mailbox history information stored

FMX5918W The mailbox history did not update
on the TSM Server. If the specified mailboxes exist in
successfully on the TSM Server.
Active Directory, then the database backup was not
Explanation: An attempt was made to update the found.
mailbox location history stored on the TSM Server. This
System action: The specified mailboxes are not
operation is performed to help facilitate individual
restored.
mailbox restore operations. Problems were encountered
during the update attempt. User response: Verify that the specified mailbox
names are correct. Make sure that you are using the
System action: The mailbox history is not updated,
mailbox alias when specifying the mailbox names. After
but processing continues.
correcting the mailbox names, retry the mailbox restore
User response: Verify the following: operation. If this mailbox restore is for a deleted or
v the Active Directory configuration moved mailbox, you might retry the mailbox restore
operation using the 'MAILBOXOriglocation' option.
v the Data Protection for Exchange node username and
Also, make sure that the database is restored into the
password
recovery database properly. If specified mailbox name
v the proxynode configuration on the TSM Server is correct, verify that it has been successfully backed
up.
FMX5921E Data Protection for Exchange requires a
user with Organization Management FMX5924E There were no usable backups found.
privileges. For mailbox restores, the user
must also have an active mailbox. Explanation: The mailbox restore operation failed
because no usable backups were found.
Explanation: Mailbox restore operations requires a
user with Organization Management privileges, and an System action: No mailboxes are restored.
active Exchange mailbox. User response: Verify that you have specified the
System action: Processing stops. No mailboxes are correct TCPServeraddress and node name, and retry
restored. the operation.

User response: Either log on as a user with a mailbox

that has Organization Management privileges, or add FMX5929E The Microsoft Exchange Server MAPI
an active mailbox for the current user. Client and Collaboration Data Objects
(MAPICDO) download is not installed.
Download and install the latest
FMX5922E The mailbox 'mailboxname' was not Microsoft MAPICDO from the
found. Microsoft website before running
Explanation: The mailbox specified for the mailbox mailbox restore operations.
restore operation or the destination mailbox was not Explanation: Microsoft Exchange Server MAPI Client
found in the Active Directory or in the mailbox history and Collaboration Data Objects (MAPICDO) download
information stored on the TSM Server. is required for mailbox restore operations.
System action: The specified mailbox is not restored. System action: The specified mailboxes are not
User response: Verify that the specified mailbox name restored.
is correct. Make sure that you are using the mailbox User response: Verify that the Microsoft Exchange
alias when specifying the mailbox name. After Server MAPI Client and Collaboration Data Objects
correcting the mailbox name, retry the mailbox restore (MAPICDO) download is installed.
operation. If this mailbox restore is for a deleted or
moved mailbox, you might retry the mailbox restore
operation using the 'MAILBOXOriglocation' option. FMX5930E The requested MAPI message service
Also, make sure that the database is restored into the was not found.
recovery database properly. Explanation: The MAPI message service was not
found. This is most likely due to the service not being
FMX5923E An unknown mailbox name was defined in your local MAPISVC.INF file.
specified or the mailbox backup was not System action: The mailbox restore operation has
found in the recovery database. Verify failed.
that the mailbox name is correct. If the
specified mailbox name is correct, verify User response: Verify that the requested MAPI
that it has been successfully backed up. message service is defined in your local MAPISVC.INF
file. If this error resulted from trying to restore to a
Explanation: The mailboxes specified for the mailbox Personal Folders (.pst) file, look for the section "MSPST
restore operation were not found in the Active

Chapter 4. FMX messages 215

FMX5932E • FMX5983E

MS" in this file. If it is not defined, add the message

FMX5975E A valid FlashCopy Manager license file
service to your MAPISVC.INF file and run the
could not be located. Data protection
command again.
operations to a FlashCopy Manager
virtual server are not allowed.
FMX5932E The recovery database cannot be created
Explanation: To perform data protection operations to
because the TEMP environment variable
a FlashCopy Manager virtual server, a valid license for
is set to an invalid directory.
FlashCopy Manager must be installed in the FlashCopy
Explanation: The TEMP environment variable is set to Manager installation directory. This license file is
an invalid directory. named fcmclient.lic.

System action: Processing stops. System action: Processing stops.

User response: Verify that the TEMP environment User response: Verify that the fcmclient.lic file is
variable points to valid and accessible directory and try installed and retry the operation.
again.
FMX5976E A valid Data Protection for Exchange
FMX5935W The mailbox restore operation license file could not be located. Data
completed sucessfully; however not all Protection for Exchange is not licensed
of the mailbox items were restored. Run to run data protection operations to a
the mailbox restore operation again on Tivoli Storage Manager server. With the
the mailboxes that reported partial current licenses only data protection
completion, or use mailbox filters to operations to a FlashCopy Manager
restore a smaller subset of messages. stand-alone server can be run. Use the
configuration wizard to install or locate
Explanation: The mailbox restore operation has only the proper license.
partially completed. The messages that were restored
were restored correctly, but some items were not Explanation: To perform data protection operations to
restored. This failure might be because there were too a Tivoli Storage Manager server, a valid license for
many items to restore in one operation. Data Protection for Exchange (called excclient.lic) must
be installed. The Data Protection for Exchange license
System action: Processing stops. should be installed in the Data Protection for Exchange
User response: Run the mailbox restore operation installation directory.
again on the mailboxes that reported partial System action: Processing stops.
completion, or use mailbox filters to restore a smaller
subset of messages. User response: Use the configuration wizard to install
or locate the proper license.

FMX5948E An attempt to query detailed managed

capacacity failed. FMX5977E The /BACKUPDESTINATION
parameter cannot be 'TSM' when
Explanation: performing data protection operations
System action: using a FlashCopy Manager stand-alone
server.
User response:
Explanation: Data protection commands default to
/BACKUPDESTINATION=LOCAL when performed
FMX5972T TDPEXCC RESTOREMailbox against a FlashCopy Manager stand-alone server. The
mailbox-name[,mailbox-name2,mailbox- FlashCopy Manager supports no other values for these
name3,...] where mailbox-name can be: parameters. It is not necessary to specify this
an alias or display name parameter.
[/CONFIGfile=tdpexc.cfg|filename]
(default: tdpexc.cfg) System action: Processing stops.
[/FCMOPTFile=dsm.opt|filename] User response: Retry the command removing the
(default: dsm.opt) [/KEEPRdb=Yes|No] /BACKUPDESTINATION parameter.
(default: No)
[/LOGFile=tdpexc.log|logfilename]
(default: tdpexc.log) FMX5983E The MAPI subsystem has experienced a
[/LOGPrune=60|n|No] (default: 60) failure. There are not enough system
resources to complete the selected
operation.
Explanation: There are not enough system resources
to complete the selected operation. The Windows

216 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX5986I • FMX6030W

Application Event log may contain more information.

FMX6027E mapi32.dll has build version build version.
System action: Processing stops. Expected expected build version or higher.

User response: Ensure there are sufficient system Explanation: The correct build version of Messaging
resources and run the command again. Application Programming Interface library mapi32.dll
is required for mailbox restore operations.

FMX5986I Database <component> has circular System action: The mailbox restore operation has
logging enabled. Cannot perform failed.
incremental or differential backup -
User response: Verify that the correct build version of
skipping.
mapi32.dll is installed on the system. Run the
Explanation: The database that was specified by the command again.
user has circular logging enabled. Incremental or
differential backup is not possible.
FMX6028W <database name> is a DAG passive
System action: This database is skipped. database not in Healthy state --
skipping.
User response: Ensure that the database specified
does not have circluar logging enabled and run the Explanation: A request was made to back up a
command again if you want to perform incremental or Database Availability Group (DAG) passive database.
differential backups. The DAG passive database is not in a Healthy state. In
order to back up a DAG passive database, it must be in
a Healthy state.
FMX5994E Data Protection for Exchange is only
licensed to run data protection System action: Processing continues, but the specified
operations to a Tivoli Storage Manager database is skipped.
server. It is not licensed to back up
User response: Ensure that the DAG passive database
using locally managed snapshots.
is in a Healthy state and retry the backup operation.
Explanation: To back up using locally managed
snapshots, a valid FlashCopy Manager license is
FMX6029W At least one item that has passive
required or the Tivoli Storage Manager for Copy
database copies was specified for
Services - Microsoft Exchange VSS Integration Module
restore. When restoring this type of
must be installed.
database, care must be taken in
System action: Processing stops. handling the database copies. Consult
the Data Protection for Exchange
User response: Change the backup destination to documentation for details.
backup to a Tivoli Storage Manager server or obtain the
products or licenses necessary to enable this feature Explanation: When restoring a Database Availabilty
Group (DAG) database, additional steps must be taken
in order to suspend the database copy and update the
FMX6012W The database; database has not been database copy prior to bringing it online.
found on the Exchange Server. The
database files will be restored. After the System action: None.
restore completes, you can recreate the
User response: Consult the Data Protection for
database on the Exchange Server from
Exchange or Microsoft documentation for details.
the restored files.
Explanation: The database has not been found on the
FMX6030W At least one item that has passive
Exchange Server. The restore will continue to allow VSS
database copies was specified for
writer to restore the database files.
restore. When restoring this type of
System action: The restore operation continues, but database, care must be taken in
only the files are restored. handling the database copies. If you
have not prepared the passive database
User response: After the restore completes, you can copies for restore or are unsure of the
recreate the database on the Exchange Server from the necessary steps, please consult the Data
restored files. Protection for Exchange documentation
for details. Do you want to continue
with the restore operation?
Explanation: When restoring a Database Availabilty
Group (DAG) database, additional steps must be taken
in order to suspend the database copy and update the
database copy prior to bringing it online.

Chapter 4. FMX messages 217

FMX6031I • FMX6065E

System action: None.

FMX6039E An error has occurred while mounting
User response: Consult the Data Protection for or dismounting a database.
Exchange or Microsoft documentation for details.
Explanation: An error was detected while mounting
or dismounting a database.
FMX6031I Excluding <databaseType> database
System action: Errors were detected while mounting
<databaseName> from backup list because
or dismounting a database.
of option <optionName>-- skipping.
User response: Please check the Windows Event Log
Explanation: A backup command has been issued
for any Exchange errors. If this was a mount problem
where the option /EXCLUDENONDAGDbs,
during a restore, please verify the correct /RECOVer
/EXCLUDEDAGACTive, /EXCLUDEDAGPASsive,
option value was used, and the correct sequence of the
/MINimumbackupinterval or /PREFERDAGPASsive
Exchange transaction logs. Please resolve any problems,
has been specifed. The database has met the exclude
and retry the operation. If the errors persist, contact
option criteria and is skipped from backup.
your service representative.
System action: Processing continues, but the specified
database is skipped.
FMX6040W Component <component> requires a full
User response: None. backup. Data Protection for Exchange
can not perform an incremental or
differential backup - skipping.
FMX6032E Cannot create the recovery database
because there is an existing recovery Explanation: The component that was specified by the
database recovery database name on the user requires a full backup. An incremental or
Exchange Server. differential backup is not allowed until a full backup is
performed. This situation can occur if a new storage
Explanation: Data Protection for Exchange cannot group or database has been added and a full backup
create the recovery database because there already is an has not yet been performed.
existing recovery database on the Exchange Server.
System action: This component is skipped.
System action: Processing stops.
User response: Perform a full backup on the specified
User response: Remove the existing recovery database component as soon as possible.
from the Exchange Server. Run the command again.

FMX6055W Excluded item <databaseName> is not

FMX6033E The option /MOUNTDAtabases=yes valid. It will be ignored.
was specified without /RECOver option.
Explanation: A backup command was issued with
Explanation: A restore command has been issued either the /EXCLUDESG or /EXCLUDEDB option. An
where the option /MOUNTDAtabases=yes but the item specified in the exclude statement is not a valid
option /RECOver was not specified. This is an invalid item. It will be ignored.
combination.
System action: A warning is displayed and processing
System action: Processing Stops continues.
User response: Issue a restore command without User response: Correct the invalid item specified on
/MOUNTDAtabases=yes if you do not intent to apply the exclude option for future operations.
logs.

FMX6065E The mount backup command failed.

FMX6038I Excluding storage group <databaseName> Verify that a valid mount point and
from backup list -- skipping. backup is specified. For more
Explanation: A backup command has been issued information, see the dsmerror.log file.
where the option /EXCLUDESG has been specifed. The Explanation: The mount backup command failed. The
storage group has met the exclude option criteria and backup specified might be mounted. In addition, the
will be skipped from backup. drive to map to might be in use. The directory to
System action: Processing continues, but the specified contain the mount point directories for all snapshots
storage group is skipped. needs to be an empty NTFS directory that does not
contain hidden system files or directories.
User response: None.
System action: Processing stops.
User response: Check to make sure that the backup
specified is not mounted and that the drive to map to

218 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX6066E • FMX6082I

is available. Repeat the command using an empty

FMX6076I <databaseName> cannot be backed up
NTFS directory as the snapshots mount points
because its 'BackupInProgress' flag is set
directory.
to 'True'. Check whether the database is
being backed up by a different server --
FMX6066E The UNMOUNT BACKup command skipping.
failed. The specified backup might not
Explanation: A Database Availability Group (DAG)
be mounted. For more information, see
database is skipped from backup if its
the dsmerror.log file.
'BackupInProgress' flag is set to "True" by Exchange
Explanation: The UNMOUNT BACKup command server.
failed. The specified backup might not be mounted, or
System action: Processing continues, but the specified
there may be a different error.
database is skipped.
System action: Processing stops.
User response: Check whether the database is being
User response: Check to make sure that the backup backed up by a different server. Also check that there is
specified is mounted. If so, see the dsmerror.log file not another instance of tdpexcc.exe or other backup
and take the appropriate action. running.

FMX6067E In the component list that is specified, FMX6080E Conflict option:

the following object is not valid: 'object'.
Explanation: This message displays the command that
Verify the volume and mount point
was entered, up to and including the conflict option
names are correctly identified and
that was detected.
spelled correctly.
System action: Processing ends.
Explanation: The command that is entered includes a
component list. The list of components contains one or User response: Re-enter the command specifying valid
more invalid objects. For example, when entering a command options.
BACKUP or RESTORE command, if the component list
includes a volume or mount point that is not valid or is
FMX6081E Missing, blank, or invalid
not eligible for back up, this message is displayed. In
REMOTEDSMAgentnode is not
addition, the GUID volume name cannot be specified.
allowed. Set the
For RESTORE, MOUNT BACKUP, or DELETE
REMOTEDSMAgentnode option to a
BACKUP commands, this message is displayed if the
valid value and retry the operation.
component list contains a backup specification that is
not found in the backup inventory. Explanation: In order to run VSS operations, Data
Protection for Exchange verifies that the Remote
System action: Processing stops.
DSMAGENT Node Name is specified and valid. This
User response: Verify the correct syntax is used when error indicates that the Remote DSMAGENT Node
entering the command. If the message is displayed Name is missing or blank. Also, the Remote
again, verify the volume and mount point names are DSMAGENT Node Name cannot be the same as the
correctly identified. A misspelling can trigger this Local DSM Agent Node Name.
message.
System action: Processing stops.
User response: Set the REMOTEDSMAgentnode to a
FMX6068I <databaseName> is being backed up by a
valid value and retry the operation.
different server -- skipping.
Explanation: A Database Availability Group (DAG)
FMX6082I The following options are deprecated
database is skipped from backup if another copy of the
and will be ignored: deprecatedOption
same database is being backed up by a different server.
Explanation: The option you entered is deprecated.
System action: Processing continues, but the specified
Data Protection for Exchange ignores the option and
database is skipped.
processing continues.
User response: Check whether the database is being
System action: Data Protection for Exchange ignores
backed up by a different server. Also check that there is
the option and processing continues.
not another instance of tdpexcc.exe or other backup
running. User response: If appropriate, update your scripts to
remove references to any deprecated options.

Chapter 4. FMX messages 219

FMX6083W • FMX6095T

FMX6083W Database <component name> is a recovery FMX6091W The mailbox 'mailboxname' was not
database -- skipping. found in the existing recovery database
Explanation: A request was made to back up a set of Explanation: The parameter USEExistingrdb is set to
databases. However, some databases are recovery YES, but the mailboxes that were specified for the
databases. Recovery databases cannot be backed up. mailbox restore operation are not found in the existing
recovery database.
System action: Processing continues, but the recovery
databases are skipped. System action: The specified mailbox is not restored.
User response: Do not specify recovery databases to User response: Verify that the specified mailbox name
be backed up. is in existing recovery database.

FMX6086W The following values for the FMX6092W An mailbox name which was not found
mailboxfilter option are not supported in the existing recovery database. Verify
and the options are ignored: that the mailbox name is correct. If the
unsupportedfilter specified mailbox name is correct, verify
that it has been in existing recovery
Explanation: The mailboxfilter option entered is not
database.
supported. Data Protection for Exchange ignores the
filter and processing continues. Explanation: The mailboxes specified for the mailbox
restore operation were not found in existing recovery
System action: Data Protection for Exchange ignores
database.
the filter and processing continues.
System action: The specified mailboxes are not
User response: Provide supported value for
restored.
mailboxfilter option
User response: Verify that the specified mailbox name
is in existing recovery database.
FMX6087E The mailbox 'mailboxname' is ambiguous,
multiple mailboxes were found.
FMX6093T Recovery database recovery database name
Explanation: Multiple mailboxes are found for the
exists on the Exchange Server...
specified display name or alias.
Explanation: The /USEEXISTINGRDB value is YES.
System action: Processing ends.
Restore the mailbox using the existing recovery
User response: Specify mailbox GUID for restore and database .
try the operation again.
System action: Processing continues.
User response: no action needed.
FMX6088W DP attempted to delete the temporary
folder 'foldername' from temporary
mailbox, but the operation was only FMX6094E The option KEEPRdb is set to Yes, but
partially successful. The remaining the mailboxes are not in the same
folder contents must be deleted database.
manually.
Explanation: The option KEEPRdb is set to Yes, but
Explanation: DP uses a temporary mail folder to the mailboxes are not in the same database.
perform some mailbox restore operations. After the
System action: Processing ends.
operation completed, DP attempted to delete the
temporary folder, but the operation only partially User response: View any other messages that were
completed. This partial failure may be due to the size displayed. Fix any of the problems indicated and enter
of the mailbox. The MAPI operation deleteFolder the command again.
returned MAPI_W_PARTIAL_COMPLETION.
System action: The temporary folder is partially FMX6095T There is no existing recovery database
removed, and processing continues. found...
User response: Manually delete the temporary folder. Explanation: The /USEEXISTINGRDB value is YES.
but no existing recovery database found.
System action: Processing continues.
User response: no action needed.

220 IBM Tivoli Storage FlashCopy Manager: Messages

 FMX6096T

FMX6096T Existing recovery database recovery

database name is being removed...
Explanation: The /USEEXISTINGRDB value is NO.
Remove the existing recovery database .
System action: Processing continues.
User response: no action needed.

Chapter 4. FMX messages 221

222 IBM Tivoli Storage FlashCopy Manager: Messages
Chapter 5. FMY messages
Messages with prefix FMY are issued by the IBM Tivoli Storage FlashCopy
Manager for Microsoft SQL Server. Tivoli Storage FlashCopy Manager V4.1.1 FMY
messages are listed in ascending numerical order. The complete message is
documented, including message ID, message text, explanation, system action, and
user response.

FMY0003S An internal processing error has FMY0055E Write failure on license file (licensefile).
occurred.
Explanation: An attempt to write to the license file
Explanation: An internal processing error has failed.
occurred.
System action: Processing ends.
System action: Processing ends.
User response: Make sure enough space exists on the
User response: Retry the operation. If this error workstation to write to the license file. If enough space
persists, contact your service representative. exists, run the command again.

FMY0004E An unknown error has been detected. FMY0056E Data in the license file (licensefile) is not
in a valid format.
Explanation: An internal processing error has
occurred that prevents the generation of a message for Explanation: An attempt to read information from the
a return code. license file failed.
System action: Processing continues. System action: Processing ends.
User response: Retry the operation. If this error User response: Install the product again.
persists, contact your service representative.
FMY0057E The checksum in the license file
FMY0005E Out of memory. Stop other processes (licensefile) does not match the license
and try the operation again. string text.
Explanation: The machine has run out of memory. Explanation: An attempt was made to read
information from the license file. The checksum was
System action: Processing continues.
not valid so it appears that the license file is not at the
User response: Close unnecessary processes and try correct level.
the operation again.
System action: Processing ends.
User response: Reinstall the product.
FMY0053E License file (licensefile) could not be
opened.
FMY0058E The 'Try and Buy' license has expired.
Explanation: An attempt to read from the license file
failed. Explanation: This 'Try and Buy' license that was
detected has expired.
System action: Processing ends.
System action: Processing ends.
User response: Install the product again. This ensures
that the correct license file is installed. User response: This product is no longer valid for use.
A valid license must be obtained before running the
product.
FMY0054E Read failure on license file (licensefile).
Explanation: An attempt was made to read from the
FMY0100E Incomplete command:
license file. This attempt failed.
Explanation: This message displays the incomplete
System action: Processing ends.
command that was entered.
User response: Reinstall the product. This will ensure
System action: Processing ends.
that the correct license file is installed.
User response: Re-enter the complete command.

© Copyright IBM Corp. 1995, 2014 223

FMY0101E • FMY0152I

FMY0101E Invalid argument: FMY0133W Could not locate installation directory.

Attempting to continue...
Explanation: This message displays the command that
was entered, up to and including the invalid command Explanation: An attempt was made to read the
or option argument that was detected. registry to determine where the Tivoli Data Protection
application client was installed. This attempt failed.
System action: Processing ends.
System action: Processing will continue with the
User response: Re-enter the command specifying a
command entered.
valid argument for the command or option.
User response: There should be other messages along
with this one. Refer to the other messages to determine
FMY0102E Invalid command:
the problem. If the problem can not be determined, it
Explanation: This message displays the invalid may be necessary to reinstall the application client
command that was entered. code. This will ensure that the registry entries are set
up correctly.
System action: Processing ends.
User response: Re-enter a valid command. FMY0134W Could not locate log directory.
Processing will continue...
FMY0103E Invalid option for the specified Explanation: An attempt was made to read the
command: registry to determine where the Tivoli Data Protection
Explanation: This message displays the command that application client log is located. This attempt failed.
was entered, up to and including the option that was System action: Processing will continue with the
detected as invalid for the command. command entered.
System action: Processing ends. User response: There should be other messages along
User response: Re-enter the command specifying valid with this one. Refer to the other messages to determine
command options. the problem. If the problem can not be determined, it
may be necessary to reinstall the application client
code. This will ensure that the registry entries are set
FMY0104E Invalid option: up correctly.
Explanation: This message displays the command that
was entered, up to and including the invalid option FMY0150I Operation canceled by user.
that was detected.
Explanation: The user has requested that the Data
System action: Processing ends. Protection for Microsoft SQL Server application client
User response: Re-enter the command specifying valid end by entering ctrl-C.
command options. System action: Processing ends.
User response: None
FMY0105E Missing argument:
Explanation: This message displays the command that FMY0151E Errors occurred while processing the
was entered, up to and including the command or request.
option whose required argument is missing.
Explanation: Attempting to process the request
System action: Processing ends. entered, an error occurred.
User response: Re-enter the command specifying a System action: Processing ends.
valid argument for the command or option.
User response: Attempt to determine the source of the
errors from viewing the log file. Correct the problems
FMY0132W Tracing could not be started. Processing and try running the command again.
will continue.
Explanation: A problem prevented tracing from FMY0152I Performance stats: seconds seconds spent
beginning. in apicall API calls
System action: Processing will continue with the Explanation: The indicated number of seconds were
command entered. spent making API calls for the indicated system.
User response: Refer to the other messages that System action: Processing continues.
display with this message to determine the problem.
User response: None

224 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY0153I • FMY0200E

FMY0153I Performance stats: seconds seconds spent FMY0160E An authentication error occurred with
in function your stored Tivoli Storage Manager
password.
Explanation: The indicated number of seconds were
spent the named function. Explanation: You were unable to log on to the Tivoli
Storage Manager server due an authentication error.
System action: Processing continues.
System action: Processing stops.
User response: None
User response: The stored Tivoli Storage Manager
password may have become corrupted. Contact your
FMY0154E The Data Protection for Microsoft SQL
Tivoli Storage Manager server administrator.
Server application client cannot work
with the version of the Tivoli Storage
Manager API you have installed. Please FMY0161E Authentication error. The password
install version version.release.level or entered is not valid. You are not logged
greater. on to the Tivoli Storage Manager server.
Explanation: The version of the Tivoli Storage Explanation: An incorrect password was entered.
Manager API currently installed on the system is older
System action: Processing stops.
than the version used to build the Data Protection for
Microsoft SQL Server application client. User response: Enter the correct Tivoli Storage
Manager password and try again.
System action: Processing ends.
User response: Install a version of the Tivoli Storage
FMY0162E The passwords entered do not match.
Manager API at or later than the indicated level. A
Please enter them again.
copy is distributed with the Data Protection for
Microsoft SQL Server application client. Explanation: An incorrect password was entered.
System action: Processing stops.
FMY0155E The Data Protection for Microsoft SQL
Server application client cannot work User response: Enter the passwords again.
with the release of Tivoli Storage
Manager API you have installed. Please FMY0163E The directory path needs to be
install release version.release.l evel or fully-qualified.
greater.
Explanation: The /intopath option was specified
Explanation: The release of the Tivoli Storage without a fully-qualified path.
Manager API currently installed on the system is older
than the release used to build the Data Protection for System action: Processing stops.
Microsoft SQL Server application client. User response: Enter the command again and specify
System action: Processing ends. a fully-qualified path in the /intopath option.

User response: Install a release of the Tivoli Storage

Manager API at or later than the indicated level. A FMY0167E The fully-qualified file name is too
copy is distributed with the Data Protection for long.
Microsoft SQL Server application client. Explanation: An attempt was made to use a
fully-qualified file name that was too long. This
FMY0156E Could not load the Tivoli Storage attempt failed.
Manager API. System action: Processing ends.
Explanation: The Tivoli Storage Manager API could User response: None
not be loaded.
System action: Processing ends. FMY0200E File (filename) could not be opened for
User response: Ensure the Tivoli Storage Manager API reading.
is correctly installed. Run the Data Protection for Explanation: An attempt was made to open a file for
Microsoft SQL Server application client with the reading. This attempt failed.
/TRACEFLAGS=API /TRACEFILE=filename options
and view the tracefile to determine why it could not be System action: Processing ends.
loaded. Another possible cause is that the TSMAPI.DLL User response: None
does not exist in the system directory. Re-install the
Tivoli Storage Manager API, if this is the case.

Chapter 5. FMY messages 225

FMY0201E • FMY0213E

FMY0201E File (filename) could not be opened for FMY0208E There is not enough disk space for the
writing. operation attempted.
Explanation: An attempt was made to open a file for Explanation: An attempted operation required more
writing. This attempt failed. disk space than was available. The attempt failed.
System action: Processing ends. System action: Processing ends.
User response: None User response: None

FMY0202E Read failure on file (filename). FMY0209E The rename of file (filename1) to
(filename2) failed.
Explanation: An attempt was made to read from a
file. This attempt failed. Explanation: An attempt was made to rename a file.
This attempt failed.
System action: Processing ends.
System action: Processing ends.
User response: None
User response: None
FMY0203E Write failure on file (filename).
FMY0210E The Tivoli Storage Manager high level
Explanation: An attempt was made to write to a file.
qualifier is too long.
This attempt failed.
Explanation: An attempt was made to use a Tivoli
System action: Processing ends.
Storage Manager high level qualifier that was too long.
User response: None This attempt failed.
System action: Processing ends.
FMY0204E File (filename) could not be closed.
User response: None
Explanation: An attempt was made to close a file.
This attempt failed.
FMY0211E The Tivoli Storage Manager low level
System action: Processing ends. qualifier is too long.

User response: None Explanation: An attempt was made to use a Tivoli

Storage Manager low level qualifier that was too long.
This attempt failed.
FMY0205E File (filename) statistics could not be
obtained. System action: Processing ends.
Explanation: An attempt was made to obtain file User response: None
statistics. This attempt failed.
System action: Processing ends. FMY0212E The Tivoli Storage Manager filespace
name is too long.
User response: None
Explanation: An attempt was made to use a Tivoli
Storage Manager filespace name that was too long. This
FMY0206E Directory (directory) could not be created. attempt failed.
Explanation: An attempt was made to create a System action: Processing ends.
directory. This attempt failed.
User response: None
System action: Processing ends.
User response: None FMY0213E The maximum number of objects
allowed per Tivoli Storage Manager
FMY0207E Directory path (directorypath) is too long. transaction is too small.

Explanation: An attempt was made to use a directory Explanation: In order to maintain backup data
path that was too long. This attempt failed. integrity, multiple backup objects are sent to the Tivoli
Storage Manager server in a single transaction. The
System action: Processing ends. Tivoli Storage Manager server has indicated that the
User response: None maximum number of objects allowed per transaction is
less than the minimum required by the Data Protection
for Microsoft SQL Server application client.
System action: Processing ends.

226 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY0214E • FMY0259E

User response: Increase the maximum number of

FMY0219E The Tivoli Storage Manager low level
objects allowed per transaction on the Tivoli Storage
qualifier is invalid.
Manager server and retry the operation.
Explanation: The low level qualifier name or directory
delimeter is invalid.
FMY0214E The backup object's management class
backup copy group does not exist. System action: Processing ends.
Explanation: The Tivoli Storage Manager server has User response: Check that the low level qualifier
indicated that the backup object's management class name length, characters, and directory delimeters are
backup copy group does not exist. valid.
System action: Processing ends.
FMY0256E The password in your Tivoli Storage
User response: Contact your Tivoli Storage Manager
Manager options file has expired. Please
server administrator.
change your password on the Tivoli
Storage Manager server using the
FMY0215E All backup objects do not have the same 'change password' command and then
management class backup copy either change or remove the password
destination. value in your options file.

Explanation: In order to maintain backup data Explanation: Your Tivoli Storage Manager password
integrity, multiple backup objects are sent to the Tivoli has expired. You need to change your password.
Storage Manager server within a single transaction. All
System action: Processing ends.
backup objects within a single transaction are required
to have the same management class backup copy User response: Obtain a new password for your Tivoli
destinations. Storage Manager server; node using the change
password command or by asking your Tivoli Storage
System action: Processing ends.
Manager Administrator to change your password.
User response: Contact your Tivoli Storage Manager
server administrator.
FMY0257E Your password has expired.
Explanation: Your Tivoli Storage Manager password
FMY0216E Unable to obtain space information for
has expired. A new password needs to be obtained.
volume (volumename).
System action: Processing ends.
Explanation: An attempt was made to obtain space
information for a volume. This attempt failed. User response: Obtain a new password for your Tivoli
Storage Manager node using the change password
System action: Processing ends.
command or by asking your Tivoli Storage Manager
User response: None Administrator to change your password.

FMY0217E The Tivoli Storage Manager filespace FMY0258E You did not enter a valid password.
name is invalid. Processing ends.

Explanation: The filespace name or directory Explanation: The password that was entered was not
delimeter is invalid. a valid password.

System action: Processing ends. System action: Processing ends.

User response: Check that the filespace name length, User response: Re-enter the command specifying a
characters, and directory delimeters are valid. valid password.

FMY0218E The Tivoli Storage Manager high level FMY0259E The password you entered for
qualifier is invalid. verification does not match the
password you entered for your new
Explanation: The high level qualifier name or password. Your password will not be
directory delimeter is invalid. changed.
System action: Processing ends. Explanation: The password you entered for
User response: Check that the high level qualifier verification of your new password does not match the
name length, characters, and directory delimeters are new password that was entered.
valid. System action: Processing ends.

Chapter 5. FMY messages 227

FMY0260I • FMY0301E

User response: Try again to change your password User response: It is possible that a default browser is
being sure to enter the same password for the new not defined for the system. This is okay. An attempt
password and for the verification password. will be made to use Microsoft Internet Explorer.

FMY0260I Password successfully changed. FMY0265E Could not find Internet Explorer.
Explanation: The change password command Explanation: An attempt was made to read the
completed successfully registry to determine where Microsoft's Internet
Explorer was installed. This attempt failed.
System action: Processing ends.
System action: Processing ends.
User response: None
User response: Make sure that the registry is set up
correctly for Internet Explorer.
FMY0261I There are no backups for the server
named servername.
FMY0266E Could not find the Tivoli Storage
Explanation: There are no backups on the Tivoli
Manager HTML books.
Storage Manager server for the specified server name.
Explanation: An attempt was made to read the
System action: Processing ends.
registry to determine where the Tivoli Storage Manager
User response: None books were installed. This attempt failed.
System action: Processing ends.
FMY0262E Errors occurred while processing the
User response: It may be necessary to reinstall the
VSS operation. Examine the Windows
application client code. This will ensure that the
Event Logs and DSMERROR.LOG for
registry entries are set up correctly.
additional details.
Explanation: While attempting to process a VSS
FMY0267E The verify password entered does not
operation, an unexpected error occurred.
match the new password entered.
System action: Processing ends.
Explanation: The verify password does not match the
User response: Attempt to determine the source of the new password.
error by examining the Data Protection for SQL log file,
System action: Processing ends.
the TSM Client error log file (DSMERROR.LOG), the
Windows Application Event Log, the Windows System User response: Retry the command with a matching
Event Log, and the VSS provider log file, if applicable. verify password.
Additional instructions for Windows VSS operations
are located in the TSM Problem Determination Guide.
FMY0292E An unknown error has been detected. rc
Correct the problem and retry the operation. If this
= rc
error persists, contact your service representative.
Explanation: An error occured without an error
message. The return code, rc, is displayed.
FMY0263E Failed to start Web browser with a
return code of returncode. System action: Processing ends.
Explanation: An attempt was made to start the web User response: Retry the operation. If this error
browser to view the TSM HTML b ook. This attempt persists, contact your service representative.
failed.
System action: Processing ends. FMY0300E Invalid restore type.
User response: Start your web browser manually and Explanation: The type of restore requested is invalid.
point it to bookfrm.htm in the agent htm directory.
System action: Processing ends.

FMY0264I Could not find the default browser User response: Re-enter the command specifying a
defined. An attempt will be made to use valid restore type.
Microsoft Internet Explorer.
Explanation: An attempt was made to read the FMY0301E Invalid backup type.
registry to determine the default browser. However, a Explanation: The type of backup requested is invalid.
default browser is not defined. A determination will be
made where Microsoft Internet Explorer is installed. System action: Processing ends.

System action: Processing continues.

228 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY0351E • FMY0488E

User response: Re-enter the command specifying a

FMY0383E Specifying the trace file 'link' as a
valid backup type.
symbolic link is not allowed.
Explanation: Trace file 'linkname' cannot be a symbolic
FMY0351E Invalid trace keyword - 'keyword'
link.
Explanation: A TRACEFLAG option in the user
System action: The symbolic link 'linkname' is deleted,
configuration file or on the command line is incorrect.
the trace file is recreated, and processing stops.
System action: Client program did not initialize or
User response: Specify the trace file location with the
tracing was not enabled in the applet.
'tracefile' option.
User response: Correct the value.
FMY0384E Symbolic link 'linkname' to 'target' was
FMY0357E Unable to open trace output file successfully deleted.
file-name.
Explanation: Log 'linkname' cannot be a symbolic link.
Explanation: A TRACEFILE option in the user
System action: The symbolic link 'linkname' is deleted,
configuration file or on the command line used a
the log is recreated, and processing stops.
directory path and file-name combination to which you
do not have write access. User response: Check the location of the new file. To
specify the location of log files, refer to the user's
System action: Client program did not initialize.
manual for the 'errorlogname' option, the
User response: Change the TRACEFILE value so that 'schedlogname' option, and the 'DSM_LOG'
it is a location to which you have write access. environmental variable.

FMY0366E Unable to close trace output file FMY0385E Unable to delete symbolic link 'link'.
file-name.
Explanation: Log 'linkname' cannot be a symbolic link.
Explanation: An error occurred during the closing of a
System action: Processing stops.
trace output file-name (for example, not enough disk
space). User response: Delete the symbolic link 'linkname'.
System action: Processing continues.
FMY0476E program-name: cannot open file file-spec:
User response: Check the options.doc file for a
error.
description of possible causes of the error, or see your
system administrator. Explanation: DP cannot open the file.
System action: DP cannot complete the requested
FMY0367E Unable to write to trace file tracefile. operation.
Tracing disabled.
User response: Retry the operation. If the problem
Explanation: An error occurred when writing to the continues, check with your system administrator.
specified tracefile.
System action: Tracing is disabled. Processing FMY0487E Specifying the error log 'link' as a
continues. symbolic link is not allowed.
User response: Ensure the device that the tracefile Explanation: Error log 'linkname' cannot be a symbolic
access is available and has sufficient space for the link.
tracefile. Retry the command.
System action: The symbolic link 'linkname' is deleted,
the error log is recreated, and processing stops.
FMY0368E Invalid trace file name (name too long).
User response: Check the location of the new error
Explanation: A TRACEFILE option in the preferences log. To specify the location of the error logs, refer to the
files used a file name that is too long. user's manual for the 'errorlogname' option and
'DSM_LOG' environmental variable.
System action: Client program did not initialize.
User response: Change the file name used as the
FMY0488E Initialization functions cannot open the
TRACEFILE so that it is equal to or less than 255
error log: log-name. errno = errno-value,
characters in length.
Explanation: The file log-name could not be opened
during initialization. The system set the error code
errno-value. If the reason given is "access denied," the

Chapter 5. FMY messages 229

FMY0495E • FMY0517I

current user does not have permission to write to the

FMY0498I count log records processed.
log in the directory specified. It is also possible that no
space is available at the given log location. Explanation: This is just a progress report to let you
know the process is still ongoing.
System action: Processing terminates.
System action: Transition processing continues.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory into which the User response: None.
current user can write. You may also use the
ERRORLOGNAME option to specify a file to which the
FMY0501E Invalid Proxy Configuration Detected:
current has write permission.
Target Node 'targetnode' is not listed as a
valid node to proxy to for Node Name
FMY0495E Failure writing to a Tivoli Storage 'nodename'.
Manager log or log-related file: file-name,
Explanation: The proxy node configuration on the
errno = errno-value, reason
TSM Server is not correct to support this VSS
Explanation: A failure was encountered when writing operation.
to one of the log files or a related file named file-name.
System action: The VSS operation stops.
The system set the error code errno-value. reason is the
system explanation of that error code. Among other User response: Contact the TSM Server administrator
things, it is possible that no space is available at the to have the correct TSM Server GRANT PROXY
given log location. commands issued to enable proxy authority for the
nodes. If the error persists, contact your service
System action: Processing terminates.
representative.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory with adequate
FMY0515E Invalid DSMAGENT Node
space to write the log data.
configuration found for node
'dsmagentnode'.
FMY0496I DP is converting the log-file from
Explanation: The DSMAGENT Node specified is not
continuous (pruning) mode to wrapping
configured properly.
mode. This process may take several
minutes. System action: The VSS operation stops.
Explanation: The log-file was previously in continouos User response: Verify that the DSMAGENT Node
mode where the only size control was through the use specified is correct and that the Client Acceptor
of ERRORLOGRETENTION or Daemon (CAD) is running for the DSMAGENT Node.
SCHEDLOGRETENTION option. This is the first If the error persists, contact your service representative.
occasion where ERRORLOGMAX or SCHEDLOGMAX
is specified for this log, so its format must be changed
and old data saved. FMY0516I The Windows console event handler
received a 'event' console event.
System action: Transition processing continues.
Explanation: A console event was received by one of
User response: None. the Data Protection for Microsoft SQL Server processes
or programs. The following events can be recevied:
FMY0497I DP is converting the log-file from v Ctrl-C - This indicates either the user entered the
wrapping mode to continuous (pruning) ctrl-c sequence or that one of the Windows services
mode. This process may take several was stopped.
minutes. System action: None.
Explanation: The log-file was previously in wrapping User response: None.
mode where the size control was through the use of the
ERRORLOGMAX or SCHEDLOGMAX option. This is
the first occasion where ERRORLOGMAX or FMY0517I An unexpected error was encountered.
SCHEDLOGMAX is not specified for this log, so its DP function name : function-name DP
format must be changed and old data saved. function : function-desc DP return code :
TSM-rc DP file : file-name (line-number)
System action: Transition processing continues.
Explanation: None.
User response: None.
System action: Processing stops.
User response: Contact the DP administrator with the
information provided in this message.

230 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY0518E • FMY0571E

user id is performing pruning at the same time.

FMY0518E Backups selected for restore must have
the same backup location (TSM or System action: Pruning stops, processing continues.
LOCAL).
User response: Set the DSM_LOG (or DSMI_LOG)
Explanation: A VSS restore operation was submitted environment variable to a directory into which the
that specified multiple backup objects. The backup current user can write.
objects chosen had different backup locations. This is
not allowed. All backup objects submitted in the same
VSS restore operation must have the same backup FMY0522E DIAG:
location, either TSM or LOCAL, but not both. Explanation: The message text is provided for
System action: The VSS restore operation stops. diagnostic purposes and is meant to provide
information to IBM support in problem determination.
User response: Retry the VSS restore operation
specifying one backup object at a time. System action: None.
User response: None.
FMY0519E The VSS operation failed with rc =
returncode. FMY0524S Error 'errtxt' (errno=errno) occurred
Explanation: There was a failure when TSM trying to write to audit log 'file-name'.
performed the VSS operation. The audit log function is disabled.

System action: The VSS operation stops. Explanation: There was an error encountered writing
to the audit log (for example, there is not enough space
User response: Verify that the TSM Client Acceptor on the disk).
Daemon (CAD) is installed, configured, and running
properly on the machine. Retry the operation. If the System action: Audit logging is disabled for the rest
error persists, contact your service representative. of the operation. The return code for the operation is
set to 12 to indicate that the contents of the audit log
are incomplete.
FMY0520E Failed to connect to Local DSMAGENT
Node 'localdsmagentnode' at address:port User response: If this is an out of space condition
'address:portnumber'. Verify that the TSM either free up space on the volume or try to write the
Client Acceptor Daemon (CAD) is audit log to a volume with more space.
installed, configured, and running
properly. FMY0555E Invalid number of snapshots:
Explanation: An attempt was made to connect to the Explanation:
TSM Client Acceptor Daemon (CAD) running on the
local machine. A communication error occurred when System action: Policy was not created.
this connection was attempted. User response: Specify a number in the range: range:
System action: The operation stops. 1...9999 or NOLimit

User response: In order to perform VSS operations,

you must have a TSM Client Acceptor Daemon (CAD) FMY0556E Invalid number of days:
and a TSM Remote Client Agent Service (DSMAGENT) Explanation:
installed and configured properly. In addition, the TSM
Client Acceptor Daemon (CAD) must be running. System action: The Policy was not created.
Verify that the TSM Client Acceptor Daemon (CAD) is User response: Specify a number in the range: range:
installed, configured, and running properly on the local 0...9999 or NOLimit
machine. If the error persists, contact your service
representative.
FMY0571E The specified policy was not found:
'policy'
FMY0521E Pruning functions cannot open one of
the Tivoli Storage Manager prune files: Explanation:
log-name. errno = errno-value,
System action:
Explanation: The file "log-name" could not be opened
User response: Please make sure that the specified
during pruning. The system set the error code
policy exists.
errno-value. If the reason given is "access denied," the
current user does not have permission to write to the
file in the directory specified. It is also possible that no
space is available at the given file location or another
Tivoli Storager Manager process started by different

Chapter 5. FMY messages 231

FMY0572E • FMY0588E

FMY0572E The specified policy already exists: FMY0583E Invalid name of policy specified. Valid
'policy' input characters include alphanumeric
charaters and underscore.
Explanation:
Explanation:
System action: Policy was not created.
System action: Policy was not created.
User response: Enter a different name for the policy.
User response: Please specify a valid name.
FMY0573E The specified policy could not be
updated: 'policy' FMY0585E Unable to connect to the TSM Client
Acceptor Daemon (CAD).
Explanation: This is due to a problem in virtual server
database. Explanation: Possible causes of this message include:
The TSM Client Acceptor Daemon (CAD) is not
System action:
running. The VSSALTSTAGINGDIR option setting in
User response: Make sure that FCM is configured the TDP option file is not set to the same value as the
correctly. VSSALTSTAGINGDIR option setting in the Data
Protection for Microsoft SQL Server Remote Client
Agent Service (DSMAGENT) option file. They must be
FMY0574E The specified policy could not be set to the same value for successful TDP operations.
deleted: 'policy'
System action: The VSS operation stops.
Explanation: This is due to a problem in virtual server
database. User response: Ensure that the TSM Client Acceptor
Daemon (CAD) is running. Ensure that the
System action: VSSALTSTAGINGDIR option setting in the TDP option
User response: Make sure that FCM is configured file is set to the same value as the
correctly. VSSALTSTAGINGDIR option setting in the Data
Protection for Microsoft SQL Server Remote Client
Agent Service (DSMAGENT) option file. After
FMY0575E The specified policy could not be correcting the VSSALTSTAGINGDIR option
created: 'policy' inconsistency, retry the TDP operation.
Explanation: This is due to a problem in virtual server
database. FMY0588E The value for the BACKUPDESTination
System action: option is not allowed. Data Protection
for Microsoft SQL Server is only
User response: Make sure that FCM is configured licensed to run data protection
correctly. operations to a Tivoli Storage Manager
server. It is not licensed to backup or to
FMY0576I There were no items found. restore locally managed snapshots.

Explanation: The query completed successfully, but no Explanation: The value for the configuration option is
results were found. not allowed. The only allowed value is TSM. Data
Protection for Microsoft SQL Server is only licensed to
System action: None. run data protection operations to a Tivoli Storage
Manager server. It is not licensed to backup or to
User response: Change the specified search criteria.
restore locally managed snapshots.
System action: Processing ends.
FMY0581E Volume volume-name could not be
locked. User response: Set the backup destination to TSM. In
order to create and restore local VSS backups it is
Explanation: The system call to lock the volume
required to use and install a fully-featured valid license
failed.
or to purchase an upgrade, and install Tivoli Storage
System action: Processing stopped. FlashCopy Manager. If you use Data Protection for
Microsoft SQL Server it is also required to purchase
User response: Please verify that no other application
and install IBM Tivoli Storage Manager for Copy
is accessing the volume. During restore of an image DP
Services - Microsoft SQL VSS Integration Module.
must have exclusive use of the volume.

232 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY0589E • FMY0599E

System action: The operation stops.

FMY0589E You are not allowed to set
REMOTEDSMAGentnode option. Data User response: In order to perform offloaded VSS
Protection for Microsoft SQL Server is backups install a valid fully-featured license. If you use
not licensed to perform offloaded VSS Data Protection for Microsoft SQL Server it is also
backups. required to purchase and install IBM Tivoli Storage
Manager for Copy Services - Microsoft SQL VSS
Explanation: The REMOTEDSMAGentnode option is
Integration Module. Contact your service representative
used to perform offloaded VSS backups.
to find out purchase details.
System action: The operation stops.
User response: In order to perform offloaded VSS FMY0594E You cannot perform offloaded VSS
backups install a valid fully-featured license. If you use backups in TSM Server independent
Data Protection for Microsoft SQL Server it is also environment.
required to purchase and install IBM Tivoli Storage
Explanation: OFFLOAD option is not available in
Manager for Copy Services - Microsoft SQL VSS
TSM Server independent environment.
Integration Module. Contact your service representative
to find out purchase details. System action: The operation stops.
User response: In order to perform offloaded VSS
FMY0590E A Data Protection communication error backups you have to configure Tivoli Storage
with the Tivoli Storage Manager server FlashCopy Manager to manage snapshot backups using
has occurred. a Tivoli Storage Manager server. To do this you can use
Tivoli Storage Manager configuration wizard.
Explanation: Communications with the Tivoli Data
Protection server has been lost.
FMY0595E The options file 'optfile' does not exist. It
System action: The operation stops.
is required for proper operation.
User response: Correct the TCP/IP communications
Explanation: The specified TSM API options file could
error with the Tivoli Storage Manager server and retry
not be found. It is required in order to complete the
the operation.
command.
System action: Processing ends.
FMY0591I Data Protection communications with
the Tivoli Storage Manager server has User response: Make sure to complete Tivoli Storage
been successfully recovered. Manager configuration and try the operation again.
Explanation: Communications with the Tivoli Data
Protection server has been successfully recovered. FMY0598E The application cannot run in safe
mode.
System action: None.
Explanation: The application requires either Services
User response: Continue with normal operations.
or Drivers that are not available when running in safe
mode.
FMY0592E The Data Protection TCP/IP session
System action: The application processing stops.
with the Tivoli Storage Manager server
was canceled. User response: Restart the system using the normal
startup. When the system is started, run the
Explanation: The Data Protection TCP/IP session with
application.
the Tivoli Storage Manager server was cancelled.
System action: The operation stops.
FMY0599E The application cannot establish a
User response: Correct the reason the Tivoli Storage remote powershell connection.
Manager server administrator cancelled the session and
Explanation: The application attempted to establish a
retry the operation.
remote powershell connection. The operation failed.
System action: The application processing stops.
FMY0593E Data Protection for Microsoft SQL
Server is not licensed to perform User response: Verify you are using the correct
offloaded VSS backups. credentials. For more information, see the Microsoft
about_Remote_Troubleshooting Help topic.
Explanation: Currently installed license does not allow
to perform offloaded VSS backups. In order to use this
feature it is necessary to install a valid fully-featured
license.

Chapter 5. FMY messages 233

FMY0601E • FMY3006I

FMY0601E There is a problem that causes FMY3002E Data Protection for SQL: backup type
processing to stop. To identify the backup of database database name from
source of the problem and the solution, server server name failed, rc = return code.
look for details in the service level trace
Explanation: This is an informational message written
file.
to the Tivoli Storage Manager Server activity log when
Explanation: This problem occurs when either the a database restore fails.
local or remote Powershell cmdlet or script reports an
System action: None
error. Details about the error are not available until
more trace file information is analyzed. User response: None Centrally logged
System action: Application processing stops.
FMY3003I Data Protection for SQL: Starting restore
User response: To identify the problem, look for
type restore of backup object object name
information in the service level trace files. For more
to database database name on server server
information about viewing trace files, see the
name.
Troubleshooting section of the technical documentation
provided with the software. Explanation: This is an informational message written
to the Tivoli Storage Manager Server activity log when
a restore is started.
FMY0602E While attempting to communicate with
the remote client, a version check System action: None
reveals that the versions do not match.
User response: None Centrally logged
Explanation: During initialization between the local
client and the remote client, version checking reveals
that the versions do not match. This is usually the FMY3004I Data Protection for SQL: restore type
result of an upgrade of one client module without restore of backup object object name to
upgrading other client modules that are part of product database database name on server server
solution. name completed successfully.

System action: The calling procedure returns and Explanation: This is an informational message written
control is passed back the user. to the Tivoli Storage Manager Server activity log when
a database restore completes successfully.
User response: Check the versions of all TSM Client
products that communicate with each other and ensure System action: None
that they are all at the same version, release, and level. User response: None Centrally logged

FMY3000I Data Protection for SQL: Starting backup FMY3005E Data Protection for SQL: restore type
type backup of database database name restore of backup object object name to
from server server name. database database name on server server
Explanation: This is an informational message written name failed.
to the Tivoli Storage Manager Server activity log when Explanation: This is an informational message written
a backup is started. to the Tivoli Storage Manager Server activity log when
System action: None a database restore fails.

User response: None Centrally logged System action: None

User response: None Centrally logged
FMY3001I Data Protection for SQL: backup type
backup of database database name from FMY3006I Data Protection for SQL: Starting
server server name completed backup for server server name.
successfully.
Explanation: This is an informational message written
Explanation: This is an informational message written to the Tivoli Storage Manager Server activity log
to the Tivoli Storage Manager Server activity log when indicating the start of a backup.
a database backup completes successfully.
System action: None
System action: None
User response: None Centrally logged
User response: None Centrally logged

234 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY3007I • FMY3014I

FMY3007I Data Protection for SQL: Backup of FMY3011I Data Protection for SQL: Restore from
server servername is complete. Total SQL server server name to server server name is
backups selected: number selected Total complete. Total database backups
SQL backups attempted: number inspected: number inspected Total
attempted Total SQL backups completed: database backups requested for restore:
number completed Total SQL backups number requested Total database backups
excluded: number excluded Throughput restored: number restored Total database
rate: rate Kb/Sec Total bytes transferred: skipped: number skipped Throughput rate:
bytes Elapsed processing time: time Secs rate Kb/Sec Total bytes transferred: bytes
Elapsed processing time: time Secs
Explanation: This is an informational message written
to the Tivoli Storage Manager Server activity log Explanation: This is an informational message written
indicating the end of a backup request. to the Tivoli Storage Manager Server activity log
indicating the end of a restore.
System action: None
System action: None
User response: None Centrally logged
User response: None Centrally logged
FMY3008I Data Protection for SQL: Backup of
server servername is complete. Total SQL FMY3012I Data Protection for SQL: restore type
backups selected: number selected Total restore of backup object object name to
SQL backups attempted: number database database name from server server
attempted Total SQL backups completed: name canceled by user.
number completed Total SQL backups
Explanation: This is an informational message written
excluded: number excluded Total SQL
to the Tivoli Storage Manager Server activity log
backups inactivated: number inactivated
indicating that a backup request was canceled by the
Throughput rate: rate Kb/Sec Total bytes
user.
transferred: bytes Elapsed processing
time: time Secs System action: None
Explanation: This is an informational message written User response: None Centrally logged
to the Tivoli Storage Manager Server activity log
indicating the end of a backup request.
FMY3013I Data Protection for SQL: Starting
System action: None Inactivate processing for backup objects
from server servername
User response: None Centrally logged
Explanation: This is an informational message written
to the Tivoli Storage Manager Server activity log when
FMY3009I Data Protection for SQL: backup type
an inactivate process begins.
backup of database database name from
server server name canceled by user. System action: None
Explanation: This is an informational message written User response: None Centrally logged
to the Tivoli Storage Manager Server activity log
indicating that a backup request was canceled by the
user. FMY3014I Data Protection for SQL: Inactivate
processing complete Total database
System action: None backups inspected: number inspected Total
database backups requested for
User response: None Centrally logged
inactivation: number requested Total
database backups inactivated: number
FMY3010I Data Protection for SQL: Starting restore inactivated Total database skipped:
for server servername. number skipped Elapsed processing time:
time Secs
Explanation: This is an informational message written
to the Tivoli Storage Manager Server activity log Explanation: This is an informational message written
indicating the start of a restore. to the Tivoli Storage Manager Server activity log to
indicate the end of an inactivate command.
System action: None
System action: None
User response: None Centrally logged
User response: None

Chapter 5. FMY messages 235

FMY3015I • FMY5056I

a fully-qualified path in the /relocatedir option.

FMY3015I Data Protection for SQL: Inactivating
backup type backup backup object.
FMY5050I A new configuration file was created.
Explanation: This is an informational message written
to the Tivoli Storage Manager Server activity log when Explanation: The file specified in the /configfile
an inactivation of a backup object is started. parameter does not exist. A new file was created.
System action: None System action: Processing continues.
User response: None Centrally logged User response: None.

FMY3016I Data Protection for SQL: Database FMY5051I The configuration file cannot be found,
database name from server server name is using default settings.
excluded from backup type backup
because it has a Simple Recovery model Explanation: The file specififed in the /configfile
or it is a system master database. parameter cannot be found.

Explanation: This is an informational message written System action: Processing continues.

to the Tivoli Storage Manager Server activity log when User response: Ensure the correct file name is
a Simple Recovery model database or a system master specified.
database is automatically excluded from a Data
Protection for SQL backup.
FMY5052E An error occurred trying to set the
System action: None requested configuration option.
User response: None Centrally logged Explanation: An error occurred while writing to the
configuration file.
FMY3528E Data Protection for Microsoft SQL System action: Processing ends.
Server is only licensed to run data
protection operations to a Tivoli Storage User response: View any other messages that were
Manager server. It is not licensed to displayed. After reviewing the messages and
backup or to restore using locally performing necessary actions, run the command again.
managed snapshots.
Explanation: Currently installed license allows to FMY5053E The value for the option option is not
create and restore only TSM VSS backups. In order to valid. See the TDPSQLC Help Set
create backups and to restore local VSS backups, Data output or the User's Guide for valid Set
Protection for SQL requires that a valid fully-featured command parameters.
license is installed. Explanation: The configuration option being set is not
System action: The operation stops. valid.

User response: In order to create and restore local VSS System action: Processing ends.
backups it is required to purchase and install a User response: Run "TDPSQLC Help Set" or refer to
fully-featured valid license. NOTE: If you use Data the User's Guide for valid Set command parameters.
Protection for Microsoft SQL Server it is also required
to use and install IBM Tivoli Storage Manager for Copy
Services - Microsoft SQL VSS Integration Module or to FMY5054I The configuration option was set
purchase an upgrade, and install Tivoli Storage successfully.
FlashCopy Manager. If IBM Tivoli Storage Manager for Explanation: The configuration option specified on the
Copy Services - Microsoft SQL VSS Integration Module Set command was set successfully.
is installed, there will be a license file, \"acssql.lic\", in
the Data Protection for Microsoft SQL Server System action: Processing ends.
installation directory.
User response: None

FMY3532E The restore destination directory path

FMY5056I The logfile log file could not be pruned.
needs to be fully-qualified.
Processing will continue.
Explanation: The /relocatedir option was specified
Explanation: An attempt to prune the log was
without a fully-qualified path.
unsuccessful.
System action: Processing stops.
System action: Processing continues.
User response: Enter the command again and specify
User response: The log file may not exist. If the log

236 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY5057I • FMY5091E

file exists, view the log for indications of possible

FMY5063I The logfile_name log file did not need
problems.
pruning.
Explanation: The log file specified did not need to be
FMY5057I The logfile log file was pruned
pruned.
successfully.
System action: Processing continues.
Explanation: The log file mentioned pruned
successfully. User response: The log file will automatically be
pruned at a later date. If the log file is currently too
System action: Processing continues.
large, decrease the number of days the log entries are
User response: None. retained.

FMY5058W The logfile name is greater than the FMY5064W The logfile_name log file could not be
maximum allowed. Processing will opened for writing. The log was not
continue using a logfile name of logfile pruned and there will be no logging of
in the current directory. events.

Explanation: The logfile name entered was not fully Explanation: The log mentioned could not be opened
qualified. When the fully qualified log file name was for appends. Therefore, no logging or pruning is
created, it was longer than the possible length of a log performed.
file.
System action: Processing continues without logging
System action: Processing continues by creating and and without pruning.
using a log file in the current directory.
User response: Determine why the log file could not
User response: Consider updating the log file name be opened. The log file may refer to a non-existent
using a fully qualified path. drive or partition, or the log file is marked read-only.

FMY5059W The logfile log file cannot be opened for FMY5065E The value specified for the /SQLUSer
writing. There will be no logging of option does not match the registry entry.
events.
Explanation: A Backup, Restore or Query Sql
Explanation: The log mentioned could not be opened command was issued with both the
for appends. Therefore, no logging is performed. /SQLAUTHentication=SQLUserid and the /SQLUSer
option specified. An attempt was made to obtain the
System action: Processing continues without logging. sqlpassword value from the registry but the user ID in
User response: Determine why the log file could not the registry does not match the user ID specified with
be opened. The log file may refer to a non-existent the /sqluser option.
drive or partition, or the log file is marked read-only. System action: Processing ends.
User response: Issue the command and either specify
FMY5060E A Tivoli Storage Manager API error has the /sqluser value which matches the registry entry or
occurred. specify the desired values for both the /sqluser and
Explanation: A Tivoli Storage Manager API error has /sqlpassword options on the command.
occurred.
System action: Processing ends. FMY5091E PASSWORDACCESS is Generate. Either
the stored password is incorrect or there
User response: Retry the operation. If the error is no stored password. If you do not
persists, contact your service representative. have a stored password, use the
-TSMPassword=xxx option to set and
FMY5061E A Microsoft SQL API error has occurred. store your password.

Explanation: A Microsoft SQL API error occurred. Explanation: The PASSWORDACCESS option is set to
generate in the client options file. However, no
System action: Processing ends. password is stored. An initial password needs to be
User response: Retry the operation. If the error stored.
persists, contact your service representative. System action: Processing ends.
User response: Invoke the command again using the
-TSMPassword option. Any subsequent commands
should now complete without specifying a password.

Chapter 5. FMY messages 237

FMY5097I • FMY5129E

FMY5097I Data Protection for SQL is not FMY5126E Invalid command. Data Protection for
configured for VSS operations. SQL only supports Legacy backups with
a backup destination of TSM.
Explanation: Data Protection for SQL has not been
configured to perform VSS operations. Explanation: An invalid backup destination was
specified with the Legacy backup method. Data
System action: None.
Protection for SQL only supports a backup destination
User response: In order to perform VSS operations, of TSM when using the Legacy backup method.
there must be a valid Tivoli Storage Manager Advanced
System action: The backup operation is canceled.
Copy Services license installed and the Data Protection
for SQL LOCALDSMAGENTNODE preference must be User response: Retry the backup operation specifying
set correctly. Refer to the Data Protection for SQL User's a backup destination of TSM.
Guide for details on configuring the client for VSS
operations.
FMY5127E Invalid command. Data Protection for
SQL does not support OFFLOAD with
FMY5098E Error obtaining VSS information from the combination specified for backup
Local DSMAgent Node: destination and version of Windows.
'localdsmagentnode'.
Explanation: The OFFLOAD option was specified
Explanation: Data Protection for SQL attempted to with an unsupported backup destination. Data
obtain VSS information through the specified Protection for SQL only supports offload with a backup
LOCALDSMAGENTNODE but failed. The error destination of TSM or if running on a Windows System
message encountered is also displayed. 2008 or later, backup destination TSM or BOTH.
System action: VSS information is not displayed. System action: The backup operation is canceled.
User response: Refer to the error message displayed User response: Retry the VSS offloaded backup
along with this message. operation specifying a backup destination of TSM.

FMY5124E Invalid command. Data Protection for FMY5128E The VSS operation failed with rc =
SQL only supports VSS backup type of returncode.
FULL.
Explanation: There was a failure when Data Protection
Explanation: An invalid backup type was specified on for SQL performed the VSS operation.
the VSS backup request. Data Protection for SQL
System action: The VSS operation stops.
supports backup types of FULL when using the VSS
backup method. User response: Verify that the Client Acceptor
Daemon (CAD) is installed, configured, and running
System action: The backup operation is canceled.
properly on the machine. Retry the operation. If the
User response: Retry the backup operation specifying error persists, contact your service representative.
a supported VSS backup type.
FMY5129E Data Protection for SQL is unable to run
FMY5125E Invalid command. Data Protection for VSS operations. A valid VSS license file
SQL does not support OFFLOAD with (acssql.lic) could not be located.
the Legacy backup method.
Explanation: In order to perform VSS operations, it is
Explanation: The OFFLOAD option was specified required that valid license files for both Data Protection
when using the Legacy backup method. Data for SQL and IBM Tivoli Storage Manager for Copy
Protection for SQL does not support offload with the Services - Microsoft SQL VSS Integration Module are
Legacy backup method. Data Protection for SQL installed. If IBM Tivoli Storage Manager for Copy
supports offload with the VSS backup method only. Services - Microsoft SQL VSS Integration Module is
installed then there will be a license file, acssql.lic, in
System action: The backup operation is canceled.
the Data Protection for SQL installation directory.
User response: Retry the backup operation without
System action: The operation stops.
specifying the offload option or by specifying the VSS
backup method. User response: Verify that the prerequisites identified
above are met and retry the operation. If the error
persists, contact your service representative.

238 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY5170E • FMY5195I

return any selectable backup components for the

FMY5170E Missing, blank, or invalid Local
specified database(s).
DSMAGENT Node Name is not
allowed. System action: Backup fails, processing ends.
Explanation: In order to run VSS operations, Data User response: Ensure that the SQL Server VSS writer
Protection for SQL verifies that the Local DSMAGENT service has been started and that service start type is
Node Name is specified and valid. This error indicates set to automatic.
that the Local DSMAGENT Node Name is missing,
blank, or invalid.
FMY5187E Multiple backup objects with
System action: The operation stops. conflicting backup desitinations were
found for one or more of the specified
User response: Set the Local DSMAGENT Node
database(s). The /OBJECT and/or
Name to a valid value and retry the operation.
/BACKUPDESTINATION options
should be used to restore a specific
FMY5171E Invalid command. Data Protection for database.
SQL only supports restoring VSS
Explanation: The backup object specified for the VSS
backup types of FULL and COPY.
restore operation was not specific enough to be unique.
Explanation: An invalid backup type was specified on More information is required in order to restore the
the VSS restore request. Data Protection for SQL correct backup object.
supports restoring backups of type FULL and COPY.
System action: The restore operation is canceled.
System action: The restore operation is canceled.
User response: Retry the restore operation specifying
User response: Retry the restore operation specifying the /OBJECT= and /BACKUPDESTINATION
a supported VSS backup type. parameters.

FMY5172E Invalid command. Data Protection for FMY5188E BOTH may not be specified for
SQL VSS restore does not support /BACKUPDESTINATION, only TSM or
RESTOREDATE and RESTORETIME LOCAL are valid.
options.
Explanation: The restore command only allows
Explanation: An invalid option was specified on the specifying backup destinations of TSM or LOCAL for
VSS restore request. Data Protection for SQL identifying database(s) to restore.
RESTOREDATE and RESTORETIME options are not
System action: The restore operation is canceled.
supported for VSS restore.
User response: Retry the restore operation specifying
System action: The restore operation is canceled.
TSM or LOCAL with /BACKUPDESTINATION
User response: Retry the restore operation without parameters.
specifying RESTOREDATE and RESTORETIME options.
FMY5195I Data Protection for SQL: Backup of
FMY5177E Invalid DSMAGENT Node server servername enhanced statistics.
configuration found for node Total SQL backups deduplicated: number
'dsmagentnode'. deduplicated Throughput rate: rate Kb/Sec
Total bytes inspected: bytes inspected
Explanation: The DSMAGENT Node specified is not
Total bytes transferred: bytes Total
configured properly.
LanFree bytes transferred: lanfree bytes
System action: The VSS operation stops. Total bytes before deduplication:
prededup bytes Total bytes after
User response: Verify that the DSMAGENT Node deduplication: postdedup bytes Data
specified is correct and that the Client Acceptor compressed by: compression ratio%%
Daemon (CAD) is running for the DSMAGENT Node. Deduplication reduction: deduplication
If the error persists, contact your service representative. ratio%% Total data reduction ratio:
reduction ratio%% Elapsed processing
FMY5186E The VSS writer didn't return any time: time Secs
selectable backup components for the Explanation: This is an informational message written
specified database(s). Ensure that the to the Tivoli Storage Manager Server activity log
SQL Server VSS writer service has been displaying additional statistics at the end of a backup
started. request.
Explanation: The SQL Server VSS writer service didn't System action: None

Chapter 5. FMY messages 239

FMY5196I • FMY5402E

User response: None Centrally logged User response: You should perform a FULL backup of
the database.
FMY5196I Data Protection for SQL: Backup of
server servername is complete. Total SQL FMY5204E None of the specified databases exist, or
backups selected: number selected Total are available for backup.
SQL backups attempted: number
Explanation: A request was made to backup databases
attempted Total SQL backups completed:
which do not exist, or are not available.
number completed Total SQL backups
excluded: number excluded Total SQL System action: Processing ends.
backups deduplicated: number
deduplicated Throughput rate: rate Kb/Sec User response: Ensure that all of the databases exist
Total bytes inspected: bytes inspected and are available, and restart the backup.
Total bytes transferred: bytes Total
LanFree bytes transferred: lanfree bytes FMY5205E The command is not valid. Data
Total bytes before deduplication: Protection for SQL supports restoring
prededup bytes Total bytes after the VMVSS FULL backup type.
deduplication: postdedup bytes Data
compressed by: compression ratio%% Explanation: When the VMVSS restore request is
Deduplication reduction: deduplication entered, an invalid backup type is specified. The FULL
ratio%% Total data reduction ratio: backup type is supported with Data Protection for SQL
reduction ratio%% Elapsed processing restore backups.
time: time Secs System action: The restore operation is canceled.
Explanation: This is an informational message written User response: Start the restore operation after you
to the Tivoli Storage Manager Server activity log specify a supported VMVSS backup type.
indicating the end of a backup request.
System action: None FMY5400E The Virtual Device Interface is not
User response: None Centrally logged registered with the Common Object
Model.

FMY5197I Data Protection for SQL: Restore from Explanation: The virtual device interface could not be
server server name to server server name is created because it is not registered with the common
complete. Total database backups object model. The SQL server may not be installed
inspected: number inspected Total properly.
database backups requested for restore: System action: Processing ends.
number requested Total database backups
restored: number restored Total database User response: Verify that the SQL server is installed
skipped: number skipped Throughput rate: properly and retry the operation. Contact your service
rate Kb/Sec Total bytes transferred: bytes representative if the error persists.
Total LanFree bytes transferred: lanfree
bytes Elapsed processing time: time Secs FMY5401E The Virtual Device Interface could not
Explanation: This is an informational message written be created.
to the Tivoli Storage Manager Server activity log Explanation: The virtual device interface could not be
indicating the end of a restore. created. The SQL server virtual device interface log or
System action: None Windows NT event log may contain more information.

User response: None Centrally logged System action: Processing ends.

User response: If the SQL server messages do not
FMY5198W WARNING: The LOG backup of the resolve the problem, retry the operation. Contact your
'database' database failed, however, the service representative if the error persists.
log may have been truncated. You
should perform a FULL backup of the FMY5402E The Virtual Device Set could not be
database. created.
Explanation: The LOG backup of the database failed, Explanation: The virtual device set could not be
however, the log may have been truncated. You should created. The SQL server virtual device interface log or
perform a FULL backup of the database. Windows NT event log may contain more information.
System action: Processing continues. System action: Processing ends.

240 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY5403E • FMY5424E

User response: If the SQL server messages do not

FMY5407E The SQL server aborted the operation.
resolve the problem, retry the operation. Contact your
service representative if the error persists. Explanation: The SQL server aborted the operation on
the selected database. The SQL server virtual device
interface log, SQL server activity log, SQL server error
FMY5403E The configuration of the Virtual Device
log, or Windows NT event log may contain more
Set could not be obtained.
information.
Explanation: The configuration of the virtual device
System action: Processing ends.
set could not be obtained. The SQL server virtual
device interface log, SQL server activity log, SQL server User response: If the SQL server messages do not
error log, or Windows NT event log may contain more resolve the problem, retry the operation. Contact your
information. service representative if the error persists.
System action: Processing ends.
FMY5420E
User response: If the SQL server messages do not help
resolve the problem retry the operation. If the error Explanation: A SQL API error has occurred.
persists, contact your service representative.
System action: Processing for this operation ends.
User response: If the SQL server messages do not
FMY5404E The Virtual Device Set could not open a
resolve the problem, retry the operation. Contact your
virtual device.
service representative if the error persists.
Explanation: The virtual device set could not open a
virtual device. The SQL server virtual device interface
FMY5421E Received the following from the MS
log, SQL server activity log, SQL server error log, or
COM component: SQL message
Windows NT event log may contain more information.
Explanation: A SQL error has occurred.
System action: Processing ends.
System action: Processing for this operation ends.
User response: If the SQL server messages do not
resolve the problem, retry the operation. Contact your User response: If the SQL server messages do not
service representative if the error persists. resolve the problem, retry the operation. Contact your
service representative if the error persists.
FMY5405E An unknown virtual device error has
been detected. FMY5422E Received the following from the MS
SQL server: SQL message
Explanation: A virtual device returned and unknown
return code.\n" The SQL server virtual device interface Explanation: A SQL error has occurred.
log, SQL server activity log, SQL server error log, or
Windows NT event log may contain more information. System action: Processing for this operation ends.

System action: Processing ends. User response: If the SQL server messages do not
resolve the problem, retry the operation. Contact your
User response: If the SQL server messages do not service representative if the error persists.
resolve the problem, retry the operation. Contact your
service representative if the error persists.
FMY5423E The following string is too long: string

FMY5406E The SQL server closed a virtual device Explanation: A SQL error has occurred.
prematurely. System action: Processing for this operation ends.
Explanation: The SQL server aborted the operation on User response: If the SQL server messages do not
the selected database. The SQL server virtual device resolve the problem, retry the operation. Contact your
interface log, SQL server activity log, SQL server error service representative if the error persists.
log, or Windows NT event log may contain more
information.
FMY5424E Could not connect to SQL server; SQL
System action: Processing ends. server returned: SQL message
User response: If the SQL server messages do not Explanation: A SQL error has occurred.
resolve the problem, retry the operation. Contact your
service representative if the error persists. System action: Processing for this operation ends.
User response: If the SQL server messages do not
resolve the problem, retry the operation. Contact your
service representative if the error persists.

Chapter 5. FMY messages 241

FMY5425E • FMY5434E

FMY5425E The SQL server is not running: SQL FMY5430E The SQL Server Name is blank or
message NULL.
Explanation: A SQL error has occurred. Explanation: In the query to obtain the SQL Server
Name, the system returned a blank name. A valid SQL
System action: Processing for this operation ends.
Server Name is necessary to continue the operation.
User response: Start the SQL server and retry the
System action: Processing for the current operation
operation.
ends.
User response: Check the SQL Server Name by using
FMY5426E The SQL log on does not have the
the "select @@servername" command from the SQL
Sysadmin role: SQL message
Query Analyzer. If that returns NULL, use the
Explanation: An attempt was made to logon to the "sp_addserver" stored procedure to set the SQL Server
SQL server but the specified logon name does not have Name to the correct value. After setting the SQL Server
the Sysadmin role. Name, retry the operation. Contact your service
representative if the error persists.
System action: Processing for this operation ends.
User response: Try the operation again and specify FMY5431E Multiple dbnames are not allowed.
either a log on name with the Sysadmin role or change
the specified log on name to have the Sysadmin role. Explanation: An invalid RESTORE command was
issued. It is not valid to specify multiple database
names in the <dbname> parameter list when using the
FMY5427E The SQL server version is less than 7.0: /STANDBY, /RELOCATE, or /INTO options.
SQL message
System action: Processing ends.
Explanation: An attempt was made to use Data
Protection for SQL Server V2 with a SQL server version User response: Enter the command again with a valid
earlier than the version 7.0 level. This is not allowed. value in the positional parameter or option.
System action: Processing for this operation ends.
FMY5432E Equal numbers of the /RELOCATE and
User response: Use the Data Protection for SQL V1 /TO options must be specified.
client with SQL server earlier than the version 7.0 level,
or retry the operation with a SQL server verison 7.0 or Explanation: Unequal numbers of the /RELOCATE
later. and /TO options were specified on a RESTORE
command.

FMY5428E The SQL server is not on the local System action: Processing ends.
machine: SQL message
User response: Re-enter the command specifying the
Explanation: An attempt was made to use the same number of /RELOCATE and /TO options.
application client specifying a SQL server that was not
on the local machine.
FMY5433E Wildcards are not allowed as part of the
System action: Processing for this operation ends. following parameters/options:

User response: Retry the operation on the machine Explanation: This message displays the positional
where the SQL server resides. parameters and/or options that were specified
incorrectly.

FMY5429E Could not obtain an event from SQL System action: Processing ends.
server: SQL message
User response: Re-enter the command specifying the
Explanation: A SQL error has occurred. correct parameters and/or options.

System action: Processing for this operation ends.

FMY5434E The following options cannot be
User response: If the SQL server messages do not specified together:
resolve the problem, retry the operation. Contact your
service representative if the error persists. Explanation: This message displays the conflicting
command options that were entered.
System action: Processing ends.
User response: Re-enter the command specifying valid
command options.

242 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY5435E • FMY5456W

FMY5435E This command requires one of the FMY5453E The number of TSM sessions (number of
following options: TSM sessions) is invalid for the specified
number of stripes (number of stripes).
Explanation: This message displays the options that
Processing will continue with the
were missing from the command entered.
number of TSM sessions (number of TSM
System action: Processing ends. sessions) as the number of stripes.

User response: Re-enter the command specifying one Explanation: An invalid number of TSM sessions was
of the command options required by the command. detected for the specified number of stripes. This
message is caused by the circumvention of an internal
error.
FMY5436E A failure occurred on stripe number
(stripe number), rc = return code System action: Processing continues utilizing the
number of TSM sessions as the number of stripes.
Explanation: A failure occurred on the numbered
stripe. User response: Try the operation again. Contact your
service representative if this error persists.
System action: Processing ends.
User response: There should be other messages along FMY5454E The maximum number of objects
with this one. Refer to the other messages to determine allowed per TSM transaction (number of
the problem. objects allowed per TSM transaction) is
invalid for the specified number of
FMY5450E The specified number of stripes (number stripes (number of stripes). Processing will
of stripes) is invalid. Processing will continue with (new number of stripes)
continue with the maximum number of stripes.
stripes (maximum number of stripes). Explanation: The maximum number of objects
Explanation: An invalid number of stripes was allowed per TSM transaction is invalid for the specified
specified. number of stripes for at least one of the TSM sessions.
All TSM sessions must allow at least one more object
System action: Processing continues utilizing the per TSM transaction than the number of stripes
allowed maximum number of stripes.
System action: Processing continues utilizing the new
User response: None number of stripes.
User response: Reduce the number of stripes. You can
FMY5451E A failure occurred on vdev (vdev name), also update the TSM server to increase the maximum
rc = return code number of logical files that a client can send to the
Explanation: A failure occurred on the named virtual server in a single transaction (TxnGrpMax).
device.
System action: Processing ends. FMY5455E The backup is corrupt and can not be
restored.
User response: There should be other messages
displayed with this message. Refer to the other Explanation: The backup being restored is corrupt
messages to determine the problem. because the data object or objects found do not
correspond to the metadata.

FMY5452E Unable to delete temporary object: System action: Processing ends.

(filespace name) (high level qualifier) (low User response: Try the operation again. Contact your
level qualifier) service representative if the error persists.
Explanation: When a backup fails, the DP agent
attempts to delete all temporary backup data objects FMY5456W The backup is corrupt and is not fully
from the TSM server. This message indicates that the restorable. Processing will continue.
specified temporary backup data object could not be
deleted from the TSM server. This error is usually Explanation: The backup being restored is corrupt
caused by the loss of all TSM server sessions. because the data object or objects found do not
correspond to the metadata. Depending on the restore
System action: Processing continues. command and the backup type, a partial restore may
User response: None. A backup of the database be possible.
should detect the temporary backup data object and System action: Processing continues.
delete it from the TSM server.
User response: Try the operation again. Contact your

Chapter 5. FMY messages 243

FMY5457E • FMY5616W

service representative if the error persists. User response: Try the operation again. Contact your
service representative if this error persists.
FMY5457E An unknown SQL API error has
occurred. FMY5501E The Common Object Model (COM)
library failed to initialize.
Explanation: A SQL API error has occurred but the
associated error message could not be found. The SQL Explanation: The unsuccessful call was
server activity log, SQL server error log, or Windows CoInitializeEx(NULL,COINIT_MULTITHREADED).
NT/2000 event log may contain more information. OLE32.dll or another COM dll may be missing,
down-level, or corrupted.
System action: Processing ends.
System action: Processing for this database ends.
User response: If the SQL server messages do not
resolve the problem, try the operation again. Contact User response: Verify your Windows NT (version 4 or
your service representative if the error persists. later) installation is complete and try the operation
again. Contact your service representative if this error
persists.
FMY5458W The TSM Server 'backup delete' setting
for node (TSM server NODENAME) is set
to NO. It should be set to YES for FMY5550I There are no backups matching the
proper operation. Processing will filespec directorypathfilename and the
continue. server name servername.
Explanation: The TSM Server setting that allows TSM Explanation: There are no database backups on the
clients to delete their own backups is set to NO for the Tivoli Storage Manager server for the specified server
specified NODENAME. This valuemust be set to YES name.
in order for cleanup operations to perform successfully.
System action: Processing ends.
A NO value means that unusable residual data may be
stored on the TSM Server. User response: None
System action: Processing continues.
FMY5551I There are no backups matching the
User response: Make sure the 'backup delete' setting
criteria specified for server name
for the specified NODENAME is set to YES on the TSM
servername.
Server. Your TSM Server administrator can change this
setting for your NODENAME. The setting can only be Explanation: There are no database backups on the
changed on the TSM Server. Tivoli Storage Manager server matching the query
criteria for the specified server name.
FMY5459W Database object name excluded from System action: Processing ends.
backup.
User response: Specify a broader range of search
Explanation: The specified database was excluded criteria when issuing this query.
from backup by the /EXCLUDEDB setting.
System action: Database isn't backed up. FMY5552I No matches were found for the criteria
specified.
User response: None.
Explanation: The SQL Server was searched for
databases that matched the specified criteria.
FMY5460W Database object object name doesn't exist
or isn't valid. System action: Processing ends.
Explanation: The specified backup object doesn't exist User response: Check the specified search criteria
or isn't valid. (database name, group name, logical filename). Enter
the command again.
System action: Processing for this backup object ends.
User response: Make sure the specified backup object
FMY5616W Database cannot be backed up because
exists.
its name contains '\', '?', '*', or ':'
character(s).
FMY5500E The MultiByteToWideChar() function
Explanation: Databases whose names contain
failed.
directory or volume separator cannot be backed up or
Explanation: This is an internal error that indicates restored.
corrupted storage.
System action: Database was excluded from backup.
System action: Processing for this database ends.

244 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY5617I • FMY5720I

User response: Rename the database and restart

FMY5716W An error was encountered with Tivoli
backup.
Storage Manager API initialization, rc =
returncode. Examine the dsierror.log for
FMY5617I Database was excluded from backup more information or determine if the
because database name contains '\', '?', TSM API is installed properly.
':' or '*' character(s).
Explanation: Errors were encountered during an
Explanation: Databases whose names contain attempt to run setup for the Tivoli Storage Manager
directory or volume separator cannot be backed up or API.
restored.
System action: Processing continues.
System action: Database was excluded from backup.
User response: Examine the dsierror.log file to
User response: Rename the database and restart determine the problem. If this file does not exist, the
backup. TSM API may not be installed properly. If the TSM API
is not installed properly, install the TSM API and run
the command again.
FMY5629E No Backups have been selected for
restore.
FMY5717E Unable to log on to the SQL server.
Explanation: The Restore button was pressed but
nothing was selected in the tree or list view. Explanation: An error occurred while trying to log on
to the SQL server.
System action: Processing stops.
System action: If running the client from the
User response: Make a selection in the tree or list command line, the client ends. If running the client
view and press the Restore button again. from the GUI, a prompt is displayed to enter the SQL
user ID and password, or to choose Windows
FMY5630E Backups from multiple Server instances authentication.
have been selected for restore. User response: Make sure the SQL server is running.
Explanation: The Restore button was pressed and the
user has selected backups from multiple server FMY5718I When the view is refreshed all
instances. selections will be lost and an attempt
System action: Processing stops. will be made to expand the new tree to
the currently highlighted item. Do you
User response: Make a selection in the tree for want to continue?
backups belonging to the same server instance only
Explanation: The refresh toolbar button or pulldown
menu item has been selected.
FMY5631E Restoring full Legacy backups and full
VSS backups in the same restore System action: Processing continues.
operation is not supported. Retry the User response: Select Yes to refresh the view or select
restores in separate operations. No to leave the current view unchanged.
Explanation: At least one VSS backup object and one
Legacy backup object were selected for a restore in the FMY5719I There are currently no backups on TSM.
same operation. This is not supported.
Explanation: The SQL server name expansion button
System action: The restore operation is canceled. was pressed on the Inactivate page.
User response: Retry the restores specifying the System action: Processing stops.
Legacy backups and VSS backups in separate
operations. User response: Either nothing was backed up to a
TSM server or all active backups were inactivated.
FMY5715E Error writing option_name preference to
the configuration file. FMY5720I No databases have been selected for
backup.
Explanation: Could not write the specified preference
to the configuration file. Explanation: The Backup button was pressed on the
GUI but no databases were selected from the tree or
System action: Preferences processing ends. list.
User response: Make sure you have a valid System action: Processing stops.
configuration file, then try to update the preference
again.

Chapter 5. FMY messages 245

FMY5721I • FMY5959E

User response: Select a database and press the Backup

FMY5805W The SQL Server you are restoring from
button again.
is different than the SQL server you are
currently logged on to. Do you want to
FMY5721I No backups have been selected for continue?
restore.
Explanation: Processing continues.
Explanation: The restore button was pressed on the
System action: None
GUI but no backup objects were selected from the tree
or list. User response: If you want to restore something from
a different SQL server, press OK; otherwise press
System action: Processing stops.
Cancel and log on to the other SQL server.
User response: Select a backup object and press the
Restore button again.
FMY5915E An attempt to query detailed managed
capacacity failed.
FMY5722I No backups have been selected for
Explanation:
inactivate.
System action:
Explanation: The Inactivate button was pressed on the
GUI but no backup objects were selected from the tree User response:
or list.
System action: Processing stops. FMY5929E An attempt to query total managed
capacacity failed.
User response: Select a backup object and press the
Inactivate button again. Explanation:
System action:
FMY5723E A named mark must be specified.
User response:
Explanation: The "Stop At Mark" or "Stop Before
Mark" option was chosen but the named mark was not
FMY5958W The selected database <> is offline --
specified.
skipping.
System action: Processing stops.
Explanation: A request was made to backup a
User response: Enter a named mark or choose the database which is offline.
"Stop At" option.
System action: Processing continues, but offline
databases are skipped.
FMY5784E A log must be selected to use point in
User response: Ensure that the selected databases are
time.
online and retry the backup.
Explanation: A log must be selected before setting
point in time parameters.
FMY5959E Unable to run data protection operations
System action: Processing stops. to a FlashCopy Manager virtual server.
A valid FlashCopy Manager license file
User response: Select at least one log for restore
could not be located.
before specifying a point in time.
Explanation: In order to perform data protection
operations to a FlashCopy Manager virtual server, a
FMY5804I Unable to get information. If data is
valid license for FlashCopy Manager must be installed
backed up to tape check the "Wait for
in the FlashCopy Manager installation directory. This
Tape Mounts for File Information"
license file is named fcmclient.lic.
checkbox.
System action: The operation stops.
Explanation: Processing stops.
User response: Verify that the prerequisites identified
System action: None
above are met and retry the operation. If the error
User response: Try checking the box specified in the persists, contact your service representative.
message.

246 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY5960E • FMY6067E

User response: Specify the correct logical name and

FMY5960E This product is not licensed to run data
retry the operation.
protection operations to a Tivoli Storage
Manager server. A valid DP for SQL
license file could not be located. With FMY5969E Database state does not allow backup
the current licenses only data protection log tail.
operations to a Flash Copy Manager
virtual server can be run. Explanation: Database status is not Normal. By now
we only support backup the tail of the log when
Explanation: In order to perform data protection database is not offline or damaged.
operations to a Tivoli Storage Manager server, a valid
license for TDP for SQL (called sqlclient.lic) must be System action: The backup operation failed.
installed. The TDP for SQL license should be installed User response: Back up the tail of the log when
in the TDP for SQL installation directory. database status is normal.
System action: The operation stops.
User response: Verify that the prerequisites identified FMY6060I No matched backup is found according
above are met and retry the operation. If the error to the Query conditions.
persists, contact your service representative. Explanation: Information: No matched backup is
found in TSM Server according to the Query
FMY5961E The parameters /BACKUPMETHOD or conditions.
/BACKUPDESTINATION or both are System action: Processing continues.
invalid when performing data protection
operations using a FlashCopy Manager User response:
virtual server.
Explanation: Data protection commands default to FMY6065E Mount backup command failed. The
/BACKUPMETHOD=VSS and mount point and / or backup specified
/BACKUPDESTINATION=LOCAL when performed is invalid. Please refer to dsmerror.log
against a FlashCopy Manager virtual server. The for further details.
FlashCopy Manager supports no other values for these Explanation: The mount backup command failed. The
parameters. As a result it is no longer necessary to backup specified may already be mounted and or the
specify these parameters. For compatibility with other drive to map to may already be in used. Check if the
products values for /BACKUPMETHOD and provided directory to contain the mount point
/BACKUPDESTINATION can be specified as long as directories for all snapshots is an empty NTFS directory
they are set to their only valid values. This means that without hidden or system files and / or directories.
/BACKUPMETHOD can only be set to VSS and
/BACKUPDESTINATION can only be set to LOCAL. System action: Processing stops.

System action: The operation stops. User response: Check to make sure that the backup
specified is not already mounted and that the drive to
User response: Retry the command removing the map to is available. Repeat the command using an
/BACKUPDESTINATION and /BACKUPMETHOD empty NTFS directory as the snapshots mount points
parameters. directory.

FMY5965E Database state does not allow log FMY6066E Unmount backup command failed.
backup with TRUNCATE=YES. Please refer to dsmerror.log for further
Explanation: Database status is not Normal. Log has details.
to be backed up with truncation turned off. Explanation: The unmount backup command failed.
System action: The backup operation failed. The backup specified may not be mounted.

User response: Back up log with TRUNCATE=NO. System action: Processing stops.
User response: Check to make sure that the backup
FMY5966E Logical name was not found in the specified is mounted.
database.
Explanation: The logical name specified during FMY6067E In the component list that is specified,
relocation was not found in the database. the following object is not valid: 'object'.

System action: Processing for this operation ends. Explanation: The command that is entered includes a
component list. The list of components contains one or
more invalid objects. For example, when entering a

Chapter 5. FMY messages 247

FMY6103I • FMY6114W

BACKUP or RESTORE command, if the component list

FMY6110W Backup of database 'database name' is
includes a volume or mount point that is not valid or is
bypassed because it is offline. Database
not eligible for back up, this message is displayed. In
attributes are database attributes.
addition, the GUID volume name cannot be specified.
For RESTORE, MOUNT BACKUP, or DELETE Explanation: Backup processing bypasses the offline
BACKUP commands, this message is displayed if the database.
component list contains a backup specification that is
System action: Backup processing continues but the
not found in the backup inventory.
offline database is skipped.
System action: The operation stops.
User response: Ensure that the selected database is
User response: Verify the correct syntax is used when online or normal database and retry the backup.
entering the command. If the message is displayed
again, verify the volume and mount point names are
FMY6111I Backup of database 'database name' is
correctly identified. A misspelling can trigger this
bypassed because it is a database
message.
snapshot. Database attributes are
database attributes.
FMY6103I AlwaysOnPriority is skipping the
Explanation: Backup processing bypasses the database
backup of availability database name
snapshot.
because it is not on the preferred
replica. System action: Backup processing continues but the
database snapshot is skipped.
Explanation: When the AlwaysOnPriority option is
specified SQL Server is queried to see if the current User response: Ensure that the selected database is
availability replica is the preferred replica. The backup online or normal database and retry the backup.
of the availability database will only be performed on
the preferred replica. The backup is skipped on all
replicas that are not the primary replica. FMY6112W Backup of database 'database name' is
bypassed because it is in restoring
System action: Processing for this backup object ends. status. Database attributes are database
attributes.
User response: No response is needed.
Explanation: Backup processing bypasses the database
with restoring status database.
FMY6104I Backup Type backup for database database
name is not supported from System action: Backup processing continues but the
none-readable secondary replica. database with restoring status database is skipped.
Explanation: Database on none-readable secondary User response: Ensure that the selected database is
replica only supports full backup and copyonly backup. online or normal database and retry the backup.
System action: Run the same backup from primary
replica or readable secondary replica. FMY6113I Backup of database 'database name' is
bypassed because it is a mirrored
User response: Run the same backup from primary
database. Database attributes are database
replica or readable secondary replica.
attributes.
Explanation: Backup processing bypasses the mirrored
FMY6105I Differential backup database database
database.
name from secondary replica is not
supported. Exclude it for backup. System action: Backup processing continues but the
mirrored database is skipped.
Explanation: Differential backup databases from
secondary replica is not supported. User response: Ensure that the selected database is
online or normal database and retry the backup.
System action: Run the same backup from primary
replica.
FMY6114W Backup bypassed some databases
User response: Run the same backup from primary
because of their status.
replica.
Explanation: Backup processing bypasses the offline,
snapshot, mirrored, or with restoring state database.
System action: Backup processing continues but some
databases are skipped.
User response: Ensure that the skipped databases are

248 IBM Tivoli Storage FlashCopy Manager: Messages

 FMY6115I • FMY6205E

online, and retry the backup. User response: Verify that the correct license file is in
the correct directory. If you use the installation wizard,
the license file should be saved to the correct directory.
FMY6115I Backup of database 'database name' is
bypassed because it is offline. Database
attributes are database attributes. FMY6202W The TDPVMWareShell command is
either at an earlier level or not found.
Explanation: Backup processing bypasses the offline
The VM backup data query or restore is
database.
not issued.
System action: Backup processing continues but the
Explanation: Warning: To issue the VM backup data
offline database is skipped.
query or restore, update the software. Please upgrade it
User response: Ensure that the selected database is to support this feature.
online or normal database and retry the backup.
System action: The command is ignored and
processing continues.
FMY6116I Backup of database 'database name' is
User response:
bypassed because it is in restoring
status. Database attributes are database
attributes. FMY6203I The tail-log backup of the database
from the secondary replica is not
Explanation: Backup processing bypasses the database
supported. databases name is excluded
with restoring status database.
from the backup process.
System action: Backup processing continues but the
Explanation: Tail-log backups of databases from the
database with restoring status database is skipped.
secondary replica are not supported.
User response: Ensure that the selected database is
System action: The database backup operation is
online or normal database and retry the backup.
canceled.
User response: Run the backup from the primary
FMY6200W The data center node is not correctly
replica.
configured. To correct the problem,
re-run the configuration wizard and set
the datacenter node field with the node FMY6204I The tail-log backup of the database name
that was used to perform the VM database from the primary server
backups. removes the databases from the AAG.
Do you want to continue? Enter 'Y' for
Explanation: Warning: Because the data center node is
Continue or 'N' to cancel.
not configured to match the query and restore
conditions, this warning is reported. Explanation: The tail-log backup of databases from
the primary server removes databases from the AAG.
System action: Processing continues, but the data
center node configuration problem persists until you System action: If the database is not removed from
update the configuration. the AAG, the SQL Server reports an error when
completing the backup.
User response: Run the Tivoli Storage Manager for
Databases: Data Protection for SQL configuration User response: To continue with the tail-log backup
wizard. If the status of the Configuring Recovery Agent and remove database from the AAG, enter Y. To cancel,
rule does not indicate Passed, there is a configuration enter N.
problem.
FMY6205E The tdpsqlc command that was entered
FMY6201W The license for the Recovery Agent, part exceeds the maximum length limit. The
of the Tivoli Storage Manager for length limit of each option is 1790
Virtual Environments, is either not valid characters.
or not found.
Explanation: The length of tdpsqlc command is too
Explanation: Warning: Without a valid license for the long. It is invalid. When the length limit is exceeded,
Recovery Agent, you cannot use parts of Tivoli Storage the command is ignored. There is no truncation.
Manager for Databases: Data Protection for SQL to
System action: tdpsqlc command will fail with error.
recover Microsoft SQL databases from a VM backup.
An error message is displayed. The command is not
System action: The software continues to run, but you processed.
cannot use Tivoli Storage Manager for Databases: Data
User response: Check the length of tdpsqlc options,
Protection for SQL to recover Microsoft SQL databses
especially check the length of multiple databases name.
from a VM backup.

Chapter 5. FMY messages 249

FMY6206W

If possible, enter abbreviated parameters and options. If

multiple database names are entered, the length of the
database names can cause this error.

FMY6206W Database '' was excluded from backup

because the database name contains
special string ''.
Explanation: There are certain characters and strings
that conflict with Data Protection for SQL backup
operations. A database name that contained one of the
special characters or strings was encountered during a
backup operation. Therefore, it was excluded from the
backup.
System action: The database was excluded from
backup.
User response: Rename the database and retry the
backup.

250 IBM Tivoli Storage FlashCopy Manager: Messages

Chapter 6. FMV messages
Messages with prefix FMV are issued by the IBM Tivoli Storage FlashCopy
Manager Volume Shadow Copy Service (VSS) Requester. Tivoli Storage FlashCopy
Manager V4.1.1 FMV messages are listed in ascending numerical order. The
complete message is documented, including message ID, message text, explanation,
system action, and user response.

Explanation: The message text for the specified

FMV0101E Unable to open English message
message number cannot be read.
repository file name.
System action: Tivoli Storage Manager is unable to
Explanation: The default English message repository
complete the requested operation.
file cannot be opened. Either the file access permissions
prevent reading the file or the file is not present in the User response: Make sure the file has not been altered
expected location. from the installation. If the problem continues, see your
system administrator for further help.
System action: Tivoli Storage Manager is unable to
complete the requested operation. Processing is
terminated. FMV0106E Message index not found for message
number.
User response: Make sure the file in your DSM_DIR is
set up properly. If the problem continues, see your Explanation: The message repository file does not
system administrator for further help. contain the message text for the message number.
System action: Tivoli Storage Manager is unable to
FMV0102W Unable to open the message repository complete the requested operation.
file name. The American English
repository will be used instead. User response: Make sure the DSM_DIR is set up
properly and it does not point to an old copy. If the
Explanation: The default message repository file for problem continues, see your system administrator for
the current locale cannot be opened. Either the file further help.
access permissions prevent reading the file, the file is
not present in the expected location, or the language
specified in the option file is not supported on this FMV0107E Error trying to read header for message
workstation. number from repository file name.

System action: Tivoli Storage Manager continues Explanation: The message header information cannot
processing using the English language message be obtained for the message number in the message
repository. file.

User response: Make sure the file in your DSM_DIR is System action: Tivoli Storage Manager is unable to
set up properly. If the problem continues, see your complete the requested operation.
system administrator for further help. User response: Make sure the file has not been altered
from the installation. If the problem continues, see your
FMV0103E Error trying to read header record from system administrator for further help.
message repository file name.
Explanation: The message repository file header FMV0108E Error trying to read text for message
record cannot be obtained. number from repository file name.

System action: Tivoli Storage Manager is unable to Explanation: The message text cannot be obtained for
complete the requested operation. the message number in the message file.

User response: Make sure the file has not been altered System action: Tivoli Storage Manager is unable to
from the installation. If the problem continues, see your complete the requested operation.
system administrator for further help. User response: Make sure the file has not been altered
from the installation. If the problem continues, see your
FMV0105E Error trying to read index for message system administrator for further help.
number from repository file name.

© Copyright IBM Corp. 1995, 2014 251

FMV0109E • FMV0202E

repository file. It is possible the message repository has

FMV0109E Insufficient memory for allocation of
been corrupted.
message structure.
System action: Tivoli Storage Manager is unable to
Explanation: There is not enough memory in your
complete the requested operation.
system to allocate the storage needed for the message
text. User response: Make sure the message file was not
altered from the installation. Check DSM_DIR to make
System action: Tivoli Storage Manager is unable to
sure it is set up properly.
complete the requested operation.
User response: Stop Tivoli Storage Manager and
FMV0120E Message number number contains an
restart Tivoli Storage Manager. Then retry the
invalid multibyte sequence for the
operation. If unsuccessful, close all unneeded
current locale.
applications and retry the operation.
Explanation: An illegal multibyte sequence for the
current locale was found in the message. Either the
FMV0110E Unable to open error log file file name
message repository has been corrupted or is coded in a
for output.
language other than that of the current locale.
Explanation: The error log cannot be opened for
System action: Tivoli Storage Manager is unable to
output.
complete the requested operation.
System action: Tivoli Storage Manager is unable to
User response: If the message repository is not
complete the requested operation. File permissions may
corrupted, process the operation in the supported
be set such that writing is not allowed.
locale.
User response: Stop and restart Tivoli Storage
Manager. Then retry the operation. If unsuccessful,
FMV0121W Unable to open the iconv converter for
make sure the file is not being locked by another
the message repository file name. The
application and that file permissions allow write access.
American English repository will be
used instead.
FMV0113E Message repository file name has an
Explanation: The iconv converter for the default
invalid control record.
message repository for the current locale cannot be
Explanation: The message repository file contains an opened. The iconv converter used to convert from
incorrect control information. UTF-8 to the current locale is not installed on this work
station.
System action: Tivoli Storage Manager is unable to
complete the requested operation. System action: Tivoli Storage Manager continues
processing using the English language message
User response: Make sure the message file was not
repository.
altered from the installation. Check DSM_DIR to make
sure it is set up properly. User response: Make sure the required iconv
converter is installed properly. If the problem
continues, see your system administrator for further
FMV0118E Unable to open schedule log file 'file
help.
name' for output.
Explanation: The schedule log file cannot be opened
FMV0201E Invalid parameter was found.
for output.
Explanation: The system encountered an internal
System action: Tivoli Storage Manager is unable to
program error due to an invalid parameter.
complete the requested operation.
System action: The system returns to the calling
User response: Stop Tivoli Storage Manager and
procedure.
restart Tivoli Storage Manager. Then retry the
operation. If unsuccessful, make sure the file has not User response: Ask your service representative to
been locked by another application. check the error log.

FMV0119E Error trying to read response string for FMV0202E Not authorized to restore the other
message number from repository file node's data.
name.
Explanation: The client is not authorized to restore the
Explanation: The response string information for the other node's data.
message number cannot be obtained from the message
System action: The system returns to the calling
procedure.

252 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0203E • FMV0213E

User response: Get authorization from the other node.

FMV0208E The TCP/IP WINSOCK.DLL file cannot
be found.
FMV0203E The objName field has no leading
Explanation: The TCP/IP WINSOCK.DLL file cannot
directory separator.
be found.
Explanation: The objName field does not have a
System action: Processing stopped.
leading directory separator.
User response: Verify your TCP/IP installation.
System action: The system returns to the calling
procedure.
FMV0209E An error occurred while loading a
User response: Correct the value for the objName.
library.
Explanation: An error occurred while loading a
FMV0204E Wildcards are not allowed in the
library. The TCP/IP DLL load failed.
objName directory path.
System action: Processing stopped.
Explanation: Wildcards are not allowed in the
objName directory path. User response: Verify your TCP/IP installation.
System action: The system returns to the calling
procedure. FMV0210E The TCP/IP load function failed.
User response: Correct the value for the objName. Explanation: An error occurred while locating a
function. The TCP/IP load function failed.
FMV0205E Unable to open error log file. System action: Processing stopped.
Explanation: The system is unable to open the error User response: Verify your TCP/IP installation.
log file.
System action: The system returns to the calling FMV0211E The object name pointer is NULL.
procedure.
Explanation: There is no value provided for the object
User response: Verify the DSMI_LOG value and name pointer.
access permission. On the IBM AS/400® platform,
System action: The system returns to the calling
verify the value specified for ERRORLOGNAME in the
procedure.
API options file.
User response: Provide an address for the
dsmObjName structure.
FMV0206E The log file cannot be written to.
Explanation: There was an error writing to the log
FMV0212E The data block pointer is NULL.
file.
Explanation: There is no value provided for the data
System action: The system returns to the calling
block pointer.
procedure.
System action: The system returns to the calling
User response: Verify the DSMI_LOG value and
procedure.
access permission. on the AS/400 platform, verify the
value specified for ERRORLOGNAME in the API User response: Provide an address for the DataBlk
options file. structure.

FMV0207E The log file name was not specified. FMV0213E The object attribute pointer is NULL.
Explanation: The system is unable to open the error Explanation: There is no value provided for the object
log file. attribute pointer.
System action: The system returns to the calling System action: The system returns to the calling
procedure. procedure.
User response: Verify the DSMI_LOG value and User response: Provide an address for the ObjAttr
access permission. On the AS/400 platform, verify the structure.
value specified for ERRORLOGNAME in the API
options file.

Chapter 6. FMV messages 253

FMV0214E • FMV0224E

FMV0214E There is no server session information. FMV0220E An invalid option was found during
option parsing.
Explanation: The server did not respond with the
session information. Explanation: An invalid option was found.
System action: The system returns to the calling System action: The system returns to the calling
procedure. procedure.
User response: Verify the server status. User response: Verify the options in dsm.opt, dsm.sys,
and the options string. Check the error log for more
details about the error. on the AS/400 platform, verify
FMV0215E There is no server policy information.
the options in *LIB/QOPTTivoli Storage
Explanation: The server did not respond with the Manager(APIOPT).
policy information.
System action: The system returns to the calling FMV0221E There was an error in the Tivoli Storage
procedure. Manager API internals.

User response: Verify the server policy definitions. Explanation: The system encountered an error in the
API internals.
FMV0216E The dataBlk bufferLen value is zero. System action: The system returns to the calling
procedure.
Explanation: The value for the dataBlk bufferLen is
zero. User response: Shut down the process and retry the
operation. Verify that any previous dsmInit calls were
System action: The system returns to the calling cleaned up and terminated by a dsmTerminate call. If
procedure. the problem continues, contact your system
User response: Provide a non-zero value for the administrator or service representative.
bufferLen.
FMV0222E The repository type is invalid.
FMV0217E The dataBlk bufferPtr is NULL. Explanation: The repository type is invalid.
Explanation: There is no value provided for the System action: The system returns to the calling
dataBlk bufferPtr. procedure.
System action: The system returns to the calling User response: For dsmDeleteFS the repository must
procedure. be one of the following:
User response: Provide an address for the bufferPtr. v DSM_ARCHIVE_REP
v DSM_BACKUP_REP
FMV0218E The objType is invalid. v DSM_REPOS_ALL.
Explanation: The value for the objType is invalid.
FMV0223E Filespace name should start with the
System action: The system returns to the calling
directory delimiter.
procedure.
Explanation: The filespace name is invalid.
User response: The value for dsmObjName.objType
must be: System action: The system returns to the calling
v DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for procedure.
Backup, or User response: Filespace name should start with the
v DSM_OBJ_FILE for Archive. directory delimiter.

FMV0219E The dsmEndTxn vote is invalid. FMV0224E The object name is either an empty
string or has no leading delimiter.
Explanation: The dsmEndTxn vote is invalid.
Explanation: The object name is invalid because of an
System action: The system returns to the calling
empty string or there is no leading delimiter.
procedure.
System action: The system returns to the calling
User response: The vote must be
procedure.
DSM_VOTE_COMMIT or DSM_VOTE_ABORT.
User response: Verify the format of the dsmObjName
full path.

254 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0225E • FMV0234E

FMV0225E Low level qualifier of the object name FMV0230E The query Backup objState is invalid.
should start with the directory delimiter.
Explanation: The query Backup objState is invalid.
Explanation: The low level qualifier for the object
System action: The system returns to the calling
name is invalid.
procedure.
System action: The system returns to the calling
User response: The qryBackupData.objState must be
procedure.
one of the following:
User response: Start the low level qualifier of the v DSM_ACTIVE
object name with the directory delimiter.
v DSM_INACTIVE
v DSM_ANY_MATCH
FMV0226E The object owner is invalid.
Explanation: The object owner must be either the root FMV0231E The management class name was not
user, or the object owner must be the same as the found.
session owner.
Explanation: A query or send operation is unable to
System action: The system returns to the calling find the management class name.
procedure.
System action: The system returns to the calling
User response: Verify the session owner and object procedure.
owner.
User response: Verify the management class name.

FMV0227E The dsmBindMC sendType is invalid.

FMV0232E The drive letter is not an alphabetic
Explanation: The dsmBindMC sendType is invalid. character.
System action: The system returns to the calling Explanation: The drive letter is not an alphabetic
procedure. character. This return code is valid on Microsoft
User response: The sendType must be one of the Windows only.
following: System action: The system returns to the calling
v stBackup procedure.
v stArchive User response: Verify that the drive designation is an
v stBackupMountWait alphabetic character. The referenced field is
v stArchiveMountWait dsmDosFSAttrib.driveLetter.

FMV0228E The dsmSendObj sendType is invalid. FMV0233E The Register Filespace name is NULL.

Explanation: The dsmSendObj sendType is invalid. Explanation: There is no value provided for the
Register Filespace name.
System action: The system returns to the calling
procedure. System action: The system returns to the calling
procedure.
User response: The sendType must be one of the
following: User response: Provide a filespace name on
dsmRegisterFS.
v stBackup
v stArchive
FMV0234E The new password value is NULL or
v stBackupMountWait
blank.
v stArchiveMountWait
Explanation: There is no value provided for new
password.
FMV0229E The dsmDeleteObj delType is invalid.
System action: The system returns to the calling
Explanation: The dsmDeleteObj delType is invalid. procedure.
System action: The system returns to the calling User response: Provide a new password on
procedure. dsmChangePW.
User response: The delType must be dtBackup or
dtArchive.

Chapter 6. FMV messages 255

FMV0235E • FMV0241E

System action: The system returns to the calling

FMV0235E The old password value is NULL or
procedure.
blank.
User response: An end user can respond in the
Explanation: There is no value provided for old
following ways:
password.
v Check the network for errors.
System action: The system returns to the calling
v Look for clues in the Tivoli Storage Manager server
procedure.
activity log file, Tivoli Storage Manager client side
User response: Provide an old password on dsierror.log log file, and log files that are specific to
dsmChangePW. the problem application.
v Search the IBM Tivoli Storage Manager support site
FMV0236E On dsmInit, the owner is not allowed to (http://www.ibm.com/support/entry/portal/
establish a session when product/tivoli/tivoli_storage_manager) for APARs
PASSWORDACCESS=generate. that match the problem.
v If the API application is developed by a third party
Explanation: PASSWORDACCESS=GENERATE
(not IBM), search that third party's support pages for
establishes a session with the current login user as the
known issues that match the problem.
owner. The application should set clientOwnerNameP
to NULL when PASSWORDACCESS=GENERATE is in
If none of the above actions resolve the problem, report
effect.
the problem to the vendor of the application that uses
System action: The system returns to the calling the Tivoli Storage Manager API.
procedure. Whether the application can continue
processing depends on how the application handles the A developer of an application that uses the TSM API
error. must investigate the reason for the problem, including
reviewing the TSM API state diagram. The TSM API
User response: This message applies to applications
state diagram is in the product documentation State
that utilize the Tivoli Storage Manager API, and is
diagram summary for the Tivoli Storage Manager API
intended primarily for the vendor of the application for
(http://www.ibm.com/support/knowledgecenter/
which the message is issued. Depending on the
SSGSG7_7.1.1/com.ibm.itsm.client.develop.doc/
application, this could be a configuration issue.
c_all_together.html).
Consult the documentation for the application and
verify that the application is configured correctly. If the
FMV0239E On dsmSendObj, wildcards are not
problem persists, contact the application vendor for
allowed for the objName.
further assistance.
Explanation: On dsmSendObj, wildcards are not
allowed for the objName.
FMV0237E On dsmInit, the node is not allowed
when PASSWORDACCESS=generate. System action: The system returns to the calling
procedure.
Explanation: PASSWORDACCESS=generate
establishes a session with the current hostname as the User response: Provide a fs, hl, and ll on the
node. dsmObjName.
System action: The system returns to the calling
procedure. FMV0240E The filespace to delete/set access cannot
be found.
User response: When using
PASSWORDACCESS=generate, set clientNodeNameP to Explanation: The filespace to delete cannot be found.
NULL.
System action: The system returns to the calling
procedure.
FMV0238E The sequence of calls is invalid.
User response: Verify the filespace name.
Explanation: Then API requires function calls to be
made in a specific sequence. The function calls were
not made in the expected sequence. The error can be FMV0241E On dsmSendObj, dsmDeleteObj, or
triggered by the following issues: dsmUpdateFS the filespace is not
registered.
v An error in the network.
v A bug in the Tivoli Storage Manager API. Explanation: On dsmSendObj, dsmDeleteObj, or
dsmUpdateFS, the filespace is not registered.
v A bug in the Tivoli Storage Manager server.
v A bug in the application (IBM or third party) that System action: The system returns to the calling
uses the Tivoli Storage Manager API. procedure.

256 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0242W • FMV0251E

User response: Verify the filespace name. v The maximum number of objects is exceeded.
System action: The system returns to the calling
FMV0242W On dsmRegisterFS the filespace is procedure.
already registered.
User response: Issue dsmEndTxn and start a new
Explanation: On dsmRegisterFS the filespace is transaction session.
already registered.
System action: The system returns to the calling FMV0247E The backup or archive object is
procedure. excluded from processing.
User response: Verify the filespace name. Explanation: The backup or archive object is excluded
from processing.
FMV0243E On dsmBeginGetData the objID is System action: The system returns to the calling
NULL. procedure.
Explanation: On dsmBeginGetData, the objID is User response: Verify the objName and Exclude lists.
NULL.
System action: The system returns to the calling FMV0248E The backup object does not have a copy
procedure. group.
User response: Verify the following: Explanation: The backup object does not have a copy
v The dsmGetList is not NULL. group.
v Each objID is not NULL. System action: The system returns to the calling
v The dsmGetList numObjId is not zero. procedure.
User response: Verify server policy definitions.
FMV0244E On dsmInit the caller's API version is
different than the Tivoli Storage FMV0249E The archive object does not have a copy
Manager library version. group.
Explanation: On dsmInit the caller's API version has a Explanation: The archive object does not have a copy
higher value than the Tivoli Storage Manager library group.
version.
System action: The system returns to the calling
System action: The system returns to the calling procedure.
procedure.
User response: Verify server policy definitions.
User response: Install the latest Tivoli Storage
Manager API library and trusted agent module.
FMV0250E Memory used by the Tivoli Storage
Manager API has been corrupted.
FMV0245E The caller's structure version is different
than the Tivoli Storage Manager library Explanation: Memory used by the Tivoli Storage
version. Manager API has been corrupted.

Explanation: The caller's structure version is different System action: The system returns to the calling
than the Tivoli Storage Manager library version. procedure.

System action: The system returns to the calling User response: Retry the operation. If the problem
procedure. continues, contact your system administrator or service
representative.
User response: Ensure that the stVersion field is set
with the value in the header file. Recompile the
application with the latest header files. FMV0251E The sendObj Archive description is too
long.

FMV0246E Issue dsmEndTxn and then begin a new Explanation: The sendObj Archive description is too
transaction session. long.

Explanation: This transaction must be ended and a System action: The system returns to the calling
new one must be started due to one of the following procedure.
reasons: User response: The sndArchiveData.descr string must
v The destination changed. be less than or equal to DSM_MAX_DESCR_LENGTH.
v The byte limit is exceeded

Chapter 6. FMV messages 257

FMV0252E • FMV0262E

User response: The fsInfo field must be less than or

FMV0252E The sendObj ObjAttr.objInfo is too
equal to DSM_MAX_FSINFO_LENGTH.
long.
Explanation: The sendObj ObjAttr.objInfo is too long.
FMV0258I On dsmGetNextQObj or dsmGetData
System action: The system returns to the calling there is more available data.
procedure.
Explanation: On dsmGetNextQObj or dsmGetData
User response: The objInfo field must be less than or there is more available data.
equal to DSM_MAX_OBJINFO_LENGTH.
System action: The system returns to the calling
procedure.
FMV0253E The sendObj dsmObjName.hl is too
User response: Call the function again.
long.
Explanation: The sendObj dsmObjName.hl is too long.
FMV0259E The dataBlk buffer is too small for the
System action: The system returns to the calling query response.
procedure.
Explanation: The dataBlk buffer is too small for the
User response: The hl field must be less than or equal query response.
to DSM_MAX_HL_LENGTH.
System action: The system returns to the calling
procedure.
FMV0254E The password, or encryptionPassword
User response: On dsmGetNextQObj ensure that the
string provided is too long.
dataBlk buffer is at least as big as the query response
Explanation: The value provided for password or structure.
encryptionPassword is too long.
System action: The system returns to the calling FMV0260E An invalid option keyword was found
procedure. during option parsing.
User response: The password or encrypionPassword Explanation: An invalid option keyword was found in
field must be less than the dsmInit configuration file, the option string,
DSM_MAX_VERIFIER_LENGTH. dsm.sys, or dsm.opt.
System action: The system returns to the calling
FMV0255E The sendObj dsmObjName.fs is too procedure.
long.
User response: Correct the spelling of the option
Explanation: The sendObj dsmObjName.fs is too long. keywords. Verify that the dsmInit configuration file
only has a subset of the dsm.sys options. Check the
System action: The system returns to the calling
error log for more details about the error.
procedure.
User response: The fs field must be less than or equal
FMV0261E The configuration file specified on
to DSM_MAX_FS_LENGTH.
dsmInit cannot be opened.
Explanation: The configuration file specified on
FMV0256E The sendObj dsmObjName.ll is too
dsmInit cannot be opened.
long.
System action: The system returns to the calling
Explanation: The sendObj dsmObjName.ll is too long.
procedure.
System action: The system returns to the calling
User response: Verify the file name.
procedure.
User response: The ll field must be less than or equal
FMV0262E The Include/Exclude definition file was
to DSM_MAX_LL_LENGTH.
not found.
Explanation: The Include/Exclude definition file was
FMV0257E On RegisterFS or UpdateFS the fsAttr's
not found.
fsInfo is too long.
System action: The system returns to the calling
Explanation: On RegisterFS or UpdateFS the fsAttr's
procedure.
fsInfo is too long.
User response: Verify the file name on the Inclexcl
System action: The system returns to the calling
option.
procedure.

258 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0263E • FMV0273E

FMV0263E Either the dsm.sys file was not found, or FMV0268E Server problem: Destination not
the Inclexcl file specified in dsm.sys defined.
was not found.
Explanation: Server problem: Destination not defined.
Explanation: Either the dsm.sys file was not found, or
System action: Processing stopped.
the Inclexcl file specified in dsm.sys was not found.
User response: Have your service representative check
System action: The system returns to the calling
the error log.
procedure.
User response: The dsm.sys file must be in the
FMV0269S The structured file data type is
directory referenced by the environment variable
unknown.
DSMI_DIR. Verify the file name on the Inclexcl option
in the dsm.sys file. Explanation: An unknown and unexpected error code
occurred within the client program. The structured file
data type is unknown. This is a programming failure
FMV0264E Only a UNIX root user can execute
and the client program ends.
dsmChangePW or dsmDeleteFS.
System action: Processing stopped.
Explanation: Only a UNIX root user can execute
dsmChangePW or dsmDeleteFS. User response: Retry the operation. If the problem
continues, contact your system administrator.
System action: The system returns to the calling
procedure.
FMV0270S The data buffer overflowed.
User response: Run this program as a root user.
Explanation: The data buffer overflowed. This is a
programming failure and the client program ends.
FMV0265E You must issue dsmBindMC before
dsmSendObj. System action: Processing stopped.
Explanation: You must issue dsmBindMC before User response: Retry the operation. If the problem
dsmSendObj. continues, contact your system administrator.
System action: The system returns to the calling
procedure. FMV0271E No more files can be restored or
retrieved since the destination directory
User response: Modify your program.
is full.
Explanation: No more files can be restored or
FMV0266I The dsmEndTxn vote is ABORT, so
retrieved since the destination directory is full.
check the reason field.
System action: Processing stopped.
Explanation: After a dsmEndTxn call, the transaction
is aborted by either the server or client with a User response: Free up disk space, or restore or
DSM_VOTE_ABORT and the reason is returned. retrieve the file to another disk.
System action: The system returns to the calling
procedure. FMV0272I The operation is finished.
User response: Check the reason field for the code Explanation: The operation is finished.
which explains why the transaction has been aborted.
System action: The system returns to the calling
procedure.
FMV0267E Invalid command line option/value:
'option' User response: Proceed with next function call.

Explanation: The option is not valid on this command

line. FMV0273E The trusted agent execution/owner
permissions are invalid.
System action: Processing stops
Explanation: The trusted agent execution/owner
User response: Verify that the option and value are permissions are invalid.
not misspelled and are valid with the current
command. System action: Processing stopped.
User response: Have your system administrator check
the installation instructions for the client to ensure that
the trusted agent permissions are set correctly.

Chapter 6. FMV messages 259

FMV0274S • FMV0285E

System action: File skipped.

FMV0274S Process killed.
User response: Verify the application sets the
Explanation: Processing stopped. This is a
mountWait value correctly on dsmBeginGetData.
programming failure and the client program ends.
System action: Processing stopped.
FMV0280E Unable to find Trusted Agent module.
User response: Retry the operation. If the problem
Explanation: Tivoli Storage Manager was unable to
continues, contact your system administrator.
find the Tivoli Storage Manager Trusted Agent module
in the specified directory. The name of the Tivoli
FMV0275S Trusted agent would block the Storage Manager Trusted Agent module is dsmtca.
operation.
System action: Tivoli Storage Manager ends.
Explanation: The trusted agent blocks the operation.
User response: Make sure the Trusted Agent module
This is a programming failure and the client program
is in the directory specified by DSMI_DIR.
ends.
System action: Processing stopped.
FMV0282E Password file is not available.
User response: Retry the operation. If the problem
Explanation: The file containing the stored password
continues, contact your system administrator.
for the specified server-name is unavailable.
System action: Tivoli Storage Manager ends.
FMV0276S The area for the include/exclude pattern
is too small. User response: The root user must set and store a new
password.
Explanation: The area for the include/exclude pattern
is too small. This is a programming failure and the
client program ends. FMV0283E High level qualifier of the object name
should start with the directory delimiter.
System action: Processing stopped.
Explanation: The high level qualifier for the object
User response: Retry the operation. If the problem
name is invalid.
continues, contact your system administrator.
System action: The system returns to the calling
procedure.
FMV0277S There is no closing bracket in the
pattern. User response: High level qualifier of the object name
should start with the directory delimiter.
Explanation: There is no closing bracket in the
pattern. This is a programming failure and the client
program ends. FMV0284E The number of objects on
dsmBeginGetData exceeds
System action: Processing stopped.
DSM_MAX_GET_OBJ |
User response: Retry the operation. If the problem DSM_MAX_PARTIAL_GET_OBJ.
continues, contact your system administrator.
Explanation: The number of objects (numObjId)
specified on the dsmBeginGetData call exceeds
FMV0278S The transaction will be aborted. DSM_MAX_GET_OBJ |
DSM_MAX_PARTIAL_GET_OBJ.
Explanation: The server encountered an error and will
abort the transaction. System action: The system returns to the calling
procedure.
System action: The transaction will be aborted. The
reason code is passed on the dsmEndTxn call. User response: Check the number of objects before
calling dsmBeginGetData. If it is greater than
User response: Issue the dsmEndTxn with a vote of
DSM_MAX_GET_OBJ |
DSM_VOTE_COMMIT and examine the reason code.
DSM_MAX_PARTIAL_GET_OBJ, then issue multiple
Get call sequences.
FMV0279I A file was skipped during a restore
operation because the file is off line and
FMV0285E The update action is invalid.
the application has chosen not to wait
for a tape mount. Explanation: The dsmUpdateFS or dsmUpdateObj
action is invalid.
Explanation: A file was skipped during a restore
operation because the file is off line and the application System action: The system returns to the calling
has chosen not to wait for a tape mount. procedure.

260 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0286E • FMV0307E

User response: Correct the action value. Valid values

FMV0299E Scheduler cannot be started manually
are defined in dsmapitd.h and documented in our
because the value of
Using the API book.
MANAGEDSERVICES option is
SCHEDULE.
FMV0286E The key file is missing.
Explanation: if MANAGEDSERVICES SCHEDULE is
Explanation: The key file for the IBM Tivoli Data indicated in the option file, the Tivoli Storage Manager
Protection application client for Oracle cannot be found. scheduler cannot be started in the traditional manner.

System action: The system returns to the calling System action: Scheduler stopped.
procedure.
User response: If you are not going to use dsmcad to
User response: Ensure that you have ordered the manage the schedule anymore, stop dsmcad and
Tivoli Data Protection application client which contains remove MANAGEDSERVICES option from the option
TDP for Oracle, and install the key file. file.

FMV0287E The key file content is invalid. FMV0302I Successfully done.

Explanation: The key file content for Tivoli Data Explanation: The operation successfully completed.
Protection application client for Oracle is invalid.
System action: None.
System action: The system returns to the calling
User response: None.
procedure.
User response: Ensure that you have ordered the
FMV0304E The password is too short.
Tivoli Data Protection application client which contains
the TDP for Oracle, and install the key file. Explanation: The new password does not have
enough characters.
FMV0296I Encryption key passwords are not the System action: The password is not updated on the
same. Please try again... server.
Explanation: Tivoli Storage Manager found that the User response: Choose a different password. Contact
encryption key passwords do not match. your Tivoli Storage Manager administrator to lean the
password requirements.
System action: You are prompted for the encryption
key password.
FMV0305E It is too soon after the previous update
User response: Enter the correct encryption key
to change the password.
password.
Explanation: The password cannot be changed since
not enough time has elapsed since the last password
FMV0297E Error opening specified file.
update.
Explanation: The specified file could not be located or
System action: The password is not updated on the
opened.
server.
System action: Attempts to open file failed.
User response: Try to change your password again
User response: Make sure the file exists. later.

FMV0298E Session Rejected: The specified user id FMV0306E The password was previously used.
is currently locked
Explanation: The new password that you entered was
Explanation: The user id you specified is currently previously used.
locked on the server.
System action: The password is not updated on the
System action: Session was not started. server.

User response: Check with your system administrator User response: Choose a different password.
to find out why your user id is locked.
FMV0307E The password does not meet the
requirements.
Explanation: The new password that you entered does
not meet the requirements, such as the number of
special characters or digits.

Chapter 6. FMV messages 261

FMV0308E • FMV0317E

System action: The password is not updated on the

FMV0313E dsmTerminate cannot finish because the
server.
application is holding on to 1 or more
User response: Choose a different password. Contact tsmBuffers.
your Tivoli Storage Manager administrator to learn the
Explanation: An application is trying to terminate a
password requirements.
session, but is still holding some tsmBuffers.
System action: The system returns to the calling
FMV0308E Remote operation failed to start on
procedure.
obj-name. Status: status reason: reason
User response: The application must return all buffers
Explanation: The request to start a remote operation
for this session by calling tsmReleaseBuffer, and then
has failed for the indicated node and filespace. The
issue dsmTerminate.
status and the reason for the failure are shown.
System action: Tivoli Storage Manager ended the
FMV0314E An internal error occurred in the
current operation.
tsmBuffer array.
User response: Contact your system administrator for
Explanation: An internal API buffer array error
more information.
occurred.
System action: The system returns to the calling
FMV0309E Remote operation failed to start on
procedure.
obj-name. Status: status
User response: Try the operation again. If the problem
Explanation: The request to start a remote operation
continues, contact your system administrator or service
has failed for the indicated node and filespace. The
representative.
status of the failure is shown.
System action: IBM Tivoli Storage Manager ended the
FMV0315E Unable to open message text file.
current operation.
Explanation: The system is unable to open the
User response: Contact your system administrator for
message txt file (dscenu.txt or dsmclientV3.cat for IBM
more information.
AIX). On the AS/400 platform this file is
QFMVAPI/QAFMVENU(TXT).
FMV0311E The tsmBuffHandle is invalid, or the
System action: The system returns to the calling
value of dataPtr is invalid.
procedure.
Explanation: An invalid value for a handle or dataPtr
User response: Verify that the dscenu.txt file is in the
has been passed into the API.
directory pointed to by DSMI_DIR. For AIX, verify that
System action: The system returns to the calling the dsmclientV3.cat file has a symbolic link to
procedure. /usr/lib/nls/msg/<locale>/dsmclientV3.cat .

User response: There is a problem with the calling

application. Verify the values of the tsmBuffHandle and FMV0316E Unable to use message text file.
dataptr passed to the API.
Explanation: The system is unable to use the message
text file (dscenu.txt or dsmclientV3.cat for AIX) because
FMV0312E The number of bytes copied into the of an invalid header. On the AS/400 platform this file
tsmBuffer is larger than the allowed is QFMVAPI/QAFMVENU(TXT).
value.
System action: The system returns to the calling
Explanation: An invalid number of bytes was copied procedure.
to a tsmBuffer.
User response: Install the message text file again.
System action: The system returns to the calling
procedure.
FMV0317E Unable to use message text file.
User response: There is a problem with the calling
Explanation: The system is unable to use the message
application. Verify the number of bytes copied into the
txt file (dscenu.txt or dsmclientV3.cat for AIX) because
tsmBuffer.
of an invalid control record. On the AS/400 platform
this file is QFMVAPI/QAFMVENU(TXT).
System action: The system returns to the calling
procedure.
User response: Install the message text file again.

262 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0318E • FMV0328E

FMV0318E Invalid value for DATEFORMAT FMV0324E partialObjLength value for partial object
specified. retrieve is invalid.
Explanation: An invalid value is specified for Explanation: partialObjLength value for partial object
DATEFORMAT. retrieve is invalid.
System action: The system returns to the calling System action: The system returns to the calling
procedure. procedure.
User response: Specify a valid value. User response: Specify a valid value.

FMV0319E Invalid value for TIMEFORMAT FMV0325E Partial Object Retrieve is not supported
specified. on this server.
Explanation: An invalid value is specified for Explanation: The Tivoli Storage Manager server
TIMEFORMAT. specified by the user does not support partial object
retrieve.
System action: The system returns to the calling
procedure. System action: The system returns to the calling
procedure.
User response: Specify a valid value.
User response: Specify a Tivoli Storage Manager
server which supports the partial object retrieve
FMV0320E Invalid value for NUMBERFORMAT
function.
specified.
Explanation: An invalid value is specified for
FMV0326E This node has exceeded its maximum
NUMBERFORMAT.
number of mount points.
System action: The system returns to the calling
Explanation: Either no tape or sequential disk mount
procedure.
points are permitted for this operation, or the
User response: Specify a valid value. maximum number of mount points allowed are already
in use. The operation can not be completed. The Tivoli
Storage Manager administrator defines the maximum
FMV0321E msg parameter for dsmRCMsg is a number of mount points with the MAXNUMMP
NULL pointer. property of your node definition.
Explanation: The message parameter for dsmRCMsg System action: The object is skipped
is a NULL pointer.
User response: If you are performing any other Tivoli
System action: The system returns to the calling Storage Manager operations that might be using mount
procedure. points, wait until those operations are complete, then
User response: Allocate enough space for the message try the failed operation again. Otherwise contact your
parameter. Tivoli Storage Manager administrator for further
assistance

FMV0322E no text available for this return code.

FMV0327E A duplicate object was found, operation
Explanation: The dsmRC parameter for dsmRCMsg is cannot complete.
an unsupported return code.
Explanation: A duplicate object was found, operation
System action: The system returns to the calling cannot complete.
procedure.
System action: The requested operation failed.
User response: Specify a valid value.
User response: Try the operation with a different file
specification.
FMV0323E partialObjOffset value for partial object
retrieve is invalid.
FMV0328E The specified objects failed the merge
Explanation: The partialObjOffset value for partial test.
object retrieve is invalid.
Explanation: The specified objects failed the merge
System action: The system returns to the calling test, operation cannot complete.
procedure.
System action: The requested operation failed.
User response: Specify a valid value.

Chapter 6. FMV messages 263

FMV0330E • FMV0340E

User response: See documentation for the merge test User response: Retry the operation at a later time.
parameters.
FMV0335E System resource in use
FMV0330E The dsmSetAccess access Type is
Explanation: A required resource is in use by another
invalid.
command or process.
Explanation: The dsmSetAccess accessType is invalid.
System action: Tivoli Storage Manager ended the
System action: The system returns to the calling current operation.
procedure.
User response: Retry the operation at a later time.
User response: The accessType must be one of the
following:
FMV0336E Server plugin communication error
v atBackup
Explanation: Communication between a server plugin
v atArchive
module and a NAS filer failed.
System action: Tivoli Storage Manager ended the
FMV0331E No files have been previously backed
current operation.
up for this filename/filespace.
User response: Contact your system administrator for
Explanation: You tried to set access to files when no
more information.
files for the specified filename, drive or file system
were previously backed up.
FMV0337E Server plugin detected unsupported
System action: Processing stopped.
NAS filer operating system.
User response: Ensure that the correct drive or file
Explanation: A plugin module detected that a NAS
system was specified and that files are backed up for
filer is running an unsupported operating system or
you to set access.
operating system level.
System action: Tivoli Storage Manager ended the
FMV0332E No files have been previously archived
current operation.
for this filename/filespace.
User response: Contact your system administrator for
Explanation: You tried to set access to files when no
more information.
files for the specified filename, drive or file system
were previously archived.
FMV0338E An invalid operation was attempted on
System action: Processing stopped.
a node
User response: Ensure that the correct drive or file
Explanation: The operation is not valid.
system was specified and that files are archived for you
to set access. System action: Tivoli Storage Manager ended the
current operation.
FMV0333E Unknown Remote Mover type User response: Contact your system administrator for
more information.
Explanation: The specified Remote Mover type is
unknown.
FMV0339E The specified target storage pool is not
System action: Tivoli Storage Manager ended the
defined.
current operation.
Explanation: The storage pool is not defined.
User response: Contact your system administrator for
more information. System action: Tivoli Storage Manager ended the
current operation.
FMV0334E An Operation for the requested node User response: Contact your system administrator for
and filespace is already in progress. more information.
Explanation: A request has been made to use a data
mover to perform an operation for the indicated node FMV0340E A target storage pool does not have the
and filespace. Since an operation for this node and correct data format for the given node
filespace is already in progress, the new operation type.
cannot be performed.
Explanation: none
System action: Tivoli Storage Manager ended the
current operation. System action: Tivoli Storage Manager ended the
current operation.

264 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0341E • FMV0350E

User response: Contact your system administrator for

FMV0346E Input destination does not match
more information.
expected destination.
Explanation: Input destination does not match
FMV0341E No associated data mover is defined for
expected destination.
the given node.
System action: The current operation stops.
Explanation: none
User response: Retry operation with proper
System action: Tivoli Storage Manager ended the
destination.
current operation.
User response: Contact your system administrator for
FMV0347E Data mover is not available.
more information.
Explanation: Data mover is not available.
FMV0342E The CRC received from the Server does System action: The current operation stops.
not match the CRC calculated by the
User response: Retry operation with a proper Data
client.
mover.
Explanation: The server sent a CRC for a buffer. The
client calculated a CRC for the same buffer. These did
FMV0348E Operation failed because the copy
not match. The mismatch indicates a communication
continue option was set to NO.
failure.
Explanation: Operation failed because the copy
System action: In some cases, the client can indicate
continue option was set to NO.
the failure to the server and retry the operation.
System action: The current operation stops.
User response: Check the trace log for additional
information and retry the operation. If the problem User response: This abort code indicates that a store
persists, contact your system administrator. operation, like backup or archive failed because the
copy continue option was set to NO. The sysadmin will
need to resolve the problem on the server end.
FMV0343E An invalid operation was attempted on
a group leader or group member.
FMV0349E Transaction failed because of a problem
Explanation: An invalid operation was attempted on a
during a store operation.
logical group.
Explanation: Transaction failed because of a problem
System action: The current operation stops.
during a store operation. This error is typical when the
User response: Retry a valid operation. next storage pool has a different copy storage pool list
and we switch to this pool in the middle of a
transaction.
FMV0344E Cannot Send data with a zero byte
sizeEstimate. System action: Transaction is aborted.
Explanation: You cannot send data for an object with User response: Resend objects in separate transactions.
size estimate = 0.
System action: The system returns to the calling FMV0350E The current client configuration does
procedure. not comply with the value of the
DATAWRITEPATH or
User response: Set size estimate greater than 0 in
DATAREADPATH server option for this
dsmSendObj.
node.
Explanation: The values of the DATAWRITEPATH
FMV0345E Remote disk not defined.
and DATAREADPATH server options specify where the
Explanation: An operation was attempted on a remote client is allowed to send data, and where data is read
disk that is not defined. from. The values for the specified node name should
correspond with the client configuration. For example,
System action: The current operation stops. you will get this error message if DATAWRITEPATH
User response: Define the proper remote disk. contains a LAN value and the client is configured to
use LAN-free protocol, or vice versa.
System action: Processing stopped.
User response: Check the client, server, and storage
agent logs to determine why the client was not able to

Chapter 6. FMV messages 265

FMV0351E • FMV0359E

send data LAN-free. Make sure the client configuration

FMV0356E This object cannot be restored/retrieved
and server options are compatible.
using useTsmBuffers, because it is
encrypted.
FMV0351E The node or user does not have proper
Explanation: useTsmBuffers does not support
authority to perform this operation
encryption.
Explanation: The node or user does not have proper
System action: The system returns to the calling
authority to perform this operation.
procedure.
System action: The transaction is ended.
User response: Try the operation again, without using
User response: Check the authority for the specified useTsmBuffers.
object.
FMV0357E When using useTsmBuffers, a
FMV0352E The operation is not permitted due to restore/retrieve with partial object
server licenses values. restore is not allowed.

Explanation: The node or user is trying to perform an Explanation: useTsmBuffers does not support partial
operation that either exceeds license values, or is not object restore.
licensed.
System action: The system returns to the calling
System action: The session is rejected or the procedure.
transaction is cancelled, ending the current operation.
User response: Make sure the calling application is
User response: See your system administrator. either using Partial object restore or useTsmBuffers.

FMV0353E When using useTsmBuffers, dataBlk FMV0358E No encryption key was found. If you
must be NULL in calls to dsmSendObj are using -encryptkey=prompt make
and dsmGetObj. sure there is a value in the
encryptionPasswordP field and that
Explanation: The value for dataBlk must be NULL bEncryptKeyEnabled is set to true.
when using useTsmBuffers.
Explanation: There was no encryption key found in
System action: The system returns to the calling the password file, or no key was provided by the
procedure. application.
User response: There is a problem with the calling System action: The system returns to the calling
application. Contact your application provider procedure.
User response: If you are using -encryptkey=prompt,
FMV0354E Encryption is not allowed when using make sure there is a value in encryptionPasswordP and
useTsmBuffers. that bEncryptKeyEnabled is set to true.
Explanation: useTsmBuffers does not support
encryption. FMV0359E Conflicting encryption key options have
System action: The system returns to the calling been specified.
procedure. Explanation: When using the ENABLEENCRYPTKEY
User response: Try the operation again, without using option, the parameter bEncryptKeyEnabled for the
useTsmBuffers, or disable encryption for this operation. Tivoli Storage Manager API dsmInitExIn_t and
tsmInitExIn_t structures cannot be set to bTrue.

FMV0355E This object cannot be restored/retrieved System action: The system returns to the calling
using useTsmBuffers, because it is procedure.
compressed. User response: Either remove the
Explanation: useTsmBuffers does not support ENABLEENCRYPTKEY option from the options file, or
compression. set the parameter bEncryptKeyEnabled to bFalse in the
program using the Tivoli Storage Manager API.
System action: The system returns to the calling
procedure.
User response: Try the operation again, without using
useTsmBuffers.

266 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0360E • FMV0410E

FMV0360E The CAD cannot start because the value FMV0401E Read failure on the license file.
of the MANAGEDSERVICES option is
Explanation: The license file was not found, or could
NONE.
not be opened because of permissions, or the file is
Explanation: The CAD will not start if corrupted.
MANAGEDSERVICES NONE is set in the option file.
System action: The system returns to the calling
The CAD is designed to manage the web client or
procedure.
Tivoli Storage Manager schedules. By specifying
NONE, the CAD will not manage any services. User response: Check permissions on file. See if the
license file is in the correct place.
System action: The CAD will stop processing.
User response: Specify either WEBCLIENT or
FMV0402E Write failure on the license file.
SCHEDULER for the MANAGEDSERVICES option in
the option file then restart the CAD. Explanation: The license file was not found, or could
not be opened because of permissions or the file is
corrupted.
FMV0361I DIAG:
System action: The system returns to the calling
Explanation: The message text is provided for
procedure.
diagnostic purposes and is meant to provide
information to IBM support in problem determination. User response: Check permissions on file. See if
license file is in the correct place.
System action: None.
User response: None.
FMV0403E Data in the license file is not in a valid
format.
FMV0362E There are insufficient Windows system
Explanation: The license file is not valid.
resources to process this command.
System action: The system returns to the calling
Explanation: This problem can occur during backup
procedure.
of a shared directory. The most likely reason is the
'IRPStackSize' setting on the computer that hosts the User response: User needs to obtain a new license.
shared directory is too small.
System action: The file is skipped. FMV0404E The checksum in the license file does
not match the licenseregistration string.
User response: Check the Windows event viewer for
event ID 2011 on the computer that hosts the shared Explanation: The registration string is not valid.
directory. This event indicates that the configuration
parameter IRPStackSize is too small. IRPStackSize is a System action: The system returns to the calling
setting of type DWORD located in Windows registry procedure.
key HKEY_LOCAL_MACHINE\SYSTEM\ User response: User needs to obtain a new license.
CurrentControlSet\services\LanmanServer\Parameters.
If the IRPStackSize value is less than 20, or
IRPStackSize is not specified, then set the value to 20, FMV0405E This is an expired try and buy license.
restart the system, and try the operation again. The Explanation: The registration string is not valid.
default IRPStackSize value is 15. Attention: Consult
with your Windows system administrator before System action: The system returns to the calling
making changes to the Windows registry or the procedure.
problem persists after changing the IRPStackSize value User response: User needs to obtain a new license.
to 20.

FMV0410E Oracle passed invalid mode

FMV0400E License file could not be opened.
Explanation: Invalid mode passed by Oracle.
Explanation: The license file was not found, or could
not be opened because of permissions or the file is System action: The system returns to the calling
corrupted. procedure.
System action: The system returns to the calling User response: Contact your system administrator.
procedure.
User response: Check permissions on file. See if the
license file is in the correct place.

Chapter 6. FMV messages 267

FMV0411E • FMV0421W

FMV0411E Oracle passed null file name FMV0418E Wrong write state
Explanation: Null filename passed by Oracle. Explanation: The operation must be in WRITE state.
System action: The system returns to the calling System action: The system returns to the calling
procedure. procedure.
User response: Contact your system administrator. User response: Contact your service representative.

FMV0412E Wrong data block size FMV0419E Invalid flag passed

Explanation: Wrong Block Size Explanation: Invalid flag passed from Oracle.
System action: The system returns to the calling System action: The system returns to the calling
procedure. procedure.
User response: Contact your system administrator. User response: Contact your system administrator.

FMV0413E Object exists FMV0420W Warning! Restoring inactive system state

objects is not recommended. Do you
Explanation: Backup or Restore Object already exists.
wish to continue?
System action: The system returns to the calling
Explanation: Restoring inactive system state objects
procedure.
may cause system instability. Examples of possible
User response: If backing up an object, be sure to problems include:
generate a unique object name. v Applications that were installed after the time the
system state was backed up cannot function properly
FMV0414E Not same Oracle handle after restoring the inactive system state
v Critical operating system updates installed after the
Explanation: The handle passed from Oracle is not the inactive system state backup was made can no
same handle that Tivoli Storage Manager passed back. longer be available, or may not function correctly.
System action: The system returns to the calling Restoring inactive system state objects is not
procedure. recommended unless you are certain that this is what
User response: Contact your system administrator. you need to do.
System action: If user responds with yes, the client
FMV0415E End of file reached will restore the object. If user responds with no, the
client will cancel the operation.
Explanation: End of file reached.
User response: Reply to the prompt. If you are
System action: The system returns to the calling unsure, reply no, and consult your system
procedure. administrator or operating system vendor before
User response: None proceeding further.

FMV0416E Wrong Read State FMV0421W Unable to synchronize the node

password with the user id password
Explanation: The operation must be in READ state. provided.
System action: The system returns to the calling Explanation: The node password was not updated
procedure. due to the reason described in the error message
User response: Contact your service representative. preceding this one.
System action: The node password is not updated on
FMV0417E Runtime API version is outdated the server. Next time you run the client you will be
prompted for the password again.
Explanation: Runtime API is lower than compile time
API. User response: See the preceding error message.

System action: The system returns to the calling

procedure.
User response: Use the WHAT command to find out
the compile time API level. Obtain the same or higher
level of API library.

268 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV0422W • FMV0994E

FMV0422W The selected journal location is a FMV0991I Tivoli Storage Manager scheduler is
network drive and might not be listening for server requests on port port
accessible from the journal service. number
Select a location on a local drive.
Explanation: This message indicates the port number
Explanation: It is not recommended to use a network on which the clients is listens for server requests. If the
device as the location where journal databases are port number in the message differs from the default
stored. Placing journal databases on a network device value or what you specified with the TCPCLIENTPORT
can prevent the journal service from running. option, it is because the port was in use by a different
process.
System action: Processing continues.
System action: Processing continues.
User response: Choose a local drive where journal
databases will be stored. User response: Normally no further action is required.
If you require Tivoli Storage Manager to use a specific
port number, you need to configure your system or
FMV0423E Directory 'filespace namepath-namefile-name'
applications so the number is avaible. Restart the Tivoli
cannot be created. Path does not exist.
Storage Manager client and confirm it uses the desired
Explanation: The operating system returned a "path port.
not found" status when IBM Tivoli Storage Manager
attempted to create the directory needed for Automated
FMV0992E The destination filespace or drive letter
System Recovery (ASR). One possible reason is that a
is unavailable. For more details please
multi disk system is restored to a single disk system.
see dsmerror.log.
System action: Processing stopped.
Explanation: The system is trying to restore or retrieve
User response: Please verify that you are restoring to to a destination that cannot be reached. The specified
identical hardware and try again. filespace name or drive letter is not valid, or does not
exist, or you are specifying a local share name that
cannot be resolved.
FMV0990W Options file 'file-name' could not be
found. Default option values will be System action: Objects which are part of this filespace
used. are not processed.

Explanation: Common reasons for this warning User response: Try the command again, and specify a
include: different destination for the object that was not
v The default options file does not exist, and processed.

v You did not specify the -OPTFILE option when

starting the Tivoli Storage Manager client, and FMV0993E The source specification "source" has
v the environment variable DSM_CONFIG was not set. invalid format.

System action: Tivoli Storage Manager client assumes Explanation: The file system must be enclosed in
default values for all client options and continues curly braces and wildcards cannot be used except at
processing, using the default server name and the lower level.
associated options found in the dsm.sys file. System action: The command processing is
User response: If the default system action is terminated.
acceptable, you can eliminate this message by creating User response: Correct the specification and try the
an empty dsm.opt file in the installation directory. command again.
If you have a client user options file (dsm.opt), either
place it in the installation directory or set the FMV0994E Invalid string 'string' for virtual file
DSM_CONFIG environment variable to the space name or group name specification.
fully-qualified path and file name of your options file.
Explanation: You entered a virtual file space name or
Review the information on configuring Tivoli Storage a group name specification that contains wildcard
Manager in the Tivoli Storage Manager client manual characters.
specific to your operating system. If the problem
persists, ask your Tivoli Storage Manager administrator System action: Processing stopped.
for further assistance. User response: Enter a correct virtual file space name
and a group name and try again. Use the pick option
to display a list of groups from which you can select
one group.

Chapter 6. FMV messages 269

FMV0995E • FMV1007E

FMV0995E Volume 'volume-name' could not be FMV1004W Node has exceeded max tape mounts
locked. allowed. Operation for 'filespace-name'
will be tried again later.
Explanation: The system call to lock the volume
failed. Explanation: Node has exceeded max tape mounts
allowed. The operation will be tried again later.
System action: Processing stopped.
System action: The operation will be retried.
User response: Please verify that no other application
is accessing the volume. During restore of an image User response: Increase the number of allowed tape
Tivoli Storage Manager must have exclusive use of the mounts for this node on the server to avoid this
volume. situation again.

FMV1000E An unsupported communications FMV1005I TCP/IP read error on socket = socket-id,

method was specified. errno = error-code, reason : 'error-reason'.
Explanation: None. Explanation: An attempt to receive data using TCP/IP
connection failed. If reason : 'Connection reset by peer',
System action: processing stops.
it is possible that the server control connection timed
User response: Specify a communications interface out. This can occur if the file transfer time is greater
that is supported by the Tivoli Storage Manager client than the IDLETIMEOUT value set on the server.
on your operating system. See the Tivoli Storage
System action: TCP/IP connection to server fails.
Manager client manual for your operating system for
further information on configuring Tivoli Storage User response: If the timeout was due to a large file
Manager client communications. transfer time, you can ignore this message. The client
will reconnect with the server automatically, finish
transferring the data, and send statistics. You can also
FMV1001E Volume being backed up was not a
consider increasing the IDLETIMEOUT value in the
system volume. Skipped.
server options file.
Explanation: User specified to back up system volume
only. This volume was not backed up since this volume
FMV1006I TCP/IP write error on socket = socket-id,
is not a system volume.
errno = error-code, reason : error-reason
System action: Volume was not backed up.
Explanation: An attempt to send data using TCP/IP
User response: Use All option or use image backup connection failed.
command to backup this volume.
System action: Connection to server fails.
User response: Retry the operation. If the problem
FMV1002I MOS image is being created. It may
persists, contact your system administrator.
take a while.
Explanation: Mini Operating System image is being
FMV1007E Sending of object 'object-nameobject-
created. It may take a while to create it.
nameobject-name' failed. There is no
System action: Tivoli Storage Manager is gathering backup copy group.
necessary information.
Explanation: The management class for this file
User response: None. (object-name) does not have a backup copy group. Either
the default management class does not have a backup
copy group, or an INCLUDE statement is attempting to
FMV1003E Backup failed to start for node = bind the file to a management class that does not have
node-name, file system = fs-name, errno = a backup copy group.
error-code, reason : error-reason
System action: Tivoli Storage Manager did not back
Explanation: An attempt to start backup for remote up the file.
node failed.
User response: Run DSMC QUERY MGMTCLASS
System action: Backup fails. -DETAIL to view information about available
User response: Retry the operation. If the problem management classes.
persists, contact the server administrator. v If the file is being bound to the default management
class, make sure the management class has a backup
copy group.

270 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1008E • FMV1018E

v If the file is being bound to a management class processing on Solaris clients might stop.
specified in an INCLUDE statement, make sure that
User response: Verify that the file system is supported
the management class has a backup copy group.
by the Tivoli Storage Manager client. If a restore or
v If you have more than one Tivoli Storage Manager retrieve failed, retry the operation to another location. If
server, make sure you are connecting to the correct the problem persists, look for other indications of
server. system problems. It may be necessary to run the
v If you are unable to find a suitable management operating system utility that checks and repairs file
class, contact your Tivoli Storage Manager system inconsistencies. If the problem still cannot be
administrator for further assistance. resolved, contact your Tivoli Storage Manager
administrator for further assistance.
FMV1008E Sending of object 'object-nameobject-
nameobject-name' failed: No Archive Copy FMV1015E The session is rejected. The server does
Group not allow a signon of a client that is not
archive-retention protection enabled.
Explanation: The management class for this file
(object-name) did not have an archive copy group Explanation: The client cannot establish a connection
specified. to the server because the server is enabled for
archive-retention protection enabled and the client is
System action: TSM did not back up the file.
not.
User response: See your system administrator.
System action: The session is not started.
User response: See your system administrator.
FMV1009W An error occurred processing the
operating system include/exclude
statements. The error was detected FMV1016I No eligible files matching 'pathname'
while processing: subsystemname. were found.
Explanation: The client encountered an error while Explanation: The backup or archive operation
obtaining the automatic include/exclude statements completed, but no files were processed. Possible
from the operating system. Possible reasons for this reasons for this include:
error include: v The directory that was backed up or archived
v The specified registry key cannot be opened for contains no files
reading v The files are excluded from backup or archive
v The entry under this key has incorrect data
System action: None
System action: Processing continues without the full
User response: Check the path you entered.
list of operating system include/exclude statements.
User response: Ensure that you have access to the
FMV1017E Session rejected: TCP/IP connection
specified registry key and that entries are a MULTISZ
failure.
values that contain:
v Individual files Explanation: An attempt to connect to the server
using TCP/IP communications failed. This can be a
v Directories
result of incorrect TCP/IP option settings in your client
v Wild card entries options file. This error can also occur if the LAN
v Environment variables connection went down or if your system administrator
v /s switch (the /s switch is used on directory and/or canceled a backup operation.
wild card entries and signifies that all subdirectories System action: Session rejected. Processing stopped.
of this directory should be excluded)
User response: Retry the operation, or wait until the
If the cause of this message can not be determined or server comes back up and retry the operation. If the
resolved, contact IBM technical support for further problem continues, see your system administrator for
assistance. further help.

FMV1010E Error processing 'filespace-name': FMV1018E Port port number is already in use
Unsupported file system operation.
Explanation: The port specified by the
Explanation: The file system does not support an TCPCLIENTPORT option is in use by a different
operation required to process the file or directory. process.
System action: The file or directory is skipped. System action: Processing stopped.
Depending on the specific error encountered,

Chapter 6. FMV messages 271

FMV1019E • FMV1026E

User response: Contact the server administrator to set

FMV1023E Session rejected: Node type mismatch
up a different port for server-initiated connections.
Update the TCPCLIENTPORT with this new port Explanation: Your node name is associated with a
number. different type of operating system (such as OS/2 or
AIX) and cannot be used on this system.
FMV1019E The volume could not be opened. System action: Tivoli Storage Manager canceled the
current operation.
Explanation: An error occurred when Tivoli Storage
Manager tried to open the volume for a backup or User response: If you need a new node name, see
restore operation. your system administrator to assign a new one to you.
Generally, you have a unique node name for each
System action: The requested operation does not run.
machine and operating system pair that requires access
User response: Examine the client error log for to the server.
additional messages related to this error. Verify that the
volume is available, and is not locked by another
FMV1024E Failed to update backup attributes on
process. Try the operation again. If the problem
server for 'backup type' backup for
persists, contact IBM technical support for further
'filespace namepath-namefile-name', object id
assistance.
'object-id:object-id' return code 'return code'.
Explanation: Tivoli Storage Manager failed to update
FMV1020E System object backup failed.
attributes for the named backup object on the server.
Explanation: An error occurred while backing up The server may not reflect correct state of the backup.
Windows system object files. The backup did not
System action: Processing continues.
complete.
User response: Check preceding error messages in
System action: Processing stopped.
error log for more information. Retry the operation. If
User response: Ask your system administrator to problem continues, contact your Tivoli Storage
check the error log. Restart the Windows service Manager administrator.
associated with the system object indicated in the error
log, and retry the backup operation
FMV1025E Session rejected: Authentication failure
Explanation: Authentication failure. You entered an
FMV1021E System object restore failed.
incorrect password.
Explanation: An error occurred while restoring
System action: Tivoli Storage Manager canceled the
Windows system object files. The restore did not
current operation.
complete.
User response: Enter your correct password. If you
System action: Processing stopped.
cannot remember the correct password, see your
User response: Ask your system administrator to system administrator to have a new one assigned for
check the error log. Restart the machine, and then your node name.
restore the system object indicated in the error log
again.
FMV1026E The session is rejected: There was a
communications protocol error.
FMV1022E Cancel failed for node: node-name
Explanation: An unexpected network message was
filesystem: fs-name operation: op-type
received by the client. This could be caused by network
error: error
problems or a programming error.
Explanation: The request to cancel a remote operation
System action: Tivoli Storage Manager canceled the
has failed. The node, filespace, operation and reason for
current operation.
the failure are shown.
User response: Verify that your communication path
System action: Tivoli Storage Manager operation not
is functioning properly and try the operation again. If
cancelled.
the problem persists, contact your Tivoli Storage
User response: Contact your system administrator for Manager administrator for further assistance.
more information.

272 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1028S • FMV1033E

"-memoryefficientbackup=yes".
FMV1028S An internal program error occurred.
For UNIX systems that support resource limits, check
Explanation: Tivoli Storage Manager encountered an
to see b if the memory resource limit is too low by
unexpected condition and can not continue the
entering the following command: ulimit -a
operation. This might be a programming error.
Based on the resulting data, you can ask the UNIX
System action: processing stops.
system root user to increase resource limits so that it
User response: Try the operation again. If the problem will override the current default. The UNIX system root
persists, contact your Tivoli Storage Manager user has the authority to increase resource limits.
administrator or IBM technical support for further
assistance.
FMV1031E The attempt to establish a TCP/IP
connection timed out before the
FMV1029E Communication with the Tivoli Storage connection was made.
Manager server is lost.
Explanation: The Object of the connection attempt
Explanation: This message is issued after the session failed to respond within the the allotted wait time. In
with the Tivoli Storage Manager server is unexpectedly the case of the B/A client, this message is preceded in
lost. The client error log might contain additional dsmerror.log by message FMV5216E that gives details
information regarding this problem. of the connection that failed. The condition may be
temporary.
System action: processing stops.
System action: processing stops.
User response:
v Restart the Tivoli Storage Manager client and retry User response:
the operation. v Restart the Tivoli Storage Manager client and retry
v If the problem persists, review the client error log for the operation.
other messages that might be related to this problem. v Check the client options file and verify that
v Verify that network connectivity exists between the TCPSERVERADDRESS and TCPPORT specify the
Tivoli Storage Manager client machine and the Tivoli correct TCP/IP address and port number for your
Storage Manager server machine. Tivoli Storage Manager server.
v Contact your Tivoli Storage Manager administrator v Verify that network connectivity exists between the
for further assistance. The Tivoli Storage Manager Tivoli Storage Manager client machine and the Tivoli
administrator can review the Tivoli Storage Manager Storage Manager server machine.
server activity log for additional information about v If the problem persists, see your Tivoli Storage
the problem. Manager administrator for further assistance.

FMV1030E The operating system refused a Tivoli FMV1032E An attempt to establish a TCP/IP
Storage Manager request for memory connection was rejected by the host
allocation.
Explanation: An attempt to establish a TCP/IP
Explanation: Tivoli Storage Manager requires access to connection was rejected by the server.
memory in order to store information as processing
System action: Processing stopped.
proceeds. In this case, more memory was requested
than the operating system would allocate. Possible User response: The server was not fully initialized, is
reasons include: not currently running, was not enabled for TCP/IP
v The system is low on memory. communications, or an incorrect TCP/IP port number
was specified. If the problem continues, see your
v The process in which the program runs has exceeded
system administrator.
the maximum memory that it is allowed to allocate.
v Some other error condition occurred that caused the
program to think it is out of memory. FMV1033E An invalid TCP/IP address was
specified.
System action: Tivoli Storage Manager cannot
complete the requested operation. Explanation: The TCP/IP address specified by the
Tivoli Storage Manager client's TCPSERVERADDRESS
User response: Close all unneeded applications and setting could not be found on the network. Common
try the operation again. If the operation still fails, try reasons for this error include:
dividing the task into several smaller units. For
v The TCPSERVERADDRESS client option specifies the
example, if a file specification contains several high
wrong TCP/IP address for the Tivoli Storage
level directories, run the Tivoli Storage Manager task
Manager server".
serially for each directory. If the Tivoli Storage Manager
task is an incremental backup, use the option

Chapter 6. FMV messages 273

FMV1034E • FMV1039S

v The machine that hosts the Tivoli Storage Manager system. If the problem persists, ask your IBM Tivoli
server is not on the network. Storage Manager administrator for further assistance.
v A network problem is preventing the Tivoli Storage
Manager client from reaching the machine that hosts FMV1036S The option 'option' or the value supplied
the Tivoli Storage Manager server. for it is not valid. It was found in
System action: processing stops. options file 'file-name' at line number:
number The complete entry: 'entry'
User response: Verify that the TCPSERVERADDRESS
and TCPPORT settings have the correct values for your Explanation: The specified option in the Tivoli Storage
Tivoli Storage Manager server. Use your operating Manager options file (file-name) or the command line, is
system's "ping" (or similar) utility to ensure that your in error. Either the option itself or its value are invalid.
machine can locate the machine that hosts the Tivoli For options that include a date or time specification,
Storage Manager server across the network. Try the the format of the date or time might not match the
operating again. If the problem persists, ask your Tivoli formats specified by the DATEFORMAT or
Storage Manager administrator for further assistance. TIMEFORMAT options.
System action: Processing stopped.
FMV1034E The specified TCP/IP host name is User response: Correct the option name or value. For
unreachable options that specify dates or times, ensure that the
Explanation: The TCP/IP host name specified in the specified date or time matches the DATEFORMAT and
TCPSERVERADDRESS statement cannot be reached. TIMEFORMAT settings. If -DATEFORMAT or
-TIMEFORMAT are specified on the command line,
System action: Processing stopped. they must precede the option that specifies the date or
User response: Check your options file for the correct time. For example, use -DATEFORMAT=3
TCPSERVERADDRESS statement. See your -FROMDATE=yyyy-mm-dd, instead of
administrator for the correct name of the server. -FROMDATE=yyyy-mm-dd -DATEFORMAT=3.

FMV1035S Options file 'file-name' could not be FMV1037S Invalid keyword specified
found, or it cannot be read. Explanation: Tivoli Storage Manager found an
Explanation: Common reasons for this error include: incorrect keyword in the options file.

v The default options file does not exist. System action: Processing stopped.
v You specified the -OPTFILE option when starting the User response: Correct the options file with valid
IBM Tivoli Storage Manager client, but the options entries.
file you provided does not exist.
v The DSM_CONFIG (or DSMI_CONFIG if you are
FMV1038S Invalid option specified.
using the IBM Tivoli Storage Manager API)
environment variable specifies an options file that Explanation: An incorrect option was specified to
does not exist. Tivoli Storage Manager.
v You specified the -OPTFILE option when starting the System action: Processing stopped.
IBM Tivoli Storage Manager client, but the options
file that you provided is not in the standard file User response: Correct the options used for running
encoding of the system. For example, on Windows Tivoli Storage Manager.
the expected file encoding is FMVI.
v You specified the -OPTFILE option when starting the FMV1039S The include or exclude pattern cannot
IBM Tivoli Storage Manager client, but the options be parsed.
file that you provided does not have appropriate
read permissions for the user that is running the Explanation: The pattern is formatted incorrectly or is
operation. too complex for Tivoli Storage Manager to interpret.

System action: IBM Tivoli Storage Manager client System action: Processing stopped.
processing stops. User response: Verify that the include or exclude
User response: Make sure that the options file you pattern is specified correctly. If the pattern is correct,
want to use exists, it has the read rights set for the user then contact IBM technical support for further
that is running the operation, and it is in the standard assistance.
file encoding of the system. For example, on Windows
the expected file encoding is FMVI. Review the
configuration information in the IBM Tivoli Storage
Manager client manual specific to your operating

274 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1040S • FMV1050E

continue the current operation.

FMV1040S Include/Exclude pattern is missing a
closing bracket User response: Check the syntax of environment
variable in the options file. Correct it and retry the
Explanation: The include or exclude pattern is
operation.
incorrectly constructed. The closing bracket is missing.
System action: Processing stopped.
FMV1046S Environment string for variable
User response: Correct the syntax for the pattern. 'environment-name' too long. Anything
beyond 1024 characters is being ignored
FMV1041S Include/Exclude pattern must start with Explanation: Environment variable expanded to a
a directory delimiter string which is too long. Make sure that the string is no
more than 1023 characters long.
Explanation: The include or exclude pattern must start
with a directory delimiter. System action: Tivoli Storage Manager attempts to
continue the current operation.
System action: Processing stopped.
User response: Check the length of environment
User response: Correct the syntax for the pattern.
string and break it up into smaller strings using
multiple environment variables.
FMV1042S A beginning or ending directory
delimiter is missing from the
FMV1047E The destination file system is
Include/Exclude pattern.
unavailable. The following object was
Explanation: skipped: File space:'filespace-name'
1. The include/exclude pattern has a '...' without a Pathname:' path-name' Filename:'file-name'
beginning or ending directory delimiter. Explanation: The client is trying to restore or retrieve
2. For Windows, the drive seperator is not the specified object to a destination that is not valid,
immediately followed by a directory delimiter. does not exist, or cannot be reached.

System action: Processing stopped. System action: The object is not restored or retrieved.
Processing continues with the next object.
User response: Correct the syntax for the pattern.
User response: Try the command again using a
different destination.
FMV1043S Quotes are not matched
Explanation: The quotes specified in the pattern are FMV1048E Device 'volname' is not local
not the same and do not make a set.
Explanation: The selected path is not a local device
System action: Processing stopped. and therefore is not a valid object for image operations.
User response: Correct the pattern by using matching System action: The requested logical volume
quotes in the syntax. operation is not performed.
User response: Choose another object.
FMV1044S Unresolved environment name
'environment-name'.This filespace is being
ignored. Processing Continues. FMV1049E 'filename' is not a valid destination file
for image restore
Explanation: The specified environment-name in the
options file is invalid. Explanation: The filename you specified is not a valid
name for a file or it is a directory.
System action: Tivoli Storage Manager attempts to
continue the current operation. System action: Restore processing stopped.
User response: Check the environment variable in the User response: Specify a correct filename for image
options file and use a valid environment variable. Retry restore.
the operation.
FMV1050E Before performing the VSS Instant
FMV1045S Environment variable syntax error. Restore Tivoli Storage Manager cannot
lock the volume 'volume-name'.
Explanation: Incorrect syntax is specified in the
options file. Make sure that the variable is enclosed in Explanation: The volume cannot be locked because
curly braces. another application is accessing the file systems on the
volume.
System action: Tivoli Storage Manager attempts to

Chapter 6. FMV messages 275

FMV1051I • FMV1057I

System action: Processing stops. User response: No further action is necessary.

However, if the file space is for Windows system state,
User response: Stop or suspend the applications that
then at some future time when you have determined
have handles open on the volume. For a file system
you no longer need the older renamed system state file
restore, close applications that are accessing the file
space, you can ask your Tivoli Storage Manager
systems that are used for the VSS Instant Restore.
administrator to delete the older file space from Tivoli
If you cannot close the applications that are accessing Storage Manager storage.
the file system, unmount the file system. After the
unmount process is complete, mount the file system
FMV1054E Existing filespace filespace-name cannot
and perform the VSS Instant Restore.
be renamed to new filespace
For more information, see the Tivoli Storage Manager filespace-name. Tivoli Storage Manager
error log file DSMERROR.LOG. return code = retcode.
Explanation: The client was unable to migrate a file
FMV1051I Invalid password space name from the volume label naming convention
to the UNC naming convention.
Explanation: You entered an invalid password.
System action: Processing stopped.
System action: Tivoli Storage Manager cannot connect
to the server without the correct password. User response: Check the client error log and the
Tivoli Storage Manager server activity log for any other
User response: Enter the password, or ask your messages that might help identify the problem. If the
system administrator for the correct password. problem cannot be resolved, contact IBM technical
support for additional assistance.
FMV1052E Direct connection to the Storage Agent
is not allowed. FMV1055I Trying to rename existing filespace
Explanation: You cannot connect directly to the filespace-name to new filespace
Storage Agent. filespace-name, but drive letters do not
match, old=drive-letter, new=drive-letter.
System action: Processing stopped. Ignore the old filespace and backup to
User response: To perform Lanfree operations using the new filespace.
the Storage Agent, specify the ENABLELANFREE Explanation: Trying to rename the existing filespace
option in your options file, and restart the process. name using the volume label to the UNC format
naming convention but the drive letters do not match.
FMV1053I Existing file space filespace-name has Leave the existing filespace alone and create a new
been renamed to filespace-name filespace.

Explanation: If the file space is for Windows system System action: Processing continues.
state, this message is issued when the Tivoli Storage User response: None.
Manager backup-archive client detects multiple system
state file spaces where the names differ only in case.
The existence of multiple system state file spaces can FMV1056E Share/network path share cannot be
occur if, at some earlier time, your Tivoli Storage resolved. Path does not exist.
Manager administrator renamed the system state file Explanation: For backup: Trying to backup
space to the same name but with a different case or the share/network, which either does not exist or does not
computer's name was changed from all upper case have the correct privilege to access the share. For
characters to lower case or mixed case characters. If the restore : Trying to restore to a share/network path that
file space name represents a drive volume label, then cannot be resolved. The directory path does not exist.
this file space was created by an older Tivoli Storage
Manager backup-archive client. System action: Processing stopped.
System action: If the file space is for Windows system User response: Retry the command and specify a
state, Tivoli Storage Manager will back up system state destination, or restore the directory tree first before
to the file space containing the most recent backup. The trying to restore the share point.
older file space is renamed as specified in this message.
Subsequent system state backups will continue to back
FMV1057I File space filespace-name cannot be
up system state to the same (most recently used) file
renamed to new file space filespace-name,
space. If the file space name represents a drive volume
because the new file space already
label, Tivoli Storage Manager renames the file space to
exists.
the corresponding UNC name and continues to back
up the drive to this renamed file space. Explanation: The client was unable to migrate a file

276 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1058E • FMV1066E

space name from the volume label naming convention User response: Try the operation again, using the file
to the UNC naming convention because the new file system name instead of the device name.
space already exists on the Tivoli Storage Manager
server.
FMV1062E Only a single image may be selected
System action: The operation proceeds using the new when a destination is entered.
file space. The old file space is ignored.
Explanation: You selected more than one image object
User response: No action is necessary, but if the data (logical volume) to be restored. You also specified a
in the old file space is no longer needed, it can be destination. The system cannot place more than one
deleted from the Tivoli Storage Manager server. image into a single destination volume. When more
than one object is selected, each must be restored to its
original location.
FMV1058E The restore destination cannot be
reached. System action: The requested logical volume restore is
not performed.
Explanation: Either the destination file system is
invalid or it cannot be reached. User response: Retry the operation, selecting one
object to be restored to the given destination, or retry
System action: Processing stopped.
the operation without entering the destination.
User response: Try the command again using a
different destination.
FMV1063E The specified path is not a valid file
system or logical volume name.
FMV1059E Two inactive objects with the same
Explanation: None.
image name were selected. Process
terminates System action: The logical volume operation is not
performed.
Explanation: You selected more than one inactive
version of the same image object (logical volume). The User response: Try the operation again using a valid
system has no way to decide which you want to path.
restore.
System action: The requested logical volume restore is FMV1064E An unexpected error occurred while
not performed. processing the image operation.
User response: Retry the operation, selecting an active Explanation: None.
version or only one inactive version of the volume you
System action: The requested operation does not run.
wish to restore.
User response: Examine the client error log for any
additional messages that may have been issued before
FMV1060E The specified path is not a mounted
or after this message. Correct any problems, if possible.
filesystem
If the cause of this message can not be determined or
Explanation: You entered a file system name that does resolved, contact IBM technical support for further
not correspond to a mounted file system for this assistance.
system. It is possible the file system name is
misspelled, or simply that the file system is not
FMV1065E Library version of the image utility does
currently mounted.
not match that of the Tivoli Storage
System action: The requested logical volume Manager API
operation is not performed.
Explanation: The current system has a mix of installed
User response: Retry the operation, using name of a components.
mounted file system.
System action: The requested logical volume
operation is not performed.
FMV1061E The specified device corresponds to a
User response: Re-install all Tivoli Storage Manager
mounted file system; you must specify
components
the file system by name.
Explanation: You entered a logical device name that is
FMV1066E The restore operation completed
mapped to a mounted file system. This volume must
successfully, but the file system could
only be referenced by its file system name.
not be remounted.
System action: The requested logical volume
Explanation: None.
operation is not performed.
System action: The file system is left unmounted.

Chapter 6. FMV messages 277

FMV1067E • FMV1074W

User response: Use the mount command to mount the System action: The requested logical volume
file system. On AIX, run fsck if requested by the operation is not performed.
operating system.
User response: Re-try the operation, check error log
for more information.
FMV1067E A call to a system function returned an
unexpected error.
FMV1071E Invalid domain name entered:
Explanation: If you are performing a JFS2 snapshot 'domain-name'
based operation, it is possible that the snapshot was not
Explanation: You entered an invalid domain
large enough to contain all the changes made to the
domain-name. Check whether the domain name is a file
filesystem after the snapshot was created. This could
system and the file system is mounted. A directory
cause the snapshot to become invalid thereby
cannot be specified in the domain option, unless it is a
preventing Tivoli Storage Manager client from reading
virtual mount point.
the snapshot.
System action: Processing continues if there are other
System action: The requested operation does not run.
file systems in the domain option to back up.
User response: Examine the client error log for
User response: Enter a valid drive or file system name
additional messages related to this error. Try the
(domain).
operation again. If the problem persists, contact IBM
technical support for further assistance.
FMV1072E Unable to continue operation; Drive
If you are performing a JFS2 snapshot based operation,
'drive-name' has no volume label.
please use the default snapshotcachesize of 100% and
ensure that the volume group has sufficient disk space Explanation: The specified drive-name in the domain
to allocate snapshots at least as large as the file system list does not have a volume label.
and retry the operation.
System action: Processing stopped.

FMV1068E Device is not local User response: Use the system format utility to place
a unique volume label on all drives on which you
Explanation: The selected path is not a local device intend to run Tivoli Storage Manager.
and therefore is not a valid object for image operations
System action: The requested logical volume FMV1073E The file space for domain 'domain-name'
operation is not performed. could not be found on the Tivoli
Storage Manager server.
User response: Choose another object.
Explanation: The specified file space was expected to
be found on the server, but it no longer exists. It is
FMV1069E An error occurred while reading data
possible that a command was issued to delete the file
from the device
space from the server while the current operation was
Explanation: An error occurred while reading data in progress.
from the device. Windows Only: This could be due to
System action: Tivoli Storage Manager processing
bad sectors on the drive.
stops.
System action: The requested logical volume
User response: Try the operation again. If the problem
operation is not performed.
recurs, check the error log for any other messages that
User response: Retry the operation, then check the might indicate a reason for the failure. Try to correct
error log for more information. Windows Only: Please any indicated problems, then try the operation again. If
run chkdsk /r and retry the operation. If the problem the problem persists, contact IBM technical support for
persists, a possible workaround is to back up the entire further assistance.
drive using a regular (non-image) backup. Please
ensure that all your data is backed up. Then format the
FMV1074W The operation was stopped by the user.
drive using a full format (without the /q quick format
option). Then restore the data and retry the image Explanation: The operation was stopped at the request
backup operation. of the user. This usually occurs when the 'Q' key is
pressed two times.
FMV1070E Write error System action: Processing stopped.
Explanation: An error occurred while writing data to User response: None.
the device.

278 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1075E • FMV1084E

FMV1075E file name(line number)The operating FMV1079E No file specification entered

system refused a IBM Tivoli Storage
Explanation: You did not enter a file specification as
Manager request for memory allocation.
prompted.
Explanation: IBM Tivoli Storage Manager requires
System action: Tivoli Storage Manager did not
access to memory in order to store information as
continue with the requested operation.
processing proceeds. In this case, more memory was
requested than the operating system would allocate. User response: Enter a file specification to continue.
Possible reasons include:
v The system is low on memory. FMV1081E Invalid search file specification 'string'
v The process in which the program runs has exceeded entered.
the maximum allocated memory.
Explanation: You entered a file specification or search
v Some other error condition occurred. No memory is string that contains incorrect characters or contains
available. wildcard characters in the drive specification or file
System action: IBM Tivoli Storage Manager cannot system name.
complete the requested operation. System action: Processing stopped.
User response: Close all unneeded applications and User response: Enter a correct file specification as
try the operation again. If the operation still fails, try described in the appropriate Using the Backup-Archive
dividing the task into several smaller units. For Client book for the particular operating system.
example, if a file specification contains several
high-level directories, run the IBM Tivoli Storage
Manager task serially for each directory. If the IBM FMV1082E Invalid destination file specification
Tivoli Storage Manager task is an incremental backup, 'file-name' entered
use the option "-memoryefficientbackup=yes".
Explanation: You entered a destination file-name
For UNIX systems that support resource limits, you can specification that contains incorrect characters or has
check if the memory resource limit is too low by wildcard characters in the specification.
entering the following command: ulimit -a
System action: Processing stopped.
Based on the resulting data, you can ask the UNIX
User response: Enter a correct file specification as
system root user to increase the resource limit above
described in the appropriate Using the Backup-Archive
the current default limit. The UNIX system root user
Client book for the particular operating system.
has the authority to increase resource limits.

FMV1083E No files have previously been archived

FMV1076E The specified directory path 'pathname'
for 'filespace-name'
could not be found.
Explanation: You tried to retrieve files when no files
Explanation: An invalid or unreachable directory path
for the specified drive or file system (filespace-name)
was specified.
were previously archived.
System action: Processing stopped.
System action: Processing stopped.
User response: Try the operation again using a valid
User response: Ensure that the correct drive or file
directory path.
system was specified and that files are archived for you
to retrieve.
FMV1078S Unknown system error error-code
occurred.
FMV1084E No files have previously been backed
Explanation: An error unknown to Tivoli Storage up for 'filespace-name' or the specified file
Manager error-code occurred within the client program. space is invalid for the current operating
system.
System action: The client stops.
Explanation: You cannot restore files. Either the file
User response: Check the error log for any other space or drive is invalid, or no backup copies exist.
messages that might indicate a reason for the failure.
Try to correct any indicated problems, then try the System action: Processing stops.
operation again. If the problem persists, contact IBM
User response: Specify a valid drive or file space.
technical support for further assistance.
Verify that backup copies exist.

Chapter 6. FMV messages 279

FMV1085E • FMV1094E

FMV1085E No memory available to store Archive FMV1090E The LVM1 device is no longer
Management Class override name supported by this client.
Explanation: Not enough memory was available for Explanation: The selected path refers to a volume
the operation. device managed by LVM version 1. LVM 1 is no longer
supported by this version of client and therefore is not
System action: Processing stopped.
a valid object for image operations.
User response: Retry the operation or restart the
System action: The requested logical volume
system with fewer programs in memory.
operation is not performed.
User response: Use earlier versions of the client that
FMV1086E File not found during Backup, Archive
support LVM1 to perform the logical volume operation.
or Migrate processing
Alternatively, you can upgrade to LVM2 and migrate
Explanation: The file being processed for backup, the volume to LVM2. LVM2 is supported by this client
archive or migrate no longer exists on the client. for logical volume operations.
Another process deleted the file before it could be
backed up, archived or migrated by Tivoli Storage
FMV1091E Communications error with server
Manager.
during object query
System action: File skipped.
Explanation: An unexpected communications error
User response: None. occurred during an object query to the server.
System action: Processing stopped.
FMV1087E Access to the specified file or directory
User response: Verify that communications are active
is denied
between the client and server machines. Server outages,
Explanation: Access to the specified file or directory is processor outages, and communication controller
denied. You tried to read from or write to a file and outages can cause this error.
you do not have access permission for either the file or
the directory.
FMV1092W No files matching search criteria were
System action: Processing stopped. found

User response: Ensure that you specified the correct Explanation: You entered a search pattern or file name
file or directory name, correct the permissions, or that cannot be found in the server database.
specify a new location.
System action: Processing stopped.
User response: Ensure that your search pattern is
FMV1088E File space 'filespace-name' does not exist
correct, or specify a new search string.
Explanation: The specified file space (domain) is
incorrect or does not exist on the machine.
FMV1093E Your Tivoli Storage Manager server does
System action: Processing stopped. not support point-in-time processing.

User response: Retry the operation specifying an Explanation: The client has requested a point-in-time
existing domain (drive letter or file system name). query or restore operation, but the Tivoli Storage
Manager server to which the client is connected does
not support point-in-time operations.
FMV1089E Destination directory path length
exceeds system maximum System action: Processing stopped.

Explanation: The path name specified plus the path User response: Make sure that you are connected to
name in the restored file name combine to create a the correct Tivoli Storage Manager server. If you are
name whose length exceeds the system maximum. connected to the correct server, then try the command
again without specifying any point-in-time options.
System action: Processing stopped.
User response: Specify a destination path that, when FMV1094E Server does not support Query Node
combined, is less than the system maximum. command.
Explanation: The server to which you are connected
does not support Query Node command.
System action: Processing stopped.

280 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1096S • FMV1103E

User response: Use a TSM Server that supports Query

FMV1100E File 'filename' not previously backed up
Node command.
Explanation: You tried to give access to a file, which
is not stored on the server.
FMV1096S Either the node does not exist on the
server or there is no active policy set for System action: Processing stopped.
the node.
User response: Ensure that the correct filename is
Explanation: This error occurs when you try to access specified.
another node's data. Either the node is not registered
with the Tivoli Storage Manager server, or there is no
FMV1101E User is not authorized to encrypt
active policy set for the node.
file-space namedirectory_pathfile_name.
System action: Processing stops.
Explanation: The user is not authorized to encrypt the
User response: Verify that the node whose data you file. Normally, only a IBM Tivoli Storage Manager
are trying to access is registered with the Tivoli Storage authorized user or a root user can use IBM Tivoli
Manager server. If you have more than one Tivoli Storage Manager encryption. However, a certain
Storage Manager server, make sure you are connecting combination of PASSWORDACCESS and
to the correct server, then try the operation again. If the ENCRYPTKEY options may allow encryption
problem persists, contact your Tivoli Storage Manager operations by a non-authorized user.
administrator for further assistance.
System action: The file is not backed up or restored.
User response: Log in as a root or IBM Tivoli Storage
FMV1097E The client help text cannot be read from
Manager authorized user and try the operation again.
the help file.
See IBM Tivoli Storage Manager Backup-Archive Client
Explanation: The help file was opened successfully Installation and User's Guide for the correct usage of
and its table of contents are available, but there is a the ENCRYPTKEY option.
problem reading the text from the help file.
System action: Processing stopped. FMV1102E An excessive number of command line
arguments are passed to the program.
User response: If the DSM_DIR environment variable
is set, verify that it points to the directory containing Explanation: This command processing routine
the current level of Tivoli Storage Manager program received more operands than it can use. The rules are:
files, then try the operation again. If the problem v Query can contain only one file specification.
recurs, re-install the Tivoli Storage Manager client
v Restore and Retrieve can contain two file
software. If the problem persists, IBM technical support
specifications.
for further assistance.
v Archive, Incremental, and Selective can contain a
maximum of 20 file specifications. To bypass the
FMV1098E Process terminated; Program memory 20-operand limit, use the -REMOVEOPERANDLIMIT
exhausted. option on the failing archive, incremental, or
Explanation: The program used all available storage. selective command.

System action: Processing stopped. Note: The Tivoli Storage Manager Client operates much
User response: Free any unnecessary programs (TSRs) more efficiently if it expands wild cards internally,
that are running, and retry the operation. Reducing the rather than accepting the expanded list from the shell.
scope of queries and the amount of data returned can System action: Processing stopped.
also solve the problem.
User response: Reduce the number of arguments and
retry the operation. For UNIX-based systems, ensure
FMV1099E File 'filename' not previously archived that you have surrounded the specification containing
Explanation: You tried to give access to a file, which pattern matching characters with quotes. As an
is not stored on the server. alternative, use the -REMOVEOPERANDLIMIT option
on the failing archive, incremental, or selective
System action: Processing stopped. command.
User response: Ensure that the correct filename is
specified. FMV1103E Invalid management class entered
Explanation: You entered an invalid management
class.

Chapter 6. FMV messages 281

FMV1104E • FMV1111E

System action: Tivoli Storage Manager is unable to do

FMV1108E Invalid option (option) for the function
the requested operation.
command
User response: Retry the operation using a valid
Explanation: There are two possible reasons for this
management class.
message:
v The option option was specified for a command or
FMV1104E The management class for this file does subcommand (function) that cannot make use of that
not have a valid archive copy group. option.
This file will not be archived.
v The option appears on the initial command line and
Explanation: The management class for this file does is not valid there.
not have an archive copy group specified. This file will
System action: Processing stopped.
not be archived.
User response: See the Backup-Archive Client
System action: Processing stopped.
Installation and User's Guide for correct use of the
User response: Add a valid archive copy group to the named option.
management class, and then retry the operation.
FMV1109E User is not authorized to encrypt the
FMV1105E The management class for this file does file.
not have a valid backup copy group.
Explanation: The user is not authorized to encrypt the
This file will not be backed up.
file. Normally, only a Tivoli Storage Manager
Explanation: The management class for this file does authorized user or a root user can use Tivoli Storage
not have a backup copy group specified. This file will Manager encryption. However, a certain combination of
not be backed up. PASSWORDACCESS and ENCRYPTKEY options may
allow encryption operations by a non-authorized user.
System action: Processing stopped.
System action: The file is not backed up or restored.
User response: Add a valid backup copy group to the
management class, and then retry the operation. User response: Log in as a root or Tivoli Storage
Manager authorized user and retry the operation. Refer
to Backup-Archive Client Installation and User's Guide for
FMV1106E ENCRYPTKEY SAVE not configured the correct usage of the ENCRYPTKEY option.
correctly. Encryption not used.
Explanation: This message is issued for TSM FMV1110E The client help file file-name could not
Authorized Users and root users when ENCRYPTKEY be opened.
SAVE and PASSWORDACCESS PROMPT options are
set. Please note that these are the default values. These Explanation: This usually occurs when the help file
values do not allow encryption. file-name cannot be found.
System action: The file is not encrypted. System action: Processing stopped.
User response: To save encryption keys, you must User response: If the DSM_DIR environment variable
change configuration values. Add PASSWORDACCESS is set, verify that it points to the directory containing
GENERATE to your system option file. the current level of Tivoli Storage Manager program
files, then try the operation again. If the problem
recurs, re-install the Tivoli Storage Manager client
FMV1107E Invalid option/value: 'option' software. If the problem persists, IBM technical support
Explanation: You specified an incorrect Tivoli Storage for further assistance.
Manager option or option value.
System action: For the command line client: FMV1111E The table of contents cannot be read
Processing stops. from the help file.

For the native GUI client: There is a small set of Explanation: The help file was opened successfully
options critical to the initialization of the client. If an but there was a problem reading the table of contents.
error is found in one of these, this message is presented System action: Processing stopped.
and the client terminates without further processing.
User response: If the DSM_DIR environment variable
User response: Specify a correct Tivoli Storage is set, verify that it points to the directory containing
Manager option as defined in the appropriate Using the the current level of Tivoli Storage Manager program
Backup-Archive Client book for the particular operating files, then try the operation again. If the problem
system. recurs, re-install the Tivoli Storage Manager client

282 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1113E • FMV1121I

software. If the problem persists, IBM technical support

FMV1117E The PICK and LATEST options are not
for further assistance.
valid together
Explanation: During a restore, PICK and LATEST
FMV1113E The snapshot cache location is not valid.
options cannot be used together.
Explanation: The snapshot cache location must point
System action: Processing stopped.
to a local volume that is formatted with NTFS. The
default cache location is on the same volume where the User response: Try again using either the PICK or the
snapshot is being performed. The operation will LATEST option.
continue without snapshot support.
System action: The client does not execute the FMV1118I Invalid file space number entered. Try
snapshot backup operation. again.
User response: Specify a different snapshot cache Explanation: The number that represents a file space
location using the SNAPSHOTCACHELOCATION was incorrect while you were using the PICK option.
option.
System action: Tivoli Storage Manager waits for your
specification.
FMV1114I Waiting for mount of offline media.
User response: Enter a correct file space number.
Explanation: The server is waiting for the requested
media to become available before the operation can
FMV1119I Initiating the removal of 'filespace-name'
continue.
file space.
System action: Tivoli Storage Manager waits for
Explanation: Indicates that file space deletion has
requested data.
started on the specified filespace-name.
User response: None.
System action: None.
User response: None.
FMV1115W File 'file-namefile-namefile-name' excluded
by Include/Exclude list
FMV1120E Removal of file space 'filespace-name'
Explanation: You can not back up, archive, or migrate
failed
files that are excluded.
Explanation: An attempt was made to delete a
System action: Tivoli Storage Manager does not
filespace (either NAS or normal) and it was
process the file.
unsuccessful.
User response: If the file is intentionally excluded, v Your client registration may not be authorized to
then this message can be ignored. Otherwise modify delete filspaces on the server. Look for message
the include/exclude list, restart the client, and try the FMV1126E.
operation again. Contact your Tivoli Storage Manager
v The named filespace does not exist on the server.
administrator for further assistance.
Look for message FMV1122W.
v Other causes which will be made known in messages
FMV1116E The process is running in a following this one
non-interactive mode, but requires user
input. System action: processing stops.

Explanation: This process requires keyboard input, User response: Take action as recommended by other
but non-interactive processes are unable to read input messages that accompanies this one. If so indicated, try
from keyboard. to remove the file space again. If the problem
continues, your Tivoli Storage Manager administrator
System action: processing stops. has the authority to delete the file space for you.
User response: Perform the following actions to
resolve this error: FMV1121I A request for removal of file space
v Run the product in interactive mode. 'filespace-name' has been successfully sent
v Ensure your password is set correctly. to the server.
Explanation: Tivoli Storage Manager has requested
deletion of the specified filespace-name. The deletion
process may not have actually been completed when
this message is displayed. To verify successful deletion,
consult the server logs.

Chapter 6. FMV messages 283

FMV1122W • FMV1130E

It is possible for errors to occur on the server during

FMV1127E Your node does not have permission to
the deletion process, or the file space might contain
delete archived files.
archive objects in deletion-hold status. In either case,
the file space will not be deleted. Explanation: You cannot delete archived files unless
your Tivoli Storage Manager administrator has
System action: None.
authorized your node to do so.
User response: None.
System action: Tivoli Storage Manager does not delete
the archived files.
FMV1122W File space 'filespace-name' does not exist
User response: Use the DSMC QUERY SESSION
on the server. The file space might have
command to verify your authorization. Ask your Tivoli
been deleted by another client using
Storage Manager administrator to provide the
your client's node name or an
necessary authorization.
administrator.
Explanation: The specified filespace-name does not exist
FMV1128S The management class assigned to
on the server. Your system administrator deleted the
directories does not exist.
file space or another client using your client’s node
name might have deleted it. Explanation: The management class named on the
DIRMC option does not exist in your assigned policy
System action: None.
set on the server. The error log contains an entry
User response: None. showing the invalid management class name.
System action: processing stops.
FMV1123E The vertical screen dimension is too
User response: Remove the current DIRMC option
small to display the Help directory.
from the client options file, then run DSMC QUERY
Increase your window height.
MGMTCLASS -DETAIL to view information about
Explanation: Execution of the HELP command available management classes. Make sure the
requires space for both the user prompts and at least management class you select has a backup copy group.
one line of the HELP directory. If you have more than one Tivoli Storage Manager
server, make sure you are connecting to the correct
System action: The help directory is not displayed, server. If you are unable to find a suitable management
and the help command cannot complete. class, contact your Tivoli Storage Manager
User response: Increase the size of your display administrator for further assistance.
window to allow more rows of text to be displayed.
FMV1129S There is no backup copy group in the
FMV1125E Unmatched Quotes: 'string' management class used for directories.

Explanation: The quotes specified in the pattern are Explanation: The DIRMC option names a
not the same and do not make a set. management class that contains no backup copy group.

System action: Processing stopped. System action: processing stops.

User response: Correct the pattern using matching User response: Remove the current DIRMC option
quotes in the syntax. from the client options file, then run DSMC QUERY
MGMTCLASS -DETAIL to view information about
available management classes. Make sure the
FMV1126E The file space cannot be deleted because management class you select has a backup copy group.
this node does not have permission to If you have more than one Tivoli Storage Manager
delete archived or backed up data. server, make sure you are connecting to the correct
Explanation: You cannot delete the file space data server. If you are unable to find a suitable management
unless your Tivoli Storage Manager administrator has class, contact your Tivoli Storage Manager
authorized your node to do so. Authorization permits administrator for further assistance.
you to delete backup data, archive data, or both.
System action: Delete processing fails. FMV1130E The drive has no label. The operation
cannot continue.
User response: Use the DSMC QUERY SESSION
command to verify your authorization. Ask your Tivoli Explanation: Backup or archive of removable media
Storage Manager administrator to provide the requires that the media have a volume label. An
necessary authorization or to delete the file space for attempt was made to back up or archive data on a
you. removable volume that has no label.
System action: The requested operation does not run.

284 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1131E • FMV1139W

User response: Create a volume label on the

FMV1135E Drive drive-name1 is a virtual drive of
removable media, then try the operation again.
drive-name2. It cannot be backed up or
archived.
FMV1131E A duplicate volume label exists. The
Explanation: Drive drive-name1 was found to be a
operation cannot continue.
substitute (SUBST) of drive drive-name2. The SUBST
Explanation: For removable media, Tivoli Storage drive cannot be backed up or archived.
Manager uses the volume label as the file space name.
System action: The SUBST drive is skipped.
To prevent data from different volumes being stored in
Processing continues with the next drive.
the same file space on the Tivoli Storage Manager
server, backup or archive of removable media volumes User response: Do not specify any file specifications
having duplicate volume labels is not allowed. for a drive that is a substitute of another drive. Remove
any explicit substitute drives from the DOMAIN
System action: The requested operation does not run.
statement or use the -<drive:> notation to remove a
User response: Change the volume labels on the substitute drive if ALL-LOCAL is specified.
removable media volumes so that there are no
duplicate labels. Then restart Tivoli Storage Manager
FMV1136E Not file owner
and try the operation again.
Explanation: The file cannot be backed up because the
client is not the file owner.
FMV1132E 'Access rule' Access Rule already defined
for node 'node'. Old rule must be deleted System action: Tivoli Storage Manager skips the file.
before new one can be defined.
User response: None.
Explanation: You are trying to define authorization for
the specified node, which already has authorization
FMV1137W Invalid Index 'number' skipped.
defined.
Explanation: An incorrect number was entered for the
System action: Tivoli Storage Manager did not
Index.
redefine authorization for the specified node.
System action: Processing stopped.
User response: Update the authorization, or delete the
old rule and define a new one, or use the current User response: Correct the Index entry and retry the
authorization. operation.

FMV1133W An expression might contain a wildcard FMV1138E The 'command-name' command must be
not enclosed in quotes. followed by a subcommand
Explanation: The command cannot be processed Explanation: You entered an incomplete
because a UNIX shell expands a wildcard expression, command-name.
such as an asterisk (*) or a question mark (?), that has
no quotes. System action: Processing stopped.

If the expression contains no wildcard characters and User response: Enter the correct syntax of the
you wish to place more than the stated limit of command and continue.
operands on the Archive, Selective, or Incremental
command, add the -REMOVEOPERANDLIMIT option FMV1139W 'object-nameobject-nameobject-name' was
to the command, and try it again. restored as 'temp-name'. A reboot is
System action: Command dependent. required to complete the restore.

User response: Enclose the wildcard expression in Explanation: The file being restored was in use by
quotes, or add the -REMOVEOPERANDLIMIT option another application, so it could not be immediately
and enter the command again. replaced. The file will be replaced during the next
reboot of the operating system. It is important to note
that until the reboot occurs, the system or its
FMV1134E Drive drive-name is an invalid drive applications might be unstable. The degree of
specification instability depends on the criticality of the file to the
operating system or applications.
Explanation: The specified drive-name was found to be
invalid; the drive probably has not been defined. System action: Tivoli Storage Manager restored the
file with a temporary name, and instructed the
System action: Tivoli Storage Manager skips the
operating system to replace the original file with the
invalid drive and continues to the next drive.
restored file during the next boot of the operating
User response: Check the invalid drive. system.

Chapter 6. FMV messages 285

FMV1140E • FMV1150E

User response: Reboot the machine as soon as

FMV1146E Macro file 'file spec' cannot be opened.
possible after the Tivoli Storage Manager restore
operation ends. Explanation: A macro command has been entered that
specifies the macro file name shown. However, that file
cannot be opened for reading.
FMV1140E Invalid format for Set Access command.
System action: The macro is ignored and an error is
Explanation: The SET ACCESS command must have
returned.
at least three operands, the first of which must be
either BACKUP or ARCHIVE. A validly formed file User response: Enter the command with the proper
specification must follow. macro name.
System action: Processing stopped, the command is
not executed. FMV1147E File is temporarily unavailable.
User response: Use the HELP SET ACCESS command Explanation: File is temporarily unavailable.
for complete details of usage, then enter the SET
System action: File skipped.
ACCESS command using the correct syntax.
User response: Check and see if file is locked by other
process. If not, retry the command.
FMV1141W Unknown command - command-name
Explanation: You entered an incorrect command-name.
FMV1148I 'Command-name' command successfully
System action: None. completed
User response: Enter the correct command. Explanation: The specified command-name was
successfully completed.
FMV1143E The DIRSONLY and FILESONLY System action: Tivoli Storage Manager completed the
options are not valid together command.
Explanation: The DIRSONLY and FILESONLY options User response: Continue with normal operations.
cannot be used together.
System action: Processing stopped. FMV1149E No domain is available for incremental
backup. The domain may be empty or
User response: Try again using either the DIRSONLY
all file systems in the domain are
or the FILESONLY option.
excluded.
Explanation: An incremental backup was started, but
FMV1144W Password authentication not active on
no domain was selected. There are two possible reasons
server
for this message:
Explanation: None. v The client is a diskless workstation for which no
System action: Processing stopped. local file systems exist.
v An attempt was made to back up a file system that is
User response: Because password authentication is excluded with the EXCLUDE.FS option.
turned off on the server, you do not need to update the
password. System action: processing stops.
User response: Choose a domain and restart the
FMV1145E The maximum macro nesting level has incremental backup. Make sure that the DOMAIN
been exceeded. Macros may be nested statement specifies the file systems you wish to back
up to 10 levels. up. Prevent this message by not trying to back up the
file system that is excluded with EXCLUDE.FS. If this
Explanation: Tivoli Storage Manager allows macros to file system should be backed up, then remove the
invoke other macros, for example, macro 'A' invokes EXCLUDE.FS option.
macro 'B' which, in turn, invokes macro 'C'. This is
nesting to 3 levels. The limit is 10 levels (the inital
macro plus nine levels of calls within macros currently FMV1150E Unable to restore current user profile
executng). There is no limit to the number of different because you are running as a local
macro calls that may be made within a macro as long system account.
as the calls are not nested.
Explanation: The local system account does not have a
System action: The macro is ignored and an error is profile. Therefore you cannot restore its profile.
returned.
System action: Processing stops.
User response: Reduce the level of macro nesting.

286 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1151E • FMV1158E

User response: Log on to the user whose profile you User response: If the file name and path are not
want to restore. corrupted, process the file in the locale for which it is
valid.
FMV1151E 'drive-name1' is not a cluster disk.
FMV1155E No domain is available for image
Explanation: The indicated file system is not a cluster
backup.
disk. Because the CLUSTERNODE option is set to YES,
the file system cannot be backed up or archived. Explanation: An image backup was started, but no
domain was specified.
System action: Processing stops.
System action: Processing stopped.
User response: If the CLUSTERNODE option is
incorrectly set to YES, then change the option to NO User response: Choose a domain and restart the
and try the operation again. Otherwise see the client image backup. Set the image domain using the
manual for further information about configuring the domain.image option in your dsm.opt file, either
Tivoli Storage Manager client to run in a cluster manually, or by using the GUI preferences editor.
environment.
FMV1156E NODENAME cannot be the local
FMV1152W The kernel level is below the required machine name when CLUSTERNODE is
level for LVM support. No LVM set to YES
volumes will be available for image
Explanation: When Tivoli Storage Manager is running
operations.
as a cluster node, the node name cannot be the local
Explanation: The LVM support for image operations machine name.
requires kernel level to be minimum at 2.6. LVM
System action: Processing stops.
volumes will not be recognized by the Tivoli Storage
Manager client. User response: Change the node name either to the
cluster name or to any other name, and restart Tivoli
System action: All subsequent logical volume
Storage Manager.
operations on LVM volumes will fail.
User response: Use earlier versions of the client that
FMV1157E The registry cannot be backed up or
support LVM1 to perform the logical volume
restored when the client is running as a
operations. Alternatively, you can upgrade the kernel to
cluster node.
the required level to fully utilize logical volume
operations on LVM2. Explanation: When the CLUSTERNODE option is set
to YES, the registry cannot be backed up or restored.
FMV1153E 'drive-name1' is a cluster disk. System action: The registry is not backed up or
restored.
Explanation: The indicated file system is a cluster
disk. Because the CLUSTERNODE option is set to NO, User response: If the CLUSTERNODE option is
the file system cannot be backed up or archived. incorrectly set to YES, then change the option to NO
and try the operation again. Otherwise see the client
System action: Processing stops.
manual for further information about configuring the
User response: If the CLUSTERNODE option is Tivoli Storage Manager client to run in a cluster
incorrectly set to NO, then change the option to YES environment.
and try the operation again. Otherwise see the client
manual for further information about configuring the
FMV1158E The event logs cannot be backed up or
Tivoli Storage Manager client to run in a cluster
restored when the client is running as a
environment.
cluster node.
Explanation: When the CLUSTERNODE option is set
FMV1154E Object name 'filespace
to YES, the event logs cannot be backed up or restored.
namepath-namefile-name' contains an
invalid multibyte sequence for the System action: The event logs are not backed up or
current locale. restored.
Explanation: An illegal multibyte sequence for the User response: If the CLUSTERNODE option is
current locale was found in the object name. Either the incorrectly set to YES, then change the option to NO
path or file name has been corrupted or is coded in a and try the operation again. Otherwise see the client
language other than that of the current locale. manual for further information about configuring the
Tivoli Storage Manager client to run in a cluster
System action: Object skipped.
environment.

Chapter 6. FMV messages 287

FMV1159E • FMV1181E

file system type as the source.

FMV1159E The specified file is being used by
another process
FMV1168E ERROR: could not create image object.
Explanation: The specified file is being used by
another process. You tried to read from or write to a Explanation: Creation of the image object failed for
file that is currently being used by another process. one of the following reasons:
System action: Processing stopped. v The image command was executed by a non-root
user
User response: Ensure that you specified the correct
v The image plugin library was not found.
file or directory name, correct the permissions, or
specify a new location. System action: The requested logical volume function
is not performed.
FMV1162E Filesystem could not be mounted User response: Retry the operation after correcting the
cause for failure.
Explanation: The system call to mount the file system
failed.
FMV1169W There is no table of contents for
System action: The file system remains unmounted.
image-name.
User response: Use the mount command to mount the
Explanation: The image item for which a table of
file system. On AIX, run fsck if requested by the
contents was requested is either a RAW logical volume
operating system.
or it was backed up without the -TOC option.
System action: No table of contents is displayed.
FMV1163E Filesystem could not be unmounted.
User response: Select another image object for TOC
Explanation: The system call to unmount the file
display.
system failed.
System action: The logical volume operation is not
FMV1170I Invalid selection number entered. Try
performed.
again.
User response: Make sure the device or file system is
Explanation: You entered a number not shown in the
not being accessed, then retry the operation.
list of images. It is either less than one or greater than
the highest item number displayed.
FMV1164E Filesystem is not mounted
System action: Tivoli Storage Manager waits for you
Explanation: The named file system is not currently to enter a valid selection.
mounted. It must be mounted for Tivoli Storage
User response: Enter a number from the list or 'Q' to
Manager to perform an image backup.
quit.
System action: The logical volume operation is not
performed.
FMV1177E Must specify a path for this operation.
User response: Mount the file system.
Explanation: A path must be specified for this
operation to execute successfully.
FMV1165E Destination is smaller than source
System action: Processing stops.
Explanation: The space allocation for the selected
User response: Specify a valid path and execute the
destination is smaller than the source.
command again.
System action: The restore operation is not performed.
User response: Choose a different, bigger destination FMV1181E There was a communication failure with
or increase the size of the destination file space. the journal service.
Explanation: An error occurred using named pipe
FMV1166E Source and destination are not the same communication with the journal service.
file system type.
System action: Processing stops.
Explanation: The source and destination file system
User response: Restart the journal service, then try the
types do not match.
operation again. If the problem persists, contact IBM
System action: The requested logical volume technical support for further assistance.
operation is not performed.
User response: Choose a destination that has the same

288 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1183E • FMV1192E

FMV1183E An unknown error occurred while FMV1187E The named helpfile "filename" has
processing system object 'sys-obj-name': invalid content.
MS API function 'func-name' failed with
Explanation: The named file does not have the proper
error error (error)
content to support the help command. One or more
Explanation: An unknown error occurred while sections could not be identified.
processing a system object. The error information
System action: The help command is terminated.
captured indicates the reason for the failure. This
information can be used to diagnose the problem. User response: During installation of Tivoli Storage
Manager a proper help file was created. Your system
System action: Tivoli Storage Manager ended the
administrator can assist you with retrieving the original
current operation.
help file to replace the named invalid file.
User response: Contact your system administrator for
more information.
FMV1188E The selected filesystem is managed by
HSM, and therefore is not a valid object
FMV1184W The command subcommand command is for image operations
not supported on this client.
Explanation: Due to the nature of HSM, image backup
Explanation: The command subcommand command is is not allowed on managed filesystems.
not supported for the client running on this operating
System action: The requested logical volume
system on this computer.
operation is not performed.
System action: The command is not processed.
User response: None.
User response: None.
FMV1189E The DIRSONLY and V2ARCHIVE
FMV1185E The help search argument you supplied options are not valid together
"string" is either too long or contains
Explanation: The DIRSONLY and V2ARCHIVE
unmatched quotes.
options cannot be used together.
Explanation: Valid arguments are the names of things
System action: Processing stopped.
like section numbers, command names, option names
and message numbers. All of these search arguments User response: Try again using either the DIRSONLY
are short and none requires quoting. or the V2ARCHIVE option.
System action: The help request is not executed and
you are given another chance to enter a valid FMV1190E Symbolic link 'linkname' to 'target' was
argument, display the table of contents, or exit help. successfully deleted.
User response: Respond to the subsequent prompt as Explanation: Log 'linkname' cannot be a symbolic link.
directed.
System action: The symbolic link 'linkname' is deleted,
the log is recreated, and processing stops.
FMV1186I The help file contains no message help
section. Requests for message help will User response: Check the location of the new file. To
all result in topic not found. Enter a specify the location of log files, refer to the user's
section number, option name, command manual for the 'errorlogname' option, the
name, or a command and subcommand. 'schedlogname' option, and the 'DSM_LOG'
Otherwise press enter or 't' to display environmental variable.
the table of contents or 'q' to exit help:
Explanation: The named file does not have the proper FMV1191E Unable to delete symbolic link 'link'.
content to support the help command for messages. Explanation: Log 'linkname' cannot be a symbolic link.
The initial scan of the help file found no messages
section. System action: Processing stops.

System action: The help command pauses and allows User response: Delete the symbolic link 'linkname'.
you to make another selection.
User response: During installation of Tivoli Storage FMV1192E Specifying the error log 'link' as a
Manager a proper help file was created. Your system symbolic link is not allowed.
administrator can assist you with retrieving the original Explanation: Error log 'linkname' cannot be a symbolic
help file to replace the named invalid file. link.
System action: The symbolic link 'linkname' is deleted,

Chapter 6. FMV messages 289

FMV1193E • FMV1201E

the error log is recreated, and processing stops.

FMV1199E The PRESNAPSHOTCMD command
User response: Check the location of the new error failed. The image snapshot backup will
log. To specify the location of the error logs, refer to the not be executed.
user's manual for the 'errorlogname' option and
Explanation: The command specified by the
'DSM_LOG' environmental variable.
PRESNAPSHOTCMD option must complete
successfully in order to execute the image snapshot
FMV1193E Specifying the trace file 'link' as a backup. If the command completed with a return code
symbolic link is not allowed. of 0 (zero), it is considered to have completed
successfully. If the command completed with any other
Explanation: For reasons of security and system return code, it is considered to have failed. If the
integrity, the trace file 'linkname' cannot be a symbolic command failed then the image snapshot backup is not
link. executed.
System action: The symbolic link 'linkname' is deleted, System action: The client does not execute the image
the trace file is recreated, and processing stops. snapshot backup operation.
User response: Use the TRACEFILE option to specify User response: Identify and repair the problem that
the actual trace file location without the use of caused the command to fail. If a non-zero return code
symbolic links. is normal for this command, then consider wrapping
the command in a script that always exits with a return
FMV1194E Specifying the schedule log 'link' as a code of zero.
symbolic link is not allowed.
Explanation: Schedule log 'linkname' cannot be a FMV1200W The POSTSNAPSHOTCMD command
symbolic link. completed with a non-zero return code.

System action: The symbolic link 'linkname' is deleted, Explanation: If the command specified by the
the schedule log is recreated, and processing stops. POSTSNAPSHOTCMD option completed with a
non-zero return code, then the image snapshot backup
User response: Check the location of the new schedule operation will continue, but with a warning-level
log. To specify the location of the schedule log, refer to result. Note that the result of the
the user's manual for the 'schedlogname' option. POSTSNAPSHOTCMD command will not supercede a
higher result from the image snapshot backup
FMV1197E The snapshot cache size was exceeded command. For example, if the image snapshot backup
during the snapshot backup. command completed with a return code of 12, the
image snapshot backup will be considered to have
Explanation: The image snapshot backup was not able completed with a return code of 12, regardless of the
to complete because while creating the snapshot Tivoli outcome of the POSTSNAPSHOTCMD command.
Storage Manager exceeded the snapshot cache size
allowed via the SNAPSHOTCACHESize option. System action: The image snapshot backup continues,
but with a warning return code of at least 8.
System action: Processing stopped.
User response: Identify and repair the problem that
User response: Increase the SNAPSHOTCACHESize caused the command to fail. If a non-zero return code
value for this volume and retry the operation. is normal for this command, then consider wrapping
the command in a script that always exits with a return
FMV1198E An invalid snapshot cache location was code of zero.
entered: path.
Explanation: The SNAPSHOTCACHELocation option FMV1201E Tivoli Storage Manager cannot build a
value entered for this volume is not valid. The value directory path because a file exists with
for this option must be an existing, full directory path. the same name as the directory.

System action: Processing stopped. Explanation: None

User response: Enter a valid System action: Processing stopped.

SNAPSHOTCACHELocation value and try the User response: Remove or rename the file that has the
operation again. same name as the directory. Alternatively, you can
restore the directory to a different location.

290 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1202E • FMV1214E

FMV1202E TOC backup for the image failed. Check FMV1207E No TOC has been previously backed up
log files. for this file system.
Explanation: An error occurred during backup of the Explanation: The user is trying to query the TOC of a
table of contents. Check the error log for more file system. TOC backup for that file system has not
information. been previously done.
System action: The requested logical volume System action: Query stopped.
operation is not performed.
User response: Backup the file system again with
User response: Check error log. -TOC option.

FMV1203E Table of Contents not available for FMV1209E The option_name option is not supported
selected backup set. Please contact with the command_name command using
server administrator. the -FILELIST option.
Explanation: There is no TOC for selected backup set Explanation: The specified option is not supported
with the specified command when the -FILELIST
System action: Expansion of selected backup set will
option is also specified.
not be possible. Will only be able to restore the whole
backup set. System action: The command is not processed.
User response: Please contact server administrator to User response: >Do not specify the offending option
regenerate TOC for backup set before backup set can be when the -FILELIST option is specified with this
expanded. command.

FMV1204E This client is not supported by the FMV1212I Invalid Process number entered. Try
Tivoli Storage Manager express server again.
Explanation: This client is not supported by the IBM Explanation: You entered a number not shown in the
Tivoli Storage Manager express server. This can occur list of processes. It is either less than one or greater
if: than the highest item number displayed.
1. the client is configured as an Tivoli Storage System action: Tivoli Storage Manager waits for you
Manager express client using the CLIENTVIEW to enter a valid selection.
option
User response: Enter a number from the list or 'Q' to
2. the client is trying to connect to an Tivoli Storage
quit.
Manager express server.
System action: Processing stops.
FMV1213W Snapshot image backup is not possible
User response: Log in using a supported Tivoli for device device-name. starting static
Storage Manager express client. image backup.
Explanation: On Linux platforms, snapshot image
FMV1205E This is not a supported Tivoli Storage backup is only possible for logical volumes created by
Manager express platform the Linux logical volume manager (LVM). Since the
default image backup type is snapshot, backing up a
Explanation: This is not a supported Tivoli Storage
partition which is not created using LVM automatically
Manager express platform.
leads to a static image backup.
System action: Processing stops.
System action: Snapshot image backup will failover to
User response: Log in using a supported Tivoli static image backup
Storage Manager express client.
User response: To avoid this message, use the
imagetype option to specify static or dynamic image
FMV1206E TOC backup of a raw device is not backup.
supported. But the raw device is backed
up.
FMV1214E The logical volume group does not have
Explanation: TOC backup of a raw device is not enough free space to contain the volume
supported. But the raw device is backed up. snapshot.

System action: Raw device is backed up with no TOC Explanation: The snapshot is created in the volume
object. group that contains the logical volume being backed

User response: NONE.

Chapter 6. FMV messages 291

FMV1215E • FMV1222E

up. There is insufficient free space in the volume group System action: Tivoli Storage Manager initialization
to contain the snapshot. fails and the program ends.
System action: The operation ends. User response: See the Tivoli Storage Manager
administrator for your system, and make sure that the
User response: Decrease the SNAPSHOTCACHESIZE
server to which you are trying to connect, has a valid
value or make additional space available in the logical
TCPSERVERADDRESS defined in the system options
volume group. Then try the operation again.
file.

FMV1215E On volumes that are RAW or formatted

FMV1219E A virtual node name must not equal
FAT32 the snapshot cache location
either a node name or the system host
cannot be located on the same volume
name.
that is being backed up.
Explanation: A VIRTUALNODENAME option was
Explanation: When the snapshot cache location is
entered with a name the same as either a NODENAME
located on the same volume that is being backed up the
option or the system host name.
volume must be formatted with NTFS. The default
cache location is on the same volume where the System action: Initialization fails and the program
snapshot is being performed. ends.
System action: The client does not execute the image User response: If the virtual node name entered was
snapshot backup operation. the same as the host name, remove the virtual node
name option. If it was the same as the node name
User response: Specify a different snapshot cache
option, you can remove either one, depending upon the
location using the SNAPSHOTCACHELOCATION
intended usage. Node name is used to assign an
option.
alternate name to your system. Virtual node name is
used to access another system's server data.
FMV1216E Not authorized to run Tivoli Storage
Manager. See the administrator for your
FMV1220E The Tivoli Storage Manager server is
system.
out of resources.
Explanation: The system options file for the server
Explanation: A lack of a storage resource or a
that you are attempting to connect to contains a user
maximum value condition does not allow any new
entry, a group entry, or both a user and group entry.
activity.
Your user ID, or group ID, was not found in any of the
entries. You are currently not authorized to run Tivoli System action: Tivoli Storage Manager canceled the
Storage Manager to this server. current operation.
System action: Tivoli Storage Manager initialization User response: Try the operation again at a later time.
fails and the program ends. If the problem continues, contact your Tivoli Storage
Manager administrator to isolate what resource is
User response: See the Tivoli Storage Manager
unavailable. The Tivoli Storage Manager administrator
administrator for your system, and ask to be added to
can check the Tivoli Storage Manager server activity log
the user or group list for this server.
for messages that might explain the problem.

FMV1217E Server name not found in System

FMV1221E Transaction aborted
Options File
Explanation: The current transaction between the
Explanation: The system options file does not contain
server and the client stopped. A server, client, or
the SERVERNAME option.
communication failure cannot be recovered.
System action: Tivoli Storage Manager initialization
System action: Tivoli Storage Manager canceled the
fails and the program ends.
current operation.
User response: See the Tivoli Storage Manager
User response: Retry the operation. If the problem
administrator for your system, and make sure that the
continues, see your system administrator to isolate the
system options file contains the server name.
problem.

FMV1218E TCPSERVERADDRESS not defined for

FMV1222E Disk space limit for this process reached
this server in the System Options File
Explanation: The disk space allocated for the client
Explanation: The TCPSERVERADDRESS for this
owner is full.
server is not defined in the server name stanza in the
system options file. System action: Processing stopped.

292 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1223E • FMV1231E

User response: Free up disk space and retry the

FMV1227E Processing stopped; Disk full condition
restore or retrieve operation.
Explanation: No more files can be restored or
retrieved because the destination disk is full.
FMV1223E File is not compressed; System failure.
System action: Processing stopped.
Explanation: A file that was flagged as compressed
was not compressed, and the system failed. User response: Free up disk space, or restore or
retrieve the file to another disk.
System action: Processing stopped.
User response: See your system administrator to
FMV1228E Sending of object 'object-nameobject-
report this problem. This error is a system failure.
nameobject-name' failed.
Explanation: The specified file (object-name) cannot be
FMV1224E File compressed on a different client
sent to the server. This message is accompanied by at
machine that has more memory
least one other message that has more specific
Explanation: You are trying to restore a file that was information about why the file could not be processed.
backed up and compressed on another client
System action: File skipped.
workstation that had more memory than your client
workstation. You cannot restore this file. When the file User response: Check previous messages pertaining to
is restored, it is expanded and your workstation does this file that indicate the reason for the failure. Where
not have enough memory. applicable, correct the conditions that prevented the file
from being sent to the server. The specific corrective
System action: Tivoli Storage Manager canceled the
actions will depend on the reason for the failure.
operation.
User response: Obtain a machine with more memory
FMV1229E MODE=INCREMENTAL is not valid on
and retry the operation.
file-space. Image backup not processed.
Explanation: Because the file space has been the
FMV1225E Insufficient memory for file
subject of at least one progressive incremental backup,
compression/expansion
the MODE=INCREMENTAL option (incremental by
Explanation: Not enough memory is available to do image date) cannot be used with the backup image
data compression or expansion. For a restore or command.
retrieve, the file cannot be recalled from the server until
System action: File system skipped.
more storage is made available. For a backup or
archive, try running without compression if storage User response: If an image backup of the named file
cannot be made available. space is desired, retry the command without the
MODE=INCREMENTAL option. To prevent this
System action: Processing stopped.
behavior in the future, delete the file space from the
User response: Free up extra storage for the operation server and do only BACKUP IMAGE -mode=selective
to continue, or run the backup or archive process and BACKUP IMAGE -mode=incremental from that
without compression enabled. point on.

FMV1226E Destination file or directory is write FMV1230E Stale NFS File Handle
locked
Explanation: An NFS file system becomes stale.
Explanation: The file or directory being restored or
System action: File system skipped.
retrieved from the server cannot be written to because
the destination is write locked. Another operation User response: Check the NFS mounted filesystem.
might have the file open and will not allow it to be
updated.
FMV1231E No file handles available
System action: File skipped.
Explanation: All file handles for your system are
User response: Either determine which operation has currently in use. No more are available.
the file write locked, or restore the file to another name
System action: Processing stopped.
or location.
User response: Either free some file handles by ending
other processes, or modify your system setup to allow
for more files to be open at the same time.

Chapter 6. FMV messages 293

FMV1232E • FMV1241E

FMV1232E The file exists and cannot be FMV1236E An unexpected error occurred.
overwritten.
Explanation: This is usually caused by a low-level
Explanation: The file being restored or retrieved exists system error or communication error from which Tivoli
and cannot be overwritten due to lack of authority or Storage Manager cannot recover.
access permissions.
System action: Processing stopped.
System action: The file is skipped.
User response: Examine the client error log for any
User response: Verify that you have sufficient access additional messages that might be related to this
permissions to overwrite the file, then try the operation problem. Try the operation again. If the problem
again. If the problem persists, contact your system persists, contact Tivoli Storage Manager technical
administrator or Tivoli Storage Manager administrator support for further assistance.
for further assistance.
FMV1237E A problem has occurred on the Tivoli
FMV1233E An invalid file handle was passed; Storage Manager server.
system error.
Explanation: The Tivoli Storage Manager client error
Explanation: An internal system error occurred: A file log and the Tivoli Storage Manager server activity log
operation failed because of an invalid file handle. might contain additional information about this error.
System action: processing stops. System action: Processing stops.
User response: Try the operation again. If the failure User response: Try the operation again. If the problem
persists, obtain a service trace that captures the persists, examine the Tivoli Storage Manager client
problem and contact IBM technical support for error log and Tivoli Storage Manager server activity log
additional assistance. Your Tivoli Storage Manager for additional information about this error. If the
administrator can help you configure the trace. problem cannot be resolved, then obtain a SERVICE
trace that captures the problem and contact IBM
technical support for additional assistance. Your Tivoli
FMV1234E Protocol violation
Storage Manager administrator can help you configure
Explanation: A communications protocol error the trace.
occurred. The communication subsystem is not
properly defined or is itself in error.
FMV1238S A policy management problem has
System action: Tivoli Storage Manager ended the occurred on the Tivoli Storage Manager
current operation. server.

User response: Verify that the communication Explanation: The Tivoli Storage Manager client error
processes are operating properly, and then retry the log and Tivoli Storage Manager server activity log may
operation. contain additional information about this error.
System action: Processing is stops.
FMV1235E An unknown system error has occurred
User response: Try the operation again. If the problem
from which Tivoli Storage Manager
persists, examine the Tivoli Storage Manager client
cannot recover.
error log and Tivoli Storage Manager server activity log
Explanation: An unknown error occurred. This might for additional information about this error. If the
be a low-level system or communication error from problem cannot be resolved, then obtain a SERVICE
which Tivoli Storage Manager cannot recover. trace that captures the problem and contact IBM
technical support for additional assistance. Your Tivoli
System action: Processing stops. Storage Manager administrator can help you configure
User response: Try the operation again. If the problem the trace.
persists, review the Tivoli Storage Manager error log
for any related messages. Obtain a service trace that FMV1241E File is in use; Write permission denied.
captures the problem and contact IBM technical
support for additional assistance. Your Tivoli Storage Explanation: The current file cannot be opened to
Manager administrator can help you configure the write to because it is currently being run by another
trace. operation.
System action: File skipped.
User response: Stop the operation that is running the
file and retry the operation, or restore or retrieve the
file to a different name or directory.

294 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1242E • FMV1252W

FMV1242E Too many symbolic links were detected FMV1247I Waiting for files from the server...
while resolving name
Explanation: Restore request has been sent to the
Explanation: While trying to resolve the file name, too server. The wait time depends on how many files you
many symbolic links were found. are restoring.
System action: File skipped. System action: Tivoli Storage Manager waits for files
to restore from the server.
User response: Ensure that you do not have a looping
symbolic link for the file. User response: None.

FMV1243E The file name is too long and can not be FMV1248E An active restore for the same source
processed by Tivoli Storage Manager file specification exists. Unable to
continue with this request.
Explanation: The size limit for file names may vary by
operating system. The most common limit is 256 Explanation: Currently, there is an active restore for
characters. The file name being processed exceeds the the same source file specification. Another restore of the
limit supported by Tivoli Storage Manager on this same source file specification cannot be started.
system.
System action: The requested restore fails.
System action: The file is skipped.
User response: Start another restore with a different
User response: Enter HELP FILE SPEC or see the source file specification.
client manual for the operating system on which you
are receiving this error. The "File specification syntax"
FMV1249W Server cannot restart the last restore
section of the manual explains file name lengths
request. Do you want to restore without
supported by Tivoli Storage Manager.
restart or abort the request?
Explanation: The restart restore token has expired.
FMV1244E File system is locked by system
The server cannot restart the restore from where it last
Explanation: File system cannot be accessed because it ended.
is locked by the system.
System action: Processing stopped; waiting for user
System action: Tivoli Storage Manager cannot intervention.
complete the operation.
User response: Retry the request without restart or
User response: See your system administrator. abort the request.

FMV1245E The file has an unknown format. FMV1251E File system/drive not ready
Explanation: Tivoli Storage Manager tried to restore or Explanation: The file system/drive was not ready for
retrieve a file, but it had an unknown format. access.
System action: The file is skipped. System action: Processing stopped.
User response: The file was either backed up by User response: Ensure that the drive is available to
another application, or the data is invalid. If the file Tivoli Storage Manager, and then retry the operation.
belongs to this system, try the operation again. If the
problem persists, contact IBM technical support for
FMV1252W The server that you are connected to
further assistance.
does not support this function.
Explanation: You attempted to run a backup-archive
FMV1246E A command-line argument exceeded the
client operation when connected to the virtual server.
maximum length (maximum length) for a
Backup-archive client operations are not supported
single token.
when connected to the virtual server.
Explanation: Command-line arguments may not
System action: The operation fails.
exceed maximum length characters.
User response: Connect to a valid server before
System action: The command is not processed.
attempting this function.
User response: Correct the command and retry the
operation.

Chapter 6. FMV messages 295

FMV1253E • FMV1262E

FMV1253E File input/output error FMV1258E The image snapshot operation failed.
Explanation: An error was found while reading from Explanation: Tivoli Storage Manager was not able to
or writing to the file. take a snapshot of the specified volume.
System action: File or file system is skipped. System action: Processing stopped.
User response: Check your system to ensure that it is User response: Check the error log for any other
operating properly. For OS/2, run CHKDSK /F for the messages that might indicate a reason for the failure.
failing drive which can be found in dsmerror.log. Try to correct any indicated problems, then try the
operation again. If the problem persists, contact IBM
technical support for further assistance.
FMV1254E File write error
Explanation: An error was found while writing to the
FMV1259E The image snapshot operation failed.
file.
Diagnostic text: diag_text.
System action: File skipped.
Explanation: An error was encountered during image
User response: Check your system to ensure that it is backup snapshot processing. The diagnostic text can
operating properly. vary, depending on the error.
System action: The operation ends.
FMV1255E File exceeds system/user file limits
User response: Examine the client error log for
Explanation: A file being restored or retrieved exceeds additional messages that might indicate the reason for
system set limits for this user. the problem. Take any corrective action suggested by
the messages, then try the operation again. If the
System action: File skipped. problem persists, contact IBM technical support for
User response: Ensure that the system limits are set further assistance.
properly.
FMV1260E File is being recalled or has been
FMV1256E Cannot make file/directory recalled.

Explanation: The directory path for files being Explanation: The file is being recalled by another
restored or retrieved cannot be created. process or has been recalled.

System action: File skipped. System action: File skipped.

User response: Ensure that you have the proper User response: None
authorization to create the directory for file being
restored or retrieved. Make sure that you have write FMV1261W The archive description you specified is
access. the empty string. Tivoli Storage
Manager will use the default description
FMV1257E An error occurred while preparing the (Archive Date: current date).
system object for restore. Explanation: The description option on the archive
Explanation: This message is typically issued when command may not specify a null string.
the client is unable to delete the ADSM.SYS staging System action: Processing continues, and the
directory in preparation for restoring the system object. description option is ignored.
System action: The system object is not restored. User response: None. Specify at least one character in
User response: Check the error log for any other the description
messages that might indicate a reason for the failure,
correct any indicated problems, then try the operation FMV1262E The password is not updated. Either an
again. If the problem occurs again, manually delete the invalid current password was supplied
ADSM.SYS directory, then try the operation again. If or the new password does not fulfill the
the problem cannot be resolved, contact IBM technical server password requirements.
support for further assistance.
Explanation: The password is not updated because of
one of the following reasons:
v You entered an incorrect current password or
v You entered a new password that does not fulfill the
password length requirements. The length
requirements are set on the server.

296 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1263E • FMV1271E

System action: The password is not updated on the

FMV1267E The management class for file file-name
server.
does not allow migration. This file will
User response: Enter another password. not be migrated.
Explanation: The management class for this file does
FMV1263E The active policy set does not contain not allow migration
any backup copy groups. The backup
System action: File is skipped.
operation can not continue.
User response: Either have the Tivoli Storage Manager
Explanation: In order to back up files, the policy set
administrator change the Space Management Technique
must contain at last one backup copy group.
within the management class to a value other than
System action: Tivoli Storage Manager did not backup NONE or change the include/exclude list to specify a
the file. management class with the appropriate Space
Management Technique value.
User response: The Tivoli Storage Manager
administrator needs to update or define at least one
management class in your policy set that contains a FMV1268E This file has been migrated.
backup copy group, or else assign you to a different
Explanation: The error can result from migrating a file
policy domain that contains at least one backup copy
with hard links. After a file with hard links is migrated,
group. Contact your Tivoli Storage Manager
attempts to migrate the alias files yield an error.
administrator for further assistance.
System action: The file is skipped.
FMV1264E The active policy set does not contain User response: If this error is not a result of a hard
any archive copy group. The archive linked file migration, then this error might be due to
operation cannot continue. the previous cancelled migration or recall operation. In
this case, restart the dsmrecalld daemon and try the
Explanation: In order to archive files, the policy set
operation again.
must contain at least one archive copy group.
System action: Tivoli Storage Manager did not archive
FMV1269I File is implicitly excluded.
the file.
Explanation: You tried to back up or migrate a file
User response: The Tivoli Storage Manager
that is implicitly excluded.
administrator needs to update or define at least one
management class in your policy set that contains an System action: Tivoli Storage Manager will not back
archive copy group, or else assign you to a different up or migrate an implicitly excluded file.
policy domain that contains at least one archive copy
User response: None.
group. Contact your Tivoli Storage Manager
administrator for further assistance.
FMV1270I Forcing compression off to enable future
server-free restore.
FMV1265E Encountered bad mount or filesystem,
processing stopped. Explanation: Because ENABLESERVERFREE had been
specified, and an attempted server-free data movement
Explanation: The getmnt system call returned an error
fell back to non-server-free, the Tivoli Storage Manager
indication. Error was encountered trying to determine
client is forcing compression off. This is to enable
what the mounted file systems are.
future server-free restore of the object backed up, when
System action: Processing stopped. Cannot recover. the problems preventing a server-free backup from
occurring have been resolved.
User response: There is a bad file system or mount
point on your system. Look at file systems and mounts, System action: The operation continues without
and correct any errors. If unsuccessful, see your system compression.
administrator for more information.
User response: Either Remove the
ENABLESERVERFREE option from the system option
FMV1266E Encountered bad mount or filesystem, file, or set COMPRESSION off in the option file.
processing stopped.
Explanation: An error was encountered trying to FMV1271E The compressed file is corrupted and
determine what the mounted file systems are. cannot be expanded correctly.
System action: Processing stopped. Cannot recover. Explanation: The compressed file cannot be expanded
correctly due to one of the following reasons:
User response: Please, see your system administrator
for more information. v There is a problem on the tape.

Chapter 6. FMV messages 297

FMV1272W • FMV1278W

v There is a communications problem. User response: Because this error is caused by

v The compressed file was corrupted on the TSM insufficient memory, shut down running applications
Server. and retry. If the problem persists, see your system
administrator.
System action: File skipped.
User response: 1) The compressed file is corrupted FMV1275E Error Loading Function(s) from
because there is a problem on the tape. To know if this WINSOCK.DLL
is the problem, please issue the following command on
the TSM Server: audit volume <volume_name> fix=no Explanation: Error loading one or more functions
If there is any problem reported, you could move the from the Windows socket support file.
data from that volume to a new one (see command System action: Connection to server fails.
MOVE DATA) and try again the restore. 2) There are
communications problems between the TSM Server and User response: Since this might possibly be caused by
the TSM Client and the results is that the file is insufficient memory, shut down running applications
corrupted during the transmission. If you use a gigabit and retry. If the problem persists, see your system
Ethernet adapter on the Server please upgrade the card administrator.
driver (AIX platform) or add provided by SUN
suggested changes to some system network options FMV1276I \"Log on as a service\" right granted to
which have resolved this problem (SUN platform). 3) account
Please verify with your network support if during the
restore there are no any problems between the TSM Explanation: You specified a Windows user account
Client/Server that is originating the file corruption. which did not have the security right to run as a
service

FMV1272W Adaptive subfile backup has been System action: Tivoli Storage Manager granted the
configured on the client but the server "log on as a service" right to the account you specified.
doesn't allow this type of backup.
User response: No action required.
Adaptive subfile backup will not be
used for this operation.
FMV1277E Error occurred while granting \"log on
Explanation: Adaptive subfile backup forced off by
as a service\" right to account
the server.
Explanation: You specified a Windows user account
System action: Processing continues.
which did not have the security right to run as a
User response: Set up the server to allow clients to service. Tivoli Storage Manager encountered a problem
back up subfiles. attempting to grant this right automatically.
System action: The "log on as a service" right is not
FMV1273E The image plug-in was not able to granted to the account specified.
acquire an exclusive lock on volume:
User response: Insure the account from which you are
volume_name
configuring the service has authority to grant rights
Explanation: To perform an offline image backup or and retry the request. Alternatively run the Windows
an image restore, IBM Tivoli Storage Manager requires policy editor from an administrative account to grant
exclusive use of the volume. the "log on as a service" right to the account that is
associated with the service you are configuring.
System action: Processing stopped.
User response: Verify that no other application is FMV1278W Virtual mount point 'filespace-name' is a
accessing the volume. If this volume is being accessed file system. It will be backed up as a
by applications that can not be shut down during file system.
backup then perform an online image backup (snapshot
with LVSA) instead. During restore of an image, IBM Explanation: A virtual mount point that is a file
Tivoli Storage Manager must have exclusive use of the system is invalid and should be deleted.
volume.
System action: The virtual mount point is ignored.
User response: Delete the virtual mount point.
FMV1274E Error Loading WINSOCK.DLL
Explanation: Error loading the Windows socket
support file into memory. This error only applies when
using TCP/IP communications.
System action: Connection to server fails.

298 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1279W • FMV1303E

corrupt by using system tools like chkdsk (Windows)

FMV1279W Virtual mount point 'filespace-name'
or fsck (UNIX).
cannot be used in a file system handled
by automounter and is ignored.
FMV1300E File 'file_name' cannot be reconstructed
Explanation: Virtual mount points cannot be used in a
because a necessary component was not
file system handled by automounter. If virtual mount
restored.
points reside in a file system that is processed from an
automounter, the backed up files underneath the Explanation: The subfile backup technique was used
virtual mount points will be expired when the file to back up this file. During the restore, a portion of the
system is unmounted. file was not be obtained from the server.
System action: The virtual mount point is ignored. System action: The file indicated in the message is not
restored. Restore for all other files continues.
User response: Delete the virtual mount point.
User response: Try to restore the file again by
selecting the file for restore from the user interface. You
FMV1286E -nasnodename option required for this
can also check the client error log and the server
operation.
activity log for any messages related to the file
Explanation: User issued a NAS related command and indicated in the message.
NASNodename option is missing.
System action: Operation aborted. FMV1301E This operation cannot continue due to
an error on the Tivoli Storage Manager
User response: Use -nasnodename option with the
server. See your Tivoli Storage Manager
command or place nasnodename option in the option
server administrator for assistance.
file.
Explanation: The Tivoli Storage Manager server
encountered an error condition that prevents the Tivoli
FMV1287E Volume could not be locked.
Storage Manager client operation from continuing. Your
Explanation: The system call to lock the volume Tivoli Storage Manager server administrator can review
failed. the Tivoli Storage Manager server activity log for more
details about the error.
System action: Processing stopped.
System action: Processing stopped.
User response: Please verify that no other application
is accessing the volume. If this volume is being User response: Contact your Tivoli Storage Manager
accessed by applications that can not be shutdown server administrator for assistance. The administrator
during backup then perform an online image backup can review the Tivoli Storage Manager server activity
(snapshot) instead. During restore of an image Tivoli log for further information about the conditions that
Storage Manager must have exclusive use of the lead to this error.
volume.
FMV1302E No objects on server match query
FMV1288E The (-TYPE) option is required with the
Explanation: No objects on the server match the query
SET EVENT command.
operation being performed. If this object is part of a
Explanation: There is no default value for the -TYPE backupset generated on a node, and the node name is
option. It must be explicitly entered with the command. changed on the server, any backup set objects that were
generated prior to the name change will not match the
System action: The current command ends. new node name.
User response: Enter the SET EVENT command again System action: Processing stopped.
with the TYPE option and a value of HOLD, RELEASE,
or ACTIVATERETENTION. User response: Ensure the names are properly
entered. If the object is part of a backupset generated
prior to a node name change, ensure that the node
FMV1289W Bad areas on 'volume' between sectors name is the same as the node for which the backup set
hi:lo and hi:lo was generated.
Explanation: Some bad sectors within the specified
range were detected on the volume during image FMV1303E Client ended transaction
operation.
Explanation: The client system ended the operation
System action: Processing continues. with the server and ended the current transaction.
User response: Make sure the volume data is not System action: Processing stopped.

Chapter 6. FMV messages 299

FMV1304W • FMV1311E

User response: Restart the session. User response: Retry the session with the correct
password. If this fails or you have forgotten your
password, ask the Tivoli Storage Manager administrator
FMV1304W An active backup version could not be
to assign a new password.
found.
Explanation: An attempt was made to expire an
FMV1307E Node in use
object, but the Tivoli Storage Manager server was
unable to find an active backup version of the object. Explanation: The node you are running on is in use
This message is preceded by message FMV1228E which by another operation on the server. This might be from
specifies the object name. For instance, this message another client or from some activity on the server.
could be issued if two separate client processes are
System action: Processing stopped.
backing up the same file system at the same time. If
one of the processes expires a file, then the Tivoli User response: Retry the operation, or see your
Storage Manager server will make that file inactive. If system administrator to see what other operations are
the second process subsequently attempts to expire that running for your node.
same file, the Tivoli Storage Manager server will not
find an active version of the file, so the second process
will issue this message for that file. FMV1308E Expiration date must be greater than
today's date
System action: The object is not expired. Processing
continues with the next object. Explanation: Archive expiration date is too low, the
date must be greater than today’s date.
User response:
System action: Tivoli Storage Manager canceled the
v Review the console output, schedule log, or error log current operation.
and locate the FMV1228E message that immediately
precedes this message. FMV1228E will identify the User response: Retry archiving the file with an
object that could not be expired. expiration date that is higher than today’s date.
v Examine the conditions under which the problem
occurred and assess whether those conditions explain FMV1309I The requested data is offline.
the occurrence of this message. For example, this
message could appear if multiple instances of the Explanation: For the restore or retrieve operation, one
client were attempting to back up the file system or more of the requested files must be recalled from
concurrently. offline storage media (generally tape). The wait time
depends on your site’s offline storage management
v Search for this message number at the Tivoli Storage
policies.
Manager Support web site (http://www.ibm.com/
software/sysmgmt/products/support/ System action: Tivoli Storage Manager waits for
IBMTivoliStorageManager.html). offline storage media to become available and then
continues.
FMV1305E The Tivoli Storage Manager server has User response: None.
no data for the object.
Explanation: Tivoli Storage Manager tried to do a FMV1310E Object too large for server limits
restore or retrieve on an object that has no data
Explanation: The object is too large. The configuration
associated with it. If a corrective action is possible, it is
of the server does not have any data storage space that
with the Tivoli Storage Manager server.
accepts the object.
System action: Tivoli Storage Manager ends the
System action: File skipped.
current operation.
User response: See your system administrator to
User response: Ask the Tivoli Storage Manager
determine the maximum file (object) size for which
administrator to check the Tivoli Storage Manager
your site’s server is configured.
activity log for any messages related to this error that
might help identify the problem.
FMV1311E Server out of data storage space
FMV1306E You entered an incorrect password. Explanation: The server does not have any space
available to store the object.
Explanation: You entered an incorrect current
password or you entered a new password that does not System action: Tivoli Storage Manager ended the
fulfill the password length requirements set on the current operation.
server.
User response: You can take any of the following
System action: Processing stops. actions:

300 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1312E • FMV1319E

v Request the system administrator to add space to the marked unavailable if prior read errors were
storage pool. encountered or the volume is checked out of the tape
v For Tivoli Storage Manager client, set library.
COMPRESSALWAYS=NO and COMPRESSIon=YES
in the options file (DSM.OPT), then the file will be FMV1315W Unexpected retry request. The server
resent uncompressed if it grows during compression. found an error while writing the data.
v For API Applications, consult the application's
Explanation: None.
documentation for recommendations regarding
compression. System action: The client retries the operation.
v Turn off disk caching in the disk storage pool, and User response: None.
issue MOVE DATA commands to each disk pool
volume to clear out the cached bitfiles.
FMV1316E The server does not have enough
recovery log space to continue the
FMV1312E Server media mount not possible current operation
Explanation: Server media mount not possible. The Explanation: The server ran out of recovery log space.
server timed out waiting for a mount of an offline
volume. System action: Tivoli Storage Manager ended the
current operation.
System action: File skipped.
User response: This error is a temporary problem.
User response: Retry later when server volumes can Retry later or see your system administrator.
be mounted. Ensure that the MAXNUMMP (maximum
number of mount points) defined on the server for this
node is greater than 0. FMV1317E The server does not have enough
database space to continue the current
operation
FMV1313E Size estimate exceeded
Explanation: The server ran out of database space.
Explanation: The total amount of data for a backup or
archive operation exceeds the estimated size originally System action: Tivoli Storage Manager ended the
sent to the server for allocating data storage space. This current operation.
happens when many files are growing by large
User response: See your system administrator.
amounts while the backup or archive operation is in
session.
FMV1318E The server does not have enough
System action: Processing stopped.
memory to continue the current
User response: Retry the operation. If the problem operation.
continues, check what other processes are running on
Explanation: The server ran out of memory.
the client machine that are generating large amounts of
data. Disable those operations while the backup or System action: Tivoli Storage Manager ended the
archive operation is taking place. current operation.
User response: This is a temporary problem. Retry
FMV1314E File data currently unavailable on server later or see your system administrator.
Explanation: The file data is currently unavailable on
the server. A retrieve or restore operation was FMV1319E An error occurred on the IBM Tivoli
attempted. Possible causes are: Storage Manager server while trying to
v Data was corrupted at the server rename file space file_space_name
v Server found a read error Explanation: None.
v File is temporarily involved in a reclaim operation at System action: Because the file space cannot be
the server renamed, the operation stops.
v Server requested a tape volume that was marked
User response: Check the client error log and the IBM
unavailable.
Tivoli Storage Manager server activity log for any other
System action: Processing stopped. messages that might help identify the problem. If the
problem cannot be resolved, contact IBM technical
User response: Retry the operation. If the problem
support for additional assistance.
continues, see your system administrator to determine
the problem from the server console or the activity log.
Check whether any requests were made for a tape
volume that was unavailable. A tape volume may be

Chapter 6. FMV messages 301

FMV1320E • FMV1329S

System action: Tivoli Storage Manager ends the

FMV1320E The specified file space does not exist
current operation.
on the server. The file space might have
been deleted by another client or an User response: Try the operation at a later time. If this
administrator. fails, contact the Tivoli Storage Manager administrator
and request more storage pool space.
Explanation: The specified file space does not exist on
the server. Your system administrator deleted the file
space or another client using your client’s node name FMV1327W The snapshot operation for 'volname'
deleted it. failed with error code: retcode.
System action: Tivoli Storage Manager canceled the Explanation: A snapshot could not be taken of the
current operation. specified volume.
User response: Check the file space name to see if it is System action: Snapshot processing stopped.
correct, and retry the operation.
User response: Check the client error log for any other
messages that might help identify the problem. If the
FMV1321S Open Registration failed because the problem cannot be resolved, contact IBM technical
specified node name is defined in the support for additional assistance.
server
Explanation: Open registration failed because a node FMV1328W An error occurred generating delta file
is defined in the server with the same name. for 'file-name'. The return code is retcode.
System action: Tivoli Storage Manager canceled the Explanation: An error occurred that prevented the
current operation. creation of the delta file. Possible reasons for this error
include:
User response: Retry with another node name.
v The base file cannot be opened for reading
v The file being backed up cannot be opened for
FMV1322S Open Registration failed because no
reading
default domain exists
v The delta file cannot be opened for writing
Explanation: Open registration failed because a
v The file being backed up has grown to a size larger
default policy domain does not exist for you to place
than 2 GB
your node.
v A memory file mapping of the file cannot be created
System action: Tivoli Storage Manager canceled the
current operation. System action: A full backup of the file is made, and a
new version of the reference file is stored in the subfile
User response: See your system administrator. cache.
User response: If the message indicates return code
FMV1323S Open Registration failed because an 4504, check the delta subfile cache directory for any
invalid node name was specified residual delta files. The delta subfile cache directory is
Explanation: Open registration failed because the specified by the client option SUBFILECACHEPATH.
specified node name contains invalid characters. Search the directory for files named \".dXXXXXXXX\"
where \"XXXXXXXX"\ is an eight-digit number. If
System action: Tivoli Storage Manager canceled the there are no backup operations in progress, there
current operation. should not be any files in the SUBFILECACHEPATH
User response: Retry with another node name that with this name. If there are no backup operations in
does not have any invalid characters. progress and these files exist, they can safely be
removed. If you continue to receive this message but
there are no residual delta files in the subfile cache
FMV1326S The Tivoli Storage Manager server does directory and the file has not grown to a size larger
not currently have space in the storage than 2 GB, then contact IBM technical support for
pool for this file. This may be a further assistance.
temporary condition.
Explanation: This message is typically issued when FMV1329S Server out of data storage space
the storage pool in which the data is being placed does
not have sufficient space to store the data, but the Explanation: The server does not have space available
space will be available soon. For example, a storage to store the object.
pool migration might free up sufficient space to store System action: Tivoli Storage Manager ended the
the data. current operation.
User response: Report to your system administrator

302 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1330S • FMV1337I

that a storage pool on the server is full. User response: None.

FMV1330S This node currently has a pending FMV1334W Volume mount point 'filespace
restartable restore session. The namepath-namedir-name' was not restored
requested operation cannot complete because the target directory is not
until this session either completes or is empty.
canceled.
Explanation: Volume mount points can only be
Explanation: This operation can not be completed restored if the target directory does not already exist, or
because a restartable restore session is pending. The if the target directory exists but is empty. If the target
operation is not allowed because the restartable session directory exists and is not empty, or already is a
and the current operation affect the same file space. junction point, then the volume mount point cannot be
restored. On Windows Vista, it is normal to see these
System action: Tivoli Storage Manager ended the
warnings during system drive restore as there are
current operation.
many junction points that point to the
User response: Issue a query restore to see the '%systemroot%\Users' folder.
conflict. Issue the cancel restore command to delete any
System action: The volume mount point is not
unneeded restartable restore sessions.
restored. Processing continues with the next object.
User response: Correct the conflict with the
FMV1331E Only a Tivoli Storage Manager
non-empty directory, then try the operation again. This
authorized user can perform this Action.
is especially important when this message is issued for
Explanation: User must be a Tivoli Storage Manager a volume mount point that resides in the SYSVOL,
authorized user to perform this action. User is not since an incomplete SYSVOL restore can result in
password authorized and this action requires system stability problems. See the reference information
authorization. for the RESTORE command in the client manual for
additional information about restoring volume mount
System action: Processing stopped. points.
User response: User must be root user, or user must
be the owner of the executable and the set effective FMV1335E The RSM database files could not be
user id bit is set to 'on' ('s' bit). restored.
Explanation: None.
FMV1332E Run the '... for Administrators' version
of the application. System action: The RSM database is not restored.
Otherwise, processing continues.
Explanation: The user must be root or a system
administrator and use the provided authorization tools User response: Check the client error log for any other
to start IBM Tivoli Storage Manager messages that might help identify the problem. Reboot
the system, then try the RSM restore operation again. If
System action: IBM Tivoli Storage Manager the problem cannot be resolved, contact IBM technical
terminates. support for further assistance.
User response: The user must login as the root user or
be a system administrator and use one of the following FMV1336I RSM service must be restarted for
authorization tools to start IBM Tivoli Storage Manager: changes to become effective.
v "Tivoli Storage Manager Backup for Administrators"
Explanation: RSM database files have been restored
v "Tivoli Storage Manager Scheduler for from the server and imported. The RSM service must
Administrators" be restarted for the updates to become effective.
v "Tivoli Storage Manager Scheduler Daemon for
Administrators" System action: Processing continues.
User response: None.
FMV1333I The used-block list used for the
snapshot image backup of volume_name FMV1337I Restarting the RSM service...
is different than list acquired before the
start of snapshot. Explanation: RSM database files have been restored
from the server and imported. Tivoli Storage Manager
Explanation: The snapshot image backup used-block is about to stop then restart the RSM service.
list is taken before and after the start of the snapshot
for informational purposes. System action: Processing continues.

System action: Processing continues. User response: None.

Chapter 6. FMV messages 303

FMV1338I • FMV1346E

FMV1338I Restart of the RSM service is completed. FMV1343E The option 'specified-option' can only be
entered when 'other-option' has been
Explanation: RSM database files have been restored
entered.
from the server and imported. Tivoli Storage Manager
has restarted the RSM service on the user's behalf. Explanation: The command failed because the
specified option (specified-option) option was entered,
System action: Processing continues.
but the other option (other-option) was not.
User response: None.
System action: The command is terminated.
User response: Run the command without the
FMV1339E Restart of the RSM service failed.
specified option. Alternatively, run the command with
Restart the RSM service manually.
the other option added.
Explanation: RSM database files have been restored
from the Tivoli Storage Manager server and imported.
FMV1344E Job is running in the background.
Tivoli Storage Manager has tried to restart the RSM
Cannot prompt for the Key.
service on the user's behalf but has run into a problem.
Explanation: When jobs are run in the background,
System action: Processing stopped.
the client cannot prompt for the key.
User response: Restart the RSM service manually.
System action: Processing stopped.
User response: Run the Job in the foreground.
FMV1340E An error occurred while backing up the
RSM database.
FMV1345E No objects on server match
Explanation: An error occurred while backing up the
'object-nameobject-nameobject-name'
RSM database files. The database will not be backed
up. Explanation: The specified file (object-name) does not
have a match on the server.
System action: Processing stopped.
System action: File skipped.
User response: Check the client error log for any other
messages that might help identify the problem. Try the User response: Backup the file and retry the
operation again. If the problem persists, contact IBM operation. If the problem continues, see your system
technical support for further assistance. administrator to isolate the problem through use of the
server console.
FMV1341E An invalid character appears in the
operand: operand. FMV1346E The image snapshot operation failed.
The SNAPSHOTCACHELocation does
Explanation: The operand contains a character that is
not contain enough space for this
not valid in the current locale and code page. It cannot
snapshot image backup.
be translated to its internal wide-character format.
Explanation: Tivoli Storage Manager was not able to
System action: Processing stops.
take a snapshot of the specified volume. The
User response: Change the locale of the workstation SNAPSHOTCACHELocation points to a location which
to match the language in which the operand is does not contain the space necessary to manage the
recorded, and try the command again. snapshot. This could be due to an unexpected amount
of disk activity which is generating more changes than
can be contained in the available space at this
FMV1342E Client cache is locked; unable to particular point in time, or the
continue with operation. SNAPSHOTCACHELocation needs to be changed
Explanation: The client cache is currently locked by because the specified location is not large enough to
another process. handle the usual amount of changes to the volume.
Another reason for this failure can be that the specified
System action: Processing stopped. SNAPSHOTCACHESize is not set to a large enough
User response: Report the program error to your value to handle the usual amount of changes to the
service representative. volume during snapshot image backup.
System action: Processing stopped.
User response: If the problem persists please increase
the SNAPSHOTCACHESize and/or change the value
of the SNAPSHOTCACHELocation.

304 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1347E • FMV1353E

FMV1347E The image snapshot operation failed. FMV1350E The logical volume snapshot agent
The percent of space to use, specified (LVSA) is currently busy performing a
via the SNAPSHOTCACHESize, has snapshot on this same volume.
been exceeded.
Explanation: Another IBM Tivoli Storage Manager
Explanation: Tivoli Storage Manager was not able to process is already performing a snapshot of this
take a snapshot of the specified volume. The percent of volume.
space allotted via the SNAPSHOTCACHESize option
System action: The operation is stopped.
was not enough to perform this snapshot image
backup. This could be due to an unexpected amount of User response: Please wait until the other IBM Tivoli
disk activity which is generating more changes than Storage Manager process finishes with the volume and
can be contained in the allotted space at this particular then retry the operation.
point in time. Another reason for this failure can be
that the specified SNAPSHOTCACHESize is not set to
a large enough value to handle the usual amount of FMV1351E Session rejected: All server sessions are
changes to the volume during snapshot image backup. currently in use

System action: Processing stopped. Explanation: Tivoli Storage Manager has all available
sessions in use and cannot accept a new one at this
User response: If the problem persists please increase time.
the SNAPSHOTCACHESize or, for Windows, change
the value of the SNAPSHOTCACHELocation. System action: Tivoli Storage Manager canceled the
current operation.

FMV1348E Unable to satisfy the User response: Retry the operation. If the problem
SNAPSHOTFSIDLEWait and continues, see your system administrator to increase the
SNAPSHOTFSIDLERetries options due number of concurrently active sessions to the server.
to volume write activity.
Explanation: Tivoli Storage Manager was not able to FMV1352E The session is rejected. Your password
take a snapshot of the specified volume. The Logical has expired.
Volume Snapshot Agent was not able to satisfy the Explanation: The password for Tivoli Storage Manager
SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries user ID has expired. It can be either Tivoli Storage
options before starting the snapshot of the specified Manager node name password or administrative user
volume. ID password or both.
System action: Processing stopped. System action: Tivoli Storage Manager canceled the
User response: If the problem persists please modify current operation. You are not allowed to connect to the
the SNAPSHOTFSIDLEWait and server until the password is updated.
SNAPSHOTFSIDLERetries options to better fit the User response: Update your password. It may require
normal disk write activity of the volume being backed updating the node name password or the corespondent
up. administrative ID password or both. You may use the
SET PASSWORD command, or have the Tivoli Storage
FMV1349E An error occurred during Logical Manager administrator update your node and/or your
Volume Snapshot Agent snapshot administrative ID.
processing.
Explanation: An unrecoverable error occurred during FMV1353E Session rejected: Unknown or incorrect
snapshot processing. This can be caused by a variety of user ID entered
errors, so the error and system event logs should be Explanation: The user ID, which is either Tivoli
checked for additional messages. Storage Manager node name or administrative user ID,
System action: Processing stopped. is not known by the server. Possible reasons for this
include:
User response: Check the client error log and the v Your node name is not registered with the Tivoli
system event log for any other messages that might Storage Manager server
help identify the problem. Try the operation again. If
the problem persists, contact IBM technical support for v The node name is correct but does not have a
further assistance. corresponding administrative ID with the same name
and client owner authority
v you are attempting to access a file that was migrated
to a different node.

Chapter 6. FMV messages 305

FMV1354E • FMV1362S

System action: Tivoli Storage Manager cancelled the User response: See your system administrator to see
current operation. what version of Tivoli Storage Manager to run for your
location.
User response: Verify that the server is using closed
registration and that your node name is registered with
the server. Ensure that you entered your Tivoli Storage FMV1358S Session rejected: Downlevel server code
Manager user ID correctly. Check that your Tivoli version
Storage Manager node name has a matching admin ID
Explanation: The server version and your client
with client owner authority for the node. If it does not,
version do not match. The server code is downlevel.
your Tivoli Storage Manager administrator needs to
create it. If attempting to access a migrated file, your System action: Tivoli Storage Manager canceled the
node name must be the same node which migrated the current operation.
file.
User response: See your system administrator to see
what version of Tivoli Storage Manager to run for your
FMV1354E Session rejected: Duplicate ID entered location.
Explanation: Another process using this node name is
active with the server. FMV1359E Session Rejected: The specified node
name is currently in use
System action: Tivoli Storage Manager cannot connect
to the server. Tivoli Storage Manager canceled the Explanation: The node name you specified is in use
current operation. on the server.
User response: If you are running a UNIX-based System action: Session was not started.
system, ensure that another process is not active with
Tivoli Storage Manager under the same name. Also, User response: The server is probably performing a
ensure that your node name is unique to the server so task that prevents your node from establishing a
that it cannot be used by another person. See your session. Retry later or check with your system
system administrator to identify the owner of that node administrator.
name.
FMV1360I Compressed Data Grew
FMV1355E Session rejected: Server disabled. Explanation: The size of the file after compression is
Explanation: The server is in a disabled state and greater than the size of the file before compressed.
cannot be accessed for normal activity. System action: Even though the size of the file
System action: Tivoli Storage Manager canceled the increased, the file is compressed.
current operation. User response: None.
User response: Retry the operation after the server
returns to an enabled state. If the problem continues, FMV1361E Session Rejected: The specified node
see your system administrator. name is currently locked.
Explanation: The node name you specified is currently
FMV1356E The server is not configured to allow locked on the server.
open registration
System action: Session was not started.
Explanation: No authorization. Registration is
required by your system administrator. The server is User response: Check with your system administrator
not configured to allow open registration. to find out why your node name is locked.

System action: Session not started.

FMV1362S SLM LICENSE EXCEEDED: The client
User response: You must obtain a Tivoli Storage licenses for Tivoli Storage Manager are
Manager node and password from your system exceeded. See your system
administrator. administrator.
Explanation: Adding a new enrollment will exceed the
FMV1357S Session rejected: Downlevel client code product license count for Tivoli Storage Manager.
version
System action: Execution of the client enrollment or
Explanation: The server version and your client connection request ends.
version do not match. The client code is downlevel.
User response: See your system administrator.
System action: Tivoli Storage Manager canceled the
current operation.

306 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1363E • FMV1372E

FMV1363E Session Rejected: The server does not FMV1368S Session Rejected: The server is not
have enough memory to allow a licensed for this platform type. See your
connection to be established. system administrator.
Explanation: The server does not have enough Explanation: The server is not licensed for the
memory to allow your client to establish a connection requesting client type.
with the server.
System action: Execution of the client enrollment or
System action: Session was not started. connection request ends.
User response: Retry later or see your system User response: See your system administrator.
administrator.
FMV1369E Session Rejected: The session was
FMV1364E Session Rejected: The server does not canceled by the server administrator.
have enough recovery log space to allow
Explanation: The server administrator canceled the
a connection to be established.
current client session.
Explanation: The server ran out of recovery log space.
System action: Execution of the client connection
System action: Session was not started. request ends.
User response: This error is a temporary problem. User response: See your system administrator.
Retry later or see your system administrator.
FMV1370E The user ID entered does not have the
FMV1365E Session Rejected: The server does not correct level of authority to access the
have enough database space to allow a client machine.
connection to be established.
Explanation: The user ID entered cannot access this
Explanation: The server ran out of database space. Tivoli Storage Manager client.
System action: Session was not started. System action: The Tivoli Storage Manager operation
ends.
User response: See your system administrator.
User response: Grant authority to this user ID on the
Tivoli Storage Manager server so that it can access this
FMV1366E The session is rejected. The Tivoli
Tivoli Storage Manager client.
Storage Manager server has an internal
error.
FMV1371E File '' cannot be reconstructed from
Explanation: The client cannot establish a connection
subfile components.
to the Tivoli Storage Manager server because of an
internal server error. Explanation: An error occurred while reconstructing
this file from its subfile components.
System action: The session was not started.
System action: The file indicated in the message is not
User response: Notify your Tivoli Storage Manager
restored. Restore for all other files continues.
administrator of this error.
User response: Try to restore the file again by
selecting the file for restore from the user interface. You
FMV1367E The client is unable to sign on to the
can also check the client error log and the server
Tivoli Storage Manager server because
activity log for any messages related to the file
the server does not allow sign-on of
indicated in the message.
Unicode clients.
Explanation: The client is not allowed to connect to
FMV1372E An inconsistency was detected between
the Tivoli Storage Manager server.
the client node and the node that is
System action: The session does not start. registered to the Tivoli Storage Manager
server.
User response: Contact your Tivoli Storage Manager
administrator for assistance in configuring a working Explanation: The user has probably coded the node
Tivoli Storage Manager client for your environment. option incorrectly. For instance, the node that is
registered to the Tivoli Storage Manager server might
be a type of NAS, but the node is actually a non-NAS
client.
System action: The Tivoli Storage Manager operation
ends.

Chapter 6. FMV messages 307

FMV1373W • FMV1379E

User response: Ensure that the node name is correct are a transmission error, data corruption, or a hash
in the client options file. Make sure to use a node of collision.
type NAS only with the nasnodename option.
System action: Processing stops
User response: Try the restore operation again. If the
FMV1373W The PRESNAPSHOTCMD command for
problem persists, contact IBM technical support for
volume filespace completed with a
additional assistance.
non-zero return code.
Explanation: The command specified by the
FMV1377W The client was unable to obtain a
PRESNAPSHOTCMD option must complete
snapshot of 'volname'. The operation will
successfully in order to perform the snapshot
continue without snapshot support.
backup/archive operation. If the command completed
with a return code of 0 (zero), it has completed Explanation: Tivoli Storage Manager client was unable
successfully. If the command completed with any other to create a snapshot of the volume due to some reason.
return code, it has failed. If the command failed, then Instead of failing the operation, Tivoli Storage Manager
the backup is still performed, but without the benefit of client will perform a non-snapshot based backup.
the snapshot technology.
System action: Snapshot processing stops.
System action: The client executes the backup/archive
operation, but without using a snapshot. User response: Check the client error log for any other
messages that might help identify the problem. Try the
User response: Identify and fix the problem that operation again. If the problem persists, contact IBM
caused the command to fail. If a non-zero return code technical support for further assistance.
is normal for this command, then consider wrapping
the command in a script that always exits with a return
code of zero. FMV1378E The snapshot operation failed. The
SNAPSHOTCACHELocation does not
contain enough space for this snapshot
FMV1374W The POSTSNAPSHOTCMD command operation.
for volume filespace completed with a
non-zero return code. Explanation: IBM Tivoli Storage Manager was not able
to take a snapshot of the specified volume. The
Explanation: The command specified by the SNAPSHOTCACHELocation points to a location which
POSTSNAPSHOTCMD option completed with a does not contain the space necessary to manage the
non-zero return code. The snapshot-based backup snapshot. Reasons for failure include:
operation yields a return code of at least 8. v An unexpected amount of disk activity which is
System action: The snapshot-based backup operation generating more changes than can be contained in
continues. the available space at this particular point in time.
v The SNAPSHOTCACHELocation is not large enough
User response: Identify and resolve the problem that
to handle the usual amount of changes to the
caused the post-snapshot command to fail. If a
volume.
non-zero return code is normal for this command, then
consider wrapping the post-snapshot command in a v The specified SNAPSHOTCACHESize is not set to a
script that always exits with a return code of zero. large enough value to handle the usual amount of
changes to the volume during snapshot backup or
archive operation.
FMV1375W File FilesystemPathFileName skipped by
user System action: Processing stopped.

Explanation: You requested that this file be skipped User response: If the problem persists, increase the
during the current operation. SNAPSHOTCACHESize or change the value of the
SNAPSHOTCACHELocation.
System action: The file is skipped during the current
operation
FMV1379E The snapshot operation failed. The
User response: None. percent of space to use for the
SNAPSHOTCACHELocation, specified
FMV1376E Error processing 'filespace via the SNAPSHOTCACHESize, has
namepath-namefile-name'; end-to-end been exceeded.
digest validation failed. Explanation: IBM Tivoli Storage Manager was not able
Explanation: Cryptographic digest of the restored or to take a snapshot of the specified volume. The percent
retrieved data did not match the digest generated of space allotted via the SNAPSHOTCACHESize option
during the backup or archive operation. Possible causes was not enough to perform this snapshot
backup/archive operation. Reasons for failure include:

308 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1380W • FMV1387E

v The SNAPSHOTCACHELocation is not large enough User response: Contact your systems administrator to
to handle the usual amount of changes to the enable client-initiated sessions for your node or update
volume. the SESSIONINITIATION option and run the client
v The specified SNAPSHOTCACHESize is not set to a scheduler.
large enough value to handle the usual amount of
changes to the volume during snapshot backup or FMV1383E Wrong server port.
archive operation.
Explanation: You were trying to open a
System action: Processing stopped. backup/archive client session on the server port set up
User response: If the problem persists, increase the for administrative sessions only.
SNAPSHOTCACHESize or change the value of the System action: The IBM Tivoli Storage Manager
SNAPSHOTCACHELocation. operation ends.
User response: Contact your systems administrator
FMV1380W The snapshot operation failed. The and/or use the correct values for TCP port and TCP
filesystem write activity prevented the Admin Port.
Logical Volume Snapshot Agent from
satisfying the SNAPSHOTFSIDLEWait
and SNAPSHOTFSIDLERetries options. FMV1384E An object in the transaction has been
bound to an invalid management class.
Explanation: IBM Tivoli Storage Manager was not able
to take a snapshot of the specified volume. The Logical Explanation: One of the objects in the transaction is
Volume Snapshot Agent was not able to satisfy the bound to a management class that is not part of this
SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries node's policy, or the management class type is not
options before starting the snapshot of the specified supported for this client level.
volume. System action: The current operation ends.
System action: Snapshot processing stops. User response: Make sure all objects are bound to a
User response: If the problem persists, modify the valid management class, or upgrade the client to the
SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries proper level.
options to better fit the normal disk write activity of
the volume being backed up. FMV1385E This server does not support backup
operations.
FMV1381W On volumes that are RAW or formatted Explanation: This server only supports archive
FAT32 the snapshot cache location operations, backup is not allowed.
cannot be located on the same volume
that is being backed up. System action: The current operation ends.
Explanation: When the snapshot cache location is User response: Use only archive operations with this
located on the same volume that is being backed up the server.
volume must be formatted with NTFS. The default
cache location is on the same volume where the
FMV1386E Deleting this object: "fshlll" is not
snapshot is being performed. The operation will
allowed.
continue without snapshot support.
Explanation: The object is either under a hold and
System action: The client does not execute the
cannot be deleted, or it is on a retention-protection
snapshot operation.
enabled server and has not expired.
User response: Specify a different snapshot cache
System action: The object is skipped and processing
location, using the SNAPSHOTCACHELOCATION
continues.
option.
User response: Check the status of the object through
a query to see if it is held, or when it expires.
FMV1382E Server does not allow client-initiated
connections for this node.
FMV1387E The number of objects in this
Explanation: The node is not allowed to initiate
transaction exceed TXNGROUPMAX
connections due to the configuration parameters for
values.
this node on the server. Server is able to initiate
connections to the client scheduler running in Explanation: There are too many objects in this
prompted mode. transaction.
System action: The IBM Tivoli Storage Manager System action: The current operation ends.
operation ends.

Chapter 6. FMV messages 309

FMV1388E • FMV1394E

User response: Try the operation again with fewer correctly, and PASSWORDACCESS GENERATE is set,
objects in the transaction, or increase the Tivoli Storage Manager cannot be used.
TXNGROUPMAX value on the server.
System action: Processing continues.
User response: Contact your system administrator so
FMV1388E fshlll is already under hold.
the permissions can be corrected. A System
Explanation: The specified object is already under Administrator should use the "Tivoli Storage Manager
hold, and it cannot be placed under a new hold. Backup for Administrators" application to update the
permissions.
System action: This object is skipped and processing
continues.
FMV1392W The TCA file permissions are not
User response: Issue a query to see the status of the
correct. Would you like to update the
objects, and try the operation again, without the object
permissions?
that is already held.
Explanation: The TCA is a tool used by Tivoli Storage
Manager to provide secure access to the password file
FMV1389W Invalid option (option) for the scheduled
for non-administrators. If the permissions are not set
function command
correctly, Tivoli Storage Manager cannot be used. The
Explanation: There are two possible reasons for this dsmtca application needs to be owned by root and
message: have 4755 permissions.
v The option option was specified for a scheduled System action: If you select yes, Tivoli Storage
command or subcommand (function) that cannot Manager will set the owner of the TCA to root and the
make use of that option. permissions to 4755. If you select no, the permissions
v The option appears on a scheduled command but is will not be changed. In either case, processing
valid only on the client scheduler initial command continues.
line, not on commands in a schedule from the server.
User response: Select yes when you are prompted so
System action: The option is ignored. Tivoli Storage Manager can repair the permissions of
the file. If you select no, PASSWORDACCESS
User response: See the Backup-Archive Client GENERATE will not work for non-Tivoli Storage
Installation and User's Guide for correct use of the Manager Authorized users.
named option. The system administrator should
remove the invalid option from the schedule definition
on the server. FMV1393W The command line tools are not
installed. The command line tools
include the Tivoli Storage Manager
FMV1390I A Tivoli Storage Manager authorized client acceptor daemon and the Tivoli
user must configure the Tivoli Storage Storage Manager client scheduler.
Manager client acceptor daemon and the
Tivoli Storage Manager client scheduler. Explanation: The command line tools are required for
the IBM Tivoli Storage Manager scheduler. The
Explanation: The installation of the Tivoli Storage 'dsmcad' application or the 'put in /Library/
Manager client acceptor daemon requires access to Startupitems' folder could not be located.
system locations, which require full access to the
system. The Tivoli Storage Manager client acceptor System action: The setup assistant cannot be used to
daemon is installed as a startup item in configure the IBM Tivoli Storage Manager scheduler.
/Library/StartupItems, and a link is added to /usr/bin
User response: A System Administrator must reinstall
for the dsmcad tool.
IBM Tivoli Storage Manager the command line tools.
System action: The setup assistant cannot be used to
configure the IBM Tivoli Storage Manager scheduler or
FMV1394E The node name contains periods. Would
the Tivoli Storage Manager client acceptor daemon.
you like to remove them? Select "no" if
User response: To acquire this access, system this is an existing node name.
administrators must use the "Tivoli Storage Manager
Explanation: A node name with periods complicates
Backup for Administrators" application.
the management of the node.
System action: IBM Tivoli Storage Manager prompts
FMV1391W The TCA file permissions are not
to remove the periods.
correct.
User response: Respond to the prompt. If this is a
Explanation: The TCA is a tool used by Tivoli Storage
new node, select "yes", so the node is created without
Manager to provide secure access to the password file
the periods in the name. For existing nodes, select "no",
for non-administrators. If the permissions are not set

310 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1395E • FMV1402W

so the node name is not changed. directory. Attempts to do so will result in an "access
denied" error.
FMV1395E The destination filespace or drive letter System action: Processing terminates.
is unavailable. The following object was
User response: Set the DSM_LOG (or DSMI_LOG)
not processed: Filespace:'filespace-name'
environment variable to a directory into which the
Explanation: The system is trying to restore or retrieve current user can write. You may also use the
to a destination that cannot be reached. The specified ERRORLOGNAME option to specify a file to which the
filespace name or drive letter is not valid, or does not current user has write permission.
exist, or you are specifying a local share name that
cannot be resolved.
FMV1399W The logical volume snapshot agent
System action: Objects which are part of this filespace (LVSA) is currently busy performing a
are not processed. snapshot on this same volume.
User response: Try the command again, and specify a Explanation: IBM Tivoli Storage Manager was not able
different destination for the object that was not to take a snapshot of the specified volume because
processed. another process is already performing a snapshot of
this volume. The operation continues without snapshot
support.
FMV1396E Access to the specified log or trace file
(filename) is denied. System action: Snapshot processing stops.
Explanation: Access to the specified file is denied. You User response: Wait until the other IBM Tivoli Storage
specified a log or trace file name that cannot be written Manager process finishes with the volume and then try
by the current user. the operation again.
System action: Processing stops.
FMV1400W The snapshot cache location is not valid.
User response: Ensure that you specified the correct
file or directory name, correct the permissions, or Explanation: The snapshot cache location must point
specify a new location. to a local volume that is formatted with NTFS. The
default cache location is on the same volume where the
snapshot is being performed. The operation will
FMV1397W The snapshot cannot be taken because
continue without snapshot support.
the SNAPSHOTCACHELocation does
not have enough space for this snapshot System action: Snapshot processing stops.
operation.
User response: Specify a different snapshot cache
Explanation: IBM Tivoli Storage Manager was not able location using the SNAPSHOTCACHELOCATION
to take a snapshot of the specified volume. The option.
SNAPSHOTCACHELocation points to a location which
does not contain the space necessary to create the
FMV1401W The snapshot virtual volume is not
snapshot; the disk is probably full. The operation
accessible.
continues without snapshot support.
Explanation: The logical volume snapshot agent
System action: The client does not execute the
(LVSA) cannot access the virtual volume during
snapshot operation.
OFS-enabled backup/archive operation because IBM
User response: Change the value of the Tivoli Storage Manager was probably started via
SNAPSHOTCACHELocation, or clean the disk to which terminal services. The operation continues without
the SNAPSHOTCACHELocation points. snapshot support.
System action: Snapshot processing stops.
FMV1398E Initialization functions cannot open one
User response: Do not use terminal services for the
of the Tivoli Storage Manager logs or a
snapshot. Try the operation again on the local machine.
related file: log-name. errno = errno-value,
reason
FMV1402W The snapshot is not supported on a
Explanation: The file "log-name" could not be opened
remote, removable, or SAN drive.
during initialization. The system set the error code
errno-value. If the reason given is "access denied," the Explanation: IBM Tivoli Storage Manager was not able
current user does not have permission to write to the to take a snapshot of the specified volume because
log in the directory specified. It is also possible that no open file support is only supported on local fixed
space is available at the given log location. volumes, including volume mountpoints. The operation
continues without snapshot support.
On Unix systems, the log must not be in the root

Chapter 6. FMV messages 311

FMV1403E • FMV1412E

System action: The client does not execute the

FMV1408W Previous changes have not been
snapshot operation.
commited. The machine must be
User response: To take advantage of the open file restarted before the snapshot can be
support, you may try the operation again on the local taken
machine.
Explanation: IBM Tivoli Storage Manager was not able
to take a snapshot of the specified volume because a
FMV1403E Error loading a required filename DLL previous operation required the machine to be restarted
for the changes to take effect, but the machine has not
Explanation: An error occurred while loading a been restarted. The operation will continue without
dynamic link library. The DLL load failed. snapshot support.
System action: Processing stopped. System action: The client does not execute the
User response: Verify that your system software is up snapshot operation.
to date and that all DLLs required by the Tivoli Storage User response: Restart the machine and then try the
Manager client are present. operation again.

FMV1404E Error loading one or more functions FMV1409E The remote copy process process ID on
from a required filename DLL server could not be canceled.
Explanation: An error occurred while loading a Explanation: A remote copy operation with process id
function from a dynamic link library. The DLL load process ID, which is in progress on server, could not be
failed. canceled. Check your error log to see cause of failure.
System action: Processing stopped. System action: None.
User response: Verify that your system software is up User response: Contact your Tivoli Storage Manager
to date. administrator.

FMV1405I 'service-name' service needs to be FMV1410E Unable to access the network path.
restarted.
Explanation: The network path cannot be accessed
Explanation: The service must be restarted for the due to a possible network problem.
restored changes to take effect.
System action: The client terminates.
System action: Changes are not effected.
User response: Ensure that the network is up and the
User response: Restart the service. path can be accessed using a system command, and
retry the operation.
FMV1406I Performing operation using
point-in-time copy of the filesystem: FMV1411E A communication session was dropped.
'volname'.
Explanation: A communication session was dropped
Explanation: IBM Tivoli Storage Manager is taking a due to a possible network problem.
snapshot of the specified volume during the backup or
archive operation. This allows the IBM Tivoli Storage System action: The client terminates.
Manager to access locked or in-use files.
User response: Ensure that the network is up and
System action: Operation proceeds. retry the operation.
User response: None.
FMV1412E Directory or file has bad EA data or
inconsistent data.
FMV1407I Performing operation using
point-in-time copy of the filesystem. Explanation: Directory or file has bad EA data or
inconsistent data.
Explanation: IBM Tivoli Storage Manager is taking a
snapshot of the specified volume during the backup or System action: The client terminates.
archive operation. This allows the IBM Tivoli Storage
User response: Check failing directory or file for bad
Manager to access locked or in-use files.
EA data. Copy the directory to a new location and retry
System action: Operation proceeds. the operation.
User response: None.

312 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1413W • FMV1421E

addressed. On Microsoft Windows 2008 and Microsoft

FMV1413W File 'filespace namepath-namefile-name' is
Windows 2008 R2 you can use the DiskShadow utility
not recognized by the system as a disk
sub-command LIST WRITERS DETAILED to enumerate
file and cannot be processed. The file is
the system state files. On other versions of Microsoft
skipped.
Windows you can use the vshadow utility with the
Explanation: The client is unable to process file types -wm2 option to enumerate the system state files. Verify
that are not 'disk', such as 'character' and 'pipe'. This that the file indicated in this message is not listed.
message is typically, but not always, issued for file Note: vshadow is a utility that you can obtain from
names that are normally reserved for the operating Microsoft. After confirming that the files are not
system. In the Windows environment, reserved names enumerated, contact your operating system technical
include AUX, CON, NUL, PRN, COMx or LPTx, where support for help to diagnose and resolve the issue that
'x' is any digit from 1 to 9 (for example, COM1, LPT3, prevents the file from being correctly enumerated as
etc.). part of the system state.
System action: The file is skipped.
FMV1418W A call to Tivoli Storage Manager API
User response: Either delete the file if you do not
API-name failed.
need it, or else use an EXCLUDE statement in the client
options to prevent the client from trying to process the Explanation: An unexpected error occurred while
file. In the Windows environment, normal delete performing server-free data movement.
commands will most likely not work. You will need to
System action: The requested operation will be retried
prefix the file name with the characters '\\.\'. For
with out server-free data movement.
example, "del c:\mydir\lpt4" will not work, but "del
\\.\c:\mydir\lpt4" will work. User response: Contact your Tivoli Storage Manager
administrator to correct problems with server-free data
movement.
FMV1414W Don't have sufficient authority to delete
open group on server.
FMV1419W Remote copy operation for volume
Explanation: An open image group exists on the
filespace-name failed or could not be
Tivoli Storage Manager server and cannot be deleted
restarted, return code retcode.
due to missing backup delete rights for this node.
Explanation: An error occurred on server when
System action: Processing continues.
starting or during the remote copy operation for
User response: Ask your Tivoli Storage Manager volume filespace-name.
administrator to grant backup delete rights for your
System action: The requested operation will be retried
node.
with out server-free data movement.
User response: Contact your Tivoli Storage Manager
FMV1417W Protected system state file 'filename' is
administrator to correct problems with server-free data
backed up to the drive file space, not
movement.
system state file space.
Explanation: Files protected by Microsoft Windows
FMV1420E Volume map document (tsmvolmap.txt)
File Protection (WFP) or Microsoft Windows Resource
not found.
Protection (WRP) are part of the Microsoft Volume
ShadowCopy Services (VSS) System Writer which is Explanation: An error occurred while performing VSS
part of the system state. These files are normally Automated System Recovery (ASR). Check
backed up as part of the system state, not the file dsmerror.log for more information.
system on which the files reside. A problem in the
operating system environment prevented the protected System action: Processing stops.
file named in the message text from being enumerated User response: Ask your system administrator to
as a system state file and thus backed up as part of the check the error log.
system state. The conditions that lead to this message
are not normal. In order to ensure that the file is
protected, it is backed up as part of the file system on FMV1421E The image object 'object-type' was not
which it resides. found on server.

System action: The file is backed up as part of the file Explanation: The specified image object of type
system on which it resides. object-type could not be located on the server. The
operation cannot complete without this object.
User response: It is possible to restore the system
using the file system and system state backups. System action: The operation ends.
However the conditions that prevent the system state User response: Examine the client error log for
files from being correctly enumerated should be

Chapter 6. FMV messages 313

FMV1422W • FMV1430W

additional messages that might indicate the reason for

FMV1426E An error occurred creating the Registry
the problem. Take any corrective action suggested by
backup directory structure
the messages, then try the operation again. If the
problem persists, contact IBM technical support for Explanation: The Tivoli Storage Manager client uses
further assistance. an intermediate directory structure on the client
machine as part of the Windows Registry backup
process. The client was unable to create this
FMV1422W The image data for volume filespace-name
intermediate directory structure, so the Windows
is either compressed or its compression
Registry could not be backed up. This problem can
information can not be determined.
occur if you do not have sufficient privileges to
Explanation: The image data was backed up either perform the backup operations, if the client is unable to
with compression or by an older client version. This allocate more memory from the system, or if a
data format cannot be restored on server-free path. component within the directory structure already exists
as a file.
System action: The requested operation will be retried
without server-free data movement. System action: The Windows Registry is not backed
up.
User response: None.
User response: Check the client error log for any other
messages that might have been logged when this
FMV1423W 'filesystem' is a virtual mount point. message was written, and take the corrective action (if
Migration is not supported on virtual any) suggested by those messages. Make sure that
mount points. account under which the operation runs has sufficient
Explanation: Tivoli Storage Manager HSM does not privileges. Ensure that the system has sufficient
support virtual mount points within managed file memory to run Tivoli Storage Manager. Remove the
systems. Files in the virtual mount point folder can not ADSM.SYS directory from the root of your system
be migrated. drive, then try the operation again. If the problem
persists, contact IBM support for further assistance.
System action: Tivoli Storage Manager attempts to
continue the current operation.
FMV1427I Registry Backup function completed
User response: Do not use virtual mount points successfully.
within file systems that are managed by HSM. Use
include/exclude rules instead. Explanation: Registry backup was successful.
System action: None.
FMV1424W Retrying failed image operation for User response: Continue with normal operations.
volume filespace-name.
Explanation: The transaction for image operation for FMV1428E Backup of the registry failed.
volume filespace-name failed due to reason described by
earlier message(s). Explanation: None.
System action: The requested image operation will be System action: The registry is not backed up.
retried again.
User response: Check the client error log for any other
User response: None. messages that might help identify the problem. Try the
operation again. If the problem persists, contact IBM
technical support for further assistance.
FMV1425E The image operation for volume
filespace-name cannot be retried because
of a severe error. FMV1429I Registry Restore function completed
successfully.
Explanation: None.
Explanation: Registry Restore was successful.
System action: The image operation fails for the
indicated volume. System action: None.
User response: Check the client error log for any other User response: Continue with normal operations.
messages that might help identify the problem. Try the
operation again. If the problem persists, contact IBM
FMV1430W The machine must be rebooted for the
technical support for further assistance.
changes to take effect.
Explanation: The Tivoli Storage Manager restore
operation made changes that will not be in effect until
the machine is rebooted. It is important to note that

314 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1431E • FMV1441E

until the reboot occurs, the system or its applications

FMV1436E An error occurred replacing a registry
might be unstable.
key.
System action: None
Explanation: None.
User response: Reboot the machine as soon as
System action: The registry key is restored from the
possible after the Tivoli Storage Manager restore
server, but cannot be activated in the registry. The
operation ends.
current registry key remains active.
User response: Check the client error log for any other
FMV1431E Restore of the registry failed.
messages that might help identify the problem. Try the
Explanation: None. operation again. If the problem persists, contact IBM
technical support for further assistance.
System action: The registry is not restored.
User response: Check the client error log for any other FMV1437I Event Log Backup function completed
messages that might help identify the problem. Try the successfully.
operation again. If the problem persists, contact IBM
technical support for further assistance. Explanation: Event Log backup was successful.
System action: None.
FMV1432E Keyword Expected after keyword
User response: Continue with normal operations.
'keyword'.
Explanation: A registry command was incorrectly
FMV1438E Backup of the event logs failed.
entered.
Explanation: None.
System action: Registry function is not invoked.
System action: The event logs are not backed up.
User response: Refer to the command reference for
this command. User response: Check the client error log for any other
messages that might help identify the problem. Try the
operation again. If the problem persists, contact IBM
FMV1433E Extraneous argument 'input' after
technical support for further assistance.
keyword 'keyword'
Explanation: A registry command was incorrectly
FMV1439I Event Log Restore function completed
entered.
successfully.
System action: Registry function not invoked.
Explanation: Event Log Restore was successful.
User response: Refer to the command reference for
System action: None.
this command.
User response: Continue with normal operations.
FMV1434E Invalid argument 'input' after keyword
'keyword' FMV1440E Restore of the event logs failed.
Explanation: A registry command was incorrectly Explanation: None.
entered.
System action: The event logs are not restored.
System action: Registry function not invoked.
User response: Check the client error log for any other
User response: Refer to the command reference for messages that might help identify the problem. Try the
this command. operation again. If the problem persists, contact IBM
technical support for further assistance.
FMV1435E An error occurred saving a registry key.
FMV1441E Keyword Expected after keyword
Explanation: None.
'keyword'.
System action: The registry is not backed up.
Explanation: A event log command was incorrectly
User response: Check the client error log for any other entered.
messages that might help identify the problem. Try the
System action: Event Log function is not invoked.
operation again. If the problem persists, contact IBM
technical support for further assistance. User response: Refer to the command reference for
this command.

Chapter 6. FMV messages 315

FMV1442E • FMV1448E

User response: Retry the operation after correcting the

FMV1442E Extraneous argument 'input' after
cause for failure.
keyword 'keyword'
Explanation: A event log command was incorrectly
FMV1446E VSS ASR backup document
entered.
(ASRBackupDoc.xml) not found.
System action: Event Log function not invoked.
Explanation: An error occurred while performing VSS
User response: Refer to the command reference for Automated System Recovery (ASR). Check
this command. dsmerror.log for more information. Possible causes for
the error are the following:
FMV1443E Invalid argument 'input' after keyword v You are trying to recover a machine running a legacy
'keyword' operating system such as windows XP or windows
2003. VSS ASR Restore is not supported for legacy
Explanation: A event log command was incorrectly operating systems.
entered.
v You are trying to run ASR recovery from a backup
System action: Event Log function not invoked. created by a client earlier than version 6.2.2. Such
backups do not have ASRBackupDoc.xml file.
User response: Refer to the command reference for
this command. System action: Processing stops.
User response: Ask your system administrator to
FMV1444E An error occurred creating the Event Log check the error log.
backup directory structure
Explanation: The Tivoli Storage Manager client uses FMV1447I The current user does not need to back
an intermediate directory structure on the client up the default profile.
machine as part of the Windows Event Log backup
Explanation: You are currently using the default
process. The client was unable to create this
profile, and there is no need to back it up.
intermediate directory structure, so the Windows Event
Logs could not be backed up. This problem can occur if System action: None.
you do not have sufficient privileges to perform the
User response: None.
backup operations, if the client is unable to allocate
more memory from the system, or if a component
within the directory structure already exists as a file. FMV1448E The command command is not supported
by the current server.
System action: The Windows Event Logs are not
backed up. Explanation: The server to which the client is
connected does not support the command.
User response: Check the client error log for any other
messages that might have been logged when this 1. If the command is "set event," the server does not
message was written, and take the corrective action (if support event-based policy. This command requires
any) suggested by those messages. Make sure that that the server support event-based policy. That
account under which the operation runs has sufficient support is available only at TSM Server levels 5.2.2
privileges. Ensure that the system has sufficient and above.
memory to run Tivoli Storage Manager. Remove the 2. If the message displays any other command, the
ADSM.SYS directory from the root of your system server is configured to support archive retention
drive, then try the operation again. If the problem protection and cannot process operations not
persists, contact IBM support for further assistance. associated with that facility.
System action: The command is skipped and other
FMV1445E ERROR: could not create NAS image processing continues.
object.
User response: Log in to an appropriate server and
Explanation: Creation of the NAS image object failed retry the command.
for one of following reasons:
v An unauthorized user invoked the NAS command
v NAS operations are not supported on the current
platform
v Cannot find the NAS plugin library.
System action: The requested NAS operation is not
performed.

316 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1449W • FMV1460W

FMV1449W A non-critical, unexpected error was FMV1455I Resynching mirrors. Please wait.
encountered. Deletion of a
Explanation: The destination volume for server-free
snapshot(Set/Volume) failed. Probable
restore has mirrored layout. The mirrors are being
cause, snapshot does not exists anymore.
resynched after the data restored.
Continuing Process... Tivoli Storage
Manager snapShot ID : snapshot-id Tivoli System action: Processing continues.
Storage Manager function name :
function-name Tivoli Storage Manager User response:
function : function-desc Tivoli Storage
Manager return code : TSM-rc Tivoli FMV1456I Mirror synchronization completed.
Storage Manager file : file-name
(line-number) Explanation: Synchronization of the volume's mirrors
completed successfully.
Explanation: None.
System action: Processing continues.
System action: Processing continues.
User response:
User response: Contact the Tivoli Storage Manager
administrator with the information provided in this
message. FMV1457E Mirror synchronization failed.
Explanation: Synchronization of the volume's mirrors
FMV1450W The -FILENAME option was specified failed.
without a file name. Output will be System action: Processing stopped.
written to filename.
User response: Check the error log for more errors.
Explanation: The -FILENAME option was specified, Contact your systems administrator.
but the file name was omitted.
System action: The output is written to the default FMV1458I OBF file for volume name is too small
file. for server-free data transfer.
User response: Reissue the command and specify a Explanation: The OBF file for volume is very small to
valid file name, or use the information that was written initiate a server-free data transfer. Hence this file will
to the default file. not be transferred via a server-free data path.
System action: Processing continues.
FMV1453W The IMAGEGAPSIZE option is not
supported for non-NTFS file systems. User response: None.
The entire volume will be backed up.
Explanation: None. FMV1459E VSS Automated System Recovery (ASR)
failed.
System action: The entire volume is backed up.
Explanation: An error occurred while performing VSS
User response: Refer to the client manual for Automated System Recovery (ASR). Check
additional information regarding the IMAGEGAPSIZE dsmerror.log for more information.
option.
System action: Processing stops.

FMV1454W Used blocks information could not be User response: Ask your system administrator to
obtained for name. The entire volume check the error log.
will be backed up.
Explanation: None. FMV1460W The file segment size entered is greater
than the max size. Please increase the
System action: The entire volume is backed up. max size or decrease the file segment
User response: Check the client error log for any other size.
messages that might help identify the problem. Try the Explanation: The user has enabled both trace
operation again. If the problem persists, contact IBM wrapping and trace spanning but has entered a
technical support for further assistance. segment size greater than the max size.
System action: Allow the user to re-enter the max size
or reduce the segment size.
User response: The user should either increase the
max size or reduce the segment size.

Chapter 6. FMV messages 317

FMV1461E • FMV1468E

FMV1461E Error processing 'filespace FMV1465E Conflicting options ERRORLOGMAX

namepath-namefile-name': unsupported and ERRORLOGRETENTION were
encryption type. specified.
Explanation: The files you are trying to restore or Explanation: Values were specified for both the
retrieve have been backed up or archived by a later ERRORLOGMAX and the ERRORLOGRETENTION
version of the Tivoli Storage Manager client. The file options. These options are mutually exclusive.
encryption method is not supported by the current
System action: Processing stops.
client.
User response: Specify a nonzero value for
System action: Object skipped.
ERRORLOGMAX if you wish to have the Tivoli Storage
User response: Restore or retrieve the file with the Manager error log wrap when it reaches the specified
most recent version of the Tivoli Storage Manager maximum value. Use ERRORLOGRETENTION if you
client. wish you have the error log limited in size on a
time-based schedule.
FMV1462E Unsupported encryption type
FMV1466E Conflicting options SCHEDLOGMAX
Explanation: The files you are trying to restore or
and SCHEDLOGRETENTION were
retrieve have been backed up or archived by a later
specified.
version of the Tivoli Storage Manager client. The file
encryption method is not supported by the current Explanation: Values were specified for both the
client. SCHEDLOGMAX and the SCHEDLOGRETENTION
options. These options are mutually exclusive.
System action: Object skipped.
System action: Processing stops.
User response: Restore or retrieve the file with the
most recent version of the Tivoli Storage Manager User response: Specify a nonzero value for
client. SCHEDLOGMAX if you wish to have the Tivoli
Storage Manager scheduler log wrap when it reaches
the specified maximum value. Use
FMV1463E Unexpected error in cryptography
SCHEDLOGRETENTION if you wish you have the
library.
scheduler log limited in size on a time-based schedule.
Explanation: There was an unexpected error in the
cryptography library. See the error log for more
FMV1467E ICC routine icc-routine returned: majRC
information.
= majRC, minRC = minRC, desc = 'desc'.
System action: processing stops.
Explanation: There was an error within an ICC
User response: Check the error log for FMV1467E to cryptography library. This message reports return codes
determine the cause of failure. Verify you Tivoli Storage and problem description which can be used by Tivoli
Manager client is installed properly. If needed, reinstall Storage Manager technical support personnel to
client and/or API. If the problem still exists, contact determine the cause of the error.
Tivoli Storage Manager technical support.
System action: Client exits.
User response: Verify you Tivoli Storage Manager
FMV1464S Cannot load ICC encryption library.
client is installed properly. If needed, reinstall client
Explanation: Tivoli Storage Manager is using and/or API. If the problem still exists, contact Tivoli
cryptography library which is installed automatically Storage Manager technical support.
with the client and is being loaded at runtime. The
client cannot proceed if the library is not loaded.
FMV1468E Backing up Automated System Recovery
System action: Client exits. (ASR) files failed. No files will be
backed up.
User response: Check the error log for FMV1467E to
determine the cause of failure. Verify you Tivoli Storage Explanation: An error occurred while backing up the
Manager client is installed properly. If needed, reinstall files needed for Automated System Recovery (ASR). No
client and/or API. If the problem still exists, contact files were backed up.
Tivoli Storage Manager technical support.
System action: Processing stops.
User response: Ask your system administrator to
check the error log. Verify that the Windows account
from which you are running this command has
administrator authority and try the command again.

318 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1469E • FMV1476E

FMV1469E Error processing 'filespace FMV1473E Session rejected: TCP/IP connection

namepath-namefile-name'; invalid failure for Shared Memory
encryption key.
Explanation: An attempt to connect to the local server
Explanation: The key you entered does not match the using the Shared Memory protocol has failed during
key that was used to encrypt the file during backup. initial TCP/IP communications. This error can occur if
The file can not be restored unless the matching key is the server is not listening on the correct port, or if the
entered. server is down.
System action: processing stops. System action: Session rejected. Processing stopped.
User response: Try the restore operation again and User response: Retry the operation, or wait until the
provide the correct key. server comes back up and retry the operation. If the
problem continues, see your system administrator for
further help.
FMV1470E Unable to load GPFS functions needed
for ACL and extended attributes
support: skip path_name FMV1474E An error occurred using the Shared
Memory protocol
Explanation: The IBM GPFS functions that handle the
GPFS ACL and extended attributes were not loaded. Explanation: An error has occurred while reading or
writing data through the Shared Memory
System action: The object is skipped. Processing
communications protocol.
continues with the next object.
System action: Tivoli Storage Manager cannot
User response: Ensure that the GPFS software is
complete the requested operation.
installed on the system and try the operation again. On
Linux, iensure that there has been an appropriate User response: Check the trace log for additional
symbolic link created in /usr/lib/ directory for the information and retry the operation. If the problem
GPFS libgpfs.so shared library. continues, see your system administrator for further
help.
FMV1471E ASR system information file creation
failed. ASR backup is unsuccessful. FMV1475E Insufficient authority to connect to the
shared memory region
Explanation: An error occurred while creating the
system information file (asr.sif) needed for Automated Explanation: The user issuing the command does not
System Recovery (ASR). The ASR backup is have authority to connect to the shared memory
unsuccessful. segment. When the shared memory segment is created
by the server, it will be owned by the effective uid of
System action: Processing stops.
the server process (dsmserv). Only processes running
User response: Ask your system administrator to under this uid or root will be allowed to connect to the
check the error log. Verify that the Windows account segment (and thus to the server).
from which you are running this command has
System action: The session is rejected and processing
administrator authority and that you have access to the
stops.
system object staging directory <system drive>
:\adsm.sys. Try the command again. User response: Run the command under the uid of
the processing running dsmserv, if possible. Otherwise
contact your system administrator for further help.
FMV1472E Could not add entry to the ASR system
information file. ASR backup is
unsuccessful. FMV1476E CLUSTERNODE is set to YES but the
Cluster Information Daemon is not
Explanation: An error occurred while adding an entry
started.
to the system information file (asr.sif) needed for
Automated System Recovery (ASR). The ASR backup is Explanation: The IBM HACMP™ Cluster Information
unsuccessful. Daemon must be started in order to specify the
CLUSTERNODE option.
System action: Processing stops.
System action: Processing ends.
User response: Ask your system administrator to
check the error log. Verify that the Windows account User response: Start the HACMP Cluster Information
from which you are running this command has Dameon.
administrator authority and try the command again.

Chapter 6. FMV messages 319

FMV1477E • FMV1487E

FMV1477E CLUSTERNODE is set to YES but the FMV1482E An unexpected error (retcode) occurred
cluster load library is not valid. while the program was trying to obtain
the cluster name from the system.
Explanation: The load library that the operating
system provides to obtain the cluster name is not valid. Explanation: An unknown error occurred while the
A possible cause is an out-of-date load library which program was trying to obtain the cluster name from the
does not contain the proper routines this product cluster service. The error code is the reason code
expects. provided directly from the cluster service being used in
this operating system environment.
System action: Processing ends.
System action: Processing ends.
User response: Ensure that the latest cluster software
is installed on the system. User response: Consult the documentation for your
clustering software for an explanation of the reason
code. Insure that your clustering service is operational,
FMV1478E CLUSTERNODE is set to YES but the
then try the Tivoli Storage Manager operation again.
cluster software is not available on this
system.
FMV1483I Schedule log pruning started.
Explanation: The load library that the operating
systems provides to obtain the cluster name is not Explanation: The schedule log pruning function has
available on this system. begun.
System action: Processing ends. System action: The schedule log is pruned.
User response: Ensure that the cluster software is User response: None.
installed on the system.
FMV1484I Schedule log pruning finished
FMV1479E CLUSTERNODE is set to YES but this successfully.
machine is not a member of a cluster.
Explanation: The schedule log pruning function
Explanation: This machine is not a member of a completed with no errors.
cluster node. Possible causes are that the cluster service
System action: None.
has not been configured correctly, or that the cluster is
in the process of initialization. User response: None.
System action: Processing ends.
FMV1486E An error occurred while restoring the
User response: Ensure that the cluster software is
WMI repository. The database will not
configured properly. If the cluster is in the process of
be updated.
initialization, retry the operation at a later time.
Explanation: The Windows event log and Tivoli
Storage Manager error log might contain additional
FMV1480E CLUSTERNODE is set to YES but the
information related to this error.
cluster service is not enabled on this
system. System action: processing stops.
Explanation: The cluster service has not been enabled User response: Examine the Windows event log and
on this system. Tivoli Storage Manager error log for messages related
to Windows Management Instrumentation (WMI).
System action: Processing ends.
Ensure that the WMI is started.
User response: Enable the cluster service on the
system.
FMV1487E An error occurred while backing up the
WMI repository. The database will not
FMV1481E The CLUSTERNODE option is not be backed up.
supported on this system.
Explanation: The Windows event log and Tivoli
Explanation: This option is not supported on this Storage Manager error log might contain additional
system. information related to this error.
System action: Processing ends. System action: processing stops.
User response: Disable the CLUSTERNODE option in User response: Examine the Windows event log and
the local options file. Tivoli Storage Manager error log for messages related
to WMI. Ensure that the Windows Management
Instrumentation service is started.

320 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1489E • FMV1497W

the system options file and make sure it is accessible.

FMV1489E The WMI service failed to stop. No files
Retry the operation.
will be restored.
Explanation: An error occurred while stopping the
FMV1494S Invalid virtual mountpoint filespace-name:
Windows Management Instrumentation (WMI) service.
Symbolic link.
The database will not be restored.
Explanation: The specified VIRTUALMOUNTPOINT
System action: processing stops.
in the system options file is invalid because it is a
User response: Examine the Windows event log and symbolic link and FOLLOWSYMBOLIC is not set.
Tivoli Storage Manager error log for messages related
System action: Tivoli Storage Manager attempts to
to Windows Management Instrumentation (WMI). You
continue the current operation.
might need to quiesce WMI activity or reboot the
machine in order to free resources which are preventing User response: Set the option FOLLOWSYMBOLIC to
the WMI service from stopping. YES in the user options file. Retry the operation.

FMV1490W File specification 'file-spec' ignored. A FMV1495S Invalid virtual mountpoint filespace-name:
file list has already been specified. Other error, rc = return-code.
Explanation: A non-option argument (file Explanation: The specified VIRTUALMOUNTPOINT
specification) was encountered after the -FILELIST has in the system options file is invalid.
been processed.
System action: Tivoli Storage Manager attempts to
System action: The argument is ignored. continue the current operation.
User response: You may have either a -FILELIST or User response: Make sure the virtual mountpoint is a
explicit file specifications on this command, but not directory and accessible from the shell, and retry the
both. operation.

FMV1491E Only one -FILELIST option allowed. FMV1496W Duplicate include/exclude option 'option
file-name' found while processing the
Explanation: The -FILELIST option may only be
client options file. This might produce
specified once per command
unexpected results.
System action: The command is not executed.
Explanation: Tivoli Storage Manager found a
User response: Enter only one -FILELIST option on duplicate statement while processing the client options
the command. file, which might produce unexpected results.
System action: Processing continues.
FMV1492S Invalid virtual mountpoint filespace-name:
User response: Verify if you obtained the desired
File not found.
results. If not, you need to correct the client options file
Explanation: The specified VIRTUALMOUNTPOINT by removing the duplicate option statement.
in the system options file is invalid because it could not
be found in the file system.
FMV1497W Duplicate include/exclude option 'option
System action: Tivoli Storage Manager attempts to file-name' found while processing the
continue the current operation. client options passed by the server. This
might produce unexpected results.
User response: Check the virtual mountpoint in the
system options file and make sure it exists in the file Explanation: Tivoli Storage Manager found a
system. Retry the operation. duplicate statement while processing the client options
by the server, which might produce unexpected results.
FMV1493S Invalid virtual mountpoint filespace-name: System action: Processing continues.
Access denied.
User response: Verify if you obtained the desired
Explanation: The specified VIRTUALMOUNTPOINT results. If not, you need to correct either the client
in the system options file is invalid because access to it options file or the client options passed by the server.
is denied.
System action: Tivoli Storage Manager attempts to
continue the current operation.
User response: Check the VIRTUALMOUNTPOINT in

Chapter 6. FMV messages 321

FMV1498E • FMV1506E

FMV1498E The IIS services failed to stop. No files FMV1502E Access to system function required to
will be restored. run has been denied
Explanation: An error occurred while stopping the Explanation: The permissions of the Trusted
Internet Information Services (IIS) services. The Communication Agent do not allow it to be accessed
metabase will not be restored. by the user of the Tivoli Storage Manager client.
System action: processing stops. System action: Tivoli Storage Manager ends.
User response: Examine the Windows event log and User response: See your system administrator.
Tivoli Storage Manager error log for messages related
to Internet Information Services (IIS). You might need
FMV1503E Valid password not available for server
to quiesce IIS activity or reboot the machine in order to
'server-name'. The administrator for your
free resources which are preventing the IIS service from
system must run Tivoli Storage Manager
stopping.
and enter the password to store it
locally.
FMV1499E Creation of table of contents failed.
Explanation: The file containing the stored password
Explanation: A failure occurred on the server during for the specified server server-name is unavailable.
creation of the table of contents.
System action: Tivoli Storage Manager ends.
System action: The table of contents was not created.
User response: The administrator for your system
User response: This abort code indicates there was a must set and store a new password.
problem creating a table of contents on the server. The
sysadmin will need to consult the activity log on the
FMV1504E Error starting the Trusted
server to determine the cause.
Communication Agent process.
Explanation: An error has occurred starting the
FMV1500E Module dsmtca not found in secure
Trusted Communication Agent process; specifically, the
directory.
fork() function has failed.
Explanation: Tivoli Storage Manager cannot find the
System action: Tivoli Storage Manager ends.
Trusted Communication Agent module (dsmtca) in the
appropriate directory. User response: Probable system error. If the problem
persists, restart the workstation.
System action: Tivoli Storage Manager ends.
User response: Log on as root user, then create a link
FMV1505W Performing image backup of the entire
to dsmtca module in /usr/bin with the command: ln -s
volume for volume name. The
/usr/tivoli/tsm/client/ba/bin/dsmtca
IMAGEGAPSIZE option value of image
/usr/bin/dsmtca
gap size is being ignored as this level of
the operating system does not support
FMV1501E Trusted agent execution/owner used block image backup. Please
permissions are invalid upgrade to AIX 5.3 Maintenance Level 7
or later in order to perform used block
Explanation: The Trusted Communication Agent
image backup.
execution/owner permissions are invalid.
Explanation: AIX 5.3 Maintenance Level 7 or later has
System action: Tivoli Storage Manager ends.
some necessary fixes that are required to support used
User response: Have your system administrator check block image backup.
the installation instructions for the client to ensure that
System action: The entire volume is backed up.
the Trusted Communication Agent permissions are set
correctly. This error can be caused by installing Tivoli User response: Please upgrade to AIX 5.3
Storage Manager as a non-root user. For the UNIX Maintenance Level 7 or later in order to perform used
platforms that have the installation program block image backup.
(dsm.install), you must run dsm.install while logged in
as the root user.
FMV1506E The Tivoli Storage Manager Trusted
Communication Agent received an
invalid request.
Explanation: The Trusted Communication Agent is
invoked by the Tivoli Storage Manager client and has
received an unknown request argument in the call.

322 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1507E • FMV1513E

System action: Tivoli Storage Manager ends.

FMV1511I Invalid Restore session number entered.
User response: It is possible the Trusted Try again.
Communication Agent was mistakenly invoked by a
Explanation: You entered a number not shown in the
process other than the Tivoli Storage Manager client. If
list of restartable restores. The number you entered is
that is not the case, then this is an internal error. If the
either less than one or greater than the highest item
problem recurs, contact your IBM service
number displayed.
representative.
System action: Tivoli Storage Manager waits for you
to enter a valid selection.
FMV1507E This action requires Tivoli Storage
Manager administrative authority on User response: Enter a number from the list or 'Q' to
this system. quit.
Explanation: An activity has been attempted that must
be performed by the Tivoli Storage Manager FMV1512E Scheduled event 'event' failed. Return
administrator (for example, open registration, filespace code = value.
delete or password update).
Explanation: One or more error conditions were
System action: Tivoli Storage Manager ends. encountered that prevented the schedule from
completing successfully. This message is preceded by
User response: If the activity is required, the
other messages that indicate the specific problems
administrator for this system must perform it.
encountered during the operation.
System action: Scheduled event failed.
FMV1508E Error allocating semaphores.
User response: Check the schedule and error log files
Explanation: An error has occurred because the
for the messages that specify what problems were
semaphores you are attempting to allocate have become
encountered during the operation. Correct the
insufficient.
conditions that caused those messages to be issued. The
System action: Processing ends. specific corrective actions will depend on the specific
errors encountered.
User response: Ask your system administrator for
assistance, and possibly increase the number of For more information about return codes, search for
semaphores in your system. "client return codes" in the appropriate version of the
product information (www.ibm.com/support/
knowledgecenter/SSGSG7/).
FMV1509E Error setting semaphore value or
waiting on semaphore.
FMV1513E The object 'object_name' is skipped from
Explanation: An error has occurred while attempting rename. Error_condition.
to set or wait on a semaphore.
Explanation: IBM Tivoli Storage Manager skips the
System action: Processing ends. specified object from renaming because the object with
User response: Probable system error. If the problem the same long name but with different attributes exists
persists, restart the workstation. on the server.
System action: The backup operation continues. The
FMV1510W The specified backupset either does not specified object will expire during the next incremental
exist, or does not contain file data. backup.

Explanation: The specified backupset either does not User response: The object is skipped if one of the
exist, or does not contain file data for the node name following condition occurs:
specified. The restore backupset command is limited to v The long name object(LN) has a more recent insert
backupsets that contain file data. To restore an image date than the short name object(SN).
backup from a backupset, use the restore image v The management classes for LN and SN do not
command. match.
System action: Processing stopped. v The copy groups for LN and SN do not match.
User response: If an incorrect backupset name was v LN and SN have different owners.
specified, try the command again with the correct v The creation date for LN and SN do not match.
backupset name. If you are trying to restore an image v The short name attribute for LN does not match SN.
from a backupset, refer to the restore image command
for the correct syntax. If you are unable to determine what is wrong, report
the problem to your service representative.

Chapter 6. FMV messages 323

FMV1514W • FMV1529I

FMV1514W Encryption key passwords are not the FMV1522E It is not possible to authenticate with
same. the client node client-node ! The Space
Management Agent version agent-version
Explanation: The key passwords are different.
running on client-node does not match
System action: Tivoli Storage Manager allows you to with the Space Management Console
try again. version console-version you are running !

User response: Enter the correct password. Explanation: The version of the Space Management
Console does not match with the version of the Space
Management Agent running on the client node
FMV1515E Loading a table of contents failed. machine. To avoid incompatibleness it is necessary to
Explanation: A failure occurred on the server during run the console and the agent with the same version.
loading of the table of contents. System action: The Space Management Console exits.
System action: The table of contents was not loaded. User response: Use Space Management Console with
User response: This abort code indicates there was a the same version like the Space Management Agent
problem loading a table of contents on the server. The running on the HSM node you want to manage.
sysadmin will need to consult the activity log on the
server to determine the cause. FMV1523E An error occurred while connecting to
TSA/SMDR service.
FMV1519E Your node does not have permission to Explanation: An error was encountered during a call
delete backup files to the TSA/SMDR service. This message usually
Explanation: The server does not allow your node to follows previous messages that contain more specific
delete backup files. information about the problem.

System action: Tivoli Storage Manager did not delete System action: Processing stopped.
the backup files. User response: Refer to previous messages in
User response: See your system administrator. dsmerror.log for further information. If those messages
are not helpful in identifying the cause of the problem,
see your system administrator for further assistance.
FMV1520E Failure writing to the Tivoli Storage
Manager error log: errno = errno-value,
FMV1528I Tivoli Storage Manager is converting the
Explanation: A failure was encountered when writing log-file from continuous (pruning) mode
to the dsmerror log or dsierror log. The system set the to wrapping mode. This process may
error code errno-value. It is possible that no space is take several minutes.
available at the given log location.
Explanation: The log-file was previously in continuous
System action: Processing terminates. mode where the only size control was through the use
User response: Set the DSM_LOG (or DSMI_LOG) of ERRORLOGRETENTION or
environment variable to a directory with adequate SCHEDLOGRETENTION option. This is the first
space to write the log data. occasion where ERRORLOGMAX or SCHEDLOGMAX
is specified for this log, so its format must be changed
and old data saved.
FMV1521E Failure writing to a Tivoli Storage
Manager log or log-related file: file-name, System action: Transition processing continues.
errno = errno-value, reason User response: None.
Explanation: A failure was encountered when writing
to one of the log files or a related file named file-name. FMV1529I Tivoli Storage Manager is converting the
The system set the error code errno-value. reason is the log-file from wrapping mode to
system explanation of that error code. Among other continuous (pruning) mode. This
things, it is possible that no space is available at the process may take several minutes.
given log location.
Explanation: The log-file was previously in wrapping
System action: Processing terminates. mode where the size control was through the use of the
User response: Set the DSM_LOG (or DSMI_LOG) ERRORLOGMAX or SCHEDLOGMAX option. This is
environment variable to a directory with adequate the first occasion where ERRORLOGMAX or
space to write the log data. SCHEDLOGMAX is not specified for this log, so its
format must be changed and old data saved.
System action: Transition processing continues.

324 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1530I • FMV1540E

User response: None. User response: Use the ASNODENAME option only
to access another node. It is not necessary to set
ASNODENAME option to access your own node.
FMV1530I count log records processed.
Remove ASNODENAME from your option file unless
Explanation: This is just a progress report to let you you are actually trying to access a node that you have
know the process is still ongoing. been granted authority to access with the
administrative command "Grant Proxynode".
System action: Transition processing continues.
User response: None. FMV1536E Proxy Rejected: The server has an
internal error.
FMV1532E Proxy Rejected: Proxy authority has not Explanation: The client cannot proxy to the node
been granted to this node. named by the ASNODENAME option because of an
Explanation: The node has not been granted proxy internal server error.
authority to access the node named by the System action: Tivoli Storage Manager canceled the
ASNODENAME option. The Tivoli Storage Manager current operation.
administrator must first grant proxy authority.
User response: See your system administrator
System action: The Tivoli Storage Manager operation immediately.
ends.
User response: The Tivoli Storage Manager server FMV1537E The ASNODENAME option is not valid
administrator must grant proxy authority for this node. with the FROMNODE option.
See the administrator command "Grant Proxynode".
Explanation: None.
FMV1533E Proxy Rejected: The node name you System action: Processing stops.
specified in the ASNODENAME option
User response: Remove the ASNODENAME option
is locked.
from the options file or do not use the FROMNODE
Explanation: The Tivoli Storage Manager option.
administrator has locked the node you specified as the
ASNODENAME option.
FMV1538E The operation that is being attempted
System action: The Tivoli Storage Manager operation cannot be invoked using the
ends. ASNODENAME option.

User response: The Tivoli Storage Manager server Explanation: None.

administrator must unlock the node before you can
System action: Processing stops.
access it. Try the operation later, or check with your
Tivoli Storage Manager administrator. User response: Remove the ASNODENAME option
and retry the operation.
FMV1534E Proxy Rejected: The Tivoli Storage
Manager server has run out of memory. FMV1539E The ASNODENAME option cannot be
used with the CLUSTERNODE option.
Explanation: There is not enough memory available to
allow this operation to continue. Explanation: None.
System action: Tivoli Storage Manager canceled the System action: Processing stops.
current operation.
User response: Remove the ASNODENAME option
User response: Try the operation again. If the problem and retry the operation.
continues, see your system administrator to increase the
amount of memory of the server.
FMV1540E Incremental backups using snapshot
difference is not supported on this
FMV1535E Proxy Rejected: ASNODENAME and version of the NetApp file server.
NODENAME are identical.
Explanation: Incremental backup using Snapshot
Explanation: Tivoli Storage Manager does not allow difference requires Data ONTAP V7.3 or later. To back
the ASNODENAME and NODENAME option values to up unicode file names, upgrade to Data ONTAP V7.3.3
be the same. or later or V8.1 or later.
System action: Tivoli Storage Manager canceled the System action: Processing stops.
current operation.
User response: Upgrade the file server to a supported

Chapter 6. FMV messages 325

FMV1541E • FMV1551E

level of Data ONTAP, then retry the operation. can be backed up, enter: 'dsmc q was -wastype=local'.

FMV1541E Node entered has been federated into a FMV1547W Tivoli Storage Manager failed to unlock
Network Deployment, federated nodes the WebSphere Configuration
cannot be backed up. Repository.
Explanation: Node entered has been federated into a Explanation: None.
Network Deployment, federated nodes cannot be
System action: The unlock of the WebSphere
backed up.
Configuration Repository fails.
System action: None
User response: Make sure that the WebSphere server
User response: Run 'dsmc q was -wastype=local' to is running. If the repository is locked, then unlock it
see the nodes that may be backed up. and try the operation again. Ensure that the correct
node is being backed up. To see a list of available
nodes that can be backed up, run: 'dsmc q was
FMV1542E Incorrect WAS backup type entered, no
-wastype=local'.
node of that name and type exists.
Explanation: There is no node with the WAS backup
FMV1548E A supported version of WebSphere is
type that was entered.
not installed on this machine.
System action: None
Explanation: A supported version of WebSphere is not
User response: Check the wastype that was entered. installed on this machine. The only version of
Run 'dsmc q was -wastype=local' to see the nodes that WebSphere that is supported is 5.0.x.
may be backed up.
System action: None
User response: Install WebSphere 5.0 on the machine.
FMV1543E Incorrect WAS node entered, no node
exists with that name.
FMV1549E No application server instances were
Explanation: There is no node with the WAS backup
found. Unable to perform backup.
type that was entered.
Explanation: The application server is not installed on
System action: None
this machine.
User response: Check the node name that was
System action: Backup is not performed.
entered. Run 'dsmc q was -wastype=local' to see the
nodes that may be backed up. User response: Install the application server.

FMV1544E An error in WAS processing has FMV1550E No network deployment manager

occurred. instances were found to back up.
Explanation: None. Explanation: Deployment manager is not installed on
this machine.
System action: None
System action: Back up is not performed.
User response: Run the following command to see the
nodes that can be backed up: dsmc query was User response: Install the network deployment
-wastype=local Make sure the results are correct for manager.
your environment, then try the operation again. If the
problem persists, contact Tivoli Storage Manager
FMV1551E A Tivoli Storage Manager authorized
technical support for further assistance.
user must configure IBM Tivoli Storage
Manager before individual users can use
FMV1546W Tivoli Storage Manager failed to lock it.
the WebSphere configuration repository.
Explanation: IBM Tivoli Storage Manager was not
Explanation: None. started by a Tivoli Storage Manager authorized user
and the 'Tivoli Storage Manager System Preferences' file
System action: The lock of the WebSphere®
could not be located.
configuration repository fails.
System action: IBM Tivoli Storage Manager exits.
User response: Ensure that the WebSphere server is
running. If the server is already running, ensure that User response: The initial setup and configuration of
the repository is unlocked. Ensure that you are backing IBM Tivoli Storage Manager must be done by a Tivoli
up the correct node. To see a list of available nodes that Storage Manager authorized user. To become a Tivoli

326 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1552W • FMV1558W

Storage Manager authorized user, system User response: Upgrade the WAS plug-in to 5.2.1 or
administrators must use the "Tivoli Storage Manager greater.
Backup for Administrators" application. Refer to the
Backup-Archive Client Installation and User's Guide for a
FMV1556E Setting the WAS user and password
complete discussion of the Tivoli Storage Manager
failed.
authorized user.
Explanation: Password validation for the WAS user
and password failed.
FMV1552W A user name and a password have not
been provided to Data Protection for System action: WAS password validation fails.
WebSphere.
User response: Rerun the set WASPassword command
Explanation: The dsmc set WASPassword command with the correct values for user and password.
has not been run to provide the user name and the
password for Data Protection for WebSphere. Data
Protection for WebSphere needs the user name and FMV1557W The WAS Server was not running, and
password to be able to run when WebSphere security is the password file was saved without
turned on. validation.

System action: Data Protection for WebSphere cannot Explanation: If the WAS server is down, then it is not
run. possible to connect to the server and validate the
user-entered password. The password has still been
User response: Run the dsmc set WASPassword saved, but no validation has been performed.
command to set the WebSphere security user name and
password. System action: The set WAS password command did
not validate the password. The password has still been
saved, but no validation has been performed. The
FMV1553W The user name and password that have password may be incorrect.
been provided to Data Protection for
WebSphere are invalid. User response: There are two options:
v Try a backup. If the backup performs a failover, and
Explanation: None. there is a incorrect password message in the error
System action: Data Protection for WebSphere cannot log, then the password that was entered is incorrect.
run. v Start the WAS server and rerun the set password
command. Since the server is now up, validation will
User response: Run the dsmc set WASPassword
be performed as normal and the user notified if a
command to set the WebSphere security user name and
good/bad password was entered.
password.

FMV1558W The WebSphere backup is failing over

FMV1554W The WASOffline option has been
to an offline backup.
ignored.
Explanation: If there is an error locking the
Explanation: When a WebSphere server is running,
WebSphere configuration repository, then Data
Data Protection for WebSphere contacts WebSphere and
Protection for WAS will still get a backup and not lock
locks the Configuration Repository. The WASOffline
the repository.
option is only valid when a WebSphere server is not
running. If a WebSphere server is running, then System action: The WebSphere backup fails over to an
WASOffline is ignored. offline backup.
System action: The WASOffline option is ignored. User response: Check the error log to see the nature
of the lock error. The lock operation can fail because:
User response: Remove the WASOffline option from
the options file. v The WAS server is not running
v The repository is already locked
FMV1555E The WebSphere Application Server v Security is turned on and there is no WAS
(WAS) plug-in level must be at 5.2.1 or user/password file
greater to set the WebSphere user and v Security is turned on and the information in the
password. WAS user/password file is bad.
Explanation: You must have the backup-archive client
and the WAS plug-in at a level of 5.2.1 or higher to be Correct the lock error.
able to connect to WebSphere when security is enabled.
System action: WebSphere does not set the user and
password.

Chapter 6. FMV messages 327

FMV1560W • FMV1569E

FMV1560W The WebSphere server is not running. FMV1567I A 5.2.2 or higher client is restoring data
backed up from a 5.2.0 client. No
Explanation: The WebSphere server is not running.
version check can be performed before
The WAS server is running for backup operations.
the restore.
System action: The WebSphere server is not running.
Explanation: WebSphere's version information was not
User response: Start the WAS server and run the stored as part of the backup for 5.2.0. So, a 5.2.2 client
backup again. cannot ensure that the version of WAS that is being
restored is the same version of WAS that is on the
machine. A version of WAS that is restored may be
FMV1562E WAS Restore failed during EAR incompatible with the version of WAS on the machine
Expansion. and can cause errors in WAS.
Explanation: EAR Expansion is performed for a System action: No version check is performed.
WebSphere Application server after the files have been
restored. User response: Make sure that the version of WAS
that is being restored is the same as the version of WAS
System action: WAS restore fails. that is installed on the machine.
User response: Run the restore again.
FMV1568E The CAD attempted to register it's
FMV1563W The itsm.was.properties file does not tcpport and tcpip address without using
exist. the TCPCADADDRESS option.

Explanation: The itsm.was.properties file is used to Explanation: The CAD sent the port and address
store the WebSphere security user name and password. information to the server, however, there was a
problem registering the information with the server.
System action: None. The problem occurred because no default value for the
User response: Run the dsmc set waspassword tcpip address was provided. The server was unable to
command to create this file. determine a default value for the tcpip address because
the communication method was not tcpip.

FMV1565E No WebSphere EARExpander was System action: The server cannot register the
found. Copy the EARExpander tool information for the CAD. CAD processing will
from the base WebSphere bin directory continue, but some functions of the CAD may not be
to the instance bin directory, then run working properly.
the restore operation again. User response: Use TCPCADADDRESS in the client
Explanation: The EAR files are expanded for an option file to indicate the proper TCP/IP address for
instance of an Application server and the EARExpander this CAD.
tool does not exist in the instance bin directory.
System action: No WebSphere EARExpander found. FMV1569E The CAD attempted to register it's
tcpport and tcpip address but the
User response: Copy the WAS EARExpander tool TCP/IP address resolved to the loopback
from the base install's bin directory to the bin directory address and was rejected by the server.
of the instance. Then run the WAS restore operation
again, after the EARExpander tool has been copied. Explanation: The CAD sent the port and address
information to the server, however, there was a
problem registering the information with the server.
FMV1566E The version of WebSphere on the The problem occurred because the server detected that
machine does not match the version of the address provided resolved to the loopback address.
WebSphere that was backed up. These
versions must match for a WAS restore System action: The server did not register the
operation. information for the CAD. CAD processing will
continue, but some functions of the CAD may not be
Explanation: The version of WebSphere on the working properly.
machine does not match the version of WebSphere that
was backed up. These versions must match for a WAS User response: Use TCPCADADDRESS in the client
restore operation. option file to indicate the proper TCP/IP address for
this CAD. Loopback address is not valid.
System action: The WAS restore operation fails.
User response: Install the correct version of
WebSphere on the machine before performing the
restore operation.

328 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1570E • FMV1577I

additional information about these options.

FMV1570E Registering this instance of the Cad
with the server failed. Cad process
continues. FMV1574E Journal Query Failed.
Explanation: The CAD failed to register address Explanation: The journal daemon was unable to
information to the server, due to an error. There should process the requested journal query.
be a message immediately preceding this message that
would indicate the problem more precisely. System action: Journal backup processing is
interrupted.
System action: The server did not register the
information for the CAD. CAD processing will User response: Retry the backup, check the journal
continue, but some functions of the CAD may not be daemon errorlog for the cause of the failure. Backup of
working properly. other file systems in the domain will continue.

User response: Look at messages immediately

preceding this message to help determine what error FMV1575E Journal Daemon Communications Error.
occurred. Explanation: An error occurred communicating with
the journal daemon.
FMV1571E The time-option option cannot be used System action: Journal backup processing is
without specifying the date-option option interrupted.
Explanation: If the to/from/pit time options is User response: Retry the backup, check the journal
specified then the corresponding to/from/pit date daemon and client errorlogs for the cause of the failure.
MUST also be specified.
System action: Processing stopped. FMV1576W Space Management Agent version
User response: Either remove the to/from/pit time mismatch. The Space Management
option or add the corresponding to/from/pit date Agent (hsmagent) version agent-version
option. running on 'client-node' client node does
not match with the Space Management
Console (GUI) version console-version
FMV1572E An unexpected error was received from you are running! To avoid compatibility
the server query, RC=re tcode. problems, please use the same version
for the Space Management Console and
Explanation: An unexpected error was received by the
the Space Management Agent. Do you
client. This could be caused by network problems or a
want to proceed?
programming error.
Explanation: The version of the Space Management
System action: Tivoli Storage Manager canceled the
Console does not match with the version of the Space
current operation.
Management Agent running on the client node
User response: Verify that your communication path machine. To avoid compatibility problems, please use
is functioning properly and try the operation again. If the same version for the Space Management Console
the problem persists, contact your Tivoli Storage (GUI) and the Space Management Agent (hsmagent).
Manager administrator for further assistance.
System action: Prompt the user to exit or continue.
User response: Use Space Management Console (GUI)
FMV1573E FROMDATE and TODATE cannot be
with the same version like the Space Management
used with PITDATE.
Agent (hsmagent) running on the HSM node you want
Explanation: The PITDATE option specifies different to manage.
and conflicting date selection criteria from the
FROMDATE and TODATE options. Therefore these
FMV1577I The Windows console event handler
options cannot be combined.
received a 'event' console event.
System action: The restore operation is not performed.
Explanation: A console event was received by one of
User response: Determine whether you require the the IBM Tivoli Storage Manager processes or programs.
functionality of PITDATE or FROMDATE and The following events can be received:
TODATE, then try the operation again. If you want to v Ctrl-C - This indicates either the user entered the
restore files as of a certain date and time, use PITDATE ctrl-c sequence or that one of the Windows services
and PITTIME. If you want to restore files from a given was stopped.
range of dates, use FROMDATE, TODATE,
FROMTIME, and TOTIME. Refer to the Tivoli Storage System action: None.
Manager client manual for your operating system for User response: None.

Chapter 6. FMV messages 329

FMV1578E • FMV1587W

User response: Reboot the machine as soon as

FMV1578E The specified path 'path' is not valid for
possible after the Tivoli Storage Manager restore
backup or archive.
operation ends.
Explanation: The specified path is a special file system
or part of a special file system. Special file systems
FMV1583E The Hardware Utility plug-in module
contain dynamic information generated by the
was not found or could not be loaded.
operating system and should not be backed up or
archived. Refer to the Tivoli Storage Manager client Explanation: Processing stops.
manual for a complete list of special file systems for
your operating system. System action: None.

System action: Processing continues if there are other User response: Run "dsmc show plugins" at the Tivoli
file systems to back up. Storage Manager command-line client prompt to see
the available plug-ins on the system and verify the
User response: Do not specify special file systems for path which is being used to load the plug-ins. If the
backup or archive. plugin path is available and the Hardware Utility
plug-in, libPiHDW.a, is present, ensure that the
LIBPATH variable is set to the Hardware product's
FMV1579E GSKit function func-name failed with
library path, for example, LIBPTH=/usr/opt/
error-code: session
db2_08_01/lib.
Explanation: A GSKit function has failed with the
specified error code.
FMV1584E Error loading system library
System action: Processing stopped 'libdevmapper.so' required for image
operations for LVM2 volumes.
User response: Make sure you have configured the
key database for SSL communication as described in Explanation: The system library libdevmapper.so
the documentation. If the problem persists, contact required for LVM2 image operations could not be
Tivoli Storage Manager customer support. loaded. This error can occur when the library does not
exist on the system, or the library is an earlier level
than is required. This error also occurs when the library
FMV1580W An Include.Fs statement with
can not be opened by the Tivoli Storage Manager clienti
performance algorithm set already exists
process.
for the drive specified. Do you want to
replace the statement? System action: The image operations for LVM2
volumes are not available.
Explanation: The user tried to create a duplicate
Include.Fs entry on a drive that already has a User response: Check the installed packages and the
performance algorithm associated with it. This is library versions on the system. If correct versions are
applicable to the Preference Editor on the MFC GUI installed, check for access related issues. If the system
does not have these libraries installed, contact your
System action: The user can replace the statement
Linux OS distributer.
with the new one or they can cancel out of this
operation
FMV1587W Unable to read extended attributes for
User response: The user is prompted to replace the
object object-full-name due to errno:
statement with the new one or they can say No to
errno-value, reason: errno-explanation
cancel out of this operation.
Explanation: The extended attributes of the object
could not be read. The system set the error code
FMV1581W 'object-name' was restored as 'temp-name'.
errno-value and the reason errno-explanation. If the
A reboot is required to complete the
reason errno-explanation is either "access denied" or
restore.
"permission denied", the current user does not have
Explanation: This is a system file restored and could permission to read the extended attributes of the object.
not be immediately replaced. The file will be replaced
System action: The object is skipped. Processing
during the next reboot of the operating system. It is
continues with the next object.
important to note that until the reboot occurs, the
changes will not be in effect. User response: The error is expected if the operation
tries to read extended attributes of an object that you
System action: Tivoli Storage Manager restored the
do not own or do not have access to. If the reason
file with a temporary name, and instructed the
indicates an input/output error, perform the file system
operating system to replace the original file with the
consistency check procedure and try the operation
restored file during the next boot of the operating
again. If the problem persists, contact IBM technical
system.
support for further assistance.

330 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1588W • FMV1597E

FMV1588W I/O error reading file attribute: attr-name FMV1593E Cannot open the key database.
for: file-name. errno = errno-value,
Explanation: Tivoli Storage Manager was unable to
Explanation: The attribute attr-name of the file open the keyfile that is expected to contain the server
file-name could not be retrieved. The system set the certificate for SSL communications.
error code errno-value. If the reason given is "access
System action: Processing stopped
denied," the current user does not have permission to
read the file attributes. User response: Make sure you have configured the
key database for SSL communication as described in
System action: Processing continues without backing
the documentation. If the problem persists, contact
up the specified file attribute.
Tivoli Storage Manager customer support.
User response: Correct the condition causing the
physical error.
FMV1594E The key database password is incorrect
or unavailable.
FMV1589W Unable to write extended attributes for
Explanation: The client was unable to open the
object-full-name due to errno: errno-value,
certificate key database using the stored password, or
reason: errno-explanation
the stored password could not be read.
Explanation: The extended attributes of the object
System action: Processing stops.
could not be written. The system set the error code
errno-value and the reason errno-explanation. If the User response: Make sure that you configure the key
reason is either "access denied" or "permission denied", database for SSL communication as described in the
the current user does not have permission to write the Client Installation and User's Guide. Also make sure
extended attributes of the object. that the stash file, dsmcert.sth, is readable by the
current user.
System action: Processing continues without restoring
the extended attributes.
FMV1595E Bad server certificate.
User response: The error is expected if the operation
tries to write extended attributes to an object that you Explanation: Tivoli Storage Manager was unable to
do not own or do not have access to. If the reason open SSL connection to server because of a bad
indicates an input/output error, perform the file system certificate. This error usually occurs when the server
consistency check procedure and retry the operation. If certificate cannot be verified by the client.
the problem persists, contact IBM technical support for
further assistance. System action: Processing stopped
User response: Make sure you have configured the
FMV1590W I/O error writing file attribute: attr-name key database for SSL communication as described in
for: file-name. errno = errno-value, the documentation. Make sure to import the correct
certificate from the Tivoli Storage Manager server you
Explanation: The attribute attr-name of the file are trying to connect to.
file-name could not be set. The system set the error code
errno-value. If the reason given is "access denied," the
current user does not have permission to set the file FMV1596E SSL protocol is not supported.
attributes. Explanation: SSL protocol is not supported on this
System action: Processing continues without restoring platform.
the specified file attribute. System action: Processing stopped
User response: Correct the condition causing the User response: Refer to Tivoli Storage Manager
physical error. documentation for the list of supported platforms.

FMV1592E Failed to initialize SSL protocol. FMV1597E The -pick and -deltype=all options are
Explanation: Tivoli Storage Manager was unable to not valid together.
initialize SSL protocol. Explanation: -deltype=all is used to delete an entire
System action: Processing stopped directory tree. You cannot use -pick to select individual
objects from the tree. -pick is valid only with
User response: Check for GSKit related messages in -deltype=active or -deltype=inactive.
the error log. Make sure you have configured the key
database for SSL communication as described in the System action: Processing stopped.
documentation. If the problem persists, contact Tivoli User response: Try the operation again with a valid
Storage Manager customer support. combination of options. If you want to delete an entire

Chapter 6. FMV messages 331

FMV1598E • FMV1606E

tree, use -deltype=all, but do not use -pick. If you want

FMV1602E The Domino plugin operation failed
to select which backup versions to delete, specify
because the preferences file was not
-deltype=active or -deltype=inactive, and use the -pick
found.
option. Also use -subdir=yes if you want the file
selection to include files in subdirectories of the file Explanation: The Data Protection for Lotus Domino
specification. See the client manual or command line preference file could not be found.
help for additional information.
System action: Processing ends.
User response: The Data Protection for Lotus for
FMV1598E -deltype=all is not valid for this file
Domino configuration file (default name domdsm.cfg)
specification.
could not be found. Check the error log on the client
Explanation: -deltype=all is used to delete an entire machine for more information.
directory tree. You must specify a fully wildcard
directory when using -deltype=all.
FMV1603E The Domino plugin operation failed
System action: Processing stopped. because of an internal TCP/IP error.
User response: Try the operation again with a valid Explanation: A TCP/IP error has occurred.
combination of options. If you want to delete all
System action: Processing ends.
backup versions of an entire directory tree, use
-deltype=all and a fully wildcarded file specification. If User response: Check the error log on the client
you want to delete backup versions of partially machine for more information.
qualified file names, use -deltype=inactive or
-deltype=active. Also use -subdir=yes if you want to
delete backup versions in subdirectories of the file FMV1604E The Domino plugin operation failed
specification. See the client manual or command line trying to start the dsmdomp address
help for additional information. space.
Explanation: The dsmdomp address space could not
FMV1599E Cannot load SSL runtime library. be started. This is probably an installation error.

Explanation: Tivoli Storage Manager failed to System action: Processing ends.

dynamically load SSL runtime library necessary for SSL User response: Ensure that the lotus/bin directory has
protocol a symbolic link to the tools directory for dsmdomp and
System action: Processing stopped the lotus/notes directory has a symbolic link to the
dsmdomp executable. If the problem persists, contact
User response: Make sure Tivoli Storage Manager your System Administrator for further assistance.
client is properly installed. Try to reinstall the client
software. If the problem persists, contact Tivoli Storage
Manager customer support. FMV1605E The Domino plugin operation failed
while initializing communications with
the dsmdomp address space.
FMV1600E Unable to load the Data Protection for
Lotus Domino library. Explanation: The Domino plugin communication
initialization failed.
Explanation: The Data Protection for IBM Lotus®
Domino® library could not be loaded. System action: Processing ends.

System action: Processing ends. User response: The dsmdomp address space failed
during its initialization. This is likely to be an
User response: Ensure that Domino plugin is properly installation error. Ensure that the lotus/bin directory
configured and check the error log on the client has a symbolic link to the tools directory for dsmdomp
machine for more information. and the lotus/notes directory has a symbolic link to the
dsmdomp executable. If the problem persists, contact
your System Administrator for further assistance.
FMV1601E The Domino plugin operation failed
because of an internal error.
FMV1606E The Domino plugin operation failed
Explanation: A Domino plugin internal error has
while starting up the dsmdomp address
occurred.
space.
System action: Processing ends.
Explanation: The dsmdomp address space could not
User response: Check the error log on the client be started.
machine for more information.
System action: The TDP for Domino processing stops.

332 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1607E • FMV1616E

User response: The dsmdomp address space failed persists, contact your System Administrator for further
during its initialization. This is likely to be an assistance.
installation error. Ensure that the lotus/bin directory
has a symbolic link to the tools directory for dsmdomp
FMV1611E A plugin operation failed because of an
and the lotus/notes directory has a symbolic link to the
internal error.
dsmdomp executable. Examine the file
/tmp/dsmdomp* for more information. If the problem Explanation: A plugin internal error has occurred.
persists, contact your System Administrator for further
assistance. System action: The plugin operation stops.
User response: If the error persists, run with tracing
FMV1607E A plugin found in the plugins library is enabled and contact your System Administrator and
not supported by the current level of the IBM for further assistance.
Tivoli Storage Manager client.
Explanation: The plugin is not loaded, and processing FMV1612E The Domino plugin operation failed
continues. because of a Tivoli Storage Manager
API error.
System action: The plugin is not loaded, and
processing continues. Explanation: An Tivoli Storage Manager API error
occurred .
User response: This probably is an installation error.
Ensure that the plugins directory contains valid plugin System action: Processing ends.
libraries, and that the correct level of the Tivoli Storage User response: Check error log on the client machine
Manager client has been installed. If the problem for more information.
persists, contact your System Administrator for further
assistance.
FMV1613E >Could not load the Tivoli Storage
Manager API.
FMV1608E Domino plugin operation failed with
the following message: messsage Explanation: The Tivoli Storage Manager API could
not be loaded.
Explanation: A Domino plugin operation error
occurred. System action: Processing ends.

System action: Processing ends. User response: Check error log on the client machine
for more information.
User response: Correct the error that caused the
operation to fail.
FMV1614E The Domino plugin 'Try and Buy'
license has expired.
FMV1609E Domino plugin process failed. The
following messages are associated with Explanation: The 'Try and Buy' license that was
the error. messsage. detected has expired.

Explanation: A Domino plugin operation error System action: Processing ends.

occurred. User response: This product is no longer valid for use.
System action: Processing ends. A valid license must be obtained before running the
product.
User response: Correct the error that caused the
operation to fail.
FMV1615E The Domino plugin operation failed
due to a license error.
FMV1610E The domnode option has not been
properly specified for the node Explanation: Domino plugin license verification failed.
'node_name'. System action: Processing ends.
Explanation: The domnode option has not been User response: Check the error log for further
properly specified in the dsm.sys file for the node information.
shown.
System action: Processing for this request stops. FMV1616E The Domino plugin operation failed
User response: This is likely to be an installation error. because the Lotus Domino API could
Ensure that the domnode option has been properly not be loaded.
specified for the node in question. If the problem Explanation: The Lotus Domino API could not be
loaded.

Chapter 6. FMV messages 333

FMV1617E • FMV1623W

System action: Processing ends. corrupted on the client system. This backup can not be
restored, therefore it will be deleted on the server.
User response: Ensure the Lotus Domino Server is
installed correctly. System action: The specified backup object will be
deleted on the server. Processing will continue.
FMV1617E The Domino plugin operation failed User response: None.
because of a Data Protection for Domino
API error.
FMV1621E Failed to update backup attributes on
Explanation: A Data Protection for Domino API error server for local backup for 'filespace
occurred during a Domino plugin operation. namepath-namefile-name', object id -
'object-id':'object-id' return code 'return
System action: Processing ends.
code'.
User response: For more details, view the following
Explanation: Tivoli Storage Manager failed to update
Tivoli Storage Manager error logs.
attributes for the named backup object on the server.
The API error log (dsierror.log) and the log of Data The server may not reflect correct state of the backup.
Protection for Domino activity (domdsm.log). The
System action: Processing continues.
default location of these logs is the Data Protection for
Domino installation directory. User response: Check preceding error messages in
error log for more information. Retry the operation. If
The backup-archive client error log (dsmerror.log), the
problem continues, contact your Tivoli Storage
web client error log (dsmwebcl.log), and the log of
Manager administrator.
scheduler activite (dsmsched.log). The default location
of these logs is the backup-archive installation
directory. FMV1622I Number of backup objects cleaned up
on server: 'number' number of local
snapshot resources made available
FMV1618E A Domino plugin operation is already
:'number'.
in progress. Please wait for operation to
complete. Explanation: While performing consistency check for
server's database and the local repository maintained
Explanation: A Domino plugin operation is in
on the client system, reported inconsistencies were
progress.
found. Inconsistent backups cannot be restored,
System action: The Domino plugin operation stops. therefore Tivoli Storage Manager deletes all inconsistent
backup objects and frees the space occupied in the local
User response: Please wait for the Domino plugin repository.
operation to complete before starting a new Domino
plugin operation. System action: Processing continues.
User response: Check error log for further details on
FMV1619E The IBM Tivoli Storage Manager which objects on server were deleted. If numbers look
application client cannot work with the unusually high check your configuration and if it
version of the Domino plugin you have continues, contact your Tivoli Storage Manager
installed. administrator.

Explanation: The version of the Domino plugin

currently installed on the system is older than the FMV1623W Backup of NSF DB2 database was
version used to build the IBM Tivoli Storage Manager skipped. NSF DB2 databases not
application client. supported.
System action: Processing ends. Explanation: This version of DP for Domino plugin
does not support IBM DB2 NSF databases.
User response: Install a version of the Domino plugin
at or later than the level of the IBM Tivoli Storage System action: Backup of NSF DB2 databases is
Manager application client. skipped.
User response: Exclude NSF DB2 databases from
FMV1620I Backup version for 'filespace backup.
namepath-namefile-name', object id -
'object-id':'object-id' is not consistent with
local repository. Its being deleted.
Explanation: The specified backup instance of the
named object is not valid with local repository contents.
This could happen if local repository is modified or got

334 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1624E • FMV1647E

FMV1624E 'value' is an invalid value for option FMV1629E The source v1 and target v2 virtual disks
'option' for 'command' command are of different size.
Explanation: The specified option value is not valid in Explanation: The SVC source and target virtual disks
this context. have to be of the same size.
System action: The operation was stopped System action: Process stops.
User response: Specify a valid value for the option. User response: Ensure that the source and target
Consult documentation for valid values. virtual disks are the same size.

FMV1625I Number of volumes to be FlashCopied: FMV1630E An error was returned calling an

v1 operation of the Common Interface
Model(CIM). Tivoli Storage Manager
Explanation: Number of volumes to be flashcopied.
function name : function-name Tivoli
System action: None. Storage Manager function : function-desc
Tivoli Storage Manager CIM return
User response: None. code: 0xCIM-rc Tivoli Storage Manager
file : file-name (line-number)
FMV1626E An unexpected error was encountered Explanation: An error occurred when calling a CIM
when processing a Tivoli Storage operation of the disk subsystem.
Manager operation using a hardware or
snapshot function. Tivoli Storage System action: Processing stops.
Manager function name : function-name
User response: Please see the section about the CIM
Tivoli Storage Manager function :
return codes and their descriptions in the product
function-desc Tivoli Storage Manager
publication.
return code : TSM-rc Tivoli Storage
Manager file : file-name (line-number)
FMV1631E A memory allocation error has occurred
Explanation: None.
in file filename, line number linenumber.
System action: Processing stops.
Explanation: Enough memory was not available to
User response: Contact the Tivoli Storage Manager continue processing.
administrator with the information provided in this
System action: Processing ends.
message.
User response: Ensure that your system has sufficient
real and virtual memory. Close unnecessary
FMV1627E SVC virtual disk v1 is not valid.
applications.
Explanation: The specified virtual disk is not found in
the list of virtual disks provided by the connected SVC
FMV1632I 'option name' not specified, defaults to
cluster.
'deafult value'
System action: Process stops.
Explanation: A value for the option is not spedified,
User response: Ensure that this virtual disk exists in default value wil be used.
the SVC.
System action: The operation continues using default
value for the option
FMV1628E The source v1 and target v2 virtual disks
User response: To override the default, specify a valid
are in different SVC clusters.
value for the option. Consult documentation for valid
Explanation: The SVC source and target virtual disks values.
have to be assigned to the same SVC cluster.
System action: Process stops. FMV1647E 'input spec': Invalid input specification
format.
User response: Ensure that the source and target
virtual disks are in the same SVC. Explanation: The specified input for this commmand
is invalid.
System action: The operation stops.
User response: Verify that the syntax specified with
the parameter is correct.

Chapter 6. FMV messages 335

FMV1648W • FMV1658I

FMV1648W PREViewsize option value is greater FMV1653I Updated: fshlll

than the specified stub size.
Explanation: The update operation for the object was
Explanation: The PREViewsize CLI option value successful.
specified must not be greater than the stub size for the
System action: This message is for auditing purposes
file.
only.
System action: Operation stopped. File skipped.
User response: This message is for auditing purposes
User response: Change the value of the PREViewsize only.
accordingly.
FMV1654E Failed: fshlll
FMV1649E The option 'specified-option' is
Explanation: The backup, archive, restore or retrieve
inconsistent with the option
operation for the object failed.
'other-option'.
System action: This message is for auditing purposes
Explanation: The command failed because the
only.
specified option (specified-option) can not be specified in
combination with the option (other-option), which is also User response: This message is for auditing purposes
specified. only. For information about the failure refer to the
Tivoli Storage Manager Backup-Archive Client error
System action: The command is terminated.
log.
User response: Run the command without the
specified option. Alternatively, run the command
FMV1655I Restored: fshlll
without the other option.
Explanation: The restore operation for the object was
successful.
FMV1650I Command: command-string
System action: This message is for auditing purposes
Explanation: The command string listed in the
only.
messagewas issued by the Tivoli Storage Manager
Backup-Archive client. User response: This message is for auditing purposes
only.
System action: This message is for auditing purposes
only.
FMV1656I Retrieved: fshlll
User response: This message is for auditing purposes
only. Explanation: The retrieve operation for the object was
successful.
FMV1651I Backed Up: fshlll System action: This message is for auditing purposes
only.
Explanation: The backup operation for the object was
successful. User response: This message is for auditing purposes
only.
System action: This message is for auditing purposes
only.
FMV1657I Expired: fshlll
User response: This message is for auditing purposes
only. Explanation: The active version of the object was
expired in the Tivoli Storage Manager database.
FMV1652I Archived: fshlll System action: This message is for auditing purposes
only.
Explanation: The archive operation for the object was
successful. User response: This message is for auditing purposes
only.
System action: This message is for auditing purposes
only.
FMV1658I Deleted: fshlll
User response: This message is for auditing purposes
only. Explanation: The object was deleted from the Tivoli
Storage Manager database.
System action: This message is for auditing purposes
only.

336 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1659I • FMV1668E

User response: This message is for auditing purposes

FMV1664E The snap restore for volume volname
only.
with snapshot name snapname would
destroy later snapshots that are required
FMV1659I Skipped: fshlll for other applications or for volume
clones.
Explanation: The object was skipped by the user
during backup or archive processing. Explanation: ONTAP will delete newer snapshots of a
volume when a specific snapshot is used for snap
System action: This message is for auditing purposes restore.
only.
System action: Process stops.
User response: This message is for auditing purposes
only. User response: Prior to a snap restore, ensure that
newer snapshots are not used in other applications or
in volume clones.
FMV1660I Excluded: fshlll
Explanation: The object was excluded from backup or FMV1665W Tivoli Storage Manager for ACS did not
archive processing. find any snapshots for volume volname
System action: This message is for auditing purposes on the N series filer.
only. Explanation: No snapshots were found for this
User response: This message is for auditing purposes volume on the N series filer.
only. System action: Process continues.
User response: None.
FMV1661I Unchanged: fshlll
Explanation: The object has not changed since the last FMV1666W Tivoli Storage Manager for ACS did not
incremental backup was performed and does not need find any information about the N series
to be resent. volume volname.
System action: This message is for auditing purposes Explanation: The query for information about this
only. volume did not return any data.
User response: This message is for auditing purposes System action: Process continues.
only.
User response: None.
FMV1662I Agent Node: 'agent_node' Target Node:
'target_node' FMV1667E The snapshot name snapname for volume
volname was not found in the snapshot
Explanation: Proxy nodes information. list on the N series filer.
System action: None Explanation: Snapshot identified by this name does
User response: None not exist.
System action: Process stops.
FMV1663W The option fractional reserve on volume User response: None.
vol_name was reduced to less than 100
percent.
FMV1668E The 'drive-name1' is not a local disk.
Explanation: Network Appliance strongly
recommends that when the fractional reserve is set to Explanation: The specified file system is network disk
less than 100 percent you actively monitor space or network share. Because the CLUSTERNODE option
consumption and the rate of change of data in the is set to YES, the file system cannot be backed up or
volume to ensure you do not run out of space reserved archived.
for overwrites. In that case, if you run out of overwrite
System action: Processing stops.
reserve space, writes to the active file system fail and
the host application or operating system might crash. User response: If the CLUSTERNODE option is
incorrectly set to YES, then change the option to NO
System action: Process continues.
and try the operation again. Otherwise see the client
User response: Ensure that you monitor the space manual for further information about configuring the
consumption. Consult Network Appliance for tools to Tivoli Storage Manager client to run in a cluster
monitor available space in your volumes. environment.

Chapter 6. FMV messages 337

FMV1669W • FMV1676W

FMV1669W The command subcommand command can FMV1673W Cluster service on node node name could
only be run in Windows WinPE mode. not be started. You must manually start
the service.
Explanation: The command subcommand command is
not supported on a currently running operating system. Explanation: The cluster database has been restored.
You must reboot to Windows WinPE mode to run this During the restore, the cluster service was taken offline.
command. Tivoli Storage Manager failed to restart the cluster
service.
System action: The command is not processed.
System action: Processing continues.
User response: None.
User response: You can manually start the service for
this node.
FMV1670E The file specification is not valid.
Specify a valid Network Appliance or
N-Series NFS (AIX, Linux) or CIFS FMV1674I The cluster database has been restored
(Windows) volume. but the cluster service on some nodes
could not be started. Use the Failover
Explanation: The file specification is not valid.
Cluster Management tool to manually
Incremental backup using snapshot difference using the
start the nodes.
-SNAPDIFF option can only be performed on Network
Appliance or N-Series NFS volumes on AIX and Linux, Explanation: The cluster database has been restored.
and on CIFS volumes on Windows. Do not specify During the restore, the cluster services were taken
either Network Appliance or N-Series Qtrees or a path offline except for the node being restored. Tivoli
within the Network Appliance or N-Series volume. Storage Manager failed to automatically start these
Only full volumes are supported. cluster services. You need to start them manually. The
nodes whose services failed to start are logged in the
System action: Processing stops.
client error log.
User response: Retry the incremental backup
System action: Processing continues.
operation using the -SNAPDIFF option. Specify a valid
Network Appliance or N-Series NFS volume on AIX or User response: You can manually start the cluster
Linux, or a CIFS volume on Windows. services.

FMV1671I The cluster database has been restored. FMV1675W Unable to obtain a list of cluster nodes
Restarting the cluster services on all to restart after the cluster database is
nodes. This will take a few minutes. restored. The call 'cmd' returned with
MS rc retcode. You must restart the
Explanation: After the cluster database is restored, the
cluster service on all the nodes after the
cluster service on the restoring node is in a paused
restore is finished.
state. The cluster service on other nodes were
shutdown. All services need to be restarted. If some of Explanation: Due to an error, Tivoli Storage Manager
the services cannot be started automatically, restart could not retrieve a list of nodes in the cluster to
them manually. restart. The cluster services on these nodes need to be
started manually. The client error log might contain
System action: Processing continues.
additional information depending on where the failure
User response: No action. occured.
System action: Processing continues.
FMV1672I Could not take the cluster resource
User response: Manually start the cluster services on
resource name offline. MS rc retcode. Error
all nodes.
is ignored.
Explanation: Microsoft recommends taking the cluster
FMV1676W You are doing an authoritative cluster
resources offline during an authoritative cluster
database restore. The process may seem
database restore. However, the restore can still be done
to be hang before and after the file is
if the resources cannot be taken offline. The error is
restored. This is because it may need to
ignored.
start the cluster service if it is not up
System action: Processing continues. and take all the resources offline. After
the cluster database is restored, the
User response: No action. 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.

338 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1677W • FMV1684W

This may take a few minutes. User response: None

Explanation: The restore will seem to be paused at
time because before the restore, Tivoli Storage Manager FMV1680W Function refresh incremental FlashCopy
ensures the cluster service is up on the restoring node cannot be accomplish because no
and all the resources are taken offline. After the cluster consistency group found for these
database is restored, the cluster service on the restoring volumes.
node is in a paused state. The cluster service on other
Explanation: A refresh of the incremental FlashCopy
nodes were shutdown. All services need to be retarted.
can only be done when the consistency group and the
If some of the services cannot be started automatically,
correspondent FlashCopy relation were established
you can try to restart them.
previously.
System action: Processing continues.
System action: None.
User response: No action.
User response: None.

FMV1677W Tivoli Storage Manager failed to set the

FMV1681E DSM_DIR was not set and the
disks for quick formatting because of an
ASRFILESPATH option was not
error. See the error log for more details.
specified.
The disks will be slow formatted which
will cause a slower restore process. Explanation: The ASR files can be in put in the
DSM_DIR path by default or overriden with the
Explanation: By default, Tivoli Storage Manager tries
ASRFILESPATH option. Either one is being set.
to set the QuickFormat value of the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ System action: Processing stops.
Windows NT\CurrentVersion\ASR\RestoreSession key
to perform quick formatted on all the disks. Due to an User response: Set the DSM_DIR environment
error, a slow format will be performed on the variable or specify the ASRFILESPATH option on the
re-creation of the disks. This process will cause a "RESTORE MACHINEASR" command.
slower restore process.
System action: None FMV1682W No FlashCopy relationships found in
the storage system.
User response: None
Explanation: The copy services server (mostly a CIM
Object Manager) does not have any FlashCopy relation
FMV1678E ASR path 'path': not found. objects.
Explanation: You have specified a directory that does System action: Process may stop.
not exist.
User response: This is not necessarily a message that
System action: Processing stops. implies the stop of the process.
User response: Recheck all spelling and punctuation,
particularly the placement of directory delimiters (for FMV1683E The state status of the consistency group
example, "\"). Correct the syntax if it is incorrect, then is bad to achive a valid disk backup.
retry the operation.
Explanation: Tivoli Storage Manager ACS function
monitoring will expect that the FlashCopy are in one of
FMV1679W Updating the registry to identify which the state Idle_Copied or Copying.
volumes have been restored has failed.
This does not affect the volumes that System action: Process will stop.
have already been restored. See the User response: Verify using the storage GUI the state
error log for more details. The error is of the FlashCopy. If this state was generated by an user
being ignored and processing continues. action, try to start the copy process through the storage
Explanation: After restoring the critical volumes, GUI, then re-start the Tivoli Storage Manager ACS
Tivoli Storage Manager tries to update the moniotoring fuction.
RestoredVolumes value of the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ FMV1684W Disk Full Error Accessing Subfile
Windows NT\CurrentVersion\ASR\RestoreSession key Cache: exception-name
to indicate which volumes have been restored. Due to
an error accessing the registry, the error is logged but Explanation: A disk full error occurred attempting to
processing continues. access or write to the specified subfile cache file during
a subfile incremental backup. See the client error log
System action: Processing continues. for more detailed information.

Chapter 6. FMV messages 339

FMV1685E • FMV1691I

System action: Processing continues without subfile.

FMV1688I Sparse attributes for 'file-name' cannot be
User response: None. backed up correctly because the volume
from which the file is backed up does
not support sparse files.
FMV1685E Incremental backup operation using
snapshot difference is only available for Explanation: If the volume from which a file is backed
N series/NetApp filer volumes, is not a up does not support sparse files, then the allocated
NetApp volume. ranges for the sparse file cannot be backed up. This is
true even if a file has its sparse attribute set. One
Explanation: Cannot perform NAS NFS/CIFS example where this can occur is if a sparse file is
incremental backup operation using snapshot difference created on a NAS volume, but the volume is backed up
on the mounted or mapped volume because the over CIFS, where CIFS does not support sparse files.
volume is not a N series/NetApp filer volume.
System action: The sparse attribute and allocated
System action: Processing stops. ranges for the file are not backed up. If the file is
User response: Retry the incremental backup restored, the restored file will not be sparse.
operation by specifying an entire NAS NFS or CIFS User response: No action is required if you do not
volume. need the sparse attribute and allocated ranges backed
up. If you require backup of the file's sparse attribute
FMV1686I Single Instance Store link 'file-name' will and allocated ranges, then the volume from which IBM
be restored or retrieved as a normal file. Tivoli Storage Manager backs up the file must support
sparse files.
Explanation: Tivoli Storage Manager restores Single
Instance Store (SIS) links as normal files. If the restored
version is a duplicate of of the copy in the SIS FMV1689E The registry was not updated after VSS
Common Store, then the SIS Groveler will eventually ASR restore.
recreate the SIS link. Explanation: An error occurred while updating the
System action: Tivoli Storage Manager creates normal registry after VSS Automated System Recovery (ASR).
files instead of the reparse point. Check dsmerror.log for more information.

User response: None System action: Processing stops.

User response: Ask your system administrator to
FMV1687E VSS Instant Restore operation failed. check the error log.
Please examine the Tivoli Storage
Manager client error log file FMV1690E The list of volumes passed contain pairs
(DSMERROR.LOG), the Windows which belong to different consistency
Application Event Log, the Windows groups in the scope of one single
System Event Log, and the VSS cluster.
provider log file (if applicable) for more
details. Consult the VSS provider Explanation: Tivoli Storage Manager ACS handles for
documentation for the meaning of the each operation only one consistency group per cluster
error return code. at the same time. If the set of volumes in a backup or
restore operation contain pairs that belong to different
Explanation: VSS hardware provider failed while consistency group inside one single cluster, then the
performing volume-level copy restore operation. process of the operation will be stopped.
System action: Processing stopped. System action: Process stopped.
User response: Attempt to determine the source of the User response: If you added volumes to the
error by examining the Application Client log file, the production database or to the target set, ensure that
Tivoli Storage Manager client error log file they are not in any FlashCopy relation.
(DSMERROR.LOG), the Windows Application Event
Log, the Windows System Event Log, and the VSS
provider log file, if applicable. Additional instructions FMV1691I The option 'option' that was found in the
for Windows VSS operations are located in the TSM options file 'file-name' at the line
Problem Determination Guide. Correct the problem and number: number is not supported and
retry the operation. If this error persists, contact your will be ignored by the client.
service representative.
Explanation: The specified option is valid but not
supported on the current platform and will be ignored
by the client.
System action: Processing continues.

340 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1692E • FMV1706E

User response: You can ignore the message or remove Refer to Tivoli Storage Manager documentation for
the option from the option file. more information.

FMV1692E The certificate is not trusted. FMV1696E Only root can perform this action.
Explanation: The client was unable to open SSL Explanation: User must be root to perform this action.
connection to the server because the server certificate
System action: Processing stopped.
was not trusted.
User response: Log in as root and try the operation
System action: Processing stopped
again.
User response: Make sure that you have configured
the key database for SSL communication as described
FMV1700W Database 'database' (save date=date) was
in the documentation. If the Tivoli Storage Manager
successfully recovered.
server is using a self-signed certificate, make sure that
you import the correct certificate from the server you Explanation: The specified database (which was saved
are trying to connect to. When the server is using a on the specified date) was successfuly recovered.
certificate signed by an authority, make sure that the
root certificate of the authority is imported into the System action: The specified database was recovered
client key database. with the last saved version.
User response: none.
FMV1693E The certificate validity period is
incorrect. FMV1704W Option 'option-name' can not be supplied
Explanation: The client was unable to open an SSL by application and is ignored.
connection to the server because the certificate validity Explanation: An API application supplied option. The
period is incorrect. option cannot be specified by an application. The
System action: Processing stopped option can be specified only in the dsm.sys options file.

User response: Report this to the Tivoli Storage System action: The supplied option is ignored.
Manager server administrator. The server must have Processing continues.
the correct certificate installed. User response: Correct the application configuration.

FMV1694E The certificate identity could not be FMV1705E System Writers writersname do not exist.
verified.
Explanation: These writers are an essential part of the
Explanation: Tivoli Storage Manager was unable to operating system. When they are not available the
open an SSL connection to the server because the backup will complete successfully but the data for
certificate identity could not be verified. This happens those writers will not get backed up to the IBM Tivoli
when the certificate ownership information does not Storage Manager server. This can result in the computer
match the Tivoli Storage Manager domain name or IP not booting after a restore of the system state.
address.
System action: System state backup stopped.
System action: Processing stopped
User response: Verify that these writers exist using
User response: Make sure that the server domain 'vssadmin list writers' command. Try the operation
name or the IP address (the value of the again. If the problem persists, contact your system
TCPSERVERADDRESS option) is correct. If the problem administrator or IBM Tivoli Storage Manager
persists, report it to your Tivoli Storage Manager server administrator for further help.
administrator.

FMV1706E Error creating directory ' directory'.

FMV1695E The certificate is not valid.
Explanation: The system was unable to create the
Explanation: Tivoli Storage Manager was unable to specified directory.
open an SSL connection to the server because of an
invalid certificate. The client was unable to determine System action: Processing terminates.
the exact cause of the failure. User response: Verify that the system has the
System action: Processing stopped appropriate permissions to create this directory, and
then restart the operation.
User response: Further analysis of the server
certificate, the client key database, or both, is needed.

Chapter 6. FMV messages 341

FMV1707E • FMV1714I

FMV1707E Hard link 'new-file-name' could not be FMV1710W Image backed floppy devices will not be
created for existing file 'exist-file-name'. backup with the Virtual Machine.
Microsoft Windows return code:
Explanation: The Virtual Machine create on restore
'windows-return-code' 'windows-error-text'
would fail if the floppy images was not available.
Explanation: Some system state files are hard links
System action: The Virtual Machine backup will
that point to another file. During system state restore,
continue minus the floppy device.
IBM Tivoli Storage Manager recreates the hard links for
restored system state files. If a file with the same name User response: Once the Virtual Machine is created
as the hard link already exists at the time of the restore, you may add a Floppy device to it.
IBM Tivoli Storage Manager attempts to replace the file
with the hard link. This message is issued when IBM
Tivoli Storage Manager is unable to replace an existing FMV1711W Incremental backup selected for 'VM
file with a hard link. The message includes the hard name', but a Full backup has not yet
link name, the system state file name to which the hard been performed. Performing a Full
link points and the Microsoft Windows return code backup instead.
information. The return code information indicates why Explanation: An incremental backup of the specified
the file could not be replaced. It is possible for the virtual machine was selected, but no full backup of that
operating system or applications to behave erratically if virtual machine exists; A full backup must exist before
the hard link cannot be recreated. an incremental backup can be performed.
System action: The hard link is skipped, system state System action: A full backup of the virtual machine is
restore continues. performed instead of an incremental backup.
User response: Use the Microsoft Windows return User response: None
code information provided in the message to determine
the underlying cause of the error. Based on the
underlying cause of the error and the reason you are FMV1712I Changed block tracking not supported
restoring the system state, you can choose to either for disk disk name; Performing FULL
correct the underlying cause and perform the restore backup of disk.
again, or you can attempt to manually create the hard Explanation: Changed block tracking is not enabled or
link. Because this error message represents an unusual supported for the specified disk, so a full backup of the
and unexpected condition, you should give careful disk will be performed.
consideration to the potential consequences of either
choice. The hard link can be created manually as System action: A full backup of the disk is performed.
follows: Rename the file that has the same name as the User response: None
hard link. Then use the Microsoft Windows utility
fsutil.exe as follows: FSUTIL HARDLINK CREATE
hardlinkname originalfilename FMV1713W There was a problem getting changed
block tracking information for disk disk
name; Performing FULL backup of disk.
FMV1708E Backup operation failed. Only a root
user can do this operation. Explanation: Changed block tracking is supported for
the specified disk, but there was a problem getting the
Explanation: Backups initiated by non-root users are changed block tracking information, so a full backup of
disabled by IBM Tivoli Storage Manager administrator. the disk will be performed.
System action: The operation stops. System action: A full backup of the disk is performed.
User response: Request the IBM Tivoli Storage User response: Review the error log for messages as
Manager administrator to enable non-root backups. to why the changed block tracking information could
not be obtained.
FMV1709W An ISO backed CDrom devices will not
be backup with the Virtual Machine. FMV1714I No changed extents found for disk disk
Explanation: The Virtual Machine create on restore name - skipping disk.
would fail if the ISO CDrom images was not available Explanation: No changed extents were found for the
or on-line. specified disk, so there is nothing to backup; The disk
System action: The Virtual Machine backup will will be skipped.
continue minus the CDrom device. System action: No data is backed up for the specified
User response: Once the Virtual Machine is created disk so no data has changed.
you may add a CDrom device to it. User response: None.

342 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1715E • FMV1730E

FMV1715E A filespace already exists for virtual FMV1717E A VMware vStorage web service task
machine (VM_name), but with a different failed.
virtual machine UUID (VM_UUID) than
Explanation: A VMware vCenter or ESX host web
the current virtual machine UUID
service task failed.
(VM_UUID).
System action: Processing stopped
Explanation: A virtual machine with this name was
backed up, and it has a different virtual machine UUID User response: Please check the VMware vCenter or
than the virtual machine that is backed up now. This ESX host for errors.
can occur if there are two virtual machines with the
same name that are backed up to the same Tivoli
Storage Manager data center node name. In this case, FMV1718E VMware vStorage create snapshot
the backup can not continue because the failed.
backup-archive client uses the virtual machine name to Explanation: VMware vStorage failed to create the
uniquely reference the virtual machine on the Tivoli requested snapshot.
Storage Manager server.
System action: Processing stopped
This can also occur if the virtual machine UUID
changed after a previous backup operation. This is the User response: Please check the TSM error logs and
case after the following events: VMware vCenter or ESX host for errors.
1. Virtual machine VM_1 backed up.
2. Virtual machine VM_1 is restored with a new name: FMV1719E VMware vStorage remove snapshot
VM_2. A new UUID is assigned to VM_2. failed.
3. Virtual machine VM_1 is deleted. Explanation: VMware vStorage failed to remove the
4. Virtual machine VM_2 is renamed to VM_1. requested snapshot.

System action: The backup of this virtual machine System action: Processing stopped
fails. The backup process can continue with other User response: Please check the TSM error logs and
virtual machines. VMware vCenter or ESX host for errors.
User response: If there are two or more virtual
machines with the same name in the data center FMV1729E The passed file list 'file-list' is not a valid
inventory, you can complete either of the following input file list. Pass standard file list or
actions: collection file list to the dsmrecall
v Rename the virtual machines so that all names in the command.
data center inventory are unique.
Explanation: User has passed a invalid file list type to
v Backup up virtual machines with the same name to the dsmrecall command
different Tivoli Storage Manager servers.
System action: Processing stopped
If the VM's UUID changed, run a BACKUP VM User response: pass standard file list or collection file
command with VMBACKUPUPDATEGUID option. The list to dsmrecall command.
VMBACKUPUPDATEGUID option updates the UUID
on the Tivoli Storage Manager server.
FMV1730E The IBM Tivoli Storage Manager server
query for ordering information failed.
FMV1716E A VMware vStorage web service task
timed-out. Explanation: Tape optimized recall was not able to
retrieve ordering information from the IBM Tivoli
Explanation: The TSM client timed-out waiting for Storage Manager server.
VMware vCenter or ESX host to complete a requested
web service task. Resources could be low or the system System action: Processing stopped
could be busy. User response: Check the connection to the IBM Tivoli
System action: Processing stopped Storage Manager server to see if the IBM Tivoli Storage
Manager server is available and you have the correct
User response: Please check the VMware vCenter or access rights configured.
ESX host for errors.

Chapter 6. FMV messages 343

FMV1731E • FMV1738W

Explanation: Physical RDMs are not included in

FMV1731E Tape optimized recall for file list 'file-list'
snapshots so the TSM client does not support backing
failed with rc = code.
them up.
Explanation: Tape optimized recall was not able to
System action: The virtual machine is not backed up.
retrieve ordering information from the IBM Tivoli
Storage Manager server. User response: Turn off the virtual machine and
change the RDMs to virtual mode or remove them
System action: Processing stops.
from the virtual machine. Or specify the
User response: Check all error messages above this '-vmprocessvmwithprdm=yes' option to exclude these
message to get details about the problem. disks from the backup.

FMV1732W File 'file' is from a different file system. FMV1736I Change block tracking is not supported
writing file to list of unprocessed files: for virtual machine VM.
'file-list'.
Explanation: RDM disks in physical mode, virtual
Explanation: The dsmrecall command specifies a file disks attached to shared virtual SCSI bus, and VMs
system to process. Files from other file systems are with hardware version 6 or earlier are not supported.
skipped and written into a unprocessed list.
System action: The full disk is not backed up.
System action: File is skipped and information is
User response: None.
written to a list of unprocessed files
User response: Check that all files in the input file list
FMV1737E The PRESNAPSHOTCMD command
are from the correct file system.
failed.
Explanation: The command specified by the
FMV1733I A collection file was specified 'file-list'
PRESNAPSHOTCMD option must complete
The ordering process is skipped.
successfully in order to perform the VSS snapshot
Explanation: A collection file was passed as the input backup. If the command completed with a return code
file list. Ordering is not necessary since it the file is of 0 (zero), it is considered to have completed
already ordered. Only the recall is started. successfully. If the command completed with any other
return code, it is considered to have failed. If the
System action: The ordering processed is not started,
command failed then the VSS snapshot backup is not
only recall started.
performed.
User response: No further action needed.
System action: The client does not perform the VSS
snapshot backup operation.
FMV1734W The virtual machine 'VM-name' contains
User response: Identify and repair the problem that
one or more independent disks.
caused the command to fail. If a non-zero return code
Backups are not supported in this
is normal for this command, consider wrapping the
configuration. Specify the
command in a script that always exits with a return
'-vmprocessvmwithindependent=yes'
code of zero.
option to exclude these disks from the
backup.
FMV1738W The POSTSNAPSHOTCMD command
Explanation: Independent disks are not affected by
failed.
snapshots so the IBM Tivoli Storage Manager client
does not support backing them up. Explanation: If the command specified by the
POSTSNAPSHOTCMD option completed with a
System action: The virtual machine is not backed up.
non-zero return code, the VSS snapshot backup
User response: Turn off the virtual machine and operation continues. The operation continues with a
change the disk independent mode or remove them warning-level result. The result of the
from the virtual machine. Or specify the POSTSNAPSHOTCMD command does not supersede a
'-vmprocessvmwithindependent=yes' option to exclude higher result from the VSS snapshot backup command.
these disks from the backup. For example, if the VSS snapshot backup command
completed with code 12, a lower return code from the
POSTSNAPSHOTCMD command does not alter the
FMV1735W The virtual machine 'VM-name' contains return code.
one or more physical Raw Device
Mappings (RDMs). Backups are not System action: The VSS snapshot backup continues,
supported in this configuration. Specify but with a warning return code of at least 8.
the '-vmprocessvmwithprdm=yes' option
User response: Identify and repair the problem that
to exclude these disks from the backup.

344 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1739E • FMV1747W

caused the command to fail. Consider wrapping the

FMV1744E One or more of the snapshots(volumes)
command in a script that always exits with a return
needed for the restore operation were
code of zero.
not found. See dsmerror.log for further
details.
FMV1739E Restore of a system drive is not
Explanation: One or more of the snapshots needed for
permitted.
restore were not found on the system.
Explanation: The drive to which you are restoring
System action: Processing stops
contains the operating system.
User response: See the dsmerror.log file for further
System action: Processing stops.
details.
User response: Try the operation again without
specifying a system drive.
FMV1745I The virtual machine to restore has one
or more distributed port groups. Further
FMV1740W Unable to read ACLs for object: configuration might be necessary to
file_system path name. Check dsmerror.log select a port number after the restore is
for more information. complete.

Explanation: The ACLs of the object are not read. Explanation: The virtual machine was saved with one
or more NIC cards backed by distributed port groups.
System action: The object is skipped. Processing Due to conflicts on restore the port number(s) were not
continues with the next object. saved.
User response: Examine the client error log for System action: The restore continues.
additional messages that might indicate the reason for
the problem. Try to follow the suggested corrective User response: Edit the virtual machine settings and
actions (if any) and try the operation again. select a port if needed.

FMV1741W Unable to read extended attributes for FMV1746E No available LUNs were found.
file_system path name. Check dsmerror.log Confirm that the storage adapters are
for more information. configured correctly on the host and that
the LUNs are not mapped to another
Explanation: The extended attributes of the object are virtual machine.
not read.
Explanation: The virtual machine was stored with a
System action: The object is skipped. Processing Raw Device Mappings disk backed by a LUN. The
continues with the next object. required LUN is missing or still mapped to another
User response: Examine the client error log for virtual machine.
additional messages that might indicate the reason for System action: The virtual machine cannot be
the problem. Follow the suggested corrective actions (if restored.
any) and try the operation again.
User response: Confirm that the Storage Adapters are
configured correctly on the host and that the LUNs are
FMV1742E Expose Snapshot failed for backup not mapped to another virtual machine.
'backup-name'.
Explanation: Expose snapshot failed. FMV1747W The virtual machine contains one or
System action: Processing stops more Version 2 Raw Device Mappings
(RDMs). Backups are not supported in
User response: See the dsmerror.log file for further this configuration.
details.
Explanation: Version 2 RDMs are not supported.

FMV1743E Unexpose snapshot failed for backup System action: The virtual machine is not backed up.
'backup-name'. User response: Turn off the virtual machine and
Explanation: Unexpose snapshot failed. remove the version 2 RDMs from the virtual machine.

System action: Processing stops

User response: See the dsmerror.log file for further
details.

Chapter 6. FMV messages 345

FMV1748E • FMV1754E

or an account that has access to the file system must be

FMV1748E The virtual machine was stored with a
used. If the file system does not exist, then remove or
Raw Device Mappings disk backed by a
correct the file system specification.
LUN. The required LUN is missing or
still mapped to another virtual machine:
LUN UUID lun. FMV1752E The file system can not be accessed.
Explanation: The virtual machine was stored with a Explanation: The client is unable to access the file
Raw Device Mappings disk backed by a LUN. The system. Two common reasons for this are the account
required LUN is missing or still mapped to another under which the client is running does not have access
virtual machine. to the root of the file system, or the file system does
not exist.
System action: The virtual machine cannot be
restored. System action: The inaccessible file system is ignored.
User response: Find the required LUN and make it User response: Check the error log for additional
available to the virtual machine. messages that might yield additional information about
the problem that prevents access to the file system.
Correct the problem, then retry the operation. If the
FMV1749W Object 'filespace-namehl-namell-name' was
account does not have access to the file system, then
backed up with invalid file system type
either the system administrator needs to grant access,
attribute.
or an account that has access to the file system must be
Explanation: File system type is used by the client to used. If the file system does not exist, then remove or
determine if an object name is case sensitive or not. correct the file system specification.
Wrong file system type may result in incorrect sort
order of the server tree for case sensitive file systems.
FMV1753E File space 'filespace name' was backed up
Finally some unchanged files may expire and then
by an older client version, and cannot
re-backed up during full incremental backup.
be restored with this client version. The
System action: Processing continues. file space will be skipped.
User response: It is recommended to rename the Explanation: The backup set format in earlier client
correspondent filespace on TSM server and do the full versions for SYSTEM STATE and SYSTEM SERVICES is
incremental backup again. incompatible with the current client version. Those file
spaces will be skipped. The restore might appear to
pause while the client skips past the objects in those
FMV1750I Volume mount point 'volumemountpoint'
file spaces. Other remaining file space data will be
is mounted to volume 'volume'. Using
restored.
snapshot volume for 'volume' to backup.
System action: Objects in this file space are skipped.
Explanation: The volume mount point resolved to a
Other remaining file space data will be restored.
volume that has been snapped. The same snapshot
volume will be used. User response: Restore this specific file space in the
backupset with a prior level client.
System action: Processing continues.
User response: None.
FMV1754E File space 'filespace name' cannot be
restored when ASNODENAME option
FMV1751E Error processing 'filespace name': The file is in affect. The file space will be
system can not be accessed. skipped.

Explanation: The client is unable to access the file Explanation: System state data of another node should
system. Two common reasons for this are the account not be restored to a different node. Those file spaces
under which the client is running does not have access will be skipped. The restore might appear to pause
to the root of the file system, or the file system does while the client skips past the objects in those file
not exist. spaces. Other remaining file space data will be restored.

System action: The inaccessible file system is skipped. System action: Objects in this file space are skipped.
Processing continues with the next file system. Other remaining file space data will be restored.

User response: Check the error log for additional User response: Remove ASNODENAME option before
messages that might yield additional information about restoring this specific file space in the backupset or use
the problem that prevents access to the file system. the node name that was used to backup system state
Correct the problem, then retry the operation. If the data to restore.
account does not have access to the file system, then
either the system administrator needs to grant access,

346 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1755W • FMV1763W

User response: None.

FMV1755W An error communicating with Active
Directory has occured. USEDIRECTORY
option will be ignored and processing FMV1759W The Journal for 'backup-specification' has
will continue. been reset: The policy set was updated
since the last backup completed.
Explanation: Tivoli Storage Manager attempted to
query Active Directory for Tivoli Storage Manager Explanation: The client has reset the journal for the
Server parameters but an error has occured. This could specified file system because the node policy set was
be caused by Active Directory or the Tivoli Storage updated since the last backup completed.
Manager Server's setup.
System action: The journal is reset, the current backup
System action: Tivoli Storage Manager will ignore the won't use the journal, and the journal won't be
USEDIRECTORY option and continue with client available for backup until a full incremental backup
processing. successfully completes.
User response: Make sure your computer is properly User response: None.
set up to the domain with Active Directory. Also, make
sure your Tivoli Storage Manager Administrator has
properly configured the Tivoli Storage Manager Server FMV1760I Journal for 'backup-specification' enabled
for your node. for node 'nodename' and server
'servername'

FMV1756W The Journal for 'backup-specification' has Explanation: The journal for the specified file system
been reset: The server filespace was is now valid and will be used by the next full
deleted since the last backup completed. incremental backup by the specified TSM node and
server.
Explanation: The client has reset the journal because
the corresponding server filespace was deleted since System action: The next full incremental backup of
the last backup completed. the file system will use the journal.

System action: The journal is reset, the current backup User response: None.
won't use the journal, and the journal won't be
available for backup until a full incremental backup FMV1761I Journal for 'backup-specification' will be
successfully completes. enabled upon successful completion of
User response: None. the backup.
Explanation: An active but invalid journal is present
FMV1757W The Journal for 'backup-specification' has for the file system being backed up. Once the backup
been reset: The server filespace was successfully completes the journal will available for use
deleted since the last backup completed. by the next full incremental backup of the file system
with the same TSM node and server.
Explanation: The client has reset the journal because
the corresponding server filespace was deleted since System action: None.
the last backup completed. User response: None.
System action: The journal is reset, the current backup
won't use the journal, and the journal won't be FMV1763W Unable to unmount snapshot mount
available for backup until a full incremental backup point snapshot mountpoint during cleanup
successfully completes. of snapshot 'snapshot' of volume 'volume'.
User response: None. Error is 'error'. Operation will continue.
Please manually unmount, remove the
snapshot mount point directory and
FMV1758W The Journal for 'backup-specification' has delete the snapshot after backup is
been reset: The server filespace was completed.
deleted since the last backup completed.
Explanation: During the termination phase of TSM
Explanation: The client has reset the journal because client operation, it was not possible to unmount the
the corresponding server filespace was deleted since snapshot for some reason. However, TSM operation
the last backup completed. was completed successfully.
System action: The journal is reset, the current backup System action: Processing continues, and the unmount
won't use the journal, and the journal won't be error is ignored.
available for backup until a full incremental backup
successfully completes. User response: Please manually cleanup the snapshots
as follows: Query the snapshot: snapshot -q -c: <source

Chapter 6. FMV messages 347

FMV1764W • FMV1766W

FS>. Snapshot name will be of the format: issued in the order of oldest snapshot first, next oldest
tsmxxxxxxxxxx. Check if it is mounted: df -k | grep snapshot second and so on. If there are other processes
tsmxxxxxxxxxx. Unmount the snapshot: umount -f using older snapshots for the same filesystem, it fails
tsmxxxxxxxxxx. Remove snapshot mount point: rmdir the delete request. Also, TSM only deletes snapshots
tsmxxxxxxxxxx. Delete the snapshot: snapshot -d that was created by one of its processes. It will not
/dev/tsmxxxxxxxxxx. If snapshot delete fails with delete older snapshots created by other applications or
"Device Busy" or some other error, unmount the users. In this case, the user will have to manually
snapshot source filesystem: umount -f <source FS>. delete all the older snapshots so that the next TSM
Retry snapshot delete: snapshot -d command can complete successfully.
/dev/tsmxxxxxxxxxx. Check if any logical volumes are
System action: Processing continues, and the snapshot
remaining: ls -l /dev/tsm*. Remove any remaining
delete error is ignored.
logical volumes: rmlv -f tsmxxxxxxxxxx. Remount
source file system, if previously unmounted: mount User response: Please manually cleanup the snapshots
<source FS>. as follows: Query the snapshot: snapshot -q -c: <source
FS>. Snapshot name will be of the format:
tsmxxxxxxxxxx. Check if it is mounted: df -k | grep
FMV1764W Unable to remove the snapshot mount
tsmxxxxxxxxxx. Unmount the snapshot: umount -f
point directory snapshot mountpoint
tsmxxxxxxxxxx. Remove snapshot mount point: rmdir
during cleanup of snapshot 'snapshot' of
tsmxxxxxxxxxx. Delete the snapshot: snapshot -d
volume 'volume'. Error is 'error'.
/dev/tsmxxxxxxxxxx. If snapshot delete fails with
Operation will continue. Please
"Device Busy" or some other error, unmount the
manually remove the snapshot mount
snapshot source filesystem: umount -f <source FS>.
directory and delete the snapshot after
Retry snapshot delete: snapshot -d
backup is completed.
/dev/tsmxxxxxxxxxx. Check if any logical volumes are
Explanation: During the termination phase of TSM remaining: ls -l /dev/tsm*. Remove any remaining
client operation, it was not possible to remove the logical volumes: rmlv -f tsmxxxxxxxxxx. Remount
mount point directory for the snapshot for some source file system, if previously unmounted: mount
reason. However, TSM operation was completed <source FS>.
successfully.
System action: Processing continues, and the rmdir FMV1766W Unable to remove the snapshot logical
error is ignored. volume during cleanup of snapshot
'snapshot' of volume 'volume'. Error is
User response: Please manually cleanup the snapshots
'error'. Operation will continue. Please
as follows: Query the snapshot: snapshot -q -c: <source
manually remove the snapshot logical
FS>. Snapshot name will be of the format:
volume after backup is completed.
tsmxxxxxxxxxx. Check if it is mounted: df -k | grep
tsmxxxxxxxxxx. Unmount the snapshot: umount -f Explanation: During the termination phase of TSM
tsmxxxxxxxxxx. Remove snapshot mount point: rmdir client operation, it was not possible to remove the
tsmxxxxxxxxxx. Delete the snapshot: snapshot -d snapshot logical volume for some reason. However,
/dev/tsmxxxxxxxxxx. If snapshot delete fails with TSM operation was completed successfully.
"Device Busy" or some other error, unmount the
System action: Processing continues, and the snapshot
snapshot source filesystem: umount -f <source FS>.
logical volume remove error is ignored.
Retry snapshot delete: snapshot -d
/dev/tsmxxxxxxxxxx. Check if any logical volumes are User response: Please manually cleanup the snapshots
remaining: ls -l /dev/tsm*. Remove any remaining as follows: Query the snapshot: snapshot -q -c: <source
logical volumes: rmlv -f tsmxxxxxxxxxx. Remount FS>. Snapshot name will be of the format:
source file system, if previously unmounted: mount tsmxxxxxxxxxx. Check if it is mounted: df -k | grep
<source FS>. tsmxxxxxxxxxx. Unmount the snapshot: umount -f
tsmxxxxxxxxxx. Remove snapshot mount point: rmdir
tsmxxxxxxxxxx. Delete the snapshot: snapshot -d
FMV1765W Unable to delete the snapshot during
/dev/tsmxxxxxxxxxx. If snapshot delete fails with
cleanup of snapshot 'snapshot' of volume
"Device Busy" or some other error, unmount the
'volume'. Error is 'error'. Operation will
snapshot source filesystem: umount -f <source FS>.
continue. Please manually delete the
Retry snapshot delete: snapshot -d
snapshot after backup is completed.
/dev/tsmxxxxxxxxxx. Check if any logical volumes are
Explanation: During TSM client operation, it was not remaining: ls -l /dev/tsm*. Remove any remaining
possible to delete the snapshot for some reason. logical volumes: rmlv -f tsmxxxxxxxxxx. Remount
However, TSM operation was completed successfully. source file system, if previously unmounted: mount
One of the reasons that the snapshot delete failed <source FS>.
maybe due to the fact that AIX JFS2 expects the
snapshot delete requests for a given filesystem to be

348 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1767E • FMV1774W

FMV1767E Unable to create a snapshot logical FMV1771W The system state filespace 'filespace name'
volume using command: 'cmd'. Error is cannot be restored to a different
'error'. Please ensure that the volume location.
group has sufficient free partitions to
Explanation: The system state file space cannot be
fulfill the allocation request.
restored to a different location. This file space is
Explanation: During the initialization phase of TSM skipped.
client operation, it was not possible to create a logical
System action: Objects in the system state file space
volume for the snapshot.
are skipped. Other remaining file spaces are restored.
System action: Processing continues, and the create The restore might appear to pause while the client
snapshot logical volume error is ignored. TSM skips past the objects in this file space.
operation will be performed without the snapshot.
User response: Restore system state to its original
User response: Please ensure that the volume group location.
has sufficient free partitions to fulfill the mklv
allocation reuest and retry the operation.
FMV1772E Error loading the snapshot plugin. The
plugin might not be installed.
FMV1768E TSM was unable to find space for a new
Explanation: The snapshot plugin could not be
snapshot. Tivoli Storage Manager
loaded, possibly because the plugin is not installed.
function name : function-name Tivoli
Storage Manager function : function-desc System action: The snapshot backup is stopped.
Tivoli Storage Manager return code :
TSM-rc Tivoli Storage Manager file : User response: On Linux 86/86_64 platform, install
file-name (line-number) the TIVsm-BAhdw package if it is not already installed.
Try the operation again. On AIX platform, install the
Explanation: None. hdw and snphdw filesets if they are not already
installed. Try the operation again.
System action: Processing stops.
User response: Previous backups may still be
FMV1773W The virtual machine 'VM-name' contains
pending. If problem persists contact the Tivoli Storage
one or more independent disks and
Manager administrator with the information provided
these disks are excluded from the VM
in this message.
backup.
Explanation: You cannot perform a shapshot of
FMV1769E NetApp file server 'server-name' at Data
independent disks. Specify the option
ONTAP version
'-vmprocessvmwithindependent=yes' to skip these
'version.modification.submodification' is not
disks.
supported for performing incremental
backups using snapshot difference. System action: The virtual machine independent disks
will not be backed up.
Explanation: Incremental backup using Snapshot
difference requires Data ONTAP V7.3 or later. However, User response: None.
if you are upgrading from Data ONTAP V7.3.3 or later
to V8.0, you will lose snapshot difference support for
unicode file names. Upgrade to Data ONTAP V8.1 or FMV1774W The virtual machine 'VM-name' contains
later. one or more physical Raw Device
Mappings (RDM) disks and these disks
System action: Processing stops. are excluded from the VM backup.
User response: Upgrade the file server to a supported Explanation: You cannot perform a shapshot of
level of Data ONTAP, then retry the operation. physical RDM disks. Specify the option
'-vmprocessvmwithprdm=yes' to skip these disks.
FMV1770E Unable to resolve address 'tcpip address'. System action: The virtual machine physical RDM
Error = error code, 'error message' disks are not backed up.
Explanation: The system was not able to get the User response: None.
TCP/IP v6 address.
System action: Processing stopped
User response: Verify the address shown is a TCP/IP
v6 address and can be resolved with ping or ping6.

Chapter 6. FMV messages 349

FMV1780E • FMV1794I

User response: After the virtual machine has been

FMV1780E writer-name failed to initialize and
restored a new NIC card can be added.
subscribe to VSS.
Explanation: IBM Tivoli Storage Manager encountered
FMV1788I The target ESX host is missing the
an error while creating writer-name under control of the
required distributed virtual port group,
Windows Volume Shadow Copy Service (VSS).
the virtual machine NIC cannot be
Examine the IBM Tivoli Storage Manager error log and
restored.
Applications Event Log for additional information
about this error. Explanation: The virtual machine NIC was backed by
a distributed virtual port group but the target ESX host
System action: Processing ends.
is missing this port group.
User response: Try the operation again. If the error
System action: The virtual machine can be restored
persists, examine the IBM Tivoli Storage Manager error
but the NIC cannot be restored.
log and Windows event log for information related to
this error. User response: After the virtual machine has been
restored a new NIC card can be added.
Restart the Windows Volume Shadow Copy Service
(VSS), and try the operation again.
FMV1789I No Ddistributed virtual port group were
In some cases, it is necessary to restart the machine to
found on the target ESX host. The
clear the VSS error state.
virtual machine NIC cannot be restored.
Explanation: The virtual machine NIC was backed by
FMV1782E writer-name failed to be stopped.
a distributed virtual port group but the target ESX host
Explanation: IBM Tivoli Storage Manager encountered has no port group available.
an error while stopping writer-name. Examine the IBM
System action: The virtual machine can be restored
Tivoli Storage Manager error log and Applications
but the NIC cannot be restored.
Event Log for additional information about this error.
User response: After the virtual machine has been
System action: Processing ends.
restored a new NIC card can be added.
User response: Try the operation again. If the error
persists, examine the IBM Tivoli Storage Manager error
FMV1790E Volume 'volname' cannot be backed up
log and Windows event log for information related to
because 'nosnapdir=on' is set on the
this error.
filer.
Restart the Windows Volume Shadow Copy Service
Explanation: This message is issued when option
(VSS), then try the operation again.
'nosnapdir=on' is in set for the volume indicated in the
In some cases, it is necessary to retart the machine to message. When this option is set, the volume snapshots
clear the VSS error state. are hidden and thus cannot be backed up.
System action: The volume indicated in the message
FMV1784E Incremental by snapshot difference is not backed up. Processing continues with the next
cannot be performed on 'volume-name' as volume.
it is a vFiler volume.
User response: To back up the volume, change the
Explanation: Snapshot difference incremental backup volume on the filer: Set option 'nosnapdir=off'. Then try
is not supported on vFiler volumes. the backup operation for this volume again. If the
volume is not backed up, remove it from the
System action: Processing stops.
backup-archive client DOMAIN setting.
User response: Perform snapshot difference
incremental backup on normal NetApp/N-Series
FMV1794I The option 'cifs.enable_share_browsing
volumes only.
= off' is set on the filer 'filerName'.
Explanation: This message is issued when the option
FMV1787I The virtual machine NIC is backed by a
'cifs.enable_share_browsing = off' is set on the NAS
distributed virtual port group but it is
filer indicated in the message.
missing the portgroupKey attribute, The
NIC cannot be restored. System action: Processing continues.
Explanation: The virtual machine NIC is missing the User response: Set option 'cifs.enable_share_browsing
required portgroupKey attribute. = on'. Then try the snapshot difference backup
operation again.
System action: The virtual machine can be restored
but the NIC cannot be restored.

350 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1795I • FMV1800W

User response: Contact your system administrator for

FMV1795I Operation will continue without using
more information.
snapshot provider, because file system
'volname' does not have write
permissions. FMV1798W An error occurred while accessing
encrypted data of the object 'object-name',
Explanation: The source file system for a snapshot
skipping object. Windows system error
should be read-write as by definition a snapshot is a
code error, reason 'error-reason'
point-in-time snapshot of changing file system.
Snapshot creation updates the file system superblock Explanation: An error occurred while processing
which requires the file system to be read-write encrypted data of the object. The error information
captured indicates the reason for the failure. This
System action: Processing continues without using
information can be used to diagnose the problem.
snapshot provider.
System action: Object skipped.
User response: If the volume needs to be backed up
via snapshot provider, change its permissions to User response: Contact your system administrator for
read-write. more information.

FMV1796I The short name for 'fullpath-name' could FMV1799I The last access date for 'fullpath-name'
not be set to original short name could not be reset because the file is
'file-name': Windows function 'func-name' read-only.
failed with return code return-code,
reason: 'error text' Explanation: Option PRESERVELASTACCESSDATE
YES is in effect, but the Tivoli Storage Manager client
Explanation: The client cannot set the short name for was unable to reset the last access date for the specified
the specified object. This is usually because the short file because the file's "read only" attribute is enabled.
name is already in use by another object located in the The client cannot reset the last access date for "read
same directory. Another possible reason is that the only" files.
account under which the client is running does not
have the SE_RESTORE_NAME privilege. System action: The last access date for the specified
file is not reset. Otherwise processing continues.
System action: The short name for the specified object
is not set. The object will retain the default short name. User response: This message is informational and can
Otherwise processing continues. be safely ignored. You might want to turn off the "read
only" attribute for the file so that subsequent backups
User response: This message is informational and can can reset the last access date. Before turning off the
be safely ignored. If you require that the object be attribute, you should verify that doing so will not
restored with its original short name, you will need to impact the integrity of the file or the applications that
move or delete the conflicting object. From an use the file. You should also make sure that turning off
operating system command prompt, change to the the attribute will not conflict with the file management
directory that contains the object you want to restore. policies of your organization.
Then use the \"dir /x\" command to identify the
conflicting object. Also make sure that you have the
SE_RESTORE_NAME privilege. If you need assistance, FMV1800W The last access date for 'fullpath-name'
see your system administrator. After the conflict has could not be reset: function 'func-name'
been resolved, try to restore the file again. failed with return code return-code
Explanation: Option PRESERVELASTACCESSDATE
FMV1797E Function function-name received an YES is in effect, but the Tivoli Storage Manager client
unexpected error from the Microsoft API was unable to reset the last access date for the specified
MS-function-name: rc=error while file. The message includes the name of the function that
attempting to access the object failed and the return code from that function.
'object-name'. Error occurred in file System action: The last access date for the specified
file-name (line-number). file is not reset. Otherwise processing continues.
Explanation: An error occurred while processing the User response: If the problem is reproducible, obtain a
'object-name'. The error code indicates the reason for the SERVICE trace that captures an instance of this
failure. This information can be used to diagnose the problem. Run the QUERY SYSTEMINFO command and
problem. collect the dsminfo.txt file. Contact IBM support and
System action: The Tivoli Storage Manager client may report the exact text of this error message. Be sure to
or may not fail the operation, depending on the error provide support with the dsminfo.txt and dsmerror.log
code. files and (if available) the SERVICE trace.

Chapter 6. FMV messages 351

FMV1801E • FMV1808E

FMV1801E Unable to register the new ID with FMV1805E Unable to restore symbolic link
server. 'file-name'.
Explanation: The reasons of this problem can be lack Explanation: The client operating system is not able to
of client system memory or server protocol error. The create a symbolic link because the link points to a
Tivoli Storage Manager activity log might contain a filename that is not given.
corresponding error message with further information
System action: Processing continues.
about the cause.
User response: Try the restore on a different operating
System action: The new ID is not registered with the
system.
server.
User response: Please check your network connection
FMV1806W Size exceeded the maximum file size
and try again after time. If the error appears again,
limit on your system for 'filespace
please contact your client machine administrator.
namepath-namefile-name' of 'file-size'.
Explanation: You tried to restore or retrieve a file that
FMV1802E Incremental backup of 'file-name'
has exceeded the maximum file size limitation on your
finished with failCount failure(s)
system.
Explanation: This message is issued after completion
System action: Tivoli Storage Manager cannot restore
of an incremental backup operation for the named file
or retrieve the file.
specification when one or more objects in that file
specification could not be backed up. User response: Restore or retrieve this file on a system
that supports the file size. See your system
System action: Processing continues.
administrator.
User response: Examine the client error log for
additional messages that indicate the reasons that each
FMV1807E Unable to recall file from server due to
failed object could not be backed up. Take any
error from recall daemon.
corrective action as suggested by the messages.
Explanation: Unable to recall file. The recall daemon
reported an error while trying to recall a file. Look in
FMV1803E Archive processing of 'file-space name'
the recall daemon’s error log for more information. This
finished with failures.
can happen if the server is down, the connection is
Explanation: This message is issued after completion broken, or the file is missing on the server. It is also
of an archive operation for the named file specification possible that the migration server in the system option
when one or more objects in that file specification file has been changed to a different server. The recall
could not be archived. daemon does not check the system option file for
changes once it has started.
System action: Processing continues.
System action: File skipped.
User response: Examine the client error log for
additional messages that indicate the reasons that each User response: See if the server is up, and retry. If the
failed object could not be archived. Take corrective problem still exists, look in the error log. Also have the
action as suggested by the messages. workstation administrator run dsmreconcile against the
file system and see if the file shows up in the
.SpaceMan/orphan.stubs file. If system option file has
FMV1804E Selective Backup processing of 'file-space
been changed, stop all recall daemons and restart the
name' finished with failures.
master recall daemon to pick up the changes.
Explanation: This message is issued after completion
of a selective backup operation for the named file
FMV1808E The Logical Volume Snapshot Agent is
specification when one or more objects in that file
not at the correct level. It is possible
specification could not be backed up.
that the Client was upgraded to a newer
System action: Processing continues. level but the LVSA driver was not
updated at the same time. Use the Setup
User response: Examine the client error log for Wizard to configure either Online Image
additional messages that indicate the reasons that each or Open File support and choose Update
failed object could not be backed up. Take any the Logical Volume Snapshot Agent.
corrective action suggested by those messages.
Explanation: The selected operation requires the
current level of the Logical Volume Snapshot Agent.
Use the Setup Wizard to update the LVSA.

352 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1809W • FMV1815E

System action: The selected operation is not

FMV1811S Tivoli Storage Manager session could
performed.
not be reestablished.
User response: Retry the operation after updating the
Explanation: The session with the server has been
Logical Volume Snapshot Agent.
lost. Attempts to reestablish the session were
unsuccessful. Possible causes include, but are not
FMV1809W A session with the Tivoli Storage limited to the following:
Manager server has been disconnected. v The server has been halted.
An attempt will be made to reestablish
v The network connection to the server is down.
the connection.
v The communication program that Tivoli Storage
Explanation: This message is issued after the session Manager is interacting with has encountered some
with the Tivoli Storage Manager server is unexpectedly problem.
lost. Some possible reasons that this message might be
issued: - There is a problem with the network. - The System action: Processing is stopped.
Tivoli Storage Manager server was shut down. - The User response: Check network connection to the
Tivoli Storage Manager server administrator cancelled server. Insure that the Tivoli Storage Manager server is
the client session. running. Insure that the communication program
System action: The client will try to reestablish a underlying Tivoli Storage Manager is working properly.
connection with the server. If the Tivoli Storage
Manager server administrator cancelled the session, FMV1813E Image Backup processing of
then the attempt to reestablish the connection will fail 'filespace-name' finished with failures.
and message FMV1369E will be issued. If the attempt
to reestablish the connection is successful, then Explanation: The image backup operation failed. This
processing will continue. If the attempt to reestablish message is usually preceded by other messages
the connection fails, then the client will continue to try indicating the nature of the failure.
to reestablish a connection according to the System action: The failing file space is skipped and
COMMRESTARTDURATION and processing continues.
COMMRESTARTINTERVAL client option settings.
User response: Examine the messages preceding this
User response: If the session was cancelled by the message and the Tivoli Storage Manager Client error
Tivoli Storage Manager server administrator and you log for more specific indications about the problem. A
do not know why, or if the client is unable to common cause is that a tape could not be mounted on
reestablish a session with the Tivoli Storage Manager the Tivoli Storage Manager server, perhaps due to an
server, then contact your Tivoli Storage Manager server insufficient number of mount points. If there is a
administrator for further information. Frequent problem with the server, contact your System
occurrences of the FMV1809W message can indicate a Administrator for further assistance.
problem with the network. If this message is repeatedly
found in the dsmerror.log, investigate possible
networking trouble, such as a failing network interface FMV1814E Unable to start the scheduled event
card or router problem. One common problem is the 'event-name'
media speed of the network adaptors: If the network
Explanation: The scheduled event is no longer valid
adaptors are set to "auto-negotiate", try changing them
on the server. Either the window has elapsed or the
to "100%% full duplex". If the problem persists, then as
schedule has been deleted.
a temporary measure ask your Tivoli Storage Manager
server administrator increase the COMMTIMEOUT and System action: The client scheduler queries the server
IDLETIMEOUT option settings on the Tivoli Storage to obtain the next scheduled event.
Manager server. This might reduce the frequency of
User response: If the problem continues, contact your
this message.
system administrator to correct the problem on the
server.
FMV1810I A session with the Tivoli Storage
Manager server has been reestablished.
FMV1815E Either the window has elapsed or the
Explanation: The session with the server has been schedule has been deleted
reestablished after a connection failure. This message is
Explanation: Scheduled event was no longer valid on
usually preceded by message FMV1809W.
the server.
System action: Processing will continue.
System action: The client scheduler queries the server
User response: None. This message is informational to obtain the next scheduled event.
only.
User response: If the problem continues, see your

Chapter 6. FMV messages 353

FMV1816E • FMV1823E

system administrator to correct the problem on the

FMV1820E Command line options must be
server.
preceded by a '-'
Explanation: An option was specified without a '–'
FMV1816E Invalid scheduling mode
delimiter.
Explanation: The mode entered for the scheduled
System action: Processing stopped.
event was not correct.
User response: Enter the command again with a dash
System action: Event does not occur.
preceding each option.
User response: Enter the correct scheduling mode and
retry the operation.
FMV1821E Unable to start POSTSCHEDULECMD/
PRESCHEDULECMD 'command'
FMV1817E Schedule function can only be run by a
Explanation: The requested action required a new
Tivoli Storage Manager authorized user.
process to be created. Either an option or a schedule
Explanation: An attempt to use the schedule function “action” that requested an operating system command
failed because of improper authority. to be executed was entered.

System action: Processing stopped. System action: Request is ignored.

User response: See the Tivoli Storage Manager User response: Remove the request from the options
authorized user for schedule function information. file or the schedule defined on the server.

FMV1818E The SCHEDULE command is not FMV1822E Too many objects were selected for
allowed in LOOP (interactive) mode. restore. Please select less than
max_objects objects
Explanation: The SCHEDULE command may only be
given on the inital command line. Enter the HELP Explanation: The restore cannot be performed,
SCHED command for a complete description of the because too many objects were selected.
SCHEDULE command.
System action: The restore is not performed.
System action: The client does not execute any
User response: Retry the operation after reducing the
scheduled events.
number of objects selected.
User response: Start the scheduler from the OS
prompt. For example: dsmc schedule Windows clients
FMV1823E The TESTFLAGS or TRACEFLAGS
can also use the client scheduler service. Read the client
option specifies unknown flag name
manual for information on how to use the SCHEDULE
'keyword' or the value supplied is invalid
command and how to use the Tivoli Storage Manager
for the named keyword.
client scheduler features.
Explanation: Either the testflag or traceflag name is
incorrectly spelled, or the value supplied for that flag is
FMV1819E The Tivoli Storage Manager server was
not valid.
unable to register the address for this
node. System action: If the TESTFLAGS or TRACEFLAGS
option was specified in the client options file or on the
Explanation: This is a rare situation, and is usually an
command line during client initialization, the the client
indication of a problem with the Tivoli Storage
program does not start. If the option was specified
Manager server.
from the command line client while running in LOOP
System action: Processing stopped. (interactive) mode, then the operation does not run.

User response: Check the error log for any other User response: Correct the TESTFLAGS or
messages that might indicate a reason for the failure. TRACEFLAGS flag name or correct the value specified
Ask your Tivoli Storage Manager server administrator for the TESTFLAG keyword shown in the message.
to check the Tivoli Storage Manager server activity log These options are typically used at the direction of IBM
for any messages that might indicate a problem on the technical support or as specified in the Tivoli Storage
server. Try to correct any indicated problems, then try Manager Problem Determination Guide. If you are not
the operation again. If the problem persists, contact sure which flag names to use, review the Tivoli Storage
IBM technical support for further assistance. Manager Problem Determination Guide for additional
information or contact IBM technical support for
further assistance.

354 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1824E • FMV1835E

access is available and has sufficient space for the

FMV1824E Invalid trace file name (name too long).
tracefile. Retry the command.
Explanation: A TRACEFILE option in the preferences
files used a file name that is too long.
FMV1831E Password expired. The administrator for
System action: Client program did not initialize. this system must run Tivoli Storage
Manager to update the password.
User response: Change the file name used as the
TRACEFILE so that it is equal to or less than 255 Explanation: The password expired.
characters in length.
System action: Tivoli Storage Manager ends.
User response: The administrator for this system must
FMV1826E Unable to open trace output file
update the password.
file-name.
Explanation: A TRACEFILE option in the user
FMV1832W The option 'option' is no longer
configuration file or on the command line used a
supported and will be ignored by Tivoli
directory path and file-name combination to which you
Storage Manager client in this release.
do not have write access.
Explanation: The specified option is in the process of
System action: Client program did not initialize.
being made obsolete and will be ignored by the client
User response: Change the TRACEFILE value so that in this release. This option will be removed in the next
it is a location to which you have write access. release and will no longer be valid.
System action: Processing continues.
FMV1827W Directories cannot be selected with the
User response: Remove the option from the option
table of contents currently loaded on the
file. Also check the documentation to see if this option
server.
has been replaced by a newer option.
Explanation: The table of contents that is currently
loaded on the server for this volume does not contain
FMV1834S Unable to write to 'file-name' for storing
objects corresponding to the one and only point-in-time
password
backup. It contains an incomplete point in time or
multiple points in time. Explanation: Tivoli Storage Manager cannot write to
the specified file-name.
System action: The directory is not selected for
restore. System action: Processing continues.
User response: To be able to select an entire directory User response: Check access permissions and disk
for restore, select "Use Latest" or "Use Point in Time" space. If unsuccessful, see your system administrator.
from the Point in Time dialog.

FMV1835E PASSWORDACCESS is GENERATE,

FMV1828E Screen size is too small for using the but password needed for server
PICK option. 'server-name'. Either the password is not
stored locally, or it was changed at the
Explanation: You cannot use the PICK option on a
server.
workstation that has a screen smaller than 20 characters
across and 10 lines down. Explanation: Either the password is not stored locally,
or it was changed at the server.
System action: Tivoli Storage Manager did not
complete the operation. System action: Tivoli Storage Manager prompts you
for the password if Tivoli Storage Manager is running
User response: Retry the operation using a
in the foreground.
workstation that has a screen with the minimum size,
or do not use the PICK option. User response: If Tivoli Storage Manager was running
as a background process, issue any Tivoli Storage
Manager command from the foreground. Enter the
FMV1830E Unable to write to trace file tracefile.
password in answer to the prompt. Then try your
Tracing disabled.
background Tivoli Storage Manager command again.
Explanation: An error occurred when writing to the
specified tracefile.
System action: Tracing is disabled. Processing
continues.
User response: Ensure the device that the tracefile

Chapter 6. FMV messages 355

FMV1836I • FMV1867E

FMV1836I Unable to process Processor Value Unit FMV1853E Server could not load the Table of
hardware scan info file 'file name', errno, Contents. Status: status
cause.
Explanation: A failure occurred when the server
Explanation: The internal-use data file was not attempted to load a file-level Table of contents for an
readable. NDMP volume. No file-level queries can be performed
against the volume until the problem is solved.
System action: Processor Value Unit information is
not sent to the IBM Tivoli Storage Manager server. System action: The table of contents is not loaded.
Processing continues.
User response: Check the server Activity Log to
User response: No response is necessary. This does determine the cause of failure. Retry the operation after
not affect regular processing. Correct any file access correcting the problem.
permission issues and try the command again. If the
file exists, delete the file and try the command again.
FMV1862W No table of contents information is
available on the server for this volume.
FMV1837S File space filespace-name is ignored.
Explanation: No objects for the selected volume exist
Processing continues.
on the server that were backed up with table of
Explanation: The specified filespace-name in the system contents information. Consequently no file-level queries
options file is invalid. can be performed against the volume.
System action: Tivoli Storage Manager attempts to System action: none
continue the current operation.
User response: If file-level information is desired, use
User response: Check the file space in the system TOC option during backup.
options file and use a valid file space. Retry the
operation.
FMV1865E Session rejected: Named Pipes
connection failure.
FMV1838E Error opening user specified options file
Explanation: An attempt to connect to the server
'filespace-name' .
using Named Pipes communications failed. This might
Explanation: The specified options file-name could not have occurred if an incorrect NAMEDPIPENAME was
be located or opened. specified in the options files or if your system
administrator canceled a backup operation.
System action: Tivoli Storage Manager attempts to
open default option file. System action: Processing stopped.
User response: Make sure specified option file exists User response: Retry the operation, or wait until the
and is valid. server comes back up and retry the operation. Ensure
that the value specified on the NAMEDPIPENAME
option is the same as the one used by the server. If the
FMV1839E Cannot read password.
problem continues, contact your system administrator
Explanation: An error occurred in setting up the input for further help.
file (for example, the terminal) to be read.
System action: Processing stopped. FMV1867E The server generated a CRC for verb
type CRC verb which does not match the
User response: Check the attributes of the terminal. received verb verb received.
Explanation: A cyclic redundancy check (CRC) failed
FMV1852E Server could not load the table of between Tivoli Storage Manager client and server
contents. Status: status reason: reason communication.
Explanation: A failure occurred when the server System action: The current object is skipped.
attempted to load a file-level Table of contents for an Processing continues with the next object.
NDMP volume. No file-level queries can be performed
against the volume until the problem is solved. User response: This is an unusual condition, and
could indicate a communications problem between the
System action: The table of contents is not loaded. Tivoli Storage Manager client and server. Try the
User response: Check the server Activity Log to operation again. If the problem persists, contact IBM
determine the cause of failure. Retry the operation after for further assistance.
correcting the problem.

356 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1869E • FMV1876E

FMV1869E The NDS object requires its parent, or FMV1872E Unable to connect to NetWare target
container, to be present before this service 'server-name'. Make sure the TSA
object can be restored. Try first restoring NLM is loaded on the specified
the parent of this object. machine.
Explanation: SMS requires the parent of the object Explanation: Tivoli Storage Manager interacts with the
(container) to be present before the child or object can Target Service Agent (TSA) and the connection cannot
be created. be made to the Netware server-name.
System action: Processing stops. System action: Processing stopped.
User response: Retry restoring, but at least one level User response: Ensure that the TSA is loaded and
up. For instance, restore 'dir\.o=ibm\*' instead of retry the Tivoli Storage Manager command.
'dir\ou=gpl.o=ibm\*'.
FMV1873E An unknown error occurred while
FMV1870E NDS transport failure FFFDFEAF has processing system object 'sys-obj-name':
occurred. Contact Novell technical utility function 'func-name' failed with
support for further assistance. error error
Explanation: The failure is reported from the NDS Explanation: An unknown error occurred while
ResolveName() function. It indicates a communication processing a system object. The error information
failure between TSANDS and the partition on which captured indicates the reason for the failure. This
the object resides. information can be used to diagnose the problem.
System action: Object skipped. System action: Tivoli Storage Manager ended the
current operation.
User response: Check the Tivoli Storage Manager
client README file for information on required User response: Contact your system administrator for
NetWare software levels, and verify that those levels more information.
are installed. Reducing the RESOURCEUTILIZATION
client setting might also help avoid this error. If the
FMV1874E Login denied to NetWare Target Service
problem persists, contact Novell technical support for
Agent 'server-name'.
further assistance regarding the FFFDFEAF return code.
Explanation: The connection to the Target Service
Agent (TSA) requires a NetWare user name and a
FMV1871W The server CRC version is server CRC
password. The password you entered at the prompt
version which does not match the client
may be incorrect.
version client CRC version.
System action: Processing stopped.
Explanation: This is a rare situation. The server and
client are using different versions of cyclic redundancy User response: Retry the Tivoli Storage Manager
check (CRC) algorithms. command, supplying the correct LAN password.
System action: Processing continues without CRC
checking. FMV1875E Unable to connect to target service. Out
of memory.
User response: Clients can be no more than one
version downlevel from the Tivoli Storage Manager Explanation: Not enough memory to connect to the
server. Make sure the client and server are at Target Service Agent (TSA).
compatible levels. The command line client displays
both client and server versions when the client starts System action: Processing stopped.
and connects to the server. The QUERY SESSION User response: Either add memory to the server or
command will also display the server version. From the free memory by unloading some programs, or by
GUI, use the \"Help/About\" menu item to identify restarting the server.
the client version, and the \"File/Connection
Information\" menu item to identify the server version.
If the client and server versions are incompatible, then FMV1876E Tivoli Storage Manager is unable to
the Tivoli Storage Manager server administrator can connect to the NetWare target service.
turn off CRC checking for your node. NetWare SMS return code = value.
Explanation: The NetWare SMS return code was
unexpected.
System action: Processing stopped.
User response: Messages FMV1874E, FMV1876E and

Chapter 6. FMV messages 357

FMV1877E • FMV1881E

FMV2025E can all be issued due to related problems. System action: The object is skipped. Processing
These problems might include: 1) The NetWare server continues.
has an insufficient number of NetWare user licenses. 2)
User response: Check the Novell web site for any
The NetWare license files are corrupt. The NetWare
additional information about the error, as a fix might
license files can be reinstalled. 3) A NetWare typeful
already be available. Contact Novell technical support
name is not being provided at the NetWare User
for further assistance.
prompt. 4) The Tivoli Storage Manager password file is
corrupt. In this situation, quit all Tivoli Storage
Manager processes, delete or move the *.PWD files that FMV1880E TSA Connect error,
are located in the Tivoli Storage Manager installation NWSMConnectToTargetService
directory, then load dsmc and run the following 'TSA_Target_Service' password file
commands: QUERY SESSION QUERY TSA QUERY 'password_file'. Userid = 'NetWare_userid'
TSA NDS. failed with cc = TSA_ccode
Explanation: Tivoli Storage Manager received an
FMV1877E The parsed string is too long for Tivoli unexpected error from the Novell TSA interface while
Storage Manager to process and has processing the userid and password from NWPWFILE.
been truncated to prevent a buffer
overflow. System action: If the failure is a 'Login Denied' the
user will be prompted for a Novell NetWare Userid
Explanation: This is a rare condition. A very long and Password, and a password file will be created.
string would have to be entered by the user in a
command line, dsm.opt file, or filelist. This string User response: The cc is returned from the TSA which
exceeds the maximum input string size of 1024 bytes. belongs to Novell NetWare. If you get cc = FFFDFFD7
'Login Denied', please check the following:
System action: Tivoli Storage Manager truncated the v The user-id has been disabled.
string to the maximum possible length of 1024, then
continued with the operation. The operation may fail v The user-id/password is invalid or expired.
later due to this truncation. v The user-id has inadequate security access.
User response: Check the client error log for other v The user-id has insufficient rights to files and
messages that might have been logged after this directories.
message was written, and take any corrective action v The user-id specified has a login restriction based on
suggested by those messages. If the problem persists, time-0f-day.
contact IBM support for further assistance. v The user-id specified has a Network address
restriction.
FMV1878E An unknown error occurred while v The user-id specified has a login restriction based on
processing system object 'sys-obj-name': number of concurrent connections.
Service 'service-name' and its dependent v NetWare is not allowing logins (DISABLE LOGIN
services could not be stopped. was issued at the console).
Explanation: An unknown error occurred while If you are unable to determine what is wrong, report
processing a system object. The service listed in the the problem to your service representative.
message and all of its dependent services could not be
stopped. Processing cannot complete until the service is
stopped. FMV1881E Tivoli Storage Manager is unable to use
NWPWFILE 'password_file' to connect
System action: Tivoli Storage Manager ended the TSA target service 'TSA_Target_Service',
current operation. the file is corrupted.
User response: Manually stop the service and retry Explanation: Tivoli Storage Manager could not use the
the operation. NWPWFILE to connect to Novell TSA interface. The
file was corrupted.
FMV1879E A NetWare NDS error occurred during System action: User will be prompted for Novell
restore processing: object NetWare Userid and Password, and password file will
'nds_objectnds_object' TSA error 'tsa_error', be created.
tsa_error_text
User response: The file can be corrupted via another
Explanation: Tivoli Storage Manager received an application or hardware failures. If problem is
unexpected error from the Novell TSA interface. All persistent contact your service representative. A copy of
TSA errors between 0xFFFDFE70 and 0xFFFDFEFF, the corrupted password file will be needed. This
inclusive, can generate this error message. corrupted file must be preserved before you enter a
new userid and password, because Tivoli Storage

358 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1882E • FMV1900I

Manager will overwrite the corrupted file with correct

FMV1896I ***** Restored number objects *****
information.
Explanation: Indicates the number of objects Tivoli
Storage Manager has restored. During a restore session,
FMV1882E Unable to stop service 'service-name';
the running total is periodically printed to the screen of
error error
a command line client.
Explanation: The service could not be stopped by the
System action: Continue with restore.
program.
User response: None.
System action: Tivoli Storage Manager ended the
current operation.
FMV1897I ***** Retrieved number objects *****
User response: Manually stop the service and retry
the operation. Explanation: Indicates the number of objects Tivoli
Storage Manager has retrieved. During a retrieve
session, the running total is periodically printed to the
FMV1891W SUBDIR is not a valid option when
screen of a command line client.
using FILELIST, SUBDIR will be
ignored. System action: Continue with retrieve.
Explanation: When Specifying FILELIST each entry is User response: None.
a single object and so SUBDIR will not apply.
System action: The option SUBDIR is ignored. FMV1898I ***** Processed count files *****
User response: You may have either a -FILELIST or Explanation: Tivoli Storage Manager has processed
SUBDIR on this command, but not both. the specified number of files.
System action: Processing continues.
FMV1892W Expire command is not allowed on the
User response: None.
Tivoli Storage Manager journaled
filespace 'filespace'.
FMV1899I ***** Examined count files *****
Explanation: You cannot expire files from the server
on a Tivoli Storage Manager journaled filespace. Explanation: Tivoli Storage Manager has examined the
specified number of files.
System action: The expire command will not work on
this filespec System action: Processing continues.
User response: If you want to expire this filepec User response: None.
remove it from the local filesystem.

FMV1900I Return code is return code value.

FMV1895I Highest macro return code was return
code value. Explanation: The return code has been issued for the
preceding client command. In order of increasing
Explanation: This message is issued after all severity, the return code meanings are:
commands in a client macro have completed. The v 0 - The command completed successfully
return code represents the highest return code that was
issued during processing of the macro. In order of v 4 - One or more files were skipped
increasing severity, the return code meanings are: v 8 - One or more warning messages were issued
v 0 - The command completed successfully v 12 - One or more error messages (except for skipped
v 4 - One or more files were skipped files) were issued
v 8 - One or more warning messages were issued The return code indicates the highest severity message
v 12 - One or more error messages (except for skipped that was issued during execution of the client
files) were issued command. For a scheduled event, the event will be
considered successful if the return code is 0, 4, or 8.
System action: None. The event will be considered to have failed if the return
code is 12.
User response: For return codes other than 0, the user
may wish to verify the results of the client operation(s) System action: None.
and take diagnostic and repair actions, as necessary.
User response: For return codes other than 0, the user
may wish to verify the results of the client operation
and take diagnostic and repair actions, as necessary.

Chapter 6. FMV messages 359

FMV1901I • FMV1907E

System action: At a minimum, the result code of the

FMV1901I Highest return code was return code
scheduled event is 8.
value.
User response: Identify and repair the problem that
Explanation: This message indicates the highest return
caused the command to fail. If it is not necessary for
code of all the client commands that were executed. In
the command to complete before posting the result of
order of increasing severity, the return code meanings
the scheduled event, then consider using the
are:
POSTNSCHEDULECMD option. If a non-zero return
v 0 - The command completed successfully code is normal for this command, then consider
v 4 - One or more files were skipped wrapping the command in a script that always exits
v 8 - One or more warning messages were issued with a return code of zero.
v 12 - One or more error messages (except for skipped
files) were issued FMV1904E The archive description may not contain
any wildcard characters like '?' or '*'.
System action: None.
Explanation: Descriptions for archive files must not
User response: For return codes other than 0, the user
contain wildcard characters.
may wish to verify the results of the client operation(s)
and take diagnostic and repair actions, as necessary. System action: Processing stopped.
User response: Enter an archive description that does
FMV1902E The PRESCHEDULECMD command not contain wildcard characters.
failed. The scheduled event will not be
executed.
FMV1905E There was a NetWare SMS error
Explanation: The command specified by the processing 'filespace-name
PRESCHEDULECMD option must complete path-namefile-name': error-text
successfully in order to execute the scheduled event. If
Explanation: Tivoli Storage Manager received an
the command completed with a return code of 0 (zero),
unexpected error from the Novell SMS interface.
it is considered to have completed successfully. If the
command completed with any other return code, it is System action: The object is skipped. Processing
considered to have failed. If the command failed then continues.
the scheduled event is not executed.
User response: Check the Novell web site for any
System action: The client does not execute the additional information about the error, as a fix might
scheduled event, and the result code of the scheduled already be available. Contact Novell technical support
event will be 12. for further assistance.
User response: Identify and repair the problem that
caused the command to fail. If it is not necessary for FMV1906I Destination must be specified for this
the command to complete before starting the scheduled operation when using FROMNODE.
event, then consider using the PRENSCHEDULECMD
option, which does not require that the command Explanation: You must specify a destination with a
complete successfully. If a non-zero return code is Restore/Retrieve command when using FROMNODE
normal for this command, then consider wrapping the processing.
command in a script that always exits with a return System action: Processing stops.
code of zero.
User response: Retry the Restore/Retrieve command
with a destination specified.
FMV1903W The POSTSCHEDULECMD command
failed. For example, with the Windows backup-archive client:

Explanation: If the command specified by the restore -fromnode=cougar \\cougar\d$\projx\*

POSTSCHEDULECMD option completed with a d:\projx\
non-zero return code, then the scheduled event is Or, with the UNIX and Linux backup-archive clients:
considered to have completed successfully, but with a
warning-level result. Note that the result of the restore -fromn=node1 -fromo=ann "/home/proj/*"
POSTSCHEDULECMD command will not supercede a /home/gillis/
higher result from the scheduled client command. For
example, if the scheduled client command completed FMV1907E An error occurred while trying to
with a return code of 12, the scheduled event will be perform an object merge operation on
considered to have completed with a return code of 12, the server.
regardless of the outcome of the POSTSCHEDULECMD
command. Explanation: For NetWare clients: The Tivoli Storage
Manager server is unable to perform a NetWare long

360 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1908I • FMV1919E

name conversion. For Unix or Windows image backup:

FMV1914E The specified subkey isn't valid for the
The group used to store associated image components
specified hive.
could not be closed.
Explanation: The specified registry subkey is invalid
System action: The operation ends.
for the specified registry hive.
User response: For NetWare: It is possible that a more
System action: Processing stopped.
current level of the Tivoli Storage Manager server can
perform the conversion. Contact your Tivoli Storage User response: Correct the command and retry the
Manager server administrator for assistance. For Unix operation.
or Windows: This error indicates an authorization
problem. Contact your Tivoli Storage Manager server
FMV1915E Too many arguments specified for the
administrator for assistance. If the problem still cannot
BACKUP REGISTRY command.
be resolved, contact IBM technical support for further
assistance. Explanation: Too many arguments were specified for
the BACKUP REGISTRY command.
FMV1908I The scheduled command completed System action: Processing stopped.
successfully.
User response: Correct the command and retry the
Explanation: The scheduled command completed with operation.
return code of zero, which is interpreted as success.
System action: The scheduled event is successful. The FMV1916E Too many arguments specified for the
result code for the event is 0. RESTORE REGISTRY command.
User response: None. Explanation: Too many arguments were specified for
the RESTORE REGISTRY command.
FMV1909E The scheduled command failed. System action: Processing stopped.
Explanation: The scheduled command completed with User response: Correct the command and retry the
a non-zero return code, which is interpreted as failure. operation.
System action: The scheduled event is failed. The
result code for the event is 12. FMV1917E Too few arguments specified for the
BACKUP REGISTRY command.
User response: Identify and repair the problem that
caused the command to fail. If a non-zero return code Explanation: Too few arguments were specified for
is normal for this command, then consider wrapping the BACKUP REGISTRY command.
the command in a script that always exits with a return
code of zero. System action: Processing stopped.
User response: Correct the command and retry the
FMV1912E An invalid registry hive was specified. operation.

Explanation: The specified registry hive is invalid.

FMV1918E Too few arguments specified for the
System action: Processing stopped. RESTORE REGISTRY command.
User response: Correct the command and retry the Explanation: Too few arguments were specified for
operation. the RESTORE REGISTRY command.
System action: Processing stopped.
FMV1913E An invalid registry subkey was
specified. User response: Correct the command and retry the
operation.
Explanation: The specified registry subkey is invalid.
System action: Processing stopped. FMV1919E The specified eventlog is not valid.
User response: Correct the command and retry the Explanation: The specified eventlog is not valid.
operation.
System action: Processing stopped.
User response: Correct the command and retry the
operation.

Chapter 6. FMV messages 361

FMV1920E • FMV1930W

FMV1920E Too many arguments specified for the FMV1926E The specified system object type is only
BACKUP EVENTLOG command. valid on Windows NT.
Explanation: Too many arguments were specified for Explanation: The specified system object type is only
the BACKUP EVENTLOG command. valid on Windows NT.
System action: Processing stopped. System action: Processing stopped.
User response: Correct the command and retry the User response: Correct the command and retry the
operation. operation.

FMV1921E Too many arguments specified for the FMV1928E Server-initiated sessions are not
RESTORE EVENTLOG command. available in the LAN-free mode.
Explanation: Too many arguments were specified for Explanation: Conflicting options
the RESTORE EVENTLOG command. SESSIONINIT=serveronly and ENABLELANFREE=yes
were specified. This combination is not allowed.
System action: Processing stopped.
System action: Processing stops.
User response: Correct the command and retry the
operation. User response: Use client-initiated sessions or disable
LAN-free.
FMV1922E Too few arguments specified for the
BACKUP EVENTLOG command. FMV1929E An error occurred saving the registry
key.
Explanation: Too few arguments were specified for
the BACKUP EVENTLOG command. Explanation: The active registry key cannot be copied
to the ADSM.SYS staging directory.
System action: Processing stopped.
System action: The registry backup operation stops.
User response: Correct the command and retry the
operation. User response: Check the space available on the
Windows boot partition to ensure there is room to
contain a copy of the Windows registry. This might
FMV1923E Too few arguments specified for the
require several megabytes of free space. Also check the
RESTORE EVENTLOG command.
Windows permissions on the ADSM.SYS staging
Explanation: Too few arguments were specified for directory and ensure that the Windows user which you
the RESTORE EVENTLOG command. are using to run Tivoli Storage Manager has full access
to that directory and its contents.
System action: Processing stopped.
User response: Correct the command and retry the FMV1930W Tivoli Storage Manager Express client
operation. view not supported with a Tivoli
Storage Manager Enterprise server.
FMV1924E The specified system object is not valid. CLIENTVIEW option ignored.

Explanation: The specified system object is not valid. Explanation: The Tivoli Storage Manager Express®
client view is only supported when going to a Tivoli
System action: Processing stopped. Storage Manager Express server. When a Tivoli Storage
User response: Correct the command and retry the Manager Express client connects to a Tivoli Storage
operation. Manager Enterprise server, the CLIENTVIEW option is
ignored, and the Tivoli Storage Manager Standard
client view is displayed instead.
FMV1925E The specified system object type is not
valid. System action: The CLIENTVIEW option is ignored
and the Tivoli Storage Manager Enterprise client view
Explanation: The specified system object type is not is displayed.
valid.
User response: If you intend to use the Tivoli Storage
System action: Processing stopped. Manager Enterprise server, then update your
User response: Correct the command and retry the CLIENTVIEW option to a value of STANDARD.
operation. Otherwise, update your TCPSERVERADDRESS option
to point to your Tivoli Storage Manager Express server.

362 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1931E • FMV1941E

User response: Correct the command and retry the

FMV1931E An error saving one or more eventlogs.
operation.
Explanation: An error occurred saving one or more
eventlogs.
FMV1937E No NTDS server name specified for the
System action: Processing stopped. BACKUP NTDS command.
User response: Correct the command and retry the Explanation: No NTDS server name was specified for
operation. the BACKUP NTDS command.
System action: Processing stopped.
FMV1932E An error occurred replacing one or more
User response: Specify NTDS server name at the
registry keys.
command and retry the operation.
Explanation: The registry key or keys being replaced
are exclusively held by another process. The registry
FMV1938E NT Active Directory is not supported in
keys were previously restored but the system was not
this OS level.
restarted.
Explanation: NT Active Directory is not supported in
System action: processing stops.
this OS level.
User response: This error occurs because the registry
System action: Processing stopped.
key or keys being replaced are exclusively held by
another process. This can happen if the registry keys User response: Install Active Directory before
were previously restored but the system was not performing backup operation.
rebooted. Reboot the system and attempt the restore
operation again.
FMV1939E File Replication Service backup failed.

FMV1933E Error accessing file or device 'name'. Explanation: IBM Tivoli Storage Manager encountered
an error while backing up files under control of the
Explanation: An error has occurred while accessing Windows 2000 File Replication Service
the file or device.
System action: Processing stopped.
System action: Backup set operation is not completed.
User response: Examine the Windows 2000 File
User response: Verify that the file or device exists and Replication Service Event log to insure the File
is accessible. Replication Service is operating properly. Restart the
service and retry the backup operation.
FMV1934E Backup set 'name' not found.
FMV1940E File Replication Service restore failed.
Explanation: The backup set name was not found on
the server. Explanation: IBM Tivoli Storage Manager encountered
an error while restoring files under control of the
System action: The backup set operation is not
Windows 2000 File Replication Service
processed.
System action: Processing stopped.
User response: Verify that the backup set name is
correct. User response: Examine the Windows 2000 File
Replication Service Event log to insure the File
Replication Service is operating properly. Restart the
FMV1935E Too many arguments specified for the
service and retry the restore operation.
BACKUP NTDS command.
Explanation: Too many arguments were specified for
FMV1941E System Volume backup failed.
the BACKUP NTDS command.
Explanation: IBM Tivoli Storage Manager encountered
System action: Processing stopped.
an error while backing up files of the Windows 2000
User response: Correct the command and retry the System Volume
operation.
System action: Processing stopped.
User response: Examine the Windows 2000 File
FMV1936E Not enough arguments specified for the
Replication Service Event log to insure the system
BACKUP NTDS command.
volume was successfully initialized. Restart the service
Explanation: Not enough arguments were specified and retry the backup operation
for the BACKUP NTDS command.
System action: Processing stopped.

Chapter 6. FMV messages 363

FMV1942E • FMV1949E

REPLACE NO was in effect, causing all existing files

FMV1942E System Volume restore failed.
and directories to be skipped, or REPLACE PROMPT
Explanation: IBM Tivoli Storage Manager encountered was in effect, and when prompted, the user chose to
an error while restoring files under control of the skip this file or all existing directories and files. No
Windows 2000 File Replication Service additional action is necessary if the decision to skip the
file was deliberate. Otherwise the operation can be
System action: Processing stopped.
retried using either REPLACE ALL (automatically
User response: Examine the Windows 2000 File replace existing directories and files) or REPLACE
Replication Service Event log to insure the system PROMPT (prompt the user whether to replace the file).
volume was successfully initialized. Restart the service
and retry the restore operation.
FMV1947W The following directory exists and is
skipped: file-space_name directory_path
FMV1943E The operation is not supported: directory_name
Downlevel server version.
Explanation: The client tried to restore or retrieve the
Explanation: The operation cannot be performed specified directory. The directory exists in the target
because server version is downlevel. restore location and the user chose not to replace the
existing directory.
System action: Processing stopped.
The directory can be skipped because the option
User response: Use correct server version. REPLACE=NO is set, which causes all existing files and
directories to be skipped. The directory can be skipped
FMV1944E Error accessing file or device. because option REPLACE=PROMPT is set, and the user
chooses to skip this directory when prompted.
Explanation: An error has occurred while accessing
the file or device. System action: The directory is skipped, a message is
logged in the dsmerror.log log file, and restore or
System action: Backup set operation is not completed. retrieve processing continues with the next object.
User response: Verify that the file or device exists and User response: No additional action is necessary.
is accessible.
To replace the files, try the operation again and set
option REPLACE=ALL. You can set
FMV1945E The long namespace has been removed REPLACE=PROMPT and when prompted, choose to
from the local filespace. If you wish to replace the directory.
proceed with the backup/archive
operation, rename your filespace on the
server. FMV1948E The Microsoft volume shadow copy
system components could not be
Explanation: Tivoli Storage Manager has detected that queried.
the server namespace is NTW:LONG, but the local
volume does not have long name support. If you Explanation: IBM Tivoli Storage Manager encountered
would like to back up the volume using the short an error while querying the system writers under
names, rename the filespace on the server. If you would control of the Windows volume shadow copy service.
like to back up using long names, add the long The Tivoli Storage Manager error log and Windows
namespace support back to the volume in question. event log might contain additional information about
this error.
System action: Processing stopped.
System action: Processing stops.
User response: Add the long namespace support to
the volume or rename(remove) the corresponding User response: Try the operation again. If the error
server filespace. persists, review the Tivoli Storage Manager error log
and Windows event log for information related to this
error. You might need to restart the volume shadow
FMV1946W File exists, skipping copy service, then try the operation again. It might be
Explanation: The client tried to restore or retrieve the necessary to reboot the machine to clear the volume
specified file, but the file already existed in the target shadow copy error state.
restore location and the user chose not to replace the
existing file. FMV1949E Microsoft volume shadow copy
System action: The file is skipped, a message is snapshot initialization failed.
logged in dsmerror.log, and restore or retrieve Explanation: IBM Tivoli Storage Manager encountered
processing continues with the next object. an error while initializing the Microsoft Volume
User response: The file was skipped because either Shadow Copy Service for backup or restore. The Tivoli
Storage Manager error log and Windows event log can

364 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1950E • FMV1959I

contain additional information about this error. System action: Processing stopped.
System action: processing stops. User response: Enter a correct file specification.
User response: Try the operation again. If the error
persists, review the Tivoli Storage Manager error log FMV1954E Backup processing of 'file-space name'
and Windows event log for information related to this finished with failures.
error. Use the Windows command VSSADMIN LIST
Explanation: This message indicates that the file
WRITERS to determine the status of the Volume
system backup has completed, but encountered errors
Shadow Copy service. You can reboot the machine to
during backup processing.
clear the volume shadow copy error state. If the system
is a Domain Controller and the Active Directory service System action: Processing continues.
is stopped, restarting the Active Directory service will
resolve the issue. User response: Examine the client error log for
additional messages related to errors in backing up the
file system. Take any corrective action as suggested by
FMV1950E Backup using Microsoft volume shadow the messages.
copy failed.
Explanation: IBM Tivoli Storage Manager encountered FMV1956E Too few arguments specified for the
an error while performing a backup operation using the BACKUP GROUP command.
Microsoft volume shadow copy service. The Tivoli
Storage Manager error log and Windows event log Explanation: Too few arguments were specified for
might contain additional information about this error. the BACKUP GROUP command.

System action: processing stops. System action: Processing stopped.

User response: Review the Tivoli Storage Manager User response: Correct the command and retry the
error log and Windows event log for information operation.
related to this error. Restart any failing system service
indicated in the Windows event log. Restart the volume FMV1957E Showmembers and inactive are
shadow copy Service. You can use the Windows mutually exclusive parameters on a
command VSSADMIN LIST WRITERS to determine the query.
status of the volume shadow copy service. It might be
necessary to reboot the machine to clear the Volume Explanation: Showmembers and inactive are mutually
Shadow Copy error state. exclusive parameters on a query.
System action: Processing terminates.
FMV1951E Restore using Microsoft volume shadow User response: Specify one of the mutually exclusive
copy failed. parameters on the query
Explanation: IBM Tivoli Storage Manager encountered
an error while restoring with the Microsoft Volume FMV1958W No base group found, attempting a full
Shadow Copy Service. backup.
System action: processing stops. Explanation: A differential backup requires a previous
User response: Review the Tivoli Storage Manager full backup to have been performed.
error log and Windows event log for information System action: Processing continues, and a full
related to this error. Restart any failing system service backup is attempted.
indicated in the Windows event log. Restart the volume
shadow copy Service. You can use the Windows User response: None. Perform a full backup before
command VSSADMIN LIST WRITERS to determine the attempting a differential backup
status of the volume shadow copy service. It might be
necessary to reboot the machine to clear the Volume FMV1959I Removing previous incomplete group
Shadow Copy error state. 'name' Id:hi-lo
Explanation: A previous group backup failed without
FMV1952E Invalid symbolic link destination cleaning up the temporary groups correctly.
'file-name' entered
System action: The previous incomplete groups are
Explanation: You entered a restore/retrieve removed and processing continues.
destination file-name specification that is a symbolic
link. To restore to symbolic link, make sure you set the User response: None.
followsymbolic option to yes. Also, check where this
symbolic link points. You can restore/retrieve to a
symbolic link that points to an existing object.

Chapter 6. FMV messages 365

FMV1960I • FMV1975W

messages that might indicate a reason for the failure.

FMV1960I Contacting the WebSphere
Verify that the web client is installed correctly. Try to
component-name. This step could take a
correct any indicated problems, then try the operation
few minutes...
again. If the problem persists, contact IBM technical
Explanation: The application needs to contact the IBM support for further assistance.
WebSphere component to obtain configuration
information.
FMV1972E The connection to the remote client
System action: Processing continues agent (dsmagent) failed. Either the port
number could not be read, or the port
User response: None.
number is invalid.
Explanation: An error occurred when trying to read
FMV1961E Could not detect any installation of the
the port number. A connection to the remote client
WebSphere Deployment Manager or
agent cannot be made.
Application Server.
System action: Processing stopped.
Explanation: The application could not detect a
supported WebSphere component installed. At this User response: Check the error log for any other
time, only the WebSphere Deployment Manager and messages that might indicate a reason for the failure.
Application Server are supported. Verify that the web client is installed correctly. Try to
correct any indicated problems, then try the operation
System action: Processing stops
again. If the problem persists, contact IBM technical
User response: Verify that the intended WebSphere support for further assistance.
component is installed on this machine, and retry the
operation.
FMV1973I VSS writer for system object 'name' does
not exist. Restore skipped.
FMV1962E Operation Failed.
Explanation: Microsoft Volume Shadow Copy Service
Explanation: The attempted operation on the does not detect a writer for this system component.
WebSphere component failed. Either the component is not installed or is not running..

System action: Processing stops System action: Object skipped.

User response: Check the error log for more details. User response: Install or enable the affected system
service and retry the operation.
FMV1963E WAS Filesweep failed for filespec 'name'
FMV1974W Error removing previous incomplete
Explanation: Could not obtain the list of files to be group Id:hi-lo
backed up for the indicated filespec
Explanation: A previous group backup failed without
System action: Processing stops cleaning up the temporary groups correctly, and the
User response: Verify that the process has access to error still can not be cleaned up.
the indicated filespec and retry the operation. System action: The previous incomplete groups
remain and processing continues.
FMV1964E A failure occurred while contacting the User response: None.
WebSphere component-name.
Explanation: The attempted operation on the FMV1975W Tivoli Storage Manager server error
WebSphere component failed. reason occurred closing and renaming
System action: Processing stops the group

User response: Check the error log for more details. Explanation: An error was encountered closing and
renaming the temporary group.

FMV1971E The remote client agent (dsmagent) System action: The backup is unsuccessful.
could not be started. User response: Ensure that the user has the proper
Explanation: The remote client agent cannot be authority to update the group and try the operation
started. This error message is usually preceded or again.
followed by other messages.
System action: Processing is stopped.
User response: Check the error log for any other

366 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV1976E • FMV1989E

System action: The operation fails.

FMV1976E The specified system service is not
valid. User response: Upgrade your Tivoli Storage Manager
Server and Tivoli Storage Manager Storage agent to a
Explanation: The specified system service is not valid.
level that supports this function. See error log for
System action: Processing stopped. version information.
User response: Correct the command and retry the
operation. FMV1981E Server :Version ver, Release rel, Level
lev.subl Storage Agent:Version SAver,
Release SArel, Level SAlev.SAsubl
FMV1977E Dsmcad schedule invocation was
unsuccessful. This command will be Explanation: This message supplies extra detail to
tried again in 10 minutes. downlevel messages.
Explanation: Dsmcad was unable to get the valid System action: The operation fails.
scheduler information from the dsmc schedule process.
User response: This message supplies extra detail to
This could be due to some problems during the
downlevel messages.
scheduler initialization, such as incorrect option usage.
System action: Dsmcad will try to invoke the
FMV1986E Initialization functions cannot open the
scheduler again in 10 minutes in order to get the valid
trace file specified.
information.
Explanation: The file "tracefile-name could not be
User response: Check the console and error logs to
opened during initialization. The specified path may be
determine what kind of error occurred during the dsmc
incorrect. It is also possible that the current user does
process and correct the problem.
not have permission to write to the tracefile in the
directory specified. It is also possible that no space is
FMV1978E The Tivoli Storage Manager server is available at the given tracefile location.
downlevel and does not support the
System action: Processing terminates.
requested function. See error log for
version information. User response: Make sure the tracefile option points
to a valid path and that the user has proper
Explanation: The function being used requires a more
permissions to write to the file specified.
current Tivoli Storage Manager Server.
System action: The operation fails.
FMV1987E A destination file specification is not
User response: Upgrade your Tivoli Storage Manager allowed with this command.
Server to a level that supports this function. See error
Explanation: Of all the system object restore
log for version information.
commands only RESTORE ASR allows the entry of a
destination file specification.
FMV1979E The Tivoli Storage Manager Storage
System action: Processing stopped.
Agent is downlevel and does not
support the requested function. See User response: Re-issue the command without a
error log for version information. destination file specification.
Explanation: The function being used requires a more
current Tivoli Storage Manager Storage Agent. FMV1988W No filespaces are selected for preview.
System action: The operation fails. Explanation: You requested a preview operation
without selecting a client filespace.
User response: Upgrade your Tivoli Storage Manager
Storage Agent to a level that supports this function. See System action: Tivoli Storage Manager cannot perform
error log for version information. a preview without a filespace selected.
User response: Select the volumes you want to
FMV1980E The Tivoli Storage Manager Server and preview and retry the operation.
Tivoli Storage Manager Storage agent
are downlevel and do not support the
requested function. See error log for FMV1989E Initialization functions cannot open the
version information. Error Log file specified.

Explanation: The function being used requires a more Explanation: The Error Log file could not be opened
current Tivoli Storage Manager Server and Tivoli during initialization. The specified path may be
Storage Manager Storage agent incorrect. It is also possible that the current user does
not have permission to write to the logfile in the

Chapter 6. FMV messages 367

FMV1990W • FMV1999E

directory specified. It is also possible that no space is User response: Select objects of the same type to
available at the given logfile location. perform delete operation.
System action: Processing terminates.
FMV1996W The volume mount points enumeration
User response: Make sure the logfile option points to
on 'filesystem name' volume failed.
a valid path and that the user has proper permissions
Windows system error code: error;
to write to the file specified.
reason: 'error-reason'.
Explanation: The client was unable to scan the
FMV1990W The 'filesystem name' volume mount point
specified volume for volume mount points. The error
can not be accessed. The Tivoli Storage
information captured indicates the reason for the
Manager return code is 'rc'.
failure. A common reason is that the account under
Explanation: The client is unable to access volume which the client is running does not have access to the
mount point. The common reasons for this are that the volume.
account under which the client is running does not
System action: The processing continues with the next
have access to the volume mount point, or the volume
volume.
is mounted onto a cluster volume which is currently
not available. User response: Ensure that the client is running under
an account which has access to the volume and volume
System action: The inaccessible mount point is
mount points. Correct the condition causing the error
skipped and processing continues. with the next mount
and try the operation again. If the problem persists,
point or volume.
contact your system administrator or Tivoli Storage
User response: Check the error log for additional Manager administrator for further help.
messages that might yield additional information about
the problem that prevents access to the volume mount
FMV1997W No files have been previously backed
point. Ensure that the Tivoli Storage Manager client is
up for the VSS component
running under an account which as access to the
'component-name'.
volume mount point. Ensure that the mount point is
not accessing a clustered volume. Please refer to Explanation: You tried to restore the Microsoft Volume
Microsoft KB Article 280297 for more information about Shadow Copy (VSS) System State component which
how to configure volume mount points on a clustered does not contain file data. This is not necessarily a
server. problem.
System action: Processing continues.
FMV1991E An error occurred processing registry
User response: Check the error log for any other
key 'key-name', data value 'value-name'.
messages that occurred during backup. The logs can
See the client error log for additional
indicate a reason for the failure.
information about this error.
Explanation: An unexpected error occurred when the
FMV1998W Transaction byte limit 'name' is not
client tried to read or update the Windows registry.
supported by the server. Value reset to
Additional information regarding the error is usually
limit
placed in the error log.
Explanation: The TXNBYTELIMIT is larger than the
System action: The operation might not execute
server supports. The value will be reset to a supported
correctly, depending on the error.
limit.
User response: Check the client error log for any other
System action: TXNBYTELIMIT is reset, and
messages that might have been logged when this
processing continues.
message was written, and take any corrective action
suggested by those messages. If the problem persists, User response: Set the option to a value supported by
contact IBM support for further assistance. the server.

FMV1995W Objects of different types cannot be FMV1999E type of the operation processing of
deleted at the same time. 'filespace-name' stopped.
Explanation: Deleting objects of different types is not Explanation: The client has encountered a condition
allowed. For example, deleting Backup Sets and regular where it can not continue processing the specified file
file objects at the same time is not possible. space. The Tivoli Storage Manager client error log or
schedule log should contain additional messages
System action: No processing takes place.
related to this error.
System action: Processing stops.

368 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2000I • FMV2036W

User response: Check the Tivoli Storage Manager

FMV2032I The client VM restore is skipping the
client error log and schedule log for any additional
unsupported Independent disk : vmdk
messages related to this error. Take any corrective
action that might be suggested by the related messages, Explanation: The VMware vStorage APIs do not
then try the operation again. If the problem persists, support snapshoting Independent disks, no backups
contact your Tivoli Storage Manager administrator for were created.
further assistance.
System action: Processing continues.
User response: None.
FMV2000I Unable to convert file names because
MEMORYEFficientbackup option is ON.
FMV2033I The client VM restore is skipping the
Explanation: Tivoli Storage Manager has detected that
unsupported physical Raw Device
a local name space change has occurred on the volume
Mapping (pRDM) disk : vmdk
that is currently being backed up. Tivoli Storage
Manager would convert the file names to the new Explanation: The VMware vStorage APIs do not
name space, but cannot because the option support snapshoting physical Raw Device Mapping
MEMORYEFficientbackup, is on. (pRDM) disks, no backups were created.
System action: Tivoli Storage Manager continues to System action: Processing continues.
backup using the old name space.
User response: None.
User response: Edit the dsm.opt file, and set
MEMORYEFficientbackup to OFF.
FMV2034I The virtual machine backup is skipping
the unsupported physical Raw Device
FMV2025E Login failed to NetWare file server Mapping (pRDM) disk : vmdk
'server-name'.
Explanation: The VMware vStorage APIs do not
Explanation: Tivoli Storage Manager cannot establish support snapshoting physical Raw Device Mapping
an authorized connection to the Netware file server (pRDM) disks, backups are not possible.
through NDS. Connection numbers might be
exhausted. System action: Processing continues.

System action: Processing stopped. User response: None.

User response: Messages FMV1874E, FMV1876E and

FMV2025E can all be issued due to related problems. FMV2035I The virtual machine backup is skipping
These problems might include: 1) The NetWare server the unsupported Independent disk :
has an insufficient number of NetWare user licenses. 2) vmdk
The NetWare license files are corrupt. The NetWare Explanation: The VMware vStorage APIs do not
license files can be reinstalled. 3) A NetWare typeful support snapshoting Independent disks, backups are
name is not being provided at the NetWare User not possible.
prompt. 4) The Tivoli Storage Manager password file is
corrupt. In this situation, quit all Tivoli Storage System action: Processing continues.
Manager processes, delete or move the *.PWD files that User response: None.
are located in the Tivoli Storage Manager installation
directory, then load dsmc and run the following
commands: QUERY SESSION QUERY TSA QUERY FMV2036W Pruning functions cannot open one of
TSA NDS. the Tivoli Storage Manager prune files:
log-name. errno = errno-value,

FMV2026W Bad sectors were detected on the volume Explanation: The file "log-name could not be opened
'volname'. during pruning. The system set the error code
errno-value. If the reason given is "access denied," the
Explanation: Bad sectors are skipped during image current user does not have permission to write to the
backup/restore operations. file in the directory specified. It is also possible that no
System action: Processing continues. space is available at the given file location or another
Tivoli Storage Manager process started by different user
User response: Make sure the volume data is not id is performing pruning at the same time.
corrupt by using system tools like chkdsk (Windows)
or fsck (Unix). System action: Pruning stops, processing continues.
User response: Set the DSM_LOG (or DSMI_LOG)
environment variable to a directory into which the
current user can write.

Chapter 6. FMV messages 369

FMV2037W • FMV2044E

products that communicate with each other and ensure

FMV2037W Schedule log pruning failed.
that they are all at the same version, release, and level.
Explanation: The schedule log pruning function
completed with errors.
FMV2041E Snapshot Differencing support is not
System action: Processing continues. available on the specified NetApp filer.
User response: Check error log for possible reasons of Explanation: Incremental by snapshot difference
failure. backup cannot be performed because required support
on the specified NetApp filer is not availble. .
FMV2038W Invalid option 'option-name' received System action: Processing terminates.
from the Tivoli Storage Manager server
User response: None.
client options set.
Explanation: The client received an invalid option
FMV2042W 'symboliclink':is a symbolic link to a file
from the Tivoli Storage Manager server's client option
or directory in another filesytem. ACLs
set. Although most syntax checking for client option set
or extended attributes might not be
options is done by the server, there are still errors that
backed up.
can only be detected by the client. These errors include:
v Option value is not correct. Explanation: The backup or archive operand contains
a symbolic link to a file or directory in another file
v Options that have been retired by newer versions of
system. Processing may lead to loss of ACLs or other
the Tivoli Storage Manager client.
extended attributes because they might not be
v Missing brackets or directory delimiters. processed.
v Include and exclude patterns that are too complex.
System action: The file data is backed up. Processing
System action: The option is ignored by the Tivoli continues with the next object.
Storage Manager client.
User response: If you need to ensure that ACLs and
User response: Contact the Tivoli Storage Manager other extended attributes are backed up successfully, do
server administrator to determine if the option can be not use symbolic links to back up files on other file
removed from the client option set. systems of different file system types. Instead use Tivoli
Storage Manager to process the other file system
directly.
FMV2039E Invalid destination file specification
'file-name' entered
FMV2043I The virtual machine template 'name' has
Explanation: The destination file specification must
already been backed up.
end with directory delimiter when performing a file list
restore, or when the restore specification is for more Explanation: Virtual machine templates are skipped if
than one file, or when the option SUBDIR YES is in no change has occurred since the last backup.
effect.
System action: Processing skips this virtual machine
System action: Processing stopped. template.
User response: Specify a destination that ends with User response: To back up this virtual machine
directory delimiter. template, run an incremental forever full backup
operation.
FMV2040E While attempting to communicate with
the remote client, a version check FMV2044E The template virtual machine 'name'
reveals that the versions do not match. cannot be restored when the Tivoli
The version is remoteversion but the Storage Manager data mover node on
expected version is localversion. the vStorage Backup Server is connected
directly to an ESX/ESXi host.
Explanation: During initialization between the local
client and the remote client, version checking reveals Explanation: The VMware vStorage API do not
that the versions do not match. This is usually the support template virtaul machine operations when
result of an upgrade of one client module without connected directly to an ESX/ESXi host.
upgrading other client modules that are part of product
System action: Processing stops for this template
solution.
virtual machine
System action: The calling procedure returns and
User response: Virtual machine template operations
control is passed back the user.
are supported when the IBM Tivoli Storage Manager
User response: Check the versions of all TSM Client data mover node connects directly to a ESX/ESXi host.

370 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2045E • FMV2052E

Modify the VMCHOST to connect the TSM data mover User response: The backup copy of the named stream
to a vCenter Server. is damaged. The file is restored to as great an extent as
possible, but the file should be examined to verify that
it is usable.
FMV2045E The VMENABLETEMPLATEBACKUPS
option is not specified. The virtual
machine template 'name' can not be FMV2049W Named stream of object 'object-name' may
backed up. be corrupt.
Explanation: The VMENABLETEMPLATEBACKUPS Explanation: One or more of the file's named streams
template option must specify YES in order for a virtual may be corrupt.
machine template to be included in a backup operation.
System action: The named stream is
The default value is NO.
restored/retrieved to as great an extent as possible.
System action: Processing stops for this template
User response: The backup copy of the named stream
virtual machine
may be damaged. The file is restored to as great an
User response: Use the option extent as possible, but the file should be examined to
-vmenabletemplatebackups=yes and run the operation verify that it is usable.
again.
FMV2050E Tivoli Storage Manager needs to prompt
FMV2046S Error 'errtxt' (errno=errno) occurred for the password but cannot prompt
trying to write to audit log 'file-name'. because the process is running in the
The audit log function is disabled. background.
Explanation: There was an error encountered writing Explanation: If PASSWORDACCESS=PROMPT or if
to the audit log (for example, there is not enough space the password that is stored locally is incorrect, Tivoli
on the disk). Storage Manager attempts to prompt the user for the
password. The attempt to prompt the user fails because
System action: Audit logging is disabled for the rest
Tivoli Storage Manager is running in the background.
of the operation. The return code for the operation is
When a process is running in the background,
set to 12 to indicate that the contents of the audit log
prompting is not allowed.
are incomplete.
System action: Processing stopped.
User response: If this is an out of space condition
either free up space on the volume or try to write the User response: If RUNASSERVICE=YES, do not set
audit log to a volume with more space. PASSWORDACCESS=PROMPT. Use
PASSWORDACCESS=GENERATE.
FMV2047E An unexpected error was encountered
processing a system state/services FMV2051W The local snapshot repository was not
request. Tivoli Storage Manager found on location.
function name : function-name Tivoli
Explanation: The specified directory for the local
Storage Manager function : function-desc
snapshot location does not exist.
Tivoli Storage Manager return code :
TSM-rc Tivoli Storage Manager System action: Processing continues.
explanation : TSM-msg Tivoli Storage
Manager file : file-name (line-number) User response: A new local snapshot repository will
be build in the specified directory.
Explanation: None.
System action: Processing the system state stops. FMV2052E Information about the disk subsystem is
missing.
User response: Contact the Tivoli Storage Manager
administrator with the information provided in this Explanation: The local snapshot repository could not
message. be initialized due to missing information about the disk
subsystem.
FMV2048W Named stream of object System action: Processing stops.
'object-namepath-name file-name' is corrupt.
User response: The application ensures that the disk
Explanation: One or more of the file's named streams subsystem is initialized properly. Check for preceding
are corrupt. error messages.
System action: The named stream is not
restored/retrieved.

Chapter 6. FMV messages 371

FMV2053E • FMV2062W

System action: Processing ends.

FMV2053E A memory allocation error has occurred
in file filename, line number linenumber. User response: Check for preceding error messages
like memory allocation error or other system error.
Explanation: Enough memory was not available to
continue processing.
FMV2059E Cannot find a target data container that
System action: Processing ends.
match with the source data container.
User response: Ensure that your system has sufficient
Explanation: During a snapshot type backup or
real and virtual memory. Close unnecessary
hardware function, Tivoli Storage Manager tries to find
applications.
a target data container that match to the source data
container to satisfy the operation. A matching target
FMV2054E Operating system error errno: messagetext. data container could not be found.
Explanation: The application encountered an System action: Processing ends.
unexpected message error during the execution of a
User response: See the rules for select one of multiple
system function. The respective operating system error
target data containers. For example, this message will
and message text will be displayed.
be displayed if the user is trying to start a FlashCopy
System action: Processing stops. backup of type 'INCR' and all the target sets are being
used for the FlashCopy type 'COPY'. Make sure also
User response: Check the specific error message.
that the target volumes are available to the backup
system and the syntax is correct for the following setup
FMV2055I The local snapshot manager could not file parameters: 1. shark_target_volume 2.
be locked. shark_copy_service_code 3. java_home_directory 4.
primary_copyservices_servername 5. shark_username 6.
Explanation: The local repository is locked by another shark_password
application. This process will proceed when the other
application unlock the local repository.
FMV2060W Cannot find a volume in the target data
System action: Processing continues. container dcID to match with the source
User response: None. srcvol.
Explanation: This warning message indicates that for
FMV2056I Waiting maximal timeout seconds until the specific source not any target volume could be
the lock is released by the other found in this target data container that matches for a
application. FlashCopy operation. If multiple target data containers
are being used, the processing will continue checking
Explanation: While the local repository is locked by the volumes of the next target data container.
another application, the program will wait a specific
period of time to proceed. For example, in the mySAP System action: Processing continues.
environment, the wait period is 1 hour. User response: None.
System action: Processing continues.
User response: None. FMV2061W The target data container with ID dcid
was not found in the local repository.

FMV2057E Local snapshot manager not initialized. Explanation: An inquire of the data container with the
specified ID could not be satisfied because that target
Explanation: The local snapshot repository was used set does not exists in the local repository.
without previous initialization.
System action: Processing may continue.
System action: Processing ends.
User response: The application that is requesting the
User response: The system normally ensures that the inquire will decide whether or not the error should end
local repository is initialized. Check for preceding error the program. Check for following messages.
messages.

FMV2062W Could not find a target data container in

FMV2058E The data container with ID dcID could the state state to fulfill the requested
not be updated in the local repository. criteria.
Explanation: During a FlashCopy backup the target Explanation: A data container in the specified state
set record in the local repository is updated with the was not found in the local repository to satisfy specific
correspondent properties. A failure occurred during criteria requested by the application.
that process.

372 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2063W • FMV2071E

System action: Processing may continue.

FMV2068E No target LUNs were found for the data
User response: Which criteria have been passed is container dcID in the .fct file filename.
application specific. Check for following messages. The
Explanation: The program will search in the .fct file
application will decide whether or not that warning
for each specific data container a list of entries with the
should end the program.
label <PREFIX>TARGET_VOLUME where the prefix
depends on the hardware type. Either you have a
FMV2063W The local snapshot repository already wrong label for the target volumes of the specified data
exists on the directory location. container or this data container in the .fct file does not
have any target LUNs.
Explanation: An application tried to create the local
repository in a directory that already exists. System action: Processing ends.

System action: Processing may continue. User response: This error can only occurred if the
application does not have a GUI where the user
User response: The application will decide whether or provides the input of the target data containers and the
not that warning should end the program. Check for format will automatically be checked. If so, please
following messages. check the format of the .fct file.

FMV2064I The local snapshot repository will be FMV2069E Cannot read the file filename of the local
created on the directory location. snapshot repository.
Explanation: The local snapshot repository containing Explanation: The system keeps some information
information about the state of the data containers is about the state of the data containers locally in a file.
being created. This file was not found or is not accessible.
System action: Processing continues. System action: Processing ends.
User response: None. User response: Check the name, the path and the
right of the file.
FMV2065I The local snapshot repository could not
be created on the directory location. FMV2070E The repository state file filename is
Explanation: A failure occurred creating the local empty or has a wrong format.
snapshot repository. Explanation: The system keeps some information
System action: Processing ends. about the state of the data containers locally in a file.
This file was found but the expected format of the data
User response: Look for a operating system error in not correct.
message.
System action: Processing ends.

FMV2066E Cannot read the .fct file filename. User response: Normally the system ensures that the
format of this file is correct. Check for preceding error.
Explanation: The .fct file containing the target data
containers was not found or is not accessible.
FMV2071E The data container dcID could not be
System action: Processing ends. inserted in the local snapshot repository.
User response: Check the name, the path and the Explanation: The system keeps some information
right of the file. about the state of the data containers locally in a file.
Inserting an entry for a new data container occurred an
FMV2067E The exception CLsmException was error.
thrown. Reason: txt. System action: Processing ends.
Explanation: An unexpected error occurred processing User response: This is an unexpected error. Check for
a function of the local snapshot repository. preceding error. If not any other error can be seen,
System action: Processing ends. collect the logs and traces and contact the support.

User response: Check the specific reason.

Chapter 6. FMV messages 373

FMV2072E • FMV2079E

Explanation: The DMAPI has a limitation in the size

FMV2072E An unexpected error was encountered
of data that can be stored in a DMAPI attribute. If the
processing a Tivoli Storage Manager
lenght of the file system name exceeds this limit the
operation using a hardware or snapshot
Tivoli Storage Manager client can not add space
function. Tivoli Storage Manager
management to the file system.
function name : function-name Tivoli
Storage Manager function : function-desc System action: Space management cannot be added to
Tivoli Storage Manager return code : file system.
TSM-rc Tivoli Storage Manager file :
file-name (line-number) User response: Please make sure that the length of the
file system name does not exceed the DMAPI limit.
Explanation: None.
System action: Processing stops. FMV2077E program-name: Reconcile for file system
'filesystem' can not be started for the
User response: Contact the Tivoli Storage Manager
selected mode in a non-scout
administrator with the information provided in this
environment. Please use Two Way
message.
Orphan Check Reconcile instead.
Explanation: The Tivoli Storage Manager client
FMV2073E The file filename of the local snapshot
reconciliation program can not be started in orphan
repository could not be opened for
check or stub restore mode when the HSM system is
writing.
configured to run without the scout daemon.
Explanation: The system keeps some information
System action: Reconcile can not run in a non scout
about the state of the data containers in the local
environment.
snapshot repository. Opening a file of this repository
occurred an error. User response: If you have configured a non scout
environment you need to use the Two Way Orphan
System action: Processing ends.
Check Reconcile.
User response: Check the rights permission of that
file.
FMV2078E System state backup is not allowed
CLUSTERNODE is set to YES.
FMV2074E Cannot open user input FlashCopy
Explanation: When the CLUSTERNODE option is set
target file 'fct_file'.
to YES, the backup systemstate command is not valid.
Explanation: The FlashCopy target file that the user
System action: System state backup is stopped.
provided cannot be read.
User response: If the CLUSTERNODE option is
System action: The operation fails.
incorrectly set to YES, then change the option to NO
User response: Run the client configuration utility and and try the operation again. Otherwise see the
provide a valid FlashCopy target user input file. backup-archive client manual for further information
about configuring the client to run in a cluster
environment.
FMV2075E There is no VTOC data available for the
volume. The volume cannot be backed
up. FMV2079E Error processing 'filespace
namepath-namefile-name': error scanning
Explanation: The volume disk label type is not VTOC.
snapshot
It is possible that your disk is formatted with an EFI
label. The Tivoli Storage Manager client on Solaris Explanation: This message is issued when the Tivoli
currently supports only VTOC disk labels. Storage Manager client is unable to read data from a
snapshot used for the backup. If you are performing
System action: The volume is not backed up.
the Microsoft Volume Shadowcopy Service (VSS)
User response: Do not attempt to backup volumes snapshot backup one possible cause is that the
formatted with a non-VTOC disk label. operating system deleted a VSS snapshot because the
shadow copy storage could not grow. If you are
performing the snapshot difference incremental backup
FMV2076E program-name: Space Managment can not on normal NetApp/N-Series volumes one possible
be added for file system 'filesystem' The cause is that the base snapshot was accidentally
length of the file system name exceeds removed from the NetApp file server.
the maximum length of 'maxlength'
which can be stored in a DMAPI System action: Backup processing for the file system
attribute. stops.

374 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2080W • FMV2091I

User response: If you were performing VSS disable fault tolerant. Then, after the backup completes,
snapshot-based backup, examine the client error log enable fault tolerant.
and the Microsoft Windows system event log for any
other messages that might help identify the problem. If
FMV2087I 'vApp name' does not contain VMs.
there are no obvious reasons for the failure, try the
operation again,the problem might be caused by Explanation: The specified vApp does not contain any
temporary I/O conflicts between VSS and other system VMs.
disk I/O activities. If you were performing snapshot
difference incremental backup, contact your Tivoli System action: Back up of the specified vApp
Storage Manager administrator to verify that base completes. Processing continues to the next vApp.
snapshot was not accidentally deleted. User response: No response is required.

FMV2080W The value 'option' for the option 'option' FMV2088E Session rejected: The client does not use
is no longer supported and will be unicode.
ignored by Tivoli Storage Manager
client in this release. Explanation: The server cannot accept the client
session because the client does not use unicode and the
Explanation: The specified option value is in the node already contains a unicode filespace. The server
process of being made obsolete and will be ignored by records whether or not the client's data is unicode, and
the client in this release. This option value will be does not let the node change this attribute.
removed in the next release and will no longer be
valid. System action: Processing stops.

System action: Processing continues. User response: Logon to the server from a client with
a platform that uses unicode data. For example, the
User response: Update the option value or remove the original platform that was used to create the existing
option from the option file. Also check the filespaces for this node. Alternatively, if the client node
documentation to see if this option has been replaced needs to change to the platform that is currently being
by a newer option. attempted, contact the server administrator to remove
the existing filespaces that contain unicode data and try
FMV2083W No vApps that match the input the node connection again.
specification were found.
Explanation: A vApp that matches the specified input FMV2089I The specified vApps do not contain
or the VAPP value in the DOMAIN.VCD option was VMs.
not found. Explanation: None of the specified vApps contain any
System action: The operation is stopped VMs.

User response: Make sure the the VAPP value in the System action: Backup processing is skipped. The
DOMAIN.VCD option is correct. operation is complete.
User response: No response is required.
FMV2084I Creating a new vApp
Explanation: The estore is attempting to create the FMV2090I The virtual machine folder could not be
destination vApp. found in this path: 'name'.

System action: This message is for informational Explanation: The destination target does not have the
purposes only. original inventory path that was saved with the virtual
machine. As a result, the virtual machine is restored to
User response: No action is required. the top level of the ESX/ESXi inventory.
System action: Processing continues
FMV2085E The virtual machine is configured as a
fault tolerant virtual machine. As a User response: None
result, it cannot be backed up.
Explanation: vSphere does not allow for the snapshot FMV2091I The virtual machine resource could not
or backup of fault tolerant virtual machines with be found in this path: 'name'.
vStorage API for Data Protection. Explanation: The destination target does not have the
System action: The virtual machine is not backed up. original resource path that was saved with the virtual
machine. As a result, the virtual machine is restored to
User response: To back up a fault tolerant virtual the top level of the ESX/ESXi inventory.
machine with vStorage API for Data Protection, first
System action: Processing continues

Chapter 6. FMV messages 375

FMV2092I • FMV2106I

User response: None

FMV2102E File list processing not started
Explanation: An error occured before the file list
FMV2092I The restore process will override the
processing was started.
original inventory path that was saved
with this virtual machine. System action: Processing stops.
Explanation: Specifying the -datacenter or -host option User response: Examine the client error log for
will override the original inventory path that was additional messages that might indicate the reason for
saved with the virtual machine. As a result, the virtual the problem. Try to follow the suggested corrective
machine is restored to the top level of the ESX/ESXi actions (if any) and try the operation again.
inventory.
System action: Processing continues FMV2103E File list processing was interupted
User response: None Explanation: An error occured suring file list
processing.
FMV2093E The remote file system agent is System action: Processing stops.
downlevel and does not support this
User response: Examine the client error log for
operation. NODENAME : node
additional messages that might indicate the reason for
MULTI-NODE NAME : multi-node
the problem. Try to follow the suggested corrective
hostname : host TCP/IP address :
actions (if any) and try the operation again. The error
tcpaddr:tcpport version :
log will list all entries that were not processed. If audit
version.release.level..mod
logging is enabled, the audit log will also list the
Explanation: None. entries that were not processed.
System action: The operation fails.
FMV2104E An error occured after processing the
User response: Upgrade the remote file system agent
file list.
to a supported level.
Explanation: An error occured after the file list
processing completed.
FMV2097E Unable to establish a session with the
Tivoli Storage Manager server as target System action: Processing stops.
node 'target' using agent node 'agent'.
User response: Examine the client error log for
Explanation: None. additional messages that might indicate the reason for
the problem. Try to follow the suggested corrective
System action: Processing ends.
actions (if any) and try the operation again.
User response: Ensure that the multi-node name exists
on the server and that the agent node has the proper
FMV2105I File list entry not Processed: File List
authority to target node listed.
Entry
Explanation: A file list operation encounted an error.
FMV2100E Neither source volume id nor target
This entry from the file list was not processed.
volume id is in the volume list.
System action: This message is for auditing purposes
Explanation: None.
only.
System action: Processing ends.
User response: This message is for auditing purposes
User response: None. only.

FMV2101E Compressed data grew. FMV2106I Connection to primary Tivoli Storage

Manager server primary server; failed
Explanation: The size of data is growing after
compression Explanation: A communication error occured while
attempting to connect to the primary server. The node
System action: Processing continues. is configured for replication and will attempt to connect
User response: The application must abort the to the secondary server.
transaction. System action: Processing continues.
Please turn off compression and try to resend the User response: Contact the Tivoli Storage Manager
object. server administrator to verify if the primary server is
available. If the primary server is available, check the

376 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2107I • FMV2114W

Tivoli Storage Manager error log for communications also be specified. These options are normally set by the
failures and correct any configuration issues. If the Tivoli Storage Manager server administrator and saved
Tivoli Storage Manager server is not available, allow to the options file during logon to the primary server.
the node to fail over to the secondary server as
System action: Processing stops.
configured by the primary Tivoli Storage Manager
server administrator. User response: Manually edit the options file to either
correct or remove the options.
FMV2107I Attempting to connect to secondary
server secondary server; at secondary server; FMV2112I Secondary server is configured as
: TCP/IP Port; 'read-only'. Backup and Archive
operations are not supported when the
Explanation: The node is configured for replication
secondary server is in 'read-only' mode
and will attempt to connect to the secondary server.
The secondary server address and port are configured Explanation: The Tivoli Storage Manager client has
by the primary Tivoli Storage Manager server established a session with a server that is configured as
administrator and are saved in the options file. 'read-only'. The Tivoli Storage Manager server is
configured as a replication server and will not accept
System action: Processing continues.
data from this node.
User response: Contact the Tivoli Storage Manager
System action: Processing continues.
server administrator to verify if the primary server is
available. If the primary server is available, check the User response: The Tivoli Storage Manager may be
Tivoli Storage Manager error log for communications used for Restore, Retrieve and Query operations.
failures and correct any configuration issues. If the Backup and Archive commands will fail. The Tivoli
Tivoli Storage Manager server is not available, allow Storage Manager server administrator can enable
the node to fail over to the secondary server as Backup and Archive operations for the node with the
configured by the primary Tivoli Storage Manager 'Update Node' command.
server administrator.

FMV2113E The Command; command is not enabled

FMV2108I Connected to secondary server secondary when connected to the secondary server
server;. in failover mode.
Explanation: The node is configured for replication Explanation: The Tivoli Storage Manager client has
and has successfully connected to the secondary server. failed over and established a session with a secondary
server. The Tivoli Storage Manager server is configured
System action: Processing continues.
as a replication server and will not accept data from
User response: None. this node. Commands that store data on the server are
disabled.
FMV2110I Connection to secondary server Tivoli System action: Processing continues.
Storage Manager secondary server; failed
User response: You can use the Tivoli Storage
Explanation: A communications error occured while Manager client for Restore, Retrieve, and Query
attempting to connect to the secondary server. The operations. Backup and Archive operations will fail.
node is configured for replication and an attempt to
connect to the secondary server was made but failed.
FMV2114W IBM Tivoli Storage Manager application
System action: Processing continues. protection did not copy the VSS
Manifest files from VM 'VM'.
User response: Contact the Tivoli Storage Manager
server administrator to verify if the secondary server is Explanation: The VSS Manifest files are not found on
available. If the secondary server is available, check the the guest machine.
Tivoli Storage Manager error log for communications
System action: The VSS Manifest files cannot be
failures and correct any configuration issues.
copied. Verify that the VSS and SQL Writer services are
running on the guest VM
FMV2111E The REPLSERVERNAME entry for the
User response: None
specified MYREPLICATIONSERVER
option was not found.
Explanation: The MYREPLICATIONSERVER option
must have a matching REPLSERVERNAME entry in
the options file. The REPLSERVERGUID,
REPLTCPPORT, and REPLTCPSERVERADDRESS must

Chapter 6. FMV messages 377

FMV2115I • FMV2121I

space. The replication server connection information

FMV2115I Replication server connection
can not be saved and failover will not be possible.
information saved: connection information;
System action: The operation failed.
Explanation: This node is configured for replication.
The replication server connection information has been User response: Check the local disk for possible
saved to the options file. The replication server options causes of the write error, and check to see that
are set by the IBM Tivoli Storage Manager sufficient access to the options file is configured.
Administator, sent to the client during logon, and are
saved to the options file.
FMV2119I An invalid replication server address
System action: Processing continues. return code rc value = rc-value was
received from the server.
User response: None.
Explanation: An invalid replication server address
return code indicates that the server was not able to
FMV2116W IBM Tivoli Storage Manager application
aquire connection information.
protection did not back up the VSS
Manifest files from VM 'VM'. System action: Possible server problem.
Explanation: A failure occurred while backing up the User response: Check the server log for more
files that are necessary for application protection. information.
System action: The back up of this VM failed.
FMV2120W The last store operation date reported by
User response: Check the dsmerror.log for additional
the server replication server; of server
information. Then try the operation again.
commit date; UTC does not match the last
store operation date of client commit date;
FMV2117E Source volume is of subtype dev-type UTC stored by the client.
and destination is of subtype dev-type.
Explanation: The last store operation date reported on
Destination must be larger than source.
the server does not match the date stored locally on the
Explanation: Logical volumes from scalable volume client. If connected to the replication server it is likely
groups (subtype DS_LVZ) do not contain an LVCB. that the replication was done before the last store
That is, the very first block contains user data. AIX operation from the client to the primary server. Hence,
LVM volumes from original volume groups (subtype the replication is out of date. If connected to the
LVM) contain a Logical Volume Control Block (LVCB) primary server it is likely that the previous backup was
on the first block (512 bytes) of the volume. When done from another machine.
restoring to a volume of subtype LVM, the first block
System action: Processing continues.
must be skipped in order to preserve the existing LVCB
of the destination volume. That is, the restore operation User response: Contact the Tivoli Storage Manager
begins writing at the second block of the volume. This server administrator. Restoring from an out of date
means that given two volumes of identical size, one of replica may lead to loss of data. If the primary server
subtype DS_LVZ and the other is of subtype LVM, the cannot be recovered, a full backup to the replica may
latter has one less 512-byte block in which to store user be appropriate. If connected to the primary server, the
data. Thus when you restore a volume of subtype message can be ignored.
DS_LVZ to a volume of subtype LVM, it is not
sufficient for the destination volume to be the same size
as the source volume. Instead, the destination volume FMV2121I The file space on replication server;
must be at least one 512-block larger than the source started replication at server replication
volume. start date; The replication completed
successfully at server replication complete
System action: The restore operation is not performed. date;.
User response: Make sure that both source and Explanation: The last server replication completed
destination logical volumes are of the same type, or successfully.
choose a larger destination volume, or increase the size
of the destination volume. System action: Processing continues.
User response: None.
FMV2118I A write failure occurred while
attempting to save node replication
failover values to the options file.
Explanation: A write failure is often a result of
insufficient access permissions to the options file, but
could also be caused by the lack of available disk

378 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2122I • FMV2129E

FMV2122I The file space on replication server; FMV2126E The Organization VDC node that
started replication at server replication contains snapshots of Organization
start date;. The replication did not VDC 'org vdc name' of organization 'org
complete successfully. The last name' was not found.
successful replication completed at server
Explanation: The Organization VDC node contains the
replication last successful date;.
backup data to be restored. The specified organization
Explanation: The last server replication did not and organization VDC are not mapped to this
complete successfully. Organization VDC node. As a result, the restore
operation cannot proceed.
System action: Processing continues.
System action: The operation stops.
User response: Contact the Tivoli Storage Manager
server administrator. Restoring from an out of date User response: Verify that the specified organization,
replica may lead to loss of date. If the primary server organization VDC, and vApp are correct.
cannot be recovered, a full backup to the replica may
be appropriate.
FMV2127E The snapshot data that is required to
restore 'vapp name' cannot be retrieved
FMV2123W Issue the dsmc SET PASSWORD from the Tivoli Storage Manager Server.
-type=VCD 'vCloud Director hostname'
Explanation: The required snapshot data was unable
'userid' 'password' command to save an
to be retrieved from the Tivoli Storage Manager Server.
encrypted password.
System action: The operation stopped.
Explanation: The VCDPW option was found either in
an options file or as a command- line entry. Although User response: Check the dsmerror.log file for
both methods of entry are allowed, they present a information about why the data was not retrieved.
security risk because the password is in plain text and Then, try the operation again. If the problem persists,
is not encrypted. search the Tivoli Storage Manager Support web site
(http://www.ibm.com/software/sysmgmt/products/
System action: The option is accepted and the VCD
support/IBMTivoliStorageManager.html) for known
password is used in the current session.
solutions.
User response: To save an encrypted password, issue
the following command: dsmc SET PASSWORD
FMV2128E Failed in creating a restored version of
-type=VCD 'VirtualCenter hostname' 'userid' 'password'
vApp 'vapp name'.
Explanation: The operation to create a restored vApp
FMV2124W Client node replication table is locked
on the vCloud failed. The data associated with the
by another process.
vApp snapshot might not be complete.
Explanation: Another process is using the client node
System action: The operation stops.
replication table. Only one process may use it at a time.
User response: Check the dsmerror.log file for
System action: This process does not use the client
information about why the operation failed. Then, try
node replication table.
the operation again. If the problem persists, search the
User response: You can serialize processes using the Tivoli Storage Manager Support web site
client node replication table. Or you can reconfigure the (http://www.ibm.com/software/sysmgmt/products/
current process to use a different table path to avoid support/IBMTivoliStorageManager.html) for known
contention. solutions.

FMV2125I Total number of VMs to process: vms FMV2129E Failed to associate the vApp contents to
num to restore the restored vApp: 'vapp name'.
Explanation: Displays the total of VMs to process Explanation: The vApp metadata or VM data was not
during the vApp restore operation. added to the created vApp. This failure might be
caused by a problem in the backed up vApp, its
System action: This message is for informational
metadata, or in the backup data.
purposes only.
System action: The operation completes. However, it
User response: No action is required.
is possible that the restored object does not contain all
of the expected content.
User response: Check the backed up vApps on the
vCloud. In addition, check the dsmerror.log file for any

Chapter 6. FMV messages 379

FMV2135E • FMV2148I

additional messages that might be related to this products/support/IBMTivoliStorageManager.html) for

problem. Try the operation again. If the problem known solutions.
persists, search the Tivoli Storage Manager Support
web site (http://www.ibm.com/software/sysmgmt/
FMV2143E vApp verification failed. Data
products/support/IBMTivoliStorageManager.html) for
inconsistency was found.
known solutions.
Explanation: During the verification of a vApp, an
inconsistency was found in the backup data.
FMV2135E The node on the Tivoli Storage Manager
server is in read only mode. System action: The restore operation was stopped.
Explanation: The server has prevented a store User response: Examine the client error log for any
operation on the Tivoli Storage Manager server. The additional messages that might be related to this
most likely explaination for this is the node has failed problem and contact Tivoli Storage Manager technical
over to the secondary server. support for further assistance.
System action: Processing stops.
FMV2145W Warning - updating an existing virtual
User response: Contact the Tivoli Storage Manager
machine named 'name'. The restore
server administrator to verify if the primary server is
operation continues.
available. If the primary server is available, check the
Tivoli Storage Manager error log for communications Explanation: The virtual machine exists and will be
failures and correct any configuration issues. updated with the disks specified.
System action: The virtual machine will be updated
FMV2136E Operation not permitted. The secondary by the restore operation.
server reports the primary server is
available. Quit and restart the Tivoli User response: No user action is necessary.
Storage Manager client and retry the
command. FMV2146E The target vCenter or ESX/ESXi host is
Explanation: The server has prevented a store no longer supported, for virtual machine
operation on the secondary Tivoli Storage Manager backups, by this version of IBM Tivoli
server. The secondary server reports that the primary Storage Manager.
server is available. However, the Tivoli Storage Explanation: The target vCenter or ESX/ESXi host is
Manager client failed over to the secondary server. no longer supported, for virtual machine backups, by
System action: Processing stops. this version of IBM Tivoli Storage Manager.

User response: Restart the Tivoli Storage Manager System action: Processing stops for this virtual
client and verify the primary server connection is machine.
made. If the Tivoli Storage Manager client is unable to User response: Specify another target vCenter or
connect to the primary server, contact the Tivoli Storage ESX/ESXi host that is supported by this version of IBM
Manager server administrator to verify if the primary Tivoli Storage Manager.
server is available. If the primary server is available,
check the Tivoli Storage Manager error log for
communications failures and correct any configuration FMV2147E The virtual machine named 'name'
issues. already exists on the target system.
Explanation: The virtual machine cannot be restored
FMV2138E Failed in restoring the vApp properties because the name already exists on the target system.
to vApp: 'vapp name'. System action: Processing stops for this virtual
Explanation: The vApp properties were not restored machine
to the created vApp. This failure might be caused by a User response: Use the -vmname option to rename the
problem in the backed up vApp or in its metadata. virtual machine.
System action: The operation completes. However, it
is possible that the restored object does not contain all FMV2148I Virtual machine templates cannot be
of the expected content. backed up in incremental mode,
User response: Check the backed up vApps on the switching to full mode.
vCloud. In addition, check the dsmerror.log file for any Explanation: The backup of virtual machine templates
additional messages that might be related to this are only supported as full backups.
problem. Try the operation again. If the problem
persists, search the Tivoli Storage Manager Support System action: Processing continues in full mode for
web site (http://www.ibm.com/software/sysmgmt/ this template virtual machine.

380 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2149E • FMV2160I

User response: To back up this virtual machine User response: Eliminate the possible causes for this
template use full mode. issue and retry.

FMV2149E The restore operation for this virtual FMV2157E The server 'server-name' was not removed
machine to the target ESX/ESXi host is from the environment.
not supported because virtual machine
Explanation: The requested IBM Tivoli Storage
hardware version is incompatible.
Manager server was not added to the multi-server
Explanation: The target ESX/ESXi host does not environment. There are several causes for this error:
support the virtual hardware version of the virtual v The file system is not managed by HSM.
machine. As a result, a restore of the specified virtual
v The HSM management is not active for the file
machine to this host is not supported.
system.
System action: Processing stops for this virtual v The IBM Tivoli Storage Manager server is the default
machine. server for the file system and must be removed last.
User response: Specify another virtual machine to v The IBM Tivoli Storage Manager server name is not
restore or specify another target ESX/ESXi host that valid.
supports virtual hardware version of the virtual
System action: HSM multi-server processing stops.
machine.
User response: Eliminate the possible causes for this
issue and retry.
FMV2150E Set
HSMDISABLEAUTOMIGDAEMONS
YES in the dsm.opt file to use HSM FMV2158E The server 'server-name' was not added to
multi-server functionality. the environment. You must first add the
default IBM Tivoli Storage Manager
Explanation: Set HSMDISABLEAUTOMIGDAEMONS
server ('default-server-name') for this file
YES in the dsm.opt file to use HSM multi-server
system.
functionality.
Explanation: The requested IBM Tivoli Storage
System action: HSM multi-server processing stops.
Manager server was not added to the multi-server
User response: Set environment. The requested IBM Tivoli Storage
HSMDISABLEAUTOMIGDAEMONS YES in dsm.opt. Manager server is not the default server for the file
system.
FMV2155W Skipping file 'file-name'. File related to System action: HSM multi-server processing stops.
'server-name'.
User response: Add the default IBM Tivoli Storage
Explanation: File is already coupled to another server. Manager server first.
System action: HSM continues with normal operation.
FMV2159I The server 'server-name' was added to the
User response: Use the correct server to process the
environment.
file.
Explanation: The requested IBM Tivoli Storage
Manager server was added to the multi-server
FMV2156E The server 'server-name' was not added to
environment.
the environment.
System action: HSM multi-server processing
Explanation: The requested IBM Tivoli Storage
continues.
Manager server was not added to the multi-server
environment. There are several causes for this error: User response: None.
v The file system is not managed by HSM.
v The HSM management is not active for the file FMV2160I The server 'server-name' was removed
system. from the environment.
v The file system is out of space. Explanation: The requested IBM Tivoli Storage
v The default IBM Tivoli Storage Manager server for Manager server was removed from the multi-server
the file system was not yet added to the multi-server environment.
environment.
System action: HSM multi-server processing
v The IBM Tivoli Storage Manager server name is not continues.
valid.
User response: None.
System action: HSM multi-server processing stops.

Chapter 6. FMV messages 381

FMV2161E • FMV2172E

FMV2161E The server 'server-name' is not a valid FMV2167W Can not read SERVERNAME attribute.
IBM Tivoli Storage Manager server for
Explanation: IBM Tivoli Storage Manager cannot read
this environment.
the SERVERNAME attribute from file.
Explanation: The requested IBM Tivoli Storage
System action: HSM multi-server processing
Manager server was not added to the multi-server
continues.
environment.
User response: None.
System action: HSM multi-server processing stops.
User response: Check the dsm.sys file for the correct
FMV2168W Can not write SERVERNAME attribute.
IBM Tivoli Storage Manager server name.
Explanation: IBM Tivoli Storage Manager cannot write
SERVERNAME attribute to file.
FMV2162E HSM cannot be removed from the file
system. The IBM Tivoli Storage System action: HSM multi-server processing
Manager multi-server list is not empty. continues.
Explanation: HSM management was not removed User response: None.
from the file system.
System action: HSM processing continues. FMV2169E Skipping - Requested server is not
included in multi-server environment
User response: Remove all IBM Tivoli Storage
for filesystem 'file-system'.
Manager servers from the multi-server list before
removing HSM. Explanation: The requested IBM Tivoli Storage
Manager server is not part of the multi-server
environment.
FMV2163E The default IBM Tivoli Storage Manager
server ('server-name') for the file system System action: HSM multi-server processing
will be removed. continues.
Explanation: The default IBM Tivoli Storage Manager User response: None.
server will be removed. The IBM Tivoli Storage
Manager server list for multi-server will be empty after
this step. FMV2170W Skipping - file linked to another server.

System action: HSM processing continues without Explanation: The file is already coupled to another
multi-server support. IBM Tivoli Storage Manager server.

User response: nothing. System action: HSM continues with normal operation.
User response: Use the correct server to process the
FMV2165I The server 'server-name' is the default file.
server and has been removed last.
Explanation: The requested IBM Tivoli Storage FMV2171E The DMAPI version 'dmapi-version' is not
Manager server was removed from the multi-server supported.
environment. Explanation: The DMAPI version installed on this
System action: HSM multi-server processing node is not supported from the given TSM client.
continues. System action: Due to this issue the affected HSM
User response: None process ends.
User response: Use the documentation to identify the
FMV2166I The IBM Tivoli Storage Manager server supported DMAPI versions. Install a supported DMAPI
'server-name' is not included in the and retry the HSM command or process.
multi-server environment.
Explanation: The requested IBM Tivoli Storage FMV2172E Command not supported in
Manager server is not part of the multi-server HSMBACKENDMODE TSMFREE.
environment. Explanation: That command is not supported using
System action: HSM multi-server processing an external HSM backend.
continues. System action: Exit programm
User response: None. User response: Do not use the command

382 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2173E • FMV2184E

setup wizard. The "baclient" and "config" directories

FMV2173E Volume 'volume name' from vFiler 'vFiler
can be found in the directory where you installed the
name' is mounted using AIX NFS
Tivoli Storage Manager Backup-Archive Client. For
version 4. This configuration is not
example, "C:\Program Files\Tivoli\TSM\baclient" and
supported for snapshot difference
"C:\Program Files\Tivoli\TSM\config"
incremental backups.
Explanation: Snapshot difference incremental backups
FMV2177E The vCloud vApp named 'vapp name'
are not supported for vFiler volumes mounted using
already exists on the target system.
AIX NFS version 4.
Explanation: The restore vApp command does not
System action: Snapshot difference incremental
support restoring a vApp with an existing name.
backup fails.
System action: The restore was not performed.
User response: This problem is documented by
NetApp BURT 630200. Apply the fix for this once it is User response: Execute the required restore command
available from NetApp. Specify "testflag again, considering that the given name for the restored
snapdiffenablevfilernfs4" in dsm.opt file and retry the vApp is not used.
snapshot difference incremental backup.

FMV2181I Option primary server; saved.

FMV2174E Conflicting options HSMLOGMAX and
HSMLOGRETENTION were specified. Explanation: This node is configured for replication.
The primary server name option is now saved to the
Explanation: Values were specified for both the options file. The replication server options are set by
HSMLOGMAX and the HSMLOGRETENTION options. the IBM Tivoli Storage Manager Administator, sent to
These options are mutually exclusive. the client during logon, and are saved to the options
file.
System action: Processing stops.
System action: Processing continues.
User response: Specify a nonzero value for
HSMLOGMAX if you wish to have the Tivoli Storage User response: None.
Manager hsm log wrap when it reaches the specified
maximum value. Use HSMLOGRETENTION if you
wish you have the hsm log limited in size on a FMV2182I Option secondary server; saved.
time-based schedule. Explanation: This node is configured for replication.
The replication server option is now saved to the
FMV2175I Data from server 'server-name' should be options file. The replication server options are set by
recalled using the script the IBM Tivoli Storage Manager Administator, sent to
'dsmMultiServerRemove.pl'. the client during logon, and are saved to the options
file.
Explanation: Migrated files must be recalled before a
server can be removed from the multiserver System action: Processing continues.
configuration. User response: None.
System action: The server will not be removed.
User response: Check the documentation for detailed FMV2183E Organization 'Org name' not found in the
information about the 'dsmMultiServerRemove.pl' vCloud Director.
script. Explanation: The specified Organization is not
recognized by the vCloud Director.
FMV2176E The sample journal configuration file '' System action: The action requested for the
could not be copied to ''. organization is canceled.
Explanation: The TSM Journal Engine setup wizard User response: Verify that an organization by the
tried to create a new journal configuration file by specified name exists in the vCloud. Organization
copying the sample configuration file. However the names are case-sensitive.
sample configuration file could not be successfully
copied.
FMV2184E Organization VDC 'Org vDC name' not
System action: The TSM Journal Engine setup wizard found in organization 'Org name'.
stops.
Explanation: The specified organization VDC is not
User response: Manually copy the sample journal part of the specified organization.
configuration file "config\tsmjbbd.ini.smp" to
"baclient\tsmjbbd.ini", then try the TSM Journal Engine System action: The action requested for the
organization VDC is canceled.

Chapter 6. FMV messages 383

FMV2185E • FMV2192E

User response: Verify that an organization VDC by

FMV2189E The vCloud protection runtime library
the specified name exists in the specified organization.
cannot be initialized.
Organization and organization VDC names are
case-sensitive. Explanation: The vCloud protection runtime library
failed to initialize. This issue might be caused by the
Java runtime not being installed.
FMV2185E Failed to log on to the vCloud Director
on 'vCD host name' with user name 'vCD System action: vCloud operations cannot be
user name': Authentication failed. performed.
Explanation: The vCloud credentials specified in the User response: Verify that Java is installed.
VCDUser and VCDPass options were rejected by the
vCloud director.
FMV2190E The vCloud protection runtime library
System action: vCloud operations cannot be encountered an internal error.
performed.
Explanation: An internal error had occured in the
User response: Update the VCDUser and VCDPass vCloud runtime library.
options with valid credentials for the vCloud Director.
System action: vCloud operations cannot be
performed.
FMV2186E Failed to log on to the vCloud Director
User response: Check the dsmerror.log file for any
on 'vCD host name' with user name 'vCD
additional messages that might be related to this
user name': User not found.
problem. Try the operation again. If the problem
Explanation: The vCloud user specified by the persists, search the Tivoli Storage Manager Support
VCDUser option does not exist on the vCloud Director. web site (http://www.ibm.com/software/sysmgmt/
products/support/IBMTivoliStorageManager.html) for
System action: vCloud operations cannot be
known solutions.
performed.
User response: Update the the VCDUser option with
FMV2191E An error occurred creating the default
a valid vCloud user name for the vCloud Director.
VSS staging directory 'path'.
Explanation: The Tivoli Storage Manager client uses
FMV2187E Failed to establish connection to the
an VSS staging directory to store files related to to VSS
vCloud Director on 'vCD host name'.
snapshot operations. The Tivoli Storage Manager client
Explanation: A connection cannot be established to was unable to create this directory structure.
the vCloud Director on the host that is specified by the
System action: The Tivoli Storage Manager client
VCDHost and VCDPort options.
stopped.
System action: vCloud operations cannot be
User response: If the problem persists, contact IBM
performed.
technicalsupport for further assistance.
User response: Verify that the values of the VCDHOst
and VCDPort options are valid, network connectivity to
FMV2192E Failed to read the node configuration
the host exists, and that the vCloud Director service is
information from node 'node name'.
running.
Explanation: Node mapping information is required
for this vCloud operation. However, the mapping
FMV2188E The vCloud protection runtime library
information either does not exist or cannot be read
is not installed or failed to load.
from the specified node.
Explanation: The vCloud runtime library is not
System action: The operation is canceled.
installed or cannot be loaded.
User response: Make sure that you are accessing the
System action: vCloud operations cannot be
correct node. The node mapping information is stored
performed.
in the Provider VDC node. If necessary, go to the
User response: Verify that the Tivoli Storage Manager Configuration page and click 'Run the Configuration
for Virtual Environments vCloud runtime library is Wizard' to make corrections to the node mapping.
installed. If neccessary, reinstall Tivoli Storage Manager
for Virtual Environments.

384 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2193E • FMV2200I

User response: Issue a full VM restore to retrieve a

FMV2193E The required filespace for the vApp
previous state of the SQL Server environment.
'vapp name' backup does not exist.
Explanation: No filespace exists for the specified
FMV2197E The verification test of vApp 'vapp name'
vApp backup.
indicates that VM data is incomplete in
System action: The restore was not performed. the vApp. The vApp cannot be restored.
User response: Make sure that the specified vApp is Explanation: Inconsistent data was found in the VM
correct. Then, try the restore operation again. for the specified vApp. It is not possible to restore the
specified vApp. This may happen due to incomplete
node replication or if a file space was deleted.
FMV2194E The snapshot data is incomplete for
vApp 'vapp name'. System action: Operation continues.
Explanation: Inconsistent data was found in the User response: Check the dsmerror.log file for any
backed up vApp. It is not possible to restore the additional messages that might be related to this
specified vApp. problem. Run a detailed query for this vApp to verify
that all VMs backups exist. If node replication is used,
System action: The restore was not performed.
ensure it is working correctly. If the problem persists,
User response: Check the dsmerror.log file for any perform a FULL new backup of the vApp and search
additional messages that might be related to this the Tivoli Storage Manager Support web site
problem. If the problem persists,search the Tivoli (http://www.ibm.com/software/sysmgmt/products/
Storage Manager Support web site support/IBMTivoliStorageManager.html) for known
(http://www.ibm.com/software/sysmgmt/products/ solutions.
support/IBMTivoliStorageManager.html) for known
solutions.
FMV2198I Backup of VMware vCloud Director
vApp 'vApp name' in Organization VDC
FMV2195E The number of VMs that are available 'Org VDC name' of organization 'Org
for restore is different from expected name' completed successfully. VMs:
according to the vApp 'vapp name' number of VM backed up out of number of
metadata. VMs in vApp VMs backed up
successfully.
Explanation: Inconsistent data was found in the vApp
metadata. It is not possible to restore the specified Explanation: The backup operation completed. The
vApp. More VMs have been backed up than are now number of VMs backed up and the total number of
available for restore. This may happen due to VMs in the vApp are displayed.
incomplete node replication or if a file space was
System action: This message is for informational
deleted.
purposes only.
System action: The restore was not performed.
User response: If the number of VMs backed up is
User response: Check the dsmerror.log file for any less than the total in the vApp please check the error
messages that may indicate the problem. Run a detailed logs for more information.
query for this vApp to verify that all VMs backups
exist. If node replication is used, ensure it is working
FMV2199W The virtual machine 'VM-name' contains
correctly. If the problem persists, search the Tivoli
one or more disks that are larger than
Storage Manager Support web site
the currently supported size so the
(http://www.ibm.com/software/sysmgmt/products/
individual disks will be excluded.
support/IBMTivoliStorageManager.html) for known
solutions. Explanation: The virtual machine contains disks larger
than the currently supported size so the individual
disks will be excluded from the backup.
FMV2196W An incompatible disk configuration is
detected. Individual SQL Database System action: The backup will continue without the
Restore of database 'database name' is not larger disks.
supported.
User response: None.
Explanation: One or more SQL database files in this
operation are located on Dynamic and/or Guid
FMV2200I ***** Filling Cache count files *****
Partition Table (GPT) style disks. Individual SQL
Database Restore is not supported from disks that are Explanation: Tivoli Storage Manager the specified
configured in this manner. number of files have been added to the disk cache.
System action: Backup of the full VM continues. System action: Processing continues.

Chapter 6. FMV messages 385

FMV2201I • FMV2220E

User response: None.

FMV2213E Error while querying volume properties
of volume volserial. Please verify that the
FMV2201I ***** Inspecting Cache count files ***** volume specified in the target volumes
file exists.
Explanation: Tivoli Storage Manager the specified
number of files have been examined in the disk cache. Explanation: None.

System action: Processing continues. System action: Processing stops.

User response: None. User response: Contact the Tivoli Storage Manager
administrator with the information provided in this
message.
FMV2202E Disk Full Error Accessing Disk Cache.
Explanation: A disk full error occurred attempting to FMV2218I The encryption key password for node
access or write to the specified disk cache file during a node name and server server name has
disk cache incremental backup. See the client error log been migrated.
for more detailed information.
Explanation: The format of the Tivoli Storage Manager
System action: Processing stops. password file has recently changed. The option
User response: This error can be resolved by freeing MIGRATEENCRYPTKEY is set and the stored
up space in the file system containing the cache file, or encryption key password was automatically migrated
specifying a different location for the cache file. Use the to the new format. This message confirms that the
diskcachelocation option to specify the location of the migration was successful.
cache file. System action: The encryption key password has been
migrated.
FMV2203E Error Accessing Disk Cache. User response: No response.
Explanation: An error occurred attempting to access
the specified disk cache file during a disk cache FMV2219E Cannot backup or archive files into
incremental backup. See the client error log for more filespace because it is owned by a TSM
detailed information. Tivoli Storage Manager. API application.
System action: Processing stops. Explanation: TSM Client cannot archive or backup
User response: None. files into a file space that is used a TSM API
application.

FMV2204E Disk cache restarted. System action: Processing stops.

Explanation: The length of an object name exceeded User response: Use separate node names for TSM
the configured disk cache key length during a disk Client and TSM API application(s).
cache incremental backup. The backup must be
restarted.. Tivoli Storage Manager. FMV2220E The cluster disk could not be put in
System action: Backup is restarted with a larger key maintenance mode.
length to accommodate the object name. Explanation: The system call to put the cluster disk in
User response: None required. The name of the object maintenance mode failed.
that caused the failure can be found in the dsmerror.log System action: Processing stopped.
file.
User response: Try the operation again. If the problem
continues, check the client error log for any other
FMV2206W The user must have root authority to use messages that might have been logged when this
the memory efficient backup disk cache message was written, and take the corrective action (if
method. The operation will continue any) suggested by those messages. Examine the
using memory efficient backup method Windows event log which may contain additional
without disk caching. information. See your system administrator or Tivoli
Explanation: None. Storage Manager administrator for further help.

System action: The operation continues without using

disk caching.
User response: None.

386 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2221W • FMV2228W

provided by the Tivoli Storage Manager snapshot

FMV2221W Java was not able to resolve the IP
providers be used instead of using the
address of your local machine due to
(-SNAPSHOTROOT) option. Processing will continue
network misconfiguration problems!
without the use of the Tivoli Storage Manager snapshot
Please verify your network and DNS
providers.
configuration are setup correctly. Note
that on UNIX machines the hostname System action: Processing continues without the use
must be reported correctly (the same) for of the Tivoli Storage Manager snapshot providers.
IPv4 and IPv6 communication methods
in the /etc/hosts configuration file. User response: See the appropriate Using the
Tivoli Storage Manager processing Backup-Archive Client book for your operating system
continues. for correct use of the named option.

Explanation: Java was not able to get the local host

address due to network misconfiguration problems. FMV2226I Filespace filespace-name is renamed to
old-filespace-name. unicode-filespace-name is
System action: Processing continues. recreated as a Unicode enabled
filespace. The current operation will
User response: Please verify your network and DNS
continue using the Unicode enabled
configuration are setup correctly. Note that on UNIX
filespace.
machines the hostname must be reported correctly (the
same) for IPv4 and IPv6 communication methods in the Explanation: Tivoli Storage Manager Unicode Client
/etc/hosts configuration file. See your system operates with Unicode enabled filespace. In order to
administrator or Tivoli Storage Manager administrator save your data there needs to be a one time automatic
for further help. rename of the existing MBCS filespace on the server. A
new Unicode enabled filespace is created on the server
and backup/archive continues.
FMV2223W Rejected unauthenticated
server-initiated session from peer name. System action: Processing continues.
Explanation: For security, the client will not accept User response: None.
server-initiated sessions from servers that have
authentication turned off.
FMV2227W Server option 'option-name' 'option-value'
System action: The client-server session is not opened, has not been applied on the client due
and the schedule is not executed. The scheduler to the client option
continues to wait for contact by a server that has SRVOPTSETENCRYPTIONDISABLED.
authentication turned on.
Explanation: The client option
User response: If the client system is supposed to SRVOPTSETENCRYPTIONDISABLED has been set to
accept scheduled events from the prompting Tivoli YES on the client thereby preventing the Tivoli Storage
Storage Manager server, either ask the Tivoli Storage Manager administrator from setting one of the
Manager server administrator to turn authentication on, following client options - ENCRYPTKEY GENERATE,
or do not use server-initiated sessions. If the client EXCLUDE.ENCRYPT, INCLUDE.ENCRYPT.
system is not supposed to accept scheduled events
from the prompting server, ask the Tivoli Storage System action: The option will be ignored.
Manager server administrator to remove the client node User response: None required.
name from the schedule on the prompting server.

FMV2228W Backup of VMware vCloud Director

FMV2225W User has specified 'SNAPSHOTROOT' vApp 'vApp name' in Organization VDC
option. snapshot provider snapshot backup 'Org VDC name' of organization 'Org
is not valid in conjunction with this name' completed. Some VMs were not
option. "SNAPSHOTROOT option will backed up. VMs: number of VM backed up
take precedence and processing will out of number of VMs in vApp VMs
continue without the use of a snapshot backed up successfully.
taken internally by Tivoli Storage
Manager. Explanation: The vApp backup operation completed
successfully. However, one or more VMs for the
Explanation: The (-SNAPSHOTROOT) option is specified vApp were not backed up. These VMs will
incompatible with Tivoli Storage Manager snapshot not be created during the restore operation.
providers such as Logical Volume Snapshot Agent, VSS
snapshot provider, JFS2 snapshot provider etc. which System action: Processing continues to the next vApp.
provide a comprehensive snapshot solution withot User response: Check the log file for this vApp for
having to use the (-SNAPSHOTROOT) option. It is more information about this message. Resolve the
strongly recommended that the snapshot capabilities

Chapter 6. FMV messages 387

FMV2229E • FMV2241T

problem, then try the operation again. failure might be caused by incorrect option settings.
System action: VMs for the specified vApps are not
FMV2229E Failed to initialize the vCloud protection backed up. Processing continues to the next vApp.
environment. See the local client error
User response: Make sure the VMCHost option
log for detailed error message
specifies a vSphere host that belongs to the protected
information.
vCloud Director. Verify that VMCUser and VMCPW
Explanation: The vCloud protection package could settings are correct. Also check the dsmerror.log file for
not be initialized. information that is related to this issue.
System action: The operation is stopped
FMV2236I The virtual machine 'VM-name' contains
User response: Make sure all options that are related
one or more disks that exceed the 2 TB
to the vCloud environment are specified correctly.
maximum size limit. These disks will be
Check the dsmerror.log file for detailed information.
excluded from the backup.
Explanation: The IBM Tivoli Storage Manager client
FMV2230E Failed to create vApp list according to
does not support backing up VMDKs that are greater
spec 'vApp specification'
than the supported limit.
Explanation: The vApp list was unable to be retrieved
System action: The virtual machine is backed up,
from the vCloud Director.
however the disks exceeding the limit are skipped.
System action: The operation is stopped
User response: Make sure the values specified in the FMV2238E VCDHOST option must be set before
VCDHost, VCDUser, VCDPW, and DOMAIN.VCD running this operation.
options are correct. Make sure the vCloud Director is
Explanation: VCDHOST option is missing.
alive.
System action: Operation cannot continue without this
option being set.
FMV2231E Failed to back up vApp properties for
vApp 'vApp name' User response: Add the option to the client options
file, either via the preferences editor or by manually
Explanation: A backup was not created for the
editing the file, or specify the option on the command
specified vApp.
line.
System action: Back up of the specified vApp stops.
Processing continues to the next vApp.
FMV2239W The annotations field contained too
User response: Check the dsmerror.log file for many characters and had to be
additional information. truncated.
Explanation: vSphere limits the size of the annotations
FMV2232E Failed to retrieve the list of VMs for to 2000 characters. Some special characters, such as
vApp 'vApp name' from the vCloud new lines, get encoded as multiple characters. This can
Director. lead to exceeding the limit even though the size may
appear to be within the limit.
Explanation: The VM information for the specified
vApp was not retrieved from the vCloud Director. This System action: The annotation field is truncated to
failure might be caused by the vCloud Director not less than 2000 characters so that the vSphere API will
being alive or accessible. not reject it.

System action: The VMs that compose the specified User response: Take care to avoid creating large
vApp are not backed up. Processing continues to the annotations that may exceed the 2000 character limit
next vApp. after special characters are encoded.

User response: Make sure that the vCloud Director is

alive and accessible. Check the dsmerror.log file for FMV2240T The basic verification of vApp 'vApp
specific errors that are related to this issue. name' succeeded.

FMV2233E Failed to get information from the FMV2241T The extended verification of vApp 'vApp
vSphere server for the VMs that name' succeeded.
compose vApp 'vApp name'.
Explanation: The VM information for the specified
vApp was not retrieved from the vSphere server. This

388 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2242E • FMV2250W

FMV2242E No nodes were found that matched the FMV2247E ASNODENAME option must be
input specification: node specification specified when running this command.
Explanation: An invalid node specification was Explanation: When running vCloud-related
entered. commands, ASNODENAME option must specify the
Provider vDC node.
System action: The operation was stopped.
System action: Operation cannot continue.
User response: Check documentation how to specify
nodes. User response: Specify the Provider vDC node as
ASNODENAME to the command.
FMV2243W An incompatible disk configuration is
detected. Individual SQL Database FMV2248E Failed to load or initialize the Java
Restore of some databases on this guest runtime library.
VM is not supported.
Explanation: The Java runtime library (libjvm),
Explanation: One or more SQL database files in this required by the vCloud Protection environment, cannot
operation are located on Dynamic and/or Guid be loaded, or initialization of Java runtime environment
Partition Table (GPT) style disks. Individual SQL failed
Database Restore is not supported from disks that are
System action: Operation is stopped
configured in this manner.
User response: For Linux operating system, verify that
System action: Backup of the full VM continues.
a link named 'jre', referencing the 'jre' directory under
User response: Issue a full VM restore to retrieve a your Java installation path, exists in the backup-archive
previous state of the SQL Server environment. client installation directory. If a link does not exist,
create the link (e.g. ln -s /opt/ibm/java-x86_64-70/jre
/opt/tivoli/tsm/client/ba/bin/jre). Alternatively,
FMV2244W The virtual machine contains one or
modify LD_LIBRARY_PATH to include the path to
more disks that exceed the maximum
libjvm.so (e.g. export
size limit. Specify the
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/
'-VMSKIPMAXVMDKS=yes' option to
tivoli/tsm/client/ba/bin:/opt/ibm/java-x86_64-70/jre/
exclude these disks from the backup.
bin/classic). For Windows operating system, verify that
Explanation: The IBM Tivoli Storage Manager client the JRE directory exists under the client installation
does not support backing up VMDKs that are greater directory. Reinstall the backup-archive client if
than the supported limit. necessary.

System action: The virtual machine is not backed up.

FMV2249W A virtual machine named 'vmname' exists
User response: Specify the on this system. Do you want to replace
'-VMSKIPMAXVMDKS=yes' option to exclude these the existing virtual machine?
disks from the backup.
Explanation: Restoring this virtual machine will stop
and delete the existing virtual machine and all of its
FMV2245E Virtual machine backups and restores files. To protect application data, stop any applications
are not supported on 32 bit data movers. that are running, and then shut down the virtual
Explanation: Virtual machine operations such as machine before you restore it.
backups and restores are not supported on 32 bit Data System action: If the user chooses to continue, the
Movers. system will stop and delete the existing virtual machine
System action: The operation is not performed. and all of its files.

User response: Update to a 64 bit Data Mover and User response: Choose whether to replace the existing
retry the operation. virtual machine.

FMV2246W Failed to disable maintenance mode for FMV2250W A Tivoli Storage Manager core file or
vApp vApp name. crash report was found: filename

Explanation: The client has tried to disable the Explanation: The presence of a core dump or crash
maintenance mode of this vApp. This operation failed. report indicates a process has abnormally terminated.

System action: Operation continues. System action: The core file or crash report name is
reported in the message. Processing continues.
User response: Check whether the vApp is still in
maintenance mode. If yes, disable it manually. User response: Review the error log for any other

Chapter 6. FMV messages 389

FMV2253W • FMV2316E

error messages that may help diagnose the cause of the failed file can be identified. Enable HSM Logging if
core dump. If possible, correct any issues found. As a failed failed file cannot be identified and wait for new
core dump is generally caused by a programming error, occurrence. (HSM Logging allows you to map between
save the file noted in this message and contact IBM the token displayed from the FMV message and the
technical support. recalled file) Static errors: Restore the file from backup.

FMV2253W The version of the message catalog, FMV2312E -DELTYPE=ALL is not allowed for
catalogversion, in use by Tivoli Storage DELETE BACKUP -OBJTYPE=VM.
Manager does not match the version of
Explanation: DELTYPE=ALL is not a valid option
Tivoli Storage Manager, clientversion
value when deleting VM backup objects.
Explanation: A check of the catalog version indicates
System action: The command is not executed.
the catalog and Tivoli Storage Manager are not the
same version. This may lead to missing or incorrect User response: If you wish to delete all backups for a
messages being used. VM node, use the DELETE FILESPACE command.
System action: Processing continues.
FMV2313E -FILELIST is not allowed for DELETE
User response: Review the installation of Tivoli
BACKUP or EXPIRE when
Storage Manager, verify the message catalog files match
-OBJTYPE=VM.
the installed version of Tivoli Storage Manager.
Re-installation of Tivoli Storage Manager may be Explanation: -filelist is not a valid option value when
required, or a system reboot may be required to deleting or expiring VM backup objects.
complete the installtion.
System action: The command is not executed.

FMV2254E program-name with session id sessid User response: If you wish to delete or expire all
aborted recall for token token. ERRNO backups for a VM node, use the DELETE FILESPACE
errno : errno-text was set. See message command.
explanation.
Explanation: A recall was aborted from HSM. The FMV2314E No VM backup exists for VM-Name.
ERRNO set from HSM explains why the recall was Explanation: The Tivoli Storage Manager server has
aborted. Transient errors (The operation must be retried no record of a VM backup for the VM name provided.
after the associated problem was solved): ENOSPC : No The backup might have been deleted, or the VM name
space left on device. HSM couldn't free space for the spelled incorrectly.
recall. ENOMEM : Not enough memory available to
acquire the required resocurces for the recall. ESRCH : System action: The command is not executed.
The internal communication between master and User response: If spelling is the problem, correct it
distributor failed. EACCES : Most common errno. One and resubmit the command.
of the failures below: - The recall daemon are exiting.
System cleanup ongoing. - Recovery of previously
failed nodes is ongoing. - File is immutable and can't FMV2315E -PICK is not allowed for EXPIRE when
be opened for write / truncate. - The HSM internal -OBJTYPE=VM.
processing failed due to issues with the DMAPI. Explanation: -pick is not a valid option value when
EBUSY : HSM can't acquire exclusive rights on the file. expiring VM backup objects.
EFAULT : The system detected an invalid address in
attempting to use an argument. EINTR : The DMAPI System action: The command is not executed.
implementation allows interruption and the process
User response: If you wish to expire all VM nodes,
was interrupted. EINVAL : The requested right is not
use the DELETE FILESPACE command.
valid or the session or token is not valid or token was
DM_NO_TOKEN. Static errors (The operation can't be
fullfilled. Recall not possible): EIO : The stub file is FMV2316E Wildcards are not allowed in the VM
orphan. ENOENT : The file doesn't exist in the file name argument.
system. EBADF : The file handle does not refer to an
Explanation: When expiring or deleting a VM backup,
existing or accessible object.
the VM name must be specified exactly. The EXPIRE
System action: The recall request was aborted from -OBJTYPE=VM command processes only one backup
the HSM service. on each invocation. When -INACTIVE is present the
DELETE BACKUP -OBJTYPE=VM command displays
User response: Transient errors: Solve problem
all versions of a single VM backup in a list from which
indicated from the errno. On GPFS platforms: Use
to choose. If -INACTIVE is not present, this command
command dsmmigfs q -d -n=all to verify HSM and
expires the current active VM backup.
GPFS are running properly. Retry the recall operation if

390 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2317E • FMV2326W

System action: The command is not executed.

FMV2322I EXPIRE with -OBJTYPE=VM finished
User response: Specify only one VM name without without failures.
wild cards. It may be in upper or lower case.
Explanation: The EXPIRE command executed
successfully.
FMV2317E Deletion of VM object VMname failed.
System action: Control returns to the command line.
Reason:
User response: No action is required, this message is
Explanation: The transaction which deletes the named
informational.
VM object failed at the server. The reason code ....?????
System action: The deletion is skipped and processing
FMV2323E The user ID and password for VMware
continues with the next selection, if any.
vCloud Director 'vCD host name' are not
User response: Consult the error log for specific set.
reasons for this failure.
Explanation: The user ID and password for VMware
vCloud Director could not be read from encrypted
FMV2318E Command with -OBJTYPE=VM requires password file.
exactly one non-option argument
System action: Processing stops.
Explanation: This command accepts only a single VM
User response: Issue the dsmc SET PASSWORD
name as an argument. Either no arguments were
-type=VCD 'vCloud Director hostname' 'userid'
entered or more than one appeared on the command
'password' command to save an encrypted password.
line.
System action: The command is not executed.
FMV2324W WARNING: The VMware vCloud
User response: Specify only one VM name without Director user ID <hostuserid> read from
wild cards. It may be in upper or lower case. the password file is different from the
VCDUser option value <vmcuserid>.
Using stored value.
FMV2319W DELETE BACKUP -OBJTYPE=VM
finished with failures. Explanation: All user IDs that are specified in the
TSM.PWD file and in the VCDUSER option must be
Explanation: One or more deletions failed. the same.
System action: The VM backups which failed have System action: Processing stops.
been reported in previous messages. Processing
continues with the next selection, if any. User response: Contact the Tivoli Storage Manager
administrator with the information that is provided in
User response: Consult the previous error messages this message.
for the cause of each failure.

FMV2325E Error Accessing Snapshot Differential

FMV2320I DELETE BACKUP -OBJTYPE=VM Change Log for filer '' volume '', see
finished without failures. client error log for more information.
Explanation: All VM backups selected for deletion Explanation: The Snapshot Differential Change Log
were deleted. needed needed to backup the specified filer volume
System action: Control returns to the command line. could not be accessed

User response: No action is required, this message is System action: The backup of the specified volume
informational. fails.
User response: Ensure that the client staging directory
FMV2321W EXPIRE with -OBJTYPE=VM finished where change logs are located is accessible.
with failures.
Explanation: The command did not complete, no FMV2326W Corrupt Snapshot Differential Change
objects were expired. Log detected, change log will be reset
and a full progressive incremental will
System action: The VM expire which failed has been be performed.
reported in previous messages.
Explanation: A corrupt snapshot differential change
User response: Consult the previous error messages log for the filer volume being backed up was detected.
for the cause of the failure.
System action: The change log will be reset and a full

Chapter 6. FMV messages 391

FMV2327I • FMV2335E

progressive incremental with a new base snapshot will System action: None.
be performed.
User response: Specify another Hyper-V VM name or
User response: none. VMList parameter that exists on the server.

FMV2327I Creating Snapshot Differential Change FMV2332E Failed to log on to the vCloud Director.
Log. Authentication failed.
Explanation: A new snapshot differential change log Explanation: The vCloud credentials were rejected by
was created. the vCloud Director.
System action: This message is for informational System action: The operation is stopped
purposes only.
User response: Update username and password for
User response: No action is required. the vCloud Director.

FMV2328I Using Snapshot Differential Change FMV2333E Failed to establish connection to the
Log. vCloud Director.
Explanation: A snapshot differential change log is Explanation: A connection cannot be established to
being used for the backup. the vCloud Director on the host that is specified by the
VCDHost and VCDPort options.
System action: This message is for informational
purposes only. System action: The operation is stopped
User response: No action is required. User response: Verify that the values of the VCDHOst
and VCDPort options are valid, network connectivity to
the host exists, and that the vCloud Director service is
FMV2329W Down level Snapshot Differential
running.
Change Log detected, Change Log will
be reset and a full progressive
incremental will be performed. FMV2334E An operation requiring the Windows
Management Instrumentation (WMI)
Explanation: none.
service has failed with the error
System action: none. 'errorstring'. Unable to connect to the
Hyper-V namespace. Confirm that
User response: none. Hyper-V is installed on the backup
node.
FMV2330E Failed to unfreeze the VSS writers Explanation: The Windows Management
because the snapshot time exceeded the Instrumentation (WMI) namespace
10 second timeout limitation. "root\virtualization\v2" for Hyper-V could not be
Explanation: Microsoft VSS has a 10 second timeout found. This namespace is installed with Hyper-V. If
limitation between freeze and thaw events for VSS Hyper-V is installed, Hyper-V is not in a good state.
writers on a VM. When the snapshot time exceeds the System action: Creating a connection to the Hyper-V
10 second timeout limit, the VSS writers return to a WMI provider.
'failed' state. This failed state occurs because the VSS
provider did not thaw the VSS writers within the User response: Check that Hyper-V is installed. If
allowed time. Hyper-V is not installed, install Hyper-V before
attempting this operation again.
System action: Processing stops.
User response: Check the event log. Ensure that the FMV2335E An operation requiring the Windows
writers on the guest VM are in 'stable' state before Management Instrumentation (WMI)
trying an application protection VM backup operation service has failed with the error
again. A snapshot operation must be completed within 'errorstring'. The WMI service is in the
10 seconds. shutting down or shutdown state.
Restart the service and try again.
FMV2331W No match found on the server for the Explanation: The Windows Management
Hyper-V VM name or VMList 'string' Instrumentation (WMI) service has received a request
entered to shutdown or has been shutdown due to an external
Explanation: No match found on the server for the error. An internal operation which requires WMI has
Hyper-V VM name or VMList parameter entered. been attempted and failed. The requested operation is
unavailable while WMI is shutdown.

392 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2336W • FMV2342E

All Hyper-V operations require the Windows corruption if a backup of the original is followed by a
Management Instrumentation service. backup of the replica.
System action: An internal Tivoli Storage Manager System action: A backup request of a virtual machine
operation involving Windows Management replica is being processed.
Instrumentation has occurred.
User response: Configure IBM Tivoli Storage Manager
User response: Restart the Windows Management to back up only the original virtual machine or the
Instrumentation service. replica. Alternatively, one can change the name of the
replica compared to the original virtual machine; and
the replica will back up to a separate filespace.
FMV2336W Tivoli Storage Manager has detected
that the following Hyper-V virtual
machine "virtual_machines" has an FMV2339W The Hyper-V VM 'vmname' is in a
interrupted incremental backup chain. "branch" state compared to the last
Performing a full backup on the backup. Incremental Forever -
specified Hyper-V virtual machine. Incremental backup cannot be
performed. An Incremental Forever -
Explanation: The last operation of the virtual machine
Full backup will be performed instead.
was a restore; or an unknown party has performed
incremental backup operations on the listed virtual Explanation: The VM state is in a "branch" compared
machine. To prevent backup corruption a full backup to the last backup. This causes a fallback to Incremental
will be performed instead. Forever - Full as backup consistency in this state is not
guaranteed.
System action: Tivoli Storage Manager has detected
that a virtual machine has an interrupted incremental System action: An Incremental Forever - Full backup
backup chains. will be performed.
User response: A full backup is performed instead of User response: None.
an incremental.
FMV2340W The target virtual machine 'VM-name'
FMV2337E Tivoli Storage Manager was unable to exists, use the REPLACE option to
take cluster resource 'resourcename' overwrite.
offline. The current operation requires
Explanation: The specified target VM exists and the
the resource to be offline. Turning the
user specified not to allow restore to replace existing
cluster resource off failed with rc=rc.
machines.
Explanation: The cluster resource was not taken
System action: The virtual machine is not restored.
offline within the time limit or an attempt was made to
take offline a failed cluster resource. User response: Specify a different virtual machine as a
restore target or specify that existing virtual machines
System action: The current operation stops.
can be replaced.
User response: Check that the cluster resource is not
in a failed state. Verify that the cluster resource can be
FMV2341E The target virtual machine 'VM-name'
taken offline.
cannot be restored: The guid differs
from the backup copy.
FMV2338W Tivoli Storage Manager has detected a
Explanation: The specified target VM exists and has a
request to backup a virtual machine
different guid than the virtual machine was backed up
replica. The state of the replica
with..
'vmreplicaname', ID='vmid' may differ
from the original virtual machine. If the System action: The virtual machine is not restored.
names of the original virtual machine
and the replica are identical the same User response: Specify a different virtual machine as a
filespace will be used. The data may restore target or delete the specified target virtual
become unrecoverable because the state machine.
of the original virtual machine and the
replica may differ. FMV2342E The specified restore target 'VM-name' is
Explanation: Backups of an original virtual machine ambiguous: Multiple virtual machines
and their replica overwrite each other as their name with the same name exist.
and ID are usually identical. Virtual machine replicas Explanation: The specifed restore target is ambiguous,
are taken in definite time intervals. Between these multiple virtual machine with the same name exist.
intervals the data on the original and the replica may
differ. In some occasions the difference may cause data System action: The virtual machine is not restored.

Chapter 6. FMV messages 393

FMV2343E • FMV2350E

User response: Specify a different virtual machine as a

FMV2347E IBM Tivoli Storage Manager application
restore target.
protection cannot be used. The correct
Java Runtime Environment version has
FMV2343E A snapshot of Virtual machine 'vmname' not been detected on machine. A Java
cannot be taken because a physical disk Runtime Environment version or higher
attached. is required to run this program. If you
have already installed this level of Java
Explanation: The Volume Snapshot Service (VSS) is version on this machine, please ensure
unable to snapshot a virtual machine with a physical that the correct Java executable is on
disk. your PATH and start the program again.
System action: The full backup of the the virtual Explanation: IBM Tivoli Storage Manager application
machine finished with failures. The next virtual protection vm backup cannot be started because the
machine in the backup will be processed. Java runtime environment does not meet the
User response: Do not include this virtual machine in requirements.
domain.vmfull for backup. A snapshot of this virtual System action: Processing stops.
machine cannot be taken.
User response: Verify that the correct java executable
is on your PATH or install the required version of Java
FMV2344E 'drive-name1' is a disk witness. runtime environment and run the backup again.
Explanation: The indicated volume is a disk witness.
Because the CLUSTERNODE option is set to YES, the FMV2348E Mount proxy host 'remoteversion' does
volume cannot be backed up or archived. not have a supported operating system.
System action: Processing stops. Explanation: The mount proxy node needs to be
User response: If the CLUSTERNODE option is configured on a supported operating system.
incorrectly set to YES, then change the option to NO System action: The calling procedure returns and
and try the operation again. Otherwise see the client control is passed back the user.
manual for further information about configuring the
Tivoli Storage Manager client to run in a cluster User response: Check the documentation for a list of
environment. supported operating systems. Configure the mount
proxy node on a supported operating system.

FMV2345W The virtual machine named '' was found

to have an old snapshot ''. A command FMV2349W The virtual machine named '' was found
was sent to the vCenter to remove it. to need snapshot consolidation. A
command was sent to the VMware
Explanation: During the snapshot clean-up process the vCenter to perform consolidation.
backup-archive client found old snapshots on the
virtual machine. A remove snapshot command was sent Explanation: During the virtual machine backup
to the VMware vCenter to remove the old snapshots. process the backup-archive client found the virtual
machine needed snapshot consolidation. A command
System action: Processing continues was sent to the VMware vCenter to perform
User response: Confirm that the the virtual machine is consolidation.
free of all snapshots before the next scheduled backup. System action: Processing continues
User response: Confirm that the virtual machine is
FMV2346E Expiration of VM object VMname failed. clean of all snapshots and snapshot delta files before
Reason: the next scheduled backup.
Explanation: The transaction which expires the named
VM object failed at the server. The reason code ....????? FMV2350E Virtual machine 'VM name' will not be
System action: The expiration is not completed. backed up because it contains at least
one of the following unsupported
User response: Consult the error log for specific special characters \ / : ; , * ? " ' < > |
reasons for this failure.
Explanation: The specified virtual machine contains
characters that are not supported for virtual machine
backup and restore operations.
System action: The backup for the specified virtual
machine fails.

394 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2351E • FMV2414E

User response: Rename the virtual machine so that it

FMV2410E Instant Restore information for the
does not contain any of the specified special characters.
specified virtual machines was not
found.
FMV2351E Duplicate virtual machine name
Explanation: The Tivoli Storage Manager server does
'vmname' was detected in the same
not contain Instant Restore information for the specified
backup operation. Backups of a virtual
virtual machines. Or, the virtual machines were
machine can not continue without a
specified incorrectly.
unique object name.
System action: Processing stops.
Explanation: The backup of the virtual machine failed
because no unique object name is available. User response: Issue the QUERY VM *
-VMRESTORETYPE=ALLTYPE command. This
System action: The backup for the specified virtual
command queries all active Instant Access, Restore, and
machine fails. The next virtual machine to back up will
Disk sessions available on the Tivoli Storage Manager
be processed.
server.
User response: Rename the virtual machine so that it
is unique among virtual machines for the node.
FMV2411E Instant Restore/Access of virtual
machine 'vmname' failed with rc =
FMV2352E Validation of virtual machine 'vmname' return-code
configuration returned the following
Explanation: An error happened during processing of
message from Hyper-V: hypervmessage
an Instant Restore or Access. See previous output what
This message indicated that the virtual
happens exactly.
machine could not be restored until the
message from Hyper-V is addressed. System action: Processing stops.
Explanation: When validating the virtual machine User response: Check the error log for information
with Hyper-V a message was returned that prevents about how to resolve this error.
the virtual machine restore from continuing.
System action: Cannot continue with restore until the FMV2412E IBM Tivoli Storage Manager Recovery
issue is resolved. Agent is not installed.
User response: Resolve the issue outlined by the Explanation: IBM Tivoli Storage Manager Recovery
message. Agent is not installed.
System action: Processing stops.
FMV2408I The virtual machine named 'VMNAME'
User response: Ensure that IBM Tivoli Storage
is ready for Instant Access
Manager Recovery Agent is correctly installed and
Explanation: The Instant Access operation for the configured.
specified virtual machine successfully completed.
System action: None. FMV2413E Cannot find the Recovery Agent shell
command in the expected installation
User response: None
path. Ensure that Tivoli Storage
Manager for VE is correctly installed
FMV2409E The Instant Restore type was not and configured.
identified.
Explanation: The Recovery Agent shell command was
Explanation: The client encountered a connection not found in the expected installation path.
error when querying the Tivoli Storage Manager server
System action: Processing stops.
for Instant Restore and Access information.
User response: Ensure that Tivoli Storage Manager for
System action: Processing stops.
VE is correctly installed and configured.
User response: Verify that the client is connected to
the server. Then run the operation again. Check with
FMV2414E An error occurred when the hostname
the command QUERY SESSION what is the cause for
for the local machine was called.
the connection issue. Also check the dsmerror.log for
additional information Explanation: The system call gethostname failed.
System action: Processing stops.
User response: Verify that the configuration of the
network interface is correct.

Chapter 6. FMV messages 395

FMV2415E • FMV2426E

FMV2415E An error occurred when the machine FMV2420E Cannot detect storage device
address information was called. information.
Explanation: The system call getaddrinfo failed. Explanation: Storage device information cannot be
retrieved.
System action: Processing stops.
System action: Processing stops.
User response: Verify that the configuration of the
network interface is correct. User response: Ensure that the communication with
the ESX host is working. Also, review the log messages
on the ESX host.
FMV2416E An error occurred when the machine
name information was called.
FMV2421E Cannot detect the iSCSI initiator on the
Explanation: The system call getnameinfo failed.
ESXi host.
System action: Processing stops.
Explanation: The iSCSI initiator name of the ESXi host
User response: Verify that the configuration of the cannot be detected.
network interface is correct.
System action: Processing stops.
User response: Ensure that the communication with
FMV2417E Unexpected communication method.
the ESX host is working. Also, review the log messages
Only TCP and TCPv6 are accepted.
on the ESX host.
Explanation: An unexpected communication method
was detected.
FMV2422E Cannot detect the iSCSI Host Bus
System action: Processing stops. Adapter.

User response: Verify that the communication method Explanation: The iSCSI adapter was not detected.
for Tivoli Storage Manager is correct. Use either TCP or
System action: Processing stops.
TCPv6.
User response: Ensure that the communication with
the ESX host is working. Also, review the log messages
FMV2418E Unable to read or write to the local
on the ESX host.
instant restore data. filename File cannot
be accessed or is damaged.
FMV2424E Cannot find the ESX host 'ESXHOST' in
Explanation: Instant access and instant restore
the vCenter.
operations require read/write access on the local data
mover to store data. Explanation: The specified ESX host cannot be found
in the vCenter.
System action: Processing stops.
System action: Processing stops.
User response: To store the instant restore restore
data, the data mover application requires read and User response: Ensure that the specified ESX host is in
write access to the C:\Documents and the vCenter. Ensure that the name of the ESX host is
Settings\AllUsers\Application Data\Tivoli\TSM\ or correct. Alternatively, specify another ESX host.
C:\ProgramData\Tivoli\TSM folder. Set the access
rights to this directory so that your user has the correct
FMV2425E Cannot connect to the ESX host
rights. If the file was damaged it can be helpfull to
'ESXHOST'
replace the current version with the .bak file.
Explanation: A connection to the specified ESX host
cannot be made
FMV2419E The datastore does not have enough free
space for the instant restore operation. System action: Processing stops.
Explanation: The space on the selected datastore is not User response: Ensure that the specified ESX host is
sufficient for the instant restore operation. connected to the vCenter and the network.
Alternatively, specify another ESX host.
System action: Processing stops.
User response: Increase the datastore space or choose
FMV2426E The ESX host 'ESXHOST' is not powered
a different datastore.
on.
Explanation: The specified ESX host is not powered
on.
System action: Processing stops.

396 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2427E • FMV2444E

User response: Turn on the power to the ESX host.

FMV2433E The '-vmtempdatastore' option must be
Alternatively, specify another ESX host.
specified for an instant restore
operation.
FMV2427E The ESX host 'ESXHOST' is in
Explanation: You must specify two different
maintenance mode.
datastores for Storage vMotion to work. Use the
Explanation: The specified ESX host is in maintenance '-vmtempdatastore' option to specify a temporary
mode. A connection cannot be made to this host. datastore.

System action: Processing stops. System action: Processing stops.

User response: Change the ESX host back to normal User response: Specify a temporary datastore.
mode and try again. Alternatively, specify another ESX
host.
FMV2434E The datastore 'DATASTORE' was not
found on the host 'ESXHOST'.
FMV2428E The ESX host 'ESXHOST' is not
Explanation: The specified datastore cannot be found
connected.
on the ESX host.
Explanation: The specified ESX host is not connected
System action: Processing stops.
in the vCenter.
User response: Ensure that the specified datastore is
System action: Processing stops.
on the ESX host. Alternatively, specify another
User response: Connect the ESX host in the vCenter datastore.
and try again. Alternatively, specify another ESX host.
FMV2435E TDP for VMware Recovery Agent
FMV2430E Cannot find the datacenter detected the following failure while
'DATACENTER'. trying to mount a snapshot of VM 'VM'
from disc='disk-label':
Explanation: The specified Datacenter cannot be FBSxxxxE-error-message
found in the vCenter.
Explanation: The attempt to mount a VM disk as a
System action: Processing stops. iSCSI device failed.
User response: Ensure that the specified datacenter is System action: The operation was stopped.
in the vCenter. Alternatively, specify another datacenter.
User response: Check the FBSxxxxxE error message,
resolve the problem, and try the operation again.
FMV2431E Cannot find the temporary datastore
'TEMPDATASTORE' on the ESX host
'ESXHOST'. FMV2436E IBM Tivoli Storage Manager Recovery
Agent detected the following failure
Explanation: The specified temporary datastore cannot while trying to dismount a snapshot of
be found on the specified ESX host. VM 'VM' from target 'target':
System action: Processing stops. FBSxxxxxE-error-message

User response: Ensure that the specified datastore is Explanation: The snapshot for the specified VM could
on the ESX host. Alternatively, specify another not be dismounted from the iSCSI target.
datastore. System action: The operation was stopped.
User response: Check the FBSxxxxE error message,
FMV2432E The temporary datastore resolve the problem, and try the operation again.
'TEMPDATASTORE' is the same as the
target datastore 'DATASTORE'.
FMV2444E Cannot find the datacenter for host
Explanation: The specified temporary datastore must 'ESXHOST'.
be a different datastore than the one where the machine
is restored to. You must specify two different datastores Explanation: Unable to determine the datacenter
for Storage vMotion to work. where the ESX host is located.
System action: Processing stops. System action: The operation was stopped.
User response: Specify another datastore as a User response: Check that the vCenter of the ESX host
temporary datastore. is in a datacenter and that the user has the proper
authority to access this information.

Chapter 6. FMV messages 397

FMV2445E • FMV2463W

FMV2445E Virtual machine 'VM' is running. You FMV2454E An error occurred when the iSCSI target
cannot delete this VM. target_name was disconnected from the
ESX host bus adapter.
Explanation: You cannot delete a virtual machine that
is running. Explanation: An error occurred when a specific iSCSI
target was disconnected from the ESX host bus adapter.
System action: The operation was stopped.
System action: The cleanup operation is stopped.
User response: Ensure that you have the proper
authority to power off virtual machines, then power off User response: Run the cleanup process after you fix
and delete the VM. any problems with the ESX host bus adapter.

FMV2447E Failed to delete VM 'VM' from the ESX FMV2455I The virtual machine has been started.
host. You can use the machine after it has
booted, or you can connect to it and
Explanation: You cannot delete the virtual machine
manage its settings through the vCenter
form the ESX host.
console.
System action: The operation was stopped.
Explanation: The virtual machine is being started.
User response: Ensure that you have the proper
System action: Processing continues.
authority to delete virtual machines, then delete the
VM. User response: While the boot is in progress, you can
connect to the virtual machine and view or manage
BIOS settings, manage the bootloader options, or
FMV2448E Mount command failed. Command was
perform other tasks. After the boot process completes,
COMMAND Shell command returned:
you can use the virtual machine and its applications
RESULT
and resources.
Explanation: The TDP mount command was not
successful.
FMV2462E Unable to start the vMotion task for
System action: The operation was stopped. virtual machine 'vm_name'.

User response: Determine the problem from the Explanation: An instant restore of the specified virtual
information that was returned for the TDP mount machine was attempted but failed. The client could not
command. Resolve the problem, then run the command start a vMotion task to migrate the virtual machine.
again.
System action: The Instant Restore operation stops.
User response: Examine the client dsmerror.log file to
FMV2452E num_discovered iSCSI devices were
see if a log entry indicates why the vMotion task failed.
discovered on the ESX host, while
Additional information about the failure might also be
num_mounted were expected.
available in the vCenter server, on the Task and Events
Explanation: After the ESX host bus adapter was tab for the ESXi host that you were migrating the VM
scanned, the number of devices that were discovered is from. If possible, use the log and event records to
different from the number of mounted devices. determine what caused the vMotion task to fail and fix
it. Then, clean up the virtual machine (use the Restore
System action: The Instant Restore or Instant Access VM command with the -VMRESToretype=VMCLeanup
process is stopped. option) and restart the vMotion task. If you cannot
User response: Verify that the Tivoli Storage Manager restart the task, suspend the virtual machine and use
mount is configured to use the correct ESX host IP. To the vSphere web client to start the virtual machine
clean the environment, you must run the cleanup migration from one host to another.
process.
FMV2463W Instant Restore information cannot be
FMV2453E An error occurred when the host bus saved on the server.
adapter was scanned. Explanation: An error occurred when Instant Restore
Explanation: An error occurred when the ESX host information was being saved on the server. The Instant
bus adapter was scanned. Restore process is still running.

System action: The Instant Restore, Instant Access, or System action: The operation continues.
cleanup process is stopped. User response: The client dsmerror.log file might
User response: Run the cleanup process after you fix contain information to help troubleshoot the reason for
any problems with the ESX host bus adapter. this error. Let the Instant Restore process complete on

398 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2464E • FMV2471E

its own. You might need to run a clean up operation on destroy all data and delete the virtual machine from the
the virtual machine. Use the Restore VM command, server. Press any other key to continue without
and specify the -VMRESToretype=VMCLeanup option. deleting.

FMV2464E Unable to delete Instant Restore FMV2467W Unable to delete the snapshot that was
information from the server. created for the virtual machine named
'vm_name'
Explanation: An error occurred while attempting to
delete Instant Restore information from the server. Explanation: When a virtual machine is restored by an
instant restore operation, a snapshot is created to store
System action: The Instant Restore operation
all data that were written to the virtual machine disks.
continues.
When the restore is completed, the ESXi host deletes
User response: The most likely reason for this error is the snapshot. The snapshot for the specified virtual
that an FMV2463W warning previously occurred, and machine could not be deleted.
there is no data to delete. If you have not previously
System action: Operation continues.
seen an FMV2463W message, the client dsmerror.log
file might contain information to help you troubleshoot User response: Examine the vSphere log to determine
this error. Clean up the virtual machine to remove old why is it not possible to delete the snapshot and
information from the server. Use the Restore VM resolve the problems that prevent the deletion. Then,
command, and specify the delete the snapshot by using the snapshot manager.
-VMRESToretype=VMCLeanup option.
FMV2468E The necessary iSCSI targets could not
FMV2465E An error occurred during a storage be found on the ESX host.
vMotion operation.
Explanation: An instant restore operation was
Explanation: A storage vMotion task failed while initiated and one or more of the required iSCSI targets
trying to migrate a running virtual machine. could not be found on the ESXi host.
System action: The Instant Restore operation stops. System action: Processing stops.
User response: Examine the client dsmerror.log file to User response: Verify that the IP address that was
see if a log entry indicates why the vMotion task failed. specified with the -VMISCSISERVERADDRESS
Additional information about the failure might also be parameter is correct.
available in the vCenter server, on the Task and Events
tab for the ESXi host that you were migrating the VM
FMV2469E Unable to remove the iSCSI target.
from. If possible, use the log and event records to
determine what caused the vMotion task to fail and fix Explanation: An error occurred while trying to
it. Then clean up the virtual machine (use the Restore remove an iSCSI target.
VM command with the -VMRESToretype=VMCLeanup
option) and restart the vMotion task. If you cannot System action: Processing stops.
restart the task, suspend the virtual machine and use User response: Check vSphere client log file for the
the vSphere web client to start the VM migration from reason this operation failed and remove the iSCSI
one host to another. target. To remove the failed iSCSI static targets go to
your ESXi host Configuration -> Storage Adapters ->
FMV2466W If you continue you will lose all data Select the iSCSI Adapter -> right click on it -> Click
created on this virtual machine. The Properties -> Static Discovery and select the failed
virtual machine will also be removed iSCSI targets and remove them.
from the ESXi host. Are you sure that
you want to do this? Press Y the virtual FMV2471E Unable to stop the vMotion Task 'task'.
machine data and remove it from the
ESXi host. Press any other key to Explanation: The specified vMotion task could not be
continue without deleting data or the stopped.
VM. System action: The instant restore operation is
Explanation: You are performing an operation that, if stopped.
allowed to continue, will delete all data that was User response: Examine the vSphere log to determine
created after this virtual machine was created. why the migration cannot be stopped. Resolve the
System action: If Y is pressed, the Instant Restore problem and cancel the vMotion task. Then, use the
operation is stopped, and a cleanup operation is -VMRESToretype=VMFULLCleanup option on the
performed Restore VM command to remove any files or other

User response: Respond to the prompt. Press Y to

Chapter 6. FMV messages 399

FMV2472E • FMV2490E

resources that were created by the instant restore

FMV2476E A restore location must be specified via
operation.
the TARGETPATH option when
restoring to a different virtual machine
FMV2472E Cannot detect the LUN for the attached name.
RDM devices for virtual machine named
Explanation: A restore location must be specifed via
vmname'. The restore operation for this
the TARGETPATH option when restoring to a different
virtual machine cannot be completed.
virtual machine name specified by the VMNAME
Explanation: The LUNs for the RDM devices use by option.
the specified virtual machine are either missing, are
System action: The virtual machine is not restored.
mapped to an other machine, or the device name and
the LUN do not match. User response: Specify a restore location with the
TARGETPATH option.
System action: The restore operation is stopped.
User response: For restore operations where
FMV2484I Virtual Machine 'vm_name' was
vmrestoretype=instantrestore or
successfully restored
vmrestoretype=instantaccess, verify that the iSCSI
server address and the VMkernel port binding match. Explanation: The Virtual Machine was successfully
Verify this information by checking the following restored.
things: 1. Check the Data Protection for VMware
System action: None.
configuration file TDPVMwareMounter.conf and verify
that the iSCSI server address is bound to the correct User response: None
network card and segment. 2. Use the vSphere client to
connect to your ESXi host. In vSphere, select
Configuration->Storage Adapters to display a list of the FMV2485E Cannot query the Tivoli Storage
iSCSI adapters. Right click the adapter that you are Manager server to get instant access
verifying. Then, select Properties ->Network information
Configuration. In the VMkernel Port Bindings Details Explanation: The server did not respond to the query
output, verify that the VMkernel Adapter is on the for instant access information.
same subnet that the datamover node is on.
System action: The virtual machine cleanup operation
is halted.
FMV2473E Unable to create a Snapshot of the
virtual machine named 'vm_name'. User response: Examine the dsmerror.log file and the
Tivoli Storage Manager server activity logs to
Explanation: An instant restore operation was determine the cause of this error.
attempted for the specified virtual machine. The
snapshot that is used to restore the virtual machine
could not be created. FMV2488E Error mounting the iSCSI device.

System action: The instant restore operation stops. Explanation: An error occurred while trying to mount
the iSCSI device. Check the dsmerror.log file to
User response: Examine the vCenter logs to determine determine the cause of this error.
why the snapshot could not be created and try the
instant restore operation again. System action: The operation was stopped.
User response: No action is required.
FMV2474E Unable to cleanup after an instant
restore operation for the virtual machine FMV2490E Could not turn off the VM that is
named 'vm_name', because vMotion task named 'VM' .
is still running.
Explanation: The specified virtual machine could not
Explanation: An instant restore operation is still be powered off. This prevents attempts to clean up the
running for the specified virtual machine. resources that were created to restore the virtual
System action: The cleanuop operation stops. machine.

User response: Use the query command to check on System action: The restore operation was stopped.
the status of the instant restore operation. Examine the User response: Turn off the virtual machine and then
vCenter to determine the status of the vMotion task. If delete it using the vSphere web client.
you want to stop the instant restore, cancel the
operation in the DP VMware GUI or stop the vMotion
task from the vCenter interface. Then, start the cleanup
operation again.

400 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2513I • FMV2520E

to the vMotion documentation to get details about the

FMV2513I The virtual machine has no disks
manual recovery process.
attached
Explanation: The virtual machine exists, but it does
FMV2517E Cannot query the Tivoli Storage
not have any disks attached. The machine can be
Manager server to get instant restore
cleaned up.
information
System action: None.
Explanation: The server did not respond to the query
User response: None for instant restore information.
System action: The virtual machine clean up
FMV2514I Disk status cannot be determined operation stops.
Explanation: It is not possible to determine the status User response: Examine the dsmerror.log file and the
of this disk. Tivoli Storage Manager server activity logs to
determine the cause of this error.
System action: None.
User response: Examine the vSphere Client log to
FMV2519E The disk \"diskname\" is an iSCSI
determine what is wrong with the machine. If the log
device with an inactive path. Powering
entries do not reveal problems with this virtual
off the virtual machine will cause the
machine, inspect the virtual machine in the vSphere
ESXi server to hang. The clean up
Client to determine why the disk status cannot be
operation has been stopped to prevent
determined. See the vSphere documentation for
this. Use the Query VM command with
additional guidance, if necessary.
the -detail option to obtain detailed
status information about the virtual
FMV2515I No additional information is available machine. Correct the path so that the
for this virtual machine. The virtual iSCSI state is active and then try
machine was deleted or it has been running the VMFULLCleanup operation
renamed again.

Explanation: Information about the virtual machine Explanation: A running virtual machine that has an
cannot be found on the ESXi host. The virtual machine inactive iSCSI device cannot be cleaned up.
might have been previously deleted or renamed.
System action: The virtual machine full clean up
System action: None. (VMRESTORType=VMFULLCLeanup) operation stops.

User response: Use the vSphere Client to determine User response: For information about troubleshooting
what happened to this virtual machine. If the virtual inactive iSCSI resources, search the VMware support
machine was renamed, make sure that it is running pages by using a search string like "troubleshooting
without errors before you clean up the temporary iSCSI" or "inactive iSCSI".
resources, by using the Restore VM command with the
-VMRESToretype=VMCLEANUP option.
FMV2520E The disk \"diskname\" is not a physical
device. An instant restore clean up was
FMV2516E VMware storage vMotion operation stopped because vMotion could not
failed. Restart the storage vMotion restore all virtual machine data.. Use the
operation manually, by using the Query VM command with the -detail
vSphere web client, to finish the restore option to obtain information about state
operation. Refer to the documentation to of the specified disk. Use vMotion to
get details about the manual recovery manually migrate the virtual machine
process. devices and then try the clean up
operation again.
Explanation: Tivoli Storage Manager Changes to the
restored VM might not be permanently saved. Explanation: An instant restore clean up operation
(-VMRESToretype=VMCLeanup) cannot complete
System action: Tivoli Storage Manager Automatic because vMotion could not restore all of the virtual
cleanup cannot be performed for the failed vMotion machine resources.
operation.
System action: The virtual machine clean up
User response: Examine the event logs to determine operation stops.
the cause for the failure. Fix any problems and restart
the storage vMotion operation manually, by using the User response: Use the VMware documentation to
vSphere web clien, to finish the restore operation. Refer determine how to use vMotion to migrate the virtual
machine. Then, try the clean up operation again by
using the Restore VM command with the

Chapter 6. FMV messages 401

FMV2521E • FMV2601S

-VMRESToretype=VMCLeanup option. If you do not mounted from another operation and cannot be
want to restore this virtual machine, use the Restore remounted. .
VM command with the
System action: The mount operation stops.
-VMRESTORType=VMFULLCLeanup option to remove
the virtual machine and all of its resources. User response: Dismount the volume by running a
mount cleanup operation, then run the mount
operation again.
FMV2521E Instant restore operations require valid
licenses for both vMotion and storage
vMothion. FMV2525E Unable to power on the created virtual
Machine.
Explanation: Instant restore works only when the
ESXi host has a valid license for both vMotion and Explanation: The vSphere Server is unable to power
storage vMotion on the created virtual machine.
System action: The instant restore operation is System action: The operation will be rolled back and
stopped. stopped.
User response: Obtain the necessary license from User response: Check the dsmerror.log file for more
VMware and assign the license to the ESXi host. information. Check the vSphere log to check what error
happened during virtual machine power on.
FMV2522W A user canceled the 'operationType'
operation . FMV2600S Browser trying to establish connection
to client; received socket exception:
Explanation: A user canceled the restore/backup
exception-name
operation .
Explanation: The browser received the exception
System action: The operation is stopped
exception-name trying to connect to the Tivoli Storage
User response: No response is required. Manager client computer.
System action: The Tivoli Storage Manager operation
FMV2523E The virtual machine named vm cannot ends.
not be restored to the same
User response: Validate that the LAN is up and that
configuration it had when it was backed
you are trying to connect to the correct port number.
up. IBM Tivoli Storage Manager will
reconfigure the virtual machine to Check error logs for any additional information:
include only the most essential dsmerror.log, dsmwebcl.log, or dsmj.log. The default
configuration information and retry the location of these logs is the installation directory of the
restore operation. backup-archive client.
Explanation: The restore operation failed to restore the Ensure that the command line client runs without
virtual machine to its original configuration. This error problems. Test the command line client with a
can occur if there is incompatibility between the command like "dsmc q sess".
hardware that the virtual machine was on when it was
backed up, and the hardware on the physical host
where it was restored. IBM Tivoli Storage Manager will FMV2601S Browser trying to establish connection
reconfigure the virtual machine to eliminate all but to client; received unknown host
most necessary configuration information (video and exception: exception-name
virtual disks) and retry the restore operation. Explanation: The browser received the exception
System action: The restore operation continues, using exception-name trying to connect to the Tivoli Storage
the reconfigured virtual machine information. Manager client machine.

User response: When the restore completes, System action: The Tivoli Storage Manager operation
reconfigure the restored virtual machine to your ends.
requirements. User response: Retry the operation. If it persists,
determine what might be causing this kind of a
FMV2524E An attempt to mount a snapshot of VM problem. Determine if your LAN went down.
'disk' from disk 'vm' failed. The volume Determine if you are trying to connect to the correct
might be mounted from another Tivoli Storage Manager client machine.
operation and cannot be remounted.
Explanation: An attempt to mount a snapshot of VM
'disk' from disk 'vm' failed. The volume might be

402 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2602S • FMV2609S

FMV2602S Browser trying to establish connection FMV2606S An invalid password was sent to the
to client; received IO exception: server.
exception-name
Explanation: The Tivoli Storage Manager password
Explanation: The browser received the exception that was sent to the Tivoli Storage Manager server was
exception-name trying to connect to the Tivoli Storage invalid.
Manager client machine.
System action: The Tivoli Storage Manager operation
System action: The Tivoli Storage Manager operation ends.
ends.
User response: Make sure that you have the correct
User response: Determine what might be causing this password. Also make sure that it is valid, for example
kind of an exception. Retry the problem, and check if it is not too short.
the LAN is down.
FMV2607S Browser could not establish connection
FMV2603S Browser trying to establish connection to client.
to client; received exception:
Explanation: The Tivoli Storage Manager browser
exception-name
could not connect to the Tivoli Storage Manager client
Explanation: The browser received the exception machine.
exception-name trying to connect to the Tivoli Storage
System action: The Tivoli Storage Manager operation
Manager client machine.
ends.
System action: The Tivoli Storage Manager operation
User response: Determine what might be causing this
ends.
kind of a problem. Determine if the LAN is down, or if
User response: Determine what might be causing this the Tivoli Storage Manager Client Acceptor Daemon on
kind of an exception. Determine if the LAN may be the Tivoli Storage Manager machine is up and running.
down, or if the Tivoli Storage Manager Client Acceptor
Daemon on the Tivoli Storage Manager machine is up
FMV2608S Nothing was selected so no operation
and running.
was performed.
Explanation: No object was selected in the GUI for the
FMV2604S The Web client agent was unable to
operation to be performed upon.
authenticate with the server.
System action: The Tivoli Storage Manager operation
Explanation: The Tivoli Storage Manager Web client
ends.
agent was unable to authenticate with the Tivoli
Storage Manager server. User response: Make sure you select one or more
objects (volume, directory or file) in the GUI before
System action: The Tivoli Storage Manager operation
clicking on the operation to be performed.
ends.
User response: One possible solution is to run the
FMV2609S TCP/IP communications failure between
command line client so that the client password can be
the browser and the client machine.
re-entered. Another approach is to check the error log
on the Tivoli Storage Manager Web client agent for any Explanation: This error can occur due to any of the
relevant messages. following:
v The LAN connection to the Tivoli Storage Manager
FMV2605S Browser could not re-establish client machine went down.
connection to client; received protocol v You are trying to connect to the Tivoli Storage
error. Manager client machine using the wrong port
number.
Explanation: The browser received a protocol error
trying to re-connect to the Tivoli Storage Manager client v The Client Acceptor Daemon on the Tivoli Storage
machine. Manager client machine is not up and running and
accepting connections.
System action: The Tivoli Storage Manager operation
ends. System action: The Tivoli Storage Manager operation
ends.
User response: Determine what might be causing this
kind of an error. Determine if the Tivoli Storage User response: Retry the operation and make sure the
Manager browser and the Tivoli Storage Manager client LAN is up. Also check that the port number is correct,
code might be out of sync. and that the Client Acceptor Daemon is started and
running on the Tivoli Storage Manager client machine,
and that it is listening on the correct port number.

Chapter 6. FMV messages 403

FMV2610S • FMV2618S

FMV2610S TCP/IP communications failure between FMV2614S A protocol error occurred in

the client and the server machine. communications between the client and
the server.
Explanation: An attempt to connect to the server
using TCP/IP communications failed. This can be a Explanation: A protocol error happened between the
result of incorrect TCP/IP option settings in your client Tivoli Storage Manager client and the Tivoli Storage
options file. This error can also occur if the LAN Manager server.
connection went down or if your system administrator
System action: The Tivoli Storage Manager client
canceled a backup operation.
ends.
System action: The Tivoli Storage Manager client
User response: Retry the operation. If the problem
ends.
persists, check the Tivoli Storage Manager Error Log for
User response: Retry the operation and make sure the any additional information. Verify that you are running
LAN is up. Make sure that both the Tivoli Storage the correct applet with the appropriate level of the
Manager server and the Tivoli Storage Manager client client.
are up and running.
FMV2615S The user ID entered does not match the
FMV2611S An unknown error occurred in the node name configured on the client
browser. machine.
Explanation: An unknown error occurred in the Explanation: The user ID that was entered is not the
applet running in the browser. same as the node name on this Tivoli Storage Manager
client.
System action: The Tivoli Storage Manager operation
ends. System action: The Tivoli Storage Manager operation
ends.
User response: Retry the operation. If the problem
persists, turn on tracing and see if the trace to the User response: Verify that the node name entered is
browser console gives the reason for the error. configured correctly on the Tivoli Storage Manager
client.
FMV2612S An unknown error occurred in the client
Please check the Tivoli Storage Manager FMV2616I The machine must be rebooted for the
Error Log for any additional information changes to take effect
Explanation: An unknown error occurred in the Tivoli Explanation: The machine must be started for the
Storage Manager client. restored registry changes to take effect.
System action: The Tivoli Storage Manager client System action: None
ends.
User response: Reboot the machine
User response: Retry the operation. If the problem
persists, check the Tivoli Storage Manager Error Log for
FMV2617S The destination directory specified is
any additional information.
invalid.
Explanation: The user specified a destination target
FMV2613S A communications protocol error
directory for restore or retrieve which is invalid.
occurred between the web browser and
the client. System action: The Tivoli Storage Manager operation
ends.
Explanation: None.
User response: Retry the operation specifying a valid
System action: The operation ends.
directory name.
User response: Try the operation again. If the problem
occurs again, verify that the Tivoli Storage Manager
FMV2618S Browser trying to retrieve resources;
web client is installed and configured correctly, and
received resource exception:
make sure you are using a supported browser. Flush
exception-name
the browser cache. Then try the operation again. If the
problem persists, enable SERVICE traces on the web Explanation: The browser received the exception
client on the target machine and the Tivoli Storage exception-name trying to retrieve resources from the
Manager Java applet, then reproduce the problem. Tivoli Storage Manager client machine.
Collect the traces and contact IBM for further
assistance. System action: The Tivoli Storage Manager operation
ends.

404 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2619S • FMV2626E

User response: Verify that the resources are installed does not exist, then the Tivoli Storage Manager
correctly on the Tivoli Storage Manager client machine. administrator can use the REGISTER ADMIN and
GRANT AUTHORITY commands to register an ID that
can access the remote client node's data. If the
FMV2619S The Client Acceptor Daemon was
password is unknown, the Tivoli Storage Manager
unable to start the Remote Client Agent.
administrator can use the UPDATE ADMIN command
Explanation: The Tivoli Storage Manager Client to reset the password.
Acceptor Daemon could not start the Tivoli Storage
Manager Remote Client Agent.
FMV2623S Web Client applet level is out of sync
System action: The Tivoli Storage Manager operation with Web Client agent.
ends.
Explanation: The Web Client applet and Web Client
User response: Check the error log on the Tivoli agents are at incompatible levels.
Storage Manager Web client agent for any relevant
System action: The Tivoli Storage Manager operation
messages. Then correct the problem and retry.
ends.
User response: Verify that you have the correct level
FMV2620W The expand entire branch operation may
of the applet installed with the client, and that an
take a long time, and cannot be canceled
incorrect level of the applet was not placed in the
once it has started. Are you willing to
install directory.
wait for the operation to complete?
Explanation: The expand entire branch operation
FMV2624E This operation requires client owner
could take a long time and cannot be canceled once it
authority.
is started.
Explanation: Your user ID has insufficient authority to
System action: Processing stopped; waiting for user
perform this operation.
intervention.
System action: Processing continues, but the user is
User response: Answer 'Yes' to start the expand entire
not allowed to do this operation.
branch operation. If you answer 'No', the current
operation will be canceled. User response: Do not perform this operation, or get a
higher authority level for your user ID in order to
perform this operation.
FMV2621W This function is not available on the
client platform
FMV2625E Node does not support this image
Explanation: The browser received a request that is
operation.
not available on the Tivoli Storage Manager client
machine. For example, registry backup and restore are Explanation: Node does not support or is not
available only on the Windows platform. configured to perform this image operation.
System action: The Tivoli Storage Manager operation System action: Processing continues, but the user is
ends. not allowed to do this operation.
User response: Request only those functions that are User response: Verify whether this image related
valid for the platform of the Tivoli Storage Manager operation is supported or configured on the target
client machine. platform.

FMV2622S An invalid ID or password submitted. FMV2626E The Include-Exclude statement:

ieStatement contains invalid characters.
Explanation: Either the ID is not registered on the
Tivoli Storage Manager server, or the password for the Explanation: The specified Include-Exclude statement
ID is incorrect. has invalid characters.
System action: The Tivoli Storage Manager operation System action: Tivoli Storage Manager will not add
ends. the specified Include-Exclude statement to the list.
User response: Verify that the ID you are using exists User response: Retry the operation with another
on the TSM server to which the remote client node statement that has valid characters.
connects. The ID must have sufficient privileges to
access the remote client node's data. Also make sure
that you have the correct password for the ID. If the ID
does not exist or if the password is unknown, contact
your Tivoli Storage Manager administrator. If the ID

Chapter 6. FMV messages 405

FMV2627W • FMV2670I

with a duplicate volume path. See addition information

FMV2627W The NTFS security attributes for object
in the error log.
'full-name' could not be set. Windows
system error code: error; reason: System action: Tivoli Storage Manager cannot select
'error-reason'. Default NTFS security the volume.
attributes have been set.
User response: Delete the last snapshots created as
Explanation: Tivoli Storage Manager was unable to set they are not managed by Tivoli Storage Manager.
the NTFS security attributes of the file. The error Unmount the duplicate volume path in order to have a
information captured indicates the reason for the single mount point to the same source volume. Restart
failure. Default NTFS security attributes have been set. Tivoli Storage Manager and retry the operation.
System action: Processing continues.
FMV2667I Scan operation was successful.
User response: Check the reason field for the code
which explains why the NTFS security attributes have Explanation: The virtual machine was scanned
not been set. Correct the condition causing the error successfully.
and try the operation again. If the problem persists,
contact your system administrator or Tivoli Storage System action: The scan process stops for the virtual
Manager administrator for further help. machine. The next virtual machine in the data center
will be processed.

FMV2628W Failed to create named stream of object User response: None

'filespace namepath-namefile-name'.
Explanation: Tivoli Storage Manager was unable to FMV2668E Scan operation failed with an
create named stream. unexpected error.

System action: The named stream is not Explanation: An unexpected error occurred during
restored/retrieved. guest scan operations.

User response: The object is restored without named System action: The scan process stops for the virtual
stream, the object should be examined to verify that it machine. The next virtual machine in the data center
is usable. Check the client error log for FMV5250E error will be processed.
message that should have been logged when this User response: Check the client error log for
message was written, take the corrective action and try additional information.
the operation again. If the problem persists, contact
your system administrator or Tivoli Storage Manager
administrator for further help. FMV2669I Guest operating system platform is not
supported.

FMV2629I Migration: The filespace will be Explanation: The operating system of the virtual
migrated to the Incremental Forever machine was not supported by the scan operation.
model. System action: The scan process stops for the virtual
Explanation: The first time an Incremental Forever machine. The next virtual machine in the data center
Incremental (IFIncr) backup is performed against a will be processed.
virtual machine that was previously backed up using User response: None
the Periodic Full model, and the latest backup is an
incremental backup, then backup chain will be
migrated to the Incremental Forever model. FMV2670I Remote directory in guest is being used
by another application.
System action: This message is for informational
purposes only. Explanation: The scan operation was unable to copy
files to the remote directory because the directory is in
User response: No action is required. use by another application.
System action: The scan process stops for the virtual
FMV2666S Source and/or target volumes are machine. The next virtual machine in the data center
duplicated. The same volume is will be processed.
mounted on more volume paths.
User response: Ensure that the remote directory is
Explanation: This error can occur when a source unlocked. Then, reschedule the scan operation.
volume is mapped on more volume paths, for example,
a drive letter and one or more mount point directories.
Because Tivoli Storage Manager uses the volume path
to keep track of backup information in its internal
backups database, it cannot back up the same volume

406 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2671I • FMV2681W

FMV2671I Virtual machine name was not found on FMV2676W The guest operating system credential
the VMware server. was not found.
Explanation: None Explanation: The guest scan operation requires a valid
operating system credential.
System action: The scan process stops for the virtual
machine. The next virtual machine in the data center System action: The scan process stops for the virtual
will be processed. machine. The next virtual machine in the data center
will be processed.
User response: None
User response: Ensure the guest operating system
credential is set. Then, reschedule the scan operation.
FMV2672W Hostname could not be found for the
specified virtual machine name.
FMV2677W The guest operating system credential is
Explanation: This issue might be caused by the virtual
invalid.
machine not running and not having a static IP
address. Explanation: The guest scan operation requires a valid
operating system credential.
System action: The scan process stops for the virtual
machine. The next virtual machine in the data center System action: The scan process stops for the virtual
will be processed. machine. The next virtual machine in the data center
will be processed.
User response: Make sure the guest is properly
configured. Then, reschedule the scan operation. User response: Ensure a valid guest operating system
credential is set. Then, reschedule the scan operation.
FMV2673I Duplicate virtual machine name was
detected. FMV2678I Guest machine is powered off.
Explanation: None Explanation: None
System action: The scan process stops for the virtual System action: The scan process stops for the virtual
machine. The next virtual machine in the data center machine. The next virtual machine in the data center
will be processed. will be processed.
User response: None User response: None

FMV2674I The virtual machine is not connected to FMV2679I VMware Tools on the guest machine is
ESX server. not running.
Explanation: None Explanation: None
System action: The scan process stops for the virtual System action: The scan process stops for the virtual
machine. The next virtual machine in the data center machine. The next virtual machine in the data center
will be processed. will be processed.
User response: None User response: None

FMV2675E Proxy Rejected: Proxy authority has not FMV2680I VMware Tools version on the guest
been granted to the specified data machine is not current.
mover node.
Explanation: None
Explanation: The scan of the virtual machine failed.
System action: The scan process stops for the virtual
System action: The scan process stops for the virtual machine. The next virtual machine in the data center
machine. The next virtual machine in the data center will be processed.
will be processed.
User response: None
User response: The Tivoli Storage Manager server
administrator must grant proxy authority for this node.
FMV2681W ESX host or vCenter version is not
See the administrator command "Grant Proxynode".
supported.
Explanation: The ESX host or vCenter is a down level
version.
System action: The scan process stops for the virtual

Chapter 6. FMV messages 407

FMV2682I • FMV2690E

machine. The next virtual machine in the data center

FMV2687W The virtual machine 'VM-name' contains
will be processed.
one or more disks that exceed the
User response: Refer to the product documentation maximum size limit. Specify the
for supported ESX and vCenter versions. '-VMSKIPMAXVMDKS=yes' option to
exclude these disks from the backup.

FMV2682I The guest credential has insufficient Explanation: The IBM Tivoli Storage Manager client
permissions. does not support backing up VMDKs that are greater
than the supported limit.
Explanation: None
System action: The virtual machine is not backed up.
System action: The scan process stops for the virtual
machine. The next virtual machine in the data center User response: Specify the
will be processed. '-VMSKIPMAXVMDKS=yes' option to exclude these
disks from the backup.
User response: None

FMV2688E The restore of a Hyper-V virtual

FMV2683W Cannot communicate with the remote machine that was backed up using
host. incremental forever backup is not
Explanation: This communication issue is caused by allowed on a Windows 2008 or Windows
network errors or by the host not responding. 2008 R2 host. The restore operation must
be completed on a Windows 2012 or
System action: The scan process stops for the virtual later Hyper-V host
machine. The next virtual machine in the data center
will be processed. Explanation: A Hyper-V virtual machine that was
backed up with the incremental forever backup type
User response: Ensure that the network and host can only be restored on a Windows 2012 or later
connection are configured correctly. Then, reschedule Hyper-V host.
the scan operation.
System action: The restore operation does not start.

FMV2684I The guest operation agent could not be User response: Try the operation again with a
contacted. Windows 2012 or later Hyper-V host.

Explanation: None
FMV2689E A Hyper-V command subcommand
System action: The scan process stops for the virtual command was specified, but the
machine. The next virtual machine in the data center Hyper-V role is not enabled on the host
will be processed. system
User response: None Explanation: The Hyper-V role must be enabled on
the host system where the Hyper-V operation occurs.
FMV2685I The VM is a template. The current system does not have the Hyper-V role
enabled.
Explanation: VM templates are not supported by the
scan operation. System action: The operation does not start.

System action: The scan process stops for the virtual User response: Try the operation again from a host
machine. The next virtual machine in the data center that has the Hyper-V role enabled.
will be processed.
User response: None FMV2690E A Hyper-V BACKUP VM command
with mode IFFULL or IFINCR was
specified but the Data Protection for
FMV2686E VM scan initialization error. Microsoft Hyper-V license file does not
Explanation: The vm scan operation encountered an exist or is not valid
error during initialization. Explanation: The Data Protection for Microsoft
System action: The scan process stops for the virtual Hyper-V license file is required to issue Hyper-V
machine. The next virtual machine in the data center BACKUP VM commands with mode IFFULL or
will be processed. IFINCR. Make sure the Data Protection for Microsoft
Hyper-V file is installed.
User response: Check the client error log and trace for
additional information. System action: The backup does not start.
User response: Try the operation again from a host

408 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2691E • FMV2700E

that has the Data Protection for Microsoft Hyper-V inactive on the ESX/ESXi that you are restoring the
license file installed. Or, issue the BACKUP VM virtual machine to.
command and specify mode FULL.
System action: The virtual machine cannot be
restored.
FMV2691E A Hyper-V BACKUP VM command
User response: Find the missing datastore or specify
with mode FULL was specified but the
the -datastore option on the Restore VM command to
Data Protection for Microsoft Hyper-V
specify an existing datastore to restore the virtual
license file exists. Mode IFFULL or
machine files to.
IFINCR must be specified
Explanation: Hyper-V BACKUP VM commands with
FMV2698E Snapshot operation failed.
mode FULL are not allowed on hosts where the Data
Protection for Microsoft Hyper-V license file is Explanation: If you are performing a VSS or LVSA
installed. Instead, issue the BACKUP VM command snapshot based operation, it is possible that the
using mode IFFULL or IFINCR. snapshot was not large enough to contain all the
changes made to the file system after the snapshot was
If you must issue the BACKUP VM command with
created. This could cause the snapshot to become
mode FULL, you must uninstall the Data Protection for
invalid thereby preventing the Tivoli Storage Manager
Microsoft Hyper-V license file. However, uninstalling
client from reading the snapshot.
the license file invalidates the IFINCR backup chain. As
a result, an IFFULL is performed if the Data Protection System action: The requested operation stopped.
for Microsoft Hyper-V license file is reinstalled.
User response: Examine the client error log for
System action: The backup does not start. additional messages related to this error. Perform
corrective actions indicated by the messages, then try
User response: Try the operation again and specify
the operation again.
mode IFFULL or IFINCR.

FMV2699W Importing VM 'vm name' failed for vApp

FMV2692E An error occurred while registering the
'vapp name'.
filespace for virtual machine (VM_name).
Explanation: The import VM from vSphere to a
Explanation: An error occurred while registering the
vCloud vApp operation failed.
filespace for the specified virtual machine.
System action: Restore processing for the vApp
System action: The backup of this virtual machine
continues.
fails. The backup process can continue with other
virtual machines. User response: Check the dsmerror.log file for
information about why the VM was not imported.
User response: Check the error log for information
Then, try the operation again. If the problem persists,
about how to resolve this issue.
search the Tivoli Storage Manager Support web site
(http://www.ibm.com/software/sysmgmt/products/
FMV2693E An error occurred while registering the support/IBMTivoliStorageManager.html) for known
filespace for virtual machine (VM_name). solutions.
There is a filespace with the same name
that is currently being deleted.
FMV2700E Restoring VM 'vm name' of vApp 'vapp
Explanation: An error occurred while registering the name' is not possible. There is no VM
filespace for the specified virtual machine. A filespace backup data.
with the same name is currently being deleted on the
Explanation: During the vApp restore, a VM that
Tivoli Storage Manager server
exists in the restored vApp version could not be
System action: The backup of this virtual machine restored, because it was not successfully backed up.
fails. The backup process can continue with other
System action: The restore operation will proceed,
virtual machines.
attempting to restore any available vApp backup data.
User response: Wait for the delete filespace to finish
User response: Examine the client error log for any
and run the backup command again.
messages that might be indicate on the reason for the
specified VM's backup failure. Contact Tivoli Storage
FMV2697E The virtual machine cannot be restored Manager technical support if further assistance is
because the datastore named 'datastore' required.
does not exist or is inactive.
Explanation: The datastore referenced by virtual
machine when it was backed up does not exist or is

Chapter 6. FMV messages 409

FMV2701E • FMV2715E

System action: The virtual machine is not backed up.

FMV2701E The attempted database operation was
unsuccessful, check the Tivoli Storage User response: Ensure that another application or
Manager error log for any additional process does not remove or modify the virtual machine
information. during the backup.
Explanation: Processing stops.
FMV2712W The virtual machine 'name' has a
System action: Reserved.
VMware Tools running, but VMware
User response: Check the Tivoli Storage Manager Tools is out of date.
error log for information regarding failure and take
Explanation: A supported version of VMware Tools
further action.
must be installed, running and current to complete a
virtual machine backup.
FMV2704E Error: The vCenter server version is at a
System action: The backup operation fails.
lower level than the ESX host version,
or the user ID specified by the User response: Verify that a supported version of
VMCUser option does not have VMware Tools is installed, current and running. Then,
sufficient permission to perform the try the backup operation again.
operation.
Explanation: The vCenter returned an error indicating FMV2713E The virtual machine 'VM-name' is in an
there is a problem with the license. This error can occur invalid connection state 'state'. As a
when the vCenter server version is at a lower level result, it cannot be backed up.
than the ESX host version. The vCenter server version
must be at the same (or later) level as the ESX host Explanation: To back up a virtual machine it must be
version. This error can also occur when the user ID in the 'connected' state to be accessed.
specified by the VMCUser option does not have System action: The virtual machine is not backed up.
sufficient permission to perform the operation or the
permissions are not applied at the vCenter server level. User response: Return the virtual machine to the
'connected' state and try the backup again.
System action: Processing stops.
User response: Verify the vCenter server is at the FMV2714W The management class 'mc' specified for
correct level, and verify that the user ID specified by the 'dest' backup destination is invalid.
the VMCUser option has sufficient permission to The default management class will be
perform the operation. used.
Explanation: None.
FMV2705S No DB2 UDB partitions are available for
restore. System action: Processing continues.

Explanation: No DB2 UDB partitions are available on User response: Contact the Tivoli Storage Manager
the Tivoli Storage Manager server for restore. This is administrator to run the configuration utility for DB2
most likely due to a previous backup that was aborted UDB and specify a valid management class.
before the backup completed. The DB2 UDB database
and selected partitions cannot be restored. FMV2715E The virtual machine 'VM-name' is
System action: Processing stops. configured as a fault tolerant virtual
machine. As a result, it cannot be
User response: Issue the Tivoli Storage Manager client backed up.
command QUERY DB2UDB command with the
-DETAIL parameter using the same database, file, and Explanation: vSphere does not allow for the snapshot
date criteria to see if any database partitions are or backup of fault tolerant virtual machines with
available for restore. Alternatively restore the DB2 UDB vStorage API for Data Protection.
database from a different backup. System action: The virtual machine is not backed up.
User response: To back up a fault tolerant virtual
FMV2711E The snapshot of virtual machine machine with vStorage API for Data Protection, first
'VM-name' was removed during the disable fault tolerant. Then, after the backup completes,
backup. enable fault tolerant.
Explanation: The virtual machine snapshot was
removed by another application or process during the
backup. This removal corrupts the backup and it
becomes unusable.

410 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2716E • FMV2723E

FMV2716E A background copy process is still FMV2720W Failed to execute the command
pending on local hardware. A restore 'command'.
operation cannot be initiated until the
Explanation: IBM Tivoli Storage Manager Failed to
background copy process is completed.
execute a command. The possible reason - the
Explanation: None. command interpreter cannot be found. Verify the
ComSpec and PATH environment variables that locate
System action: Processing stops.
the command interpreter. Either ComSpec or PATH is
User response: Wait until the background copy not defined, or it is not correctly defined.
process completes and retry the restore operation.
System action: The command does not run. Otherwise
processing will attempt to continue.
FMV2717E The multi-node definition does not have
User response: Correct the ComSpec and PATH
permission to delete its own backup
environment variable that locate the command
files from the server.
interpreter. Contact your system administrator if you
Explanation: All DB2 UDB commands require that the are not sure how to make this correction.
multi-node definition has permission to delete its own
backup files from the server in order to properly
FMV2721E The virtual machine is in an invalid
reconcile the local backup repository with the server
connection state. As a result, it cannot
backup repository.
be backed up.
System action: Processing stops.
Explanation: One or more virtual machine backups
User response: Have the Tivoli Storage Manager failed because of an invalid connection state. A virtual
administrator update the multi-node definition so that machine must be in the 'connected' state to be accessed
it has permission to delete its own backup files from for backup.
the server. For example, on the Tivoli Storage Manager
System action: Processing stops for this virtual
administrative command-line client: . dsmadmc update
machine
node <multi-node name> backdelete=yes
User response: Check the console output and error
logs for information about why the connection state
FMV2718W The virtual machine 'VM-name' requires
was invalid. Correct any issues and try backing up the
snapshot consolidation.
failed virtual machines.
Explanation: Snapshot consolidation is required when
a snapshot is deleted but its associated disk is not
FMV2722E There is not enough space in the local
committed back to the base disk. If consolidation is not
repository to complete this backup.
completed, snapshot disks might grow and eventually
fill the data store. Explanation: This space available in the local
repository is not enough to perform snapshot for this
System action: The virtual machine backup continues.
backup operation. It could happen if there is more
User response: Consolidate the virtual machine number of local versions kept by the management class
snapshots according to instructions provided in the than there is space allocated in the local repository at
appropriate VMware vSphere documentation. configuration time or application configuration has
changed such that previously allocated space is not
enough.
FMV2719E A previous backup started on 'datetime',
is using the resources needed for new System action: None.
backup is still pending.
User response: Please validate TSM configuration by
Explanation: A new backup can not be done until running the configuration wizard.
previous backup completes.
System action: Processing stops. FMV2723E A value of UNDEF for the
REAdstartsrecall option is not valid
User response: Wait until previous backup completes when the HSMBACKENDMODE option
before starting another local backup. Alternatively, use is set to TSM.
different copyType value to perform a local backup.
TSM local backup policy only allows one incremental Explanation: A value of UNDEF for the
and one full background copy to be pending at any REAdstartsrecall option is valid only when the
time, before local backup resources are reused for a HSMBACKENDMODE option is set to TSMFREE.
new backup version. A new local backup would result
System action: The operation stops. The file is
in a backup with background copy in pending state.
skipped.

Chapter 6. FMV messages 411

FMV2724E • FMV2733E

User response: If the HSMBACKENDMODE option is operating system for more information about the
set to TSM, set the REAdstartsrecall option to YES or failure. Issue the failing command manually to see if
NO. the same failure occurs.

FMV2724E The version of IBM Enterprise Storage FMV2730E The primary and secondary copy service
Server is not supported. servers are down.
Explanation: This product only supports IBM ESS Explanation: None.
microcode level 2.3 and 2.4.
System action: Process stops.
System action: Process stops.
User response: Start at least one of the ESS copy
User response: Ensure that ESS microcode level 2.3 or service servers. If copy server is already running, check
2.4 is installed. the value of java home specified during configuration
to make sure it is a valid path name of the directory
where JRE is installed on master backup node. Use
FMV2726E The putenv command failed for path =
configuration wizard to update java home value for the
v1.
configuration.
Explanation: There was not enough memory in the
environment to successfully set the environment.
FMV2731E Cannot open the ESS command output
System action: Process stops. file v1 for writing.

User response: Close all unneeded applications and Explanation: Can't open this file for writing.
try the operation again. For UNIX systems that support
System action: Process stops.
resource limits, check to see if the memory resource
limit is too low by entering the following command: User response: Make sure you have enough space on
ulimit -a your system and write permission to the file.
Based on the resulting data, you can ask the UNIX
system root user to increase resource limits so that it FMV2732E The ESS LUN 'Serial number string' are
will override the current default. The UNIX system root already in use.
user has the authority to increase resource limits.
Explanation: One or more LUNs specified in the
message are in use by other flashcopy operation.
FMV2727E ESS Lun ID v1 is not valid. Therefore this flashcopy operation can not continue.
Explanation: Length of ESS LUN id must be 8 System action: Process stops.
characters.
User response: Release ESS LUN in order to reuse
System action: Process stops. them.
User response: Make sure the length of ESS Lun id is
8. FMV2733E An operation requiring the Windows
Management Instrumentation (WMI)
service has failed with the error
FMV2728E The ESS jar file v1 cannot be found.
'errorstring'. Tivoli Storage Manager has
Explanation: The Enterprise Storage Sub-system Copy been denied access to a WMI system
Services JAR file could not be located. due to insufficient privileges.

System action: Process stops. Explanation: Windows denied access to a Windows

Management Instrumentation (WMI) resource, object,
User response: In order to complete Enterprise or operation. This program has insufficient permissions
Storage Sub-system Copy Services functions the Copy to perform the requested operation.
Services command line functions must be available.
Check the Copy Services command line is installed and System action: Performing an operation requiring the
your Copy Services option setting is pointing to the Windows Management Instrumentation service.
installation directory of the command line.
User response: Raise the permissions assigned to
Tivoli Storage Manager and retry the operation.
FMV2729E Operating system command 'command'
failed; rc=rc.
Explanation: None.
System action: Process stops.
User response: Check the return code from the

412 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2734E • FMV2747E

FMV2734E An operation requiring the Windows FMV2745E An assigned virtual disk to Hyper-V
Management Instrumentation (WMI) Virtual Machine 'virtualmachinename'
service has failed with the error cannot be found.
'errorstring'. The application interface
Explanation: The IBM Tivoli Storage Manager client
does not exist.
detected that a Virtual Machine has assigned a disk
Explanation: This error occurred because Windows that is unreachable. The disk may have been moved or
Management Instrumentation (WMI) classes were not deleted. A snapshot cannot be taken while the disk
registered or have become unregistered. WMI classes cannot be found.
are registered with Windows features.
System action: The IBM Tivoli Storage Manager could
System action: Initialization of a Windows not find a virtual disk at the assigned path.
Management Instrumentation object failed.
User response: Check that the virtual disk has not
User response: Register the Windows Management been moved or deleted and update the virtual machine
Instrumentation classes of the appropriate Windows configuration to match any changes to the file system.
feature.
FMV2746E An assigned virtual disk to Hyper-V
FMV2736E An unexpected response was received virtual machine 'virtualmachinename' is a
from a remote Tivoli Storage Manager VHD or invalid format. Only virtual
file system agent. verb : verb remote host disks in VHDX format can be backed
: host return code : rc reason code : rs up.
msg. string : msg-string
Explanation: The IBM Tivoli Storage Manager client
Explanation: None. detected that a virtual machine has assigned a disk that
is in the VHD format or is in an unrecognisable or
System action: Processing stops.
unsupported format. If the disk is in VHDX format it
User response: Contact the Tivoli Storage Manager may be corrupted.
administrator with the information provided in this
System action: The IBM Tivoli Storage Manager found
message.
a virtual disk in VHD or unrecognisable format while
preparing for a backup of a virtual machine.
FMV2737W No disks from VM are mounted because
User response: If the virtual disk is in VHD format
all disks were excluded during the
there are several options: Remove the VHD from the
backup.
virtual machine, convert the virtual disk from VHD
Explanation: No disks from VM can be mounted format to VHDX format, or adjust DOMAIN.VMFULL
because all disks were excluded during backup or the to skip the virtual machine from backup. If the disk is
VM did not contain any disks. in VHDX format, check that the disk has not been
corrupted.
System action: The operation stops.
User response: If files from the affected file systems or FMV2747E An assigned AVHDX virtual disk to
volumes must be recovered, ensure that at least one Hyper-V virtual machine
disk is included in the backup. 'virtualmachinename' cannot find the
parent disk. Snapshots can be taken
FMV2740E The vApp restore operation failed. only if the parent can be found.

Explanation: The vApp restore operation failed. Check Explanation: The AVHDX format specifies an internal
the error log for details on why the operation failed. field that points to a parent AVHDX or VHDX file. If
the parent cannot be found the disk is invalid and a
System action: Processing stops snapshot will fail.
User response: Review the console output and error System action: Tivoli Storage Manager discovered an
logs for the details on the problem. Fix any issues and AVHDX attached to a virtual machine and attempted to
restart the operation. find the parent AVHDX or VHDX file.
User response: Check that the parent AVHDX or
FMV2744I TESTFLAG DB2 enabled with the value VHDX file still exists and has not been moved or
of 'value'. deleted. Return the parent AVHDX and/or VHDX file.
Explanation: None.
System action: This message is informational.
User response: None.

Chapter 6. FMV messages 413

FMV2748E • FMV2798E

FMV2748E An assigned virtual disk to Hyper-V FMV2750E The Hyper-V Virtual Machine
virtual machine 'virtualmachinename' 'virtualmachinename' is currently
exceeds the maximum capacity limit. undergoing one of the following
The IBM Tivoli Storage Manager client operations: * Creating Local Snapshot *
cannot backup virtual machines with Applying Local Snapshot * Deleting
disks that exceed the limit of two Local Snapshot * Exporting Virtual
terabytes. Machine * Migrating Virtual Machine *
Volume Snapshot Service (VSS)
Explanation: The IBM Tivoli Storage Manager client
Snapshot * Restore * Merging
detected that a Virtual Machine has assigned a disk
Differencing Disks The above
whose capacity exceeds two terabytes. Virtual disks
operations prevent a Hyper-V VSS
that exceed 2 terabytes are currently not supported by
snapshot from taking place. Wait for the
incremental forever backups.
operation to finish or cancel to perform
System action: The IBM Tivoli Storage Manager found a backup.
a virtual disk whose capacity exceeds two terabytes on
Explanation: Some virtual machine management tasks
a virtual machine scheduled for back up.
interfere with a virtual machine VSS snapshot. One of
User response: There are several options available: these operations was detected during a back up
Remove the disk from the virtual machine, shrink the request.
disk to under two terabytes, copy the data to virtual
System action: The IBM Tivoli Storage Manager client
disk with a capacity under two terabytes. Even though
discovered the virtual machine is currently undergoing
incremental backup is not available, the always full
an operation that will prevent a Volume Snapshot
backup type is compatible with disks over two
Service snapshot from occuring.
terabytes.
User response: Cancel or wait for the current virtual
machine management task to finish and then retry the
FMV2749E See Microsoft Technote KB2771882. An
back up.
assigned virtual disk to Hyper-V Virtual
Machine 'virtualmachinename' contains
files that are on a Cluster Shared FMV2753I Establishing inter-client communication
Volume and local volumes. A snapshot with node node(s).
of a Virtual Machine in this
Explanation: None.
configuration cannot be taken.
System action: This message is informational.
Explanation: The IBM Tivoli Storage Manager client
detected that a Virtual Machine has files involved in User response: None.
the snapshot on both local volumes and Cluster Shared
Volumes. Attempting to snapshot a virtual machine in
this configuration always results in failure. This error is FMV2785I Gathering current DB2 configuration for
documented in Microsoft Technote KB2771882. 'type' restore.

System action: The IBM Tivoli Storage Manager client Explanation: None.
discovered the virtual machine has files on local System action: This message is informational.
volumes and cluster shared volumes prior to taking a
snapshot. User response: None.

User response: Check that all of the disks and the

configuration files are all on local volumes or cluster FMV2798E Unable to start a session from client
shared volumes. If necessary, perform a storage node 'nodename' multi-node 'multi-node'
migration to move the disks and/or configuration files. to client at address 'ip-address:ip-port'.
The Tivoli Storage Manager return code
is rc.
Explanation: None.
System action: This message is informational.
User response: None.

414 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2799E • FMV2808W

FMV2799E An error was encountered during a FMV2804W Tracing is already enabled.

session with another client. check the -TRACEFILE, -TRACEMAX, and
Tivoli Storage Manager error log for any -TRACESEGSIZE are ignored.
additional information
Explanation: When tracing is already enabled for a
Explanation: This message is reserved for DB2 UDB. client process, only the -TRACEFLAGS option has any
effect.
System action: Reserved.
System action: The -TRACEFLAGS options are set on
User response: This message is reserved for DB2 UDB.
the client process. -TRACEFILE, -TRACEMAX, and
-TRACESEGSIZE are ignored.
FMV2800W No Tivoli Storage Manager processes
User response: If you need to modify the
were found.
-TRACEFILE, -TRACEMAX, or -TRACESEGSIZE
Explanation: The QUERY PIDS command was unable settings, you must first use the dsmtrace DISABLE
to identify any known Tivoli Storage Manager command to disable tracing for the client process. Then
processes running on the system. If the -FILTER option run the dsmtrace ENABLE command to configure the
was used, no processes matching the filter specification desired trace settings. If it is not necessary to modify
were found. these settings, then this message may be ignored.

System action: None.

FMV2805I Tracing has been enabled.
User response: If you need to use dsmtrace to enable
or disable tracing for a running client process, make Explanation: None.
sure that the client is already running. If you used the
System action: None.
-FILTER option, try the command again with a different
filter specification. You can use -FILTER=* to display all User response: None.
processes running on the system.
FMV2806E Tracing could not be enabled.
FMV2801E The dsmtrace utility was unable to
Explanation: A problem occurred while trying to
connect to the specified process.
enable tracing for the specified process. This message is
Explanation: This message typically occurs when the usually accompanied by other, more specific messages
specified process ID is not active. immediately preceding or following this message.
System action: None. System action: No changes are made to the trace
status of the specified process.
User response: If you need to use dsmtrace to enable
or disable tracing for a running client process, make User response: Review the messages that immediately
sure that the client is already running. Use the precede or follow this message for further information
dsmtrace QUERY PIDS command to identify running about this error.
client processes, then try the command again.
FMV2807E An incorrect number of parameters was
FMV2802I Tracing has been disabled. specified for the command-name
command.
Explanation: None.
Explanation: The specified command was invoked
System action: None.
with too few or too many parameters.
User response: None.
System action: The command is not processed.
User response: Try the command again with the
FMV2803E Tracing could not be disabled.
correct number of parameters. Run \"dsmtrace help\"
Explanation: A problem occurred while trying to for additional information on dsmtrace command
disable tracing for the specified process. This message syntax.
is usually accompanied by other, more specific
messages immediately preceding or following this
FMV2808W Incremental by snapshot difference
message.
backup did not locate the registered
System action: No changes are made to the trace base snapshot 'regbase-name' on
status of the specified process. NetApp/N-Series filer volume
'volume-name'. Snapshot 'olderbase-name' is
User response: Review the messages that immediately used as the base snapshot.
precede or follow this message for further information
about this error. Explanation: Incremental by snapshot difference

Chapter 6. FMV messages 415

FMV2809E • FMV2815E

backup did not locate the specified registered base

FMV2812E The Tivoli Storage Manager for Virtual
snapshot on the specified NetApp/N-Series filer
Environments could not find Datamover
volume. The most recent existing snapshot which is
node named 'datamover nodename' on the
older than the registered base snapshot is used as the
Tivoli Storage Manager Server.
current base snapshot.
Explanation: While processing Proxy relationships
System action: Processing continues.
with the DataCenter node and DataMover node
User response: None. specified, no appropriate Datamover node name
matches detected.

FMV2809E The backupid 'backupid:' in the input file System action: The operation cannot continue without
does not match the vmname 'vmname:' a valid Datamover Node name.
being restored.
User response: Make sure the Datamover node name
Explanation: There is a discrepency between the specified is a valid Tivoli Storage Manager node name
backupid and vmname specified in the input file and that the node has the proper proxy relationships
established.
System action: The virtual machine cannot be
restored.
FMV2813E The Tivoli Storage Manager Server
User response: Confirm that the backupid specified returned an empty network address or
matches the vmname you are attempting to restore by port number for 'datamover nodename'.
re-running the inquire_detail command and make any
necessary corrections before attempting the restore Explanation: While querying the Tivoli Storage
again. Manager Server for the Datamover network address
and port number, the Server returned zero for one of
the values.
FMV2810E The Tivoli Storage Manager for Virtual
Environments Input File 'input file:' System action: The operation cannot continue without
appears to be empty. a valid Datamover network address and port number.

Explanation: While processing the Input File no items User response: This is usually the result of a
were found to operate on. Datamover Node not being started. Log on to the
Datamover host and start or restart the DSMCAD
System action: The operation cannot continue with an service and retry the Tivoli Storage Manager for Virtual
empty list. Environments command again. If the problem persists,
User response: Confirm that the input file is not work with your Tivoli Storage Manager Server
empty and has valid input. If the file is not empty it Administrator to inspect the Tivoli Storage Manager
may be that an error occurred while reading the file, Server activity log to identify the issue.
please check the error log for any errors found during
the reading of the file. If errors are found make the FMV2814E Tivoli Storage Manager for Virtual
necessary corrections before attempting the operation Environments detected an error while
again. parsing the Input File 'input file'. The
'specifier' appears to be empty or invalid.
FMV2811E The Tivoli Storage Manager for Virtual Explanation: While parsing the Input File an error
Environments could not find a suitable occurred.
datamover agent for the DataCenter
Node 'datacenter nodename'. System action: The operation cannot continue without
valid virtual machine specifications.
Explanation: While processing Proxy relationships
with the DataCenter Node specified, no appropriate User response: This is usually the result of an empty
datamover matches detected virtual machine name or other identifier. Please check
that the syntax of the Input File is correct for all entries
System action: The operation cannot continue without and that virtual machine names are not empty and
a valid datamover. retry the operation.
User response: Work with your Tivoli Storage
Manager Administrator to ensure that your DataCenter FMV2815E Tivoli Storage Manager for Virtual
Nodes have granted proxy authority to your Environments detected an error while
DataMover Nodes. parsing 'read in line' from the Input File
'input file'.
Explanation: While parsing the Input File an error
occurred.

416 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2816E • FMV2826E

System action: The operation cannot continue without

FMV2820E An interrupt has occurred. The current
valid specifications in the Input File.
operation will end and the client will
User response: This may be the result of an empty shut down.
virtual machine name or other identifier. Please check
Explanation: This message is issued when the process
that the syntax of the Input File is correct for all entries
is interrupted by a break signal such as CTRL-BREAK
and that virtual machine names are not empty and
or CTRL-C.
retry the operation.
System action: The Tivoli Storage Manager operation
and process are ended immediately.
FMV2816E Tivoli Storage Manager for Virtual
Environments detected that the Tivoli User response: Restart the operation if desired.
Storage Manager Server IP address was
not specified.
FMV2821E The function is not supported on the
Explanation: While parsing the command line options, platform.
an empty Server address was detected.
Explanation: The specified function isn't supported on
System action: The operation cannot continue without the specified platform.
a valid network address for the Tivoli Storage Manager
System action: Processing stops.
Server.
User response: Please retry the specified function on a
User response: This may be a result of the VMCLI
supported platform.
profile having an empty VE_TSM_SERVER_NAME
entry. Please check that the VMCLI profile is configured
correctly specifying the Tivoli Storage Manager Server FMV2824E Tivoli Storage Manager for Virtual
address. Environments detected that the node
name representing the vCenter is not
specified.
FMV2817E Tivoli Storage Manager for Virtual
Environments detected that the vCenter Explanation: While parsing the command line options,
Command-Line interface node name an empty vCenter node name was detected.
was not specified.
System action: The operation cannot continue without
Explanation: While parsing the command line options, a valid vCenter node name.
an empty vCenter Command-Line interface node name
was detected. User response: This may be a result of the VMCLI
profile having an empty VE_VCENTER_NODE_NAME
System action: The operation cannot continue without entry. Please check that the VMCLI profile is configured
a valid vCenter Command-Line interface node name. correctly specifying the vCenter node name.
User response: This may be a result of the VMCLI
profile having an empty VE__TSMCLI_NODE_NAME FMV2825E Tivoli Storage Manager for Virtual
entry. Please check that the VMCLI profile is configured Environments detected that the node
correctly specifying the vCenter Command-line name representing the Datacenter is not
interface node name. specified.
Explanation: While parsing the command line options,
FMV2818E Tivoli Storage Manager for Virtual an empty datacenter node name was detected.
Environments detected that the Tivoli
Storage Manager Server port was not System action: The operation cannot continue without
specified. a valid datacenter node name.

Explanation: While parsing the command line options, User response: This is a result of the -d DataCenter
an empty Tivoli Storage Manager Server port was Node Name not being passed in to the Command-line.
detected. Re-try the operation making sure to pass the -d
Datacenter Node Name to the command-line call.
System action: The operation cannot continue without
a valid Tivoli Storage Manager Server port.
FMV2826E Tivoli Storage Manager for Virtual
User response: This may be a result of the VMCLI Environments detected that the node
profile having an empty VE_TSM_SERVER_PORT name representing the vCenter
entry. Please check that the VMCLI profile is configured Datamover is not specified.
correctly specifying the Tivoli Storage Manager Server
port. Explanation: While parsing the command line options,
an empty Datamover node name was detected.
System action: The operation cannot continue without

Chapter 6. FMV messages 417

FMV2827E • FMV2834E

a valid Datamover node name. possible reason for this failure is that snapshot
difference incremental backups can only be performed
User response: This is a result of the -o Datamover
against NetApp/N-Series NFS volumes on AIX/Linux
Node Name not being passed in to the Command-line.
platforms, or CIFS volumes on Windows platforms.
Re-try the operation making sure to pass the -o
Datamover Node Name to the command-line call. Another possible reason for this failure is that the qtree
security style for the volume was incorrectly selected. If
the CIFS volume is mapped on Windows, ensure that
FMV2827E Tivoli Storage Manager for Virtual
the security style is set to NTFS. If the volume is
Environments detected that the input
mounted as NFS, ensure that the security style is set to
file is not specified.
UNIX.
Explanation: While parsing the command line options,
System action: Processing stops.
an empty or non-existing input file name was detected.
User response: Try the command again with a
System action: The operation cannot continue without
NetApp/N-Series NFS or CIFS volume with the correct
a valid input file name.
security style.
User response: This is a result of the -I Inputfile name
not being passed in to the Command-line. Re-try the
FMV2832E Incremental by snapshot difference
operation making sure to pass the -I input file name to
failed for filespace name. See the error log
the command-line call.
for details.
Explanation: Failed to perform NAS NFS/CIFS
FMV2828E Image operations are not supported for
Incremental by snapshot difference operation.
the specified file system.
System action: Processing stops.
Explanation: Image backup and restore are not
supported for the specified file system. User response: Take appropriate action based on the
information in the error log. If the problem persists
System action: The requested image operation is not
please contact your IBM Tivoli Storage Manager
performed.
administrator.
User response: Choose another object.
FMV2833E Incremental backup operation using
FMV2829E Image operations are not supported for snapshot difference failed because the
GPFS. base snapshot snapshot name is the same
as the latest snapshot for the NAS
Explanation: Image backup and restore are not volume NAS volume.
supported for GPFS volumes.
Explanation: User specified that the latest snapshot on
System action: The requested image operation is not the NAS Filer be used as the difference snapshot
performed. during an incremental backup operation using snapshot
User response: Choose another object. difference. However, the previously taken base
snapshot and the latest snapshot on the filer are
identical.
FMV2830E An incorrect number of parameters was
specified. System action: Processing stops.

Explanation: The specified command was invoked User response: Try the operation again using the
with too few or too many parameters. default value of "create" for the difference snapshot.

System action: Processing stops.

FMV2834E You have to be a root user in order to
User response: Try the command again with the perform incremental backup using
correct number of parameters. snapshot difference.
Explanation: Failed to perform NAS NFS/CIFS
FMV2831E Incremental by snapshot difference incremental backup operation using snapshot difference
cannot be performed on 'volume-name' as as the user was non root.
it is of type 'type' and is not a
NetApp/N-Series 'fsType' volume. System action: Processing stops.

Explanation: The volume specified cannot be used for User response: Please retry the operation as root user.
performing NetApp/N-Series snapshot difference
incremental operation. The volume does not correspond
to the NFS mount point or the CIFS shared drive for a
Network Appliance or N-Series NAS volume. One

418 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2835E • FMV2842E

Explanation: The user ID and password have been

FMV2835E Incremental backup using snapshot
configured incorrectly for the specified Filer.
difference is not supported on this
platform. If you are using the snapdiffhttps option, ensure that
you are not specifying vFiler volumes as vFiler does
Explanation: NetApp NFS/CIFS incremental backup
not support the HTTPS transport type.
operation using snapshot difference is only supported
on AIX, Linux and Windows platforms. System action: Processing stops.
System action: Processing stops. User response: Make sure that the credentials you
have specified for the Filer are the correct ones. Use the
User response: Retry the incremental operation
dsmc set password command to specify the correct
without the snapdiff option.
credentials for your Filer and try the command again.

FMV2836E Incremental backup operation using

FMV2840E Incremental backup using snapshot
snapshot difference is only available for
difference is not supported for Data
full volumes. is a partial volume or
ONTAP file server version
qtree.
'version.modification.submodification'.
Explanation: Cannot perform NAS NFS/CIFS Upgrade the file server 'file-server-name'
incremental backup operation using snapshot difference to Data ONTAP version '7.3' or later in
on the mounted or mapped volume due to one of the order to perform incremental backup
following reasons: 1) The volume is actually a qtree. 2) operations using snapshot difference.
The volume is not a full volume, it is not mounted or
Explanation: The file server specified is not at the
mapped to the root of the volume.
Data ONTAP version that supports snapshot difference
System action: Processing stops. API.
User response: Retry the incremental backup System action: Processing stops.
operation by specifying an entire NAS NFS or CIFS
User response: Upgrade the file server to Data
volume.
ONTAP version 7.3 or later and retry the operation.

FMV2837E Failed to perform incremental backup

FMV2841E Incremental by snapshot difference is
operation using snapshot difference as
only supported on AIX 64 bit and Linux
the user id and password for NAS Filer
86 bit clients.
'' have not been configured correctly.
Explanation: Incremental backup using snapshot
Explanation: The user id and password for the
difference feature is only available on IBM Tivoli
specified NAS Filer have been either not configured or
Storage Manager AIX 64 bit and Linux 86 clients.
have been specified incorrectly.
System action: Processing stops.
System action: Processing stops.
User response: Try the command again with an IBM
User response: Use the 'set password -type=filer'
Tivoli Storage Manager AIX 64 bit or Linux 86 client.
command to define the user id and password for the
specified NAS Filer and retry the incremental backup
operation. FMV2842E Tivoli Storage Manager for Virtual
Environments detected an error with the
createsnap: keyword. createsnap:yes is
FMV2838W The file path 'filename' exceeds HSM
specified while also specifying
maximaum path length.
vmsnapname:VMWare Snapshot Name.
Explanation: A file that you tried to migrate has a
Explanation: While parsing the Input File for IBM
path name that is too long.
Tivoli FlashCopy Manager for VMWare offload backup,
System action: File skipped from migration. an error condition was detected with VM Ware
snapshot handling. Specifying a VMWare Snapshot
User response: Place files into a shorter path to make
name while specifying createsnap:yes is not allowed.
them available for migration.
System action: The operation cannot continue without
specifying the correct createsnap: and vmsnapname:
FMV2839E Failed with ONTAPI error 'error_code'
combination.
while connecting to NetApp Filer
'filer_name' using user id 'id_name'. You User response: This is a result of the -I Inputfile
might have provided credentials containing conflicting input for createsnap: and
incorrectly for this Filer. vmsnapname: keywords. If you intend to have Tivoli
Storage Manager for Virtual Environments use a

Chapter 6. FMV messages 419

FMV2849E • FMV2857E

VMWare Snapshot created by FlashCopy Manager then User response: See other error messages to determine
specify createsnap:no with a valid VMWare Snapshot why the base could be established.
for the vmsnapname: keyword.
FMV2854E Unable to establish diff snapshot on
FMV2849E Incremental backup operation using volume .
snapshot difference failed because a
Explanation: A diff snapshot could not be created or
snapshot matching 'snapshot name' could
selected on the specified volume.
not be located on volume NAS volume.
System action: Processing stops.
Explanation: A snapshot name or pattern specified by
the BASESNAPSHOTNAME or User response: See other error messages to determine
DIFFSNAPSHOTNAME option could not be located on why the diff could be established.
the volume being backed up.
System action: Processing stops. FMV2855W Tivoli Storage Manager for Virtual
Environments detected an error while
User response: Rety the operation and specify a
parsing the Input File 'input file'. The
snapshot with the BASESNAPSHOTNAME or
'specifier' should not be specified when
DIFFSNAPSHOTNAME which exists on the specified
using 'specifier'. Option will be ignored.
volume.
Explanation: While parsing the Input File an error
occurred.
FMV2850E Error Creating Snapshot: Volume NAS
volume is a snapmirror destination System action: The operation will continue ignoring
volume. this parameter.
Explanation: An attempt was made to create a User response: This is usually the result of an
snapshot on a read only snapmirror destination identifier used with the wrong option. Please check that
volume. the options in the Input File matches the requested
operation and retry the operation.
System action: Processing stops.
User response: Rety the operation using the
FMV2856E Tivoli Storage Manager for Virtual
USEEXISTINGBASE and DIFFSNAPSHOT=latest
Environments detected that the node
options.
name representing the vCloud is not
specified.
FMV2851E Snapshot Processing Error: .
Explanation: A node name that represents the vCloud
Explanation: An error occurred due to the reason is not specified in the VMCLI profile.
specified in the message
System action: The operation cannot continue without
System action: Processing stops. a valid vCloud node name.
User response: Ensure that the specified volume is User response: Specify the vCloud node name in the
online and allows write access. VE_VCENTER_NODE_NAME parameter in the VMCLI
profile. Then, try the operation again.
FMV2852W Registered Base Snapshot '' no longer
exists on volume . FMV2857E Tivoli Storage Manager for Virtual
Environments detected while parsing
Explanation: The specified base snapshot registered by
'read in line' from the input file 'input file'
the previous backup no longer exists on the specified
that option 'specifier' is required for
volume.
'operation' operation.
System action: Processing continues.
Explanation: A required option or identifier is missing
User response: The client will attempt to use an from the input file.
existing snapshot older than the missing registered
System action: The operation stops.
snapshot as the base for the current backup.
User response: This may be the result of a missing
option or identifier. Verify that the syntax of the
FMV2853E Unable to establish base snapshot on
command and the syntax of the values in the input file
volume .
are correct. Then, try the operation again.
Explanation: A base snapshot could not be created or
selected on the specified volume.
System action: Processing stops.

420 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2858E • FMV2866E

System action: The snapshot differential backup

FMV2858E Failed to get the list of available VMs
continues, but with a warning return code of at least 8.
for backup
User response: Identify and repair the problem that
Explanation: Failed to get the entire list of VMs in
caused the command to fail. Consider wrapping the
order to choose ones that needed to be backed up.
command in a script that always exits with a return
System action: The operation was stopped code of zero.
User response: Verify that configuration parameters
for connection to vCenter. FMV2863E The backup-archive client failed to load
the vCloud protection runtime library.
FMV2859E Failed to locate the Organization VDC Explanation: vCloud protection runtime library is not
node that is used to store the backed up loaded by the backup-archive client.
data.
System action: The operation is stopped
Explanation: The Organization VDC node that stores
User response: Verify that the vCloud runtime library
the backed up vApp data was not located. This node
exist in the 'plugins' folder under the client installation
must be mapped to the Provider VDC node. This issue
folder.
might be caused by invalid mapping between the
Provider VDC node and the Organization VDC node.
FMV2864E A Hyper-V operation was attempted, but
System action: The operation was stopped
the Hyper-V role was not detected on
User response: Go to the Configuration page and click the host system.
'Run the Configuration Wizard' to verify that mapping
Explanation: The Hyper-V role must be enabled on
information for the Provider VDC node is valid.
the host system where the Hyper-V operation occurs.
The current host system either does not have the
FMV2860E The PRESNAPSHOTCMD command Hyper-V role enabled or does not support Hyper-V.
failed. The snapshot differential backup
System action: The operation does not start.
will not be executed.
User response: If the host system supports Hyper-V
Explanation: The command specified by the
then enable the Hyper-V role. Otherwise, try the
PRESNAPSHOTCMD option must complete
operation again from a host system that supports
successfully in order to execute the snapshot
Hyper-V and has the Hyper-V role enabled.
differential backup. If the command completed with a
return code of 0 (zero), it is considered to have If you want to process VMware virtual machines, go to
completed successfully. If the command completed with the IBM Tivoli Storage Manager window, and click Edit
any other return code, it is considered to have failed. If > Client Preferences > VM Backup. Click VMWare Full
the command failed then the snapshot differential VM or VMWare File Level. Then, click OK.
backup is not executed.
System action: The client does not execute the FMV2865E An error occurred creating or accessing a
snapshot differential backup operation. virtual disk for virtual machine
'VM-name'.
User response: Identify and repair the problem that
caused the command to fail. If a non-zero return code Explanation: An error occurred creating or accessing a
is normal for this command, then consider wrapping virtual disk while restoring a virtual machine.
the command in a script that always exits with a return
code of zero. System action: The virtual machine is not restored.
User response: See the client error log for more
FMV2861W The POSTSNAPSHOTCMD command detailed information about the error.
failed.
Explanation: If the command specified by the FMV2866E An error occurred creating virtual
POSTSNAPSHOTCMD option completed with a machine 'VM-name'.
non-zero return code, the snapshot differential backup Explanation: An error occurred creating the virtual
operation continues. The operation continues with a machine during the restore operation.
warning-level result. The result of the
POSTSNAPSHOTCMD command does not supersede a System action: The virtual machine is not restored.
higher result from the snapshot differential backup User response: See the client error log for more
command. For example, if the snapshot differential detailed information about the error.
backup command completed with code 12, a lower
return code from the POSTSNAPSHOTCMD command
does not alter the return code.

Chapter 6. FMV messages 421

FMV2867E • FMV2889I

User response: Check the user privileges include

FMV2867E An error occurred querying virtual
access to virtual disk writes or move the disk to an
machine 'VM-name'.
accessible location.
Explanation: An error occurred querying the virtual
machine during the restore operation.
FMV2873I Virtual machine 'vmname' was
System action: The virtual machine is not restored. successfully restored. If this virtual
machine was restored to a cluster,
User response: See the client error log for more
ensure that the cluster settings enable
detailed information about the error.
the restored virtual machine to operate
in high availability mode. High
FMV2868E An error occurred removing virtual availability settings, and the preferred
machine 'VM-name'. set of hypervisor nodes that can operate
in high availability mode, might not be
Explanation: An error occurred removing the virtual set automatically.
machine during the restore operation.
Explanation: The specified virtual machine has been
System action: The virtual machine is not restored. restored, but the restore process does not alter
User response: See the client error log for more Microsoft Failover Clustering High Availability settings.
detailed information about the error. If you restored a virtual machine that you previously
deleted, or if you restored a virtual machine to a new
name and location, the restored virtual machine might
FMV2869E A virtual machine on the hypervisor has not be enabled as a high availability resource. Enable
a different name but the same ID as high availability for this virtual machine by using
virtual machine to restore 'VM-name' Microsoft Failover Cluster Manager, System Center
has. Restore not allowed. Virtual Machine Manager, or by using PowerShell
Explanation: A virtual machine with a different name cmdlets.
and the same ID than the virtual machine being System action: Processing continues.
restored exists on the hypervisor.
User response: Use Microsoft Failover Cluster
System action: The virtual machine is not restored. Manager, System Center VM manager, or PowerShell to
User response: Choose a different virtual machine to configure the cluster to allow this virtual machine to
restore to or delete the existing virtuual machine. perform in a high availability configuration.

FMV2870W An incremental backup of virtual FMV2888E Backup VM Full VM Incremental is

machine 'vmname' was requested, but the unable to run. A valid TSM for Virtual
virtual machine lacks an existing Environments license file (license-file)
recovery snapshot. A full backup will be cannot be located.
taken to prevent data loss. Explanation: The license file was not found, or cannot
Explanation: Removal of the recovery snapshot of a be opened because of permissions, or the file is
virtual machine does not reset the last successful corrupted.
backup time maintained internally. The lack of a reset System action: The system returns to the calling
creates an inconsistency between the backup time and procedure.
the hard disk configuration of the virtual machine. A
full backup fixes the ambiguity and prevent data loss. User response: Check permissions on file. See if the
license file is in the correct place.
System action: An inconsistency in the virtual
machine configuration was detected.
FMV2889I The vApp 'vapp name' was successfully
User response: Avoid deleting the recovery snapshot restored under the name 'new vapp name'
between back up operations.
Explanation: The restore operation was succesful in
restoring the vApp into the specified name.
FMV2872E Tivoli Storage Manager was unable to
restore a virtual disk user metadata System action: This message is for informational
entry of virtual machine 'vmname' to purposes only.
disk 'diskpath'. User response: No action is required.
Explanation: An attempt to restore a user metadata
entry of a disk failed. The user metadata of the disk
may inaccessible or unreachable.
System action: A restore of a virtual disk.

422 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV2890E • FMV2998I

User response: Run the operation again and specify

FMV2890E Restore of vApp 'vapp name' failed.
the -domain option.
Explanation: The restore operation on the vCloud for
the specified vApp failed.
FMV2901E Tivoli Storage Manager for Virtual
System action: The operation stops. Environments detected that the domain
user was not specified.
User response: Check the dsmerror.log file for
information about why the restore operation failed. Explanation: While parsing the command line options,
Then, try the operation again. If the problem persists, no domain user was detected. This error occurred
search the Tivoli Storage Manager Support web site because the -user option was not specified.
(http://www.ibm.com/software/sysmgmt/products/
System action: The operation cannot continue without
support/IBMTivoliStorageManager.html) for known
a valid domain user.
solutions.
User response: Run the operation again and specify
the -user option.
FMV2891W The vApp 'vapp name' was successfully
restored. However, failed vms num out of
existing vms num VMs were not restored. FMV2902E Save domain password failed in
function func-name with return code
Explanation: Although the vApp restore operation on
return-code.
the vCloud completed successfully, one or more VMs
were not restored. Explanation: An unexpected write access error
occurred when the function tried to save the domain
System action: The operation completed successfully.
password. Write access does not exist to either the
However, some VMs were not restored.
registry or to the Tivoli Storage Manager for Virtual
User response: Check the dsmerror.log file for Environments on Linux installation folder where the
information about why the VMs were not restored. password file is saved.
Then, try the operation again. If the problem persists,
System action: The operation ends.
search the Tivoli Storage Manager Support web site
(http://www.ibm.com/software/sysmgmt/products/ User response: Grant write access to either the
support/IBMTivoliStorageManager.html) for known registry or to the Tivoli Storage Manager for Virtual
solutions. Environments on Linux installation folder and try the
operation again.
FMV2892E Restoring VM 'vm name' of vApp 'vapp
name' failed (Error error code occurred). FMV2903E Read domain password failed in
function func-name with return code
Explanation: The VM identified in the error message
return-code.
was not restored. The error code identified in the
message indicates why the VM was not restored. Explanation: An unexpected error occurred when the
However, the restore operation for the vApp that function tried to read the domain password.
contains the VM continues to process.
System action: The operation ends.
System action: Restore processing for the vApp
continues. User response: On Windows, verify that the password
exists in the registry. On Linux, verify that the
User response: Check the dsmerror.log file for password exists in the password file. Try the operation
information about why the VM was not restored. Then, again.
try the operation again. If the problem persists, search
the Tivoli Storage Manager Support web site
(http://www.ibm.com/software/sysmgmt/products/ FMV2998I The option 'option' that was found in the
support/IBMTivoliStorageManager.html) for known include/exclude file 'file-name' at the line
solutions. number: number is not supported and
will be ignored by the client.

FMV2900E Tivoli Storage Manager for Virtual Explanation: The specified option is valid but not
Environments detected that the scan supported on the current platform and will be ignored
domain was not specified. by the client.

Explanation: While parsing the command line options, System action: Processing continues.
no scan domain was detected. This error occurred User response: You can ignore the message or remove
because the -domain option was not specified. the option from the include/exclude file.
System action: The operation cannot continue without
a valid scan domain.

Chapter 6. FMV messages 423

FMV3000I • FMV3009E

FMV3000I communication-type communications FMV3005I Session for user userid terminated - idle
available on port port-number. for idle-minutes minutes.
Explanation: The specified communications are Explanation: A session was terminated for the
available on the specified port number. specified user because there was no activity on the
session for the specified number of minutes.
System action: None.
System action: The session with the specified user is
User response: None.
terminated.
User response: Re-start the remote client to begin a
FMV3001E Error initializing HTTPS
new session.
communications - Secure HTTP not
available.
FMV3006I Processing request for the Tivoli Storage
Explanation: An error occurred initializing HTTPS
Manager Web Client (ip-address).
communications. Processing will continue, but secure
HTTP communications will not be available. Explanation: A request for the Web Client is being
processed.
System action: Processing continues, but secure HTTP
communications will not be available. System action: None.
User response: Check the console and error logs to User response: None.
determine why secure HTTP communications was
unable to start, correct the problem, and restart the
FMV3007I Tivoli Storage Manager client-name
client.
terminating - idle for idle-minutes
minutes.
FMV3002I Session started for user userid
Explanation: The specified client is terminating
(communication-method address).
because it has been idle for the specified time. It will be
Explanation: A session was started for the specified automatically started when it is needed.
user.
System action: The client program stops.
System action: None.
User response: None.
User response: None.
FMV3008E Too many symbolic links were detected
FMV3003I The new password is case sensitive. while resolving name 'file_name'
Explanation: Your account has been updated to use Explanation: While trying to resolve the file name, too
case sensitive password. many symbolic links were found.
System action: None System action: File skipped.
User response: Make sure to remember the new User response: Ensure that you do not have a looping
password as you enter it, including character casing. symbolic link for the file.
For more details, contact your Tivoli Storage Manager
administrator.
FMV3009E The Logical Volume Snapshot Agent
plugin library was not found.
FMV3004E Session for user userid terminated -
Explanation: The Logical Volume Snapshot Agent
invalid password entered.
(LVSA) plugin library should have been installed when
Explanation: A session was terminated for the the client was installed, but it cannot be found.
specified user because an invalid password was
System action: The selected operation is not
entered.
performed.
System action: The session with the specified user is
User response: Try the operation again. If the problem
terminated.
recurs, re-install the Tivoli Storage Manager client
User response: Re-start the remote client and enter the software. If the problem persists, contact IBM technical
correct password for the specified user. support for further assistance.

424 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV3010E • FMV3103E

FMV3010E The snapshot wizard operation failed. FMV3014E Expose snapshot failed for backup
document 'xml-backup-doc-file'.
Explanation: The snapshot wizard operation failed
with a non-zero return code. Check the error log for Explanation: Expose snapshot failed.
additional information.
System action: Processing stops
System action: The selected operation is not
User response: See the dsmerror.log file for further
performed.
details.
User response: Review the error log for any error
messages, and then retry the operation after correcting
FMV3100E Unable to get the iSCSI initiator name.
the cause for failure.
The Windows error is (error)
Explanation: The iSCSI initiator name is not
FMV3011E Previous changes have not been
configured on the system.
commited. The machine must be
rebooted before this operation can be System action: The operation stops.
performed
User response: See the appropriate Microsoft
Explanation: A previous operation required the Documentation about how to configure the iSCSI
machine to be rebooted for the changes to take effect, initiator name.
but the machine has not been rebooted. The machine
must be rebooted before this selected operation can be
performed. FMV3101E The mount operation for virtual
machine 'vmname' failed with rc =
System action: The selected operation is not return-code
performed.
Explanation: An error occurred during the mount
User response: Reboot the machine and then retry the operation. See the output from the previous operation
operation. to identify the cause of the error.
System action: Processing stops.
FMV3012E The Logical Volume Snapshot Agent is
not installed. Use the Setup Wizard to User response: Check the error log for information
configure either Online Image or Open about how to resolve this issue.
File support and choose the Logical
Volume Snapshot Agent as the snapshot FMV3102I 'VMNAME' mounted successfully and is
provider. ready
Explanation: The selected operation requires the Explanation: The mount operation for the specified
Logical Volume Snapshot Agent, but it is not installed. virtual machine completed successfully. As a result, the
Use the Setup Wizard to install the LVSA. virtual machine is ready for a file-level restore
System action: The selected operation is not operation.
performed. System action: None.
User response: Retry the operation after installing the User response: None
Logical Volume Snapshot Agent.

FMV3103E Unable to load the dynamic link library

FMV3013E The specified snapshot provider is not (iscsidsc.dll). The Windows error is
supported on this version of the (error)
operating system.
Explanation: The iSCSI dynamic link library
Explanation: The specified snapshot provider is not (iscsidsc.dll) cannot be found on the system.
supported on the version of the operating system you
are currently running. If another snapshot provider is System action: The operation stops.
available, select it and retry the operation. User response: See the appropriate Microsoft
System action: The selected operation is not Documentation about how to install the dynamic link
performed. library (iscsidsc.dll).

User response: If another snapshot provider is

available, select it and retry the operation.

Chapter 6. FMV messages 425

FMV3104E • FMV3112E

recover files from any of the file systems or volumes

FMV3104E A target was not found on the iSCSI
that use this disk.
portal The missing target is 'target'
System action: The operation continues.
Explanation: The iSCSI portal is unable to discover all
of the targets that were created by the IBM Tivoli User response: If files from the affected file systems or
Storage Manager Recovery Agent command-line volumes must be recovered, ensure that the disk is
interface. included in the backup.
System action: The operation stops.
FMV3109E Operation "name failed with Windows
User response: See the appropriate Microsoft
error code code ("text")!
Documentation about how to correct this iSCSI portal
issue. Search http://technet.microsoft.com/en-US/ Explanation: A Windows API function returned with a
windowsserver for iSCSI troubleshooting information. specific error code.
System action: The operation stops.
FMV3105E Unable to connect all targets on the
iSCSI Portal The target that is not User response: See the other error messages that were
connected is 'target'. Windows error is returned with this operation to identify the cause of the
(error) failure.

Explanation: The iSCSI portal is unable to connect all

discovered targets that were created by the IBM Tivoli FMV3110E Unable to communicate with Windows
Storage Manager Recovery Agent command-line device 'device'. The Windows error is
interface. (error)

System action: The operation stops. Explanation: A Windows API call failed to open a
Windows device.
User response: See the appropriate Microsoft
Documentation about how to correct this iSCSI portal System action: The operation stops.
issue. Search http://technet.microsoft.com/en-US/ User response: See the appropriate Microsoft
windowsserver for iSCSI troubleshooting information. Documentation for information about how to resolve
this Windows API call issue.
FMV3106E Windows Configuration Manager is
unable to scan for new hardware. FMV3111E Unable to mount the same dynamic
Windows error is (error) disks mutliple times. The disk 'disk'
Explanation: The new iSCSI disk connection cannot be signature is the same as the disk
detected by the Windows Configuration Manager. signature of another disk that is online.

System action: The operation stops. Explanation: It is not possible to attach a second disk
to the system with the same disk signature.
User response: See the appropriate Microsoft
Documentation about how to correct this hardware System action: The operation stops.
scan issue. User response: The other disk with the identical disk
signature must be dismounted before you can attempt
FMV3107E The attempt to retrieve information for the operation again.
disk 'disk' failed with Windows error
(error). FMV3112E Windows Virtual Disk Service is not
Explanation: A Windows API call failed to retrieve the able to detect all new devices.
disk information. Explanation: The Virtual Disk Service VDS is unable
System action: The operation stops. to access all iSCSI targets. Some targets are missing or
not working.
User response: See the appropriate Microsoft
Documentation for information about how to resolve System action: The operation will be rolled back and
this Windows API call issue. stopped.
User response: Determine why the data mover cannot
FMV3108W The disk with label='label' is not access some iSCSI targets. Determine that the TSM
mounted because it was excluded server is working correctly. Determine that the iSCSI
during the backup (Reason: 'reason'). service is running. Search the Windows event log for
problems with the missing devices.
Explanation: The disk cannot be mounted because it
was excluded during backup. It is not possible to

426 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV3113E • FMV3122E

FMV3113E The virtual machine 'name' has at least FMV3118E Unable to determine the operating
one mirror or RAID5 volume. Mirror system type of the VM to be restored.
and RAID5 support is disabled!
Explanation: The operating system type of the VM to
Explanation: During the mount operation it was be restored cannot be determined. This issue can occur
detected that the virtual machine has a mirror or when the restore parameter -VMOSType is not
RAID5 volumes. The support for such volumes were specified or it specifies an incorrect operating system
diabled by the Administrator. type.
System action: The operation stops. System action: The operation stops.
User response: Contact the Administrator for more User response: Use the -VMOSType parameter to
information. specify the correct operating system type of the VM to
be restored.
FMV3114E The attempt to retrieve information for
volume 'volume' failed with Windows FMV3119W Operating system type "name1" is
error (error). detected but operating system type
"name2" is specified.
Explanation: A Windows API call failed to retrieve the
volume information. Explanation: The operating system type of the
detected VM does not match the type specified with
System action: The operation stops.
the restore parameter -VMOSType. Inconsistent
User response: See the appropriate Microsoft operating system types might negatively impact the
Documentation for information about how to resolve mount operation. The operation will continue using
this Windows API call issue. "name2" as the operating system type.
System action: The operation continues.
FMV3115E The attempt to bring disk 'disk' online
User response: If the mount operation fails, try the
failed with Windows error (error).
operation again and use automatic detection or specify
Explanation: A Windows API call failed to bring the the correct operating system.
disk online.
System action: The operation stops. FMV3121E Unable to retrieve the iSCSI initiator
name from the Linux data mover.
User response: See the appropriate Microsoft
Documentation for information about how to resolve Explanation: The iSCSI initiator name for the Linux
this Windows API call issue. data mover is not configured or not formatted correctly.
System action: The operation stops.
FMV3116E The attempt to create directory 'dir'
User response: On the Linux data mover, verify that
failed with Windows error (error).
the /etc/iscsi/initiatorname.iscsi file exists and is
Explanation: A Windows API call failed to create the accessible. If the file exists and is accessible, verify that
directory. the file content is formatted correctly as shown here:
InitiatorName=iqn.<Year>-<Month>.<domain name
System action: The operation stops. backward>:<unique number. Here is an example of a
User response: See the appropriate Microsoft MAC address:> InitiatorName=iqn.2014-
Documentation for information about how to resolve 04.com.ibm:0123456789ABCDEF The iSCSI initiator
this Windows API call issue. name must be a unique name in your network.

FMV3117E The mount volume attempt at directory FMV3122E The Microsoft iSCSI Initiator Service
'dir' failed with Windows error (error). encountered an error. The Windows
error is (error).
Explanation: A Windows API call failed to mount the
specified volume. Explanation: The Microsoft iSCSI Initiator Service
encountered an error during an iSCSI operation. This
System action: The operation stops. error caused the operation to stop.
User response: See the appropriate Microsoft System action: The operation stops.
Documentation for information about how to resolve
this Windows API call issue. User response: See the Microsoft iSCSI Initiator
Service error message to determine the cause of the
error. If necessary, see the appropriate Microsoft

Chapter 6. FMV messages 427

FMV3123E • FMV3130E

Documentation for information about how to resolve

FMV3127E The IP address or port of the Linux
this iSCSI Initiator error.
mount proxy partner could not be
found.
FMV3123E Unable to read or write the local VM
Explanation: An error occurred while querying the
file-level restore data. filename File
IBM Tivoli Storage Manager server for the Linux mount
cannot be accessed or is damaged.
proxy partner. The IP address or port of that partner
Explanation: For VM file-level restore operations, data could not be found; the address and port are required
must be stored on the local data mover in a directory to process file-level restores for Linux VMs.
that the user running the restore can access. It can also
System action: Processing stops.
be that the data file was damaged!
User response: Check the node configuration and
System action: Processing stops.
ensure that the Linux mount proxy partner is correctly
User response: To store the VM file-level restore data, configured and running. Verify that the Client Acceptor
the data mover application requires read and write Daemon on the Linux mount proxy partner is running
access to the C:\Documents and Settings\AllUsers\ and able to connect to the IBM Tivoli Storage Manager
Application Data\Tivoli\TSM\ or C:\ProgramData\ server.
Tivoli\TSM folder. Set the access rights to this directory
so that your user has the correct rights. If the file was
FMV3128E The node name of the Windows mount
damaged it can be helpfull to replace the current
proxy does not comply with Tivoli
version with the .bak file.
Storage Manager naming conventions.
Explanation: An error occurred while querying the
FMV3124E The VM File Level Restore Mount
IBM Tivoli Storage Manager server for Linux mount
Cleanup of virtual machine 'vmname'
proxy partner. The name of the Windows mount proxy
failed with rc = return-code
does not comply the naming convention. A correct
Explanation: An error occurred during processing of a name is required for processing of Linux VMs.
VM file-level restore mount cleanup.
System action: Processing stops.
System action: Processing stops.
User response: Check the node configuration and
User response: Check the error log for information ensure that the mount proxy name is correct. Use the
that led to this failure. web based configuration wizard to set up the
configuration.

FMV3125E The local data for file-level restore

mount with the ID: id and virtual FMV3129I The mount cleanup of VM 'VMNAME'
machine name 'name' cannot be found! completed.
Explanation: The local data set for the specified Explanation: The mount cleanup operation for the
mount ID or virtual machine name cannot be found specified virtual machine completed.
System action: The operation stops. System action: None.
User response: Use the query "dsmc q vm <name> User response: None
-vmrestoretype=mount" command to get the correct
mount ID and virtual machine name for the cleanup
FMV3130E The mount cleanup operation for virtual
machine 'vmname' failed with rc =
FMV3126E The node name of the Linux mount return-code
proxy partner could not be found.
Explanation: An error occurred during the mount
Explanation: An error occurred while querying the cleanup operation. See the output from the previous
IBM Tivoli Storage Manager server for Linux mount operations to identify the cause of the error.
proxy partner; the node could not be found.
System action: Processing stops.
Communications with the Linux mount proxy partner
is required to perform Linux VM file-level restore User response: Check the dsmerror.log file for
operations. information about how to resolve this issue.
System action: Processing stops.
User response: Check the Linux mount proxy partner
node configuration and ensure that the node is
correctly configured and running.

428 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV3131E • FMV3139E

FMV3131E The operation to disconnect the iSCSI FMV3135E The removal of iSCSI Portal 'target'
targets from the Windows data mover failed with a Windows error of (error)
failed.
Explanation: The iSCSI Service cannot remove the
Explanation: An error occurred during the mount iSCSI Portal.
cleanup operation while disconnecting the iSCSI
System action: The operation stops.
targets. See the output from the previous operations to
identify the cause of the error. User response: See the Microsoft documentation for
information to correct this iSCSI portal issue. Search
System action: Processing stops.
http://technet.microsoft.com/en-US/windowsserver
User response: Open the Windows iSCSI Initiator Tool for iSCSI troubleshooting information.
and disconnect the targets and remove the target portal.
The tool can be found in "Administrative Tools" ->
FMV3136E The mount ID was not specified in the
"iSCSI Initiator"
cleanup operation.
Explanation: The -MOUNTID parameter must be
FMV3132E The Windows iSCSI Service is unable to
specified to perform a 'mountcleanup' operation.
get a list of all currently running
sessions. The Windows error is (error) System action: The operation stops.
Explanation: The iSCSI Service could not get a list of User response: Use the query "dsmc q vm <name>
all connected targets and the corresponding sessions. -vmrestoretype=mount" command to get the correct
mount ID for the cleanup
System action: The operation stops.
User response: See the Microsoft documentation for
FMV3137W 'VMNAME' mount completed with
information to correct this iSCSI issue. Search
errors.
http://technet.microsoft.com/en-US/windowsserver
for iSCSI troubleshooting information. Explanation: The mount operation for the specified
virtual machine completed with errors. Only a subset
of the virtual machine's disks are ready for a file-level
FMV3133E The target 'target' could not be
restore operation.
disconnected by the iSCSI portal. The
Windows error is (error) System action: The VM disks that failed were
reported in previous messages.
Explanation: The iSCSI portal is unable to disconnect
all the connected targets that were created by the User response: Read the previous error messages for
recovery agent command-line interface. the cause of each failure.
System action: The operation stops.
FMV3138E The unmount of the volumes failed
User response: See the Microsoft documentation for
during the cleanup operation of mount
information to correct this iSCSI portal issue. Search
ID mountid
http://technet.microsoft.com/en-US/windowsserver
for iSCSI troubleshooting information. Explanation: An error occurred during the mount
cleanup operation while unmounting the volumes.
FMV3134E The Windows iSCSI Service is unable to System action: Processing stops.
get list of all currently available portals.
The Windows error is (error) User response: See the output from the previous
operations to identify the cause of the error.
Explanation: The iSCSI Service has a problem getting
a list of all available portals.
FMV3139E The attempt to unmount the disk failed
System action: The operation stops. with Windows error (error).
User response: See the Microsoft documentation for Explanation: The Windows API call failed to unmount
information to correct this iSCSI portal issue. Search the disks.
http://technet.microsoft.com/en-US/windowsserver
for iSCSI troubleshooting information. System action: The operation stops.
User response: See the Microsoft documentation for
information to correct this issue; search the
documentation for this Windows error.

Chapter 6. FMV messages 429

FMV3140E • FMV3149E

perform a file level restore operation. For VM instant

FMV3140E The connection to the following iSCSI
access and instant restore no action is required.
targets failed: 'target_list'.
Explanation: The iscsiadm command-line interface
FMV3145E A Windows API call has failed.
was not able to connect to the specified iSCSI targets,
from the Linux mount proxy machine. Explanation: A Windows API call has failed.
System action: The operation stops. System action: Operations cannot continue.
User response: If the target is already connected on User response: See the dsmerror.log for more
the Linux mount proxy machine, log out from the information.
target, for example: iscsiadm -m node -T targetname
--logout Also, verify that the iSCSI server address is
correctly specified. FMV3146E The cleanup operation to unmount the
volume volume failed. The mounted file
system is busy.
FMV3141W Mounting the following devices failed:
'device_list'. Explanation: An error occurred during the mount
cleanup operation while unmounting the volumes on
Explanation: It was not possible to mount the the Linux mount proxy machine.
specified devices on the Linux mount proxy machine.
System action: Processing stops.
System action: The operation continues to mount the
other devices. User response: Ensure the file system is not in use
and then try the cleanup operation again, or manually
User response: Perform a cleanup, or try to manually unmount the volume on the host.
unmount the devices on the Linux mount proxy
machine.
FMV3147W The iSCSI Target 'iscsi_target'was
disconnected successfully, but the
FMV3142E The Windows Virtual Disk Service attempt to delete the target failed.
encountered an error. The Windows
error is (error) Explanation: It was not possible to delete the object
after the target was disconnected.
Explanation: The Windows Virtual Disk Service is not
working correctly. System action: The operation continues.

System action: The operation stops. User response: Try to manually delete the object on
the Linux machine. For example: iscsiadm -m node -T
User response: See the Microsoft documentation for targetname -o delete
information to correct this issue. Search
http://technet.microsoft.com/en-US/windowsserver
for Virtual Disk Service troubleshooting information. FMV3148W The iSCSI Target 'iscsi_target' was
already connected.

FMV3143W The ISCSI service is not running. Its Explanation: The target was already connected on the
state is 'state'. Linux mount proxy machine. This error can occur if a
cleanup was not perfomed, or if the cleanup was only
Explanation: The ISCSI Service is not running. partially successful.
System action: The service maybe suspended, System action: The operation continues.
however operations cannot continue.
User response: The Linux mount proxy machine tried
User response: Start the ISCSI service. to reuse the already connected targets. If the volumes
are not correctly mounted, manually disconnect the
targets on the Linux mount proxy machine. For
FMV3144W The ISCSI service is not running. File
example: iscsiadm -m node -T targetname --logout;
level restore mount operations will not
iscsadm -m node -T targetname -o delete
work.
Explanation: The ISCSI Service is not running. This
FMV3149E The iSCSI target 'target' failed to
service is required on the Windows and Linux mount
disconnect from the Linux machine. The
proxy for file level restore mount operations. Full VM
message from the iscsiadm
instant access and instant restore are not affected.
command-line interface is:
System action: Mount operations for file level restore message_output
cannot continue.
Explanation: The iscsiadm command-line interface
User response: Start the ISCSI service if you want to

430 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV3150W • FMV3158W

was unable to disconnect the specified iSCSI target

FMV3154E The ISCSI service is not installed.
from the Linux machine.
Explanation: The ISCSI Service is not installed.
System action: The operation stops.
System action: Operations cannot continue.
User response: See if the target is already
disconnected on the Linux machine, or try to manually User response: Install the ISCSI service for your
disconnect it. For example, iscsadm -m node -T platform.
targetname --logout Verify that the iSCSI server address
is correctly specified.
FMV3155I The Windows data mover is 'name' (ip)
Explanation: The DNS name and the IP of the
FMV3150W The block device 'block_device' of type
Windows data mover.
'device_type' failed to mount. The system
message is: 'system_message' System action: None.
Explanation: It was not possible to mount one or User response: This information can be used to
more devices on the Linux machine. determine if hostname and IP of the Windows data
mover are correctly resolved. The information can help
System action: The operation continues to mount the
if the iSCSI connection is not working as expected.
other devices.
User response: Perform a cleanup, or try to manually
FMV3156I The iSCSI server address used is 'ip'
unmount the devices on the Linux machine.
Explanation: This message returns the IP address of
the iSCSI server.
FMV3151E The initiator.iscsi file does not exist or
cannot be opened. System action: None.
Explanation: The file does not exist or cannot be User response: This information can be used to
opened. determine if the IP address of the iSCSI server address
is correctly resolved. The information might help you
System action: Operations cannot continue.
troubleshoot problems if the iSCSI connection is not
User response: The ISCSI service may not be installed. working as expected.

FMV3152E The initiator.iscsi file does not have a FMV3157I The Linux data mover is 'name' (ip)
valid initiator id entry.
Explanation: The DNS name and the IP address of the
Explanation: No ISCSI Initiator ID exists. Linux data mover.
System action: Operations cannot continue. System action: None.
User response: The ISCSI servoce may not be User response: This information can be used to
installed. determine if hostname and IP of the Linux data mover
are correctly resolved. The information might help you
troubleshoot problems if the iSCSI connection is not
FMV3153E The mount cleanup completed with
working as expected.
error for mount ID 'mountid' of virtual
machine 'VMNAME'; Error log 'errlog' is
available on 'machinename'. FMV3158W The attempt to create the Windows
share failed with Windows error (error).
Explanation: An error occurred during the mount
The share is not created.
cleanup operation while unmounting the volumes. The
mounted file systems may be busy. See the error log to Explanation: The creation of the Windows share failed
identify the cause of the error. with the given user/group name.
System action: Processing stops. System action: The Windows share is not created. The
operation continues.
User response: Ensure the file systems are not in use
and the cleanup or manually unmount the volumes on User response: One common reason for failures is that
the host. the specified user/group does not exist. Ensure that the
Windows user or group name exists and is accessible
on the Windows data mover. If this is a domain user or
group, the Windows data mover has to be part of that
domain. If this does not resolve the problem, see the
appropriate Microsoft Documentation for information
about this error code.

Chapter 6. FMV messages 431

FMV3159E • FMV3168E

FMV3159E The attempt to remove the Windows FMV3164W The minimum level for 'os' is 'level'. Your
Share failed with Windows error (error). current level is 'actual'.
Explanation: A Windows API call failed to remove the Explanation: The Linux Operating System is not at the
Windows Share. minimum level.
System action: The operation stops. System action: Mount operations may not complete
successfully.
User response: See the appropriate Microsoft
Documentation for information about how to resolve User response: Upgrade the Linux operating system
this Windows API call issue. to at least the minimum level.

FMV3160W The attempt to export Linux file system FMV3165W A Package installed on the Linux
failed with error: NFS service is not Operating System is not at the
running. minimum level. Mount operations may
not complete successfully.
Explanation: exportfs command failed to make the
directory on the Linux mount proxy available for NFS Explanation: A Package installed on the Linux
clients to mount. Operating System is not at the minimum level.
System action: The operation continues without System action: Mount operations may not complete
creating the NFS export. successfully.
User response: Resolve the error on the Linux mount User response: Upgrade the package to at least the
proxy. Manually export the directory. minimum level.

FMV3161E The attempt to unexport Linux file FMV3166W The minimum level for package 'package'
system failed with error: NFS service is is 'level'. Your current level is 'actual'.
not running.
Explanation: A Package installed on the Linux
Explanation: exportfs command failed to unexport the Operating System is not at the minimum level.
directory on the Linux mount proxy.
System action: Mount operations may not complete
System action: The operation stops. successfully.
User response: Resolve the error on the Linux mount User response: Upgrade the package to at least the
proxy. Manually unexport the directory. minimum level.

FMV3162I The Mount cleanup of VM 'VMNAME' FMV3167E IBM Tivoli Storage Manager Recovery
with mount id 'Id' and snapshot date Agent service is not installed.
'date time' completed.
Explanation: IBM Tivoli Storage Manager Recovery
Explanation: The mount cleanup operation for the Agent service is not installed.
specified virtual machine completed.
System action: Operations cannot continue.
System action: None.
User response: Ensure that IBM Tivoli Storage
User response: None Manager Recovery Agent is correctly installed and
configured.
FMV3163W The Linux Operating System is not at
the minimum level. Mount operations FMV3168E IBM Tivoli Storage Manager Recovery
may not complete successfully. Agent service is not running.
Explanation: The Linux Operating System is not at the Explanation: IBM Tivoli Storage Manager Recovery
minimum level. Agent service is not running.
System action: Mount operations may not complete System action: Operations cannot continue.
successfully.
User response: Start IBM Tivoli Storage Manager
User response: Upgrade the Linux operating system Recovery Agent service. The Recovery Agent can be
to at least the minimum level. started using "net start RecoveryAgent" or by
referencing TSM Recovery Agent in services.msc.

432 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV3169E • FMV3177E

FMV3169E The mount proxy's operating system is FMV3174E The VM mount failed.
not Windows 2008, or a newer, operating
Explanation: An error occurred during the mount
system.
operation.
Explanation: The Windows operating system is not at
System action: Processing stops.
the minimum level.
User response: Check the command-line output for
System action: Processing stops
the messages that specify what problems were
User response: Upgrade the Windows mount proxy to encountered during the operation.
a supported operating system.
FMV3175E The VM mount cleanup failed.
FMV3170W The attempt to export Linux file system
Explanation: An error occurred during the mount
failed with error: exportfs command
cleanup operation.
failed.
System action: Processing stops.
Explanation: exportfs command failed to make the
directory on the Linux mount proxy available for NFS User response: Check the command-line output for
clients to mount. the messages that specify what problems were
encountered during the operation.
System action: The operation continues without
creating the NFS export.
FMV3176W Unable to locate the Windows user or
User response: Resolve the error on the Linux mount
group named 'name'. The share is not
proxy. Manually export the directory.
created.
Explanation: Tivoli Storage Manager was unable to
FMV3171E The attempt to unexport Linux file
map the specified user or group name to a Windows
system failed with error: exportfs
security identifier.
command failed.
System action: The Windows share is not created. The
Explanation: exportfs command failed to unexport the
operation continues.
directory on the Linux mount proxy.
User response: One common reason for this message
System action: The operation stops.
is that the specified user or group does not exist.
User response: Resolve the error on the Linux mount Ensure that the Windows user or group name exists
proxy. Manually unexport the directory. and is accessible on the Windows data mover. If this is
a domain user or group, the Windows data mover has
to be part of that domain.
FMV3172T Restoring virtual machine 'source' to new
VM with name 'destination'. This message can also indicate that the Windows data
mover is not able to access the active directory domain
Explanation: The specified virtual machine will be
server. Ensure that network problems are not
restored as a new vm with a new name.
preventing the Windows data mover from
System action: None communicating with the active directory domain server.

User response: None.

FMV3177E No iSCSI target was connected. Check
your iSCSI options for backup-archive
FMV3173E The Linux devices failed to mount client.
correctly.
Explanation: No iSCSI target was found or connected
Explanation: The Linux devices failed to mount on the Linux mount proxy machine.
correctly.
System action: The operation is rolled back.
System action: Mount operations did not not
complete successfully. User response: Check that iSCSI is setup correctly on
your Windows as well as your Linux mount proxy. One
User response: Verify that the Linux mount proxy common reason for a failure is that the
server can communicate with the TSM server. VMISCSIServeraddress option is not specified or is set
incorrectly in the options file of the Windows data
mover.

Chapter 6. FMV messages 433

FMV3178E • FMV3404W

FMV3178E Volume 'volume' of type 'file_system_type' FMV3402W name: A system call func failed with code
has not been unmounted. System rc.
message: 'system_message'
Explanation: An error occurred while obtaining
Explanation: An error occurred during the mount information from the operating system. The volume
cleanup operation while unmounting the volumes on information could not be obtained.
the Linux mount proxy machine.
System action: Processing can continue if the
System action: Processing stops. information being obtained is not critical for the
operation or if it is expected behaviour in the context of
User response: Ensure the file system is not in use
the operation being performed.
and then try the cleanup operation again, or manually
unmount the volume on the Linux mount proxy. User response: Check the error log for any other
messages that might indicate a reason for the failure.
Try to correct any indicated problems, then try the
FMV3179W Another folder share with the same
operation again. If the problem persists, contact IBM
name 'name' already exists.
technical support for further assistance.
Explanation: Tivoli Storage Manager was unable to
create a folder share with the specified name because a
FMV3403W Volume name cannot be opened for
share with that name already exists
reading. System error code is err.
System action: The folder share is not created. The
Explanation: The named volume could not be opened.
operation continues and the VM disks are mounted for
Examples of why this can occur include, but are not
file-level recovery on the mount proxy.
limited to: the device is not a valid system device, the
User response: Use operating system commands to device is locked by another application, or the user
create the share of the folder with a unique name and does not have correct or permissions. The operating
delete it before running the dismount operation. system error code shown in the message indicates the
specific reason for the failure.

FMV3180W The parameter 'name' contains characters System action: Processing stops.
that are not allowed and have been
User response: Use your operating system's tools to
removed. Resulting value is 'new'
obtain the description of the error code. Also check the
Explanation: Some characters cannot be used on multi error log for any other messages that might indicate a
platform environments. To solve compatibly problems reason for the failure. Try to correct any indicated
only a limited set of characters are allowed on this problems, then try the operation again. If the problem
specific parameter. persists, contact IBM technical support for further
assistance.
Parameter "-MOUNTPoint" is restricted at
[a-z][A-Z][0-9][:][/][\][_]
FMV3404W An error occured reading volume name.
Parameter "-MOUNTTag" is restricted at
[a-z][A-Z][0-9][_] Explanation: The named volume could not be read.
Examples of why this can occur include, but are not
Parameter "-EXPORTParameter" is restricted on limited to: the data being read is outside the valid
Windows at [a-z][A-Z][0-9][ ][-][_][\][@] range of the volume, or the device is locked by another
Parameter "-EXPORTParameter" is restricted on Linux application. The operating system error code shown in
at [a-z][A-Z][0-9][.][:] the message indicates the specific reason for the failure.

System action: The operation continues with modified System action: If server-free data movement is used,
parameter. processing continues using non-server-free data
movement. Otherwise processing stops.
User response: None
User response: Use your operating system's tools to
obtain the description of the error code. Also check the
FMV3401W The entity name is invalid. error log for any other messages that might indicate a
Explanation: A volume with this name could not be reason for the failure. Try to correct any indicated
found or is not suitable for server-free operations. problems, then try the operation again. If the problem
persists, contact IBM technical support for further
System action: Processing stopped. assistance.
User response: Specify the correct name.

434 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV3405W • FMV3412I

obtain the description of the error code. Also check the

FMV3405W File system fs on volume name is
error log for any other messages that might indicate a
unknown.
reason for the failure. Try to correct any indicated
Explanation: The file system on the volume is not problems, then try the operation again. If the problem
supported for the operation being performed. persists, contact IBM technical support for further
assistance.
System action: If server-free data movement is used,
processing continues using non-server-free data
movement. Otherwise processing stops. FMV3410E The operating system refused a Tivoli
Storage Manager request for memory
User response: Check the error log for any other
allocation.
messages that might indicate a reason for the failure.
Try to correct any indicated problems, then try the Explanation: Tivoli Storage Manager requires access to
operation again. If the problem persists, contact IBM memory in order to store information as processing
technical support for further assistance. proceeds. In this case, more memory was requested
than the operating system would allocate. Possible
reasons include:
FMV3406W Physical mapping of the volume name is
not supported. v The system is low on memory.
v The process in which the program runs has exceeded
Explanation: The logical volume layout is not
the maximum memory that it is allowed to allocate.
currently supported for physical mapping.
v Some other error condition occurred that caused the
System action: program to think it is out of memory.
User response: Refer to the documentation for System action: Tivoli Storage Manager cannot
information on what volume layouts are supported for complete the requested operation.
physical mapping.
User response: Close all unneeded applications and
try the operation again. If the operation still fails, try
FMV3407W name is not local. dividing the task into serveral smaller units. For
Explanation: The drive or filesystem is not local and is example, if a file specification contains several high
not suitable for image backup. level directories, run the Tivoli Storage Manager task
serially for each directory. If the Tivoli Storage Manager
System action: Processing stopped. task is an incremental backup, use the option
"-memoryefficientbackup=yes".
User response: Specify a volume that is local.
For UNIX systems that support resource limits, check
to see b if the memory resource limit is too low by
FMV3408E System call 'umount' failed for volume
entering the following command: ulimit -a
'volume' with errno='error'. Please take
suitable action based on errno and retry Based on the resulting data, you can ask the UNIX
the operation. system root user to increase resource limits so that it
will override the current default. The UNIX system root
Explanation: Umount failed for the specified volume
user has the authority to increase resource limits.
with the indicated errno. Please take suitable action
based on errno and retry the operation.
FMV3411E Invalid arguments were passed to
System action: Processing stopped.
function name.
User response: Check errno for umount failure and
Explanation: The named function did not receive
take corrective action before retrying the operation.
correct arguments to proceed. Please check error log for
additional errors following this one for further
FMV3409W An error occurred writing to volume explanation.
name.
System action: Processing stops.
Explanation: Tivoli Storage Manager could not write
User response: Retry the operation. If problem persists
to the named volume. Examples of why this can occur
contant your Tivoli Storage Manager administrator.
include, but are not limited to: the data being written is
outside the valid range of the volume, or the device is
locked by another application. The operating system FMV3412I DiskMapper does not support name for
error code shown in the message indicates the specific entity name.
reason for the failure.
Explanation: The requested function is not
System action: Processing stops. implemented in DiskMapper at this time. Please report
this error to your Tivoli Storage Manager administrator.
User response: Use your operating system's tools to

Chapter 6. FMV messages 435

FMV3413I • FMV4000E

System action: Processing stops. System action: Processing can continue if the
information being obtained is not critical for the
User response: Contact your Tivoli Storage Manager
operation or if it is expected behaviour in the context of
administrator.
the operation being performed.
User response: Check the error log for any other
FMV3413I DiskMapper object 'name' type 'name' is
messages that might indicate a reason for the failure.
not valid.
Try to correct any indicated problems, then try the
Explanation: The named object is not valid on the operation again. If the problem persists, contact IBM
originating client system. technical support for further assistance.

System action: Processing stops.

FMV3418W Memory allocation request for image
User response: Retry the operation. If the problem backup operation was refused by the
persists, review the client error log for other messages operating system.
that might be related to this problem. Contact your
Tivoli Storage Manager administrator for additional Explanation: Tivoli Storage Manager requires access to
help. memory in order to store information about used
blocks of a file system. In this case, more memory was
requested than the operating system would allocate.
FMV3414I Disk 'name' is not part of any container
defined on the system. System action: If imagegapsize is too small for a
dedicated filesystem and Tivoli Storage Manager faces
Explanation: None. out-of-memory condition then Tivoli Storage Manager
System action: None. This is informational message. automatically switches to full volume backup.
Operation continues with imagegapsize = 0.
User response: None.
User response: Some recommendations to avoid the
out-of-memory condition:
FMV3415W At least one of the disk containing data
v check to see if the memory resource limit is too low
for 'name' has bad blocks.
by entering the following command: ulimit -a
Explanation: One or more physical disks containing Then you can ask the UNIX system root user to
data blocks of the above object has bad blocks and the increase memory limit.
requested operation can not continue. v increase the value of the imagegapsize option. The
System action: The system may find a work-around to bigger imagegapsize is used, the less memory is
complete the requested operation, pleasecheck console needed for image backup, but more unused data is
log and error log for additional information on sent to server. And vice versa: the smaller
corrective actions taken or suggested user action. imagegapsize is used, the more memory is needed
for backup, but less unused data is sent to server.
User response: Depending on the operation Tivoli The outcome also depends much on how data is
Storage Manager may suggest an alternate way to spread on the volume.
complete the operation. Check your error log, sched
log, or console log for additional information.
FMV4000E Error processing 'filespace-name': file
space does not exist.
FMV3416E The volume 'name' is currently in use by
other process. Explanation: The specified file space (domain) is
incorrect or does not exist on the workstation. If the
Explanation: The operation requires exclusive access message results from the BACKUP IMAGE command
to the volume. The most likely cause of this failure is with the -MODE=INCREMENTAL option, it means that
that other process on the system has the volume you have entered the name of a raw logical volume.
opened. The MODE=INCREMENTAL option is not valid for
System action: Processing stopped. raw logical volumes.

User response: Check applications running on your System action: Processing stops.
system to ensure that volume is not opened by any if User response: Try the operation again, specifying an
the process and then retry the operation. existing domain (drive letter or file system name). If
the message resulted from improper use of the
FMV3417W name: A system call func failed with code MODE=INCREMENTAL option, try the command
rc - strerror again, omitting that option.

Explanation: An error occurred while obtaining

information from the operating system. The volume
information could not be obtained.

436 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4001E • FMV4008E

the file write locked, or restore the file to another name

FMV4001E The file space for domain 'filespace-name'
or location.
could not be found on the Tivoli
Storage Manager server.
FMV4005E Error processing 'filespace
Explanation: The specified file space was expected to
namepath-namefile-name': file not found
be found on the server, but it no longer exists. It is
possible that a command was issued to delete the file Explanation: The file being processed for backup,
space from the server while the current operation was archive or migrate no longer exists on the client.
in progress. Another process deletes the file before it can be backed
up, archived or migrated by Tivoli Storage Manager.
System action: Tivoli Storage Manager processing
stops. System action: File skipped.
User response: Try the operation again. If the problem User response: None.
recurs, check the error log for any other messages that
might indicate a reason for the failure. Try to correct
any indicated problems, then try the operation again. If FMV4006E Error processing 'filespace
the problem persists, contact IBM technical support for namepath-namefile-name': directory path
further assistance. not found
Explanation: The operating system returned a "path
FMV4002E Error processing 'filespace-name': volume not found" status when IBM Tivoli Storage Manager
label does not exist attempted to access the directory. You either have
specified a directory that does not exist, as shown in
Explanation: The selected drive does not have a label. the message (path-name), or the directory being
processed no longer exists on the client because another
System action: Tivoli Storage Manager is unable to do
process deleted it before it could be backed up or
the requested operation without a drive or label
archived by IBM Tivoli Storage Manager.
entered.
System action: The directory is skipped, processing
User response: If the drive is a floppy drive, place a
continues
disk with a volume label in it and retry the operation.
If the disk is a hard drive, ensure the drive has a User response: Recheck all spelling and punctuation,
volume label, and retry the operation. particularly the placement of directory delimiters (for
example, "\"). Correct the syntax if it is incorrect, then
retry the operation. Ensure that the path is specified
FMV4003E Error processing 'filespace-name':
correctly and that the directory actually exists. Retry
duplicate volume label encountered
the command with the corrected path and directory
Explanation: The selected drive has a duplicate name. If you cannot correct the directory name, use the
volume label. Because Tivoli Storage Manager uses the Exclude option to exclude the directory from the
volume label to keep track of backup/archive operation.
information, it cannot back up or archive files from a
drive with a duplicate volume label.
FMV4007E Error processing 'filespace
System action: Tivoli Storage Manager cannot select namepath-namefile-name': access to the
the drive. object is denied
User response: If the volume needs to be available to Explanation: Access to the specified file or directory is
the system, exit Tivoli Storage Manager, and assign a denied. You tried to read from or write to a file and
volume label to the drive. Restart Tivoli Storage you do not have access permission for either the file or
Manager and retry the operation. the directory.
System action: Processing stopped.
FMV4004E Error processing 'filespace
User response: Ensure that you specified the correct
namepath-namefile-name': destination file
file or directory name, correct the permissions, or
or directory is write locked
specify a new location.
Explanation: The file or directory being restored or
retrieved from the server cannot be written to because
FMV4008E Error processing 'filespace
the destination is write locked. Another operation
namepath-namefile-name': file is
might have the file open and will not allow it to be
temporarily unavailable
updated.
Explanation: File is temporarily unavailable.
System action: File skipped.
System action: File skipped.
User response: Either determine which operation has

Chapter 6. FMV messages 437

FMV4009E • FMV4016E

User response: Check and see if file is locked by other

FMV4013E Error processing 'filespace
process. If not, retry the command.
namepath-namefile-name': invalid file
handle
FMV4009E Error processing 'filespace
Explanation: An internal system error occurred. A file
namepath-namefile-name': disk full
operation failed because an invalid file handle was
condition
passed.
Explanation: No more files can be restored or
System action: Processing stopped.
retrieved because the destination disk is full.
User response: Report the problem to your system
System action: The client prompts you for action:
administrator, and then retry the operation.
v Retry this object
v Skip this object
FMV4014E Error processing 'filespace
v Abort the action namepath-namefile-name': unknown system
User response: Select the appropriate action for this error (error-code) encountered. Program
object. Create some free space on the destination disk ending.
before you retry the operation. Another option is to Explanation: An unrecognized and unexpected
restore or retrieve the file to another disk. error-code occurred within the client program. This is a
programming failure and the client program ends.
FMV4010E Error processing 'filespace System action: processing stops.
namepath-namefile-name': stale NFS handle
User response: Try the operation again. If the problem
Explanation: An NFS file system becomes stale. continues, report the error to your Tivoli Storage
System action: File system skipped. Manager administrator.

User response: Check the NFS mounted filesystem.

FMV4015E Error processing 'filespace
namepath-namefile-name': unexpected
FMV4011E Error processing 'filespace Tivoli Storage Manager error (error-code)
namepath-namefile-name': no file handles encountered
available
Explanation: An unexpected error occurred. This
Explanation: All file handles for your system are might be a low-level system or communication error
currently in use. No more are available. that Tivoli Storage Manager cannot handle or recover
from.
System action: Processing stopped.
System action: processing stops.
User response: Either free some file handles by ending
other processes, or modify your system setup to allow User response: Try the operation again. If the problem
for more files to be open at the same time. continues, look for other indications of system
problems to determine where the problem exists. Most
systems have error or event logs which may contain
FMV4012E 'filespace namepath-namefile-name' already
additional information. See your system administrator
exists. It will be skipped.
or Tivoli Storage Manager administrator for further
Explanation: The client tried to restore or retrieve the help.
specified file, but the file already existed in the target
restore location and the user chose not to replace the
FMV4016E Error processing 'filespace
existing file.
namepath-namefile-name': file is being
System action: The file is skipped, a message is executed; write permission denied
logged in dsmerror.log, and restore or retrieve
Explanation: The current file cannot be opened to
processing continues with the next object.
write to because it is currently being run by another
User response: The file was skipped because either operation.
REPLACE NO was in effect, causing all existing files
System action: File skipped.
and directories to be skipped, or REPLACE PROMPT
was in effect, and when prompted, the user chose to User response: Stop the operation that is running the
skip this file or all existing directories and files. No file and retry the operation, or restore or retrieve the
additional action is necessary if the decision to skip the file to a different name or directory.
file was deliberate. Otherwise the operation can be
retried using either REPLACE ALL REPLACE
PROMPT.

438 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4017E • FMV4025E

Manager client software. If the problem persists, contact

FMV4017E Error processing 'filespace
IBM technical support for further assistance.
namepath-namefile-name': too many
symbolic links were detected while
resolving name FMV4021E Error processing 'filespace
namepath-namefile-name': file system not
Explanation: While trying to resolve the file name, too
ready
many symbolic links were found.
Explanation: The file system/drive was not ready for
System action: File skipped.
access.
User response: Ensure that you do not have a looping
System action: Processing stopped.
symbolic link for the file.
User response: Ensure that the drive is available to
Tivoli Storage Manager, and then retry the operation.
FMV4018E Error processing 'filespace
namepath-namefile-name': file name too
long FMV4022E Error processing 'filespace
namepath-namefile-name': file system is
Explanation: The file name specified is too long to be
invalid.
handled by Tivoli Storage Manager.
Explanation: The drive was not available for access.
System action: File is skipped.
System action: processing stops.
User response: See the appropriate Using the
Backup-Archive Client book for the particular operating User response: Ensure that the drive is operational,
system, for the file names that are handled by Tivoli and then try the operation again. If this is unsuccessful,
Storage Manager. check the error log.

FMV4019E Error processing 'filespace FMV4023E Error processing 'filespace

namepath-namefile-name': file system is namepath-namefile-name': file input/output
locked by system error
Explanation: File system cannot be accessed because it Explanation: An error was found while reading from
is locked by the system. or writing to the file.
System action: Tivoli Storage Manager cannot System action: File skipped.
complete the operation.
User response: Check your system to ensure that it is
User response: See your system administrator. operating properly. For OS/2, run CHKDSK /F for the
failing drive which can be found in dsmerror.log.
FMV4020E The data format for object 'filespace
namepath-namefile-name' is unknown. The FMV4024E Error processing 'filespace
unknown format usually occurs when namepath-namefile-name': file write error
the file was backed up or archived by a
later version of IBM Tivoli Storage Explanation: An error was found while writing to the
Manager. file.

Explanation: When a file is backed up or archived, System action: File skipped.

IBM Tivoli Storage Manager includes some additional User response: Check your system to ensure that it is
information about the file. This message is issued if operating properly.
IBM Tivoli Storage Manager cannot recognize the
information during a restore or retrieve operation. The
most likely cause is that the file was backed up or FMV4025E Error processing 'filespace
archived with a newer version of IBM Tivoli Storage namepath-namefile-name': file exceeds user
Manager. If the file was backed up from a or system file limit
case-preserving but not case-sensitive file system, the Explanation: A file being backed up/restored or
file name might be displayed with incorrect casing. The archived/retrieved exceeds system set limits for this
incorrect casing does not otherwise affect processing user. Shown below are the filesize limits corresponding
since the file is skipped. to various platforms.
System action: The file is not restored or retrieved. AIX 68,589,453,312 (64GB)
Processing continues with the next file.
HP-UX 1,099,511,627,775 (1TB-1)
User response: Try the restore or retrieve operation
again with a current version of the IBM Tivoli Storage Linux 2,147,483,647 (2GB)

Chapter 6. FMV messages 439

FMV4026W • FMV4031E

Mac pre-OS9
FMV4028E Error processing 'filespace
2,147,482,624 (2GB-1K)
namepath-namefile-name': cannot create
Mac OS9 file/directory entry
18,446,744,073,709,551,616 (16EB)
Explanation: The directory path for files being
NetWare restored or retrieved cannot be created.
4,294,963,200 (4GB -4KB)
System action: File skipped.
IBM NUMA-Q® DYNIX/ptx®
User response: Ensure that you have the proper
4.5 1,095,216,660,480 (1TB-4GB)
authorization to create the directory for file being
IBM OS/390® restored or retrieved.
4,294,967,295 (4GB)
SGI 18,446,744,073,709,551,615 (16EB-1) FMV4029E Error processing 'filespace
namepath-namefile-name': unable to build
Solaris 2.6 or higher a directory path; a file exists with the
1,099,511,627,775 (1TB-1) same name as a directory
Tru64 UNIX Explanation: Tivoli Storage Manager tried to create a
1,099,511,627,776 (1TB) directory path, but is unable to because a file exists that
UnixWare has the same name as a directory.
2,147,483,647 (2GB) System action: Processing stopped.
Windows ME (FAT32) User response: Remove the file that has the same
4,294,967,295 (4GB) name as the directory. Refer to the last restore/retrieve
Windows NT/2000 (NTFS) operation and check all directories along the path.
17,592,185,978,880 (16TB-64K)
System action: File skipped. FMV4030E Error processing 'filespace
namepath-namefile-name': disk space limit
User response: Ensure that the system limits are set for this process reached
properly.
Explanation: The disk space allocated for the client
owner is full.
FMV4026W Error processing 'filespace
namepath-namefile-name': size of 'file-size' System action: Processing stopped.
exceeded the maximum file size limit on User response: Free up disk space and retry the
your system restore or retrieve operation.
Explanation: You tried to restore or retrieve a file that
has exceeded the maximum file size limitation on your FMV4031E Error processing
system. 'file_space_namepath_namefile_name'. Name
System action: Tivoli Storage Manager cannot restore exceeds an internal Tivoli Storage
or retrieve the file. Manager limit.

User response: Restore or retrieve this file on a system Explanation: During a file operation, Tivoli Storage
that supports the file size. See your system Manager encountered a filename where at least one
administrator. component of the file name (file_space_name,
path_name or directory_name or file_name) exceeded
an internal Tivoli Storage Manager maximum. The
FMV4027S Error processing 'filespace internal Tivoli Storage Manager limits should not be
namepath-namefile-name': internal program confused with the operating system limits for
message 'value' encountered file_space_name, path_name or directory_name,
Explanation: An unexpected catastrophic program file_name.
failure occurred, indicated by value. Shown below are the Tivoli Storage Manager internal
System action: Processing stopped. file name limits for various platforms.
AIX HP-UX Solaris
User response: Retry the operation. If the problem File_space_name 1024
continues, see your system administrator or service Path_name or directory_name 1023
representative. File_name 256

Linux
File_space_name 1024

440 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4032E • FMV4039E

Path_name or directory_name 768 System action: Tivoli Storage Manager Cannot restore
File_name 256 or retrieve the file.

Windows XP/2000/2003 User response: Try to restore or retrieve after the file
File_space_name 1024 was made available on the server. See your system
Path_name or directory_name 248 administrator.
File_name 248
System action: The file is skipped. FMV4036E An error occurred saving the registry
key.
User response: Reduce the size of the filename so that
it is smaller that the Tivoli Storage Manager internal Explanation: The active registry key cannot be copied
limits. to the ADSM.SYS staging directory.
System action: Registry backup operation terminates.
FMV4032E Error processing 'filespace
namepath-namefile-name': file is not User response: Check the space available on the
compressed. Windows boot partition to ensure there enough space
to contain a copy of the Windows registry. This might
Explanation: A file that was flagged as compressed require several megabytes of free space. Also check the
was not compressed, and the system failed. Windows permissions on the ADSM.SYS staging
directory and ensure that the Windows user under
System action: Processing stopped.
which you are running Tivoli Storage Manager has full
User response: See your system administrator to access to that directory and its contents.
report this problem. This error is a system failure.
FMV4037E Object 'file-namefile-namefile-name'
FMV4033E Error processing 'filespace changed during processing. Object
namepath-namefile-name': file compressed skipped.
on a different client machine that has
Explanation: The specified file-name was skipped
more memory
during backup, archive, or migrate because it was
Explanation: You are trying to restore a file that was changing during the attempt to process it.
backed up and compressed on another client
System action: Tivoli Storage Manager skipped the
workstation that had more memory than your client
object.
workstation. You cannot restore this file. When the file
is restored, it is expanded and your workstation does User response: If you want the file backed up,
not have enough memory. archived, or migrated, retry the operation. If it fails,
determine why the object is being changed. For more
System action: Tivoli Storage Manager canceled the
information on backing up, archiving, or migrating
operation.
changing objects, see your system administrator.
User response: Obtain a machine with more memory
and retry the operation.
FMV4038E An error occurred processing file system
'filespace name'.
FMV4034E Error processing 'filespace
Explanation: File system 'filespace name' is corrupted or
namepath-namefile-name': unknown system
contains one or more corrupted directories and cannot
error
be processed.
Explanation: An unknown error occurred. This might
System action: File system is skipped.
be a low-level system or communication error that
Tivoli Storage Manager cannot handle or recover from. User response: Check your system to ensure that it is
operating properly. For the Windows environment, run
System action: Processing stopped.
CHKDSK utility for the failing drive. More information
User response: Retry the operation. If the problem about corrupted directories can be found in
continues, determine where the problem exists. See dsmerror.log.
your system administrator for further help.
FMV4039E Error processing 'filespace
FMV4035W File 'filespace namepath-namefile-name' namepath-namefile-name': compressed file
currently unavailable on server. is corrupted and cannot be expanded.
Explanation: You tried to restore or retrieve a file that Explanation: The compressed file cannot be expanded
is currently not available from the Tivoli Storage correctly due to one of the following reasons:
Manager server. v There is a problem on the tape.

Chapter 6. FMV messages 441

FMV4040E • FMV4047E

v There is a communications problem. User response: Check the disk for errors.
v The compressed file was corrupted on the TSM
Server. FMV4044E Error processing 'filespace-namepath-
System action: File skipped. namefile-name': Case-sensitive name
conflict exists.
User response: 1) The compressed file is corrupted
because there is a problem on the tape. To know if this Explanation: While processing the specified file on the
is the problem, please issue the following command on workstation, another file name was encountered with a
the TSM Server: audit volume <volume_name> fix=no similar name which only differed in case. The
If there is any problem reported, you could move the Backup-Archive client does not allow names which
data from that volume to a new one (see command differ only in case on this platform and cannot
MOVE DATA) and try again the restore. 2) There are guarantee the integrity of the file, so the file is skipped.
communications problems between the TSM Server and System action: This object will be skipped.
the TSM Client and the results is that the file is
corrupted during the transmission. If you use a gigabit User response: Rename the file in question to a
ethernet adapter on the Server please upgrade the card unique name.
driver (AIX platform) or add provided by SUN
suggested changes to some system network options FMV4045E Error processing 'filespace-namepath-
which have resolved this problem (SUN platform). 3) namefile-name': Case-sensitive name
Please verify with your network support if during the conflict exists. The directory tree will be
restore there are no any problems between the TSM skipped.
Client/Server that is originating the file corruption.
Explanation: While processing the specified file on the
workstation, another object name was encountered with
FMV4040E Error processing 'filespace a similar name which only differed in case. The
namepath-namefile-name': file system Backup-Archive client does not allow names which
filespace name has exceeded its space differ only in case on this platform and cannot
management quota. guarantee the integrity of the file, so the directory and
Explanation: Tivoli Storage Manager detects that the all of the objects contained within it are skipped.
file system has exceeded its quota. No more data can System action: This object will be skipped.
be migrated out of this file system.
User response: Rename the file in question to a
System action: Tivoli Storage Manager will not unique name.
migrate files from this file system.
User response: Recall some files, or ask the system FMV4046E There is an error processing
administrator to increase the quota for this file system. 'filespace-namepath-namefile-name': the
object is corrupted and unreadable.
FMV4041W Error processing 'filespace Explanation: You tried to read from or write to a file
namepath-namefile-name': Out of free space or directory that is corrupted. The corrupted file is
or inodes in file system to migrate or skipped. If this is a directory, the objects contained in
recall. the directory and its subdirectories are skipped.
Explanation: The file system is full. No more free System action: This object will be skipped.
space or free inodes are available to be allocated for the
transaction file that is needed when a file is being User response: Check your system to ensure that the
migrated or recalled. filespace is not corrupted by using system tools like
chkdsk (Windows) or fsck (UNIX).
System action: Tivoli Storage Manager terminates the
current operation for this file system.
FMV4047E There is a read error on
User response: Remove some files in the file system, 'file-namefile-namefile-name'. The file is
and then run reconciliation. Retry the operation. skipped.
Explanation: The specified file-name was skipped
FMV4042E Object name 'filespace during backup archive because the file could not be
namepath-namefile-name' contains one or read.
more unrecognized characters and is not
valid. If you are performing a JFS2 snapshot based operation,
it is possible that the snapshot was not large enough to
Explanation: The file name, directory name, or contain all the changes made to the filesystem after the
volume label syntax is incorrect. snapshot was created. This could cause the snapshot to
System action: The file is skipped. become invalid thereby preventing Tivoli Storage

442 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4048W • FMV4053E

Manager client from reading the snapshot.

FMV4051E Error processing 'filespace
System action: Tivoli Storage Manager skipped the namepath-namefile-name': The decryption
file. option is in effect, but the user ID
under which back-up or archive is being
User response: Check your system to ensure that it is run is not authorized to decrypt this
operating properly. encrypted-file-system (EFS) file.
If you are performing a JFS2 snapshot based operation, Explanation: The file being processed is encrypted by
please use the default snapshotcachesize of 100% and an encrypted file system (EFS). The option is specified
ensure that the volume group has sufficient disk space to back-up or archive the file in decrypted form. The
to allocate snapshots at least as large as the file system user ID under which the back-up or archive is being
and retry the operation. run does not have decryption rights for this file.
System action: The file is skipped.
FMV4048W LAN-Free connection failed.
User response: There are three possible ways to make
Explanation: ENABLELANFREE option is set to YES decryption work:
for this session, but an attempt to establish LAN-Free
connection failed. v Re-encrypt the file under the encryption key of a
group to which both the owner and the
System action: The Tivoli Storage Manager client will back-up/archive user IDs belong
failover to non LAN-Free support. v Add the back-up/archive user ID to the list of users
User response: Review the Tivoli Storage Manager authorized to decrypt this file
error.log for LAN-Free failures. Check your LAN-Free v Run the back-up or archive under the owner's user
setup and verify that all components are working ID, if possible
properly.

FMV4052E Error processing 'filespace

FMV4049I Established LAN-Free connection. namepath-namefile-name':
Encrypted-file-system (EFS) file cannot
Explanation: ENABLELANFREE option is set to YES
be restored, because file system does
for this session and the Tivoli Storage Manager client
not support restore from the raw-EFS
successfully established LAN-Free connection with
back-up data, or possibly because the
server, after the LAN-Free connection was broken.
restore function does not have write
System action: The Tivoli Storage Manager client will access to the directory.
communicate with the server via LAN-Free.
Explanation: The file being processed is encrypted by
User response: Review the Tivoli Storage Manager an encrypted file system (EFS). The file was backed up
error.log for LAN-Free errors. Check your LAN-Free in the raw encrypted format. Either the target
setup and verify that all components are working filesystem does not support the encrypted format, or
properly. restore does not have write access to the directory to
which the file is to be restored.
FMV4050W Scheduled action 'schedule-action' did not System action: The restore is terminated.
execute for schedule 'schedule-name' as
User response:
the Tivoli Storage Manager
administrator has been disabled from v The file cannot be restored to this location if the file
executing the scheduled action on the system is not the AIX Enhanced Journaled File
client. System (JFS2)
v If the file is JFS2 but EFS is not enabled, then EFS
Explanation: One or more of the client options -
must be enabled before the file can be restored
schedcmddisabled, srvprepostscheddisabled,
srvprepostsnapdisabled, restretrscheddisabled, have v If the user ID under which restore is being run does
been set to YES on the client thereby preventing the not have write permission for the directory, the
Tivoli Storage Manager administrator from executing permissions must be changed or the restore must be
one of the following scheduled actions on the client - run under a different user ID
preschedule, postschedule, presnapshot, postsnapshot
or scheduled operating system commands, restore or FMV4053E Error processing 'filespace path filename':
retrieve operations. The file cannot be restored because the
System action: The scheduled operation will not be file system or operating system does not
executed and a message will be logged to Tivoli support the Encrypting File System
Storage Manager Server indicating this. (EFS) data.

User response: None required. Explanation: The specified object was backed-up as

Chapter 6. FMV messages 443

FMV4054E • FMV4058I

raw Encrypting File System (EFS) data. The client is backup or archive operation and then a subsequent
trying to restore or retrieve the object to a destination backup or archive operation is attempted with a client
that does not support the EFS data. The location might V5.5 or lower.
not support the EFS data for one of the following
System action: Processing stops.
reasons:
v The operating system does not provide the support, User response: Use the correct level of the client.
or is a release that does not include the support
v EFS support has not been activated on the operating FMV4056E Object 'object-name' returned by the IBM
system Tivoli Storage Manager server has a
v The target file system does not support the EFS data high-level name that exceeds the
maximum length of 6000 characters. The
System action: The object is not restored or retrieved. file or directory cannot be processed.
Processing continues with the next object.
Explanation: The IBM Tivoli Storage Manager server
User response: If this file must be restored, restore it returned information about a backup or archive version
to an AIX operating system environment supporting with a high level name that exceeds 6000 characters.
EFS data. The high-level name is the directory path that contains
the object (file or directory).
FMV4054E Error processing 'filespace This message is displayed when all of the following
namepath-namefile-name': The encryption conditions are true:
key is not loaded.
v The object was backed up or archived by a version
Explanation: The file being processed is encrypted by 6.1 or lower IBM Tivoli Storage Manager client.
an encrypted file system (EFS). The option is specified v The object was backed up or archived to a version
to backup or archive the file in decrypted form. The 5.5 or lower IBM Tivoli Storage Manager server.
encryption key, required to decrypt the file, is not
v IBM Tivoli Storage Manager client version 6.2 or
loaded in the kernel keyring.
higher is attempting to perform an operation that
System action: The file is skipped. causes the IBM Tivoli Storage Manager server to
return information about this object to the client.
User response: There are three situations in which this
Note: During incremental backup, the server returns
problem can occur:
information to the client about active backup
v You just performed initial activation of EFS on the versions which is used to determine which files have
AIX system, and have not logged out. AIX does load changed.
the keys for the session running at the time of initial
activation. Solution: Logout and login again. Beginning with IBM Tivoli Storage Manager server
v The login password has been changed recently, and version 6.1, the maximum high level name length was
you normally run with the EFS password the same reduced from 8192 characters to 6000 characters.
as the login password. AIX does not automatically Objects with high level names that exceed 6000
change the EFS password when you change the login characters are not supported for backup or archive.
password. Solution: Issue 'efskeymgr -n' to set the Beginning with IBM Tivoli Storage Manager
EFS password to be the same as the login password. backup-archive client version 6.2, the maximum high
v You need to run the decrypting backup when the level name length was similarly reduced.
EFS password is different from the login password. System action: The file or directory specified in the
Solution: Issue 'efskeymgr -o ksh' to launch a new message is skipped. Processing will continue with the
shell with the keys loaded. AIX will prompt you for next object.
the EFS password as you launch the shell. Run the
backup from the new shell. User response: Contact your IBM Tivoli Storage
Manager server administrator for further assistance.

FMV4055E Cannot update file space 'filespace-name':

the file space version on the Tivoli FMV4058I A write failure occurred while
Storage Manager server is not attempting to save node replication
compatible with this client failover values to the options file.

Explanation: The file space on the Tivoli Storage Explanation: A write failure is often a result of
Manager server is not compatible with this client. This insufficient access permissions to the options file, but
is caused by performing a backup or archive operation could also be caused by the lack of available disk
with a client and then using a down-level client and space. The replication server connection information
attempting a backup or archive operation targeting the can not be saved and failover will not be possible.
same file space. This problem occurs specifically after a System action: The operation failed.
Windows or AIX client V6.1 or higher performs a

444 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4059I • FMV4081E

User response: Check the local disk for possible User response: No action is required.
causes of the write error, and check to see that
sufficient access to the options file is configured.
FMV4065E Proxy rejected: data mover node 'dm
node' has not been granted proxy
FMV4059I The option USEREPLICATIONFailover authority for target node 'target_node',
is set. The node will not attempt a fail associated with Organization vDC
over to the secondary server 'OVDC name' of Organization 'Org Name'.
Explanation: This option will prevent the node from Explanation: The operation requires that a proxy
connecting to the replication server in the event of a access for the data center node is granted to the data
failure of the primary server. mover node.
System action: The configuration set by the Tivoli System action: Operation is canceled for the specified
Storage Manager administrator will be saved to the vApp.
options file. The client will fail to connect to the
User response: Run configuration wizard or
primary server and processing stops.
configuration editor to configure proper nodes
User response: No response is required. relashionship.

FMV4061I Connected to secondary server secondary FMV4077E File 'filespace namepath-namefile-name' is

server; in fail over mode. Home server is: encrypted by Microsoft EFS and
home server; contains at least one sparse data stream.
The operating system does not support
Explanation: The node is configured for replication
restore for this file so it is not backed
and has successfully connected to the secondary server.
up or restored.
This message is to notify the server administrator that a
node has connected to the secondary server in fail over Explanation: An error in the Microsoft Windows API
mode. prevents successful restore of files that meet the
following conditions:
System action: Processing continues.
v The file is encrypted by Microsoft Encrypting File
User response: None. System (EFS) at the time it was backed up
v The file includes at least one data stream (alternate
FMV4063W IBM Tivoli Storage Manager application "named" stream or unnamed stream) that is sparse
protection did not copy the v The operating system is any edition of Microsoft XP,
SqlServerWriter.xml and/or Microsoft Windows Server 2003, or Microsoft
SQLDBINFO.XML files from VM 'VM'. Windows Server 2003 R2
Individual SQL Database restore from
this backup is not supported. Because the file cannot be restored, IBM Tivoli Storage
Manager does not back it up. The problem is
Explanation: The SqlServerWriter.xml and/or documented by Microsoft at http://
sqldbinfo.xml files were not found on the guest support.microsoft.com/kb/2525290.
machine.
System action: The file is not backed up or restored.
System action: The operation completes. However, the Processing continues with the next object or ends if
SqlServerWriter.xml or sqldbinfo.xml files were not there are no further objects.
copied.
User response: If this message is issued during a
User response: Make sure that the 'SQL Server VSS backup operation, you can do the following:
Writer' and the 'SQL Server' services are running on
v Disable EFS encryption for the file so that it can be
this guest machine. Then try the operation again.
backed up.
v If a backup copy of the file is not necessary, you can
FMV4064I Restoring vCloud Director vApp 'vapp exclude it from backup.
name' from Organization VDC 'org vdc
name' from organization 'org name' Target
vApp name is 'restored vapp name' FMV4081E Error processing 'filespace-name': file
Restore VAPP command started. Total space type is not supported.
number of vApps to process: vapps num Explanation: The specified file space type is not
to restore currently supported by Tivoli Storage Manager on this
Explanation: The restore vApp operation completed. platform.

System action: This message is for informational System action: The unsupported file system is
purposes only. skipped. Processing continues with the next file system.

Chapter 6. FMV messages 445

FMV4082I • FMV4092E

User response: Refer to the documentation for

FMV4087E An attempt to load data for the wizard
information on what file space types are supported.
failed. For more information, please see
the log file.
FMV4082I Node password has been reset to the
Explanation: An attempt to load data for the wizard
administrative id password.
failed as the remote agent is probably unavailable.
Explanation: The client logged in using administrative
System action: Processing stopped.
id rather than node name. The node password has been
reset to be in sync with the administrative password. User response: Check the log for reason for the
failure.
System action: Processing continues.
User response: None.
FMV4089W File server file-server-name has been
upgraded to Data ONTAP version
FMV4083I New node password has been 'version.modifcation.submodification'.
generated. Perform a full incremental backup by
specifying option
Explanation: The client logged in using administrative createnewbase=migrate as soon as
id rather than node name. New random node password possible.
has been generated and recorded.
Explanation: The file server has been upgraded to a
System action: Processing continues. version that supports unicode file names for
User response: None. incremental backup using snapshot difference. Perform
a full incremental in order to backup any files with
unicode names that may have been skipped by the
FMV4084E Error processing 'filespace-namepath- previous version of the IBM Tivoli Storage Manager
namefile-name': cannot get file status. client.
Explanation: While processing the file, the lstat() call System action: Processing continues.
set EOVERFLOW error code.
User response: Perform a full incremental by
System action: This file will be skipped. specifying the command line option
User response: The file is skipped. Processing createnewbase=migrate with the snapdiff option as
continues with the next file. soon as possible.

FMV4085I Assigned 'number' objects from previous FMV4090I File server file-server-name has been
systemstate backup to the new upgraded to Data ONTAP version
systemstate backup. 'version.modifcation.submodification'.
Perform a full incremental backup by
Explanation: Objects in the previous System State specifying option
backup have not changed and were assigned to the createnewbase=migrate as soon as
new System State backup. possible.
System action: Processing continues. Explanation: The file server has been upgraded to a
User response: None. version that supports unicode file names for
incremental backup using snapshot difference. Perform
a full incremental in order to backup any files with
FMV4086W Failed to assign unchanged objects from unicode names that may have been skipped by the
previous systemstate backup to the new previous version of the IBM Tivoli Storage Manager
systemstate backup. Objects will be client.
backed up.
System action: Processing continues.
Explanation: Objects in the previous System State
backup have not changed and should be assigned to User response: Perform a full incremental backup by
the new systemstate backup. Due to error assign specifying the command line option
operation failed and objects will be backed up. createnewbase=migrate with the snapdiff option as
soon as possible.
System action: Processing continues.
User response: Retry the operation. If the problem FMV4092E Data mover platform is not supported
persists, contact Tivoli Storage Manager technical for instant access/restore operations.
support.
Explanation: The instant access/restore operation
failed.

446 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4099E • FMV4154E

System action: The instant access/restore operation finished with failures. The next virtual machine in the
failed. The reason for the failure is unsupported vmlist will be processed. The reason for the failure is
platform. written to the local client error log.
User response: The instant access/restore operation User response: Check the local client error log for
should be performed from a supported data mover reason for the failure.
platform.
FMV4151E Failure mounting Virtual Machine
FMV4099E The system volume cannot be 'vmname'. RC=rc
identified. Therefore the system state
Explanation: The VMware failed to mount virtual
cannot be backed up.
machine disk.
Explanation: The system volume contains the
System action: The backup of the virtual machine can
hardware-specific system state files that are needed to
not continue. The next virtual machine in the vmlist
start Windows, such as Ntldr, Boot.ini, Ntdetect.com or
will be processed. Refer to dsmerror.log for detailed
Bootmgr. If the system volume cannot be identified,
error message for the reason for the failure.
then these files cannot be backed up. Therefore it is not
possible to back up the system state. User response: Refer to dsmerror.log for detailed error
message.
System action: Systemstate backup stops.
User response: Try the operation again. If the problem
FMV4152E Failure initializing VMware virtual
persists, obtain a service trace that captures the
machine environment. RC=rc. Refer to
problem and contact IBM technical support for
IBM Tivoli Storage Manager error log
additional assistance. Your Tivoli Storage Manager
for detailed error messages.
administrator can help you configure the trace.
Explanation: Failure initializing VMware virtual
machine environment. Refer to IBM Tivoli Storage
FMV4137E Error processing 'filespace
Manager error log for detailed error messages.
namepath-namefile-name': exceeded
maximum number of links allowed System action: The backup can not continue.
Explanation: Link cannot be restored or retrieved User response: Refer to IBM Tivoli Storage Manager
because the destination file system has exceeded error log for detailed messages.
maximum number of links allowed.
System action: The client prompts you for action: FMV4153E Hostname could not be found for
v Skip this object Virtual Machine 'vmname'
v Abort the action Explanation: The backup of virtual machine failed.
User response: Select the appropriate action for this System action: The backup of the virtual machine
object. Restore or retrieve the link to another file finished with failures. The next virtual machine in the
system. vmlist will be processed. The reason for the failure is
written to the local client error log.
FMV4148E Full VM backup of Virtual Machine User response: Check the local client error log for
'vmname' failed with RC rc reason for the failure.
Explanation: The Full VM backup of virtual machine
failed. FMV4154E Possible cause Virtual Machine is not
running and does not have a static IP
System action: The full backup of the virtual machine
address.
finished with failures. The next virtual machine in the
vmlist will be processed. The reason for the failure is Explanation: The backup of virtual machine failed.
written to the local client error log.
System action: The backup of the virtual machine
User response: Check the local client error log for finished with failures. The next virtual machine in the
reason for the failure. vmlist will be processed. The reason for the failure is
written to the local client error log.
FMV4150E Incremental backup of Virtual Machine User response: Check the local client error log for
'vmname' failed with RC rc reason for the failure.
Explanation: The incremental backup of virtual
machine volumes failed.
System action: The backup of the virtual machine

Chapter 6. FMV messages 447

FMV4155E • FMV4164W

FMV4155E Virtual Machine 'vmname' could not be FMV4161E Duplicate virtual machine name
found on VMware server. 'vmname' was detected in the same
backup operation. Backup of virtual
Explanation: The backup of virtual machine failed.
machine 'vmfullname' can not continue
System action: The backup of the virtual machine without a unique object name.
finished with failures. The next virtual machine in the
Explanation: The backup of virtual machine failed.
vmlist will be processed. The reason for the failure is
written to the local client error log. System action: The backup of the virtual machine
finished with failures. The next virtual machine in the
User response: Check the local client error log for
vmlist will be processed. The reason for the failure is
reason for the failure.
written to the local client error log.
User response: Choose a unique name for the virtual
FMV4156E File level VM backup of virtual machine
machine.
'vmname' not supported. File level VM
backup not support on non Windows
platform guest OS. Platform type: FMV4162E The virtual machine
'platform'. 'virtual-machine-name' has not been
previously backed up.
Explanation: The backup of virtual machine failed.
Explanation: The specified virtual machine has not
System action: The backup of the virtual machine
been previously backed up, so can not be specified for
finished with failures. The next virtual machine in the
restore.
vmlist will be processed. The reason for the failure is
written to the local client error log. System action: The specified virtual machine is
skipped, and the next virtual machine in the restore list
User response: Back up the virtual machine using the
is processed.
VMBACKUPType=FULLvm option.
User response: Verify the virtual machine name to be
restored, and re-try the operation.
FMV4159E Backup of Virtual Machine 'vmname'
failed. rc=rc.
FMV4163I Encryption is currently enabled, but the
Explanation: The backup of virtual machine failed.
virtual machine backup for
System action: The backup of the virtual machine 'virtual-machine-name' will not be
finished with failures. The next virtual machine in the encrypted.
vmlist will be processed. The reason for the failure is
Explanation: Virtual Machine files are not encrypted
written to the local client error log.
when backed up to the TSM server.
User response: Check the local client error log for
System action: The virtual machine files are not
reason for the failure.
encrypted during the backup processing.
User response: No user action is necessary.
FMV4160E Proxy Rejected: Proxy authority has not
been granted to Agent Node: 'agent_node'
for Target Node: 'target_node'. FMV4164W Compression is currently enabled, but
the virtual machine backup for
Explanation: The backup of virtual machine failed.
'virtual-machine-name' is not compressed
System action: The backup of the virtual machine because client-side deduplication is not
finished with failures. The next virtual machine in the being used.
vmlist will be processed. The reason for the failure is
Explanation: Compression can only be used with
the node has not been granted proxy authority to
virtual machine CTL and Data files when the files are
access the node named by the backup proxy node. The
stored in a storage pool that is enabled for client-side
Tivoli Storage Manager administrator must first grant
deduplication. This message is issued when the client is
proxy authority.
configured for compression and virtual machine CTL or
User response: The Tivoli Storage Manager server Data files are directed to a storage pool that is not
administrator must grant proxy authority for this node. enabled for client-side deduplication.
See the administrator command "Grant Proxynode".
System action: Backup continues, and data is not
compressed.
User response: If you intend to compress virtual
machine CTL and Data files, then update your Tivoli
Storage Manager configuration so that both types of

448 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4165E • FMV4171E

files are directed to storage pools that are enabled for Restore or Backup summary panel under the Last Error
client-side deduplication. If you intend to compress Message section.
virtual machine Data files but not CTL files, then
System action: An error occurred, and the operation
update your Tivoli Storage Manager configuration so
failed.
that the Data files are directed to a storage pool that is
enabled for client-side deduplication. Set the User response: Check the reported error and correct
VMSKIPCTLCOMPRESSION to YES in your client the problem. Usually the reason for the error is a
options file. If you do not intend to use compression, user-supplied value which is not valid for the
then set COMPRESSION NO in your client options file. operation.

FMV4165E Creating a Virtual Machine, but the FMV4169E A write failure occurred on the local
hostname 'virtual-machine-name' was not disk proxy used to temporarily store the
found. virtual machine virtual disk
information. The write failure can be
Explanation: The Virtual Machine being creating must
caused by the lack of available disk
have a valid hostname to be created.
space on the drive used to store this
System action: Check the virtual machine hostname information. The VMBACKDIR option
specified for correctness. can be used to assign a different disk
location for this purpose. Check the
User response: Correct the virtual machine hostname
drive being used and ensure that there
specified and retry the restore.
is enough space available for this
operation.
FMV4166E Creating a Virtual Machine, but the
Explanation: There was a write error from the local
datacenter 'virtual-machine-name' was not
disk used to store the virtual machine virtual disk
found. The name may be incorrect or
information. Usually the write error is due to lack of
may be located in a VMware folder and
disk space, lack of write permissions, or some similar
require the folder name such as
problem with the local disk. The VMBACKDIR option
vmfolder/dcname.
can be used to assign a different disk location if the
Explanation: The Virtual Machine being created must local drive does not have enough free space for the
have a valid datacenter to be created. operation.

System action: Processing stops. System action: A disk write error occurred, and the
operation failed.
User response: Check the virtual machine datacenter
specified for correctness. If the datacenter is contained User response: Check the local disk for possible
in a folder then the full datacenter name, complete with causes of the write error, and use the VMBACKDIR
the folder path, must be specified, such as option to assign another disk if needed.
vmfolder/dcname.
FMV4170E Can not create a Virtual Machine on
FMV4167E Creating a Virtual Machine, but the VMware release 'release-version-target'
datastore 'virtual-machine-name' was not which was backed up from VMware
found. release 'release-version-source'.

Explanation: The Virtual Machine being creating must Explanation: The Virtual Machine being created was
have a valid datastore to be created. backed up from a version of VMware which is not
compatible with the target VMware release version
System action: Check the virtual machine datastore being used for the restore.
specified for correctness.
System action: Processing stops.
User response: Correct the virtual machine datastore
specified and retry the restore. User response: Restore the Virtual Machine to a
VMware system which is compatible with the level
from which the Virtual Machine was backed up.
FMV4168E VMware has reported an error via their
SOAP interface. On the Detailed Status
Report panel, view the last error FMV4171E Backup of virtual machine 'vmname'
message reported. Also check the error failed. VM could not be contacted
log for more information about the because of 'vmfullname' connection state.
problem that occurred.
Explanation: The backup of virtual machine failed.
Explanation: The command to VMware failed to
System action: The backup of the virtual machine
complete. The error returned is displayed on the

Chapter 6. FMV messages 449

FMV4174E • FMV4191E

finished with failures. The next virtual machine in list deduplication is enabled on the server. To enable
will be processed. client-side data deduplication, use the
DEDUPLICATION parameter on the REGISTER NODE
User response: Correct the connection state from
or UPDATE NODE server command. Set the value of
VMware vCenter and assign VM to an ESX Server.
the parameter to CLIENTORSERVER. The value of the
DEDUPLICATION option on the client must be set to
FMV4174E Full VM backup of VMware Virtual YES. You can set the DEDUPLICATION option in the
Machine 'vmname' failed with RC=rc client options file, in the preference editor of the Tivoli
mode=full_or_incr, target node Storage Manager client GUI, or in the client option set
name='target_node_name', data mover on the Tivoli Storage Manager server. Use the DEFINE
node name='data_mover_node_name' CLIENTOPT command to set the DEDUPLICATION
option in a client option set. To prevent the client from
Explanation: The Full VM backup of virtual machine overriding the value in the client option set, specify
failed. FORCE=YES. Ensure that the deduplication parameter
System action: The full backup of the virtual machine for the node is "ClientOrServer": The value of the
finished with failures. The next virtual machine in the DEDUPLICATION option on the client must be set to
vmlist will be processed. The reason for the failure is YES.
written to the local client error log.
User response: Check the local client error log for FMV4179I IBM Tivoli Storage Manager application
reason for the failure. protection did not truncate the Microsoft
SQL Server logs on VM 'VM'.

FMV4177E Full VM restore of VMware Virtual Explanation: The SQL server logs were not truncated
Machine 'vmname' failed with RC=rc because the following option was specified for this
target node name='target_node_name', virtual machine: INCLUDE.VMTSMVSS vname
data mover node OPTIONS=KEEPSQLLOG
name='data_mover_node_name' System action: The operation completes.
Explanation: The Full VM restore of the virtual User response: Remove the OPTIONS=KEEPSQLLOG
machine failed. option to enable truncation of the SQL logs when a
System action: The full restore of the the virtual backup completes.
machine finished with failures. The next virtual
machine in the vmlist will be processed. The reason for FMV4187W CPU and Memory Resource Allocation
the failure is written to the local client error log. configuration settings cannot be restored
User response: Check the local client error log for when the IBM Tivoli Storage Manager
reason for the failure. data mover node is connected directly to
a Virtual Center managed ESX/ESXi
host. These settings have been skipped.
FMV4178W Compression is currently enabled, but
the virtual machine control files for Explanation: The VMware vStorage APIs do not
'virtual-machine-name' will not be support the restore of CPU and Memory Resource
compressed because client-side Allocation configuration settings when connected
deduplication is not being used for the directly to an ESX/ESXi host that is managed by a
management class default or specified Virtual Center.
by the -vmctlmc option for System action: CPU and Memory Resource Allocation
'vm-ctl-mgmt-class-name'. configuration settings are skipped. Processing
Explanation: Virtual machine control files are not continues.
compressed because data is stored in a storage pool User response: Virtual machine CPU and Memory
that is not enabled for client-side data deduplication. Resource Allocation configuration settings will be
The virtual machine control files are not compressed restored when the IBM Tivoli Storage Manager data
during the backup processing unless data is stored in a mover node connects directly to a vCenter Server.
storage pool that is enabled for client-data Modify the VMCHOST to connect the TSM data mover
deduplication. to a vCenter Server.
System action: Backup continues, and control file data
is not compressed. FMV4191E Restore VM operation failed using 'san'
User response: Ensure that the storage pool is enabled transport mode. In some cases switching
for client-side data deduplication: run "q stg <pool from SAN to network-based VM
name> f=d" and verify that the value of "Deduplicate restores can be successful.
Data?" is "yes". Ensure that client-side data Explanation: Restore VM operations that fail using

450 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4193E • FMV4200I

SAN transport mode can often be successful over a the Organization VDC node was not found in the
LAN path. If a restore vm operation fails using the Provider VDC node.
'SAN' transport mode, set the client option
System action: Back up of the specified vApp stops.
VMVSTORTRFMVPORT to "nbd:nbdssl" and try the
Processing continues to the next vApp.
restore vm operation again.
User response: Go to the Configuration page and click
System action: Restore VM operation failed using 'san'
'Run the Configuration Wizard' to verify that all
transport mode. Restore may be successful using
required Tivoli Storage Manager nodes are registered
'nbd:nbdssl' transport modes.
on the Tivoli Storage Manager server. If required,
User response: Restore VM operation failed using register a new data mover node. Make sure that the
'san' transport mode. In some cases network-based VM organization VDC belongs to the provider VDC that
restores can be successful when using 'nbd' or 'nbdssl' this data mover node protects.
transport modes. The VMVSTORTRFMVPORT option
can used to restrict the TSM client to use only the
FMV4199W File 'file name' is not backed up as part
specified transport modes.
of the system state because cluster disk
'volume name' is not accessible.
FMV4193E vApp 'vApp name' cannot be processed
Explanation: The indicated file or directory was
because data mover 'dm node' cannot
returned by VSS as part of the backup file list of the
connect to the target node 'target_node'.
writer. However, the cluster disk where the file is
Explanation: The operation requires that a proxy located is not accessible. The reasons for this problem
access for the data center node is granted to the data can be that the cluster disk is offline or belongs to
mover node. another node.
System action: Operation is canceled for the specified System action: The file is not backed up. Processing
vApp. continues.
User response: Look for errors in error log and correct User response: This problem is documented in
any problems. Run configuration wizard or Microsoft knowledge base topic 980794
configuration editor to ensure proper nodes http://support.microsoft.com/default.aspx?scid=kb;EN-
configuration. US;980794. The topic includes a hotfix. With the hotfix,
you can specify a registry key that contains a list of one
or more files to be excluded from VSS enumeration.
FMV4194E Encryption is currently enabled, but is
IBM Tivoli Storage Manager does not back up files that
not supported for incremental forever
are not enumerated by VSS. If the volume is brought
backups of virtual machines
online to the node performing the system state backup,
(-MODE=IFFULL or
then it cannot be backed up. You must remove the
-MODE=IFINCREMENTAL) .
volume from the registry key and restart the system
Explanation: Client encryption of virtual machine before you can back up the volume. If you do not want
incremental forever backups (-mode=IFFULL or to implement the hotfix for this problem, IBM Tivoli
-mode=IFINCREMENTAL) is not supported. In order Storage Manager continues to issue this message.
to avoid the unintentional storage of unencrypted data
on the server, the backup operation stops.
FMV4200I architecture, schedule-name, domain-name:
System action: The virtual machine backup stops. The Deployment Manager process was
started successfully. Deployment
User response: Remove the encryption options for this Manager Version Information: version.
operation and run it again. You can use Secure Sockets
Layer (SSL) encryption to encrypt the data over the Explanation: The Deployment Manager process was
network. If the backup data must be encrypted in started as a post schedule command. This is the first
Tivoli Storage Manager storage pools, use an message from the Deployment Manager. The
alternative backup method such as full and incremental architecture of the client, schedule name, and domain
backups (-mode=FULL and -mode=INCREMENTAL), name are identified at the beginning of the message
or in-guest backups. text.
System action: Deployment Manager continues to
FMV4195E The target node for Organization VDC process.
'OrgVDC name' in Organization 'Org
User response: None
name' was not found. As a result, vApp
'vApp name' cannot be backed up.
Explanation: Either the Tivoli Storage Manager node
for the specified organization VDC was not found on
the Tivoli Storage Manager server, or information about

Chapter 6. FMV messages 451

FMV4202E • FMV4215E

System action: Processing stops.

FMV4202E The Deployment Manager failed to
install language pack: language pack User response: For information about Microsoft
name. The Microsoft Installer error code Installer error codes go to the Microsoft Developers
was error code. Network (http://msdn.microsoft.com/en-US/) and
search for "Windows Installer Error Messages".
Explanation: The previous language pack has been
uninstalled, and the installation of the new language Check the install log on the client computer.
pack failed.
System action: Processing continues. FMV4212E The Deployment Manager failed to
restart service: service name.
User response: For more information about Windows
installer error messages, go to the Microsoft Developer Explanation: After the automatic client deployment,
Network (MSDN) technical library at the Tivoli Storage Manager client services failed to
http://msdn.microsoft.com/en-us/library and search start.
on "Windows Installer Error Messages".
System action: Processing stops.
Check the install log on the client computer.
User response: Log on to the client machine and
check the backup-archive client error log.
FMV4204E The Operating System of the client
computer: os name is not supported by
the target version: target version. FMV4213E Automatic restart of the client computer
was required because reason
Explanation: The operating system level of the client
computer is no longer supported by the target level. Explanation: The Deployment Manager determined
that the deployment requires restarting the client.
System action: Processing stops.
Automatic restart is not enabled. The Deployment
User response: Check the release documentation for Manager process cancels the deployment.
information on supported operating system levels.
The current client is not uninstalled or updated.

FMV4206E The Deployment Manager received an System action: Deployment Manager cancels the client
error while extracting from installation deployment and stops
image: image name. User response: Reschedule the client deployment.
Explanation: The installation image might be missing,
corrupted, or there might be insufficient disk space on FMV4214E The operating system platform of the
the client computer. client package 'OS platform of package' is
System action: Deployment Manager stops. incompatible with the client computer
'OS platform of client computer'.
User response: Make sure that there is sufficient disk
space on the client computer. Explanation: None

Make sure that all of the Windows self extracting client System action: Processing stops.
images on the client computer are valid. User response: Reschedule the client deployment. Use
a client package with the appropriate operating system
FMV4208E The Deployment Manager could not platform.
shut down Tivoli Storage Manager
service: service name. FMV4215E The automatic deployment path from
Explanation: None the current client code version 'source
version' to the client package version
System action: Processing continues. 'target version' is not supported.
User response: None Explanation: None
System action: Processing stops.
FMV4210E The Deployment Manager failed to
install package: client package name. The User response: Reschedule the client deployment with
Microsoft Installer error code was error an appropriate target level.
code. For more information, search for "automatic client
Explanation: The previous client package has been deployment" in the appropriate version of the product
uninstalled, and the installation of the new client information (www.ibm.com/support/
package failed. knowledgecenter/SSGSG7/).

452 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4216E • FMV4225W

automatic restart is not enabled, Deployment Manager

FMV4216E The Tivoli Storage Manager API library
stops.
version API version is at an earlier
version than the version of the client User response: Reschedule with automatic restart
package package version. (autoreboot) enabled.
Explanation: The client package for automatic
deployment is invalid. In the client package, the API FMV4221E The architecture of the package: package
version does not match the Deployment Manager architecture does not match the current
version. client: system architecture.
System action: Deployment Manager stops processing. Explanation: The setup script was unable to retrieve
the matching package from the server.
User response: Please make sure that the installation
package is valid. System action: Processing stops.
User response: Ensure that the client packages for all
FMV4217E The Deployment Manager received an architectures are available on the server.
error while setting up the client API.
The standard API function being
invoked is API setup function name. FMV4222E The Deployment Manager is unable to
read information in file: file name.
Explanation: The Deployment Manager process failed
when setting up the client API. Explanation: Deployment Manager failed to open a
file containing required system information.
System action: Processing stops.
System action: Processing stops.
User response: Check the error log on the client
computer. User response: Check the error log on the client
computer.

FMV4218E The Deployment Manager received an

error while initializing the client API. FMV4223E The Deployment Manager is missing
The standard API function being required information in file: file_name.
invoked was API init function name. Explanation: The Deployment Manager relies on the
Explanation: The Deployment Manager process failed information in this file to complete the client
when initializing the client API. deployment.

System action: Processing stops. System action: Processing stops.

User response: Check the error log on the client User response: Check the error log on the client
computer. computer.

FMV4219E The Deployment Manager received an FMV4225W The setup script is still waiting for the
error while creating a pipe for the result of querying system information.
standard output of the child process. Ensure that "PASSWORDACCESS
GENERATE" is set in the client options
Explanation: The Deployment Manager failed to file and that a connection to the server
create a pipe for the standard output of the child can be made without being prompted
process. for a password.
System action: Processing stops. Explanation: The results of querying the system
information has taken longer than expected. This could
User response: Check the error log on the client
be caused by either a slow system or becuase there is
computer.
no password saved for the node.
System action: If the password is not generated,
FMV4220E The Deployment Manager is unable to
processing stops and client deployment will not begin.
determine if Tivoli Storage Manager
If the system is slow, processing continues.
processes are still running.
User response: Ensure that "PASSWORDACCESS
Explanation: The Deployment Manager could not
GENERATE" is set in the client options file and that a
determine whether all Tivoli Storage Manager processes
connection to the server has been made without being
were shut down successfully.
prompted for a password. Ignore the warning if the
System action: If automatic restart (autoreboot) is password has been generated.
enabled, the Deployment Manager continues. If

Chapter 6. FMV messages 453

FMV4226E • FMV4234E

System action: The Deployment Manager process

FMV4226E There is at least one error in the post
continues. The client computer will be shut down and
schedule command of the client
restarted after all language packs are deployed, or
deployment schedule.
immediately if there are no language pack to install.
Explanation: The Deployment Manager encountered
User response: None
at least one error while parsing the post schedule
command of the client deployment schedule.
FMV4230I The client computer will be shut down
System action: Processing stops, and client
and restarted immediately.
deployment will not begin.
Explanation: The Deployment Manager needs to
User response: Check the release documentation for
restart the client computer to complete the client
information on the format of the post schedule
deployment. It is possible the other messages provide
command of the client deployment schedule.
details of the deployment.
System action: The Deployment Manager process
FMV4227E The Deployment Manager failed to
continues. The client computer will be shut down and
install package: client package name. The
restarted immediately after all language packs are
client computer is out of disk space. The
deployed, or immediately if there are no language pack
Microsoft Installer error code was error
to install.
code.
User response: None
Explanation: The previous client package has been
uninstalled, and the installation of the new client
package failed because the client computer is out of FMV4231E The deployment for language pack:
disk space. image name was cancelled.
System action: Processing stops. Explanation: The Deployment Manager does not
uninstall or update the current language pack. It is
User response: For information about Microsoft
possible the other messages provide details of the
Installer error codes go to the Microsoft Developers
deployment.
Network (http://msdn.microsoft.com/en-US/) and
search for "Windows Installer Error Messages". System action: Processing stops. The client computer
will be shut down and restarted immediately after all
Check the install log on the client computer.
language packs are deployed, or immediately if there
are no language pack to install.
FMV4228E The Deployment Manager failed to
User response: Check the error log on the client
install language pack: language pack
computer. Manually deploy the language pack.
name. The client computer is out of disk
space. The Microsoft Installer error code
was error code. FMV4232E Self-extracting installation image: image
name cannot be found.
Explanation: The previous language pack has been
uninstalled, and the installation of the new language Explanation: The Deployment Manager could not find
pack failed because the client computer is out of disk the required installation image.
space.
System action: Processing stops. Client deployment
System action: Processing continues. will be cancelled.
User response: For information about Microsoft User response: Check the server's activity log or the
Installer error codes go to the Microsoft Developers scheduler log on the client computer. Reshcedule the
Network (http://msdn.microsoft.com/en-US/) and client deployment.
search for "Windows Installer Error Messages".
Check the install log on the client computer. FMV4234E The deployment for language packs
failed.
FMV4229I The client computer is required to Explanation: The Deployment Manager failed to
restart to complete the new install one or more language packs. It is possible the
Backup-Archive client installation. other messages provide details of the installation.
Explanation: The deployment of the new System action: The Deployment Manager process
backup-archive client will not be complete until the continues.
client computer is restarted. The restart is scheduled to
happen immediately after all language packs are User response: Check the error log and installation on
deployed. the client computer. Identify the language packs that
failed to install and manually deploy them.

454 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4235I • FMV4243I

FMV4235I The deployment manager cannot log FMV4239E Processor Architecture information is
events to the server. missing in the client package.
Explanation: The Deployment Manager is unable to Explanation: It is possible the client deployment
log events to the server. It is possible the other package is missing or corrupted.
messages provide details of the communications.
System action: Processing stops. Client deployment
System action: The Deployment Manager process will not start.
continues. Events will be logged locally on the client
User response: Ensure that the client package is
machine only.
available and imported to the server correctly.
User response: Check network connection and the
error log on the client computer.
FMV4240E Client version information is missing in
the client package.
FMV4236E The setup script was unable to query
Explanation: It is possible the client deployment
the registry for the Tivoli Storage
package is missing or corrupted.
Manager client installation directory.
System action: Processing stops. Client deployment
Explanation: The setup script encountered an error
will not start.
while querying the Windows registry for
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\ User response: Ensure that the client package is
BackupClient]. available and imported to the server correctly.
System action: Processing stops, and client
deployment will not begin. FMV4241I Architecture of the package: package
architecture does not match the current
User response: Check the release documentation for
client: system architecture. The setup
information on supported Windows platforms and
script is attempting to retrieve the
ensure the REG.EXE command is available on the client
matching package.
computer.
Explanation: The setup script is trying to retrieve the
matching client package from the server.
FMV4237W Query system information was
completed with warnings or errors. System action: Processing continues.
ErrorLevel was error level
User response: Ensure that the client packages for all
Explanation: The setup script encountered warnings architectures are available on the server.
or errors while querying system information.
System action: Processing continues. The Deployment FMV4242E The setup script encountered a warning
Manager will check to see if required system or error while retrieving the client
information is available. Client deployment could be package for architecture. The error level
cancelled if required information is missing. is error level.
User response: Check the error log of the Explanation: It is possible the client package is not
backup-archive client for warning and error messages. available on the server.
System action: Processing stops.
FMV4238E Processor Architecture information is
missing in the system information. User response: Ensure that client packages for all
architectures are available on the server. Check the
Explanation: It is possible the setup script backup-archive client error log for more detailed error
encountered a warning or error while querying system messages.
information.
System action: Processing stops. Client deployment FMV4243I The setup script successfully retrieved
will not start. the client package for architecture.
User response: Check the error log of the Explanation: The client package that was downloaded
backup-archive client for warning and error messages. matches the processor architecture of the current client.
System action: Processing continues.
User response: None

Chapter 6. FMV messages 455

FMV4244E • FMV4252E

FMV4244E The setup script failed to install the FMV4249E The setup script was unable to query
Microsoft Visual C++ redistributable the registry for the client scheduler
package. Error Level is error level. service name.
Explanation: The Microsoft Visual C++ redistributable Explanation: The setup script encountered an error
package is required by the new client. while querying the Windows registry for
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\
System action: Processing stops.
BackupClient\Scheduler Service].
User response: Check the installation log file for
System action: Processing stops, and client
names with "vcredist*.log" file in system temp directory.
deployment will not begin.
User response: Check the release documentation for
FMV4245I The setup script successfully installed
information on supported Windows platforms and
the Microsoft Visual C++ redistributable
ensure the REG.EXE command is available on the client
package.
computer.
Explanation: The Microsoft Visual C++ redistributable
package is required by the new client.
FMV4250E There is already a deployment manager
System action: Processing continues. running on this computer.

User response: none Explanation: Only one instance of client deployment

manager can be active at a time. This client computer
might be configured with multiple node names, but the
FMV4246E The setup script failed to start the new client code only needs to be deployed to one node
Deployment Manager program. Error per computer. Each client deployment instance can take
Level is error level. a few minutes to complete.
Explanation: The setup script could not start the client System action: Processing stops.
deployment process.
User response: Ensure only one client deployment
System action: Processing stops. task is scheduled to run at a time.
User response: Check the log files on the client
computer for more details. Ensure the client package is FMV4251W writername file 'filename': not found.
not corrupted.
Explanation: The indicated VSS writer file or directory
was returned by VSS as part of the backup file list of
FMV4247I The setup script successfully started the the writer. However, the object does not exist on the
Deployment Manager program. disk. .
Explanation: The setup script invokes the Deployment System action: Processing stops if
Manager to manage the deployment process. SKIPMISSINGSYSWFILES option is set to NO.
System action: Processing continues. Processing continues if SKIPMISSINGSYSWFILES
option is set to YES.
User response: None
User response: Verify that this file can be skipped
during system state backup.
FMV4248E The client is already at the target level:
'target version'.
FMV4252E The deployment manager failed to start
Explanation: Processing stopped because the as a scheduled task.
automatic client deployment feature does not support
the installation of a client to a workstation that is Explanation: The setup script failed to start the
already at its target level. deployment manager as a scheduled task with the
Windows "at" command.
System action: Your current backup-archive client is
not affected. System action: Processing stops.

User response: Reschedule the client deployment with User response: Ensure that the Windows Task
an appropriate target level. Scheduler service is running. It is possible that the
system event log contains more details about the
For more information, search for "automatic client failure. Reschedule the client deployment.
deployment" in the appropriate version of the product
information (www.ibm.com/support/
knowledgecenter/SSGSG7/).

456 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4253E • FMV4261E

System action: Processing stops.

FMV4253E There was not enough disk space on the
client computer. Required space: package User response: Check the error log file on the client
space bytes; available space: system space workstation.
bytes.
Explanation: The deployment manager determined FMV4258E The deployment manager received the
there was insufficient free disk space for the client Windows "OpenSCManager failed" error
deployment. message.
System action: Processing stops. Explanation: The deployment manager could not
connect to the Windows service control manager to
User response: Free up required disk space and
start the client scheduler. In general, this error occurs
reschedule the client deployment.
because the user who is initiating the task does not
have sufficient authority.
FMV4254E The deployment manager detected an
System action: Processing stops.
HSM client on the workstation that it
needs to deploy the Backup-Archive User response: Ensure that the user who starts the
client to. client scheduler has administrative privileges.
Explanation: An attempt was made to deploy the
Backup-Archive client to a workstation that already has FMV4259E The client scheduler is not started as a
the HSM client installed. The Backup-Archive client root user.
cannot be deployed to a workstation that has the HSM
client. Explanation: The client scheduler requires root user
privileges to upgrade the client code.
System action: Processing stops.
System action: Processing stops.
User response: Uninstall the HSM client and
reschedule the Backup-Archive client deployment. User response: Log in as root and start the client
scheduler.

FMV4255E There is not enough memory for the

deployment manager to create the FMV4260E The installation file system is not
system information object writeable.

Explanation: The system information object could not Explanation: The deployment manager cannot write
be created because there is not enough available RAM to the installation file system.
to temporarily write the data into. System action: Processing stops.
System action: Processing stops. User response: Check the installation file system
User response: Close all unneeded applications on the permissions. It is possible that the current client node
client workstation and reschedule the deployment. runs in a virtualized environment using the client code
installed in a shared storage of the physical
environment. Reschedule the client deployment with
FMV4256E The DSMI_DIR environment variable is the client node in the physical environment.
not defined.
Explanation: The deployment manager cannot initiate FMV4261E The deployment manager cannot
a connection to the server because the DSMI_DIR upgrade the Backup-Archive Client.
environment variable is not set. This error can occur if
the deployment manager is started without using the Explanation: The Backup-Archive Client cannot be
client scheduler. upgraded because either the current location is not the
default installation location or the DSM_DIR,
System action: Processing stops. DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
environment variables are defined with a relative path
User response: Read the available documentation to
and not an absolute path.
determine how to use the client scheduler to create a
client deployment task. System action: Processing stops.
User response: Check the installation directory of the
FMV4257E The deployment manager cannot parse current Backup-Archive Client. If the Backup-Archive
information in file: file name. Client is not installed in the default location, manually
upgrade the Backup-Archive Client. If the DSM_DIR,
Explanation: The deployment manager could not
DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
parse or extract the required information from the
environment variables are defined with a relative path,
specified file.

Chapter 6. FMV messages 457

FMV4262E • FMV4270I

define them with an absolute path and try the client

FMV4266I The deployment manager failed to
deployment again.
install non-English language pack(s).
Explanation: The previous packages were uninstalled,
FMV4262E The preview of the client installation
and the installation of one or more new language packs
failed.
were not successful.
Explanation: The deployment manager did not
System action: Processing continues.
uninstall the current client. The client code is
unchanged. User response: Check the deployment trace file on the
client workstation for specific language pack
System action: Processing stops.
information.
User response: Check the deployment manager log
and trace files on the client workstation for specific
FMV4267I The deployment manager failed to
issues identified during the preview. Reschedule a
install the hardware plugin package.
deployment after any issues are resolved.
Explanation: The previous package was uninstalled.
The installation of the new hardware plugin package
FMV4263E The deployment manager failed to
failed.
uninstall the backup-archive client.
System action: Processing stops.
Explanation: The deployment manager received an
error while uninstalling the current client. User response: Check the deployment trace file on the
client workstation.
System action: Processing stops.
User response: Check the deployment manager log
FMV4268I The deployment manager failed to
and trace files on the client workstation for more
install the journal-based backup
details on the error. You might have to manually
package.
uninstall the client.
Explanation: The previous journal-based backup
package was uninstalled. The new journal based
FMV4264E The deployment manager failed to
backup package installation failed.
install the backup-archive client.
System action: Processing stops.
Explanation: The current client was uninstalled and
the deployment manager received an error while User response: Check the deployment trace file on the
installing the new client code. client workstation.
System action: Processing stops.
FMV4269W The deployment manager is stopping
User response: Check the deployment manager log
the scheduler and/or CAD processes.
and trace files on the client workstation for more
details on the error. Manully install the new client after Explanation: Before deploying the new client, the
the issue is resolved. deployment manager must stop the scheduler and
CAD processes. After the deployment, the processes
must be restarted.
FMV4265I Client deployment options are not
specified in the scheduler command or System action: Processing continues.
from client services.
User response: The client scheduler is interrupted
Explanation: The default client options file will be during the deployment.
used. The deployment manager might not report the
correct server and node information when reporting
FMV4270I The deployment manager and the new
status.
client installation packages were
System action: Processing continues. downloaded to directory: file name.
User response: Avoid initiating the client deployment Explanation: The download directory contains
directly from the command-line, instead, always start everything required to complete the new client
the client scheduler as a Windows service. deployment. Deployment log and trace files can be
found in the log/ sub-directory.
System action: Processing continues.
User response: Obtain log and trace files from the
download directory for problem determination. The
files are found within the log/ sub-directory.

458 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4271E • FMV4280E

FMV4271E The deployment package is missing one FMV4275E The deployment manager cannot restart
or more required installation image the scheduler or the CAD processes.
files.
Explanation: Before exiting, the deployment manager
Explanation: The client deployment package might could not restart the Backup-Archive Client scheduler
not have been imported correctly to the server. It is or CAD processes. The deployment manager stopped
possible that the deployment package is not retrieved the processes prior to the client upgrade.
completely to the client computer, due to a lack of disk
System action: Processing continues.
space.
User response: Log on to the Backup-Archive Client
System action: Processing stops.
workstation and check the error log file. If you have set
User response: Ensure that client packages are environment variables make sure they are not defined
available on the server and there is sufficient disk space using relative path.
on the client computer. Check the backup-archive client
error log file for more detailed error messages.
FMV4276E The deployment manager cannot obtain
information about the scheduler or the
FMV4272E The processor type of the package: CAD processes.
package processor type does not match the
Explanation: The deployment manager needs process
current client: system processor type. .
information in order to stop and restart the
Explanation: The processor type supported by the Backup-Archive Client scheduler or CAD processes.
client package that you want to deploy does not match
System action: Processing stops.
the processor type of the workstation that you are
trying to deploy the client to. It is not always possible User response: Log on to the Backup-Archive Client
for the deployment manager to connect to the server workstation and check the error log file and the
and report the error. deployment manager error log file.
System action: Processing stops.
FMV4277E The target operating system version
User response: Verify that you are using the correct
target operating system does not meet the
client package for the processor architecture of the
minimum required version minimum
computer that you want to upgrade. Then restart the
required version
deployment.
Explanation: The operating system version is earlier
than the version required by the automatic deployment
FMV4273E The deployment manager detected a
package.
journal based backup (JBB) client on the
workstation where it needs to deploy System action: The deployment is canceled.
the Backup-Archive Client.
User response: Ensure that the Tivoli Storage Manager
Explanation: An attempt was made to deploy the version being deployed is supported by the target
Backup-Archive Client to a workstation that already operating system.
has the JBB client installed. On some platforms, the
Backup-Archive Client cannot be deployed to a
workstation that has the JBB client installed. FMV4278E The deployment manager cannot obtain
information about the Logical Volume
System action: Processing stops. Snapshot Agent (LVSA).
User response: Uninstall the JBB client and reschedule Explanation: The deployment manager needs to
the Backup-Archive Client deployment. determine whether an LVSA is installed on the client
workstation.
FMV4274E The deployment manager cannot stop System action: Processing stops.
the scheduler or the CAD processes.
User response: Log on to the Backup-Archive Client
Explanation: The deployment manager tried to shut workstation and check the error log file and the
down the Backup-Archive Client scheduler or CAD deployment manager error log file.
processes but the Backup-Archive Client might be busy
with other tasks.
FMV4280E Automatic client deployment is not
System action: Processing stops. allowed on the client workstation.
User response: Reschedule the Backup-Archive Client Explanation: One or more of the running client
deployment. services include AUTODEPLOY = NO in the option
file.

Chapter 6. FMV messages 459

FMV4281E • FMV4292E

System action: Processing stops.

FMV4284E The deployment is cancelled because an
User response: Change the AUTODEPLOY option on automatic client deployment task was
the client and reschedule the client deployment. scheduled for a sparse-root, non-global
zone that shares the /usr file system
with the global zone.
FMV4281E The update manager cannot remove the
TIVsmCapi package from non-global Explanation: The automatic client deployment task
zone(s): zone name. that was attempted is not supported and will be
cancelled.
Explanation: APAR IC57433 prevents the removal of
the TIVsmCapi package on Solaris on a sparse-root, System action: Processing stops.
non-global zone if uninstalling is done from the global
User response: Install the Backup-Archive Client from
zone.
the global zone or manually upgrade the
System action: Processing stops. Backup-Archive Client.

User response: Manually uninstall the Tivoli Storage

Manager client directly from the non-global zones and FMV4285E The update restore operation to an
reschedule the deployment. existing virtual machine 'VmName'
failed. The virtual machine is not in
power off state.
FMV4282E Sparse-root non-global zone(s) were
found with Tivoli Storage Manager Explanation: The update restore operation to an
Backup-Archive Client that was existing virtual machine is not supported for a running
installed from the non-global zone: zone machine and will be aborted.
names.
System action: Restore aborted.
Explanation: One or more non-global zones are
User response: Turn off the virtual machine and
sharing the /usr file system with the global zone. The
re-run the update restore command.
Tivoli Storage Manager Backup-Archive Client is
installed in the global zone with the -G parameter and
also installed manually in the non-global zone(s). You FMV4290E Only one virtual machine can be
cannot update the Tivoli Storage Manager selected for restore.
Backup-Archive Client in the global zone because it
Explanation: Restoring multiple virtual machines is
will update the version of GSKit that is shared with the
not allowed. Only one virtual machine can be selected
sparse-root non-global zones that are not part of the
for restore.
automatic deployment.
System action: No processing occurs.
System action: Processing stops.
User response: Select only one virtual machine for
User response: Manually upgrade the Backup-Archive
restore.
Client or install it from the global zone without using
the -G parameter. This ensures that you have the same
version between the global zone and the sparse-root FMV4291E Virtual Machine could not be found on
non-global zones, and you can then deploy the client VMware server.
automatically on all such zones.
Explanation: The backup of virtual machine failed.

FMV4283E There is not enough disk space on path System action: The backup of the virtual machine
to uncompress GSKit packages. finished with failures. The next virtual machine in the
Required space: req_space bytes; vmlist will be processed. The reason for the failure is
available space: avail_space bytes. written to the local client error log.

Explanation: The deployment manager determined User response: Check the local client error log for
that there is not enough free disk space to uncompress reason for the failure.
GSKit packages.
System action: Processing stops. FMV4292E No virtual machine found.

User response: Free up the required amount of disk Explanation: No virtual machine found with name or
space and reschedule the automatic client deployment. specified in domain option.
System action: Processing stopped.
User response: Specify a correct VM name or domain
option.

460 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4293E • FMV4300I

System action: The Deployment Manager process

FMV4293E Backup of VMware vApp 'vApp name' in
completes.
Organization VDC 'Org VDC name' of
organization 'Org name' failed. User response: Check the warning messages from the
server administration center, the server activity log, or
Explanation: The vApp backup operation failed. This
error log on the client computer for more information.
error message is a summary message and does not
contain detailed information.
FMV4298E architecture, schedule-name, domain-name:
System action: The configuration information and
The client deployment was canceled.
VMs for the specified vApps are not backed up.
The previous event causing the
Processing continues to the next vApp.
cancellation is: event.
User response: Check the previous messages in the
Explanation: This message is a generic message that
dsmerror.log file for more details about this vApp .
the client deployment was canceled. The Deployment
Manager does not uninstall or update the current client.
FMV4295W architecture, schedule-name, domain-name: It is possible that the other messages provide details of
The client deployment was not the deployment. The architecture of the client, schedule
completed pending the restart of the name, and domain name are identified at the beginning
client computer. The deployment of the message text.
manager did not restart the client
System action: Processing stops.
computer automatically because the
AUTODEPLOY option was set to User response: Check the warning messages from the
NOREBOOT. server administration center, the server activity log, or
error log on the client computer for more information.
Explanation: The previous client has been uninstalled,
and the installation of the new client was not
completed pending the restart of the client computer. FMV4299E architecture, schedule-name, domain-name:
The architecture of the client, schedule name, and The client deployment failed. The
domain name are identified at the beginning of the previous event causing the failure is:
message text. event.
System action: The Deployment Manager process Explanation: This message is a generic message that
completes. the client deployment failed. It is possible that other
messages provide details of the failure. The architecture
User response: Manually restart the client computer
of the client, schedule name, and domain name are
as soon as possible.
identified at the beginning of the message text.
System action: Processing stops.
FMV4296I architecture, schedule-name, domain-name:
The client deployment was completed User response: Check the warning messages from the
successfully, and the client computer is server administration center, the server activity log, or
being restarted. error log on the client computer for more information.
Explanation: Restarting the computer is required to
complete the client deployment. The architecture of the FMV4300I architecture, schedule-name, domain-name:
client, schedule name, and domain name are identified Client deployment was completed
at the beginning of the message text. successfully.
System action: The Deployment Manager process Explanation: This is a generic message that the client
completes. The client computer will be shut down and deployment was successful. It is possible that other
restarted. messages provide details of the deployment. The
architecture of the client, schedule name, and domain
User response: None
name are identified at the beginning of the message
text.
FMV4297W architecture, schedule-name, domain-name:
System action: The Deployment Manager process
Client deployment was completed with
completes.
warnings: warnings.
User response: None
Explanation: This message is a generic warning
message. It is possible that other messages provide
details of the deployment. The architecture of the client,
schedule name, and domain name are identified at the
beginning of the message text.

Chapter 6. FMV messages 461

FMV4301I • FMV4446E

FMV4301I IBM Tivoli Storage Manager detected FMV4305W Backup of VMware vApp 'vApp name' in
Microsoft Active Directory Domain Organization VDC 'Org VDC name' of
Controller on virtual machine 'VM'. organization 'Org name' completed. Some
VMs were not backed up. mode:
Explanation: The virtual machine contains Microsoft
'Incremental Forever - full_or_incr' target
Active Directory Domain Controller.
node name: 'target_node_name' data
System action: IBM Tivoli Storage Manager saved mover node name:
additional information about this virtual machine. 'data_mover_node_name' VMs backup
status: number of VM backed up out of
User response: None number of VMs in vApp VMs backed up
successfully.
FMV4302W IBM Tivoli Storage Manager failed to Explanation: The vApp backup operation completed
detect if Microsoft Active Directory successfully. However, one or more VMs for the
Domain Controller on virtual machine specified vApp were not backed up. These VMs will
'VM'. not be created during the restore operation.
Explanation: There was an error while checking if the System action: Processing continues to the next vApp.
virtual machine contains Microsoft Active Directory
Domain Controller. User response: Check the dsmerror.log file for this
vApp for more information about this message. Resolve
System action: IBM Tivoli Storage Manager continues the problem, then try the operation again.
backing up this virtual machine.
User response: Check IBM Tivoli Storage Manager FMV4308E Full VM backup of 'hypervisor' Virtual
error log for additional information. Machine 'vmname' failed with RC=rc
mode=full_or_incr, target node
FMV4303E The vCloud Director vApp 'vapp-name' name='target_node_name', data mover
has not been previously backed up. node name='data_mover_node_name'

Explanation: The specified vCloud Director vApp has Explanation: The Full VM backup of virtual machine
not been previously backed up, so can not be specified failed.
for restore. System action: The full backup of the virtual machine
System action: The specified vCloud Director vApp is finished with failures. The next virtual machine in the
skipped, and the next vApp in the restore list is vmlist will be processed. The reason for the failure is
processed. written to the local client error log.

User response: Verify the vCloud Director vApp name User response: Check the local client error log for
to be restored, and re-try the operation. reason for the failure.

FMV4304I IBM Tivoli Storage Manager could not FMV4311E Full VM restore of 'hypervisor' Virtual
detect the TSM for VE license. Active Machine 'vmname' failed with RC=rc
Directory Domain Controller will not be target node name='target_node_name',
protected on VM 'VM'. data mover node
name='data_mover_node_name'
Explanation: The virtual machine contains Microsoft
Active Directory Domain Controller, but a TSM for VE Explanation: The Full VM restore of the virtual
license is not detected. The Domain Controller will not machine failed.
be protected. System action: The full restore of the the virtual
System action: Install TSM for VE 7.1 or later to machine finished with failures. The next virtual
protect Active Directory. machine in the vmlist will be processed. The reason for
the failure is written to the local client error log.
User response: None
User response: Check the local client error log for
reason for the failure.

FMV4446E 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'

462 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4449E • FMV4910E

Explanation: The file-level restore mount operation of User response: None required. If this is a recurrent
the virtual machine failed. condition, you may want to check for network
problems.
System action: The mount of the virtual machine
finished with failures. The reason for the failure is
written to the local client error log. FMV4901E The following object contains one or
more unmatched quotation marks and
User response: Check the local client error log for
cannot be processed: 'filespace path
reason for the failure.
filename'.
Explanation: The file name in the file list contains
FMV4449E A cleanup of the file-level restore of
unmatched quotes. If a line in the file list begins with a
hypervisor type Virtual Machine 'vmname'
single or double quotation mark this quotation mark is
failed. The data center node name is
considered to be an opening quotation mark. The
'data center node name', the mount proxy
corresponding closing quotation mark of the same type
node name is 'mount proxy node name'
must be at the end of the line. If there is no closing
Explanation: The cleanup of file-level restore mount quotation mark or the closing quotation mark has been
operation of the virtual machine failed. encountered in the middle of the line, it is an invalid
input.
System action: The cleanup of mount of the virtual
machine finished with failures. The reason for the System action: The object is skipped.
failure is written to the local client error log.
User response: Correct the specification of the object.
User response: Check the local client error log for
reason for the failure.
FMV4904E Instant access of VMware Virtual
Machine 'vmname' failed. target node
FMV4450E Mount proxy platform is not supported name='target_node_name', data mover
for file-level restore operations. node name='data_mover_node_name'

Explanation: The file-level restore operation failed. Explanation: The instant access of the virtual machine
The reason for the failure is an unsupported platform failed.
or that the IBM Tivoli Storage Manager Recovery Agent
System action: The instant access of the the virtual
is not correctly installed and configured.
machine finished with failures. The reason for the
System action: The file-level restore operation failed. failure is written to the local client error log.

User response: The file-level restore mount operation User response: Check the local client error log for
should be performed from a supported mount proxy reason for the failure.
platform with IBM Tivoli Storage Manager Recovery
Agent installed and configure correctly .
FMV4907E Instant restore of VMware Virtual
Machine 'vmname' failed. target node
FMV4451E The Windows iSCSI service is not name='target_node_name', data mover
available. node name='data_mover_node_name'

Explanation: The Windows iSCSI service is not Explanation: The instant restore of the virtual machine
available on the mount proxy machine. It is either not failed.
started or not installed or configured correctly.
System action: The instant restore of the the virtual
System action: Processing stops, the file-level restore machine finished with failures. The reason for the
mount operation fails. failure is written to the local client error log.

User response: Ensure that the iSCSI service is up and User response: Check the local client error log for
running on the mount proxy machine. reason for the failure.

FMV4900W Schedule 'schedule-name' has opened a FMV4910E Cleanup of VMware Virtual Machine
new session with the server. 'vmname' failed. target node
name='target_node_name', data mover
Explanation: A scheduled event endsbecause of a node name='data_mover_node_name'
connection failure. The scheduled event had to be
restarted outside its normal startup window to Explanation: The cleanup of the virtual machine
continue the operation. failed.

System action: The scheduled event is completed System action: The cleanup of the the virtual machine
using more than one session. finished with failures. The reason for the failure is
written to the local client error log.

Chapter 6. FMV messages 463

FMV4915I • FMV4973E

User response: Check the local client error log for Check the spelling of the disk label and correct the disk
reason for the failure. label and then retry the 'backup vm' operation.

FMV4915I Object increased in size during FMV4948E A specified virtual disk was not found
compression: filespace pathfilename on the virtual machine.
Explanation: The file increased in size during Explanation: You must specify a virtual disk label
compression. name which exists on the virtual machine.
System action: Processing contiues. System action: Processing stops.
User response: None. User response: For a backup operation, use the "dsmc
backup vm ..." command with the -preview option to
display a listing of the disk labels which exist on the
FMV4942E The file specification 'string' is invalid.
virtual machine. For a restore operation, use the "dsmc
Explanation: The operating system indicated that the query vm ..." command with the -detail option to
file specification is invalid. One possible reason is that display a listing of the disk labels which exist on the
the file specification contains unrecognized characters. virtual machine backup. Check the spelling of the disk
Another possible cause is incorrect use of quotation label and correct the disk label and then retry the
marks in the file specification. operation.

System action: Processing stopped.

FMV4972W File server file-server-name has been
User response: Enter a correct file specification as upgraded to Data ONTAP version
described in the Using the Backup-Archive Client book 'version.modifcation.submodification'. This
for the particular operating system. Ensure that the file version does not support unicode file
specification contains valid characters. Verify correct names for snapshot difference
use of quotation marks for specifications that contain incremental backup. Upgrade to a
blanks spaces. If multiple file specifications are used, version that supports unicode file names
make sure that any use of quotation marks does not as soon as possible.
cause the file specifications to be treated as a single file
specification. Explanation: The file server has been upgraded from a
version that supports unicode file names for
incremental backup using snapshot difference to a
FMV4946W Warning: virtual machine: 'vm-name' version that does not. If you have upgraded from Data
disk: 'disk-name' excluded by user, was ONTAP version 7.3.3 (or later) to 8.0, you lose the
not found. ability to back up files with unicode file names when
Explanation: The specified virtual disk does not exist performing snapshot difference incremental backup.
on the virtual machine. System action: Processing continues. However, files
System action: Processing continues. with unicode names are not backed up.

User response: Use the "dsmc backup vm ..." User response: Upgrade to a version that supports
command with the -preview option to display a listing unicode file names as soon as possible. If you have
of the disk labels which exist on the virtual machine. upgraded from Data ONTAP version 7.3.3 (or later) to
Since the disk was specified to be excluded from the 8.0, upgrade to 8.1 (or later). If it is not possible to
backup, the backup will continue. However it is upgrade at this time, you can suppress this warning
possible that a disk will included in the backup which message by renaming the file space on the IBM Tivoli
was not desired, check the spelling of the disk label, Storage Manager server and performing a snapshot
and correct the disk label if an undesired disk is now difference incremental backup.
included in the backup operation.
FMV4973E An error occurred accessing NTFS
FMV4947E Error: virtual machine: 'vm-name' disk: security information for file 'filespace
'disk-name' included by user, was not namepath-namefile-name'
found. Explanation: An access denied error occurred while
Explanation: The specified virtual disk does not exist attempting to access NTFS security info rmation.
on the virtual machine. System action: The object is skipped.
System action: Processing stops. User response: See your system administrator or
User response: Use the "dsmc backup vm ..." bypass the failing check by using SkipNTSecu rity
command with the -preview option to display a listing option.
of the disk labels which exist on the virtual machine.

464 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV4974E • FMV4997E

backup when no process has exclusive use of the

FMV4974E Error processing 'filespace
directory.
namepath-namefile-name': a required NT
privilege is not held.
FMV4991I Application Type Application Message Id
Explanation: The user account running Tivoli Storage
Application Message
Manager does not possess a required NT user right/pr
ivilege for performing the current operation. Explanation: This is a message sent by the application
you are currently running with Tivoli Storage Manager.
System action: The object is skipped.
System action: Tivoli Storage Manager logs the
User response: Your system administrator has the
application message.
authority to grant the needed privilege.
User response: Refer to the documentation for the
application that you are using.
FMV4987E Error processing 'filespace
namepath-namefile-name': the object is in
use by another process FMV4992W Application Type Application Message Id
Application Message
Explanation: The specified file is being used by
another process. You tried to read from or write to a Explanation: This is a message sent by the application
file that is currently being used by another process. you are currently running with Tivoli Storage Manager.
System action: File skipped. System action: Tivoli Storage Manager logs the
application message.
User response: Ensure that the file is not locked by
another process. If the file is not locked, retry the User response: Refer to the documentation for the
command. application that you are using.

FMV4988W File 'filespace namepath-namefile-name' is FMV4993E Application Type Application Message Id

currently unavailable on server and has Application Message
been skipped.
Explanation: This is a message sent by the application
Explanation: You tried to restore or retrieve a file that you are currently running with Tivoli Storage Manager.
is currently not available from the Tivoli Storage
Manager server. This is most likely a temporary System action: Tivoli Storage Manager logs the
condition. application message.

System action: Tivoli Storage Manager cannot restore User response: Refer to the documentation for the
or retrieve the file. application that you are using.

User response: Try to restore or retrieve the file again

after the file becomes available on the server. If the FMV4994S Application Type Application Message Id
problem persists, see your Tivoli Storage Manager Application Message
administrator for assistance. Explanation: This is a message sent by the application
you are currently running with Tivoli Storage Manager.
FMV4989E Error processing 'filespace System action: Tivoli Storage Manager logs the
namepath-namefile-name': the directory is application message.
in use by another process. All objects in
the directory and any of its User response: Refer to the documentation for the
subdirectories are skipped. application that you are using.

Explanation: The specified directory is being used by

another process. You tried to read from or write to a FMV4997E Error processing 'filespace
directory that is currently being used by another namepath-namefile-name': file system quota
process. The objects contained in the directory and its reached condition - no space left.
subdirectories are not backed up. Explanation: No more files can be restored or
System action: Processing stopped for that directory. retrieved because the quota of the destination file
If other files and directories were also specified in this system has been reached.
backup, they are processed System action: The client prompts you for action:
User response: Ensure that you specified the correct v Retry this object
directory name, correct the permissions, or specify a v Skip this object
new location.If the directory name is correct, retry the
v Abort the action

Chapter 6. FMV messages 465

FMV4998E • FMV5005E

User response: Select the appropriate action for this

FMV5002E Open registration failed
object. Create some free space or increase the quota on
the destination file system before you retry the Explanation: During the change password, update
operation. Another option is to restore or retrieve the password, or open register dialog, the open registration
file to another file system. failed.
System action: Tivoli Storage Manager did not register
FMV4998E Link information for file 'filename' could this system.
not be obtained: access to the object is
User response: Reenter the password, or see your
denied.
system administrator to register this system.
Explanation: Access to the specified file link is denied.
You tried to read information for file link and you do
FMV5003S The management class assigned to
not have access permission for this object.
directories does not exist.
System action: Processing of System State stops.
Explanation: The management class named on the
User response: Try the operation again. If the problem DIRMC option does not exist in your assigned policy
persists, contact IBM technical support for additional set on the server. The error log contains an entry
assistance. showing the invalid management class name.
System action: processing stops.
FMV4999I The following message was too long to
User response: Remove the current DIRMC option
log to the server: 'shortened message with
from the client options file, then run DSMC QUERY
message number'
MGMTCLASS -DETAIL to view information about
Explanation: The message text and inserts are too available management classes. Make sure the
large to send to the server in the available internal management class you select has a backup copy group.
buffer. If you have more than one Tivoli Storage Manager
server, make sure you are connecting to the correct
System action: The message number message is written
server. If you are unable to find a suitable management
to the local client error log, then shortened and sent to
class, contact your Tivoli Storage Manager
the server as a part of this message. The message is
administrator for further assistance.
reduced in length by substituting '...' in the middle of
the original message.
FMV5004S There is no backup copy group in the
User response: The message referred to has been
management class used for directories.
shortened, but describes the error that occurred. See the
See the error log.
documentation for that message for more information.
Explanation: The DIRMC option names a
management class that contains no backup copy group.
FMV5000W Unable to update password
System action: processing stops.
Explanation: Intended new password cannot be
registered. User response: Remove the current DIRMC option
from the client options file, then run DSMC QUERY
System action: The server did not replace the old
MGMTCLASS -DETAIL to view information about
password with the new password.
available management classes. Make sure the
User response: Update the password again. If management class you select has a backup copy group.
unsuccessful, see your system administrator. If you have more than one Tivoli Storage Manager
server, make sure you are connecting to the correct
server. If you are unable to find a suitable management
FMV5001E Open registration required. Root user class, contact your Tivoli Storage Manager
must run Tivoli Storage Manager to administrator for further assistance.
register with server
Explanation: This client must be registered with this FMV5005E Table of contents information is not
server. available for the selected images.
System action: Tivoli Storage Manager ends. Explanation: An error occurred when the server tried
User response: The root user must register the client to load a table of contents. Requested image or table of
with the server. contents may have expired or been deleted on the
server.
System action: Processing stopped.

466 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5006W • FMV5016E

User response: Start a new restore window to get

FMV5011I Backup stopped by user
current information.
Explanation: You requested to stop the backup
operation.
FMV5006W The policy set does not contain any
backup copy groups. Tivoli Storage System action: Backup stopped.
Manager is unable to continue the
User response: Continue with normal operations.
backup.
Explanation: You tried to back up the files using a
FMV5012E Server out of backup data storage space
policy set that contained no backup management
information. Explanation: The server ran out of space in its backup
data storage.
System action: Tivoli Storage Manager did not back
up the files. System action: Tivoli Storage Manager cannot
complete the requested backup operation. Any files
User response: See your Tivoli Storage Manager
displayed on the lower half of the backup activity
administrator for assistance in associating your node
panel were successfully backed up.
with a policy set containing a management class that
has a backup copy group. Then try the operation again. User response: See your system administrator.

FMV5007W The policy set does not contain any FMV5013E Not enough memory for backup
archive copy groups. Tivoli Storage operation
Manager is unable to continue the
archive. Explanation: Tivoli Storage Manager cannot allocate
memory for the specified backup operation.
Explanation: You tried to archive the files using a
policy set that contains no archive management System action: Tivoli Storage Manager cannot
information. complete the requested operation.

System action: Tivoli Storage Manager did not archive User response: Close all unneeded applications and
the files. retry the operation. Reducing the scope of queries and
the amount of data returned might also help, or see
User response: See your Tivoli Storage Manager your system administrator.
administrator for assistance in associating your node
with a policy set containing a management class that
has an archive copy group. Then try the operation FMV5014I Backup completed
again. Explanation: The backup was completed.
System action: Tivoli Storage Manager backed up the
FMV5008W Incorrect password entered files.
Explanation: You entered a password that was User response: Continue with normal operations.
incorrect.
System action: Tivoli Storage Manager cannot connect FMV5015I Restore stopped by user
to the server without the correct password.
Explanation: You requested to stop the restore
User response: Reenter the password, or ask your operation.
system administrator for the current password.
Attention: If you were restoring files with the
FMV5009W New password entries are not the same "overwrite" option specified, the file you restored last
can be damaged (partially overwritten).
Explanation: During the change password, update
password, or open registration dialog, the two entries System action: Restore stopped.
for the new password were not the same. User response: Continue with normal operations.
System action: The password was not changed on the
server. FMV5016E Not enough memory for restore
User response: Backspace over both of the new operation
passwords and reenter them, ensuring that they match. Explanation: Tivoli Storage Manager cannot allocate
memory for the requested restore operation.
System action: Tivoli Storage Manager cannot
complete the requested restore operation.

Chapter 6. FMV messages 467

FMV5017I • FMV5027W

User response: Close all unneeded applications and Attention: If you were restoring files with the
retry the operation. Reducing the scope of queries and "overwrite" option specified, the file you retrieved last
the amount of data returned can also help, or see your can be damaged (partially overwritten).
system administrator.
System action: Retrieve stopped.
User response: Continue with normal operations.
FMV5017I Restore completed
Explanation: A restore was completed.
FMV5023E Not enough memory for retrieve
System action: Tivoli Storage Manager restored the operation
files.
Explanation: Tivoli Storage Manager cannot allocate
User response: Continue with normal operations. memory for the specified retrieve operation.
System action: Tivoli Storage Manager cannot
FMV5018E Not enough memory for archive complete the requested retrieve operation.
operation
User response: Close all unneeded applications and
Explanation: Tivoli Storage Manager cannot allocate retry the operation. Reducing the scope of queries and
memory for the requested archive operation. the amount of data returned might also help, or see
your system administrator.
System action: Tivoli Storage Manager cannot
complete the archive operation.
FMV5024I Retrieve completed
User response: Close all unneeded applications and
retry the operation. Reducing the scope of queries and Explanation: A retrieve was completed.
the amount of data returned might also help, or see
System action: Tivoli Storage Manager retrieved the
your system administrator.
files.
User response: Continue with normal operations.
FMV5019I Archive stopped by user
Explanation: You requested to stop the archive
FMV5025E The node name contains invalid
operation.
characters.
System action: Archive stopped.
Explanation: The specified node name has invalid
User response: Continue with normal operations. characters.
System action: Tivoli Storage Manager canceled the
FMV5020E The Tivoli Storage Manager server is current operation.
out of archive data storage space.
User response: Retry with another node name that
Explanation: The server ran out of space in its archive has valid characters.
data storage.
System action: Tivoli Storage Manager cannot FMV5026W MatchAllChar and MatchOneChar
complete the requested archive operation. options MUST precede Include/Exclude
options
User response: Report the problem to your Tivoli
Storage Manager system administrator, who can Explanation: The MatchAllChar and MatchOneChar
allocate more resources to archive storage. options must precede any include-exclude options.
System action: The Tivoli Storage Manager client ends
FMV5021I Archive completed the current application.
Explanation: An archive was completed. User response: Move the MatchAllChar and
MarchOneChar options before any include-exclude
System action: Tivoli Storage Manager archived the
options.
files.
User response: Continue with normal operations.
FMV5027W Objects of different types cannot be
backed up at the same time.
FMV5022I Retrieve stopped by user
Explanation: Backing up objects of different types at
Explanation: You requested to stop the retrieve the same time is not allowed in certain scenarios. For
operation. example, backing up Hyper-V and VMware virtual
machines at the same time is not possible.
System action: No processing takes place.

468 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5028I • FMV5036E

User response: Select objects of the same type to System action: The object is not expired. Processing
perform backup operation. continues with the next object.
User response: Review the console output, schedule
FMV5028I Successful completion log, or error log and locate the FMV1228E message that
immediately precedes this message. FMV1228E will
Explanation: The operation successfully completed.
identify the object that could not be expired. Examine
System action: None. the conditions under which the problem occurred and
assess whether those conditions explain the occurrence
User response: None. of this message. For example, this message could
appear if multiple instances of the client were
FMV5029E This operation cannot continue due to attempting to back up the file system concurrently.
an error on the Tivoli Storage Manager Search for this message number in the IBM Tivoli
server. See your Tivoli Storage Manager Storage Manager support site (http://www.ibm.com/
server administrator for assistance. support/entry/portal/product/tivoli/
Explanation: The Tivoli Storage Manager server tivoli_storage_manager).
encountered an error condition that prevents the Tivoli
Storage Manager client operation from continuing. Your FMV5033E Server has no data for the object.
Tivoli Storage Manager server administrator can review
the Tivoli Storage Manager server activity log for more Explanation: Server tried to do a restore or retrieve on
details about the error. an object that has no data associated with it. If a
corrective action is possible, it is with the server.
System action: The processing stopped.
System action: Server ends the current operation.
User response: Contact your Tivoli Storage Manager
server administrator for assistance. The administrator User response: Ask the administrator to check the
can review the Tivoli Storage Manager server activity activity log for any messages related to this error that
log for further information about the conditions that might help identify the problem.
lead to this error.
FMV5034E You entered an incorrect password.
FMV5030E No objects on server match query
Explanation: You entered an incorrect current
Explanation: No objects on the server match the query password or you entered a new password that does not
operation being performed. fulfill the password length requirements set on the
server.
System action: The processing stopped.
System action: The processing stops.
User response: Ensure the names are properly
entered. User response: Retry the session with the correct
password. If this fails or you have forgotten your
password, ask the administrator to assign a new
FMV5031E Client aborted transaction password.
Explanation: The client system ended the operation
with the server and ended the current transaction. FMV5035E Node is in use.
System action: The processing stopped. Explanation: The node you are running on is in use
User response: Restart the session. by another operation on the server. This might be from
another client or from some activity on the server.

FMV5032W Active object not found System action: The processing stopped.

Explanation: An attempt was made to expire an User response: Retry the operation, or see your
object, but the server was unable to find an active system administrator to see what other operations are
backup version of the object. This message is preceded running for your node.
by message FMV1228E which specifies the object name.
For instance, this message could be issued if two FMV5036E Expiration date must be greater than
separate client processes are backing up the same file today's date
system at the same time. If one of the processes expires
a file, then the server will make that file inactive. If the Explanation: Archive expiration date is too low, the
second process subsequently attempts to expire that date must be greater than today's date.
same file, the server will not find an active version of
System action: The current operation is canceled.
the file, so the second process will issue this message
for that file. User response: Retry archiving the file with an

Chapter 6. FMV messages 469

FMV5037W • FMV5044E

expiration date that is higher than today's date.

FMV5041E Size estimate exceeded.
Explanation: The total amount of data for a backup or
FMV5037W The requested data is offline
archive operation exceeds the estimated size originally
Explanation: For the restore or retrieve operation, one sent to the server for allocating data storage space. This
or more of the requested files must be recalled from happens when many files are growing by large
offline storage media (generally tape). The wait time amounts while the backup or archive operation is in
depends on your site's offline storage management session.
policies.
System action: Processing stopped.
System action: CLient waits for offline storage media
User response: Retry the operation. If the problem
to become available and then continues.
continues, check what other processes are running on
User response: None. the client machine that are generating large amounts of
data. Disable those operations while the backup or
archive operation is taking place.
FMV5038E Object too large for server limits.
Explanation: The object is too large. The configuration FMV5042E File data is currently unavailable on the
of the server does not have any data storage space that Tivoli Storage Manager server
accepts the object.
Explanation: The Tivoli Storage Manager client was
System action: File skipped. trying to restore or retrieve data that is currently
User response: See your system administrator to unavailable on the Tivoli Storage Manager server.
determine the maximum file (object) size for which Possible causes are:
your site's server is configured. v Data is corrupted at the Tivoli Storage Manager
server
FMV5039E Server out of data storage space. v The Tivoli Storage Manager server encountered a
read error
Explanation: The server does not have any space
v File is temporarily involved in a reclaim operation at
available to store the object.
the server
System action: Ended the current operation. v The Tivoli Storage Manager requested a tape volume
User response: You can take any of the following that is unavailable. Typical reasons for a volume to
actions: be unavailable: a disk volume is offline, the volume
is marked unavailable due to an I/O error, or a tape
v For client, set COMPRESSALWAYS=NO and
volume is checked out of the tape library.
COMPRESSIon=YES in the options file (DSM.OPT),
then the file will be resent uncompressed if it grows System action: Processing stopped.
during compression.
User response: Try the operation again at a later time.
v Request the system administrator to add space to the If the problem continues, contact your Tivoli Storage
storage pool. Manager server administrator for further assistance.
v The system administrator can also turn off disk The administrator can review the Tivoli Storage
caching in the disk storage pool, and issue MOVE Manager server activity log for messages related to the
DATA commands to each disk pool volume to clear problem.
out the cached bitfiles.
FMV5043W Unexpected retry request. The server
FMV5040E Server media mount not possible. found an error while writing the data.
Explanation: Server media mount not possible. The Explanation: None.
server timed out waiting for a mount of an offline
System action: The client retries the operation.
volume.
User response: None.
System action: File skipped.
User response: Retry later when server volumes can
FMV5044E Session rejected: All server sessions are
be mounted. Ensure that the MAXNUMMP (maximum
currently in use.
number of mount points) defined on the server for this
node is greater than 0. Explanation: Server has all available sessions in use
and cannot accept a new one at this time.
System action: Server canceled the current operation.
User response: Retry the operation.If the problem

470 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5045E • FMV5054E

continues, see your system administrator to increase the User response: Retry the operation after the server
number of concurrently active sessions to the server. returns to an enabled state. If the problem continues,
see your system administrator.
FMV5045E The session is rejected. Your password
has expired. FMV5050E The server is not configured to allow
open registration.
Explanation: Your password has expired.
Explanation: No authorization. Registration is
System action: Server canceled the current operation.
required by your system administrator. The server is
You are not allowed to connect to the server until the
not configured to allow open registration.
password is updated.
System action: Session not started.
User response: Update your password. You may use
the SET PASSWORD command, or have the User response: You must obtain a node and password
administrator update your node. from your system administrator.

FMV5046E Session rejected: Unknown or incorrect FMV5051S Session rejected: the client code is
node ID entered down-level
Explanation: The node name you entered is not Explanation: The server version and your client
known by the server, or you are attempting to access a version do not match. The client code is downlevel.
file migrated to a different node.
System action: The current operation is canceled.
System action: The current operation is canceled. You
User response: See your system administrator to see
are not allowed to connect to the server until your
what version to run for your location.
node name is registered with the server. If attempting
to access a migrated file, your node name must be the
same node which migrated the file. FMV5052E Session rejected: Downlevel server code
version.
User response: Ensure that you entered your node
name correctly. If yes, see your system administrator. Explanation: The server version and your client
Verify that the server is using closed registration and version do not match. The server code is downlevel.
that your node name is registered with the server.
System action: The current operation is canceled.

FMV5047E Session rejected: Duplicate ID entered. User response: See your system administrator to see
Node already logged onto server what version to run for your location.

Explanation: Another process using this node name is

active with the server. FMV5053W The operation was stopped by the user.

System action: Cannot connect to the server. Canceled Explanation: The operation was stopped at the request
the current operation. of the user. This usually occurs when the 'Q' key is
pressed two times.
User response: Ensure that your node name is unique
to the server so that it cannot be used by another System action: Processing stopped.
person. See your system administrator to identify the User response: None.
owner of that node name.

FMV5054E The operating system refused a request

FMV5048E Please choose a filespace.The filespace for memory allocation.
to delete/set access cannot be found.
Explanation: The client requires access to memory in
Explanation: The filespace to delete cannot be found. order to store information as processing proceeds. In
System action: The system returns to the calling this case, more memory was requested than the
procedure. operating system would allocate. Possible reasons
include:
User response: Verify the filespace name. v The system is low on memory.
v The process in which the program runs has exceeded
FMV5049E Session rejected: The server is disabled the maximum allocated memory.
Explanation: The server is in a disabled state and v Some other error condition occurred. No memory is
cannot be accessed for normal activity. available.

System action: Canceled the current operation. System action: Client cannot complete the requested
operation.

Chapter 6. FMV messages 471

FMV5055E • FMV5091S

User response: Close all unneeded applications and User response: Verify that you have sufficient access
try the operation again. If the operation still fails, try permissions to overwrite the file, then try the operation
dividing the task into several smaller units. For again. If the problem persists, contact your system
example, if a file specification contains several administrator or administrator for further assistance.
high-level directories, run the task serially for each
directory. If the task is an incremental backup, use the
FMV5060E Invalid parameter passed.
option "-memoryefficientbackup=yes".
Explanation: The system encountered an internal
program error due to an invalid parameter.
FMV5055E File not found during Backup, Archive
or Migrate processing. No file System action: The system returns to the calling
specification entered. procedure.
Explanation: The file being processed for backup, User response: Ask your service representative to
archive or migrate no longer exists on the client. check the error log.
Another process deleted the file before it could be
backed up, archived or migrated.
FMV5061E An invalid file handle passed. Report
System action: File skipped. how you got this system error.
User response: None. Explanation: An internal system error occurred. A file
operation failed because of an invalid file handle.
FMV5056E The specified directory path could not System action: Processing stops.
be found.
User response: Try the operation again. If the failure
Explanation: An invalid or unreachable directory path persists, obtain a service trace that captures the
was specified. problem and contact technical support for additional
assistance. Your administrator can help you configure
System action: Processing stopped.
the trace.
User response: Try the operation again using a valid
directory path.
FMV5062E Disk full
Explanation: Operation has stopped because the
FMV5057E Access to the specified file or directory
destination disk is full.
is denied.
System action: Processing stopped.
Explanation: Access to the specified file or directory is
denied. You tried to read from or write to a file and User response: Free up disk space and retry the
you do not have access permission for either the file or operation
the directory.
System action: Processing stopped. FMV5083E Drive specification contains wildcard
character.
User response: Ensure that you specified the correct
file or directory name, correct the permissions, or Explanation: Drive name shouldn't contain wildcard
specify a new location. character.
System action: Wildcarded objects skipped.
FMV5058E No file handles available
User response: Use valid drive specification.
Explanation: All file handles for your system are
currently in use. No more are available.
FMV5091S The Tivoli Storage Manager server does
System action: Processing stopped. not currently have space in the storage
pool for this file. This might be a
User response: Either free some file handles by ending
temporary condition.
other processes, or modify your system setup to allow
for more files to be open at the same time. Explanation: This message is typically issued when
the storage pool in which the data is being placed does
not have sufficient to store the data, but that the space
FMV5059E The file exists and cannot be
will be available soon. For example, a storage pool
overwritten.
migration may free up sufficient space to store the data.
Explanation: The file being restored or retrieved exists
System action: Tivoli Storage Manager ends the
and cannot be overwritten due to lack of authority or
current operation.
access permissions.
User response: This is possibly a temporary condition.
System action: The file is skipped.

472 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5092S • FMV5126S

Try the operation again at a later time. If the error

FMV5123S Open registration failed because the
persists, contact your Tivoli Storage Manager
specified node name is already defined
administrator, who can examine server console and
in the server.
error logs to locate the cause of the problem.
Explanation: Open registration failed because a node
is defined on the server with the same name.
FMV5092S Server out of data storage space.
System action: Tivoli Storage Manager canceled the
Explanation: The server does not have any more space
current operation.
available to store the object.
User response: Retry with another node name.
System action: Tivoli Storage Manager ended the
current operation.
FMV5124S Open registration failed because there is
User response: Report to your system administrator
no default domain.
that a storage pool on the server is full.
Explanation: Open registration failed because a
default policy domain does not exist in which to place
FMV5093S SLM_LICENSE_EXCEEDED: The client
your node. A default policy domain is required to fully
licenses for Tivoli Storage Manager are
support open node registration.
exceeded. See your Tivoli Storage
Manager administrator. System action: Tivoli Storage Manager cancels the
current operation.
Explanation: Adding a new enrollment will exceed the
product license count for this Tivoli Storage Manager User response: See your Tivoli Storage Manager
server. administrator for assistance in registering your node.
System action: The client enrollment or connection
request ends. FMV5125S Open registration failed because an
invalid node name was specified.
User response: See your Tivoli Storage Manager
administrator to delete unused enrollments or negotiate Explanation: Open registration failed because the
an increase in the number of allowed licenses for your specified node name has invalid characters.
server.
System action: Tivoli Storage Manager canceled the
current operation.
FMV5094E Session Rejected. Sufficient server
User response: Retry with another node name that
memory is not available.
does not have any invalid characters.
Explanation: The server does not have enough
memory to allow your client to establish a connection
FMV5126S Filespaces with duplicate names are not
with the server.
supported. Please unmount the
System action: Session was not started. duplicate filespace.
User response: Retry later or see your system Explanation: The selected filespace has a duplicate
administrator. volume label. Because Tivoli Storage Manager uses the
volume label to keep track of backup/archive
information, it cannot back up or archive files from a
FMV5122E The specified filespace does not exist on
filespace with a duplicate volume label.
the server. The filespace might have
been deleted by another client or an System action: Tivoli Storage Manager cannot select
administrator. the volume.
Explanation: The specified filespace does not exist on User response: If the filespace needs to be available to
the server. Your administrator might have already the system, exit Tivoli Storage Manager, and assign a
deleted the filespace or another client using your volume label to the filespace. Restart Tivoli Storage
client's node name might have deleted it. Manager and retry the operation. Otherwise, unmount
the duplicate filespace.
System action: Tivoli Storage Manager ends the
current operation.
User response: The filespace you selected does not
exist any more. See your Tivoli Storage Manager
administrator for help in finding how the filespace was
deleted.

Chapter 6. FMV messages 473

FMV5127I • FMV5136E

User response: Select the volumes you want to delete

FMV5127I Tivoli Storage Manager has detected an
and retry the operation.
incomplete setup! The system options
file 'dsm.sys' was not found, while the
client options file 'file-path' exists! The FMV5132I Filespace deletion canceled by user
wizard will guide you through the
configuration process of the initial basic Explanation: You requested to cancel the filespace
TSM client options files replacing your deletion operation.
current option file. Would you like to System action: The filespace deletion operation
continue? stopped.
Explanation: Tivoli Storage Manager has detected an User response: Continue with normal operations.
incomplete setup. The system options file, dsm.sys, was
not found. Additionally, a user options file, dsm.opt,
was found. To complete the configuration the FMV5133I Filespace 'filespace' was deleted
configuration wizard will create dsm.sys and replace Explanation: The specified filespace was successfully
dsm.opt with minimal settings. deleted.
System action: Tivoli Storage Manager may stop System action: Tivoli Storage Manager deleted the
User response: If the current version of dsm.opt is filespace.
needed, rename the file and restart Tivoli Storage User response: Continue with normal operations.
Manager. If the current version is not needed, select yes
and allow Tivoli Storage Manager to replace the file.
FMV5134E Unable to delete the filespace because
this node does not have permission to
FMV5128E The management class for this file did delete archived data and/or backed up
not have a backup copy group. data.
Explanation: For backup operations, a file may only Explanation: You tried to delete a filespace that you
be bound to a management class that has a backup do not have permission to access.
copy group.
System action: Tivoli Storage Manager canceled the
System action: Tivoli Storage Manager did not back operation.
up the file.
User response: Ensure that you specify the correct
User response: See your Tivoli Storage Manager filespace, or specify a filespace you have access to.
system administrator for assistance in finding a
management class with the required copy group. The
administrator may also define such a management class FMV5135I Archive delete stopped by user
for you. Explanation: You requested to stop the archive delete
operation.
FMV5129E The management class for this file did System action: Archive delete stopped.
not have an archive copy group
specified. User response: Continue with normal operations.
Explanation: For archive operations, a file may only
be bound to a management class that has an archive FMV5136E Not enough memory for archive delete
copy group. operation
System action: Tivoli Storage Manager did not archive Explanation: Tivoli Storage Manager cannot allocate
the file. memory for the specified archive delete operation.
User response: See your Tivoli Storage Manager System action: Tivoli Storage Manager cannot
system administrator for assistance in finding a continue with the requested archive delete operation.
management class with the required copy group. The
User response: Close all unneeded applications and
administrator may also define such a management class
retry the operation. Reducing the scope of queries and
for you.
the amount of data returned might also help, or see
your system administrator.
FMV5130W No filespaces selected for deletion
Explanation: You requested a deletion operation
without selecting a client domain.
System action: Tivoli Storage Manager cannot perform
a deletion without a domain selected.

474 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5138I • FMV5153E

System action: Processing stopped; waiting for user

FMV5138I Archive delete completed
intervention.
Explanation: An archive delete was completed.
User response: Answer “Yes” to start the archive data
System action: Tivoli Storage Manager deleted the conversion. If you answer “No”, the current operation
archived files. will be canceled.
User response: Continue with normal operations.
FMV5150E An active restore for the same source
file specification exists. Unable to
FMV5139E Your node does not have permission to
continue with this request.
delete archived files.
Explanation: Currently, there is an active restore for
Explanation: Your node is registered at the server
the same source file specification. Another restore of the
with the ARCHDELETE option set to 'no'. Therefore
same source file specification cannot be started.
your node is not allowed by the server to delete
archived files. System action: The requested restore fails.
System action: Tivoli Storage Manager did not delete User response: Start another restore with a different
the archived files. source file specification.
User response: See your Tivoli Storage Manager
system administrator. The administrator has authority FMV5151S This node currently has a pending
to delete archived files, and can also grant that restartable restore session. The
authority to your node. requested operation cannot complete
until this session either completes or is
canceled.
FMV5145W Server cannot restart the last restore
request. Do you want to restore without Explanation: This operation can not be completed
restart? because a restartable restore session is pending. The
operation is not allowed because the restartable session
Explanation: The restart restore token has expired.
and the current operation affect the same file space.
The server cannot restart the restore from where it last
ended. System action: Tivoli Storage Manager ended the
current operation.
System action: Processing stopped; waiting for user
intervention. User response: Issue the Query Restore command to
view a list of your restartable restore sessions in the
User response: Retry the request without restart or
server database. Issue the Cancel Restore command to
abort the request.
cancel any unneeded restartable restore sessions.

FMV5146W You cannot perform this operation while

FMV5152S Session Rejected: The server is not
accessing data for another node. Do you
licensed for this platform type. See your
wish to switch back to accessing your
Tivoli Storage Manager administrator.
own node?
Explanation: The server license governs the types of
Explanation: The user cannot perform the selected
client that can connect to it. The license for this server
operation while accessing another users data.
does not include the requesting client type.
System action: Processing stopped; waiting for user
System action: The client enrollment or connection
intervention.
request ends.
User response: Answer "Yes" to switch back to
User response: See your Tivoli Storage Manager
accessing the server as the original node.
administrator who must upgrade the server license to
accept your client type.
FMV5148W The server needs to do a one-time
conversion of your archive data before
FMV5153E Session Rejected: The server does not
you can continue. This operation may
allow a signon as a Unicode enabled
take a long time, and cannot be canceled
client.
once it has started. Are you willing to
wait for the conversion to complete? Explanation: The client cannot establish a connection
to the server because of a unicode enabling mismatch
Explanation: The server must do a conversion of the
between server and client.
archive data before continuing. The conversion could
take a long time, and cannot be canceled once it is System action: Session was not started.
started.

Chapter 6. FMV messages 475

FMV5154I • FMV5173E

User response: See your system administrator backup or archive information, it cannot back up or
immediately. archive files from a drive with a duplicate volume
label.
FMV5154I File is implicitly excluded System action: Tivoli Storage Manager cannot select
the drive for backup or archive operations.
Explanation: You tried to back up or migrate a file
that is implicitly excluded. User response: If the volume needs to be available to
the system, exit Tivoli Storage Manager and assign a
System action: Tivoli Storage Manager will not back
unique volume label to the drive. Restart Tivoli Storage
up or migrate an implicitly excluded file.
Manager and try the operation again.
User response: None.
FMV5165E Drive has no volume label.
FMV5155E Valid password not available. The Tivoli Backup/Archive not allowed.
Storage Manager administrator for your
Explanation: You tried to backup or archive a drive
system must run Tivoli Storage Manager
that has no volume label.
and enter the password to store it
locally. System action: Tivoli Storage Manager rejected the
selected drive.
Explanation: The file containing the stored password
for the specified server server-name is unavailable. User response: If the drive is a floppy drive, place a
disk with a volume label in it and retry the operation.
System action: Tivoli Storage Manager ends.
If the disk is a hard drive, ensure the drive has a
User response: The Tivoli Storage Manager volume label, and retry the operation.
administrator for your system must set and store a new
password.
FMV5166E An error occurred while removing
include-exclude statement 'statement'.
FMV5157E This action requires Tivoli Storage Please try again.
Manager administrative authority on
Explanation: There was a problem with removing the
this system.
include-exclude statement. Make sure that your
Explanation: An activity has been attempted that must include-exclude statement is valid.
be performed by the Tivoli Storage Manager
System action: No include-exclude statement was
administrator (for example, open registration, filespace
removed. Waiting for user action.
delete or password update).
User response: Retry your operation. If you see this
System action: Tivoli Storage Manager canceled the
error message again, contact your system administrator
operation.
User response: If the activity is required, the Tivoli
FMV5169E The destination path must contain a
Storage Manager administrator for this system must
drive letter
perform it.
Explanation: The entered path must begin with a
drive letter, colon, and root slash.
FMV5158S Filespace deletion is in progress. Try
again later. System action: Tivoli Storage Manager did not
continue with the requested operation.
Explanation: The filespace is in the process of being
deleted. User response: Enter the destination path in the
correct format.
System action: Tivoli Storage Manager cannot
complete the requested operation.
FMV5173E An error occurred accessing NTFS
User response: Try the operation again later. If the
security information.
filespace was being deleted, it could take awhile for it
to complete. If the problem continues, report the Explanation: An error occurred while attempting to
problem to your system administrator. access NTFS security information.
System action: Object will not be processed.
FMV5164E Backup or archive of drives with
User response: See your system administrator or
duplicate volume labels is not allowed.
bypass by using SkipNTSecurity option.
Explanation: You tried to back up or archive a drive
that has a duplicate volume label. Because Tivoli
Storage Manager uses the volume label to keep track of

476 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5174E • FMV5186E

FMV5174E A required NT privilege is not held. FMV5181E Invalid selection; A specific backup set
must be selected.
Explanation: The user account running Tivoli Storage
Manager does not possess a required NT user Explanation: A selection was made that might result
right/privilege for performing the current operation. in multiple backup sets being restored at the same
time, but restoring multiple backup sets at the same
System action: Object will not be processed.
time is not supported.
User response: See your system administrator.
System action: The backup set restore was not
performed.
FMV5176W The requested virtual machine operation
User response: Select a specific backup set to be
cannot be performed because a virtual
restored.
machine backup or restore operation is
already in progress. Please retry the
operation after the first operation FMV5182E Multiple backup sets can not be
completes. restored at the same time.
Explanation: A virtual machine operation is already in Explanation: Multiple backup sets were selected to be
progress, so the requested virtual machine operation restored, but restoring multiple backup sets at the same
cannot be performed until the first operation complets. time is not supported.
System action: Processing stops System action: The backup set restore was not
performed.
User response: Wait for the first virtual machine
operation to complete, and then restart the current User response: Select a specific backup set to be
request. restored.

FMV5177E Client-side deduplication and FMV5183W Objects of different types cannot be

server-initiated sessions are mutually restored at the same time.
exclusive.
Explanation: Restoring objects of different types is not
Explanation: Conflicting options allowed. For example, restoring Backup Sets and
SESSIONINIT=serveronly and DEDUPLICATION=yes regular file objects at the same time is not possible.
were specified. This combination is not allowed.
System action: No processing takes place.
System action: Processing stops.
User response: Select objects of the same type to
User response: Use client-initiated sessions or disable perform restore operation.
client-side deduplication
FMV5184E Illegal Operation On Following Object:
FMV5178E Restart of the RSM service failed. object
Restart the RSM service manually.
Explanation: Requested operation cannot be
Explanation: RSM database files have been restored performed on this object.
from the Tivoli Storage Manager server and imported.
System action: This object will be skipped.
Tivoli Storage Manager has tried to restart the RSM
service on the user's behalf but has run into a problem. User response: Try another operation on this object, or
try the same operation on another object.
System action: Processing stopped.
User response: Restart the RSM service manually.
FMV5186E Server is downlevel, System Services
and System State backup disabled for
FMV5179E Tivoli Storage Manager is unable to this session.
continue. Exiting program.
Explanation: The operation cannot be performed
Explanation: Tivoli Storage Manager ran into a because server version is downlevel.
problem and is unable to continue. This error message
System action: System Service and System State
is usually preceded by other error messages. Resolve
backup is disabled for this session.
those errors and try again.
User response: Must use level 5.2.0 or higher server.
System action: Program terminates.
User response: Fix the problem(s) that preceded this
message and then restart Tivoli Storage Manager.

Chapter 6. FMV messages 477

FMV5187E • FMV5197E

FMV5187E Unable to set SHAREAS extended FMV5192E NT Active Directory is online. Online
attribute for file: 'pathname' Return code: restore is not supported.
'returncode' 'strerror' Reason code:
Explanation: NT Active Directory is online when
'reasoncode'
performing a restore operation. Online restore is not
Explanation: You must be the file owner or have supported.
superuser authority.
System action: Processing stopped.
System action: File processed without setting
User response: Reboot computer and enter Active
attribute.
Directory repair mode, then try the operation again.
User response: The attribute must be set manually.
FMV5193E Certificate Services is not online.
FMV5188E Unable to clear SHAREAS extended Offline backup is not supported.
attribute for file: 'pathname' Return code:
Explanation: Certificate Services is not online when
'returncode' 'strerror' Reason code:
performing a backup operation. Offline backup is not
'reasoncode'
supported.
Explanation: You must be the file owner or have
System action: Processing stopped.
superuser authority.
User response: Start Certificate Services and try the
System action: File processed without setting
operation again.
attribute.
User response: The attribute must be set manually.
FMV5194E Certificate Services is online. Online
restore is not supported.
FMV5189E Unable to set APF extended attribute for
Explanation: Certificate Services is online when
file: 'pathname' Return code: 'returncode'
performing a restore operation. Online restore is not
'strerror' Reason code: 'reasoncode'
supported.
Explanation: You must have at least READ access to
System action: Processing stopped.
the BPX.FILEATTR.APF facility class profile and you
must be the file owner or have superuser authority. User response: Stop Certificate Services and try the
operation again.
System action: File processed without setting
attribute.
FMV5196W Invalid encryption key password
User response: The attribute must be set manually.
entered.
Explanation: The encryption key password supplied
FMV5190E Unable to set PROGCTL extended
does not meet the Tivoli Storage Manager requirements.
attribute for file: 'pathname' Return code:
This key can be up to 63 bytes in length and include
'returncode' 'strerror' Reason code:
the following characters: A-Z Any letter, A through Z,
'reasoncode'
uppercase or lowercase 0-9 Any number, 0 through 9 +
Explanation: You must have at least READ access to Plus . Period _ Underscore - Hyphen & Ampersand
the BPX.FILEATTR.PROGCTL facility class profile and
System action: Tivoli Storage Manager allows you to
you must be the file owner or have superuser authority.
try again.
System action: File processed without setting
User response: Enter the correct encryption key
attribute.
password.
User response: The attribute must be set manually.
FMV5197E File Replication Service backup failed.
FMV5191E NT Active Directory is not online.
Explanation: IBM Tivoli Storage Manager encountered
Offline backup is not supported.
an error while backing up files under control of the
Explanation: NT Active Directory is not online when Windows 2000 File Replication Service
performing a backup operation. Offline backup is not
System action: Processing stopped.
supported.
User response: Examine the Windows 2000 File
System action: Processing stopped.
Replication Service Event log to insure the File
User response: Reboot computer and turn on Active Replication Service is operating properly. Restart the
Directory, and try the operation again. service and retry the backup operation.

478 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5198E • FMV5208E

FMV5198E File Replication Service restore failed. FMV5203E An error occurred saving one or more
registry keys
Explanation: IBM Tivoli Storage Manager encountered
an error while restoring files under control of the Explanation: None.
Windows 2000 File Replication Service
System action: Processing stopped.
System action: Processing stopped.
User response: Check the client error log for any other
User response: Examine the Windows 2000 File messages that might help identify the problem. Try the
Replication Service Event log to insure the File operation again. If the problem persists, contact IBM
Replication Service is operating properly. Restart the technical support for further assistance.
service and retry the restore operation.
FMV5204W Only one backup set may be selected
FMV5199I The machine must be rebooted for the for restore.
changes to take effect. Would you like
Explanation: Restoring multiple backup sets is not
to reboot the machine now?
allowed. Only one backup set may be selected and
Explanation: The machine must be rebooted for the restored.
changes to take effect. The user can select to have the
System action: No processing takes place.
program reboot the machine now or can perform this
action manually at a later time. User response: Only one backup set may be selected
for restore.
System action: Tivoli Storage Manager None.
User response: Select 'YES' to reboot the machine
FMV5205E An error saving one or more eventlogs
immediately.
Explanation: An error occurred saving one or more
eventlogs.
FMV5200I 'service-name' service needs to be
restarted. System action: Processing stopped.
Explanation: The service must be restarted for the User response: Correct the command and retry the
restored changes to take effect. operation.
System action: Changes are not effected.
FMV5206E An error occurred replacing one or more
User response: Restart the service.
registry keys.
Explanation: The registry key or keys being replaced
FMV5201E The specified function is not
are exclusively held by another process. This can
implemented
happen if the registry keys were previously restored
Explanation: The specified function is not but the system was not restarted.
implemented.
System action: Processing stops.
System action: Processing stopped.
User response: Restart the system and try the restore
User response: Correct the command and retry the operation again.
operation.
FMV5207I The machine must be rebooted for the
FMV5202I One or more system objects were changes to take effect
excluded from processing by entries in
Explanation: The machine must be started for the
the include-exclude list.
changes to take effect.
Explanation: One or more system objects were
System action: Tivoli Storage Manager backed up the
excluded from processing by entries in the
files.
include-exclude list and the client did not process them.
User response: Reboot the machine
System action: Excluded objects skipped.
User response: None.
FMV5208E An invalid date or time was entered.
Explanation: An invalid date or time value was
entered. Either the syntax of the value was not correct,
or an actual value (for example, “45” for month) was
invalid.
System action: Processing stops.

Chapter 6. FMV messages 479

FMV5209E • FMV5217E

User response: Identify and correct the invalid date or User response: Select NAS objects without other
time value. Refer to the user’s guide of the objects to perform backup NAS operation.
corresponding platform for the correct date syntax.
FMV5214W NAS objects cannot be selected with
FMV5209E System Volume backup failed. other objects for restore.
Explanation: IBM Tivoli Storage Manager encountered Explanation: Restoring NAS objects with other types
an error while backing up files of the Windows 2000 of objects is not allowed.
System Volume
System action: No processing takes place.
System action: Processing stopped.
User response: Select NAS objects without other
User response: Examine the Windows 2000 File objects to perform restore NAS operation.
Replication Service Event log to insure the system
volume was successfully initialized. Restart the service
FMV5215E function-type is not allowed on object
and retry the backup operation
'object'. Object is not sent to the server.
Explanation: The operation could not be performed
FMV5210E System Volume restore failed.
on this object. For example, if this is an image
Explanation: IBM Tivoli Storage Manager encountered operation, the selected path is a file or a directory and
an error while restoring files of the Windows 2000 therefore is not a valid object for image operations.
System Volume
System action: This object is skipped.
System action: Processing stopped.
User response: Verify that the object named is of a
User response: Examine the Windows 2000 File type supported by the command. For example, if a
Replication Service Event log to insure the system filespace name is required but a directory name was
volume was successfully initialized. Restart the service given, change the name so it includes only the filespace
and retry the restore operation. name.

FMV5211E The cluster service is offline. The cluster FMV5216E Could not establish a TCP/IP connection
service must be online to perform an with address 'tcp-addr:tcp-port'. The
authoritative cluster database restore TCP/IP error is 'tcp-err-string' (errno =
operation. errno).
Explanation: The cluster service must be online to Explanation: A TCP/IP connection was attempted
restore the cluster database. Tivoli Storage Manager with a server or agent program and failed.
tried to start the service and failed. It is possible that an
System action: Processing stops.
authoritative restore cannot be done.
User response: Ensure that the target TCP/IP address
System action: Processing stops.
and port number is correct. Check to ensure that a
User response: Start the cluster service and retry the Tivoli Storage Manager server or agent has been started
operation. at the target TCP/IP address and is configured to listen
at the port listed in the message.
FMV5212E An error occurred while trying to
rename file space. FMV5217E Your node does not have permission to
delete backed up files.
Explanation: This operation can not be completed
because the file space could not be renamed. Explanation: You cannot delete backed up files unless
your Tivoli Storage Manager administrator has
System action: Tivoli Storage Manager ended the
authorized your node to do so.
current operation.
System action: Tivoli Storage Manager does not delete
User response: Contact system administrator for more
the backed up files.
information.
User response: Use the DSMC QUERY SESSION
command to verify your authorization. Ask your Tivoli
FMV5213W NAS objects cannot be selected with
Storage Manager administrator to provide the
other objects for backup.
necessary authorization.
Explanation: Backing up NAS objects with other types
of objects is not allowed.
System action: No processing takes place.

480 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5219W • FMV5230E

FMV5219W Objects of different groups cannot be FMV5227E Tivoli Storage Manager detected an
restored at the same time. error where both a snapshot name was
specified, and a request to create a
Explanation: Restoring objects of different groups is
snapshot were specified.
not allowed.
Explanation: Either a snapshot name should be
System action: No processing takes place.
specified, or a request for Tivoli Storage Manager to
User response: Select objects of the same group to create the snapshot should be specified, but not both.
perform restore operation.
System action: Processing stops.
User response: This is an internal error and should be
FMV5222E The archive description exceeds 254
reported to your service representative.
characters.
Explanation: Tivoli Storage Manager places a
FMV5228E A backup VM operation failed because
maximum length of 254 characters on the archive
VMMAXPARALLEL was reduced to 1
description.
and the client still cannot obtain a
System action: processing stops. server mount point.

User response: Issue the command again and specify Explanation: During a parallel backup operation,
a shorter valid archive description. concurrent backup sessions required additional server
mount points to perform the backups in parallel. The
client attempted to obtain the additional mount points,
FMV5224W Error error code encountered while but the client requests exceeded the number of mount
reverting to the restored snapshot. points (MAXNUMMP) defined for the node. In an
Explanation: After the virtual machine disks are effort to make the backup occur, the client reduced the
restored, the virtual machine is reverted to the restored VMMAXPARALLEL option to 1, but was still unable to
state. The specified error was encountered while obtain a mount point. The backup operation was
performing this revert operation. stopped.

System action: Processing continues System action: The backup operation was stopped

User response: Try powering on the restored virtual User response: Check the console or schedule log for
machine. If it fails to start, re-try the restore process. additional information. Retry the operation at a later
time. Ensure VMMAXPARALLEL is set to a value less
than or equal to MAXNUMMP.
FMV5225W Error error code encountered while
removing the restored snapshot.
FMV5229E The Snapshot is already mounted for
Explanation: After the virtual machine disks are backup 'backup-name'.
restored, the virtual machine is reverted to the restored
state, and the snapshot is removed. The specified error Explanation: The Snapshot is currently mounted on
was encountered while removing the snapshot. the local machine or a remote machine. No mount
operation on the snapshot will be allowed until it has
System action: Processing continues been unmounted.
User response: Try powering on the restored virtual System action: Processing stops
machine. If it fails to start, re-try the restore process.
User response: See the dsmerror.log file for further
details.
FMV5226E The virtual machine backup operation
failed.
FMV5230E The Snapshot is already imported to the
Explanation: The virtual machine backup operation local system for backup 'backup-name'.
failed. Check the error log for details on why the
operation failed. Explanation: The Snapshot is currently imported on
the local machine. This maybe becasue the Snapshot is
System action: Processing stops in use or it was not created with the Import VSS
User response: Review the console output and error snapshots only when needed feature enabled.
logs for the details on the problem. Fix any issues and System action: Processing stops
restart the operation.
User response: Remote Mount operation not allowed
on snapshots that are currenlty imported.

Chapter 6. FMV messages 481

FMV5231E • FMV5254E

FMV5231E VMDK size reported by VMware FMV5250E An unexpected error was encountered.
vSphere API is different than actual size Tivoli Storage Manager function name :
of vmdk file. Reissue the restore function-name Tivoli Storage Manager
command with the testflag function : function-desc Tivoli Storage
-VMRESTORE_INCVMDKSIZE. Manager return code : TSM-rc Tivoli
Storage Manager file : file-name
Explanation: VMDK size reported by VMware
(line-number)
vSphere API for virtual machine configuration is
different than actual size of vmdk file. This can be the Explanation: None.
result of running a storage alignment tool on vmdk
System action: Processing stops.
files before backup.
User response: Contact the Tivoli Storage Manager
System action: Restore processing stops.
administrator with the information provided in this
User response: Reissue the restore command with the message.
testflag -VMRESTORE_INCVMDKSIZE.
FMV5251E The snapshot provider is not available
FMV5245W TCPWINDOWSIZE optionCur is for this operation.
specified, but exceeds the maximum
Explanation: Tivoli Storage Manager was not able to
value allowed by Tivoli Storage
take a snapshot because the snapshot provider is not
Manager. TCPWINDOWSIZE optionNew
available.
will be used instead.
System action: Processing stopped.
Explanation: Refer to product manual for more
information about the TCPWINDOWSIZE option. User response: If you are attempting an operation
using the Microsoft Volume Shadow Copy service make
System action: The operation continues with the
sure that Volume Shadow Copy service is installed on
maximum value allowed by Tivoli Storage Manager.
the system and also ensure that the Tivoli Storage
User response: Set TCP window size to a value in the Manager snapshot plugin "pivss.dll" is present.
allowable range.
FMV5252E Tivoli Storage Manager attempted to
FMV5246W TCPWINDOWSIZE optionCur is execute a system command which failed.
specified, but exceeds the maximum command : command rc : rc
value allowed by the operating system.
Explanation: Tivoli Storage Manager needed to
TCPWINDOWSIZE optionNew will be
execute a system command in conjunction with a
used instead.
snapshot operation.
Explanation: The specified value is within the range
System action: Processing stops.
allowed by Tivoli Storage Manager, but the operating
system restricts the value to something less. User response: See your system administrator.
System action: The operation continues with the
maximum value allowed by the operating system. FMV5253W The system could not create Volume
Shadow Copy Services staging directory
User response: Set TCP window size to a value
'dir'.
allowed by the operating system.
Explanation: The system was unable to create a
user-specified location for the Volume Shadow Copy
FMV5249E The virtual machine restore operation
Services staging area. The default staging area on the
failed.
system drive will be used instead.
Explanation: The virtual machine restore operation
System action: Processing continues.
failed. Check the error log for details on why the
operation failed. User response: Check the option to specify the staging
area for Volume Shadow Copy Services operations and
System action: Processing stops
specify a valid location.
User response: Review the console output and error
logs for the details on the problem. Fix any issues and
FMV5254E The Volume Shadow Copy Services
restart the operation.
snapshot plugin 'pivss.dll' was not
found.
Explanation: The system cannot find the VSS snapshot
plugin 'pivss.dll' in any of the plugin locations.

482 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5255E • FMV5262I

System action: Processing stops. this error. Use the Windows command VSSADMIN
LIST WRITERS to determine the status of the Volume
User response: Check the Tivoli Storage Manager
Shadow Copy service. Reboot the machine to clear the
installation to ensure the plugin was installed correctly.
volume shadow copy error state. If the system is a
Domain Controller and the Active Directory service is
FMV5255E Unable to copy local file 'local-file' to stopped, restart the Active Directory service.
remote location 'remote-file'.
Explanation: An attempt to transfer a file to a remote FMV5259W Failed to update volume 'volume' for
system failed.. read-write access used for 'volume'.

System action: Processing stops. Explanation: Changing the volume to read-write

access requires exclusive access to the volume. If the
User response: Ensure that the directory path on the volume is opened by any application, this operation
remote system exists and that the Tivoli Storage will fail.
Manager application has the proper authority to write
to that location. System action: Processing continues.
User response: Close all the applications using the
FMV5256E Unable to copy remote file 'remote-file' to volumes and use operating system's interface to mount
local location 'local-file'. failed volume for read-write access.

Explanation: An attempt to transfer a file from a

remote system failed.. FMV5260W Restore object 'volume' has volume either
source 'volume' or target 'volume' volume
System action: Processing stops. that has already been selected for
User response: Ensure that the directory path on the restore from a different snapshot
remote system exists and that the Tivoli Storage volumes. It will be restore using
Manager application has the proper authority to read file-level copy.
from that location. Explanation: This error can occur when multiple
objects are selected for snapshot restore and have data
FMV5257E The volume 'volume' does not support overlapping on the volumes and were selected for
the requested VSS operation. restore from different backup versions. Snapshot restore
can only be performed from one local backup.
Explanation: The volume does not support the
requested VSS operation. Some reasons for this error System action: The restore object identified in the
include: message will be restored using the file-level copy after
snapshot restore is completed.
v For off-load backup requests, a hardware provider
cannot be found User response: Retry the restore of identified object
v For off-load backup requests, the provider does not separately for faster restore using snapshot.
support transportable media
v For local backup requests, the provider does not FMV5261W An attempt to create a snapshot has
support persistent snapshots failed. Another attempt will be made to
create the snapshot in number seconds.
System action: Processing stops.
Explanation: An attempt to create a snapshot has
User response: Retry the request using a supported
failed with a retryable error. The program will wait for
backup destination.
a short time and retry the operation.
System action: None.
FMV5258E Microsoft volume shadow copy
snapshot initialization failed. User response: Check the IBM Tivoli Storage Manager
error logs for additional information.
Explanation: IBM Tivoli Storage Manager encountered
an error while initializing the Microsoft Volume
Shadow Copy Service for backup or restore. The IBM FMV5262I Snapshot restore will failover to
Tivoli Storage Manager error log and Windows event file-level copy from snapshot volume.
log can contain additional information about this error.
Explanation: Snapshot restore is not possible due to
System action: IBM Tivoli Storage Manager stops the an error at this time. Tivoli Storage Managerwill
operation. automatically fails over to other restore method to
complete the restore operation.
User response: Try the operation again. If the error
persists, review the IBM Tivoli Storage Manager error System action: Processing continues.
log and Windows event log for information related to

Chapter 6. FMV messages 483

FMV5263E • FMV5270E

User response: Check Tivoli Storage Manager error User response: Check Tivoli Storage Manager error
log for more information from messages preceding this log for more information from messages preceding this
one to identify the error condition. one.

FMV5263E Snapshot module for 'snapshot provider' FMV5267E Disk Mapper module failed for the
failed with error 'error msg'. operation.
Explanation: The snapshot module for identified Explanation: An underlying Tivoli Storage Manager
snapshot provider failed to perform the operation and operation has failed to perform the operation due to
returned with the identified error. system error.
System action: Restore may automatically failover to System action: Processing stops.
alternate restore method 'file-level copy from snapshot
User response: Check Tivoli Storage Manager error
volume' if possible. Otherwise, processing stops.
log for more information from messages preceding this
User response: Check Tivoli Storage Manager error one to identify cause of the failure. Contact Tivoli
log for more information from messages preceding this Storage Manager administrator for more information.
one. Use snapshot provider interface to identify and
correct the problem.
FMV5268W The Microsoft Volume Shadow Copy
Services writer 'name' current state (state)
FMV5264W No snapshot plugin found for 'snapshot is not valid for the current operation.
provider' snapshot provider.
Explanation: None.
Explanation: The snapshot restore requires a plugin
System action: The system will retry the operation
for the specified snapshot provider type. The plugin
automatically after thirty seconds up to three times to
must be installed under Tivoli Storage Manager
allow the writer to return to the proper state. If after
directory.
three attempts the writer is still in the incorrect state,
System action: Restore will failover to alternate the operation will fail.
restore method of 'file-level copy from snapshot
User response: Determine if there are other Volume
volume'.
Shadow Copy Services operations that are occurring
User response: Contact your Tivoli Storage Manager concurrently with the current operation.
administrator to obtain and install the required plugin
module.
FMV5269E The Microsoft Volume Shadow Copy
Services writer 'name' current state (state)
FMV5265W Snapshot restore has already been is not valid for the current operation or
initialized using 'snapshot provider' cannot be determined. The last error
provider module. Another module for reported is 'error'.
'snapshot provider' provider can not be
Explanation: None.
loaded at the same time for restore of
'object name'. System action: Processing stops.
Explanation: This error occurs when restoring User response: Check the Microsoft event log to
multiple LOCAL backup objects that were created determine if there are any problems with the writer.
using different snapshot providers. Snapshot restore
can only be done using one snapshot interface.
FMV5270E A VSS restore request with timestamp
System action: Restore will failover to file-level copy 'time1' conflicts with a restore request
restore from snapshot volume. with timestamp 'time2'
User response: If snapshot restore is desired for the Explanation: A VSS restore request was issued which
object identified in the message, restore it using a requires restoring multiple components which reside in
separate command. VSS backup documents with different backup
timestamps. For example, a user backs up Exchange
storage group STG1 on Monday and Exchange storage
FMV5266E File-level copy restore of 'object name'
group STG2 on Tuesday. On Wednesday, the user tries
failed.
to restore STG1 and STG2.
Explanation: Data files could not be copied from the
System action: Processing stops.
local backup to their destination, causing restore to fail.
User response: Resubmit the restore request as
System action: Processing continues to another object,
separate requests for each component. For example, if
if multiple objects are selected for restore.
you receive this error trying to restore Exchange

484 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5271E • FMV5280E

storage groups STG1 and STG2, resubmit a restore

FMV5275E A Microsoft Volume Shadow Copy
request for storage group STG1 and a separate restore
Services writer is in an invalid state
request for storage group STG2.
before restore initialization.
Explanation: None.
FMV5271E A Microsoft Volume Shadow Copy
Services writer is in an invalid state System action: Processing stops.
before snapshot initialization.
User response: See the Tivoli Storage Manager error
Explanation: None. log for additional information.
System action: Processing stops.
FMV5276E A Microsoft Volume Shadow Copy
User response: See the IBM Tivoli Storage Manager
Services writer is in an invalid state
error logs for additional information.
after preparing for a restore operation.
One of the VSS writers is in an invalid or unexpected
Explanation: None.
state. Try the command "vssadmin list writers" and
check the state of VSS writers. Writers must be in System action: Processing stops.
STABLE state before IBM Tivoli Storage Manager can
User response: See the Tivoli Storage Manager error
continue with VSS operations. Some of the writers can
log for additional information.
recover automatically from minor errors. In most cases,
restarting a writer solves the problem. The easiest way
to restart writers is to restart the operating system. It is FMV5277E A Microsoft Volume Shadow Copy
possible to restart the specific service that implements a Services writer is in an invalid state
VSS writer, but it is difficult to determine which service after restore termination.
to restart.
Explanation: None.

FMV5272E A Microsoft Volume Shadow Copy System action: Processing stops.

Services writer is in an invalid state User response: See the Tivoli Storage Manager error
after snapshot initialization. log for additional information.
Explanation: None.
System action: Processing stops. FMV5278W Error processing 'filename': file not
found.
User response: See the Tivoli Storage Manager error
log for additional information. Explanation: The file being processed for backup,
archive or migrate, no longer exists on the client.
Another process deleted the file before it could be
FMV5273E A Microsoft Volume Shadow Copy backed up, archived or migrated by Tivoli Storage
Services writer is in an invalid state Manager.
after taking a snapshot.
System action: File skipped.
Explanation: None.
User response: None.
System action: Processing stops.
User response: See the Tivoli Storage Manager error FMV5279E Error processing 'filename': file not
log for additional information. found.
Explanation: The file being processed for backup,
FMV5274E A Microsoft Volume Shadow Copy archive, or migrate, no longer exists on the client.
Services writer is in an invalid state Another process deleted the file before it was backed
after backup completion. up, archived, or migrated by IBM Tivoli Storage
Manager.
Explanation: None.
System action: Processing stops.
System action: Processing stops.
User response: None.
User response: See the Tivoli Storage Manager error
log for additional information.
FMV5280E Object enumeration from a file set or
file list failed.
Explanation: For more information, see the IBM Tivoli
Storage Manager client error log. This message is
always accompanied by error log message FMV5279E if

Chapter 6. FMV messages 485

FMV5281E • FMV5287W

the object was not found or by FMV5250E for other

FMV5285E The Microsoft Volume Shadow Copy
causes, for example, access was denied. These messages
Services (VSS) backup XML document
identify the object in question.
is not valid for restore. For more
System action: Processing stopped. information, see the Tivoli Storage
Manager client error log.
User response: See the user response based on other
messages in the client error log. Explanation: Microsoft has released a Volume Shadow
Copy Services (VSS) update in the following operating
system versions:
FMV5281E A remote backup failure has occurred.
remote node name : node remote address v Windows 2003 update rollup package KB940349
: address multi-node name : multi-node v Windows Vista Service Pack 1
error message : msg return code : rc
This new VSS fix packages causes VSS to generates
Explanation: For more information, see the IBM Tivoli .xml control files in a format which is not compatible
Storage Manager client error log on the remote system. with the earlier versions of VSS. This error can occur
when a system state restore is being performed from a
System action: Processing stopped. base operating system level which does not have the
User response: See the user response based on other VSS fixes applied and the system state backup files
messages in the client error log. were created by an operating system level that did
have the VSS fixes applied.

FMV5282E A remote backup failure has occurred. System action: Processing stops.

Explanation: For more information, see the IBM Tivoli User response: The restore procedure for Windows
Storage Manager client error log. system state requires that the operating system version
and service pack level used to initiate the restore be at
System action: Processing stopped. the same operating system and service pack level used
User response: See the user response based on other to create the system state backup. In addition note the
messages in the client error log. following:
v On Windows 2003 systems you must also apply the
VSS rollup package KB940349 prior to performing
FMV5283E The operation was unsuccessful.
the Ssystem state restore.
Explanation: None. v On Windows Vista you must apply the same service
System action: Processing stopped. pack that was installed at the time of backup prior to
performing the system state restore.
User response: See the user response based on other
messages in the client error log.
FMV5286I The VSS Instant Restore operation was
successful but some existing VSS
FMV5284I Tivoli Storage Manager has detected an snapshots have been deleted by the VSS
incomplete setup! The client options file provider.
'dsm.opt' was not found, while the
system options file 'file-path' exists! The Explanation: A successful VSS Instant Restore
wizard will guide you through the operation was performed for snapshot volumes that
configuration process of the initial basic were in a dependent relationship. In order for the
TSM client options files replacing your restore process to succeed, it was necessary to remove
current option file. Would you like to the snapshot volumes causing the dependency. Those
continue? snapshot volumes typically represent newer snapshot
backups. This forced TSM to remove the backups that
Explanation: Tivoli Storage Manager has detected an included the deleted snapshots. This situation is typical
incomplete setup. The user options file, dsm.opt, was when using SAN Volume Controller (SVC)
not found. Additionally, a system options file, dsm.sys, space-efficient volumes that have multiple snapshots.
was found. To complete the configuration the
configuration wizard will create dsm.opt and replace System action: Processing continues.
dsm.sys with minimal settings. User response: None.
System action: Tivoli Storage Manager may stop
User response: If the current version of dsm.sys is FMV5287W VSS restore operation will be performed
needed, rename the file and restart Tivoli Storage using VSS Fast Restore because the XIV
Manager. If the current version is not needed, select yes VSS Hardware Provider is at level 2.2.2.
and allow Tivoli Storage Manager to replace the file. Explanation: The IBM XIV VSS Hardware Provider
2.2.2 has issues with VSS Instant Restore. Please update

486 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5288W • FMV5302E

the XIV VSS Hardware Provider to version 2.2.3, or

FMV5299E A Flashcopy association exists between
later.
source volume: and a different target
System action: Processing continues. volume: .

User response: Update XIV VSS Hardware Provider to Explanation: A Flashcopy association exists between
version 2.2.3, or later. the source volume and a target other than the
designated target volume.

FMV5288W Test flag DISCARDZEROFILEDATA System action: Restore command will fail.
enabled. Discarding data for zero length
User response: Please withdraw the Flashcopy
object file-name
association between the source volume and the target
Explanation: During the restore of a zero length file or volume and retry the restore command.
directory, data was decompressed. This data could be
Extended Attributes, Alternate Streams, or ACL data.
FMV5300E Error detected in specified file list 'file
By default this data is restored. Because the
list name' during processing of line line
DISCARDZEROFILEDATA test flag is set the data is
number: found an invalid external object
discarded.
ID / inode number / inode generation number
System action: The data is discarded and processing / restore order number / alias entry: 'invalid
continues entry'. Invalid line: 'invalid entry'

User response: Note the file or directory name in this Explanation: File list parsing failed because of an
message and determine if the discarded data needs to invalid entry.
be reset through some other means.
System action: The operation aborted because of an
file list error.
FMV5296I The virtual machine 'vm-name' contains
User response: Correct the invalid file list entry and
one or more virtual disks that are of
restart the operation.
type Thick Eager Zero. Creating disks of
this type can take a long time. This
restore operation might time out before FMV5301E Error detected in specified file list 'file
the disks are ready. list name' during processing of line line
number: found an invalid ordering of
Explanation: Restoring a VM that has Thick Eager
external object IDs. ext. object ID of
Zero virtual disks can take a long time to complete
previous file: previous external object ID
because the disks are zero-filled to obscure any
ext. object ID of current file: current
previous content. The time that is required to provision
external object ID
a Thick Eager Zero disk depends on processing loads
on the VMware resources (vCenter and datastores). Explanation: File list parsing failed because of an
invalid ordering of the external object IDs.
System action: None
System action: The operation aborted because of an
User response: Reattempt the restore operation at a
file list error.
time when the processing load is light on the
datacenter and vCenter resources User response: Correct the invalid file list ordering
and restart the operation.
FMV5298E A Flashcopy background copy is in
progress between source volume: and FMV5302E File list stream error to file 'file list name'
target volume: . detected during processing of line line
number.
Explanation: A Flashcopy background copy from a
previous operation is not complete for the given source Explanation: File list processing failed because of an
and target volumes. stream error.
System action: Command will fail. System action: The operation aborted because of an
file list stream error.
User response: Please wait until the background copy
is complete and retry the command. User response: Check the specified file list and restart
the operation.

Chapter 6. FMV messages 487

FMV5837W • FMV5845E

the Windows system32 directory. When you can run

FMV5837W 'object name': attribute 'attribute name'
the utility independently of Tivoli Storage Manager,
could not be restored.
retry the operation. If the problem persists, contact the
Explanation: The listed attribute could not be restored support.
during processing on the Active Directory object.
System action: Processing continues to process all FMV5842E 'tombstone-name': object class violation.
other Active Directory objects per user's request.
Explanation: Object class error violation occurred
User response: None. during tombstone reanimation. This can happen if the
Active Directory schema was modified and is no longer
compatible with the tombstone.
FMV5838E The utility dsamain.exe does not exist
on the system. You cannot perform the System action: Processing continues to process all
operation unless Tivoli Storage Manager other objects per user's request.
can launch this utility.
User response: Recreate the failing object manually or
Explanation: You attempted to launch dsamain.exe, restore it from a backup.
but the utility does not exist.
System action: Processing stopped. FMV5843E Object class violation.
User response: Verify that the dsamain.exe utility Explanation: Object class error violation occurred
exists in the Windows system32 directory. When you during tombstone reanimation. This can happen if the
can run the utility independently of Tivoli Storage Active Directory schema was modified and is no longer
Manager, retry the operation. compatible with the tombstone.
System action: Processing continues to process all
FMV5839E The Active Directory object specification other objects per user's request.
is not allowed.
User response: Recreate the failing object manually or
Explanation: You attempted to restore the domain restore it from a backup.
object (starting with "DC="), or you attempted to
restore all objects ("name=*"), or you did not specify
FMV5844E Unable to update password.
anything.
Explanation: An error occurred during the password
System action: Processing stops.
update attempt.
User response: Modify the specification then retry the
System action: The password is not updated on the
operation.
server.
User response: Try to update the password again.
FMV5840E The current user is not a member of the
Administrators group, and cannot
perform this function. FMV5845E Unable to update password because the
maximum number of update attempts
Explanation: You must be a member of the
has been exceeded.
Administrators group to perform the Active Directory
objects function. Explanation: This message is issued after making 3
unsuccessful attempts to update the password. The
System action: Processing stops.
original password for the node was entered incorrectly;
User response: Log on with a user who is a member the new password does not meet the length or valid
of the Administrators group or add this user to the character requirements for our passwords; or there was
Administrators group then retry the operation. a mismatch between the first and second times the new
password was entered.
FMV5841E Active Directory database could not be System action: The password is not updated.
opened.
User response:
Explanation: An error occurred while opening the v Make sure the original password is entered correctly.
restored Active Directory database. Contact your Tivoli Storage Manager administrator
System action: Processing stopped. for further assistance if you do not know the original
password.
User response: Make sure ntdsutil.exe utility is
v Make sure the new password meets the password
located in the same directory with Tivoli Storage
length and character requirements.
Manager client executables. If it doesn't exist, reinstall
the client. Verify that the dsamain.exe utility exists in

490 IBM Tivoli Storage FlashCopy Manager: Messages

FMV5837W • FMV5845E

the Windows system32 directory. When you can run

FMV5837W 'object name': attribute 'attribute name'
the utility independently of Tivoli Storage Manager,
could not be restored.
retry the operation. If the problem persists, contact the
Explanation: The listed attribute could not be restored support.
during processing on the Active Directory object.
System action: Processing continues to process all FMV5842E 'tombstone-name': object class violation.
other Active Directory objects per user's request.
Explanation: Object class error violation occurred
User response: None. during tombstone reanimation. This can happen if the
Active Directory schema was modified and is no longer
compatible with the tombstone.
FMV5838E The utility dsamain.exe does not exist
on the system. You cannot perform the System action: Processing continues to process all
operation unless Tivoli Storage Manager other objects per user's request.
can launch this utility.
User response: Recreate the failing object manually or
Explanation: You attempted to launch dsamain.exe, restore it from a backup.
but the utility does not exist.
System action: Processing stopped. FMV5843E Object class violation.
User response: Verify that the dsamain.exe utility Explanation: Object class error violation occurred
exists in the Windows system32 directory. When you during tombstone reanimation. This can happen if the
can run the utility independently of Tivoli Storage Active Directory schema was modified and is no longer
Manager, retry the operation. compatible with the tombstone.
System action: Processing continues to process all
FMV5839E The Active Directory object specification other objects per user's request.
is not allowed.
User response: Recreate the failing object manually or
Explanation: You attempted to restore the domain restore it from a backup.
object (starting with "DC="), or you attempted to
restore all objects ("name=*"), or you did not specify
FMV5844E Unable to update password.
anything.
Explanation: An error occurred during the password
System action: Processing stops.
update attempt.
User response: Modify the specification then retry the
System action: The password is not updated on the
operation.
server.
User response: Try to update the password again.
FMV5840E The current user is not a member of the
Administrators group, and cannot
perform this function. FMV5845E Unable to update password because the
maximum number of update attempts
Explanation: You must be a member of the
has been exceeded.
Administrators group to perform the Active Directory
objects function. Explanation: This message is issued after making 3
unsuccessful attempts to update the password. The
System action: Processing stops.
original password for the node was entered incorrectly;
User response: Log on with a user who is a member the new password does not meet the length or valid
of the Administrators group or add this user to the character requirements for our passwords; or there was
Administrators group then retry the operation. a mismatch between the first and second times the new
password was entered.
FMV5841E Active Directory database could not be System action: The password is not updated.
opened.
User response:
Explanation: An error occurred while opening the v Make sure the original password is entered correctly.
restored Active Directory database. Contact your Tivoli Storage Manager administrator
System action: Processing stopped. for further assistance if you do not know the original
password.
User response: Make sure ntdsutil.exe utility is
v Make sure the new password meets the password
located in the same directory with Tivoli Storage
length and character requirements.
Manager client executables. If it doesn't exist, reinstall
the client. Verify that the dsamain.exe utility exists in

490 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV5876I • FMV7500W

v You will be prompted to enter the new password Manager administrator for further assistance.
two times, so make sure it is entered correctly both
times.
FMV7422E Unsupported action 'action' in schedule
'schedule name'.
FMV5876I SET EVENT Activate Retention
Explanation: The scheduled action is unknown to the
completed
current version of the IBM Tivoli Storage Manager
Explanation: The Data Retention ACTIVATE client and cannot be performed by means of a
transaction has completed. schedule. The most likely cause is that the scheduled
action requires a later version of the backup-archive
System action: Tivoli Storage Manager activated the
client. The unsupported action is displayed as a
objects that were selected.
number because the text description is not available.
User response: Continue with normal operations. Scheduled actions and their corresponding action
number can be found by searching for this message on
the IBM Tivoli Storage Manager support site.
FMV5877I SET EVENT Hold completed
System action: The scheduled action is not performed
Explanation: The Data Retention HOLD transaction or queried.
has completed.
User response: Search the IBM Tivoli Storage Manager
System action: Tivoli Storage Manager held the support site for this message to find information about
objects that were selected. scheduled actions, their corresponding action numbers
User response: Continue with normal operations. and the client version at which the action is supported.
Then upgrade your IBM Tivoli Storage Manager client
to a version that supports running this action as a
FMV5878I SET EVENT Release completed scheduled event. Until the client is upgraded, you can
Explanation: The Data Retention RELEASE transaction run the action manually if your version of the client
has completed. supports it.

System action: Tivoli Storage Manager released the

objects that were selected. FMV7423E Use Set Access backup <vmname>
-TYPE=VM for VMware backup file
User response: Continue with normal operations. spaces. Use of the long form fs-name is
not allowed.
FMV6001S NULL character found in the name of Explanation: You have chosen to set access using the
folder/file filename. long-form VM file space name. This name format is not
Explanation: A NULL character was found in the platform independent and requires special processing.
name of a file or folder. Some products place a NULL Use the -TYPE=VM option and supply only the VM
character in a file name so that the file is sorted name.
alphabetically to the top of a list. Tivoli Storage System action: The set access command is not
Manager cannot backup/restore such files. processed.
System action: Tivoli Storage Manager cannot User response: Enter the set access command using
complete the requested operation. the -TYPE=VM option and the short form of the VM
User response: Remove the NULL character by file space name which is simply the VM name.
renaming the file or folder.
FMV7500W Object 'object-name' could not be bound
FMV7421W The archive attribute for file filename to management class 'mgmt-specified'
cannot be reset. The return code from specified in an 'option' statement.
Windows API function Explanation: The management class specified in an
SetFileAttributes() is rc. include statement was not valid. If the include
Explanation: The client was unable to reset the statement is an "INCLUDE.SIZE" statement the
archive attribute for the file indicated in the message. warning message will be issued if an appropriate
This error is due to an error received from the copygroup is defined for the management class. For
Windows API function SetFileAttributes(). example, this warning will be issued on a backup
operation if no backup copygroup is defined for the
System action: processing stops. management class or this message will be issued on an
archive operation if no archive copygroup is defined
User response: Try the operation again. If the problem
for the management class.
persists, it may be indicative of a problem with the file.
Contact your system administrator or Tivoli Storage System action: The management class on the include

Chapter 6. FMV messages 491

FMV7501E • FMV7510E

statement is ignored and processing continues.

FMV7506W Invalid label entry
User response: Contact the Tivoli Storage Manager
Explanation: An invalid entry is entered on the Label
administrator to correct the appropriate copygroup
field.
definition on the Tivoli Storage Manager Server.
System action: Tivoli Storage Manager prompts you
to enter a valid volume label.
FMV7501E An invalid host address was received.
Host address is too long. User response: Enter a valid volume label or see your
system administrator for correct syntax.
Explanation: An invalid host parameter was found in
the HTTP Request. The parameter is too long. The
maximum length for a host address is 64 characters. FMV7507W The node name entry is invalid. Please
try again.
System action: Tivoli Storage Manager returns HTTP
error code 400 Bad Request. Explanation: An invalid entry is entered on the Node
Name field.
User response: Use a host machine with a
valid/shorter host address. System action: Tivoli Storage Manager prompts you
to enter a valid node name.
FMV7502E An invalid filename was received. User response: Enter a valid node name or see your
Filename is too long. system administrator for the correct syntax.
Explanation: A filename passed to the dsmcad service
is too long and thus invalid. FMV7508W Duplicate authorization
System action: Tivoli Storage Manager returns HTTP Explanation: The authorization rule entered by the
error code 400 Bad Request. user is already defined. Duplicate rules are not allowed.
User response: Retry connecting to dsmcad but use a System action: Tivoli Storage Manager allows you to
valid/shorter filename. enter a different rule.
User response: Enter an authorization rule that has
FMV7503W Invalid drive entry not been defined yet or cancel defining authorization
rules.
Explanation: An invalid entry is entered on the Drive
field.
FMV7509W Drive and/or volume label do not exist
System action: Tivoli Storage Manager prompts you
to enter a valid drive letter. Explanation: Either the drive or the volume label or
both do not match the existing ones. Rules must be
User response: Enter a valid drive letter or see your
defined on existing drives and volumes.
system administrator for the correct syntax.
System action: Tivoli Storage Manager prompts you
to reenter drives and/or volumes or cancel defining
FMV7504W Invalid directory entry
authorization rules.
Explanation: An invalid entry is entered on the
User response: Enter an existing drive and volume to
Directory field.
define the desire rule.
System action: Tivoli Storage Manager prompts you
to enter a valid directory.
FMV7510E A NAS node cannot be used for this
User response: Enter a valid directory or see your operation.
system administrator for the correct syntax.
Explanation: NAS nodes cannot be used for
operations like Access Another Node.
FMV7505W Invalid filename entry
System action: Tivoli Storage Manager prompts you
Explanation: An invalid entry is entered on the to enter a valid node name.
Filename field.
User response: Enter a valid, non-NAS, Tivoli Storage
System action: Tivoli Storage Manager prompts you Manager node name.
to enter a valid file name.
User response: Enter a valid file name or see your
system administrator for the correct syntax.

492 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV7522E • FMV7529E

FMV7522E Environment variable name is not set. FMV7527E The (-SNAPSHOTROOT) option is not
valid in conjunction with num-specs file
Explanation: Required environment variable as
specifications.
indicated in the message is not set for Tivoli Storage
Manager processes. Explanation: The (-SNAPSHOTROOT) option must be
used in conjunction with only one file specification. It
System action: Processing stops.
cannot be used with zero file specification (e.g., an
User response: Set the environment variable and INCREMENTAL command with no file specifications)
restart Tivoli Storage Manager processes then retry the or with more than one file specification.
operation.
System action: Processing stopped.
User response: See the appropriate Using the
FMV7523E The hardware type number is not known
Backup-Archive Client book for your operating system
to Tivoli Storage Manager.
for correct use of the named option.
Explanation: Due to a configuration or internal error,
underlying snapshot hardware type is not set correctly.
FMV7528W The (-SNAPSHOTROOT) option is not
System action: Processing stops. valid in conjunction with the Logical
Volume Snapshot Agent. Processing will
User response: Check your configuration and error continue without the use of the Logical
log file for more information. If unresolved, contact Volume Snapshot Agent.
your Tivoli Storage Manager administrator for help.
Explanation: The (-SNAPSHOTROOT) option is
incompatible with the Logical Volume Snapshot Agent.
FMV7524E SSL is required. The Logical Volume Snapshot Agent provides a
Explanation: SSL is required to protect the client comprehensive snapshot solution without having to use
password during authentication. the (-SNAPSHOTROOT) option. It is strongly
recommended that the snapshot capabilities provided
System action: Processing terminates. by the Logical Volume Snapshot Agent be used instead
User response: Enable SSL communication or set of using the (-SNAPSHOTROOT) option. Processing
SSLREQUIRED to NO. continues without the use of the Logical Volume
Snapshot Agent.

FMV7525E SSL is required by server. System action: Processing continues without the use
of the Logical Volume Snapshot Agent.
Explanation: SSL is required to protect the client
password during authentication. User response: See the appropriate Using the
Backup-Archive Client book for your operating system
System action: Processing terminates. for correct use of the named option.
User response: Enable SSL communication or contact
your Tivoli Storage Manager server administrator. FMV7529E The specified SNAPSHOTROOT
'obj-name' is not valid for the BACKUP
FMV7526E The SNAPSHOTROOT option is not IMAGE command.
valid with either of the following Explanation: When you use the (-SNAPSHOTROOT)
options: -GROUPNAME and option with the BACKUP IMAGE command,
-VIRTUALFSNAME. SNAPSHOTROOT must specify the device name of the
Explanation: The SNAPSHOTROOT option is logical volume containing the snapshot for the backup.
incompatible with the -GROUPNAME and An example is /dev/fslv01 (on Unix) or
-VIRTUALFSNAME options and cannot be used with \\?\GLOBALROOT\Device\
either one of those options. HarddiskVolumeShadowCopy1 (on Windows).

System action: Processing stops. With BACKUP IMAGE, SNAPSHOTROOT cannot be

used unless SNAPSHOTPROVIDERIMAGE has one of
User response: For information about backup-archive the following values in effect:
client processing options, see IBM Tivoli Storage v VSS
Manager Backup-archive Clients Installation and User's
Guide. v JFS2
System action: Processing is stopped.
User response: For the correct use of the
(-SNAPSHOTROOT) option, see the appropriate
Backup-Archive Client Installation and User's Guide book
for your operating system.

Chapter 6. FMV messages 493

FMV7530E • FMV7544E

FMV7530E The snapshot_volume_name cannot end FMV7534W Initialization functions cannot open
with a directory delimiter. /dev/tty special file. errno = errno-value,
error message
Explanation: The snapshot_volume_name cannot end
with a directory delimiter. This name should specify Explanation: Special file /dev/tty, required by
the root of a logical volume, e.g., /snapshot, x:, command line internal editor could not be opened
\\machine\x$, SNAP_VOL:, etc. during initialization. The system set the error code
errno-value.
System action: Processing stopped.
System action: Processing continues as if EDITOR
User response: See the appropriate Using the
option was set to NO.
Backup-Archive Client book for your operating system
for correct use of the named option. User response: Check your terminal settings.

FMV7531E The (-SNAPSHOTROOT) option is FMV7535W Command line internal editor can not
invalid when processing the NetWare be initialized.
NDS or Server Specific Information.
Explanation: EDITOR option is set to YES in the
Explanation: The (-SNAPSHOTROOT) option is only options file, but command line internal editor can not
intended with NetWare file server volumes and is not be started.
compatible with processing the NDS or Server Specific
System action: Processing continues as if EDITOR
Information on NetWare.
option was set to NO
System action: Processing stopped.
User response: Check previous messages to determine
User response: See the appropriate Using the the reason why the internal editor could not be started.
Backup-Archive Client book for your operating system
for correct use of the named option.
FMV7543E Error: Scout is not available for object
query. Either scout is not running or the
FMV7532E The logical file system specified with initial file system scan has not finished.
the (-SNAPSHOTROOT) option cannot
Explanation: The scout daemon must be running for
be a remote NetWare file system.
the reconcile process to do a query for all migrated
Explanation: The (-SNAPSHOTROOT) option is only files. If the scout daemon is not running or the initial
intended with local NetWare file server volumes and is file system scan has not finished you cannot run the
not compatible with remote NetWare volumes. reconcile tool in orphan check mode.
System action: Processing stopped. System action: Processing stops.
User response: See the appropriate Using the User response: Ensure that the scout daemon is
Backup-Archive Client book for your operating system running. If the scout daemon is not running, restart it
for correct use of the named option. and retry the command. If the scout daemon is
running, wait until it finishes the initial file system
scan. You can check the current status of the scout
FMV7533E The specified file system 'obj-name' does
daemon by using the dsmscoutd scanplan command.
not exist or is not local.
Explanation: When you use the (-SNAPSHOTROOT)
FMV7544E ICC routine icc-routine failed with the
option, the target and source file systems must be valid,
following error: "error-string".
local file systems. The file systems cannot be non-local,
such as a remote NetWare drive, a remote Windows Explanation: There was an error within ICC
drive, or an NFS mount. The (-SNAPSHOTROOT) cryptography library while processing the data. For
option is valid for local operations only. example, this problem can occur when encrypted client
data is corrupted, so the restore operation cannot
System action: Processing is stopped.
correctly decrypt it. This message reports an error code
User response: For the correct use of the and problem description which can be used by Tivoli
(-SNAPSHOTROOT) option, see the appropriate Storage Manager technical support personnel to
Backup-Archive Client Installation and User's Guide book determine the cause of the failure.
for your operating system.
System action: The processing stops.
User response: Ensure Tivoli Storage Manager
software is installed correctly. If needed, reinstall the
software. Make sure you use the correct encryption key
password for the data. Make sure there are no Tivoli

494 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV7545E • FMV7555E

Storage Manager server or network problems that may

FMV7551E The source path cannot contain a drive
affect the transfer of data. If the problem still exists,
letter
contact Tivoli Storage Manager technical support.
Explanation: The entered path cannot contain a drive
letter.
FMV7545E Unexpected error while encrypting the
data. System action: Tivoli Storage Manager did not
continue with the requested operation.
Explanation: There was an error while encrypting the
data. See the error log for more information. User response: Enter the source path in the correct
format.
System action: The object is not backed up.
User response: Ensure Tivoli Storage Manager
FMV7552I timestamp ***** Processed count files
software is installed correctly. If needed, reinstall the
*****
software. Retry the operation. If the problem still exists,
contact Tivoli Storage Manager technical support. Explanation: IBM Tivoli Storage Manager has
processed the specified number of files.
FMV7546E Unexpected error while decrypting the System action: Processing continues.
data.
User response: None.
Explanation: There was an error while decrypting the
data. See the error log for more information. This can
FMV7553W Disabled demand migration (ENOSPC)
happen if the encrypted data has been corrupted while
on file system file-system-name because of
in storage, during the network transfer, or both.
high threshold, low threshold, and
System action: The object is not restored. pmpercentage settings.
User response: Ensure Tivoli Storage Manager Explanation: The settings of high threshold = 100, low
software is installed correctly. If needed, reinstall the threshold = 100, and pmpercentage = 0 are reserved to
software. Make sure there are no Tivoli Storage disable demand migration and automigration. Used for
Manager server or network problems that may affect GPFS driven migration.
the transfer of data. Retry the operation. If the problem
System action: Processing continues.
still exists, contact Tivoli Storage Manager technical
support. User response: None.

FMV7547E Unexpected error while digesting the FMV7554E provider option is required if
data. HSMBACKENDMODE is set to
TSMFREE.
Explanation: There was an error while digesting the
data. See the error log for more information. Explanation: You need to specify provider option for
every operation with dsmmigrate.
System action: The object is not backed up.
System action: The operation stopped.
User response: Ensure Tivoli Storage Manager
software is installed correctly. If needed, reinstall the User response: Specify the provider option value for
software. Retry the operation. If the problem still exists, the operation.
contact Tivoli Storage Manager technical support.

FMV7555E The destination path must contain a

FMV7550E The absolute option requires using the drive letter
CreateNewBase=yes option when
performing a snapshot differential Explanation: The entered path must begin with a
backup. drive letter, colon, and root slash.

Explanation: The absolute option specified does not System action: Tivoli Storage Manager did not
have any effect when performing a snapshot continue with the requested operation.
differential backup. User response: Enter the destination path in the
System action: Processing stopped. correct format.

User response: Try to use the CreateNewBase=yes

option when performing a snapshot differential backup.

Chapter 6. FMV messages 495

FMV7556E • FMV7641I

FMV7556E An invalid drive letter was entered FMV7561E Drive drive-name is unavailable
Explanation: You entered an invalid drive letter. Explanation: In an attempt to process a file, the
specified drive-name was found unavailable.
System action: Tivoli Storage Manager prompts you
for the correct drive ID. System action: Tivoli Storage Manager did not process
the file.
User response: Reenter the drive ID in the correct
format. User response: Determine why the drive was not
available, make it ready, and retry the operation.
FMV7557E invalid provider.
FMV7564E Backup or archive of drives with
Explanation: You need to specify a valid provider for
duplicate volume labels is not allowed.
every operation with dsmmigrate.
Explanation: You tried to back up or archive a drive
System action: The operation stopped.
that has a duplicate volume label. Because Tivoli
User response: Specify a valid provider option value Storage Manager uses the volume label to keep track of
for the operation. backup or archive information, it cannot back up or
archive files from a drive with a duplicate volume
label.
FMV7558E target option is required if
HSMBACKENDMODE is set to System action: Tivoli Storage Manager cannot select
TSMFREE. the drive for backup or archive operations.

Explanation: You need to specify target option for User response: If the volume needs to be available to
every operation with dsmmigrate. the system, exit Tivoli Storage Manager and assign a
unique volume label to the drive. Restart Tivoli Storage
System action: The operation stopped. Manager and try the operation again.
User response: Specify the target option value for the
operation. FMV7566E Unable to load external library: reason
Explanation: There is no valid library in hsm/bin
FMV7559E The absolute option requires specifying directory.
the NoJournal option when performing
a Journal Based Backup for backing up System action: The operation stopped.
fs .
User response: Copy a valid external library to
Explanation: The absolute option specified does not hsm/bin directory.
have any effect when performing journal based
backups.
FMV7567E program-name:External recall failed!
System action: Incremental backup is performed. Reason:
User response: Verify that the file spaces specified are Explanation: There is no valid library in hsm/bin
not associated with journal based backup. If the directory.
-nojournal option is also specified, then this message
System action: The operation stopped.
will not appear.
User response: Copy a valid external library to
hsm/bin directory.
FMV7560E Drive drive-name has no volume label.
Backup/Archive not allowed.
FMV7641I The user does not have administrative
Explanation: The specified drive-name selected cannot
credentials to perform a full system
be backed up.
state backup.
System action: Tivoli Storage Manager rejected the
Explanation: The user account used to perform system
selected drive.
state backup including ASR Writer data must be a
User response: If the drive is a floppy drive, place a member of the Administrators group.
disk with a volume label in it and retry the operation.
System action: System state backup skips ASR Writer
If the disk is a hard drive, ensure the drive has a
data.
volume label, and retry the operation.
User response: Log on with a user who is a member
of the Administrators group or add this user to the
Administrators group. Then try the system state
backup again.

496 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV7642E • FMV7901W

FMV7642E An error occurred creating the registry FMV7701E The specified directory cannot be
directory structure. created.
Explanation: An error occurred while creating the Explanation: The directory contains invalid characters,
directory structure to save or replace a registry key. or you are not authorized to create the directory.
System action: Registry function fails. System action: The directory selection dialog remains
open so that you can specify another directory name.
User response: Ensure that the user account that is
running the backup of the registry has the proper User response: Specify another directory name.
authority. If the user account has the proper authority, Ensure that the directory contains valid characters and
you might need to restart the machine. There might be that you have proper authorization to create the
operations that are pending which have a file or files in directory.
the registry directory structure locked.
FMV7709E Restore operation failed. Not all files
FMV7643E The deployment manager detected that were restored.
the client is being upgraded to an
Explanation: Restore operation failed due to an error.
incorrect architecture - from 32 bit to 64
bit or from 64 bit to 32 bit. System action: Operation completed.
Explanation: When upgrading clients to releases lower User response: Check the error log for more details.
than 6.3, deployment manager allows upgrades to like
architecture only.
FMV7899E The client referenced a deduplicated
System action: Processing stops. extent that does not exist on the Tivoli
Storage Manager server
User response: Uninstall the client and install the
Backup-Archive client at the correct bitness level. Explanation: The deduplicated extent has been
deleted from the server during the backup or archive
operation. If you are using deduplication cache, it
FMV7650E The user does not have sufficient
might be out of synch with the Tivoli Storage Manager
privileges to execute IBM Tivoli Storage
server.
Manager.
System action: The processing stops.
Explanation: The user account used to execute IBM
Tivoli Storage Manager must have the "Back up files User response: Retry the operation. If the problem
and directories" and the "Restore files and directories" persists, turn off deduplication and retry the operation.
security settings assigned.
System action: Processing stops. FMV7900W Deduplication cache has been reset
because it is not synchronized with the
User response: Assign the "Back up files and
Tivoli Storage Manager server
directories" and the "Restore files and directories"
security settings to the account using the Windows Explanation: The deduplication cache contains
Local Security Settings tool or use a different user-id to deduplicated extent entries that do not exist on the
execute IBM Tivoli Storage Manager. Tivoli Storage Manager server. This occurs when the
extents are deleted from the Tivoli Storage Manager
server after they were recorded in the deduplication
FMV7660E An error occurred replacing one or more
cache.
registry keys.
System action: The deduplication cache is reset, and
Explanation: The registry key or keys being replaced
all cache entries are removed. The processing continues.
are exclusively held by another process. The registry
keys were previously restored but the system was not User response: None
restarted.
System action: processing stops. FMV7901W Client deduplication and option-name are
mutually exclusive.
User response: Restart the system and try the restore
operation again. Explanation: The following features cannot be used
with deduplication: lan-free, subfile, NAS,
useTsmBuffers.
System action: Client deduplication is disabled.
User response: Review the configuration. Do not

Chapter 6. FMV messages 497

FMV7902I • FMV7913E

configure deduplication with the lan-free, subfile, NAS,

FMV7906W The current storage pool ran out of
or useTsmBuffers features.
space, data will be stored into the next
pool - deduplication is disabled.
FMV7902I Client deduplication cache is full. Cache
Explanation: The current storage pool on the Tivoli
is reset.
Storage Manager server is out of space. Data will be
Explanation: The number of entries cached in the stored in the next storage pool. Deduplication is
client deduplication cache has exceeded the configured disabled and the transaction is being resent.
size for the cache.
System action: Deduplication is disabled to allow the
System action: The deduplication feature is designed backup to complete.
so that this happens periodically. The cache is reset to
User response: Contact your system administrator to
no entries.
add volumes to the current storage pool.
User response: You can reconfigure the client
deduplication cache size to a larger value to reduce the
FMV7907W Connection to repository repos-name
frequency of resets.
failed. Retrying with repos2-name.
Explanation: Unable to connect to the Fastback DR
FMV7903W Client deduplication cache is locked by
Hub repository. Retry using Fastback server repository.
another process.
System action: Retry operation.
Explanation: Another process is using the client
deduplication cache. Only one process may use it at a User response: Specify a vaild repository.
time.
System action: This process does not use the client FMV7908E Unable to mount FastBack snapshot
deduplication cache. The server deduplication is not policy 'Policy' client 'Client' volume
changed. 'Volume'. Reason: reason
User response: You can serialize processes using the Explanation: Tivoli Storage Manager Mount failed.
client deduplication cache. Or you can reconfigure the
System action: Tivoli Storage Manager cannot
current process to use a different cache path to avoid
continue processing.
contention.
User response:
FMV7904E Client deduplication and lan-free or
subfile backup are mutually exclusive. FMV7912E FastBackMount or FastBackShell is not
installed.
Explanation: Client deduplication and lan-free or
subfile are mutually exclusive. Explanation: Failure initializing FastBack environment.
FastBackShell or FastBackMount are not installed or are
System action: Client deduplication is disabled.
not located in the FastBack install directory.
User response: Review the configuration. Do not
System action: The FastBack operation cannot
configure deduplication with the lan-free or subfile
continue.
feature.
User response: Reinstall the software. The
FastBackShell and FastBackMount must be installed on
FMV7905L Client deduplication statistics. Total
the dedicated proxy computer.
Objects Deduplicated objectsDeduplicated
Total Bytes Inspected bytesInspected Total
Bytes Processed bytesProcessed FMV7913E The given branch was not found in the
Deduplicated Reduction Ratio DR Hub repository.
dedupReduction Total Reduction Ratio
totalReduction Explanation: The parameter to the required fbbranch
option is incorrect.
Explanation: Deduplication statistics for diagnostic
purposes. System action: The operation cannot continue.

System action: This message is for informational User response: Correct the parameter given for the
purposes only. fbbranch option.

User response: No action is required.

498 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV7914E • FMV7937E

FMV7914E Incremental backup of FastBack client FMV7918E Failure locating mounted volumes for
'vmname' failed with RC rc FastBack client 'vmname' volumes. Failed
with RC=rc
Explanation: The archive or incremental backup of
FastBack client volumes failed. Explanation: FastBack client volumes can not be
found. Volume mount points are not available on the
System action: The archive or backup of FastBack
backup proxy computer.
client finished with failures. The next FastBack client
will be processed. The reason for the failure is written System action: The backup of the FastBack client can
to the local client error log. not continue. The next FastBack client in the list will be
processed. The output of the FastBackMount command
User response: Check the local client error log for
will show the reason for the failure.
reason for the failure.
User response: Issue a fastbackshell mount add
command for the FastBack client volume to determine
FMV7915E Failure mounting FastBack client
the reason for the failure. Refer to the documentation
'vmname' with FastBack command. RC=rc
for that message for more information.
Explanation: The FastBackMount command failed to
mount a FastBack volume.
FMV7919E Password for Host host could not be
System action: The archive or backup of the FastBack read from encrypted password file.
volume can not continue. The next Volume in in line
Explanation: Use dsmc SET PASSWORD
will be processed. The output of the FastBackMount
-type=FastBack 'FastBack hostname' 'userid' 'password'
command will show the reason for the failure.
to save encrypted password
User response: Check the local client error log for the
System action: The backup cannot continue.
reason for the failure. Issue a FastBack command for
the FastBack volume to determine the reason for the User response: Use dsmc SET PASSWORD
failure. Refer to the documentation for that message for -type=FastBack 'FastBack hostname' 'userid' 'password'
more information. to save encrypted password

FMV7916E Failure initializing FastBack FMV7920E Invalid objName specification.

environment.RC=rc
Explanation: Tivoli Storage Manager invalid option
Explanation: Failure initializing FastBack environment. value specified.
Can not find FastBackShell.exe command. The
System action: Tivoli Storage Manager cannot
FastBackShell or FastBackMount is not installed or
continue processing.
FastBackShell.exe command is not located in the
FastBack install directory. User response: Enter correct user credentials using the
set password command with option: -type=fastback.
System action: The backup can not continue. The
Then try the failed command again.
output of the FastBack command will show the reason
for the failure.
FMV7936E objType objName not found in dump.
User response: Issue a FastBack command to
determine the reason for the failure. Refer to the Explanation: Tivoli Storage Manager server could not
documentation for that message for more information. find the object that is specified in the FastBack Dump
The FastBackShell and FastBackMount must be command..
installed on the backup proxy computer.
System action: Tivoli Storage Manager skips the
current object.
FMV7917E No FastBack snapshots found for input
policy, client and volume combination. User response: Ensure that there is at least one
snapshot for this FastBack volume, client, and policy.
Explanation: Failure processing fbClientName option. Ensure that a correct object is specified as input.
System action: The backup cannot continue.
FMV7937E No objType found in dump for input
User response: Check for errors in the FBClientName
objType1 objType2.
option value. Refer to the documentation for the
FBClientName option for more information. Explanation: Tivoli Storage Manager server found no
clients for the specified policy. Tivoli Storage Manager
server found no volumes for the specified FastBack
client.

Chapter 6. FMV messages 499

FMV7938E • FMV7948E

System action: Tivoli Storage Manager skips the

FMV7943E The combination of objName and
current object.
objName is invalid.
User response: Ensure that there is at least one
Explanation: The combination of options specified is
snapshot for this FastBack volume, client, and policy.
invalid.
Ensure that a correct object is specified as input.
System action:
FMV7938E Unable to dismount FastBack volume User response: Re-run the command with a
'volName'. RC = rc compatible set of options.
Explanation: Tivoli Storage Manager Dismount failed.
FMV7944W The number of FastBack clients
System action:
specified client is greater than the
User response: number of FastBack clients found client.
Explanation: One or more of the FastBack clients
FMV7939E Invalid FastBack volume specification. specified was not found. Look for message FMV7936E
specifying the client name.
Explanation: You must enter at least one FastBack
client with the "-fbclientname=" option before entering System action:
a FastBack volume name.
User response: Correct the names of the clients
System action: specified.

User response: When entering a FastBack volume

name, enter at least one FastBack client name using the FMV7945W The number of FastBack policies
"-fbclientname=" option. specified policy is greater than the
number of FastBack policies found
policy.
FMV7940W SUBDIR NO is not valid in this context.
SUBDIR will be forced to YES for Explanation: One or more of the FastBack policies
FastBack commands. specified was not found. Look for message FMV7936E
specifying the policy name.
Explanation: When using FastBack, SUBDIR is forced
to YES to ensure that the whole volume is processed. System action:

System action: SUBDIR is forced to YES. User response: Correct the names of the policies
specified.
User response: To avoid this message, do not use
SUBDIR NO with the command.
FMV7946E FastBack shell command timeout.SSH
Keys may not be configured for no
FMV7941E FastBack invalid repository name or password.
domain not set in password file entry
for hostname. Explanation: The FastBack shell command timeout.
SSH may not be configured properly.
Explanation: The FastBack repository name is invalid
or the domain has not been set in the password file System action:
when specifying the REP form of the repository.
User response: Correct SSH configuration.
System action:
User response: Issue the command dsmc set password FMV7947E The root user .ssh directory was not
server userid:domain password -type=fastback. found. SSH is not configured properly.
Explanation: SSH is not configured properly for the
FMV7942E Maximum number of FastBack objName root user.
objects exceeded.
System action:
Explanation: The maximum number of FastBack
User response: Correct SSH configuration.
objects shown in the message has been exceeded.
System action:
FMV7948E The public key for the FastBack server
User response: Re-run the command with no more was not found. SSH public keys are
than the maximum number of objects specified. configured properly.
Explanation: The SSH public keys are not configured
properly for the root user.

500 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV7949E • FMV8002I

System action:
FMV7955E The cygdrive-prefix is set incorrectly.
User response: Correct SSH configuration.
Explanation: Ensure that cygdrive-prefix is set to / in
the ssh cygwin environment. The command mount -s
FMV7949E The connection to FastBack server --change-cygdrive-prefix / can be use to set the drive
failed. prefix correctly.

Explanation: The connection to FastBack server failed. System action:

System action: User response: Correct the error.

User response: Insure that the FastBack server on the

target machine is runing properly. FMV7956E Unable to execute cygwin shell
commands. The cygwin environment
may be incorrectly
FMV7950E The FastBack server is not installed on
the target machine. Explanation: Use ssh to connect to the cygwin shell
and ensure that the cygwin environment and cygdrive
Explanation: The FastBack server is not installed on are configured correctly.
the target machine.
System action:
System action:
User response: Correct the error.
User response: Install the FastBack server on the
target machine or specify a different target machiner.
FMV7957E Unable discover the FastBackShell
location in the registry
FMV7951E The FastBackShell on the target machine
returned with the message errormsg . Explanation: Check that the FastBackShell was
installed on the Windows FastBack server machine.
Explanation: An error occurred with the command
issued to the FastBackShell on the target machine. System action:

System action: User response: Correct the error.

User response: Correct the options specified on the

commandr. FMV8000I Server command: 'command'.
Explanation: The specified command is being sent to
FMV7952E The package package required for the server. This message is displayed when the
FastBack support is not installed. command is generated from a macro or when the client
is running in batch mode.
Explanation: The required package is not installed.
System action: The command is sent to the server for
System action: processing.
User response: Install and configure the required User response: None.
package.

FMV8001I Return code return code value.

FMV7953E The FastBack shell scripts returned an
unexpected error error. Explanation: The error code shown has been returned
from the preceding server command. This message is
Explanation: The FastBack shell scripts returned an preceded by a server message explaining the reason for
unexpected error. the error code.
System action: System action: None.
User response: Correct the error. User response: None.

FMV7954E The SSH connection failed. The SSH FMV8002I Highest return code was return code
daemon may not be started or value.
configured on the target machine
Explanation: At exit from the client, the highest return
Explanation: Ensure that the SSH daemon is code encountered during the session is displayed.
configured correctly.
System action: This value is used as the program exit
System action: code.
User response: Correct the error. User response: None.

Chapter 6. FMV messages 501

FMV8003I • FMV8011W

FMV8003I Process number process ID started. FMV8008W Redirection inside macro whose output
is redirected is ignored.
Explanation: As a result of the preceding server
command, the process whose ID is shown starts to Explanation: An output redirection symbol has been
execute the command. The process can be monitored encountered inside a macro. However, the output of the
using the QUERY PROCESS command. macro itself (or a higher level macro) is already being
redirected.
System action: None.
System action: The redirection request is ignored.
User response: None.
User response: None.
FMV8004W Your password will expire within
daysRemaining day(s). FMV8009E Exiting due to command or option
errors.
Explanation: The password for this id is about to
expire. Explanation: Because of errors in command line or
option file parameters displayed earlier, the
System action: Logging on to the TSM Server will not
administrative client session is ending.
be prevented, however, the id will be locked out once it
expires. System action: The client exits.
User response: Change the password or contact your User response: Fix the option file parameter in error
Tivoli Storage Manager administrator to get the and restart the client, or restart the client with proper
password updated. command line parameters.

FMV8005E Java Applet failed to load. Please ensure FMV8010E An attempt to backup or archive a file
that the Java Java version Plugin has been has exceed the maximum number of
installed for this browser. retries.
Explanation: Java Plugin is missing from browser. Explanation: After five unsuccessful attempts to
Since plugin is not present, applet is not able to load. backup or archive a file, the client will no longer
attempt to send the file to the server.
System action: Applet unable to load and message
displayed. System action: File skipped.
User response: Install appropriate plugin for browser User response: Check the console or schedule log for
in order to use web client. additional information. Retry the operation at a later
time.
FMV8006E Unable to generate an acceptable
password. FMV8011W Rejected server-initiated session with
LDAP authentication from peer name.
Explanation: An error occurred during a password
update attempt using a generated password. Explanation: For security, the client will not accept
server-initiated sessions from servers that use LDAP
System action: The password is not updated on the
authentication.
server.
System action: The client-server session is not opened,
User response: Contact your Tivoli Storage Manager
and the schedule is not executed. The scheduler
administrator.
continues to wait for contact by a server that uses
LOCAL authentication.
FMV8007E The user is not authorized to perform
User response: If the client system is supposed to
LDAP authentication.
accept scheduled events from the prompting Tivoli
Explanation: Your node uses LDAP authentication. Storage Manager server, either ask the Tivoli Storage
Your PASSWORDACCESS option is set to GENERATE Manager server administrator to configure your node
but the current user cannot access the stored password to use LOCAL authentication, or do not use
to perform authentication. server-initiated sessions. If the client system is not
supposed to accept scheduled events from the
System action: The operation is stopped. prompting server, ask the Tivoli Storage Manager
User response: Run Tivoli Storage Manager client as server administrator to remove the client node name
root user or set PASSWORDACCESS to PROMPT. from the schedule on the prompting server.

502 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8012E • FMV8021E

User response: Reissue the command with a shorter

FMV8012E Option processing storage exhausted.
parameter.
Explanation: During processing of the client options
file, the client runs out of memory.
FMV8017E Command line parameter parameter
System action: The client session is ended. number: 'parameter' is not valid.
User response: Make more memory available and Explanation: The command line parameter shown is
restart the administrative client. not a valid administrative client parameter.
System action: The administrative client session is
FMV8013I Invalid encryption key password ended.
Explanation: The key you entered does not match the User response: Reissue the command with valid
key that was used to encrypt the file during backup. parameters.
The file can not be restored unless the matching key is
entered.
FMV8018E Administrative command not valid in
System action: User is prompted for encryption key Console mode.
password.
Explanation: The Console Mode option has been
User response: Enter the correct encryption key specified but the client encounters what appears to be a
password. server command on the command line.
System action: The administrative client session is
FMV8014E Insufficient information to connect to ended.
host.
User response: Reissue the command with no server
Explanation: The client options file or command line, command.
or both, do not contain enough communications
information to successfully connect to the server
FMV8019E Id and password must be supplied in
system. For example, with TCP/IP both the TCPPort
Batch mode.
number and TCPServer address are required to make a
connection. Explanation: A server command has been encountered
on the command line, but no administrator ID or
System action: The administrative client session is
password, or both, are specified.
ended.
System action: The administrative client session is
User response: Determine what information is needed
ended.
to establish a connection for your communications
method and then specify all that information in your User response: Reissue the command and include the
client options file or on the administrative client -ID and -PASSWORD parameters on the command line.
command line.

FMV8020E Unable to open file 'file spec' for output.

FMV8015E File 'file spec', error code error code from
options processing. Explanation: The file name specified in the -OUTFILE
option cannot be opened.
Explanation: An unknown error code is returned from
the routine that processes the client options file. System action: The -OUTFILE parameter is ignored.

System action: The administrative client session is User response: Allow processing to continue or exit
ended. the session and correct the file name.

User response: Attempt to determine the error and

correct it. If the problem persists, contact your service FMV8021E Exiting Batch mode session due to
representative. output file error.
Explanation: The file specified in the -OUTFILE
FMV8016E Command line parameter parameter parameter cannot be opened for a session running in
number: 'parameter' is too long. Batch mode.

Explanation: The specified command line parameter System action: The administrative client session is
exceeds the maximum length for a command line ended.
parameter. User response: Reissue the command with a valid
System action: The administrative client session is output file name or make space available for the output
ended. file.

Chapter 6. FMV messages 503

FMV8022E • FMV8032E

FMV8022E Output will be written only to stdout. FMV8027E Unterminated comment in command.
Explanation: The file specified in the -OUTFILE Explanation: An input command contains an opening
parameter cannot be opened, so output is written only comment mark but no closing comment mark.
to the standard output stream.
System action: The input command is ignored.
System action: Output that would have been written
User response: Reissue the command with matching
to the output file is written to the standard output
comment marks.
stream.
User response: Allow processing to continue or exit
FMV8028E Command longer than maximum of max
the session and correct the file name.
length characters.
Explanation: An input command longer than the
FMV8023E Unable to establish session with server.
maximum command length allowed has been entered.
Explanation: The administrative client cannot start a
System action: The input command is ignored.
session with the requested server. This message is
preceded by another message that explains the reason User response: Reissue the command with fewer
for the error. characters. This could mean replacing series of
repeating blanks with a single blank.
System action: The administrative client session is
ended.
FMV8029E Macro processing terminated.
User response: Attempt to correct the error. If the
problem persists, contact your service representative. Explanation: An error occurs during processing of a
macro because the -ITEMCOMMIT option is not
specified on the command line. Processing of this
FMV8024E End of macro after continued command
macro and any higher level macro is terminated.
line.
System action: All current macro processing ends.
Explanation: A macro containing a continuation line
has been executed, but no more lines are found in the User response: Specify the -ITEMCOMMIT option on
macro file. the command line to ensure that the server commits
each command in the macro individually.
System action: The continued command is ignored,
and an error return code is set for the macro.
FMV8030E Substituted command longer than
User response: Correct the macro in error.
maximum of max length characters.
Explanation: After variable substitution, an input
FMV8025E I/O Error reading command input.
command is longer than the maximum command
Explanation: The client is unable to read an input length allowed.
command from the terminal.
System action: The input command is ignored.
System action: The administrative client session is
User response: Reissue the command with fewer
ended.
characters. This may require replacing a series of
User response: Correct the problem on the terminal repeating blanks with a single blank.
and retry the administrative session.
FMV8031E Missing name of macro to execute.
FMV8026E Input line longer than maximum of max
Explanation: A macro command is encountered that
length characters. Use continuation.
does not contain a macro name.
Explanation: An input command line is longer than
System action: The command is ignored.
the maximum input line length allowed.
User response: Reissue the macro command with a
System action: The input command is ignored.
macro file name.
User response: Reissue the command with several
lines using continuation characters.
FMV8032E Could not allocate storage to process
macro 'file spec'.
Explanation: The client cannot allocate enough
memory to process the macro shown.
System action: The macro is ignored and an error is
returned.

504 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8033E • FMV8047E

User response: Make more memory available to the

FMV8038E Unable to open file 'file spec' for
client and retry the macro command.
redirection.
Explanation: A command has been entered that
FMV8033E LDAP authentication is not supported
specifies an output redirection file, but the file cannot
by Web client.
be opened.
Explanation: The id you entered uses LDAP
System action: The command is ignored and an error
authentication. LDAP authentication is not supported
is returned.
by Web client.
User response: Reissue the command with a valid
System action: Login is unsuccessful.
output file name or make space available for the output
User response: Use an id with LOCAL authentication. file.

FMV8034E Your administrator ID is not recognized FMV8041E The server connection has been lost and
by this server. cannot be re-established.

Explanation: The administrator ID entered is not Explanation: During an administrative session, the
known to the requested server. client discovers that the connection with the server has
been severed; an attempt to reestablish the connection
System action: The administrative session terminates. fails.
User response: Ensure that you are using a registered System action: The client session is ended.
administrative ID for the server to which you are
connecting. User response: Determine the cause of the failure;
then try to restart the session at a later time. If the
problem persists, contact your service representative.
FMV8035E Interrupted by user.
Explanation: During an administrative session, a FMV8045E Communications error.
keyboard interrupt or break sequence is entered.
Explanation: An unexpected communications error
System action: The administrative session is occurs during an administrative session.
terminated.
System action: The client session is ended.
User response: Restart the administrative client
session. User response: Verify that communications are active
between the client and server machines. Server outages,
processor outages, and communication controller
FMV8036E Administrative command not valid in outages can cause this error.
Mount mode.
Explanation: The Mount Mode option has been FMV8046E The client connection with the server
specified but the client encounters what appears to be a has ended due to an unexpected error.
server command on the command line.
Explanation: The Tivoli Storage Manager error log
System action: The administrative client session is might contain other messages related to this error.
ended.
System action: The client session ends.
User response: Reissue the command with no server
command. User response: Check the communication link
between the client and server to ensure that it is
operational. Examine the client error log for additional
FMV8037E Missing name for redirection file. messages related to this error.
Explanation: A command is entered that contains an
output redirection symbol but no output file name. FMV8047E The client connection with the server
System action: The command is ignored and an error has ended due to a communications
is returned. buffer overflow.

User response: Reissue the command with an output Explanation: The Tivoli Storage Manager error log
file name. might contain other messages related to this error.
System action: The client session ends.
User response: Try the operation again. Check the
communication link between the client and server to
ensure that it is operational. Examine the client error

Chapter 6. FMV messages 505

FMV8048W • FMV8055E

log for additional messages related to this error. administrator if you do not know the correct port
number.
FMV8048W Warning! Performing image restore of
the Linux file system 'src' to an alternate FMV8051E User is not authorized to get prompted
destination 'dest' is not recommended as for encryption key
this may result in duplicate UUIDs
Explanation: The current passwordaccess option
leading to failed mounts after a
setting and user authority do not allow encryption.
successful restore.
System action: You are not prompted to set the
Explanation: Performing an image restore of a Linux
encryption key password.
file system to an alternate destination may result in
duplicate UUID leading to failed mounts after a User response: Request the Tivoli Storage Manager
successful restore. On Linux, some file systems use authorized user to set passwordaccess=GENERATE in
UUID to identify themselves. If you took an image dsm.sys and set the encryption key password. (The
backup of such volume and restored it to a different encryption key password is set the first time that the
location, you will have two volumes with the same Tivoli Storage Manager authorized user backs up a
UUID. If you use UUID to define your file systems in file).
/etc/fstab, be aware that TSM may be unable to mount
the restored file system correctly. To avoid such
situation, restore the image to its original location. FMV8052E Unable to decrypt file 'filespace
namepath-namefile-name' ....Please try to
System action: Processing continues. restore this file individually
User response: If it is not possible or not desirable to Explanation: File could not be decrypted and restored.
avoid performing an image restore to an alternate
destination, change the UUID of either the original or System action: File is not restored.
restored volume. Refer to your Linux documentation User response: Restore the file separately.
for instructions on how to do this. You may also need
to edit your /etc/fstab manually to allow the original,
the restored or both volumes to mount. FMV8053E The network cannot be accessed.
Explanation: The Tivoli Storage Manager error log
FMV8049E A connection with the server cannot be might contain other messages related to this error.
established due to a communications System action: The client session ends.
time-out.
User response: Check the communication link
Explanation: The Tivoli Storage Manager error log between the client and server to ensure it is
might contain other messages related to this error. operational. Examine the client error log for additional
System action: The client session ends. messages related to this error. Try the operation again.

User response: Check the communication link

between the client and server to ensure that it is FMV8054E No memory available to service request.
operational. Examine the client error log for additional Explanation: Sufficient server memory is not available.
messages related to this error.
System action: The client session is ended.

FMV8050E The Tivoli Storage Manager server is User response: Retry the administrative session. If the
not accepting administrative sessions on problem persists, contact your service representative.
the client port. You must use the port
number designated for administrative FMV8055E The server has insufficient resources to
sessions. perform the operation.
Explanation: The Tivoli Storage Manager server is Explanation: The server ran out of resources. A lack of
configured to not allow administrative sessions on the storage or other problem condition does not allow any
client TCP/IP port. A different port number has been new activity. The server activity log might contain
designated for use by administrative sessions. additional information about this problem.
System action: The administrative session is not System action: The client session ends.
established.
User response: The Tivoli Storage Manager
User response: Use the TCPADMINPORT client administrator should examine the Tivoli Storage
option to specify the TCP/IP port number that the Manager server activity log to determine the source of
Tivoli Storage Manager server uses for administrative the resource constraints. Try the operation again when
sessions. See your Tivoli Storage Manager server the server is under less load.

506 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8056E • FMV8064E

FMV8056E Your administrator ID is locked. FMV8061E Session Rejected: The server does not
allow a signon as a Unicode enabled
Explanation: The administrative ID entered has been
administrative client
locked by a system administrator and cannot be used.
Explanation: The administrative client is unable to
System action: The client session is ended.
establish a connection to the server because of a
User response: Contact your system administrator to unicode enabling mismatch between server and client.
unlock your ID.
System action: The client session is ended.
User response: Register a new administrator from a
FMV8057E The requested language files are not
different administrative client or the server console, and
available.
signon with the new administrator ID.
Explanation: The NLS repository for the language
specified is not available.
FMV8062E Client-to-Client communication is not
System action: The client session is ended. allowed to take place when Tivoli
Storage Manager Server authentication
User response: Use a different language or obtain a is turned off.
copy of the NLS repository for the language desired.
Explanation: Client-to-Client communication requires
Tivoli Storage Manager Authentication to be enabled.
FMV8058E The specified path is a Linux Btrfs
subvolume and is not valid for image System action: Processing stops.
backup.
User response: Turn Tivoli Storage Manager Server
Explanation: Linux Btrfs subvolumes are not authentication on using the Set AUthentication ON
supported for image backup. command.

System action: The image backup operation is not

performed. FMV8063E The remote Tivoli Storage Manager
Client Acceptor associated with Node
User response: Try the operation again using a valid 'name' could not authenticate with the
Linux Btrfs file system. Tivoli Storage Manager Server.
Explanation: Some Tivoli Storage Manager Client
FMV8059E The TCP/IP functions have not been operations require the Backup/Archive Client to
linked into this module. contact Clients on remote machines. The remote
Explanation: The ADSM TSO administrative client machine in question cannot authenticate with the Tivoli
cannot find the TCP/IP functions required to support Storage Manager Server.
TCP/IP communications. System action: Processing stops.
System action: The connection to the server fails. User response: On the remote machine, create a new
User response: The TCP/IP functions must be Tivoli Storage Manager password for the Client
included in the DSMADMC/FMVADM module. Refer Acceptor or verify that the current password is still
to the Program Directory for this product for valid before retrying the operation.
instructions on how to include the TCP/IP functions in
the DSMADMC/FMVADM module. FMV8064E Communication timeout. Reissue the
command.
FMV8060E Error validating file 'VHDX file name' Explanation: The connection to the server is ended
Explanation: Tivoli Storage Manager cannot locate the because of a communication timeout from the server.
file or the file format is not valid. System action: The server does not process the
System action: The backup operation does not start. command.

User response: Try the operation again. If the problem User response: Reissue the command. If necessary,
continues, check the error log file for information about increase the values of IDLETIMEOUT and
how to resolve this issue. COMMTIMEOUT options in the server options file.

Chapter 6. FMV messages 507

FMV8103W • FMV8501E

FMV8103W A command was not successful. FMV8201E Windows Hyper-V incremental backups
command : command Tivoli Storage require Windows 2012 or later.
Manager function name : function-name
Explanation: Tivoli Storage Manager can only perform
error output : error-output return code :
incremental backups of Windows Hyper-V on Windows
return code Tivoli Storage Manager file :
operating systems of Windows Server 2012 and later.
file-name (line-number)
Incremental backups may not be performed on
Explanation: Tivoli Storage Manager client called an previous versions of Windows.
external program that failed.
System action: The incremental backup will not occur.
System action: Depending on the circumstances, the
User response: To access incremental backups for
failure may or may not prevent further processing.
Windows Hyper-V upgrade the operating system to
User response: See addition information in the error Windows Server 2012 or later. Alternatively, Periodic
log. Use the information provided in this message for Full - Full backups are available for previous versions
troubleshooting or when talking with Tivoli Storage of Windows.
Manager support.
FMV8500I User action cannot be completed due to
FMV8104W Cannot determine EFS status of the file the following error:
system 'file-system name', errno='errnor
Explanation: An error has occurred while processing
number', processing data normally.
your requested action, user action. The message
Explanation: IBM Tivoli Storage Manager cannot displaying with this message identifies the error.
determine EFS status on the specified filesystem. No
System action: The system does not process your
EFS specific processing will take place for files on this
requested action.
filesystem. If EFS is indeed enabled on the filesystem,
all accessaible files will be backedup in cleartext. User response: See Explanation for the message
displaying with FMV8000I.
System action: The filesystem will be processed as a
regular filesystem.
FMV8501E Internal error in this graphical user
User response: Contact your system administrator to
interface. Try one of the following in
determine the cause of the error reported in the
the order listed: 1) close this window
message.
and reopen it 2) close this object and
reopen it 3) shut down this graphical
FMV8105W Unable to remove snapshot for volume user interface and restart it 4) save
'filespace-name'. dsmerror.log residing in the directory
specified by DSMG_LOG and contact
Explanation: Tivoli Storage Manager client was unable
your service representative for
to remove the snapshot used for image backup.
assistance.|Graphical User Interface -
System action: Processing continues. Internal error

User response: See additional information in the error Explanation: An internal processing error has
log. Use lvdisplay command to view the active occurred in the Tivoli Storage Manager Administrator’s
snapshots and lvremove command to remove the graphical user interface while processing your
snapshot manually. requested action. Message FMV8000I, which displays
with this message, identifies your requested action.

FMV8106E Support for multiple IBM Tivoli Storage System action: The system does not process your
Manager servers is enabled on this requested action.
node. The server name must be
User response:
specified for this command.
v Close the window in which your failed request was
Explanation: When a node is enabled to support made and reopen it.
multiple IBM Tivoli Storage Manager servers, the
v If this problem persists, close all windows associated
command must specify a valid IBM Tivoli Storage
with the object toward which your failed request was
Manager server name.
directed and reopen them.
System action: Processing stopped. v If this problem persists, shut down the Tivoli Storage
User response: Specify a valid server name for this Manager Administrator’s graphical user interface
command. and restart it.
v If this problem persists, save the dsmerror.log file
residing in the directory specified by the
environment variable DSMG_LOG or in the current

508 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8502S • FMV8510W

directory if DSMG_LOG is not specified, and contact System action: The watch daemon will now check the
your service representative for assistance. node.
User response: None.
FMV8502S Due to this error, processing cannot
continue. This graphical user interface
FMV8506I program: node hostname with id node-id
will shut down.
was removed from the Responsiveness
Explanation: A severe error has occurred. The Service.
message displaying with this message identifies the
Explanation: The remote node has shut down and
actual error.
was removed from the Responsiveness Service after
System action: The Tivoli Storage Manager some time.
Administrator’s graphical user interface closes.
System action: The watch daemon will not look for
User response: this node until it is up again.
v Restart the Tivoli Storage Manager Administrator’s User response: None.
graphical user interface.
v If this problem persists, save the dsmerror.log file
FMV8507I program: node hostname with id node-id is
residing in the directory specified by the
now online.
environment variable DSMG_LOG or in the current
directory if DSMG_LOG is not specified, and contact Explanation: The remote node has successfully joined
your service representative for assistance. our Responsiveness Service and it's availability is now
checked.
FMV8503I No matching option found for pattern: System action: The watch daemon will now check the
'pattern'. availability of the node.
Explanation: You specified a pattern which does not User response: None.
match the name of any supported option.
System action: This message is the only response to FMV8508I program: node hostname with id node-id is
your query. now offline.
User response: Specify a different pattern or omit the Explanation: The node has successfully left the
pattern to display all options. Responsiveness Service because it was shut down
normally.
FMV8504E A message related to this window or System action: The watch daemon will not check the
your requested action cannot be node again.
displayed due to an internal error in
this graphical user interface. Refresh User response: None.
this window or request the action again.
Explanation: An internal processing error has FMV8509I program: node hostname with id node-id is
occurred in the Tivoli Storage Manager Administrator’s now recovered.
graphical user interface while attempting to display an Explanation: The node has recovered from a previous
informational, warning, or error message related to the failure situation and a rollback can now be initiated.
current window or your requested action.
System action: The watch daemon will now check the
System action: The system may or may not process node for availability.
your requested action.
User response: None.
User response: View the Activity Log window in the
Server object to find out if your requested action has
completed. If it has completed successfully, refresh the FMV8510W program: node hostname with id node-id
current window to show its results. If it has not has failed, checking if failover is
completed successfully, make your request again. required.
Explanation: The node is not responding to the
FMV8505I program: node hostname with id node-id Responsiveness Service anymore, a failover will be
was added to the Responsiveness initiated if the remote and current node have failover
Service. enabled and if the remote watch daemon's filesystem
timestamp is too old.
Explanation: The remote node is running and has
failover enabled. The node is now marked as offline System action: The watch daemon will check if a
until it has successfully joined the Service. failover for any of the node's filesystems is required.

Chapter 6. FMV messages 509

FMV8511W • FMV8565W

User response: None. Responsiveness Service and will not be able to do

failover.
FMV8511W program: failover for node hostname with System action: The watch daemon is exiting and will
id node-id aborted, failover thread could be restarted to retry the operation.
not be started.
User response: None.
Explanation: The internal service thread to perform
the failover operation could not be started.
FMV8516E The values entered for the New
System action: The failover on this machine is Password and Reenter New Password
aborted. Another machine with failover enabled will fields do not match. Type the same
perform the failover. value into both fields.
User response: Please check if the machine has too Explanation: You have entered different values into
much load to start new threads. the New Password and Reenter New Password fields.
System action: The system does not process your
FMV8512W program: signal signal received, HSM requested action.
activities stopped on this node.
User response: Enter the same value into the New
Explanation: The node is failing voluntarily because of Password and Reenter New Password fields.
a local problem.
System action: Other nodes are informed to take over FMV8517W program: not trying to take over
the filesystems of the failing node. filesystems for node hostname with id
node-id since it has failover disabled.
User response: Examine the log files for possible
reasons and do a file system rollback after the Explanation: The node was detected as failing but no
computer is back online. failover will be initialized since the node is not
configured for failover.
FMV8513I program: this node is leaving the System action: No filesystem of the failing node will
Responsiveness Service voluntarily. be taken over.
Explanation: The node is shut down regularly and User response: Manually take over the filesystem if
will leave the Responsiveness Service without initiating required.
a failure notice to other nodes.
System action: The watch daemon will not check for FMV8518W program: Could not resolve cluster node
the node. id by hostname hostname.
User response: None. Explanation: The hostname provided by the
Responsiveness Service could not be resolved to a
cluster node id.
FMV8514E program: the Responsiveness Service on
this node could not be initialized. System action: The current operation aborts.
Failover will not be possible.
User response: Make sure the cluster is functional and
Explanation: It was not possible to initialize and start the machine hostnames are propperly set and
the internal thread for the Responsiveness Service. resolvable.
System action: The watch daemon is exiting and will
be restarted to retry the operation. FMV8563E Recall mode has an invalid value:
invalidValue.
User response: Verify that virtual memory (swap
space) has sufficient space. Verify that the system Explanation: The recall mode you try to enable on the
process thread limit is reasonable and has not been met system is not existing.
or exceeded. If the thread limit is reasonable, but has
System action: None.
been exceeded, or the problem otherwise persists,
reboot the GPFS cluster User response: Check the value of the recall option.

FMV8515E program: it was not possible to join the FMV8565W ProgramName: list of recall IDs not found
Responsiveness Service. Failover will in queue. These recalls are already
not work for this node. finished:
Explanation: The watch daemon could not join the Explanation: The program is not able to find the recall
IDs and is not able to delete these processes.

510 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8566E • FMV8781E

System action: None.

FMV8778E A browser program cannot be found or
User response: Check that recall IDs exist and are cannot be started. An error occurred
correct. executing the command. command Verify
that a browser is installed and works
correctly on your local machine.
FMV8566E You have not entered or selected a value
for this required field. Enter or select a Explanation: A browser program cannot be found, so
value for this field. it is not possible to access the IBM Tivoli Web site and
online documentation.
Explanation: You have not entered or selected a value
for a required field. System action: Tivoli Storage Manager continues to
process user requests.
System action: The system does not process your
requested action. User response: For the Windows platform, the default
system browser is used. Verify that a browser is
User response: Enter or select a valid value for this installed on your machine.
required field.

FMV8779E A browser program cannot be found or

FMV8776E The IBM Tivoli Enterprise Space cannot be started. One of the following
Management Console cannot be started. browsers is required: browser-list Verify
Java Runtime Environment version that one of these browsers is installed
version by company has been detected on and works correctly on your local
machine. A Java Runtime Environment machine.
version or higher is required to run this
program. If you have already installed Explanation: A browser program cannot be found, so
Java version on this machine, please it is not possible to access the IBM Tivoli Web site and
ensure that the correct Java executable is online documentation.
on your PATH, otherwise you can
System action: Tivoli Storage Manager continues to
download it from 'webAddress' and start
process user requests.
the program again.
User response: For UNIX platforms, a list of
Explanation: IBM Tivoli Enterprise Space Management
supported browsers is provided in the README.
Console cannot be started because the Java runtime
Install the required browser to access the IBM Tivoli
environment does not meet the requirements.
Web sites and online documentation.
System action: A confirmation dialog is displayed for
you to close the application, or to open a browser with
FMV8780E A browser program cannot be found or
a link to the Web site where you can download the
cannot be started. Check the 'file-name'
correct version of Java.
file on your local machine for more
User response: Verify that the correct java executable information.
is on your PATH or install the required version of Java
Explanation: A browser program cannot be found, so
runtime environment and start the program again.
it is not possible to access the Web site or online
documentation.
FMV8777E The IBM Tivoli Enterprise Space
System action: Tivoli Storage Manager continues to
Management Console cannot be started.
process user requests.
An error occurred trying to load Tivoli
look and feel. Verify that the product is User response: Install a browser to access the Web site
correctly installed. or online documentation.
Explanation: IBM Tivoli Enterprise Space Management
Console cannot be started because the library that FMV8781E The system could not log on to Tivoli
defines the Tivoli look and feel cannot be found. Storage Manager client node node-name
on machine-name. Make sure your data
System action: The IBM Tivoli Enterprise Space
and password are correct and that caps
Management Console shuts down.
lock key is not on. The Space
User response: Verify that the product is correctly Management Agent must be running at
installed. If IBM Tivoli Enterprise Space Management the specified port on the machine to
Console still cannot be started, contact your system which you are attempting to log on to.
administrator for further assistance.
Explanation: The system was not able to connect to
the specified client node.

Chapter 6. FMV messages 511

FMV8782E • FMV8785E

System action: Tivoli Storage Manager continues to the cause of the problem, then see your system
process user requests. administrator for further assistance.
User response: Verify that:
v the information provided to connect is correct FMV8784E An error occurred initializing the client
nodes table. Your local configuration file
v the machine is reachable in the network
'config-file' might be corrupted. Remove
v HSM is installed on the specified machine and a it from your installation directory and
Space Management Agent is running at the specified start the program again. Check also the
port. log-file file on your local machine for
more information.
FMV8782E An error occurred while loading file Explanation: The client nodes table cannot be
system information on 'fs-name'. Verify initialized.
that the Space Management agent is
running on the client node machine. System action: The IBM Tivoli Enterprise Space
Check also the local-log-file file in the Management Console shuts down.
installation directory of your local User response: It is possible that your local settings
machine and the $DSM_DIR/error-file file 'dsmsm.cfg' is corrupted. Try to remove it from
file on machine if present. If this does your installation directory and start the program again.
not identify the cause of the problem, Check the dsmsm.log file in the installation directory of
contact your system administrator your local machine and the $DSM_DIR/dsmerror.log
and/or Tivoli Storage Manager technical file on the client node machine if present. If this does
support for further assistance. not identify the cause of the problem, contact your
Explanation: An error occurred while loading file system administrator and/or Tivoli Storage Manager
system information on the selected client node technical support for further assistance.

System action: Disconnects the client node.

FMV8785E An error occurred disconnecting the
User response: Verify that the Space Management system from the client node 'node-name'.
agent is running on the client node machine. Check The Client node is being disconnected
also the dsmsm.log file in the installation directory of without deleting internal HsmSystem
your local machine and the $DSM_DIR/dsmerror.log objects. Verify that the Space
file on the client node machine if present. If this does Management agent is running on the
not identify the cause of the problem, contact your client node machine. Check also the
system administrator and/or Tivoli Storage Manager local-log-file file in the installation
technical support for further assistance. directory of your local machine and the
$DSM_DIR/error-file file on machine if
FMV8783E An error occurred loading file system present. If this does not identify the
properties of fsName required to show cause of the problem, contact your
space usage graphical information. system administrator and/or Tivoli
Verify that the Space Management agent Storage Manager technical support for
is running on the client node machine. further assistance.
Check also the local-log-file file in the Explanation: An error occurred disconnecting the
installation directory of your local system from the client node. It was not possible to
machine and the $DSM_DIR/error-file delete internal HsmSystem objects.
file on machine if present. If this does
not identify the cause of the problem, System action: The client node disconnected without
contact your system administrator deleting HsmSystem objects.
and/or Tivoli Storage Manager technical User response: Verify that the Space Management
support for further assistance. agent is running on the client node machine. Check the
Explanation: An error occurred while loading file dsmsm.log file in the installation directory of your local
system properties on the selected client node. machine and the $DSM_DIR/dsmerror.log file on the
client node machine if present. If this does not identify
System action: Continue to process other file system the cause of the problem, contact your system
properties. administrator and/or Tivoli Storage Manager technical
User response: Verify that the Space Management support for further assistance.
agent is running on the client node machine. Check
also the dsmsm.log file in the installation directory of
your local machine and the $DSM_DIR/dsmerror.log
file on the client node machine. If this does not identify

512 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8786E • FMV8790E

FMV8786E An error occurred loading file system FMV8788E An error occurred starting manually
information from the selected client threshold migration on file-system. Verify
node. Verify that the Space Management that the Space Management agent is
agent is running on the client node running on the client node machine.
machine. Check also the local-log-file file Check also the local-log-file file in the
in the installation directory of your local installation directory of your local
machine and the $DSM_DIR/error-file machine and the $DSM_DIR/error-file
file in the client node machine if file on machine if present. If this does
present. If this does not identify the not identify the cause of the problem,
cause of the problem, contact your contact your system administrator
system administrator and/or Tivoli and/or Tivoli Storage Manager technical
Storage Manager technical support for support for further assistance.
further assistance.
Explanation: An error occurred starting the manually
Explanation: An error occurred loading file system threshold migration on the selected client node.
information from the selected client node.
System action: Threshold migration is not started
System action: File System information is not loaded manually.
User response: Verify that the Space Management User response: Check the dsmsm.log file in the
agent is running on the client node machine. Check the installation directory of your local machine and the
dsmsm.log file in the installation directory of your local $DSM_DIR/dsmerror.log file on the client node
machine and the $DSM_DIR/dsmerror.log file on the machine if present. If this does not identify the cause of
client node machine if present. If this does not identify the problem, contact your system administrator and/or
the cause of the problem, contact your system Tivoli Storage Manager technical support for further
administrator and/or Tivoli Storage Manager technical assistance.
support for further assistance.
FMV8789E An error occurred trying to deactivate all
FMV8787E An error occurred loading file system managed file systems of client-node.
information from nodename client node. Check also the local-log-file file in the
The client node is being disconnected. installation directory of your local
Verify that the Space Management agent machine and the $DSM_DIR/error-file
is running on the client node machine. file on machine if present. If this does
Check also the local-log-file file in the not identify the cause of the problem,
installation directory of your local contact your system administrator
machine and the $DSM_DIR/error-file and/or Tivoli Storage Manager technical
file on machine if present. If this does support for further assistance.
not identify the cause of the problem,
Explanation: An error occurred trying to deactivate all
contact your system administrator
managed file systems of the selected client node.
and/or Tivoli Storage Manager technical
support for further assistance. System action: File systems are not deactivated.
Explanation: An error occurred loading file system User response: Check the dsmsm.log file in the
information from the selected client node. installation directory of your local machine and the
$DSM_DIR/dsmerror.log file on the client node
System action: The client node is disconnected
machine if present. If this does not identify the cause of
User response: Verify that the Space Management the problem, contact your system administrator and/or
agent is running on the client node machine. Check the Tivoli Storage Manager technical support for further
dsmsm.log file in the installation directory of your local assistance.
machine and the $DSM_DIR/dsmerror.log file on the
client node machine if present. If this does not identify
FMV8790E An error occurred trying to reactivate all
the cause of the problem, contact your system
managed file systems of client-node.
administrator and/or Tivoli Storage Manager technical
Check also the local-log-file file in the
support for further assistance.
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 Tivoli Storage Manager technical
support for further assistance.
Explanation: An error occurred trying to reactivate all

Chapter 6. FMV messages 513

FMV8791E • FMV8795E

managed file systems of the selected client node. Tivoli Storage Manager technical support for further
assistance.
System action: File systems are not reactivated.
User response: Check the dsmsm.log file in the
FMV8793E An error occurred trying to deactivate
installation directory of your local machine and the
file-system file system. Verify that the
$DSM_DIR/dsmerror.log file on the client node
Space Management agent is running on
machine if present. If this does not identify the cause of
the client node machine. Check also the
the problem, contact your system administrator and/or
local-log-file file in the installation
Tivoli Storage Manager technical support for further
directory of your local machine and the
assistance.
$DSM_DIR/error-file file on machine if
present. If this does not identify the
FMV8791E An error occurred trying to add space cause of the problem, contact your
management to fs-name file system. system administrator and/or Tivoli
Verify that the Space Management agent Storage Manager technical support for
is running on the client node machine. further assistance.
Check also the local-log-file file in the
Explanation: An error occurred trying to deactivate
installation directory of your local
the selected file system.
machine and the $DSM_DIR/error-file
file on machine if present. If this does System action: The selected file system is not
not identify the cause of the problem, deactivated.
contact your system administrator
User response: Check the dsmsm.log file in the
and/or Tivoli Storage Manager technical
installation directory of your local machine and the
support for further assistance.
$DSM_DIR/dsmerror.log file on the client node
Explanation: An error occurred trying to add space machine if present. If this does not identify the cause of
management to the selected file system. the problem, contact your system administrator and/or
Tivoli Storage Manager technical support for further
System action: Space management is not added to the
assistance.
selected file system.
User response: Check the dsmsm.log file in the
FMV8794E An error occurred trying to reactivate
installation directory of your local machine and the
file-system file system. Verify that the
$DSM_DIR/dsmerror.log file on the client node
Space Management agent is running on
machine if present. If this does not identify the cause of
the client node machine. Check also the
the problem, contact your system administrator and/or
local-log-file file in the installation
Tivoli Storage Manager technical support for further
directory of your local machine and the
assistance.
$DSM_DIR/error-file file on machine if
present. If this does not identify the
FMV8792E An error occurred trying to remove cause of the problem, contact your
space management from file-system file system administrator and/or Tivoli
system. Verify that the Space Storage Manager technical support for
Management agent is running on the further assistance.
client node machine. Check also the
Explanation: An error occurred trying to reactivate the
local-log-file file in the installation
selected file system.
directory of your local machine and the
$DSM_DIR/error-file file on machine if System action: The selected file system is not
present. If this does not identify the reactivated.
cause of the problem, contact your
User response: Check the dsmsm.log file in the
system administrator and/or Tivoli
installation directory of your local machine and the
Storage Manager technical support for
$DSM_DIR/dsmerror.log file on the client node
further assistance.
machine if present. If this does not identify the cause of
Explanation: An error occurred trying to remove the problem, contact your system administrator and/or
space management from the selected file system. Tivoli Storage Manager technical support for further
assistance.
System action: Space management is not removed
from the selected file system.
FMV8795E An error occurred trying to save your
User response: Check the dsmsm.log file in the
settings to config-file configuration file
installation directory of your local machine and the
on your local machine. Check the log-file
$DSM_DIR/dsmerror.log file on the client node
file in the installation directory of your
machine if present. If this does not identify the cause of
local machine for more information.
the problem, contact your system administrator and/or

514 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8809E • FMV8821E

Explanation: An error occurred trying to save your PIHDW to prevent the hardware plugin from being
settings to dsmsm.cfg configuration file on your local loaded.
machine.
System action: Customized GUI settings are not saved FMV8818E An error occurred trying to apply your
to the local machine changes. Your changes have not been
applied to the system. Contact your
User response: Check the dsmsm.log file in the
system administrator.
installation directory of your local machine and the
$DSM_DIR/dsmerror.log file on the client node Explanation: An error occurred trying to apply your
machine if present. If this does not identify the cause of changes.
the problem, contact your system administrator and/or
System action: User changes are not applied.
Tivoli Storage Manager technical support for further
assistance. User response: Contact your system administrator.

FMV8809E The LD_LIBRARY_PATH is either not FMV8819E The following trace flag(s) are not valid:
set or is set incorrectly. Ensure that the trace-flag-list. Correct them before
LD_LIBRARY_PATH environment continuing.
variable contains the installation
directory path name. Explanation: One or more of the trace flags are not
valid.
Explanation: The LD_LIBRARY_PATH must be set
and it must contain the installation directory path. System action: Prompts the user to correct the trace
flags.
System action: The VMware backup or restore
operation fails. User response: Correct the wrong trace flags.

User response: Set the LD_LIBRARY_PATH and

ensure that it contains the Backup/Archive client FMV8820E The HSM System Object was not found
installation directory. on the Space Management agent. The
error occurred when calling function:
function-name. The last operation was not
FMV8810E The LD_LIBRARY_PATH is either not processed correctly.
set or is set incorrectly. Ensure that the
LD_LIBRARY_PATH environment Explanation: The Space Management agent was
variable contains the installation unable to process a HSM System function, because the
directory. HSM System object was not found.

Explanation: The LD_LIBRARY_PATH must be set System action: The last operation is skipped.
and it must contain the installation directory path. User response: Reconnect to the Space Management
System action: The VMware backup or restore agent. If this does not solve the problem restart the
operation fails. Space Management agent.

User response: Set the LD_LIBRARY_PATH and

ensure that it contains the Backup/Archive client FMV8821E Unable to create requested HSM object
installation directory. on Space Management agent. The last
operation was not processed correctly.
The problem is caused from a memory
FMV8811E VMware operations can not be run problem. Try to free memory on the
when the hardware plugin product system where the Space Management
TIVsm-BAhdw is installed and loaded. agent is running. Or restart the Space
Please either uninstall the hardware Management agent.
product TIVsm-BAhdw, or set the
option DONTLOAD PIHDW in the Explanation: Space Management agent was not able to
options file to prevent the hardware create a requested HSM object because not enough free
plugin from being loaded. space was found on the system.

Explanation: VMware operations are incompatible System action: Last operation is skipped.
with the hardware plugin product libraries. User response: Try to free more memory on the
System action: The VMware backup or restore system where the Space Management agent is running,
operation fails. or restart the Space Management agent.

User response: Uninstall the hardware product

product TIVsm-BAhdw, or set the option DONTLOAD

Chapter 6. FMV messages 515

FMV8822E • FMV8829E

FMV8822E HSM File System Object was not found FMV8826E The Space Management API was unable
on Space Management agent. The error to query a HSM device. This error
occurred when calling function: occurs because the HSM kernel
function-name The last operation was not extension was not loaded correctly
processed correctly.
Explanation: Because of a wrong configuration HSM
Explanation: Space Management agent was not able to was not able the load the kernel extension. This causes
process a HSM File System function, because no HSM to fail the query for global activation of the HSM
File System object was found. system.
System action: Last operation is skipped. System action: Query for global HSM activation is
skipped.
User response: Reconnect to the Space Management
agent. If this does not solve the problem restart the User response: Check the configuration of the HSM
Space Management agent. system. If you can not find any problem in the
configuration contact Tivoli Storage Manager technical
support.
FMV8823E A Protocol error occurred in
communication with the Space
Management agent This error occurs FMV8827E The Space Management API was unable
when a session with the Space to locate global control block. The error
Management agent was lost, or network occurred in function : function-name
error caused synchronization problem
Explanation: Not defined exception caused this
between the Space Management console
internal error in the Space Management API.
and the agent.
System action: Load connection settings function is
Explanation: Space Management console and Space
skipped.
Management agent has different session and
transaction key in the communication header. User response: Contact Tivoli Storage Manager
technical support.
System action: Last operation is skipped.
User response: Restart Space Management console
FMV8828E The Space Management API lost the
and Space Management agent.
session with the server. This problem is
caused by a connection failure with the
FMV8824E A internal error occurred in the Space server. Check to see if your Space
Management agent. The error occurred Management Client machine has a
in function : function-name network connection to the Tivoli Storage
Manager server.
Explanation: Not defined exception caused a internal
error in the Space Management agent. Explanation: This error occurs when the Space
Management API has connection problems with the
System action: Last operation is skipped.
Tivoli Storage Manager server.
User response: Restart Space Management agent. If
System action: Session with server gets lost and
this does not solve the problem contact Tivoli Storage
server operation is skipped.
Manager technical support.
User response: Check the network connection with
Tivoli Storage Manager server machine. See the error
FMV8825E The Space Management API was unable
log file for additional information why the session gets
to locate option object The error
lost. Restart the Space Management Agent if the
occurred in function : function-name
connection re-established automatically.
Explanation: Not defined exception caused this
internal error in the Space Management API.
FMV8829E The Space Management API was unable
System action: Last operation is skipped. to initialize the HSM system. The error
is caused from a problem to initialize a
User response: Contact Tivoli Storage Manager DMAPI session.
technical support.
Explanation: This error is caused from a problem to
initialize a DMAPI session.
System action: The HSM system cannot be initialized
and the Space Management Console is ended.
User response: Try to restart Space Management

516 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8830W • FMV8836E

Agent. If this does not solve the problem, see the error
FMV8833E The Space Management API could not
log for additional information and contact Tivoli
retrieve Tivoli Storage Manager policy
Storage Manager technical support.
settings from the already loaded list.
Explanation: The Space Management API tried to get
FMV8830W Different server name stanzas
Tivoli Storage Manager policy settings from the
(HSM-stanza and BA-stanza) for
management list and failed for a unknown reason.
file-system-name file system for space
management and backup-archive. System action: Getting Tivoli Storage Manager policy
settings fails and policy information fields are not filled
Explanation: The server name stanzas you specified
up in the Space Management Console.
for the space management (HSM) client and the
backup-archive (BA) client are different. The inline User response: See the error log file for additional
backup and stub restore features will be unavailable for information.
the file system.
System action: Processing continues. FMV8834E The Space Management API was unable
to get file system information for file
User response: If you want to allow inline backup and
system : filesystem-name.
stub restore for the file system, the MIGRATESERVER
and DEFAULTSERVER options must specify the same Explanation: The Space Management API could not
SERVERNAME stanza in dsm.sys. You may also choose retrieve the file system information for a selected file
to supply a server stanza name using the system.
SERVERNAME option in dsm.opt or on the command
System action: Getting file system information fails
line. In either case the stanza name must match the
and information are not displayed in the Space
stanza specified in the MIGRATESERVER option.
Management Console.
User response: See the error log file for additional
FMV8831E The Space Management API could not
information.
find file system : function-name An
incorrect file system name was passed to
the Space Management API. Ensure that FMV8835E The Space Management API was unable
the file system that was selected in the to get file system status for file system :
file system list is still valid. Refresh the filesystem-name. System call to get file
file system view in the Space system status returned with error.
Management Console by pressing F5 on
your keyboard or select 'Refresh` under Explanation: The Space Management API could not
the View menu. retrieve the file system status for a selected file system.
The error is caused from a failed system call on the file
Explanation: The Space Management API could not system.
find the file system that was specified in the Space
Management Console. A reason could be that the file System action: Getting file system status fails and
system was unmounted and is not longer existing on information are not displayed in the Space
the system. Management Console.

System action: Getting file system information for the User response: See the error log file for additional
specified file system name is skipped. information.

User response: Update the file system list in the Space

Management Console by pressing F5 on your keyboard FMV8836E An object creation error occurred in the
or selecting 'Refresh' in the View menu. Space Management API The error
occurred in function : function-name. The
problem is caused from a memory
FMV8832E The Space Management API could not problem. Try to free memory on the
retrieve Tivoli Storage Manager policy system where the Space Management
settings from the server. agent is running. Or restart the Space
Management agent.
Explanation: The Space Management API tried to get
Tivoli Storage Manager policy settings from the server Explanation: Caused from a out of memory problem
and failed for a unknown reason. the Space Management API could not create a
requested object.
System action: Getting Tivoli Storage Manager policy
settings fails and policy information fields are not filled System action: The requested function fails and
up in the Space Management Console. cannot retrieve information to the Space Management
Console.
User response: See the error log file for additional
information.

Chapter 6. FMV messages 517

FMV8837E • FMV8843E

User response: Free more memory on the system User response: Correct the stub file size in the file
where the Space Management agent is running, or system properties dialog of the Space Management
restart the Space Management agent. Console.

FMV8837E The Space Management API was unable FMV8840E The maximum number of candidates
to get configuration data from managed that was specified for file system :
file system : filesystem-name. The filesystem-name is out of range. The
problem is caused from a error when maximum number of candidates value
reading dsmmigfs table entry. that was entered in the file system
properties dialog is out of range. Correct
Explanation: The Space Management API reads
the maximum number of candidates
information from dsmmigfs table to get HSM managed
value in the file system properties
files system configuration. This error occurs when the
dialog of the Space Management
API is unable to read an entry from this table.
Console.
System action: Getting HSM managed file system
Explanation: The maximum number of candidates
configuration fails and information is not displayed in
value that was specified is out of range for this file
the Space Management Console.
system.
User response: See the error log for additional
System action: Wrong maximum number of
information on errors occurring when reading entries
candidates value is not applied to the file system.
from the dsmmigfs table.
User response: Correct the maximum number of
candidates value in the file system properties dialog of
FMV8838E The Space Management API can not set
the Space Management Console.
HSM managed file system configuration
for file system : filesystem-name. The
configuration cannot be set because this FMV8841E The server name that was specified for
file system is NOT HSM managed. the file system : optfile-name is not valid.
Check to see if the managed file system Correct the server name value in the
that was selected in the file system list client node properties dialog of the
is still HSM managed. Refresh the file Space Management Console.
system view in the Space Management
Explanation: The server name that was specified is
Console by pressing F5 on your
not valid.
keyboard or select 'Refresh` under the
View menu. System action: Wrong server name value is not
applied to the system options file.
Explanation: The file system that you selected from
the file system list in the Space Management console is User response: Correct the server name value in the
not longer HSM managed and no configuration can bet client node properties dialog of the Space Management
set for it. A reason could be that the file system was Console.
unmanaged from a other user.
System action: Setting HSM managed file system FMV8842E The Space Management API was not
configuration fails. able to modify system options file :
optfile-name because of insufficient
User response: Update the file system list in the Space
privilege. Use root user to change HSM
Management Console by pressing F5 on your keyboard
managed file system configuration.
or selecting 'Refresh' in the View menu.
Explanation: User has no rights to modify system
options file.
FMV8839E A wrong stub file size was passed to the
Space Management API for file system : System action: Changes are not applied to the system
filesystem-name. The stub file size that options file.
was entered in the file system properties
dialog is not supported by this file User response: Run as root user to change HSM
system. Correct the stub file size value managed file system configuration.
in the file system properties dialog of
the Space Management Console. FMV8843E No correct include/exclude settings are
Explanation: The Stub file size that you has specified found in system options file :
is not supported by this file system. optfile-name. Correct the include/exclude
list in the system options file.
System action: Wrong stub file size is not applied to
the file system. Explanation: The include/exclude settings in the

518 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8844E • FMV8850E

system options file are not correct. information on why the lock on the SDR file fails.
System action: Changes are not applied to the system
options file. FMV8848E The Space Management API could not
open file system status file to retrieve
User response: Correct the include/exclude list in the
managed file system statistics for :
system options file.
filesystem-name. Reason could be
insufficient permissions or that the file
FMV8844E A incorrect preferred node or server does not exist. The managed file system
name was specified in the HSM statistics are not retrieved from the
configuration for filesystem-name. Correct HSM system.
the preferred node and server name
Explanation: The Space Management API could not
value in the HSM configuration.
retrieve managed file system information from file
Explanation: The Space Management API could not system status file. The error occurred when the API
change preferred node settings because a wrong value tries to open the file for reading.
was specified
System action: Managed file system statistics are not
System action: Changes are not applied to the system retrieved and information is not displayed in the Space
options file. Management Console.

User response: Correct the preferred node and server User response: See the error log file for additional
settings in Space Management Configuration. information on why opening the file system status file
fails.

FMV8845E A incorrect owner node or server name

was specified in the HSM configuration FMV8849E The Space Management API was not
for filesystem-name. Correct the owner able to load HSM managed file system
node and server name value in the HSM statistics for : filesystem-name. Check to
configuration. see if the managed file system that was
selected in the file system list is still
Explanation: The Space Management API could not HSM managed. Refresh the file system
change owner node settings because a wrong value was view in the Space Management Console
specified by pressing F5 on your keyboard or
System action: Changes are not applied to the system select 'Refresh` under the View menu.
options file. Explanation: The Space Management API could not
User response: Correct the owner node and server load managed file system statistics from selected file
settings in Space Management Configuration. system. The reason could be that the file system is not
longer HSM managed.

FMV8846E The Space Management API was not System action: Managed file system statistics are not
able to update the HSM managed file retrieved and information is not displayed in the Space
system : filesystem-name. Management Console.

Explanation: The Space Management API could not User response: Update the file system list in the Space
apply configuration changes to the HSM managed file Management Console by pressing F5 on your keyboard
system. or selecting 'Refresh' in the View menu.

System action: Changes are not applied to HSM

managed file system. FMV8850E The Space Management API was not
able to add HSM to file system :
User response: See error log file for additional filesystem-name. This error occurs because
information why the update of the file system fails. selected file system is not mounted. You
must mount the file system before you
FMV8847E The Space Management API was not can add HSM.
able to obtain a lock on SDR file for file Explanation: The Space Management API could not
system : filesystem-name. add HSM to a file system, because it is not mounted.
Explanation: The Space Management API could not System action: The add HSM operation fails and HSM
lock the SDR file for the file system. is not added to the selected file system.
System action: Changes are not applied to HSM User response: Mount the selected file system before
managed file system. adding HSM.
User response: See the error log file for additional

Chapter 6. FMV messages 519

FMV8851E • FMV8858E

FMV8851E The Space Management API was not FMV8855E The Space Management API was not
able to add HSM to file system : able to start automatic migration on the
filesystem-name. This error occurs because file system : filesystem-name.
selected file system is not supported to
Explanation: The Space Management API tries to start
add HSM.
automatic migration on a file system and fails for a
Explanation: The Space Management API could not unknown reason.
add HSM to a unsupported file system.
System action: The automatic migration is not started
System action: The add HSM operation fails and HSM for the file system.
is not added to the selected file system.
User response: See the error log file for additional
User response: Select a supported file system to add information and contact Tivoli Storage Manager
HSM. technical support.

FMV8852E The Space Management API was not FMV8856E The Space Management API was not
able to add HSM to file system : able to start reconciliation process on
filesystem-name. This error occurs because the file system : filesystem-name.
selected file system is already HSM
Explanation: The Space Management API tries to start
managed.
reconciliation process on a file system and fails for a
Explanation: The Space Management API attempt to unknown reason.
manage a already HSM managed file system.
System action: The reconciliation process is not
System action: The add HSM operation fails and the started for the file system.
selected file system stays HSM managed.
User response: See the error log file for additional
User response: Select a not managed file system to information, and contact Tivoli Storage Manager
add HSM. technical support.

FMV8853E The Space Management API was not FMV8857E The Space Management API was not
able to add HSM to file system : able to start scout process on the file
filesystem-name. system : filesystem-name.
Explanation: The Space Management API attempt to Explanation: The Space Management API tries to start
manage file system and fails for a unknown reason. scout process on a file system and fails for a unknown
reason.
System action: The add HSM operation fails and HSM
is not added to the selected file system. System action: The scout process is not started for the
file system.
User response: Retry the add HSM operation. If this
does not solve the problem, see the error log file for User response: See the error log file for additional
additional information and contact Tivoli Storage information, and contact Tivoli Storage Manager
Manager technical support. technical support.

FMV8854E The Space Management API was not FMV8858E The Space Management API was not
able to remove HSM from file system : able to migrate the file : file-name. The
filesystem-name. The error occurs when error occurred in function :
the Space Management API tries to lock function-name.
the SDR file and fails.
Explanation: The Space Management API tries to
Explanation: The Space Management API attempt to migrate a file and fails in the displayed API function.
unmanage (remove) file system and fails for a
System action: The selected file is not migrated to the
unknown reason.
server.
System action: The remove HSM operation fails and
User response: See the error log file for additional
HSM is not removed from the selected file system.
information.
User response: Try the remove HSM operation again.
If this does not solve the problem, see the error log file
for additional information and contact Tivoli Storage
Manager technical support.

520 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV8859E • FMV9010E

determined from a subsequent error message.

FMV8859E The Space Management API was not
able to recall the file : file-name. The
error occurred in function : FMV9007W program name: invalid 'parameter name'
function-name. value: value (must be in [minimum
value..maximum value]).
Explanation: The Space Management API tries to
recall a file and fails in the displayed API function. Explanation: The program found an invalid parameter
in the space management configuration of a filesystem.
System action: The selected file is not recalled from
the server. System action: The paramter value was rejected.
User response: See the error log file for additional User response: In case you tried to set the specified
information. value manually, choose a value from the specified
range instead. If the value is read from a file system's
space management configuration file (located at
FMV8939E An unexpected error occurred trying to
[fs]/.SpaceMan/hsmfsconfig.xml), edit the file
filter the directory tree. rc=return-code
accordingly. The name of the filesystem can be
Explanation: The filter was not applied to the determined from a subsequent error message.
directory tree.
System action: The directory tree is not filtered. FMV9008W Compression is enabled. Recall mode
for file file-name cannot be set to partial.
User response: Contact your system administrator for
further assistance. Explanation: Tivoli Storage Manager can only set file
attributes to a uncompressed migrated file. This file has
been migrated with compression enabled.
FMV8945E An unexpected error occurred analyzing
the directory tree. The list of files System action: Tivoli Storage Manager does not set
matching your search criteria is not the file attributes.
completed. rc=return-code
User response: Recall the file to state resident disable
Explanation: It was not possible to search all items compression and migrate the file again. Retry the
matching the search criteria on the directory tree due to operation.
an unexpected error.
System action: The search results table shows only the FMV9009E program name: found invalid space
items found until the error is occurred. management configuration for
'filesystem'.
User response: Contact your system administrator for
further assistance. Explanation: The program found an invalid space
management configuration for the given filesystem.
FMV8946E RPC call failed. System action: The space management configuration
was rejected for the given filesystem . When updating
Explanation: Unable to connect receiver recall
an existing configuration, invalid configurations to set
daemon.
are ignored. When a persistent configuration file is
System action: Processing stopped. invalid, the filesystem will appear to not have space
management enabled.
User response: System is not operating correctly or
recall daemons are not started. User response: In case you tried to update space
management for this filesystem manually, enter a valid
configuration instead. In case the persistent
FMV9005W program name: invalid 'parameter name' configuration file is invalid, edit the file accordingly;
value: value (must be in [minimum alternatively, you can add space management explicitly
value..maximum value]). (which will remove / overwrite the existing
Explanation: The program found an invalid parameter configuration). The reason for the configuration can be
in the space management configuration of a filesystem. determined from a preceding error message. The
filesystem's space management configuration file is
System action: The paramter value was rejected. located at 'filesystem'/.SpaceMan/hsmfsconfig.xml.
User response: In case you tried to set the specified
value manually, choose a value from the specified FMV9010E program name: could not parse space
range instead. If the value is read from a file system's management configuration file
space management configuration file (located at 'configuration file' for filesystem.
[fs]/.SpaceMan/hsmfsconfig.xml), edit the file
accordingly. The name of the filesystem can be Explanation: The space management configuration file

Chapter 6. FMV messages 521

FMV9011E • FMV9021E

for the given filesystem is present but its content

FMV9017W error-program: Minimum number of
appears to have invalid format.
recall daemons min-dsmrecalld cannot be
System action: The configuration was rejected. The greater than maximum number of recall
filesystem will appear to not have space management daemons max-dsmrecalld; defaulting to
enabled. minimum min-dsmrecalld and maximum
max-dsmrecalld.
User response: Check the given space management
configuration file; it is supposed to contain a Explanation: A minimum number of recall daemons
well-formed XML document with a root element has been entered that is greater than the maximum
named 'HsmFsConfig'. To create a new configuration number of recall daemons.
file, you can simply add space management to this
System action: Tivoli Storage Manager uses defaults
filesystem.
instead of the values specified in the client system
options file (dsm.sys).
FMV9011E program name: could not write space
User response: Correct the MINRECALLDAEMONS
management configuration file
and MAXRECALLDAEMONS options in the client
'configuration file' for filesystem.
system options file and retry the operation.
Explanation: IBM Tivoli Storage Manager could not
write and save the space management configuration file
FMV9018W program-name: option option value value
for the given filesystem.
invalid, range min-value to max-value.
System action: IBM Tivoli Storage Manager did not
Explanation: An invalid value has been entered. Value
save the space management configuration information.
should be in the range specified by the message.
If you tried to add space management for this
filesystem, it was not added. If you tried to update the System action: Tivoli Storage Manager uses defaults
space managment configuration, it was probably not instead of the value specified by the user.
updated. If an existing configuration file in old format
User response: Correct the invalid input value.
was read successfully, but could not be converted to
XML format, space management will be active for this
filesystem with the configuration from the old file. FMV9019W program-name: unable to parse option
value 'argument'
User response: Determine if there is any reason why
the given file cannot be written. Explanation: Input is incorrect or is not in correct
format.
FMV9012E error-program: Command must be run by System action: Tivoli Storage Manager continues.
root user.
User response: Retry operation with correct usage
Explanation: Tivoli Storage Manager requires that a syntax.
root user perform this operation.
System action: Tivoli Storage Manager terminates the FMV9020E Could not establish a session with a
operation. Tivoli Storage Manager server or client
agent. The Tivoli Storage Manager
User response: Change to root user, and then retry the
return code is tsm-error;.
operation.
Explanation: A communication error occured. The
return code is provided to help diagnose the problem.
FMV9016E Cannot get space management migration
status for path. System action: Processing stops.
Explanation: An error occurred while trying to get the User response: Check the Tivoli Storage Manager
space management migration status. Either the error log for communications failures such as TCP/IP,
permissions for the status file are not set correctly, or shared memory, or named pipe errors.
the status file is damaged.
System action: Tivoli Storage Manager terminates the FMV9021E error-program Unknown recall daemon
operation. (pid process-ID) terminated abnormally,
status: status.
User response: The root user should check the
permissions of the status file, or contact the service Explanation: A recall daemon stops abnormally.
representative.
System action: Tivoli Storage Manager terminates the
operation.
User response: Try the operation again. If the problem

522 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9022E • FMV9034E

persists, send the core file to IBM technical support for there was a concurrent access.
analysis.
System action: The action was cancelled.
User response: Retry the same request or determine
FMV9022E error-program Recall daemon (pid
the process holding the lock.
process-ID) ended abnormally, status:
status.
FMV9029E The WebSphere server is running, but
Explanation: A recall daemon stopped abnormally.
the server must be shut down for a
System action: The operation does not complete. restore operation. Shut down the
WebSphere server and try the restore
User response: Try the operation again. If the problem
operation again.
persists, send the core file to IBM technical support for
analysis. Explanation: The WebSphere server must be brought
down to perform a restore.
FMV9023I error-program: Subsidiary recall daemon System action: The restore operation fails.
process exiting.
User response: Shut down the WebSphere server and
Explanation: The process is interrupted and exiting. try the restore operation again.
The user has terminated the process.
System action: Tivoli Storage Manager detected an FMV9030W Cannot set conflicting attributes to file
interrupt. The recall daemon is terminated and exiting. file-name.
User response: None. Explanation: Tivoli Storage Manager cannot set the
file attributes because the requested attributes are in
conflict with one another.
FMV9024E Starting with this release all candidate
processing is done internally by the System action: Tivoli Storage Manager does not set
Tivoli Storage Manager monitor the file attributes.
daemon. Thus -c is no longer a valid
User response: Retry this operation with attributes
option for dsmreconcile.
that do not conflict with each other.
Explanation: The command line options -c and
-Candidates are no longer valid for dsmreconcile as all
FMV9031W File file-name is not a migrated file.
candidates processing is now performed by
dsmmonitord. Explanation: Tivoli Storage Manager can only set file
attributes to a migrated file. This file has not been
System action: Tivoli Storage Manager detected an
migrated.
invalid option. dsmreconcile is exiting.
System action: Tivoli Storage Manager does not set
User response: Don't use options -c and -Candidates
the file attributes.
with dsmreconcile anymore.
User response: Migrate this file, and then retry the
operation.
FMV9025E The Data Protection for WebSphere
plug-in version and the backup-archive
client version do not match. Please FMV9032W File file-name is not in an HSM managed
upgrade your Data Protection for file system.
WebSphere plug-in.
Explanation: Tivoli Storage Manager detects that the
Explanation: The release and version of the Data file is not in an HSM managed file system, and
Protection for WebSphere plug-in is downlevel from the therefore, it cannot perform the operation requested.
release and version of the Backup-Archive Client.
System action: Tivoli Storage Manager does not set
System action: None the file attributes.
User response: Upgrade Data Protection for User response: Add space management to the file
WebSphere to the proper release and version. system, migrate the file, and then retry the operation.

FMV9028E program name: could not acquire lock for FMV9034E The restore operation did not complete,
filesystem. due to a change in the original
WebSphere environment.
Explanation: Prior to modifying a space management
configuration file, it is required to lock the file in order Explanation: The data must be restored to the same
to avoid concurrent access. If acquiring the lock fails, environment that it was backed up from. This includes

Chapter 6. FMV messages 523

FMV9036W • FMV9064E

items such as cell name, node name, and the location

FMV9059E error-program: process cannot detach to
where WebSphere is installed.
become a daemon.
System action: The restore operation does not
Explanation: Tivoli Storage Manager process cannot
complete.
detach itself to become a daemon.
User response: Perform the restore procedure in the
System action: Tivoli Storage Manager cannot start
DP for WebSphere book.
the daemon as requested. Tivoli Storage Manager stops.
User response: Retry the operation.
FMV9036W program-name: migrated file(s) are
missing on server for number stub file(s).
Look in 'file-spec' for file names. FMV9060W error-program: cannot get and increase
limit of open files.
Explanation: Tivoli Storage Manager cannot find the
migrated file(s) on the server. Explanation: Tivoli Storage Manager either cannot get
the limit of the number of open files, or cannot increase
System action: Tivoli Storage Manager continues.
the limit of the number of open files.
User response: Look in the path mentioned in the
System action: Tivoli Storage Manager cannot increase
message for the file name. Also ensure that you are
the number of open files, and was not able to complete
working with the correct server for this file.
the operation.
User response: Free some file space by ending some
FMV9054E The plug-in was not found.
processes or removing some files, and retry the
Explanation: None. operation.

System action: None

FMV9062E File 'filename' has changed during the
User response: Run "dsmc show plugins" at the backup.
command prompt to see the available plug-ins on the
system. Explanation: A file changed during the backup. Check
the dsmerror.log file for a list of files that have
changed.
FMV9057W error-program: cannot get space
information for file-system: error. System action: The backup fails.
Explanation: Tivoli Storage Manager cannot get the User response: Try the backup again.
space information for the file system.
System action: Tivoli Storage Manager continues. FMV9063E error-program: file system file-system is out
of inodes.
User response: Verify that space management has
been added to the file system. Explanation: Tivoli Storage Manager cannot get space
for the file system because the file system is out of
inodes.
FMV9058E error-program: cannot close file-spec: error.
System action: Tivoli Storage Manager cannot get
Explanation: Tivoli Storage Manager cannot close the space via migration.
file. This problem occurs while the dsmmonitor
daemon examines available space on the file system. User response: Remove some files to make more
inodes available and retry.
System action: Tivoli Storage Manager terminates the
current operation.
FMV9064E error-program: Cannot fork a new
User response: Confirm that file system is still process: error.
mounted and managed by HSM. If the problem
persists, reboot the system. If that does not resolve the Explanation: Tivoli Storage Manager cannot fork a
problem, contact IBM technical support for further new process that is needed. If the operating system
assistance. Provide the operating system error code and errno is EAGAIN, then the limit on the total number of
the output of the df, dsmdf, and mount Unix shell processes running on the system or by a single user has
commands. been exceeded, or the system does not have the
resources necessary to create another process. If the
errno is ENOMEM, then there is not enough memory
to create the process.
System action: Tivoli Storage Manager cannot
complete the requested operation.

524 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9065E • FMV9075W

User response: Depending on the error code (errno),

FMV9071W program-name: error reactivating space
either allocate additional virtual memory (swap space)
management for all HSM file systems.
or increase the operating system process limit. Then
restart the HSM daemons or reboot the system. Explanation: Tivoli Storage Manager found an error in
trying to reactivate space management.
FMV9065E File 'filename' or file 'filename2' has been System action: Tivoli Storage Manager does not
added or removed during the backup. reactivate space management for HSM file systems.
Explanation: A file was added or removed during the User response: Make sure space management is
backup. installed correctly and retry the operation.
System action: The backup fails.
FMV9072W error-program: error deactivating space
User response: Try the backup again.
management for all FSM file systems.
Explanation: Tivoli Storage Manager found an error in
FMV9067W error-program: error updating
trying to deactivate space management.
dsmmigfstab file for file-system.
System action: Tivoli Storage Manager does not
Explanation: Tivoli Storage Manager found an error in
deactivate space management for FSM file systems.
updating the dsmmigfstab file for this file system.
User response: Make sure space management is
System action: Tivoli Storage Manager does not
installed correctly and retry the operation.
update the dsmmigfstab file.
User response: See the preceding error message and
FMV9073W program-name: error deactivating space
correct the error if possible. Then, retry the operation. If
management for file system file-system.
problem persists, contact your system administrator.
Explanation: Tivoli Storage Manager found an error in
trying to deactivate the file system.
FMV9068I program-name: dsmmigfstab file updated
for file system file-system. System action: Tivoli Storage Manager does not
deactivate space management for the file system.
Explanation: Tivoli Storage Manager successfully
updated the dsmmigfstab file for the file system. User response: Make sure space management is
installed correctly and retry the operation.
System action: Tivoli Storage Manager continues.
User response: Continue with normal operation.
FMV9074I program-name: space management
functions have been locally deactivated
FMV9069I program-name: all file systems are for file system file-system.
reactivated to previous states.
Explanation: Tivoli Storage Manager has locally
Explanation: Tivoli Storage Manager has reactivated deactivated space management functions like
all file systems managed by HSM to their previous migration, recall and reconciliation for the file system.
states before the global deactivation.
System action: Tivoli Storage Manager continues.
System action: Tivoli Storage Manager continues.
User response: Continue with normal operation.
User response: Continue with normal operation.
FMV9075W program-name: error reactivating space
FMV9070I program-name: space management is now management for file system file-system.
deactivated for all HSM file systems.
Explanation: Tivoli Storage Manager found an error in
Explanation: Tivoli Storage Manager has deactivated trying to reactivate space management for the file
space management for all file systems listed in the system.
dsmmigfstab file.
System action: Tivoli Storage Manager does not
System action: Tivoli Storage Manager continues. reactivate space management for the file system.

User response: Continue with normal operation. User response: Verify that the specified file system is
mounted and that HSM is enabled for this file system.
Then try the operation again. If the problem persists,
contact IBM technical support for additional assistance.
Provide the /etc/filesystems (or equivalent file) and the
output from the mount and dsmdf commands.

Chapter 6. FMV messages 525

FMV9076I • FMV9084E

attempt to recall all the migrated files.

FMV9076I program-name: space management
functions have been locally reactivated User response: Make room in the file system by
for file system file-system. increasing the file system size or removing some files.
Retry the operation.
Explanation: Tivoli Storage Manager has locally
reactivated space management functions like migration,
recall and reconciliation for the file system. Please, note FMV9081W program-name: orphaned stub file(s)
however that the space management might still be detected in file system file-system.
globally deactivated.
Explanation: Tivoli Storage Manager detected one or
System action: Tivoli Storage Manager continues. more orphaned stub files. Either the migration server
was changed in the client system options file after the
User response: Continue with normal operation.
file was migrated, or the migration server database is
damaged.
FMV9077I program-name: removed space
System action: Tivoli Storage Manager does not
management from file system file-system.
attempt to remove space management from the file
Explanation: Tivoli Storage Manager removed space system.
management. The file system is now a native file
User response: Determine the cause of orphaned stub
system.
files. Switch to the correct migration server and recall
System action: Tivoli Storage Manager continues. the migrated files. Retry the operation.
User response: Continue with normal operation.
FMV9082W program-name: error encountered while
reconciling file system file-system.
FMV9078W Space management is not removed from
file system file-system. Explanation: Tivoli Storage Manager encountered an
error performing reconciliation on the file system.
Explanation: Tivoli Storage Manager was not able to
remove space management from this file system. System action: Tivoli Storage Manager continues.
Possible causes:
User response: Refer to other messages displayed or
v Kernel extension is downlevel. messages in the log to correct the problem. Then retry
v Program is downlevel. the operation.
v Insufficient disk space.
System action: Tivoli Storage Manager is unable to FMV9083W program-name: cannot deactivate space
complete the requested operation. management on file system file-system.

User response: Refer to the immediately preceding Explanation: Tivoli Storage Manager cannot deactivate
error message and retry the operation. space management on the file system.
System action: Tivoli Storage Manager continues.
FMV9079W program-name: no migrated files User response: Correct the error if possible and retry
matching search criteria found. the operation.
Explanation: Tivoli Storage Manager did not find any
migrated files matching the search criteria. FMV9084E program-name: file-system is not managed
System action: Tivoli Storage Manager cannot or not locally managed by space
complete the requested operation. management.

User response: Retry the operation with a different Explanation: There is no entry for the file system in
search criteria. the dsmmigfstab file or the file system is managed by
another node.

FMV9080E program-name: not enough space in file System action: Tivoli Storage Manager will not
system or storage pool to recall all perform space management functions on this file
migrated files. system.

Explanation: Tivoli Storage Manager detects there is User response: Add space management to the file
not enough space in the file system to hold all the system, if appropriate, and then retry the operation. If
migrated files if all are recalled. If you are using GPFS the file system is not locally managed, retry the
storage pools, each pool needs to have enough space to operation on the node managing the file system.
recall it's files.
System action: Tivoli Storage Manager does not

526 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9085E • FMV9093W

file for a list of files that were added, removed, or

FMV9085E program-name: file system file-system is
changed.
not managed by space management.
System action: The backup fails.
Explanation: There is no entry for the file system in
the dsmmigfstab file. User response: Try the backup again.
System action: Tivoli Storage Manager will not
perform space management functions on this file FMV9090E program-name: file-system is not a valid
system. file system name.
User response: Add space management to the file Explanation: Tivoli Storage Manager received an
system, if appropriate, and then retry the operation. invalid file system name. The file system is not
mounted, or is not mounted correctly.
FMV9086E program-name: A DMAPI error occured System action: Tivoli Storage Manager continues.
adding space management to file system
file-system, It is possible DMAPI is User response: Correct the file system name, and retry
disabled on this file system. The system the operation.
set the error code: errno = errno-value
Explanation: Tivoli Storage Manager encountered an FMV9091E The WebSphere backup validation
error and cannot add space management to the file failed. One or more files were added,
system. removed, or changed during the backup.

System action: Tivoli Storage Manager Space Explanation: One or more files have been added,
management cannot be added to file system. removed, or changed from the time WebSphere was
queried to the time that all the data was sent to the
User response: Verify that DMAPI is enabled for this Tivoli Storage Manager server. Check the dsmerror.log
file system and retry the operation. file for a list of files that were added, removed, or
changed.
FMV9087I Space management is successfully System action: The backup fails.
added to file system file-system.
User response: Try the backup again. Do not install
Explanation: Tivoli Storage Manager has added space new WebSphere applications or change the WebSphere
management to the file system, and will now monitor configuration while in the backup window.
its space usage. You can also perform other space
management operations on this file system.
FMV9092W AES 128-bit Encryption is not being
System action: Tivoli Storage Manager continues. used.
User response: Continue with normal operation. Explanation: AES 128-bit encryption is not being used.
DES 56-bit encryption is being used instead.
FMV9088W program-name: space management is System action: DES 56-bit Encryption is used instead
already active for file system filesystem. of AES 128-bit encryption.
Explanation: This message is issued when trying to User response: If the user wants to use AES
add space management to a filesystem with space encryption, then the user must install the IBM JRE in
management already activated. It is not possible to add order to enable AES encryption for the web client.
space management for a filesystem that already has
space management activated.
FMV9093W program-name: cannot update migration
System action: The action was cancelled. candidates list file-name.
User response: In case you wanted to update the Explanation: Tivoli Storage Manager cannot update
filesystem's space management configuration instead, the migration candidates list because not enough
use the appropriate update command. memory is available to create a temporary file.
System action: Processing stops.
FMV9089E The group backup validation failed.
One or more files were added, removed, User response: Make some memory available by
or changed during the backup. ending some processes, and then retry the operation.

Explanation: One or more files have been added,

removed, or changed from the time WebSphere was
queried to the time that all the data was sent to the
Tivoli Storage Manager server. Check the dsmerror.log

Chapter 6. FMV messages 527

FMV9094W • FMV9128I

User response: Verify that the search patter is correct.

FMV9094W program-name: no candidates found in
file system file-system.
FMV9117E Virtual machine 'VM name' will not be
Explanation: Tivoli Storage Manager found no files
backed up because it contains at least
eligible for migration in the file system after running
one of the following unsupported
dsmreconcile.
special characters special characters
System action: Tivoli Storage Manager continues.
Explanation: The specified virtual machine contains
User response: Continue with normal operation. characters that are not supported for virtual machine
backup and restore operations.
FMV9096E User is not the owner of file System action: The backup for the specified virtual
filesystem-namedirectory-namefile-name so machine fails.
file is skipped.
User response: Rename the virtual machine so that it
Explanation: The user does not own this file and does not contain any of the specified special characters.
cannot perform this operation.
System action: Tivoli Storage Manager skips the file. FMV9121I Activate completed.
User response: None, or if you have root-user Explanation: A Domino activate databases operation
authority, switch to root user and retry the operation. was completed.
System action: Tivoli Storage Manager activated the
FMV9098E program-name: space management does databases.
not support file system file-system.
User response: Continue with normal operations.
Explanation: Tivoli Storage Manager space
management does not support this type of file system.
FMV9126E program-name: cannot determine whether
Space management supports only true local file systems
space management is active or inactive
(e.g. JFS on AIX). Space management does not support
for file-system due to error: error.
other types of file systems (IBM AFS™, NFS, etc).
Explanation: The program 'program-name' indicated
System action: Processing of the file system stopped.
in the message text was unable to obtain statistics for
User response: None. file system 'file-system'. Therefore the program cannot
determine whether space management is activated,
deactivated, or globally deactivated on that file system.
FMV9099E program-name: space management is not
The message text includes a description of the Unix
active for file system file-system.
errno error that occurred while trying to get the state of
Explanation: Tivoli Storage Manager found the file space management.
system did not have space management activated.
System action: Tivoli Storage Manager stops the
System action: Processing of that file system stopped. operation.

User response: Reactivate space management for the User response: Verify that the file system is mounted
file system. and accessible. Using the appropriate tools for that file
system, check whether there are any I/O or other
integrity errors on that file system. Then try the
FMV9100E Unable to open file 'filename' for output. operation again. If the operation fails, then a system
Explanation: The file name specified cannot be reboot might clear the error condition. If, after taking
opened. these actions the problem persists, contact IBM
technical support for assistance.
System action: Make sure that user has access to write
to specified file, or use different file name.
FMV9128I Inactivate logs completed.
User response: Output will not be saved. Please
specify different file or check permissions on chose file. Explanation: A Domino inactivate log operation was
completed.

FMV9101E Migrated files matching 'file-name' could System action: Tivoli Storage Manager inactivated the
not be found. log.

Explanation: File name for search pattern can not be User response: Continue with normal operations.
found in the TSM server database as a migrated file.
System action: No query result.

528 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9130W • FMV9137I

FMV9130W program name: could not convert the FMV9133E program name: space management already
space management configuration for active for filesystem.
filesystem from file old configuration file to
Explanation: This message is issued when trying to
XML configuration file.
add space management to a filesystem with space
Explanation: Starting from Tivoli Storage Manager management already activated.
version 6.1, space management configuration is stored
System action: The action was cancelled.
in XML format. In case the systems finds a
configuration file in former, proprietary format only, it User response: Check the filesystem's space
is read and converted to XML format. This message management configuration and consider updating it in
indicates that the old format file was read successfully case it does not match your needs. It is not possible to
but could not be written to an XML configuration file. add space management for a filesystem that already
has space management activated.
System action: Space management configuration is
taken from the old format file.
FMV9134E program name: space management not
User response: Determine the reason why the XML
active for filesystem.
file could not be written.
Explanation: The program requested the space
management configuration for a file system where
FMV9131E program name: old space management
space management is not active.
configuration file does not match
filesystem: file content. System action: The action was cancelled.
Explanation: Starting from Tivoli Storage Manager User response: In case you entered the filesystem
version 6.1, space management configuration is stored specification, check for correct spelling. It is not
in XML format. In case the systems finds a possible to perform space management actions on a
configuration file in former, proprietary format only, filesystem with space management not activated.
this file is processed. The content of the file starts with
the filesystem; this message is issued when the
filesystem name does not match. FMV9135E program name: space management for
filesystem not controlled by the local
System action: Space management configuration was node.
rejected. The filesystem is considered to not have space
management activated. Explanation: The program requested the space
management configuration for a file system where
User response: Check the old configuration file and space management is active, but not controlled by the
correct the filename manually in case the rest of the file local node. In cluster environments, some space
content is valid. Alternatively, you can explicitely add management actions are allowed from the owner node
space management for the filesystem to create a new only.
space management configuration file.
System action: The action was cancelled.

FMV9132E program name: old space management User response: Determine the controller node for this
configuration file is corrupted for filesystem and retry.
filesystem: file content.
Explanation: Starting from Tivoli Storage Manager FMV9136E program name: could not remove
version 6.1, space management configuration is stored configuration file for filesystem.
in XML format. In case the systems finds a Explanation: During removal of space management
configuration file in former, proprietary format only, for the given filesystem, this configuration file could
this file is processed. This message is issued when not be removed.
parsing its content failed.
System action: Space management could not be
System action: Space management configuration was deactivated for this filesystem.
rejected. The filesystem is considered to not have space
management activated. User response: Determine the reason why the file
could not be removed and retry.
User response: Check the old configuration file and
consider correct its content manually. Alternatively, you
can explicitely add space management for the FMV9137I File: file-name is not premigrated.
filesystem to create a new space management Explanation: File must be premigrated to migrate it.
configuration file.
System action: The file was skipped.
User response: The migration of premigrated files

Chapter 6. FMV messages 529

FMV9140E • FMV9153E

requires that the file is in premigration state.

FMV9150I Archive log completed.
Explanation: A Domino archive log operation was
FMV9140E The migration options premigration and
completed.
stub cannot be combined.
System action: Tivoli Storage Manager archived the
Explanation: The migration option premigration and
log.
stub are mutual exclusive. Both options end in different
results for the same file. User response: Continue with normal operations.
System action: Command ends without changes to the
file. FMV9151E An unexpected program error was
encountered . Tivoli Storage Manager
User response: Use the migration options
function name : function-name Tivoli
premigration and stub in different instances of the
Storage Manager function : function-desc
command.
Tivoli Storage Manager return code :
TSM-rc Tivoli Storage Manager file :
FMV9145E Virtual machine will not be backed up file-name (line-number)
because it has an empty name.
Explanation: None.
Explanation: The specified virtual machine name is
System action: Processing stops.
empty. This is not supported for virtual machine
backup and restore operations. User response: Check error log for more information.
Contact the Tivoli Storage Manager administrator with
System action: The backup for the specified virtual
the information provided in this message.
machine fails.
User response: Rename the virtual machine so that its
FMV9152E program-name: cannot deactivate space
name contains supported characters.
management for whole system: error.
Explanation: Space management cannot be
FMV9147E program-name: cannot read file-spec: error.
deactivated for the whole machine.
Explanation: Tivoli Storage Manager cannot read this
System action: Tivoli Storage Manager cannot
file.
deactivate space management support.
System action: Tivoli Storage Manager cannot fully
User response: The HSM global status is inaccessible,
complete the requested operation.
possibly due to concurrent access. Try the operation
User response: An error occurred reading an HSM again. If the problem continues, examine the output of
managed file system status file. Verify that the file the shell command ps -aef as well as the contents of
system is mounted and enabled for HSM and is /etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. If
actually managed by HSM and then try the operation a pid is stored in this file and it does correspond to a
again. If the problem persists, contact IBM technical running process, remove the dmiFSGlobalState.pid file
support for further assistance. Provide the output from and retry the operation. If the problem persists, reboot
the mount, dsmdf and ls -l [file system name] the system and repeat the appropriate analysis for your
commands. file system type.

FMV9148E program-name: cannot find mount point FMV9153E program-name: cannot reactivate space
for file system file-system. management for whole system: error.

Explanation: Tivoli Storage Manager cannot find file Explanation: Space management cannot be reactivated
system mount point. for the whole machine.

System action: Tivoli Storage Manager cannot System action: Tivoli Storage Manager cannot
complete the requested operation. reactivate space management support.

User response: The specified file system is not User response: The HSM global status is inaccessible,
currently mounted. Mount the file system and try the possibly due to concurrent access. Try the operation
operation again. again. If the problem continues, examine the output of
the shell command ps -aef as well as the contents of
/etc/adsm/SpaceMan/config/dmiFSGlobalState.pid. If
a pid is stored in this file and it does correspond to a
running process, remove the dmiFSGlobalState.pid file
and retry the operation. If the problem persists, reboot

530 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9154E • FMV9161E

the system and repeat the appropriate analysis for your

FMV9158W program-name: cannot turn on ENOSPC
file system type.
checking in kernel: error.
Explanation: Tivoli Storage Manager cannot turn on
FMV9154E program-name: cannot deactivate space
ENOSPC checking.
management for file system file-system:
error. System action: Tivoli Storage Manager cannot turn on
ENOSPC checking. Processing continues.
Explanation: Space management cannot be
deactivated for the file system. User response: Verify that the AIX JFS HSM fsm
kernel extension is loaded, then try the operation again.
System action: Tivoli Storage Manager unable to
If the problem persists, reboot the system and try the
deactivate space management support for the file
operation again.
system.
User response: The HSM file system status is
FMV9159E program-name: unable to create temporary
inaccessible, possibly due to concurrent access. Try the
file.
operation again. If the problem continues verify that
the file system is mounted and that HSM is enabled on Explanation: Tivoli Storage Manager cannot create a
the file system with the Unix shell commands mount temporary file.
and dsmdf. If the problem persists, reboot the system
System action: Tivoli Storage Manager cannot
and try the operation again.
complete its operation.
User response: Check with the Unix mount shell
FMV9155E program-name: cannot reactivate space
command that /tmp and /etc exist as separate file
management for file system file-system:
systems on your system. Use the df command to check
error.
whether they are full. Create additional space by
Explanation: Space management cannot be reactivated deleting files or increasing the file system size.
for the file system.
System action: Tivoli Storage Manager cannot FMV9160E program-name: cannot write to temporary
reactivate space management support to the file system. file or status filefile-spec: error.
User response: The HSM file system status is Explanation: Tivoli Storage Manager cannot complete
inaccessible, possibly due to concurrent access. Try the writing to the temporary file.
operation again. If the problem continues, verify that
System action: Tivoli Storage Manager cannot
the file system is mounted and that HSM is enabled on
complete the requested operation.
the file system with the Unix shell commands mount
and dsmdf. If the problem persists, reboot the system User response: The Unix error code may provide
and try the operation again. guidance as to why the write failed. Use the Unix
mount and df shell commands to verify that the
associated file system is mounted and has space
FMV9156I Rollforward completed.
available. If this message resulted from a shell
Explanation: A Domino DB2 rollforward operation command, mount the file system and create additional
was completed. space if necessary, then retry the operation. If the
message did not result from a shell command, restart
System action: Tivoli Storage Manager rollforward the
the daemons. If the problem persists, reboot the system.
Domino DB2 database log.
User response: Continue with normal operations.
FMV9161E Invalid backupset file or device name
entered.
FMV9157W Please enter a valid filespace location
Explanation: The backupset file or device name
Explanation: This message will be seen when you run specified does not contain a valid backupset.
the Pref editor from MFC GUI. This means that user
System action: Processing stopped.
has not entered a required field which is filespace
location path. User response: Specify a file name or device that
contains a valid backupset and retry the operation.
System action: Tivoli Storage Manager Enter required
field
User response: Operation will not proceed till user
enters required field

Chapter 6. FMV messages 531

FMV9162W • FMV9169E

FMV9162W Object: 'dir-name' is skipped for recall: It FMV9166I A 'backup type' backup version backup
is a directory. date 'datetime' is not consistent with local
repository and has been deleted from
Explanation: The object is a directory. Space
the server (object name='filespace
management does not recall directories.
namepath-namefile-name', ID =
System action: IBM Tivoli Storage Manager does not 'object-id:object-id').
recall this object because it is a directory.
Explanation: The specified backup instance of the
User response: None. named object is not valid with local repository contents.
This could happen if local repository is modified or got
corrupted on the client system. This backup can not be
FMV9163W program-name: Could not acquire the restored, therefore it will be deleted on the server.
recall daemon session id.
System action: The specified backup object will be
Explanation: Could not set up the event disposition deleted on the server. Processing will continue.
for the file system, because the recall daemon session
could not be acquired. It seems the recall daemon is not User response: None.
running. Recall requests will not be handled, which
means the TSM client for space management can't react
FMV9167W The client cache for adaptive subfile
to recall requests for this file system.
backup is corrupt and cannot be used.
System action: Tivoli Storage Manager could not set
Explanation: The adaptive subfile cache has become
up the recall event handling. The recall event handling
corrupt. While the backup client can detect the
is not enabled for this filesystem.
corruption, the reason for the corruption cannot be
User response: Start or restart the recall daemon. determined.
System action: The TSM client will proceed with
FMV9164W program-name: Could not acquire the standard selective or incremental backup. The cache
monitor daemon session id. will be rebuilt so that subsequent backups will use the
adaptive subfile technique.
Explanation: Could not set up the event disposition
for the file system, because the monitor daemon session User response: If the problem persists, contact IBM
could not be acquired. It seems the monitor daemon is technical support for assistance. Be prepared to provide
not running. Thus the thresholds for file system usage the client error log, which will contain additional
will not be monitored and the NOSPACE event will not messages that might be useful for support to help
be handled, which means the file system may run out identify the problem.
of space.
System action: Tivoli Storage Manager could not set FMV9168E program-name cannot open database
up the NOSPACE event handling. The NOSPACE event file-spec due to the following error: error.
handling is not enabled for this filesystem.
Explanation: The database specified in the message
User response: Start or restart the monitor daemon. text could not be opened. The reason for the error is
included in the message text.

FMV9165E program-name cannot open directory System action: The requested operation does not
directory-spec due to the following error: complete.
error.
User response: Make sure that the file system has
Explanation: The directory indicated in the message sufficient available space, then try the operation again.
text cannot be opened. The message text includes a If the problem persists, contact IBM technical support
description of the error that occurred. for further assistance.

System action: The requested operation is not

completed. FMV9169E program-name: cannot create directory
directory-spec, reason.
User response: Try to correct the error condition that
is indicated in the message text, then try the operation Explanation: Tivoli Storage Manager cannot create this
again. If the problem persists, contact IBM technical directory.
support for further assistance.
System action: Tivoli Storage Manager does not create
this directory.
User response: Verify that this directory does not
already exist, and that its parent directory has proper
permissions.

532 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9170E • FMV9179W

System action: Tivoli Storage Manager cannot

FMV9170E program-name: file-system is not a
continue with the requested backup delete operation.
mounted local file system.
User response: Close all unneeded applications and
Explanation: Tivoli Storage Manager did not find that
try the operation again. Reducing the scope of queries
this file system is properly mounted.
and the amount of data returned might also help, or
System action: Tivoli Storage Manager ignores the file see your system administrator.
system.
User response: Verify that this file system is local and FMV9176I Backup delete is stopped by the user.
mounted and activated properly.
Explanation: You requested the backup delete
operation be stopped.
FMV9171E An error internal to Tivoli Storage
System action: Archive delete stopped.
Manager has occurred. The following
string is too long: error. User response: Continue with normal operations.
Explanation: None.
FMV9177W All data events for remote recalls
System action: The requested operation does not
running on node: 'cluster node ID',
complete.
hostname: 'cluster node hostname' are
User response: A system reboot might clear up the going to be aborted.
problem, after which the operation should be tried
Explanation: The remote node is not responding, so
again. If the problem persists, contact IBM technical
all DMAPI data events which are currently being
support for further assistance.
processed on this remote node should be aborted. This
warning is likely caused by an RPC communication
FMV9172I Backup system component '' is excluded issue between the local node and the specified remote
from processing. node.
Explanation: You tried to back up the system System action: The dsmrecalld distributor process is
component that was specified to be excluded from going to abort all data events (if any) which are
backup. currently being processed on the specified remote node.
System action: IBM Tivoli Storage Manager did not User response: Ensure that the network and host
back up the system component. connection are configured correctly. Then, retry the
recall operation.
User response: Verify the input keyword or the writer
name via the command line client and the Exclude lists.
FMV9178E program-name cannot open file file-spec
due to the following error: error.
FMV9173I Backup system component '' doesn't
exist. Explanation: The program indicated in the message
text was unable to open the specified file. The message
Explanation: You tried to back up the system
text also includes a description of the error that
component that is not installed or is not started.
occurred when it tried to open the file.
System action: IBM Tivoli Storage Manager did not
System action: The requested operation does not
back up the system component.
complete.
User response: Verify the input keyword or the writer
User response: Verify that the file system on which
name by using the GUI interface to expand the "System
the file resides is mounted, then try the operation
State" or "System Services" node.
again. A system reboot might clear up the problem. If
the problem persists, contact IBM technical support for
FMV9174I A backup delete completed. further assistance.

Explanation: A Backup delete was completed.

FMV9179W The operation completed successfully.
System action: Tivoli Storage Manager deleted backup However, some error occurred on
files. creation of the required vApps list.
Explanation: One or more of the items included in the
FMV9175E There is not enough memory for the vApps specification were not found. This can be caused
backup delete operation by a change in the vCD organizations configuration or
Explanation: Tivoli Storage Manager cannot allocate a user mistake in the provided vApp spec.
memory for the specified backup delete operation. System action: The operation completes successfully

Chapter 6. FMV messages 533

FMV9180W • FMV9188E

User response: Check the local client error log for a User response: Try the operation again. If the problem
reason for the failure and check the command occurs in an HSM daemon, restart the daemon, then try
specification. Correct any issues and execute the the operation again. If the problem continues to occur,
command again. use your operating system's administrative tools to
check virtual memory (swap space) on your system,
and increase it if necessary. Check whether an
FMV9180W An entry in the password file could not
application is consuming available virtual memory. A
be decrypted.
system reboot might also clear up the problem. If the
Explanation: The password failed decryption problem persists, contact IBM technical support for
validation. further assistance.

System action: The password in the password file will

be ignored. You will be prompted for the password, FMV9185W Master scout daemon is not running!
unless the process is running in the background, such
Explanation: A list of candidates files eligible for
as in scheduling mode.
migration cannot be built because the master scout
User response: Enter the password when prompted. daemon is not running on the selected client node.
System action: Files are not automatically migrated to
FMV9182W Your customized client nodes list the Tivoli Storage Manager server.
already contains this node. Would you
User response: Restart the master scout daemon
like to update it?
manually using the "dsmscoutd" command from a
Explanation: The list of client nodes contains already command shell on the machine where Space
the specified client node. You cannot have two client Management Agent is running.
nodes with the same client node name in the same
machine.
FMV9186E program-name: cannot open mounted file
System action: Updates or does not update the client system file-system: error.
node, depending on the user response.
Explanation: Tivoli Storage Manager cannot open
User response: Select "yes" to update the client node. mounted file system.
Select "no" to cancel this operation.
System action: Tivoli Storage Manager ignores the file
system.
FMV9183W Removing Space Management from
User response: Verify that this file system is mounted
'file-system' file system means that all
and activated properly.
migrated data will be recalled from
Tivoli Storage Manager Server
'server-name' Make sure that enough free FMV9187W Monitor daemon is not running!
space is present on this file system for
Explanation: Files cannot be automatically migrated to
the recalled data. Do you want to
the Tivoli Storage Manager server or recalled from
remove Space Management from
Tivoli Storage Manager server because the monitor
'client-node' now?
daemon is not running on the selected client node.
Explanation: Removing Space Management from the
System action: Files are not automatically migrated or
selected file system means that all migrated data will
recalled from the Tivoli Storage Manager server.
be recalled from the server.
User response: Restart the monitor daemon manually
System action: Prompts the user to confirm when
using the "dsmmonitord" command from a command
removing Space Management from the selected file
shell on the machine where Space Management Agent
system.
is running.
User response: Make sure that enough free space is
present on this file system for the recalled data.
FMV9188E Not enough memory for recall operation
Explanation: Tivoli Storage Manager cannot allocate
FMV9184E program-name cannot allocate memory
storage for the requested recall operation.
due to the following error: error.
System action: Tivoli Storage Manager cannot
Explanation: A memory allocation error occurred. The
complete the requested operation.
message text includes a description of the error that
occurred. User response: Retry the recall operation. If the
problem continues, check with your system
System action: The requested operation does not
administrator.
complete.

534 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9189I • FMV9203E

FMV9189I Recall stopped by user FMV9196W The PASSWORDACCESS option in

your dsm.sys file is not set to
Explanation: You requested that Tivoli Storage
GENERATE. Reset it to GENERATE and
Manager stop the recall operation.
restart the HSM client.
System action: Recall stopped.
Explanation: The PASSWORDACCESS option in your
User response: Continue with normal operations. dsm.sys file is set to PROMPT. It must be set to
GENERATE in order for automatic space management
services to work.
FMV9191E Error checking file system state
System action: Tivoli Storage Manager terminates the
Explanation: The system cannot open /dev/dsm or client.
cannot open the file system.
User response: The root user must set the
System action: Transaction stopped. PASSWORDACCESS option to GENERATE in the
User response: Retry the operation. If the problem dsm.sys file.
continues, check with your system administrator.
FMV9197E File: file-name has already been recalled.
FMV9192I Cannot disable file-system. Explanation: You tried to recall the a file that has
Explanation: Tivoli Storage Manager cannot disable already been recalled.
the file system. This message is issued only from the System action: Tivoli Storage Manager does not
Motif HSM GUI, which is no longer supported. highlight the file.
System action: Tivoli Storage Manager ignores the User response: None.
request.
User response: Use the dsm Unix shell commands. FMV9198E File: file-name is a resident file.
Explanation: You tried to recall a file that is resident.
FMV9193I Cannot open file-system.
System action: Tivoli Storage Manager will not
Explanation: Tivoli Storage Manager cannot open the highlight the file.
file system. This message is issued only from the Motif
HSM GUI, which is no longer supported. User response: None.
System action: Tivoli Storage Manager ignores the
request. FMV9199S Cannot open /dev/fsm

User response: Use the dsm Unix shell commands. Explanation: Tivoli Storage Manager cannot open the
space management device file, /dev/fsm.
FMV9194W A selective migration is in progress. System action: Tivoli Storage Manager cannot
Wait until it completes and retry the complete the operation.
recall.
User response: Check to see whether Tivoli Storage
Explanation: You tried a recall operation while a Manager is installed correctly and that the /dev/fsm
selective migration is in progress. file exists. Correct the problem and retry the operation.
System action: Tivoli Storage Manager ignores the
request. FMV9201W LAN-free path failed.
User response: Wait until the selective migration is Explanation: A LAN-free connection could not be
complete and retry the recall operation. made.
System action: The system will connect to the server
FMV9195W A selective recall is in progress. Wait without using the LAN-free path.
until it completes and retry the
User response: Verify your LAN-free setup.
migration.
Explanation: You initiated a migration operation while
FMV9203E ENABLELANFREE can not be used
a selective recall is in progress.
when HSM is installed.
System action: Tivoli Storage Manager ignores the
Explanation: The Tivoli Storage Manager Client has
request.
detected that HSM is installed on the system. LAN-free
User response: Wait until the selective recall is is not a valid option when HSM is installed.
complete and retry the migration operation.

Chapter 6. FMV messages 535

FMV9206W • FMV9236E

v This error occurs on AIX when this file is found: User response: Check the dsmsm.log file in the
/usr/tivoli/tsm/client/hsm/bin/dsmrecalld installation directory of your local machine and the
v This error occurs on Solaris when this file is found: $DSM_DIR/dsmerror.log file on the client node
/opt/tivoli/tsm/client/hsm/bin/dsmrecalld machine if present. If this does not identify the cause of
the problem, contact your system administrator and/or
System action: An invalid option is detected and Tivoli Storage Manager technical support for further
processing stops. assistance.
User response: Remove the ENABLELANFREE option
from the system option file. ENABLELANFREE can FMV9231E Processing error detected in the
only be used when HSM is not installed. migration phase of this process!
Explanation: An unexpected error is occurred due to
FMV9206W User quota is reached! some processing communication error.
Explanation: The maximum amount of data that can System action: Tivoli Storage Manager will not
be migrated and premigrated from this file system to migrate or premigrate files from this file system.
the Tivoli Storage Manager Server is reached.
User response: Check the dsmsm.log file in the
System action: Files cannot be migrated to Tivoli installation directory of your local machine and the
Storage Manager server. $DSM_DIR/dsmerror.log file on the client node
User response: Use the File System Properties dialog machine if present. If this does not identify the cause of
to specify a different quota value. the problem, contact your system administrator and/or
Tivoli Storage Manager technical support for further
assistance.
FMV9220W Recall daemon is not running!
Explanation: Files cannot be recalled from Tivoli FMV9233E Processing error detected in the
Storage Manager server because the recall daemon is premigration phase of this process!
not running on the selected client node.
Explanation: An unexpected error is occurred due to
System action: Files are not recalled from the Tivoli some processing communication error in the
Storage Manager server. premigration phase.
User response: Restart the recall daemon manually System action: Tivoli Storage Manager will not
using the "dsmrecalld" command by a command shell premigrate files from this file system.
on the machine where Space Management Agent is
running. User response: Check the dsmsm.log file in the
installation directory of your local machine and the
$DSM_DIR/dsmerror.log file on the client node
FMV9227E Internal error loading the status: machine if present. If this does not identify the cause of
error-message the problem, contact your system administrator and/or
Tivoli Storage Manager technical support for further
Explanation: An exception has been detected loading
assistance.
the status of space management activities.
System action: The status of the related activity is not
FMV9236E Error detected performing reconciliation
loaded. The process continues to load the status at the
on this file system!
next refresh interval.
Explanation: An error is occurred performing
User response: Check the dsmsm.log file in the
reconciliation on the selected file system.
installation directory of your local machine and the
$DSM_DIR/dsmerror.log file on the client node System action: Tivoli Storage Manager will not
machine if present. If this does not identify the cause of reconcile this file system with Tivoli Storage Manager
the problem, contact your system administrator and/or server.
Tivoli Storage Manager technical support for further
assistance. User response: Check the dsmsm.log file in the
installation directory of your local machine and the
$DSM_DIR/dsmerror.log file on the client node
FMV9230E Communication error detected in the machine if present. If this does not identify the cause of
migration phase of this process! the problem, contact your system administrator and/or
Tivoli Storage Manager technical support for further
Explanation: An unexpected error is occurred due to
assistance.
server communication error in migration phase.
System action: Tivoli Storage Manager will not
migrate files from this file system.

536 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9240W • FMV9264E

User response: If HSM control file exclusion conflicted

FMV9240W Could not acquire the serial number of
with other include/exclude directives, correct the
disk 'disk-name' at LUN LUN-id.
explicit include/exclude directives to allow for
Explanation: Tivoli Storage Manager was not able to exclusion of HSM control files and directories. Ensure
determine the serial number of the specified disk. The that all HSM file systems are mounted.
disk may not support SCSI inquiries of the Vital
Product Data on page 0x80.
FMV9255I An empty status file will be generated.
System action: Server-free data movement will not be
Explanation: The HSM status file is missing or can not
possible for data residing on the specified disk.
be opened. An empty status file will be created.
User response: None.
System action: File data migration will continue to
work normally.
FMV9249E File 'file-namefile-namefile-name' accessed
User response: Please run dsmreconcile to create a
during migration. File skipped.
complete status file.
Explanation: The specified file-name was not migrated
because the file was accessed by another process during
FMV9256E File 'file-namefile-namefile-name' is
the attempt to migrate it.
currently opened by another process.
System action: Tivoli Storage Manager left the file
Explanation: The file is locked by a migration or recall
resident.
operation. A file can be the object of only one recall
User response: If you want the file migrated, stop the process or one recall operation at a time.
process which is accessing the file and retry the
System action: The file is skipped.
migration.
User response: If this error is not a result of a parallel
file migration or recall operation, then this error might
FMV9250I File system 'file-system' reconciliation
be due to the previous cancelled migration or recall
completed.
operation. In this case, restart the dsmrecalld daemon
Explanation: Tivoli Storage Manager has finished and try the operation again.
reconciling the file system.
System action: Tivoli Storage Manager continues. FMV9257E Server 'server-name' does not support
space management.
User response: Continue with normal operations.
Explanation: The specified server-name does not
support space management. It is a downlevel server, or
FMV9251E ProgramName: Cannot parse
a platform that does not support space management.
command-line options correctly.
System action: Tivoli Storage Manager failed the
Explanation: An internal program error occurred
operation.
trying to parse the command-line arguments.
User response: If you want to use the space
System action: The program is not able to process the
management function, make sure you connect to a
request.
server that supports space management.
User response: Use the -h or -help option to see what
options are allowed on the command-line, then retry
FMV9263W You cannot restore both active and
the request.
inactive versions of System State.
Explanation: Restoring an active copy and inactive
FMV9252I Value of environment variable: envVar.
copy of System State is not allowed.
Explanation: None.
System action: No processing takes place.
System action: This message is informational.
User response: Select either the active copy or the
User response: None. inactive copy to perform restore operation.

FMV9254E An error was encountered while adding FMV9264E Incremental backup of Virtual Machine
implicit excludes to the include-exclude 'vmname' failed with RC rc
list.
Explanation: The incremental backup of virtual
Explanation: None. machine volumes failed.

System action: Tivoli Storage Manager cannot System action: The backup of the virtual machine
proceed. finished with failures. The next virtual machine in the

Chapter 6. FMV messages 537

FMV9265E • FMV9284K

vmlist will be processed. The reason for the failure is

FMV9278E Failure processing vmList option. RC=rc
written to the local client error log.
Explanation: Failure processing vmList option.
User response: Check the local client error log for
reason for the failure. System action: The backup can not continue.
User response: Check for errors in the vmList option
FMV9265E Failure mounting Virtual Machine value. Refer to the documentation for the vmList option
'vmname' with vcbMounter command. for more information.
RC=rc
Explanation: The VMware vcbmount command failed FMV9279E Failure locating Virtual Machine
to mount virtual machine disk. 'vmname' volumes. Failed with RC=rc
System action: The backup of the virtual machine can Explanation: Virtual machine volumes can not found.
not continue. The next virtual machine in the vmlist Volume mount points are not available on Backup
will be processed. The output of the vcbMounter Proxy machine.
command will show the reason for the failure.
System action: The backup of the virtual machine can
User response: Issue a vcbMounter command for the not continue. The next virtual machine in the vmlist
virtual machine to determine the reason for the failure. will be processed. The output of the vcbMounter
Refer to the documentation for that message for more command will show the reason for the failure.
information.
User response: Issue a vcbMounter command for the
virtual machine to determine the reason for the failure.
FMV9266E Failure initializing virtual machine Refer to the documentation for that message for more
environment. Can not find information.
vcbMounter.exe command. RC=rc
Explanation: Failure initializing virtual machine FMV9280E 'vmname' option must be set when
environment. Can not find vcbMounter.exe command. running this operation.
The VMware Consolidated Backup Framework not
Explanation: A required option for the command is
installed or vcbMounter.exe command is not located in
missing.
current PATH environment variable.
System action: The operation can not continue.
System action: The backup can not continue. The
output of the vcbMounter command will show the User response: Set the missing option using the
reason for the failure. Preference Editor or the command line.
User response: Issue a vcbMounter command for the
virtual machine to determine the reason for the failure. FMV9283K Tivoli Space Manager is recalling a
Refer to the documentation for that message for more migrated file.
information. The VMware Consolidated Backup
Framework must be installed on the Backup Proxy Explanation: The space management kernel extension
machine. The installed location and the vcbMounter.exe is attempting to access a file that is not stored locally. If
must be located in the PATH environment variable. The the file is migrated, Tivoli Storage Manager is
default location is C:\Program Files\VMware\VMware attempting to access it from an Tivoli Storage Manager
Consolidated Backup Framework. space management server.
System action: Tivoli Storage Manager waits for the
FMV9267E program-name: File system file-system has kernel to access the file.
exceeded its quota. User response: None.
Explanation: Tivoli Storage Manager detects that the
file system has exceeded its quota. No more data can FMV9284K File access waiting for migration to
be migrated out of this file system. complete.
System action: Tivoli Storage Manager will not Explanation: The file being accessed is currently being
migrate files from this file system. migrated. Access to this file must wait until the
User response: Recall some files, or ask the system migration process is finished.
administrator to increase the quota for this file system. System action: Tivoli Storage Manager waits until the
file migration is completed.
User response: None.

538 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9285K • FMV9293E

User response: None.

FMV9285K Cannot complete remote file access.
Explanation: The space management kernel extension
FMV9290W File: file-name is skipped for migration:
cannot complete the remote file access. The file may be
The file type is either unknown or
migrated to an Tivoli Storage Manager migration
unsupported.
server. The file cannot be recalled to the local machine.
The server could be temporarily disabled. Explanation: The file either cannot be read, is not a
regular file, or its type is unknown to the HSM client.
System action: Tivoli Storage Manager terminates the
The HSM client migrates only regular files and does
current operation.
not migrate directories, symbolic links, and special files.
User response: Check to see whether the server has
System action: IBM Tivoli Storage Manager does not
been disabled by the system administrator, then retry
migrate this file.
the operation.
User response: None.
FMV9286K File migration has been discontinued.
FMV9291E program-name: A conflicting space
Explanation: Migration stops because the file is being
management program is already running
migrated by another process.
in the file-system file system. Re-run this
System action: Tivoli Storage Manager terminates the program later in this file system.
current operation.
Explanation: Tivoli Storage Manager detected another
User response: None. program running in the file system that cannot run at
the same time as the program your tried to initiate. The
following programs cannot run at the same time for a
FMV9287E Invalid or unsupported device.
file system:
Explanation: The logical volume device is either v dsmreconcile
invalid or unsupported. Refer to the documentation for
v dsmautomig
device type support for image backup.
v dsmmigfs remove.
System action: The logical volume operation is not
performed. Also, dsmmigfs remove cannot run while a migration
process is running in the file system.
User response: For image backup source or image
restore destination, specify a device of one of the System action: Tivoli Storage Manager will not run
supported types. the program at this time.
User response: Try running the program later.
FMV9288W File: file-name of logical size
file-logical-size and allocated size FMV9292E program-name: Cannot access lock file
file-allocated-size is too small to qualify lock-file/lock-filelock-file: error
for migration.
Explanation: Tivoli Storage Manager cannot access a
Explanation: To be eligible for migration, a file must lock file due to an error. The lock file provides
satisfy all of the following size criteria: - The file logical serialization of certain programs to prevent conflicting
size is larger than the value of the stubsize option. - processes from running at the same time.
The space that a file occupies (the allocated size) is at
least as great as the value of the minmigfilesize option. System action: Tivoli Storage Manager will not run
the program at this time.
System action: IBM Tivoli Storage Manager does not
migrate this file because migration does not free User response: Check the permissions on the
additional space. directories leading up to the lock file and also the
permissions on the program executable.
User response: Verify that the settings of the stubsize
option and the minmigfilesize option are appropriate
for your migration requirements. FMV9293E Tivoli Storage Manager space
management cannot access
ERRORPROG error-program:error
FMV9289W Object: 'dir-name' is skipped for
migration: It is a directory. Explanation: Tivoli Storage Manager encountered an
error trying to access the program specified with the
Explanation: The object is a directory. Space ERRORPROG option in your client system options file
management does not migrate directories. (dsm.sys). This message will appear only the first time
System action: IBM Tivoli Storage Manager does not this error occurs.
migrate this object because it is a directory. System action: Tivoli Storage Manager cannot send a

Chapter 6. FMV messages 539

FMV9294I • FMV9302E

severe error message to the specified error message different servers, there must be a valid backup copy of
program. the file on the migration server.
User response: Check to make sure the program exists System action: The file is skipped.
and that it accepts standard input when run. It is
User response: Back up the current file on the
usually best if ERRORPROG specifies the fully
migration server, or assign a management class to this
qualified file name of the program.
file that does not require a current backup copy. Retry
the operation.
FMV9294I No files matching 'file-name' were found.
Explanation: You entered a search pattern or file name FMV9299I Cannot get the number of migrated files
that cannot be found in the local file system. for file system file-system.
System action: Processing stopped. Explanation: Failed to get the number of migrated
files on the file system. The number is stored in the
User response: Ensure that your search pattern is
status file for the file system.
correct, or specify a new search string.
System action: If you are removing space
management from the file system, processing stops.
FMV9296W Performing image backup of the entire
Space management is not removed.
volume for volume name. The
IMAGEGAPSIZE option and used block User response: Run reconciliation to reconcile the file
image backup is not supported for system. Retry operation.
non-JFS2 file systems on AIX.
Explanation: None. FMV9300I Migrated files found in file system
file-system. Check for any error
System action: The entire volume is backed up.
encountered during recall.
User response: Refer to the client manual for
Explanation: Remove space management failed
additional information regarding the IMAGEGAPSIZE
because there are migrated files in the file system.
option and used block image backup.
Tivoli Storage Manager was unable to recall any files,
or some of the migrated files may have failed during a
FMV9297W File file-name is skipped for migration: recall operation.
No backup copy found.
System action: Tivoli Storage Manager remove
Explanation: A management class is assigned to the processing stops.
file with the attribute MIGREQUIRESBKUP set to YES.
User response: Check for error messages that occurred
This option requires that there exists a current backup
during the recall process, correct any problems, and
copy of the file before migration. However, there is no
retry the remove process.
backup copy found on the migration server. This file is
not migrated. Note: IBM Tivoli Storage Manager checks
only the migration server for a backup copy. If the FMV9301E Full VM backup of Virtual Machine
migration server and backup server are different 'vmname' failed with RC rc
servers, IBM Tivoli Storage Manager does not find a
Explanation: The Full VM backup of virtual machine
backup copy of the file.
failed.
System action: The file is skipped.
System action: The full backup of the virtual machine
User response: Back up this file on the migration finished with failures. The next virtual machine in the
server, or assign a management class to this file that vmlist will be processed. The reason for the failure is
does not require a current backup copy. Try the written to the local client error log.
operation again.
User response: Check the local client error log for
reason for the failure.
FMV9298W File file-name is skipped for migration:
Backup copy found is not current.
FMV9302E The Restore VM command does not
Explanation: A management class is assigned to the support VMBACKUPTYPE=FILE data.
file with the attribute MIGREQUIRESBKUP set to YES. VM File level restore must be run from
This option requires that there exists a current backup inside the virtual machine or with the
copy of the file before migration. However, the backup 'asnodename' option.
copy found on the migration server is an old version.
Explanation: The Restore VM function not supported
This file is not migrated. Note: IBM Tivoli Storage
for file level data.
Manager checks only the migration server for a backup
copy. If the migration server and backup server are

540 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9303E • FMV9313E

System action: The system does not process your System action: Processing stopped.
requested action.
User response: Specify a correct Hyper-V VM name or
User response: Virtual machine File level restore must VMList parameter.
be run from inside the virtual machine or with the
asnodename option. To process a full virtual machine
FMV9308E No match found for the Hyper-V VM
restore, issue the command with
name or VMList 'string' entered
VMBACKUPTYPE=FULLVM.
Explanation: No match found for the Hyper-V VM
name or VMList parameter entered.
FMV9303E Full VM restore of Virtual Machine
'vmname' failed with RC rc System action: Processing stopped.
Explanation: The Full VM restore of virtual machine User response: Specify a correct Hyper-V VM name or
failed. VMList parameter.
System action: The full restore of the virtual machine
finished with failures. The next virtual machine in the FMV9309E Pick option specified but also a value
vmlist will be processed. The reason for the failure is for the Hyper-V VM name or VMList
written to the local client error log. 'string' entered
User response: Check the local client error log for Explanation: You cannot specify the -pick option and
reason for the failure. also include a Hyper-V VM name or VMList parameter.
System action: Processing stopped.
FMV9304E VMware Converter tool not installed on
system. User response: Specify the -pick option without a
Hyper-V VM name or VMList parameter.
Explanation: VMware Converter tool install could not
be detected on system.
FMV9311E No Hyper-V VMs exist on the TSM
System action: The full virtual machine image files server
have been restored successfully at the specified
location. Explanation: No filespaces representing a Hyper-V
Virtual Machine currently exist on the TSM server.
User response: No further action is necessary. The full
virtual machine images files can be used by various System action: Processing stopped.
tools. VMware Converter tool can be installed on User response: You must successfully backup a
system. Hyper-V Virtual Machine before using this command.

FMV9305E Invalid Hyper-V VM name 'string' FMV9312S program-name: Cannot change

entered owner/group on file: file-name: error
Explanation: You entered a Hyper-V VM name string Explanation: Tivoli Storage Manager cannot change
that contains incorrect characters or contains wildcard the ownership or group, or both for the specified file.
characters. This change is necessary for space management to run
System action: Processing stopped. properly.

User response: Enter a correct Hyper-V VM name. System action: Tivoli Storage Manager cannot
continue processing.

FMV9306E Invalid Hyper-V VM list 'string' entered User response: Ensure that directory permissions
allow the file owner or group to be changed. Reissue
Explanation: You entered a Hyper-V VM list string the command.
that contains incorrect characters or contains wildcard
characters.
FMV9313E program-name: The TMP directory is full.
System action: Processing stopped.
Explanation: The TMP directory from the operating
User response: Enter a correct Hyper-V VM list. system is full.
System action: Tivoli Storage Manager stops.
FMV9307E No Hyper-V VM name or VMList
entered User response: Delete some files in the TMP directory
and retry the operation.
Explanation: No Hyper-V VM name or VMList
parameter was specified.

Chapter 6. FMV messages 541

FMV9316T • FMV9350E

specified file system is Tivoli Storage Manager space

FMV9316T File system 'file-system' undelete
managed, writable and in consistent state.
completed.
Explanation: Tivoli Storage Manager has finished
FMV9334E Wrong alias 'alias-name' received from
undeleting the file system.
the server.
System action: Tivoli Storage Manager continues.
Explanation: Tivoli Storage Manager could not build a
User response: Continue with normal operations. valid pathname for a migrated file due to the invalid
alias received from the server.
FMV9318W program-name: error encountered while System action: The processing continues with the next
undeleting file system file-system. file.
Explanation: Tivoli Storage Manager encountered an User response: If possible, perform either an orphan
error performing undelete on the file system. check reconcile or an inline incremental backup of the
initial file, so that the alias is updated on the server.
System action: Tivoli Storage Manager continues.
Then, retry the operation. Otherwise, contact Tivoli
User response: Continue with normal operation. Storage Manager support for further investigation and
problem resolution.

FMV9331W VMware vCenter or ESX Server userid

and password for VMC Host <host> FMV9347W Warning:'domain-keyword' specified on
VMC Userid <userid> could not be read Domain will be ignored when
from encrypted pwd file. connecting to VMware ESX/ESXi host.
Connect to VMware vCenter to process
Explanation: VMware vCenter or ESX Server userid this domain.
and password could not be read from encrypted
password file. Explanation: None.
System action: Processing stops. System action: Domain keyword is ignored.
User response: Use dsmc SET PASSWORD -type=VM User response: Connect to VMware vCenter to
'vCenter hostname' 'userid' 'password' to save process this domain.
encrypted password.
FMV9349I Selective Recall completed
FMV9332E VMware vCenter or ESX Server userid
Explanation: The selective recall was completed.
and password not set. Use dsmc SET
PASSWORD -type=VM 'vCenter System action: Tivoli Storage Manager recalled the
hostname' 'userid' 'password' to save files.
encrypted password.
User response: Continue with normal operations.
Explanation: VMware vCenter or ESX Server userid
and password could not be read from encrypted
FMV9350E Backup operation failed due to volume
password file.
mixture. Please refer to explanation
System action: Processing stops. section for additional information.
User response: Use dsmc SET PASSWORD -type=VM Explanation: IBM Tivoli Storage Manager failed to
'vCenter hostname' 'userid' 'password' to save create the backup because of the mixture of volumes
encrypted password. was detected. Some volumes selected meet the
requirements for importing snapshots only when
needed and some do not. This situation occurs when a
FMV9333E Unable to re-create 'file-name' as a stub
backup operation is requested and the "Import VSS
file due to Unix-system-call() failure;
snapshots Only When Needed" feature is enabled and
errno: error; reason: 'error-reason'.
not all the volumes involved in the backup operation
Explanation: Tivoli Storage Manager was unable to are managed by a VSS Hardware Provider that
re-create the specified file as a stub due to an error. supports transportable snapshots. Additionally the
situation can also occur in a clustered environment
System action: The processing continues with the next during a backup operation, when not all the volumes
file. involved in the backup operation are managed by a
User response: Please, look into the dsmerror.log for VSS Hardware Provider that supports transportable
further error details. If the affected file path doesn't snapshots.
exist, restore it from your backup (if any) or re-create it System action: processing stops.
manually, then re-try the operation. Make sure that the

542 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9351E • FMV9360W

User response: Try the operation again by splitting the

FMV9355E VMware vStorage VI Web Service API
backup operation. Ensure that all the volumes involved
reported error message: vstor-api-msg
in the backup operation are either managed by a
Hardware Provider that supports transportable Explanation: The VMware vStorage VI Web Service
snapshots or that all the volumes involved in the API reported an error with the specified message text.
operation do not support transportable snapshots.
System action: Processing stops.
Additionally you may also turn off the "Import VSS
snapshots Only When Needed" feature to allow the User response: Check the dsmerror log file for
backup to allow the mixure. additional information, and contact the IBM Tivoli
Storage Manager administrator with the information
provided in this message.
FMV9351E Data was not available on server and
was skipped.
FMV9356E A VMware vStorage API error was
Explanation: The data to be restored is not available
reported.
on the server, so it will not be restored.
Explanation: A VMware vStorage API was reported.
System action: The data is skipped, and the restore
See other messages displayed and logged for additional
processing continues with the next object to be restored.
information about the problem.
User response: Contact your Tivoli Storage Manager
System action: Processing stops.
administrator.
User response: Check the dsmerror log file for
additional information, and contact the IBM Tivoli
FMV9352E SAN or HOTADD was chosen as the
Storage Manager administrator with the information
transport for at least one of the disks in
provided in this message.
the operation, but the SAN policy is not
OnlineAll for this datamover. SAN or
HOTADD cannot be used unless the FMV9357E The dsmscout executable cannot be used
SAN policy is OnlineAll. on the user level.
Explanation: SAN or HOTADD was chosen as the Explanation: The dsmscout process is exclusively
transport because either the default transport setting started by the dsmmonitord.
was used, or it was specified in the
VMVSTORTRFMVPORT option. In order to use SAN or System action: Tivoli Storage Manager aborts the
HOTADD as the transport mode, the SAN policy must operation.
be set to OnlineAll. User response: None.
System action: Restore processing stops.
User response: Set the SAN policy to OnlineAll, or set FMV9359W program-name: file-system: high threshold
VMVSTORTRFMVPORT to something other than SAN high-threshold exceeds recommended
or HOTADD, such as NBD. Then try the restore maximum max-threshold maximum
operation again. percentage.
Explanation: System performance can be impacted.
FMV9353I Selective Recall stopped by user. There can be delays from waiting for demand
migration.
Explanation: You requested to stop the selective recall
operation. System action: Processing continues.

System action: Selective recall stopped. User response: Set the migration high threshold lower
than the file system capacity.
User response: Continue with normal operations.
FMV9360W program-name: file-system: configured
FMV9354E The node or owner name 'node' specified low-threshold low threshold is below the
in the SET ACCESS command exceeds recommended minimum floor-percent low
the maximum allowed length (64). threshold.
Explanation: An invalid node or owner name has Explanation: Tivoli Storage Manager low threshold is
been entered in the SET ACCESS command. not recommended to be less than teh minimum space
required by this file system and may result in endless
System action: Processing stops.
attempts to find migration candidates. Usage of the file
User response: Enter the SET ACCESS command system may be higher than the recommended
using the correct node or owner name. minimum of low threshold on GPFS and Veritas

Chapter 6. FMV messages 543

FMV9361W • FMV9370W

because these types of file system allocate some space

FMV9364E Failure initializing virtual machine
for metadata.
environment. Refer to dsmerror.log for
System action: Processing continues. detailed error messages.

User response: Set the migration low threshold higher Explanation: Failure initializing virtual machine
than the recommended-minimum size of the file environment. Refer to dsmerror.log for detailed error
system. messages.
System action: The backup can not continue.
FMV9361W program-name: file-system: the configured
User response: Refer to dsmerror.log for detailed error
pre-mig premigration is greater than the
message.
difference between the configured
low-threshold low threshold and the
recommended-minimum size of the file FMV9365E VMware vStorage API error for virtual
system Min_size. machine 'VM-name'. Tivoli Storage
Manager function name : function-name
Explanation: Tivoli Storage Manager premigration
Tivoli Storage Manager file : file-name
percentage below the low threshold may not leave
(line-number) API return code : TSM-rc
sufficient space for the file system, and can result in
API error message : function-desc
endless attempts to find migration candidates. Usage of
the file system may be higher than the recommended Explanation: None.
minimum of low threshold on GPFS and Veritas
System action: Processing stops.
because these types of file system allocate some space
for metadata. User response: Contact the Tivoli Storage Manager
administrator with the information provided in this
System action: Processing continues.
message.
User response: Lower the premigration setting.
FMV9368W WARNING: VMware Host Userid
FMV9362W program-name: file-system: MAXFILES <hostuserid> read from pwd file different
max-files is less than used inodes used than VMCUSER option value
inodes in the file system. MAXFILES <vmcuserid>. Using VMCUSER option
will be set to the minimum possible value.
value.
Explanation: None.
Explanation: Tivoli Storage Manager The specified
System action: Processing stops.
maxfiles value is below the number of files already
existing in the file system. The value will be ignored, User response: Contact the Tivoli Storage Manager
and CFI will default to the minimum possible size administrator with the information provided in this
according to the number of currently used inodes. message.
System action: Processing continues.
FMV9369W WARNING: VMware VirtualCenter or
User response: Increase the value of maxfiles.
ESX Server User Password for VMC
Host <host> VMC Userid <userid> set in
FMV9363W program-name: file-system: MAXFILES options file.
max-files is more than files total available
Explanation: None.
inodes in the file system. MAXFILES
will be set to the maximum possible System action: Processing stops.
value.
User response: Contact the Tivoli Storage Manager
Explanation: Tivoli Storage Manager The specified administrator with the information provided in this
maxfiles value is above the number of available inodes message.
in the file system. The value will be ignored, and CFI
will default to the maximum size that corresponds to
the number of available inodes. FMV9370W Use Preferences Editor or dsmc SET
PASSWORD -type=VM 'VirtualCenter
System action: Processing continues. hostname' 'userid' 'password' to save
encrypted password.
User response: Decrease the value of maxfiles.
Explanation: The VMCPW option was found either in
an option file or on the command line. While this
method of entry is allowed, it presents a security risk

544 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9371I • FMV9379E

because the password is in plain text and not Explanation: Failure initializing VMware vStorage API
encrypted. environment.
System action: The option is accepted and the VMC System action: The backup can not continue.
password is used in the current session.
User response: Make sure the VMware
User response: To save the encrypted password, use 'vstor2-mntapi20-shared.sys' service is installed and
the Preferences Editor VM Backup panel or the running. Install the VMware vStorage API runtime
command: dsmc SET PASSWORD -type=VM files.
'VirtualCenter hostname' 'userid' 'password'
FMV9376E The Backup VM command domain
FMV9371I program-name: file-system: The specified keyword 'domain-keyword' was specified,
MAXFILES value is 0. The CFI size will but this domain does not contain any
be calculated automatically now. virtual machines. This error can also
occur if the value for the VMHOST
Explanation: Tivoli Storage Manager The specified
parameter is not specified as an IP
maxfiles value is 0, which means that the CFI size is
address or as a fully qualified domain
managed automatically now.
name.
System action: Tivoli Storage Manager continues.
Explanation: The command cannot complete because
User response: none. the virtual machine could not be found.
System action: Processing stops.
FMV9372E Unable to create the virtual machine to
User response: Try the operation again. Ensure that
be restored due to an invalid host name,
the value for the VMHOST parameter is specified as an
datacenter name, or datastore name.
IP address or as a fully qualified domain name. The
Explanation: IBM Tivoli Storage Manager was unable host name that you specify must match the host name
to create the virtual machine to be restored because an as it is displayed in the vCenter server in the Host and
invalid host name, datacenter name, or datastore name Clusters view. This could be the fully qualified host
was specified. Check the dsmerror log file for name (FQDN), the shortened domain name, or the host
information on the specific reason for the failure. IP address.

System action: Processing stops.

FMV9377E No virtual machine is specified on the
User response: Check the dsmerror log file for string command or the virtual machine
additional information, and contact the IBM Tivoli domain list could not be processed.
Storage Manager administrator with the information
provided in this message. Explanation: No virtual machine found with name or
specified in domain option.

FMV9373E VMware vStorage API environment System action: Processing stops.

could not be found. Install the VMware
User response: Specify a correct VM name or domain
VDDK and copy VMware runtime
option.
libraries from the VDDK bin directory
to Tivoli Storage Manager baclient
directory. FMV9378E Unexpected error while fingeprinting
the data
Explanation: Failure initializing virtual machine
environment. Explanation: There was an error while fingerprinting
the data. See the error log for more information.
System action: The backup can not continue.
System action: The object is not backed up.
User response: Make sure the VMware VDDK is
installed and copy VMware runtime libraries from User response: Retry the operation. Retry the
VDDK bin directory to Tivoli Storage Manager baclient operation without client-side deduplication. If the
directory. problem persists, contact Tivoli Storage Manager
technical support.
FMV9374E VMware vStorage virtual storage driver
service is not running or could not be FMV9379E Unexpected error while deduplicating
found. Make sure VMware the data
'vstor2-mntapi20-shared.sys' service is
Explanation: There was an error while deduplicating
installed and running. Install the
the data. See the error log for more information.
VMware vStorage API runtime files.
System action: The object is not backed up.

Chapter 6. FMV messages 545

FMV9380E • FMV9387W

User response: Retry the operation. Retry the used and unused blocks of the disk.
operation without client-side deduplication. If the
System action: The backup continues.
problem persists, contact Tivoli Storage Manager
technical support. User response: See the error log dsmerror.log for
information about why the changed block data is not
obtained.
FMV9380E The virtual machine that was specified
on the string command could not be
found. FMV9385W Error returned from VMware vStorage
API for virtual machine 'VM-name' in
Explanation: The command cannot complete because
vSphere API function
the virtual machine could not be found.
__ns2__QueryChangedDiskAreas.
System action: Processing stopped. RC=API return code, Detail message: API
message
User response: Try the operation again. Specify a
correct VM name or DOMAIN option. This error can Explanation: None.
also be caused by incorrect settings for the VMHOST,
System action: CBT processing stops.
VMHOSTCLUSTER, VMFOLDER or VMDATASTORE
options. The VMHOST option value must be specified User response: Contact the Tivoli Storage Manager
as an IP address or as a server name that is in fully administrator with the information provided in this
qualified domain name (FQDN) format. The host name message.
that you specify must match the host name as it is
displayed in the vCenter server in the Host and
Clusters view. This could be the fully qualified host FMV9386W Changed block tracking is not
name (FQDN), the shortened domain name, or the host supported for virtual machine 'virtual
IP address. machine name'. A FULL backup of the
disk will be performed and will include
both used and unused areas of the disk.
FMV9381I The value set for vmlist option will be
migrated to the new domain option. Explanation: IBM Tivoli Storage Manager was unable
to obtain Changed Block Tracking(CBT) data for the
Explanation: New option has been set. specified virtual machine because changed block
tracking is not supported. RDM disks in physical
System action: Processing continues.
mode, virtual disks attached to shared virtual SCSI bus,
User response: None. and VMs with hardware version 6 or earlier are not
supported. The backup continues, but instead of
backing up just the used blocks (in the full VM backup
FMV9383E Required files for VMware vStorage
case), or just the changed blocks (in the incremental
virtual machine backup could not be
VM backup case), the entire virtual machine is backed
found. Run the Tivoli Storage Manager
up. This backup includes both the used and unused
install selecting the vmwaretools feature
blocks of the disk.
or install the VMware VDDK.
System action: The backup continues.
Explanation: Failure initializing virtual machine
environment. User response: See the error log dsmerror.log for
information about why the changed block data is not
System action: The backup can not continue.
obtained.
User response: Run the Tivoli Storage Manager install
selecting the vmwaretools feature. VMware.
FMV9387W An incremental backup for virtual
machine 'virtual machine name' is not
FMV9384W Unable to get VMware Changed Block possible because changed block
Tracking(CBT) data for virtual machine information cannot be obtained. A full
'virtual machine name'. Full VM backup VM backup is attempted instead.
continues, and includes both used and
Explanation: Changed block information is required to
unused areas of the disk.
perform an incremental backup, but the information
Explanation: IBM Tivoli Storage Manager was unable could not be obtained from the virtual machine. The
to obtain Changed Block Tracking(CBT) data for the information can be missing if two nodes back up the
specified virtual machine. The backup continues, but same virtual machine. One node runs a daily
instead of backing up just the used blocks (in the full incremental backup, and the other node runs a weekly
VM backup case), or just the changed blocks (in the full backup. After the weekly full backup runs, the next
incremental VM backup case), the entire virtual daily backup cannot obtain changed block information,
machine is backed up. This backup includes both the so a full backup is run instead of an incremental
backup. Subsequent daily backups will be incremental

546 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9388E • FMV9395E

until the next weekly full backup.

FMV9391W Linux guest OS with EFI Boot enabled
System action: The backup continues as a full backup is not fully supported by TSM VMware
instead of an incremental backup. backup. Manual steps may be required
following restore to enable the virtual
User response: Search the IBM Tivoli Storage Manager machine to power on correctly.
support site (http://www.ibm.com/support/entry/
portal/product/tivoli/tivoli_storage_manager) for this Explanation: A restored Linux guest OS with EFI boot
message number, for other possible causes of this error. enabled may not successfully start. Manual steps are
required to successfully boot the guest OS.

FMV9388E The management class 'management class System action: Restore processing continues.
name' specified for the 'option name'
User response: Following guest OS restore: remove
option is invalid, or does not have a
and reattach the guest Linux boot disk, select Guest
backup copy group.
Boot Option to enter EFI setup configuration on next
Explanation: The management class name for the boot, power on the guest, enter EFI Boot Maintenance,
specified option does not exist, or it exists but does not add Boot Device, select unnamed volume, give it a
have a valid backup copy group. label, save and commit changes, continue with boot.

System action: Processing stops.

FMV9392W No backupset name entered.
User response: Verify that the specified management
class name is valid, and that it contains a valid backup Explanation: You must provide a backupset for this
copy group. operation.
System action: Processing stops.
FMV9389W The DEDUP backup attempt was
User response: Specify a valid backupset name.
unsuccessful for virtual machine 'virtual
machine name'. Retry #retry attempt number
with DEDUP disabled. FMV9393W Incorrect backupset name entered.
Explanation: The attempt to backup the virtual Explanation: The backupset name provided was
machine with DEDUP enabled was unsuccessful. invalid. Wildcards are not allowed.
Instead of failing the backup right away, an attempt is
System action: Processing stops.
being made to backup the virtual machine with
DEDUP disabled. User response: Specify a valid backupset name.
System action: Processing continues with DEDUP
disabled. FMV9394W No backupset file or device name
entered.
User response: Check the log files for messages as to
why DEDUP failed. If future attempts to backup using Explanation: You must provide a backupset file or
DEDUP fail, contact your system administator. device name for this operation.
System action: Processing stops.
FMV9390W The DEDUP backup attempt was
unsuccessful for virtual machine 'virtual User response: Specify a valid backupset file or device
machine name'. Retry #retry attempt number name.
with DEDUP still enabled.
Explanation: The attempt to backup the virtual FMV9395E The filespace has been migrated to the
machine with DEDUP enabled was unsuccessful. incremental forever model;
Instead of failing the backup right away, an attempt is MODE=FULL and MODE=INCR are not
being made to retry the backup of the virtual machine valid.
with DEDUP still enabled. Explanation: You must run only incremental forever
System action: Processing continues with DEDUP still backup types (IFINCR or IFFULL) if the filespace has
enabled. been migrated to the incremental forever type.

User response: Check the log files for messages as to System action: Processing stops.
why DEDUP failed. If future attempts to backup using User response: Specify either MODE=IFFULL or
DEDUP fail, contact your system administator. MODE=IFINCR.

Chapter 6. FMV messages 547

FMV9396W • FMV9404E

FMV9396W Virtual machine 'VM' is not running. FMV9400W program-name: Recovered program-name.
IBM Tivoli Storage Manager The daemon was either not started or in
Application Protection will not be used corrupted state.
while backing up this VM.
Explanation: Tivoli Storage Manager HSM daemon
Explanation: IBM Tivoli Storage Manager Application breakdown with automatic recovery by the dsmwatchd.
Protection can only protect VMs that are running.
System action: Restarting the daemon.
System action: IBM Tivoli Storage Manager
User response: Continue with normal operation.
Application Protection uses the VMWare tools to
provide application consistency.
FMV9401E program-name: Cannot kill recall daemon.
User response: Turn on the virtual machine or exclude
it from Tivoli Storage Manager application protection Explanation: Tivoli Storage Manager A request for
by removing the INCLUDE.VMTSMVSS option for this killing the recall daemon failed. This may occur during
virtual machine. If you want logs to be truncated use node failover.
INCLUDE.VMTSMVSS to protect this machine.
System action: none.

FMV9397W Tivoli Storage Manager application User response: Continue with normal operation unless
protection cannot protect this machine. further errors occur.
Virtual machine 'VM' does not have
operating system or applications FMV9402E program-name: Cannot notify process name
supported by Tivoli Storage Manager to recover HSM operations on a failing
application protection. node.
Explanation: The application protection can be used Explanation: In order to assume the functionality of a
only for virtual machines that have operating systems failing partner node, the dsmwatchd daemon must
or applications that are supported by IBM Tivoli notify the local daemons.
Storage Manager application protection. Refer to the
product documentation for the list of supported System action: none.
operating systems and applications. User response: Communication cannot be established
System action: IBM Tivoli Storage Manager will use with the HSM daemon specified in this message. Check
the VMware Tools to provide application consistency. whether the target daemon is running. Start or restart
the target daemon as appropriate. If the problem
User response: Exclude the virtual machine from persists, restart the GPFS cluster.
application protection by removing the
INCLUDE.VMTSMVSS option for this virtual machine.
FMV9403E program-name: The local HSM
functionality cannot be recovered.
FMV9398E IBM Tivoli Storage Manager application Trying to initiate failover to another
protection failed to initialize on virtual node.
machine 'VM'. See the error log for more
details. Explanation: Tivoli Storage Manager If the GPFS
daemon crashes or the local HSM daemons cannot
Explanation: Tivoli Storage Manager application perform their function for whatever reason the
protection encountered an error during initialization. dsmwatchd will try to migrate the functionality to
System action: Processing stops. another node.

User response: See the Tivoli Storage Manager error System action: Migrate HSM functionality to another
log for more details. Correct the error(s) and try the node.
operation again. User response: Check failure node. It may be
necessary to recover the local GPFS daemon.
FMV9399W program-name: lock file access error for
operation value on path value value with FMV9404E Error creating the specified Virtual
errno text value. Machine. See log files for more
Explanation: A lock file operation has failed. information.

System action: Tivoli Storage Manager logs the Explanation: An error was encountered creating the
condition and continues processing, or exits if directory Virtual Machine. Look in the dsmerror.log for
not found. additional information on why the Virtual Machine
could not be created.
User response: Correct the configuration.
System action: Processing stops.

548 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9405I • FMV9417E

User response: Check the dsmerror.log for more recover from the failure situation during the local
specific messages on why the virtual machine could not takeover operation.
be created.
System action: None.
User response: Check failure node for consistency.
FMV9405I program-name: The takeover of filesystem
file system started.
FMV9414E program-name: Unable to create file-name
Explanation: The local activation of the specified file
in the SDR. Aborting ...
system started successfully.
Explanation: An update of an SDR object failed.
System action: Tivoli Storage Manager on the local
node will try to activate the file system that is space System action: Aborting operation.
managed on another node.
User response: Check SDR consistency.
User response: None.
FMV9415E Failed to copy 'source' to 'destination' with
FMV9410W VMware Tools are either not runnning VMware RC=rc on the virtual machine.
or out-of-date on virtual machine 'VM'.
IBM Tivoli Storage Manager application Explanation: IBM Tivoli Storage Manager was unable
protection cannot be used. to copy a file to the virtual machine.

Explanation: IBM Tivoli Storage Manager application System action: Processing stops.
protection requires that VMware tools are installed and User response: Verify that the source file exists and
running with an up-to-date version on the virtual the destination is accessible. Restart the virtual machine
machine. and try the operation again.
System action: Tivoli Storage Manager will not
provide application consistency. Application logs are FMV9416E Cannot create the directory 'source' on
not truncated. the virtual machine with Windows
User response: Install and/or upgrade and/or start RC=rc
VMware Tools on the virtual machine or exclude it Explanation: IBM Tivoli Storage Manager client was
from the application protection by removing the unable to create the specified directory on the virtual
INCLUDE.VMTSMVSS option for this virtual machine. machine. It is possible that the directory exists and is
locked by a process.
FMV9411E VSS provider registration failed. System action: Processing stops.
Command 'command' failed with
Windows RC=return code User response: Verify the the specified directory does
not exist on the virtual machine. Restart the virtual
Explanation: IBM Tivoli Storage Manager was unable machine and try the operation again.
to register the VSS provider on the virtual machine.
System action: Processing stops. FMV9417E IBM Tivoli Storage Manager application
User response: Restart the virtual machine and try the protection could not freeze the VSS
operation again. writers on the virtual machine named
'VM'. See the Tivoli Storage Manager
error log for more details.
FMV9412E program-name: Failover is disabled on the
local machine. Aborting failover ... Explanation: IBM Tivoli Storage Manager application
protection encountered an error while freezing the VSS
Explanation: Tivoli Storage Manager Failover writers.
operations were disabled either by the system or the
user. System action: Processing stops

System action: None. User response: Use the 'vssadmin list writers'
command to determine if any VSS writers detect errors
User response: Check failover policy if necessary. on he virtual machine. Restart the VM. Retry the
operation. If the retry fails, see the error log for details
about the errors.
FMV9413W program-name: The remote node was able
to recover from failure situation.
Aborting takeover ...
Explanation: The remote dsmwatchd was able to

Chapter 6. FMV messages 549

FMV9418W • FMV9428E

FMV9418W program-name: Cannot access the GPFS FMV9422I program-name: The rollback of filesystem
SDR for writing. It might be locked, or file system started.
the var filesystem might be full.
Explanation: The local activation of the specified file
Explanation: The GPFS configuration is stored in the system started successfully.
SDR. This file can be accessed as soon as it is possible
System action: Tivoli Storage Manager on the local
to set a certain SDR lock. If a second process holds this
node will try to activate the file system that is space
lock, access to the file is denied until the lock is
managed on another node.
released. Use the GPFS command - mmcommon
showLocks - to show which process holds the lock User response: None.
currently.
System action: None. FMV9423E program-name: Setting the default
partition name failed! Aborting
User response: Wait. If the situation does not get
operation ...
resolved within a reasonable amount of time (about 1
min.), examine the var file system. If it is full, free up Explanation: The application needs to have access to
some space. Otherwise use the command dsmmigfs the SP Group Services. In this context it tries to extract
SDRreset. This command resets all activated locks in the default partition name for the local system as
the SDR for the local GFPS node set. provided by spget_syspar. The data extraction failed.
System action: Aborting operation.
FMV9419E program-name:The filesystem
filesystem-name is either already managed User response: Check node consistency.
locally or under the control of a remote
HSM instance. FMV9424E program-name: It was not possible to
Explanation: A GPFS filesystem can be managed just send a message to the SP Group
once. Services. This is a severe error.

System action: Aborting operation. Explanation: The Failover environment requires

proper access to the SP Group Services. The
User response: Execute dsmmigfs query -detail to distribution of a message failed.
have a look at the current HSM configuration within
the local GFPS node set. System action: Aborting operation.
User response: If the problem persists, verify SP
FMV9420E program-name: An update of the Group Service is accessible and is not overwhelmed. If
configuration files in the SDR is not the problem persists, reboot the GPFS cluster.
allowed as long as failover is disabled
on the local machine. FMV9425E program-name: It was not possible to
Explanation: You cannot update configuration files in notify the dsmwatchd in order to
the SDR when failover is disabled on the local machine. distribute a message within the failover
group. The data of the current operation
System action: Tivoli Storage Manager Aborting may get lost.
operation.
Explanation: Some HSM commands need to inform
User response: Do nothing, or activate failover by the dsmwatchd about the current operation. This
using dsmmigfs enableFailover before running notification failed.
dsmmigfs SDRupdate.
System action: Aborting operation.

FMV9421W program-name: Recovered from Lock on User response: Restart the GPFS daemon and check
SDR File file-name that the DMApi support is active by executing
/usr/lpp/mmfs/bin/mmlsfs deviceName.
Explanation: This output relates to FMV9418W. A
previously blocked SDR file got unlocked.
FMV9428E program-name: The takeover of filesystem
System action: Tivoli Storage Manager continues. file system failed to start.
User response: None. Explanation: The local activation of the specified file
system failed to start. Please, note that only file systems
which are space managed on another node within the
same cluster can be taken over. Additionally, the file
system must be mounted locally.

550 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9431E • FMV9451E

System action: Tivoli Storage Manager will not take

FMV9442E program-name: It appears that another
over the file system.
dsmmigfs add/rem/update command is
User response: Make sure the file system is mounted in process within the local GPFS
locally and managed with the TSM client for space nodeset. Please wait a few moments,
management on another node within the same cluster then repeat the operation. If a previous
and retry the operation. dsmmigfs command was aborted, there
could be a stale lock in the SDR. If so,
run dsmmigfs SDRreset to fix the
FMV9431E IBM Tivoli Storage Manager application problem.
protection failed to thaw VSS writers on
virtual machine 'VM'. See the Tivoli Explanation: There can only be one instance of
Storage Manager error log for more dsmmigfs add/rem/update running within a GPFS
details. nodeset at the same time.

Explanation: IBM Tivoli Storage Manager application System action: Aborting operation.
protection encountered an error while thawing VSS
User response: Wait for a bit and try again. If no other
writers.
instance of dsmmigfs is running within the local GPFS
System action: Processing stops nodeset run dsmmigfs SDRreset.

User response: See the error log for more details.

Verify that all VSS writers are not reporitng errors by FMV9443E program-name: The operation cannot be
running command 'vssadmin list writers'. Restart the executed in a deactivated failover
virtual machine and try the operation again. If the retry environment.
fails, see the error log for details about the errors.
Explanation: The operation relies on an active failover
environment.
FMV9432W IBM Tivoli Storage Manager application
System action: Aborting operation.
protection failed to truncate application
logs on virtual machine 'VM'. User response: Run dsmmigfs enableFailover on the
local node and repeat the operation.
Explanation: IBM Tivoli Storage Manager application
protection encountered an error while completing VSS
backup operation. The applications were successfully FMV9449W program-name: Forced deactivation of the
quiesced, but their logs were not truncated. local failover environment!
System action: Application logs are not truncated. Explanation: Tivoli Storage Manager Failover was
initiated or a problem with the group services occurred.
User response: See the Tivoli Storage Manager error
log for more details. Verify that all VSS writers are not System action: Continuing failover or aborting
reporting errors by running command 'vssadmin list operation.
writers'. Restart the virtual machine and try the
User response: Check HSM and SP Group Services
operation again. If the retry fails, see the error log for
environments. Execute dsmmigfs enableFailover after
details about the errors. On the guest VM, verify that a
resolving the problem.
mounted volume is not online. Use the Recovery Agent
to dismount and remove any existing mount
directories. Then, try the backup operation again. FMV9450W program-name: No eligible filesystem for
takeover.
FMV9433E program-name: dm_send_msg failed with Explanation: None of the locally mounted GPFS
errno Errno. filesystems matches with the remotely managed
filesystems of the failure node.
Explanation: Unable to execute DMApi call.
System action: Aborting takeover operation.
System action: Aborting operation.
User response: Check that the filesystems of the
User response: Check consistency of the GPFS
remote failure node get managed elsewhere within the
daemon.
node set.

FMV9451E program-name: GPFS or the SP switch is

down locally. Aborting takeover
activities ...
Explanation: Tivoli Storage Manager GPFS is not
functional locally.

Chapter 6. FMV messages 551

FMV9452E • FMV9469E

System action: Aborting takeover operation.

FMV9458I program-name: Responsiveness Service
User response: Check switch and VSD status. The successfully started.
local system must be unfenced.
Explanation: Starting and joining the Responsiveness
Service to monitor other nodes for failover was
FMV9452E program-name: The DMApi is not successful. The node will now try to establish a
functional locally. Aborting takeover connection to the service of other nodes.
activities ...
System action: Processing continues.
Explanation: The operation stopped because the
User response: None.
DMApi interface is not accessible.
System action: Aborting takeover operation.
FMV9459E Using the specified MAXCANDIDATES
User response: Check GPFS status. parameter would produce an
out-of-space condition in the parent
filesystem of /etc/adsm/SpaceMan/
FMV9453E program-name: Could not determine the candidatesPool. Based on the current
GPFS storage pool id for file 'file-path'. free space situation the maximum value
Reason: reason for the MAXCANDIDATES parameter is
Explanation: The processed file does not exist or is value.
located on a file system without storage pool support. Explanation: Tivoli Storage Manager The
System action: The requested operation stops. automigration candidate pools for the selected
filesystem require MAXCANDIDATES/10 KB plus a
User response: Please check the input parameters and safety buffer of 5 MB of memory under
if DMAPI is enabled on the file system. /etc/adsm/SpaceMan/candidatesPool, which exceeds
the available space.
FMV9454W program-name: Performing System action: Tivoli Storage Manager Abort
synchronization between the local and operation.
global file event handling.
User response: Increase the filesystem size or choose a
Explanation: The local node received a request from a smaller value for the MAXCANDIDATES parameter.
remote node to synchronize with the global file event You may also create a dedicated filesystem with
handling (DMApi event disposition). sufficient space for the migration pools under
System action: Synchronization proceeds. /etc/adsm/SpaceMan/candidatesPool. Kill the
dsmscout processes after performing this option.
User response: None.

FMV9462E Failover functionality is not supported

FMV9455E program-name: Unable to join the local with this HSM release.
failover group with rc=return-code!
Explanation: The Tivoli Storage Manager user ran
Explanation: SP Group services reported a problem dsmmigfs with the failover flag on an unsupported
accessing/creating an HSM group. platform.
System action: Aborting operation. System action: Tivoli Storage Manager ends the
User response: Check PSSP environment on the local operation.
node. User response: None.

FMV9457E program-name: Could not determine the FMV9469E Warning! Unable to write a complete
storage pools of file system 'file-system'. migration candidate list due to low
Reason: reason space in the parent filesystem of name.
Explanation: The specified file system is not a GPFS Explanation: Tivoli Storage Manager Low space in
file system or has an old GPFS version. filesystem which stores the migration candidates files.
System action: The requested operation stops. System action: Tivoli Storage Manager The executable
User response: Please update to a supported version writes a partial migration candidates list.
of GPFS. User response: Increase the filesystem size or create a
dedicated filesystem with sufficient size under the
given path.

552 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9472I • FMV9491E

FMV9472I program-name: Updating failover FMV9487W program-name: cannot query the right on
information for Node ID: node session session for file handle = filehandle
token = token. Reason : error
Explanation: Failover status information for remote
node was updated. Explanation: Tivoli Storage Manager space
management cannot query the right on a file.
System action: This message is for informational
purposes only. System action: Processing of the file is interrupted.
User response: No action is required. User response: Continue with normal operation.

FMV9474E program-name: Lost my session with FMV9488E Java Runtime Environment (JRE) was
errno: errno . Trying to recover. not found. File VM does not exist.
Explanation: The DMAPI session is not valid. Explanation: JRE was not found in the TSM
installation directory.
System action: Trying to recover session.
System action: Processing stops
User response: Check the failure node. You might
have to recover the local GPFS daemon. User response: Re-install the product or install a
required version of JRE and try again. If JRE is already
installed on your machine, then make sure the PATH
FMV9475W IBM Tivoli Storage Manager application
environment variable contains path to javaw.exe.
protection failed to cleanup after a VSS
backup on virtual machine VM.
FMV9489E Java Runtime Environment (JRE) was
Explanation: IBM Tivoli Storage Manager application
not found.
protection encountered an error while cleaning up after
a VSS backup operation. Explanation: JRE was not found.
System action: None System action: Processing stops
User response: See the Tivoli Storage Manager error User response: If you have already installed JRE,
log for more details. Restart the virtual machine and try please verify that the \"java\" executable is set in the
the operation again. If the problem persists, contact system PATH, otherwise install the required JRE
IBM technical support for further assistance. version.

FMV9476I program-name: Recovered my DM session FMV9490E Cannot find httpagent.jar in the TSM
sid. client installation directory.
Explanation: DMAPI session is recovered. Explanation: The required file was not found.
System action: This message is for informational System action: Processing stops
purposes only.
User response: Re-install the product or install a
User response: No action is required. required version of JRE and try again.

FMV9480E program-name: The rollback of filesystem FMV9491E The password credentials for virtual
file system failed to start. machine 'guest VM name' could not be
found. Use dsmc SET PASSWORD
Explanation: The local activation of the specified file
-type=VMGUEST 'VM guest name'
system failed to start. Please, note that a rollback can
'userid' 'password' to save encrypted
only be performed after the space management of the
password.
file system was moved from the local node to another
node during failover. Additionally, the file system must Explanation: The required password was not found.
be mounted locally.
System action: Processing stops
System action: Tivoli Storage Manager will not roll
User response: Use dsmc SET PASSWORD
back the file system.
-type=VMGUEST 'VM guest name' 'userid' 'password'
User response: Make sure the file system is mounted to save encrypted password. And then retry the
locally and managed with the TSM client for space 'backup vm' operation.
management on another node within the same cluster
and retry the operation.

Chapter 6. FMV messages 553

FMV9492E • FMV9499W

FMV9492E Destination size is not equal to source FMV9496E Unable to lock virtual machine VM for
application protection.
Explanation: The space allocation for the selected
destination is not the same as the source. Explanation: The virtual machine is being backed up
by another process. Only one process is allowed to use
System action: The restore operation is not performed.
TSM application protection during a backup of a
User response: Choose a different destination which is virtual machine at a time.
equal in size to the source.
System action: Processing stops
User response: There is already another virtual
FMV9493E The credentials found for virtual
machine backup in process via another datamover.
machine 'guest VM name' are incorrect.
Please wait for the other virtual machine backup to
Verify the credentials and use dsmc SET
complete and re-try the operation. Or there was a crash
PASSWORD -type=VMGUEST 'VM
or CTRL+C during the previous virutal machine
guest name' 'userid' 'password' to
backup. Please wait 10 minutes and re-try the
update the username and password.
operation.
Explanation: The supplied credentials are incorrect.
Failed to authenticate to guest VM using these
FMV9497W Virtual machine 'VM' resides on an ESX
credentials.
Server or vCenter that is not supported
System action: Processing stops by TSM application protection. IBM
Tivoli Storage Manager application
User response: Use dsmc SET PASSWORD protection will not be used.
-type=VMGUEST 'VM guest name' 'userid' 'password'
to update the username and password. And then retry Explanation: Refer to the product documentation for
the 'backup vm' operation. the list of supported ESX and vCenter versions.
System action: IBM Tivoli Storage Manager will use
FMV9494E Command 'command' completed with the VMware Tools to provide application consistency.
RC=return code on virtual machine 'guest
User response: Exclude the virtual machine from
VM name'.
application protection by removing the
Explanation: A remote command either timed out or INCLUDE.VMTSMVSS option for this virtual machine.
failed.
System action: Processing stops FMV9498W A valid IBM Tivoli Storage Manager for
Virtual Environments license file
User response: Increase the value of VMTIMEOUT (license-file) cannot be located. IBM
option and try the operation again. Tivoli Storage Manager application
protection will not be used.
FMV9495E Failed to login to virtual machine 'guest Explanation: The license file was not found, or cannot
VM name' because the VMware Tools are be opened because of permissions, or the file is
not running in the guest machine. corrupted.
Verify that the VMware tools are
running and that no other program has System action: IBM Tivoli Storage Manager will use
access or is making any changes to this the VMware Tools to provide application consistency.
VM.
User response: Check permissions on file. See if the
Explanation: Failed to login to virtual machine license file is in the correct place.
because the VMware Tools are not running in the guest
machine.
FMV9499W VMware tools on virtual machine 'VM'
System action: Processing stops need to be updated. IBM Tivoli Storage
Manager application protection will not
User response: Make sure that the VMware tools are be used.
running and that no other program has access or is
making changes to this VM. And then retry the 'backup Explanation: IBM Tivoli Storage Manager application
vm' operation. protection requires that VMware Tools are up to date.
System action: IBM Tivoli Storage Manager will use
the VMware Tools to provide application consistency.
User response: Update VMware Tools on the virtual
machine

554 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9500W • FMV9508W

FMV9500W program-name: cannot disposition the FMV9504W program-name: The file system
mount event. Reason: error filesystem-name is not mounted or is
mounted with wrong options.
Explanation: The system wide mount event could not
be dispositioned. Mount events will not be received by Explanation: Either the file system is not mounted or
this daemon. it has been mounted with incorrect options.
System action: Tivoli Storage Manager continues. System action: Tivoli Storage Manager continues.
User response: Try to resolve the problem and restart User response: Mount the file system or remount it
the recall daemon. If the problem cannot be resolved with corrected mount options.
immediately, kill and restart the recall daemon after an
Tivoli Storage Manager space management supported
FMV9505E program-name: cannot initialize the
file system has been added using dsmmigfs or after a
DMAPI interface. Reason: error
file system has been mounted using the mount
command. Explanation: Tivoli Storage Manager client failed to
perform implementation-defined initialization of the
DMAPI interface.
FMV9501W program-name: cannot set event
disposition on session session for file System action: The dm_init_service() function failed.
system mountdir token = token. Reason :
error User response: If you are running Tivoli Storage
Manager as a non-root user and you have Tivoli
Explanation: Events could not be dispositioned on the Storage Manager space management client installed,
file system. No events will be received for this please, make sure that the dsmrootd daemon is up and
filesystem. HSM is not enabled for this file system. running, then retry the operation. If you don't have
Tivoli Storage Manager space management client
System action: Tivoli Storage Manager continues.
installed, retry the operation under the root user
User response: The file system must be one of the authority.
supported native file systems in order for the Tivoli
Storage Manager space management to support it.
FMV9506E program-name: The provided filespace
Verify that the mount options the file system are
argument 'argument' has an invalid
correct. Correct the problem and remount the file
format.
system.
Explanation: Occurs if you are on a GPFS file system
and the file system parameter was not in the correct
FMV9502W program-name: cannot remove event
format.
disposition on session session for file
system mountdir token = token. Reason : System action: The requested operation stops.
error
User response: See the dsmautomig documentation
Explanation: Event dispositions could not be removed for the correct syntax.
from the file system.
System action: Tivoli Storage Manager continues. FMV9507E program-name: cannot request the right
on session session for file handle
User response: Verify that the file system is mounted
filehandle token = token. Reason : error
and that dmapi is enabled on that file system. If the
problem persists, unmount and remount the file Explanation: Tivoli Storage Manager space
system, then try the operation again. If the problem still management cannot request the required right on a file.
persists, reboot the system.
System action: Processing of the file is interrupted.

FMV9503I program-name: events have been set and User response: Continue with normal operation.
dispositioned on session session for file
system filesystem-name FMV9508W program-name: cannot release the right on
Explanation: Setting events and dispositioning these session session for file handle = filehandle
on a DM session enables the file system for Tivoli token = token. Reason : error
Storage Manager space management support. Explanation: Tivoli Storage Manager space
System action: Tivoli Storage Manager continues. management cannot release the right on a file.

User response: Continue with normal operation. System action: Processing of the file is interrupted.
User response: Continue with normal operation.

Chapter 6. FMV messages 555

FMV9509W • FMV9518E

FMV9509W program-name: received an unexpected FMV9514E program-name: cannot create a file handle
event of type event-type on session from path. Reason: error
session.
Explanation: Tivoli Storage Manager space
Explanation: Tivoli Storage Manager space management cannot create a file handle from the given
management daemon received an unexpected event. file.
This event has not been dispositioned.
System action: Processing of the file is interrupted.
System action: Tivoli Storage Manager ignores event
User response: Continue with normal operation.
and continues.
User response: Continue with normal operation.
FMV9515E program-name: cannot set the migration
information. Reason: error
FMV9510E program-name: cannot get event messages
Explanation: Tivoli Storage Manager space
from session session, expected max
management cannot set the migration information of a
message-length = msglen, returned
file, because space management cannot create a file
message-length = return-length. Reason :
handle from the file and/or from the file system.
error
System action: Processing of the file is interrupted.
Explanation: Tivoli Storage Manager space
management encountered an error while trying to User response: Continue with normal operation.
receive a message on a DM session.
System action: Tivoli Storage Manager continues. FMV9516E program-name: cannot create an user
event message on session session.
User response: Continue with normal operation.
Reason: error
Explanation: Tivoli Storage Manager space
FMV9511E program-name: cannot read DM attributes
management cannot create an user event message,
on session session for file: name = name
needed to reference rights on a file to be processed.
handle = handle token = token. Reason :
error System action: Processing of the file is interrupted.
Explanation: Tivoli Storage Manager space User response: Continue with normal operation.
management cannot read the DM attributes of a DM
object, usually a file. If the file name is not available, it
will be displayed as an empty string or as <NA>. FMV9517I program-name: cleared event messages
from session session. Reason: error
System action: Processing of the file is interrupted.
Explanation: Tivoli Storage Manager space
User response: Continue with normal operation. management is in the process of destroying a DM
session. There are still unexpected event messages on
this session that were responded to.
FMV9512E program-name: cannot set DM attributes
on session session for file handle = System action: Tivoli Storage Manager DM session is
filehandle token = token. Reason : error not destroyed.
Explanation: Tivoli Storage Manager space User response: This message is informational. If the
management cannot set DM attributes for a DM object, session could not be destroyed, try the operation again.
usually a file. If the problem persists, reboot the system.
System action: Processing of the file is interrupted.
FMV9518E program-name: cannot respond to an
User response: Continue with normal operation.
event message on session session using
token token Reason : error
FMV9513E program-name: cannot remove DM
Explanation: An event message could not be
attributes on session session for file
responded to (returned to the system).
handle = filehandle token = token. Reason
: error System action: Tivoli Storage Manager space
management continues.
Explanation: Tivoli Storage Manager space
management cannot remove DM attributes for a DM User response: If a user process is unexpectedly
object, usually a file. blocked and cannot be killed, see your system
administrator.
System action: Processing of the file is interrupted.
User response: Continue with normal operation.

556 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9519W • FMV9526E

FMV9519W program-name: cannot set eventlist for a FMV9523E program-name: is unable to verify the
file system on session session token = stub size for the file on session session
token fs-handle = fs-handle. Reason : error file handle = filehandle token = token.
Reason : error
Explanation: An eventlist could not be set on a file
system. None of the events will be generated by the Explanation: A correct stub size could not be
system on this file system. determined by the system.
System action: Tivoli Storage Manager space System action: Tivoli Storage Manager stops
management continues. migration of the file.
User response: Try the operation again. If the problem User response: Try the operation again. If the problem
persists, verify that the file system is mounted with persists, verify that the file system is mounted with
dmapi enabled. If the problem still persists, reboot the dmapi enabled. If the problem still persists, restart the
system. system.

FMV9520E program-name: cannot set a managed FMV9524W program-name: adjusted stubsize to an

region on session session for file handle allowed value on session session file
= filehandle token = token. Reason : error handle = filehandle token = token old
stubsize = old-size new stubsize =
Explanation: A managed region could not be set on a
new-size
file. No events will be generated for this file.
Explanation: The predefined stubsize for the file
System action: Processing of the file is interrupted.
should be corrected to accommodate to the boundary
User response: Try the operation again. If the problem and rounding constraints imposed by the DMAPI
persists, verify that the file system is mounted with implementation. Tivoli Storage Manager space
dmapi enabled. If the problem still persists, reboot the management can also change the stubsize during
system. migration if the predefined stubsize value is larger than
the logical file size.

FMV9521E program-name: cannot get the file System action: Tivoli Storage Manager space
attributes on session session for file management continues.
handle = handle token = token. Reason :
User response: Continue with normal operation.
error
Explanation: Tivoli Storage Manager space
FMV9525E program-name: is unable to create a stub
management cannot read the attributes of a file.
file on session session for file handle =
System action: Processing of the file is interrupted. handle token = token. Reason : error

User response: Try the operation again. If the problem Explanation: An error occurred while creating a stub
persists, verify that the file system is mounted with file.
dmapi enabled. If the problem still persists, reboot the
System action: Processing of the file is interrupted.
system.
User response: Continue with normal operation.
FMV9522E program-name: can not create a file
system handle from path. Reason: error FMV9526E program-name: cannot open the state file
filename for writing. Reason: error
Explanation: Tivoli Storage Manager can not create a
file system handle from the file system name. If Reason Explanation: The global or file system state file could
is Operation not permitted, the dmapi functionality not be opened.
may be disabled for the file system.
System action: Tivoli Storage Manager stops
System action: Processing of the file system is processing.
interrupted.
User response: Try the operation again. If the problem
User response: If Reason is Operation not permitted, persists, verify that the file system is mounted with
enable dmapi functionality for the file system and retry. dmapi enabled. If the problem still persists, restart the
system.

Chapter 6. FMV messages 557

FMV9527E • FMV9535E

User response: Try the operation again. If the problem

FMV9527E program-name: cannot write to the state
persists, verify that the file system is mounted with
file filename. Reason: error
dmapi enabled. If the problem still persists, restart the
Explanation: Tivoli Storage Manager space system.
management could not write to the state file.
System action: Tivoli Storage Manager stops FMV9531E program-name: cannot create a DM
processing. session: old session = oldsession session
info = session-info. Reason : error
User response: Try the operation again. If the problem
persists, verify that the file system is mounted with Explanation: Tivoli Storage Manager space
dmapi enabled. If the problem still persists, restart the management could not create a DM session.
system.
System action: Tivoli Storage Manager stops
processing.
FMV9528W program-name: cannot read from the state
User response: Try the operation again. If the problem
file filename. . The file is corrupted and
persists restart the system.
will be recreated.
Explanation: Tivoli Storage Manager space
FMV9532W program-name: cannot destroy the session
management could not read from the state file.
session. Reason: error
System action: Tivoli Storage Manager stops
Explanation: Tivoli Storage Manager space
processing.
management could not destroy a DM session.
User response: Try the operation again. If the problem
System action: Tivoli Storage Manager continues.
persists, verify that the file system is mounted with
dmapi enabled. If the problem still persists, restart the User response: Try the operation again. If the problem
system. persists, verify that the file system is mounted with
dmapi enabled. If the problem still persists, restart the
system.
FMV9529W program-name: cannot obtain the handle
of a file system state file
FMV9533W program-name: failed getting all sessions.
Explanation: Tivoli Storage Manager space
Reason: error
management could not find the handle of a file system
state file that is stored in the global state file. This can Explanation: Tivoli Storage Manager space
occur if either space management is querying a file management could not get all DM sessions on the
system that has no HSM support added, or the file system.
system state file is corrupted, or the global state file is
corrupted. System action: Tivoli Storage Manager stops
processing.
System action: Tivoli Storage Manager continues or
stops processing, depending on the situation. User response: Try the operation again. If the problem
persists, verify that the file system is mounted with
User response: Try the operation again. If the problem dmapi enabled. If the problem still persists, restart the
persists, verify that the file system is mounted with system.
dmapi enabled. If the problem still persists, restart the
system.
FMV9534W program-name: cannot query a session.
Reason: error
FMV9530W program-name: cannot remove an entry
for file-system from the global state file. Explanation: Tivoli Storage Manager space
management could not query a DM session on the
Explanation: The entry for the file system in the system.
dmiFSGlobalState file cannot be removed. Possible
reasons: System action: Tivoli Storage Manager continues.

v There is not enough memory to create temporary file User response: Continue with normal operation.
name for temporary file system table.
v There is not enough free space or inodes to create FMV9535E program-name: a file handle could not be
temporary file system table created from the file descriptor
v The real or temporary file system table files cannot file-descriptor. Reason: error
be opened.
Explanation: Tivoli Storage Manager space
System action: Tivoli Storage Manager does not management could not create a file handle.
remove the entry from the global state file.
System action: Processing of the file is interrupted.

558 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9536E • FMV9548W

User response: Try the operation again. If the problem

FMV9543W program-name: The TSM client needs
persists, verify that the file system is mounted with
blocks-num1 free file system blocks to be
dmapi enabled. If the problem still persists, restart the
able to handle the nospace condition on
system.
file system filesystem-name, errno:
error-num, reason: error-str. Currently
FMV9536E program-name: cannot query an event blocks-num2 blocks with a block size of
message on session session. Reason: error block-size bytes are available.

Explanation: Tivoli Storage Manager space Explanation: Either the Tivoli Storage Manager client
management cannot query an event message, needed to is not able to get status information for the file system
determine whether nfs call. or there is insufficient space in the file system. The
message reports zero blocks if the file system status
System action: Processing of the file is interrupted. information is not available.
User response: Continue with normal operation. System action: Tivoli Storage Manager continues.
User response: If there is insufficient space in the file
FMV9537E program-name: Invalid storage pool system, free the required space or increase the file
'storagepool' for file system 'filesystem'. system capacity. If this is due to an input output error,
Explanation: No storage pool with that name exists on perform an appropriate file system check (e.g. fsck).
the specified file system. Then try the operation again.

System action: The requested operation stops.

FMV9545E program-name: cannot get a lock for
User response: Please make sure the storage pool lockdirlockfile to continue processing.
exists on the specified file system.
Explanation: Tivoli Storage Manager space
management could not obtain a lock for a file.
FMV9538W program-name: request request for DM file
attributes not recognized System action: processing stops.

Explanation: An unknown request type has been User response: Try the operation again. If problem
encountered that cannot be handled. persists, restart HSM. If problem still persists, restart
the system.
System action: Tivoli Storage Manager continues.
User response: Continue with normal operation. FMV9546E IBM Tivoli Storage Manager cannot
perform instant restore because
FMV9539E program-name: cannot create a file system Microsoft Active Directory Domain
handle from the file handle = filehandle. Controller was detected on virtual
Reason : error machine.

Explanation: A file system handle could not be Explanation: The virtual machine contains Microsoft
created from a file handle. Active Directory Domain Controller. It cannot be
recovered using instant restore.
System action: Tivoli Storage Manager continues.
System action: Processing stops.
User response: Continue with normal operation.
User response: Use a regular restore to recover the
virtaul machine.
FMV9542E program-name: the file attributes could
not be set on session session for file
handle = filehandle token = token flag = FMV9548W Cannot complete remote file access for
flag Reason : error inode:'inode number', alias:'file name'.

Explanation: Tivoli Storage Manager space Explanation: Tivoli Storage Manager space
management could not update file attributes. management cannot complete the remote file access.
The file may be migrated to an Tivoli Storage Manager
System action: Processing of the file is interrupted. migration server that could be temporarily unavailable.
User response: Try the operation again. If the problem The file may be an orphan stub.
persists, verify that the file system is mounted with System action: Tivoli Storage Manager terminates the
dmapi enabled. If the problem still persists, restart the current operation.
system.
User response: Check to see whether the server has
been disabled by the system administrator, then retry
the operation. To check whether the file is an orphan

Chapter 6. FMV messages 559

FMV9550W • FMV9590E

stub or not, run dsmreconcile for the affected file

FMV9555E Guest name VM does not match any
system. Note: the file alias may be displayed as
virtual machines.
'unavailable' if the connection to server is unavailable
or 'orphan' if the appropriate file copy cannot be Explanation: TSM application protection requires the
located on a particular migration server. guest name to match a virtual machine.
System action: Processing stops
FMV9550W File recall has been discontinued.
User response: Check the guest name and make sure
Explanation: Recall stops because the file being it is spelled correctly.
recalled would cause the file system to run out of
space.
FMV9556E Number of CTL files on disk (number of
System action: Tivoli Storage Manager terminates the CTLs on disk) do not match the expected
current operation. value (number of CTLs in cache).
User response: Increase the file system space, or Explanation: The number of CTLs files counted in
remove unneeded files, or wait until space VCM lib cache should be equal to that in the local
management has migrated files off the file system by disks.
demand or threshold migration, or manually migrate
System action: Processing is aborted.
files. Then retry the operation.
User response: None.
FMV9552E program-name: cannot add space
management to file-system; path includes FMV9576E Not enough space in filesystem to create
non-local file system. meta data file! At least space space
required!
Explanation: An attempt was made to add space
management to a file system whose path contains Explanation: A disk full error occurred attempting to
non-local elements. create the metadata file. Please migrate some files in
filesystem to free at least space kb.
System action: Processing stopped.
System action: Processing stops.
User response: File system must be entirely local.
User response: None.
FMV9553I Wrote temporary candidates list to
file-name. FMV9577E An exception "msg"! Unable to use meta
file!
Explanation: Due to out of space condition, the
candidates list was written to the named temporary Explanation: An internal error occurred. The dsmscout
file. is unable to use the meta data file!
System action: Temporary file created. System action: Processing stops.
User response: Temporary file can be copied to the User response: None.
appropriate .SpaceMan directory when space is made
available.
FMV9578E An unknown error occurred!

FMV9554E program-name: command for file system Explanation: An internal error has occurred. The
mountdir Reason : error dsmscout is unable to use the meta data file! The file
has been deleted. A new meta data file will be created.
Explanation: An attempt to enable or disable xdsm
api functionality on the file system failed. If the attempt System action: Processing stops.
was to enable HSM, then HSM is not enabled for this User response: None.
file system.
System action: Tivoli Storage Manager continues. FMV9590E The SOAP error information: message
User response: The file system must be of type JFS2 in failed, reason: message
order for the Tivoli Storage Manager Space Explanation: The detailed SOAP error message is
Management to successfully set the managed attribute. created from gSOAP communication module and does
Verify that the file system is of the correct type. not exist in the chosen language!
System action: Tivoli Storage Manager continues.
User response: Verify your system and retry the
operation.

560 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9591E • FMV9645W

System action: Tivoli Storage Manager aborts the

FMV9591E A SOAP UDP connection error has
operation.
happened!
User response: None.
Explanation: The SOAP communication system had
an UDP error. Please see errorlog file for more detailed
information! FMV9613E program-name: Stub size of stubsize bytes
is not supported on filesystem.
System action: Tivoli Storage Manager aborts the
operation. Explanation: The given stub size value not a multiple
of the file system block size and cannot be supported.
User response: None.
System action: The program aborts the operation.
FMV9592E A SOAP TCP connection error has User response: Use a correct stub size.
happened!
Explanation: The SOAP communication system had FMV9616E program-name: cannot get migration
an TCP error. Please see errorlog file for more detailed information for migrated-file-alias on
information! file-system-name
System action: Tivoli Storage Manager aborts the Explanation: Tivoli Storage Manager space
operation. management cannot access the specified file system
object using the system DMAPI functions. This
User response: None.
condition might occur if DMAPI support is not enabled
for the file system, or if there is an inconsistency in the
FMV9593E A SOAP HTTP communication error has file system. This message is typically preceded by other
happened! messages that have more specific information about the
error.
Explanation: The SOAP communication system had
an HTTP error. Please see errorlog file for more System action: Processing of the file is interrupted.
detailed information! Processing continues with the next file.
System action: Tivoli Storage Manager aborts the User response: Review dsmerror.log for preceding
operation. messages that might have more specific information
about the error. Verify that the file system is consistent
User response: None.
and mounted with DMAPI support enabled. Then retry
the operation. If the problem persists, contact IBM
FMV9594E An internal SOAP error has happend! technical support for further assistance.

Explanation: The SOAP communication system had

an internal error. Please see errorlog file for more FMV9641S Invalid option 'option' found in options
detailed information! file 'file-name' at line number : number
Invalid entry : 'entry'
System action: Tivoli Storage Manager aborts the
operation. Explanation: The specified option in the Tivoli Storage
Manager options file (file-name) is in error.
User response: None.
System action: Processing stopped.
FMV9595E The SOAP communication system is out User response: Correct the options file entry.
of memory!
Explanation: The SOAP communication system had FMV9645W The vApps backup operation completed.
an memory error. Please see errorlog file for more However, one or more vApp backups
detailed information! failed.

System action: Tivoli Storage Manager aborts the Explanation: There were successfull vApp backups
operation. but there were backup failures as well. The operation is
considered successfull.
User response: None.
System action: The backup operation completed
successfully.
FMV9596E The SOAP communication ended
unexpected! User response: Check the console output and error
logs for information about why the backups failed.
Explanation: The SOAP communication system had Correct any issues and try backing up the failed vApps
an EOF error. Please see errorlog file for more detailed again.
information!

Chapter 6. FMV messages 561

FMV9669W • FMV9739E

the migrate or recall operation.

FMV9669W program-name: file-system CFI is out of
range. User response: Use the HSM Unix shell commands
instead.
Explanation: Tivoli Storage Manager CFI is out of
range on the specified file system. The scout daemon
could not insert a new file entry into the CFI during FMV9736E Not enough memory for authorization
the file system scan. As a result, it may not provide list table
enough candidates for the next automigration.
Explanation: Tivoli Storage Manager cannot allocate
System action: Processing continues. enough storage for the authorization list. This message
is issued only from the Motif HSM GUI, which is no
User response: Please, reconsider the MAXFILES
longer supported.
option setting for the file system. The CFI size should
likely be increased via 'dsmmigfs update /fs System action: Tivoli Storage Manager cannot
-MAXFiles=n' command. complete the requested operation.
User response: Use the HSM Unix shell commands
FMV9674W One or more of the required vApps instead.
could not be retreived.
Explanation: Not all of the vApps that were required FMV9737E Authentication failed -- Exit Tivoli
by the given specification could be retreived. This can Storage Manager to retry
be caused by a change in the vCD vApps definition or
a user mistake in the provided vApp spec. Explanation: You typed an incorrect password four
times in a row. This message is issued only from the
System action: The operation will proceed, as there Motif HSM GUI, which is no longer supported.
are still existing items to operate on.
System action: Tivoli Storage Manager cannot connect
User response: Check the provided vApps to the server without a correct password.
specification to make sure the specification matches the
existing configuration. Correct any issues and try the User response: Use the HSM Unix shell commands
operation again. instead.

FMV9733E File: File-name excluded by the FMV9738S Out of memory

Include/Exclude list Explanation: Tivoli Storage Manager found an error
Explanation: You tried to back up the named file-name allocating storage at initialization. This message is
that was specified to be excluded from backup. issued only from the Motif HSM GUI, which is no
longer supported.
System action: Tivoli Storage Manager did not back
up the file. System action: Tivoli Storage Manager cannot
continue.
User response: Specify the file using the Include
option and retry the operation. User response: Use the HSM Unix shell commands
instead.

FMV9734E There are number file(s) not selected.

Click on file to find out reason. FMV9739E Cannot get shared memory

Explanation: There are files that cannot be selected. Explanation: The system ran out of shared storage
resources.
System action: These files will not be selected for
migrate or recall. System action: Tivoli Storage Manager cannot
continue without a shared storage segment.
User response: Click on the files to find out the reason
these files are not selected, for example, inclexcl list. User response: Check the output of the “ipcs”
program to see if there are many new shared storage
segments. Use “ipcrm” to remove them. If this problem
FMV9735E Error doing realtime initialization continues, configure UNIX to allow more shared
storage segments.
Explanation: Tivoli Storage Manager ran out of
resource (either processes or shared storage) that
prevents it from starting a migrate or recall operation.
Your file selections remain intact. This message is
issued only from the Motif HSM GUI, which is no
longer supported.
System action: Tivoli Storage Manager cannot start

562 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9740S • FMV9781E

FMV9740S This program is not installed correctly. FMV9744W Size exceeds limit
Place the application defaults file
Explanation: You tried to recall a file that has
(file-name) into the application default
exceeded the maximum file size limitation on your
directory (usually directory-name), or set
system.
the XAPPLRESDIR environment
variable to the directory containing the System action: Tivoli Storage Manager cannot recall
file-name defaults file. the file.
Explanation: Tivoli Storage Manager cannot find its User response: Recall this file on a system that
resource file (Sm) in the default directory supports the file size. See your system administrator.
(directory-name). A problem may have occurred during
installation. This message is issued only from the Motif
HSM GUI, which is no longer supported. FMV9778E Error(s) were detected in options file: ''
Do you want Tivoli Storage Manager to
System action: Tivoli Storage Manager cannot start. comment out the line with errors and
continue?
User response: Use the HSM Unix shell commands
instead. Explanation: Invalid options or option values were
encountered while reading the options file.
FMV9741E Not enough memory to hold directory System action: This message is displayed. Further
structure action depends on your response.
Explanation: Tivoli Storage Manager cannot allocate User response: Click "Yes" to allow Tivoli Storage
storage for the requested directory structure. This error Manager to turn the invalid line into comments. If you
can happen under migrate or recall operations. This click "No", you will exit immediately.
message is issued only from the Motif HSM GUI,
which is no longer supported.
FMV9779E Unable to open options file '' for
System action: Tivoli Storage Manager cannot writing.
complete the requested operation.
Explanation: An error occurred while Tivoli Storage
User response: Use the HSM Unix shell commands Manager tried to open options file for writing to
instead. update it.
System action: Program exits.
FMV9742E Error reading directory structure
User response: Check file and directory access
Explanation: Tivoli Storage Manager cannot load the permissions or correct invalid entries in your options
requested directory structure. This error is due to a file manually.
corrupted file system or a storage shortage. This can
happen under selective migrate or selective recall. This
message is issued only from the Motif HSM GUI, FMV9780E Unable to update options file ''.
which is no longer supported. Explanation: Tivoli Storage Manager was unable to
System action: Tivoli Storage Manager cannot update your options file, possibly because of disk full
complete the requested operation. condition.

User response: Use the HSM Unix shell commands System action: Program exits.
instead. User response: Check if you have enough disk space
or correct invalid entries in your options file manually.
FMV9743W No files selected in directory tree
Explanation: You did not select any files to list for FMV9781E After completing repair Tivoli Storage
migrate or recall. Manager found an invalid option,
keyword or parameter in your options
System action: Tivoli Storage Manager cannot file.
complete the requested operation.
Explanation: A final check of your options file found
User response: Select files and retry the operation. that an invalid option, keyword, or parameter still
remains. It is possible your options file was modified
by another application.
System action: Program exits.
User response: Make sure no other application
modified your options file and restart Tivoli Storage

Chapter 6. FMV messages 563

FMV9782S • FMV9799W

Manager. You may also use a text editor to correct

FMV9792W A tree view of a file system is being
invalid entries in your options file.
built. Please wait until it completes, and
then retry the operation.
FMV9782S The selected backupset was generated
Explanation: You tried to choose Selective Migration
by a newer version of the backup server,
or Selective Recall when a tree view of a file system is
and the new backupset version is not
being built.
supported by this client; The backupset
data cannot be restored by this version System action: Tivoli Storage Manager ignores the
of the client. request.
Explanation: The backupset you are attempting to User response: Wait until the tree view build
restore was generated by a newer server that has a completes, and then retry the operation.
different level of functionality. The client you are using
does not recognize this newer format so it cannot
FMV9796E Cannot access lock file for file-system file
restore the data from the backupset.
system.
System action: Processing stopped.
Explanation: Tivoli Storage Manager cannot access a
User response: Restore the backupset with a client lock file due to an error. The lock file provides
that is at the same or higher level as the server that serialization of certain programs to prevent conflicting
was used to generate the backupset. processes from running at the same time.
System action: Tivoli Storage Manager will not run
FMV9790I File is skipped for migration: No the program at this time.
backup copy found.
User response: Check the permissions on the
Explanation: A management class is assigned to the directories leading up to the lock file and also the
file with the attribute MIGREQUIRESBKUP set to YES. permissions on the program executable.
This requires a current backup copy of the file before
migration. However, there is no backup copy found on
FMV9797E A conflicting space management process
the migration server. This file will not be migrated.
is already running in the file-system file
Note: Tivoli Storage Manager checks only the migration
system. Rerun this process at a later
server for a backup copy. If the migration server and
time.
backup server are different servers, Tivoli Storage
Manager does not find a backup copy of the file. Explanation: Tivoli Storage Manager detects that
another process that conflicts with the process you are
System action: Tivoli Storage Manager does not
trying to run is running in the file system. The
migrate this file.
following processes cannot be run at the same time for
User response: Back up this file on the migration a file system:
server, or assign a management class to this file that v dsmreconcile
does not require a current backup copy. Retry the
v dsmautomig
operation.
v dsmmigfs remove.

FMV9791I File is skipped for migration: Backup Also dsmmigfs remove cannot run while a migration
copy found is not current. process is running in the file system.

Explanation: A management class is assigned to the System action: Tivoli Storage Manager will not run
file with the attribute MIGREQUIRESBKUP set to YES. the process at this time.
This requires a current backup copy of the file before User response: Try running the process again later.
migration. However, the backup copy found on the
migration server is an old version. This file will not be
migrated. Note: Tivoli Storage Manager checks only the FMV9799W Cannot open temp file for mount
migration server for a backup copy. If the migration command.
server and backup server are different servers, there
Explanation: Tivoli Storage Manager cannot open a
must be a valid backup copy of the file on the
temporary file to process the mount command for this
migration server.
file system. This message is issued only from the Motif
System action: Tivoli Storage Manager does not HSM GUI, which is no longer supported.
migrate this file.
System action: Tivoli Storage Manager cannot add
User response: Back up the current file on the space management to the file system.
migration server, or assign a management class to this
User response: Use the HSM Unix shell commands
file that does not require a current backup copy. Retry
instead.
the operation.

564 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9800W • FMV9809W

FMV9800W Cannot create temp file for mount FMV9805W Cannot create .SpaceMan directory.
command.
Explanation: Cannot create .SpaceMan directory for
Explanation: Tivoli Storage Manager cannot create a this file system. This message is issued only from the
temporary file to process the mount command for this Motif HSM GUI, which is no longer supported.
file system. This message is issued only from the Motif
System action: Tivoli Storage Manager cannot add
HSM GUI, which is no longer supported.
space management to the file system.
System action: Tivoli Storage Manager cannot add
User response: Use the HSM Unix shell commands
space management to the file system.
instead.
User response: Use the HSM Unix shell commands
instead.
FMV9806W The file system type is not supported.
Explanation: The file system is not a type supported
FMV9801W Cannot create transaction file.
by space management.
Explanation: Cannot create transaction file for this file
System action: Tivoli Storage Manager cannot add
system. This message is issued only from the Motif
space management to the file system.
HSM GUI, which is no longer supported.
User response: There is a mismatch between the HSM
System action: Tivoli Storage Manager cannot add
client and the file system type specified. If the file
space management to the file system.
system type is consistent with the intent, install an
User response: Use the HSM Unix shell commands HSM client that supports it, then try the operation
instead. again. Only one HSM client can be installed at a time.

FMV9802W Cannot create status file. FMV9807W The specified backupset file does not
contain a backupset of type "file" for the
Explanation: Cannot create status file for this file
specified nodename.
system. This message is issued only from the Motif
HSM GUI, which is no longer supported. Explanation: Local backupset support is limited to
backupsets that contain file data; Image backupsets are
System action: Tivoli Storage Manager cannot add
not supported locally. The specified backupset does not
space management to the file system.
contain a backupset with file data for the node name
User response: Use the HSM Unix shell commands specified.
instead.
System action: Processing stopped.
User response: Specify a different backupset file to
FMV9803W Cannot create premigration database.
restore file data from a backupset. To restore an image
Explanation: Cannot create a premigration database from a backupset, access the backupset from a TSM
for this file system. This message is issued only from server.
the Motif HSM GUI, which is no longer supported.
System action: Tivoli Storage Manager cannot add FMV9808W Invalid field in the dsmmigfstab file.
space management to the file system.
Explanation: There is an invalid field in the
User response: Use the HSM Unix shell commands dsmmigfstab file entry for the file system. This message
instead. is issued only from the Motif HSM GUI, which is no
longer supported.

FMV9804W Cannot create migration candidates list. System action: Tivoli Storage Manager cannot add
space management to the file system.
Explanation: Cannot create a migration candidates list
for this file system. This message is issued only from User response: Use the HSM Unix shell commands
the Motif HSM GUI, which is no longer supported. instead.

System action: Tivoli Storage Manager cannot add

space management to the file system. FMV9809W Cannot open the dsmmigfstab file.

User response: Use the HSM Unix shell commands Explanation: Tivoli Storage Manager cannot open the
instead. dsmmigfstab file. This message is issued only from the
Motif HSM GUI, which is no longer supported.
System action: Tivoli Storage Manager cannot add
space management to the file system.

Chapter 6. FMV messages 565

FMV9811W • FMV9820W

User response: Use the HSM Unix shell commands

FMV9816W File system has exceeded its quota.
instead.
Explanation: Tivoli Storage Manager detects that the
file system has exceeded its quota. No more files can be
FMV9811W Server did not respond. Check the
migrated to Tivoli Storage Manager storage for this file
server connection. Select OK to exit.
system.
Explanation: Server did not respond.
System action: Tivoli Storage Manager will not
System action: Tivoli Storage Manager stops migrate files from this file system.
processing.
User response: Either recall some files to the local file
User response: Exit dsmhsm. Check the server system, or ask the system administrator to increase the
connection and try again later. quota for this file system.

FMV9812I Files not found in current directory. FMV9817W file-system is globally deactivated. Please
Refresh file systems. wait until the file system is globally
reactivated.
Explanation: Some files are not found in the local file
system. Explanation: The file system is in a global inactive
state.
System action: The transaction will show incorrect
results. System action: Tivoli Storage Manager cannot
continue the process.
User response: Refresh the file systems to reflect local
file systems. User response: Wait until the system administrator
globally reactivates the file system.

FMV9813W Incorrect data shown. Run reconcile.

FMV9818W A selective recall is in progress. Stop the
Explanation: Information in the space management recall, and then close the window.
status file is not synchronized with the file system.
Explanation: You tried to close the Selective Recall
System action: Tivoli Storage Manager continues Status window while a selective recall was in progress.
processing.
System action: Tivoli Storage Manager ignores the
User response: To correct the information, run request.
reconcile, and then refresh the current window.
User response: Stop the selective recall process, and
then close the window.
FMV9814W Cannot create migration object ID.
Explanation: The file system is full. No more free FMV9819W A selective migration is in progress.
space can be allocated for the migration object ID when Stop the process, and then close the
a file is being migrated or recalled. window.
System action: Tivoli Storage Manager terminates the Explanation: You tried to close the Selective Migration
current operation for this file system. Status window while a selective migration was in
User response: Remove some files in the file system, progress.
and then run reconciliation. Retry the operation. System action: Tivoli Storage Manager ignores the
request.
FMV9815W Out of free space or inodes in file User response: Stop the selective migration process,
system to migrate or recall. and then close the window.
Explanation: The file system is full. No more free
space or free inodes are available to be allocated for the FMV9820W A selective recall or a selective
transaction file that is needed when a file is being migration is in progress. Wait until it
migrated or recalled. completes, and then retry the operation.
System action: Tivoli Storage Manager terminates the Explanation: You tried to perform one of the
current operation for this file system. following while a selective recall or selective migration
User response: Remove some files in the file system, process was in progress:
and then run reconciliation. Retry the operation. v Add space management
v Deactivate or reactivate space management
v Global deactivate or reactivate space management

566 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9821W • FMV9840W

v Display policy information

FMV9827W Error accessing the Recall daemon lock
v Change password file: file name.
System action: Tivoli Storage Manager ignores the Explanation: There is a problem accessing the recall
request. daemon lock file.
User response: Wait until the selective recall or System action: Tivoli Storage Manager cannot
selective migration process is complete, and then retry determine whether the recall daemon is running.
the operation. Because the recall daemon is needed to perform file
recalls, the recall fails.
FMV9821W New password is not re-entered. User response: Check with the system administrator.
Explanation: You did not re-enter the new password. The recall process needs read access to the
/etc/adsm/SpaceMan/dsmrecalld.pid file.
System action: The Change password dialog will
display again.
FMV9828W Error processing the space monitor
User response: Re-enter the new password. daemon: reason.
Explanation: There is a problem accessing the space
FMV9822W New password is not entered. monitor daemon.
Explanation: You did not enter the new password. System action: Tivoli Storage Manager cannot perform
automatic space management functions.
System action: The Change password dialog will
display again. User response: Check with the system administrator.
The space monitor daemon is normally installed as
User response: Enter the new password.
/usr/lpp/adsm/bin/dsmmonitord.

FMV9823W The current password is not entered.

FMV9829W Recall daemon is not running.
Explanation: You did not enter the current password.
Explanation: An Tivoli Storage Manager recall
System action: The Change password dialog will daemon is not running.
display again.
System action: Tivoli Storage Manager recall fails.
User response: Enter the current password.
User response: Ask the system administrator to start a
recall daemon by issuing the dsmrecalld command.
FMV9824W Cannot update space management
settings for file-system
FMV9830W Space monitor daemon is not running.
Explanation: You tried to update space management
Explanation: The space monitor daemon is not
settings for a file system, and the update failed. This
running.
message is issued only from the Motif HSM GUI,
which is no longer supported. System action: Tivoli Storage Manager is unable to
perform space management functions.
System action: Tivoli Storage Manager continues with
normal operation. User response: Ask the system administrator to start
the space monitor daemon by issuing the dsmmonitord
User response: Use the HSM Unix shell commands
command.
instead.

FMV9840W This command is not currently

FMV9825W Total migrated space is greater than
supported for local backupsets.
quota for file system.
Explanation: Local backupset support is limited to
Explanation: Tivoli Storage Manager total migrated
only a few commands and the command you specified
space is greater than quota.
is not one of the supported commands.
System action: Tivoli Storage Manager continues.
System action: Processing stopped.
User response: You can remove this warning message
User response: To perform this command on a
by increasing the quota for the file system.
backupset, access the backupset from a TSM server.

Chapter 6. FMV messages 567

FMV9841E • FMV9850E

User response: Look for previous messages.

FMV9841E Cannot get user name for the user ID.
Explanation: Tivoli Storage Manager cannot get the
FMV9846W Cannot add space management to file
user name for the user ID. This message is issued only
system.
from the Motif HSM GUI, which is no longer
supported. Explanation: Tivoli Storage Manager cannot add space
management to the file system. This message is issued
System action: Tivoli Storage Manager terminates the
only from the Motif HSM GUI, which is no longer
requested process and returns to normal operation.
supported.
User response: Use the HSM Unix shell commands
System action: Tivoli Storage Manager continues with
instead.
normal operation.
User response: Use the HSM Unix shell commands
FMV9842E The watch daemon is not running
instead.
properly.
Explanation: An Tivoli Storage Manager watch
FMV9848W Cannot activate file system file system.
daemon is either not running, has no dmapi session, or
is not connected to group services. Explanation: Tivoli Storage Manager cannot activate
space management for the specified file system. This
System action: The Tivoli Storage Manager action
message is issued only from the Motif HSM GUI,
fails.
which is no longer supported.
User response: Ask the system administrator to check
System action: Tivoli Storage Manager file system
GPFS and the group services and to restart a watch
state is not changed.
daemon by issuing the dsmwatchd command.
User response: Use the HSM Unix shell commands
instead.
FMV9843E Cannot connect to migration server.
Explanation: Tivoli Storage Manager cannot connect to
FMV9849W Local backupset cannot be expanded;
the migration server specified in your client system
Only full backupset restore is supported
options file. This message is issued only from the Motif
locally.
HSM GUI, which is no longer supported.
Explanation: Local backupsets cannot be expanded to
System action: Tivoli Storage Manager terminates the
show volumes, directories, and files. Only full
requested process and returns to normal operation.
backupset restore is supported from local backupsets.
User response: Use the HSM Unix shell commands
System action: Processing stopped.
instead.
User response: To restore specific volumes, directories,
and files from a backupset, restore the backupset from
FMV9844E Cannot close the premigrated files
the TSM server.
database.
Explanation: Tivoli Storage Manager cannot close the
FMV9850E Tape read error; Max Blocksize is
premigrated files database for the file system. The
blocksize. Attempted to read blocksize
premigrated files database resides in the .SpaceMan
blocksize. Run dsmmaxsg to update scsi
subdirectory of the file system’s root directory. This
driver max blocksize allowed and retry
message is issued only from the Motif HSM GUI,
operation.
which is no longer supported.
Explanation: An attempt to read from tape at the
System action: Tivoli Storage Manager terminates the
specified blocksize failed; Tha maximum blocksize
requested process, and returns to normal operation.
allowed for the scsi driver is shown.
User response: Use the HSM Unix shell commands
System action: Processing stopped.
instead.
User response: If the maximum blocksize is less than
the blocksize used by the operation, run the dsmmaxsg
FMV9845E Space management action ends.
utility to update the maximum blocksize allowed for
Explanation: Tivoli Storage Manager The requested the scsi driver, and then retry the operation. If the
space management operation is ended because the maximum blocksize is greater than or equal to the
watch daemon is not working properly. blocksize used, then verify that the tape installed and
operating correctly and retry the operation.
System action: Tivoli Storage Manager is unable to
complete the operation.

568 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9852E • FMV9862W

System action: Tivoli Storage Manager left the file

FMV9852E Cannot query the level of client and
resident.
kernel.
User response: If you want the file migrated, stop the
Explanation: The space management GUI client fails
processes which currently have the file open, and retry
to query the level of kernel and client code. This
the migration operation.
message is issued only from the Motif HSM GUI,
which is no longer supported.
FMV9857W The restored HSM for Windows stub
System action: Tivoli Storage Manager continues with
file may be an orphan: stub file name
normal operation.
Explanation: The restored stub file may not be
User response: Use the HSM Unix shell commands
accessible in the HSM client archive and thus it
instead.
possibly cannot be recalled.
System action: Stub file is restored.
FMV9853W The space management client program
is downlevel. User response: Check if the stub file can be accessed.
Explanation: The space management client is
downlevel compared to the kernel level. This message FMV9858E Bit file for image on push button cannot
is issued only from the Motif HSM GUI, which is no be found. Please check to make sure the
longer supported. pixmap file exists in your Tivoli Storage
Manager installed directory.
System action: Tivoli Storage Manager continues with
normal operation. Explanation: Tivoli Storage Manager failed to find the
pixmap file defined for the push button.
User response: Use the HSM Unix shell commands
instead. System action: Tivoli Storage Manager continues with
normal operation.
FMV9854W The space management kernel is User response: Check to see whether the pixmap file
downlevel. exists in the Tivoli Storage Manager installation
directory.
Explanation: The space management kernel is
downlevel compared to the client level. This message is
issued only from the Motif HSM GUI, which is no FMV9860W Some selected files are hidden. Change
longer supported. View option to see all.
System action: Tivoli Storage Manager continues with Explanation: You have selected all files in a directory
normal operation. or in all subdirectories. Due to the current View option,
only certain types of files are shown (either migrated,
User response: Use the HSM Unix shell commands
resident, or premigrated files).
instead.
System action: Tivoli Storage Manager proceeds
normally.
FMV9855W File is accessed during migration. File
skipped. User response: If you want to see all selected files,
change the View option from the View menu bar
Explanation: The specified file-name was not migrated
option.
because the file was accessed by another process during
the attempt to migrate it.
FMV9862W Do you want to exit Tivoli Storage
System action: Tivoli Storage Manager left the file
Manager space management?
resident.
Explanation: You have selected Exit from the File
User response: If you want the file migrated, stop the
menu bar option.
process which is accessing the file and retry the
migration operation. System action: Tivoli Storage Manager waits for your
response.
FMV9856E File is currently opened by another User response: If you want to exit the program, select
process. File skipped. File has already OK. Otherwise, select Cancel.
been migrated or is currently being
migrated by another process.
Explanation: The specified file was not migrated
because the file was opened by one or more other
processes.

Chapter 6. FMV messages 569

FMV9871W • FMV9882W

FMV9871W Specified column width is smaller than FMV9878W Size Factor must be a positive number.
the largest attribute value. Data will be
Explanation: You have entered an invalid value for
truncated.
Size Factor. It must be a positive number between 0
Explanation: You have entered a column width that is and 999999999.
too small to display all digits of the largest attribute.
System action: Tivoli Storage Manager continues with
System action: Tivoli Storage Manager accepts your normal operation.
request.
User response: Enter a positive number between 0
User response: To see all attributes in full length, and 999999999.
increase the column width.
FMV9879W Age Factor must be a numeric value
FMV9873W This function should not be used on between 0 - 999999999.
large file systems. Continue anyway ?
Explanation: You have entered an invalid value for
Explanation: You have decided to open selective recall Age Factor. It must be a positive number between 0
or selective migration window, but these functions may and 999999999.
take too long for large file systems.
System action: Tivoli Storage Manager continues with
System action: Tivoli Storage Manager waits for your normal operation.
response.
User response: Enter a positive number between 0
User response: If you want to continue, select OK. and 999999999.
Otherwise, select Cancel.
FMV9880W Age Factor must be a positive number.
FMV9875W Refresh time must be numeric value and
Explanation: You have entered an invalid value for
within 0 - 14400 minutes or 0 - 240 hours
Age Factor. It must be a positive number between 0
(10 days).
and 999999999.
Explanation: You have entered an invalid value for
System action: Tivoli Storage Manager continues with
Refresh time. It must be a positive number between 0
normal operation.
and 14400.
User response: Enter a positive number between 0
System action: Tivoli Storage Manager continues with
and 999999999.
normal operation.
User response: Enter a positive number between 0
FMV9881W Premigration Percent must be a numeric
and 14400.
value between 0 - 100.
Explanation: You have entered an invalid value for
FMV9876W Refresh time must be a positive number.
Premigration Percentage. It must be a positive number
Explanation: You have entered an invalid value for between 0 and 100.
Refresh time. It must be a positive number between 0
System action: Tivoli Storage Manager continues with
and 14400.
normal operation.
System action: Tivoli Storage Manager continues with
User response: Enter a positive number between 0
normal operation.
and 100.
User response: Enter a positive number between 0
and 14400.
FMV9882W Premigration Percent must be a positive
number.
FMV9877W Size Factor must be a numeric value
Explanation: You have entered an invalid value for
between 0 - 999999999.
Premigration Percentage. It must be a positive number
Explanation: You have entered an invalid value for between 0 and 100.
Size Factor. It must be a positive number between 0
System action: Tivoli Storage Manager continues with
and 999999999.
normal operation.
System action: Tivoli Storage Manager continues with
User response: Enter a positive number between 0
normal operation.
and 100.
User response: Enter a positive number between 0
and 999999999.

570 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9883W • FMV9892E

FMV9883W Quota must be a numeric value between FMV9887W Enter a positive number for Space
0 - 999999999. Between Column.
Explanation: You have entered an invalid value for Explanation: You have entered an invalid value for
Quota. It must be a positive number between 0 and Space Between Column. It must be a positive number
999999999. between 0 and 18.
System action: Tivoli Storage Manager continues with System action: Tivoli Storage Manager continues with
normal operation. normal operation.
User response: Enter a positive number between 0 User response: Enter a positive number between 0
and 999999999. and 18.

FMV9884W Quota must be a positive number. FMV9889W Space management has not been added
to file-system file system. Do you want to
Explanation: You have entered an invalid value for
build the directory tree anyway?
Quota. It must be a positive number between 0 and
999999999. Explanation: You selected a file system that is not
managed by HSM.
System action: Tivoli Storage Manager continues with
normal operation. System action: Tivoli Storage Manager builds the
directory tree if you select the OK button. Otherwise, it
User response: Enter a positive number between 0
will not.
and 999999999.
User response: You can add space management to the
file system by selecting the Space Manager push button
FMV9885I The premigration percentage will not be
in the Tivoli Storage Manager main window, and then
updated until you select the Update
selecting Add under the Selected menu option.
push button on the Update window or
the Add push button on the Add
window. FMV9890W program-name: The file system filesystem
is already owned by that node.
Explanation: While you have just selected 'OK' in the
Advanced Feature dialog, the premigration percentage Explanation: The file system is already owned by that
is not activated until you select 'Add' or 'Update' in the node..
'Add space management', or the 'Update space
System action: None.
management' dialog.
User response: None.
System action: Tivoli Storage Manager waits until you
select 'Add' or 'Update' to apply your premigration
percentage to the system. FMV9891W Please mark either or both check boxes
before proceeding.
User response: When you have changed the space
management attribute, select 'Add' or 'Update', and Explanation: You have not marked either of the check
then the system will apply your new premigration boxes.
percentage.
System action: Tivoli Storage Manager does not
proceed with reconcile processing.
FMV9886W Enter a positive number for Column
Width. User response: Mark either or both check boxes.

Explanation: You have entered an invalid value for

Column Width. It must be a positive number between 0 FMV9892E Unable to find snapshot(s) in the local
and 18. repository.

System action: Tivoli Storage Manager continues with Explanation: The requested volume snapshot(s) were
normal operation. not found in the local repository.

User response: Enter a positive number between 0 System action: Processing stops.
and 18. User response: Ensure the operation is issued with the
proper nodename and/or server address. In a
non-cluster environment perform the operation from a
different host with the expected hostname. Retry the
operation.

Chapter 6. FMV messages 571

FMV9895W • FMV9916I

FMV9895W Space management in file system file FMV9909I Error in accessing migration candidates
system is not active. list file.
Explanation: You tried to select a file in a file system Explanation: Tivoli Storage Manager detects an error
for which space management is inactive. in reading the migration candidates list file. This file
resides in the .SpaceMan directory of the file system.
System action: Tivoli Storage Manager continues with
This message is issued only from the Motif HSM GUI,
normal operation.
which is no longer supported.
User response: Reactivate space management for the
System action: Tivoli Storage Manager proceeds with
file system, and then proceed with selecting files.
normal operation.
User response: Use the HSM Unix shell commands
FMV9901E Cannot migrate Tivoli Storage Manager
instead.
system internal file.
Explanation: You tried to select files that are used
FMV9914I Space management settings have been
internally by the HSM client. You cannot migrate Tivoli
modified successfully on file-system file
Storage Manager internal files.
system.
System action: Tivoli Storage Manager ignores your
Explanation: Space management settings have been
request.
updated successfully.
User response: None.
System action: Tivoli Storage Manager updated space
management settings for the file system.
FMV9903E Space management is deactivated for
User response: Continue with normal operation.
this file system.
Explanation: You tried to migrate a file in a file
FMV9915I Space management has been added
system for which space management is inactive.
successfully to file-system file system.
System action: Tivoli Storage Manager continues to
Explanation: Space management has been added
migrate files only in active file systems.
successfully.
User response: Reactivate space management for the
System action: Tivoli Storage Manager added and
file system, and retry the migration operation.
activated space management for the file system.
User response: Continue with normal operation.
FMV9904E Transaction failed, migration aborted.
Explanation: The specified file-name was not migrated
FMV9916I VMCUSER does not have one or more
because the file was accessed by another process during
required vSphere privileges to
the attempt to migrate it.
create/update/cancel Tasks in vSphere
System action: Tivoli Storage Manager migration is related to this operation. The operation
aborted. will continue.

User response: If you want the file migrated, stop the Explanation: VMCUSER does not have one or more
process that is accessing the file, and then retry the required vSphere privileges to create/update/cancel
migration. Tasks related to this operation. This is informational
only and does not affect the Backup/Restore operation.

FMV9908E System Error. System action: A Task related to this operation may
not show up in the vSphere Client due to missing
Explanation: Tivoli Storage Manager detects an error privileges. The operation will continue.
in reading the state of the file system. This message is
issued only from the Motif HSM GUI, which is no User response: The vSphere Task provides additional
longer supported. information about TSM initiated VM Backup/Restore
operations including progress as well as the ability to
System action: Tivoli Storage Manager proceeds with cancel these tasks from the vSphere Client. Please refer
normal operation. to the 'VMware vCenter Server user privilege
User response: Use the HSM Unix shell commands requirements' section of the 'IBM Tivoli Storage
instead. Manager for Virtual Environments: Data Protection for
VMware User's Guide.'

572 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9918E • FMV9935I

FMV9918E Cannot open migration candidates list FMV9928I Space management has been deactivated
for file-system. successfully on file-system file system.
Explanation: Tivoli Storage Manager cannot access the Explanation: Space management is deactivated
migration candidates list for the specified file system. successfully.
System action: Tivoli Storage Manager continues System action: Tivoli Storage Manager deactivated
normal operation. space management for the file system.
User response: Select OK to return. User response: Select OK to return.

FMV9919E Failed to find the expected control files FMV9929I Space management has been reactivated
for vm name. successfully on file-system file system.
Explanation: During a verify operation, the number of Explanation: Space management is reactivated
control files that were found on the server do not successfully.
match the expected amount for one or more disks.
System action: Tivoli Storage Manager reactivated
System action: The backup operation for this VM space management for the file system.
continues based on the VMVERIFYIFAction option.
User response: Select OK to return.
User response: Perform a full VM backup for this
virtual machine or specify the VMVERIFYAction option
FMV9933I Migration candidates list only exists in
to force a full VM backup.
an 'Active' file system. If you want to
make file-system file system 'Active',
FMV9920W Forcing a full vm backup for vm name. select 'Add Space Management'.
Explanation: During a verify operation, the number of Explanation: You tried to display the migration
control files that were found on the server do not candidates list for a “Native” file system (a file system
match the expected amount for one or more disks. As a to which space management has not been added).
result, a full VM backup is performed.
System action: Processing stopped.
System action: The backup operation for this VM is a
User response: Select OK to return. Select “Add Space
full backup instead of an incremental backup.
Management” if you want to add space management to
User response: Ensure the VERIFYIFAction option is the file system.
set to the wanted value.
FMV9934I Reconcile only works on an 'Active' file
FMV9921E Virtual machine disk, vm name (disk system. If you want to make file-system
label), verification check failed (size on file system 'Active', select 'Add Space
disk/ ctl size). Management'.
Explanation: During a verify operation, the number of Explanation: You tried to start reconciliation on a
control files that were found on the server do not “Native” file system (a file system to which space
match the expected amount for this disk. management has not been added). You must add space
management to a file system before starting reconcile.
System action: The backup operation for this VM
proceeds based on the VMVERIFYIFAction option. System action: Processing stopped.
User response: Perform a full VM backup for this User response: Select OK to return. Select “Add” if
virtual machine or specify the VMVERIFYIFAction you want to add space management to the file system.
option to force a full VM backup.
FMV9935I Start Threshold Migration only works
FMV9922I VMVERIFYIFLatest is enabled for vm on an 'Active' file system. If you want to
name (action: type). make file-system file system 'Active',
select 'Add Space Management'.
Explanation: This VM operation verifies the control
files from the previous backup to ensure that all Explanation: You tried to start Threshold Migration on
expected files are on the server. a “Native” file system (a file system to which space
management has not been added). You must add space
System action: The operation proceeds based on the
management to the file system first.
value of the VMVERIFYIFAction option.
System action: Processing stopped.
User response: Ensure the VERIFYIFAction option is
set to the wanted value. User response: Select OK to return. Select “Add” if

Chapter 6. FMV messages 573

FMV9936I • FMV9948E

you want to add space management to the file system.

FMV9943I Space management has already been
added to file-system file system.
FMV9936I Start Threshold Migration only works
Explanation: You tried to add space management to a
on an 'Active' file system. If you want to
file system to which space management has already
make file-system file system 'Active',
been added.
select 'Reactivate'.
System action: Processing stopped.
Explanation: You tried to start Threshold Migration on
an “Inactive” file system (a file system for which space User response: Select OK to return.
management has been deactivated). You must reactivate
space management for your file system first.
FMV9944I Space management has been deactivated
System action: Processing stopped. on file-system file system. You must
reactivate space management before you
User response: Select OK to return. Select 'Reactivate'
can remove it.
to reactivate space management for the file system.
Explanation: You tried to remove space management
from a file system for which space management has
FMV9938I Space management has not been added
been deactivated. You must reactivate space
to file-system file system. You do not
management for the file system before you can remove
need to deactivate space management.
it.
Explanation: You tried to deactivate space
System action: Processing stopped.
management on a file system to which space
management has not been added. User response: Select OK to return. Select
“Reactivate”, and then select “Remove” to remove
System action: Processing stopped.
space management.
User response: Select OK to return.
FMV9945I Space management has not been added
FMV9941I Space management has not been added to file-system file system. You do not
to file-system. If you want to add space need to remove space management.
management, select 'Add space
Explanation: You tried to remove space management
management' option. The file system
from a file system to which space management has not
will automatically be activated when
been added.
you add space management.
System action: Processing stopped.
Explanation: You tried to activate space management
on a file system to which space management has not User response: Select OK to return.
been added. You must first add space management.
The file system will automatically be activated when
FMV9947E File: file-spec is in a file system to which
the add process is complete.
space management has not been added.
System action: Processing stopped.
Explanation: You tried to migrate a file that resides in
User response: Select OK to return. Select “Add” if a file system to which space management has not been
you want to add space management to the file system. added.
System action: Tivoli Storage Manager will not
FMV9942S Space management has not been added highlight/process the file.
to file-system file system. Do you want to
User response: Switch over to the Space Manager
add space management now?
window, and add space management to the file system.
Explanation: You tried to update space management
settings for a file system to which space management
FMV9948E File: file-spec size is less than the
has not been added.
minimum size required for migration.
System action: Processing stopped.
Explanation: You tried to migrate a file that is smaller
User response: Select OK to add space management to than the minimum size required for migration. To be
the file system. Select Cancel to return. eligible for migration, a file must be larger than both
the stub file size specified for the file system plus one
byte and the block size defined for the file system.
System action: Tivoli Storage Manager will not
highlight the file.

574 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9949E • FMV9964I

User response: None.

FMV9959W IBM Tivoli Storage Manager acceptor
received a non-critical network error
FMV9949E File: file-spec is not a regular file and errno, TSM return code : TSM-rc.
therefore not qualified for migration.
Explanation: The communication problem happened
Explanation: You tried to migrate a file that is not a while listening for inbound connection but the IBM
regular file. It might be a FIFO file, a special file, a Tivoli Storage Manager acceptor continues running.
directory or a symbolic link.
System action: Processing continues.
System action: Tivoli Storage Manager will not
User response: No further action is required, it can be
highlight the file.
safely ignored.
User response: None.
FMV9960W No files selected for migrate or recall.
FMV9950W Streaming and partial recall modes can
Explanation: You requested a migrate or recall
not be set for files migrated using
operation without selecting files from the presented
external backend.
directory tree.
Explanation: Streaming or partial recall modes are not
System action: Tivoli Storage Manager cannot do the
supported for files in this mode.
migration or recall without selected files.
System action: Operation aborted.
User response: Select the files that you want to
User response: Special recall modes are only available migrate or recall, and retry the operation.
for files migrated using TSM Server as a backend.
FMV9961E Server out of migrate data storage space.
FMV9951I File: file-name has already been migrated.
Explanation: The server ran out of space in its migrate
Explanation: You tried to migrate a file that is already data storage. This message is issued only from the
migrated. Note that you may get this message if the file Motif HSM GUI, which is no longer supported.
is hard linked with another, already migrated file.
System action: Tivoli Storage Manager cannot
System action: The file is skipped. complete the migrate operation. Any files displayed in
the Successful list of the Migrate Status window were
User response: None. successfully migrated.
User response: Use the HSM Unix shell commands
FMV9953E The management class assigned to this instead.
file does not allow migration.
Explanation: The management class assigned to this FMV9962I Migration stopped by user.
file does not allow migration.
Explanation: You requested that Tivoli Storage
System action: Tivoli Storage Manager does not Manager stop the migrate operation.
migrate the file.
System action: Migration stopped.
User response: None.
User response: Continue with normal operations.
FMV9954E This file has already been migrated.
FMV9963I Selective Recall completed. Check
Explanation: The file has been previously migrated. failure list for possible errors.
System action: File is skipped. Explanation: The recall was completed.
User response: None. System action: Tivoli Storage Manager recalled the
files.
FMV9958E File 'file-namefile-namefile-name has not yet User response: Continue with normal operations.
reached the age for migration. File
skipped.
FMV9964I Selective Migration completed. Check
Explanation: This file cannot be migrated because it failure list for possible errors.
has not yet reached the age for migration.
Explanation: The migration was completed.
System action: Tivoli Storage Manager will not
highlight the file. System action: Tivoli Storage Manager migrated the
files.
User response: None.

Chapter 6. FMV messages 575

FMV9965S • FMV9992E

User response: Continue with normal operations.

FMV9989W Management class mcName specified on
the INCLUDE statement in file-name at
FMV9965S Please select a file system first. line line-number does not exist.

Explanation: You did not select any file system for the Explanation: Management class named on the
Migrate window. INCLUDE statement in the file-name file does not exist
in your assigned policy set on the server.
System action: Tivoli Storage Manager ignores this
request and continues. System action: The object is bound to the default
management class.
User response: Select a file system, a directory, and all
files you want to migrate, and then select the Migrate User response:
button to start the process. v Update the INCLUDE statement so that it specifies a
valid management class.
FMV9966S No file system has been selected. v Define the management class named on the
INCLUDE statement (if it is intended to have a
Explanation: You did not select a file system. management class with that name).
System action: Tivoli Storage Manager ignores the v Verify that the node is in the correct policy domain
request and continues. (perhaps the node was accidentally put in the wrong
policy domain, and the correct domain has the
User response: Select at least one file system and retry
management class).
the operation
v Remove the INCLUDE statement if it is no longer
necessary to bind the files to the management class.
FMV9984W PFR plugin library was not found.
Explanation: PFR plugin library should have been FMV9990W Management class mcName specified on
installed when the client was installed, but it cannot be INCLUDE statement in client option set
found. does not exist.
System action: The selected operation is not Explanation: Management class named on the
performed. INCLUDE statement in client option file does not exist
User response: None. in your assigned policy set on the server.
System action: The object is bound to the default
FMV9987W Partial recall mode is not set for management class.
full-file-name User response:
Explanation: Partial recall mode is not set for the v Update the INCLUDE statement so that it specifies a
specified file. valid management class.
System action: The recall is not performed for the v Define the management class named on the
specified file. Processing stopped. INCLUDE statement (if it is intended to have a
management class with that name).
User response: Set the partial recall mode on the file
v Verify that the node is in the correct policy domain
("dsmattr -recallmode=partialrecall" command) and
(perhaps the node was accidentally put in the wrong
re-try the operation.
policy domain, and the correct domain has the
management class).
FMV9988S As part of the remove process, all v Remove the INCLUDE statement if it is no longer
migrated files in file-system will be necessary to bind the files to the management class.
recalled from Tivoli Storage Manager
server. Do you want to continue with
the remove process now? FMV9992E The following options must be set
before running this operation:
Explanation: When you remove space management VMCHOST or VMCUSER.
from a file system, Tivoli Storage Manager recalls all
migrated files. Explanation: VMCHOST or VMCUSER is missing
from the options file.
System action: Tivoli Storage Manager waits for your
response before proceeding with the remove process. System action: Operation cannot continue without
options being set.
User response: Select Yes to remove space
management from the selected file system, or select User response: Manually edit the options file or use
Cancel to skip the remove. the preferences editor to set these options.

576 IBM Tivoli Storage FlashCopy Manager: Messages

 FMV9997W • FMV9999E

FMV9997W The selective migration, selective recall,

or policy information window is
displayed. Stop any operations, close the
window, and then retry the operation.
Explanation: When a node is contacting more than
one server for space management services, the selective
migration, selective recall, and policy information
windows may not be displayed at the same time.
System action: Tivoli Storage Manager ignores the
request.
User response: Close the selective migration, selective
recall, or policy information window, and then retry the
operation.

FMV9998E The migration server changed after the

selective migration or selective recall
window was displayed. Close the
window, and then retry the operation.
Explanation: A migrate or recall operation will not be
allowed to proceed if the user changed the migration
server after the selective migration or selective recall
window was displayed.
System action: No files will be migrated or recalled.
User response: Close the selective migration or
selective recall window, and then retry the operation.

FMV9999E ():
Explanation: This message carries diagnostic text
relating to a client process or algorithm. This
information is intended for reporting processing
exceptions and other non-standard situations that occur
on the Tivoli Storage Manager client. The (component),
(code), and (text) will vary depending upon the cause
of the message and the client process or algorithm that
issues the message.
System action: Client processing may or may not
continue depending upon the cause of this message.
User response: Examine error messages that may have
been displayed before and/or after this message and
correct any problems, if possible. If the cause of this
message can not be determined or resolved, contact
your support representative. If you contact your
support representative, the entire text of this message
should be reported.

Chapter 6. FMV messages 577

578 IBM Tivoli Storage FlashCopy Manager: Messages
Appendix. Accessibility features for the Tivoli Storage
Manager product family
Accessibility features help users who have a disability, such as restricted mobility
or limited vision to use information technology products successfully.

Accessibility features

The IBM Tivoli Storage Manager family of products includes the following
accessibility features:
v Keyboard-only operation using standard operating-system conventions
v Interfaces that support assistive technology such as screen readers

The command-line interfaces of all products in the product family are accessible.

Tivoli Storage Manager Operations Center provides the following additional

accessibility features when you use it with a Mozilla Firefox browser on a
Microsoft Windows system:
v Screen magnifiers and content zooming
v High contrast mode

The Operations Center and the Tivoli Storage Manager Server can be installed in
console mode, which is accessible.

The Operations Center help system is enabled for accessibility. For more
information, click the question mark icon on the help system menu bar.

Vendor software

The Tivoli Storage Manager product family includes certain vendor software that is
not covered under the IBM license agreement. IBM makes no representation about
the accessibility features of these products. Contact the vendor for the accessibility
information about its products.

IBM and accessibility

See the IBM Human Ability and Accessibility Center (http://www.ibm.com/able)

for information about the commitment that IBM has to accessibility.

© Copyright IBM Corp. 1995, 2014 579

580 IBM Tivoli Storage FlashCopy Manager: Messages
Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

© Copyright IBM Corp. 1995, 2014 581

 IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

582 IBM Tivoli Storage FlashCopy Manager: Messages

 Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_.

If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at http://www.ibm.com/legal/copytrade.shtml.

Adobe is either a registered trademark or a trademark of Adobe Systems

Incorporated in the United States, and/or other countries.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in

the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Java and all Java-based trademarks and logos are trademarks or

registered trademarks of Oracle and/or its affiliates.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software
Offerings”) may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user, or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect
personally identifiable information.

Notices 583
 If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies
and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.

For more information about the use of various technologies, including cookies, for
these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and
IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in the
section entitled “Cookies, Web Beacons and Other Technologies,” and the “IBM
Software Products and Software-as-a-Service Privacy Statement” at
http://www.ibm.com/software/info/product-privacy.

584 IBM Tivoli Storage FlashCopy Manager: Messages

Glossary
A glossary is available with terms and definitions for the IBM Tivoli Storage Manager family of products.

See Tivoli Storage Manager glossary (http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/

com.ibm.itsm.ic.doc/glossary.html).

To view glossaries for other IBM products, see http://www.ibm.com/software/globalization/

terminology/.

© Copyright IBM Corp. 1995, 2014 585

586 IBM Tivoli Storage FlashCopy Manager: Messages



Product Number: 5641-A06

5724-X94
5608-ACB

Printed in USA