ibm tivoli storage flashcopy manager: messages...of ibm tivoli storage manager for virtual...

IBM Tivoli Storage FlashCopy ManagerVersion 4.1.2

Messages

��

Note:Before you use this information and the product it supports, read the information in “Notices” on page 551.

Fourth edition (April 2015)

This edition applies to version 4, release 1, modification 2 of IBM Tivoli Storage FlashCopy Manager (productnumbers 5641-A06, 5724-X94, 5608-ACB) and to all subsequent releases and modifications until otherwise indicatedin new editions.

© Copyright IBM Corporation 1995, 2015.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . v

About this publication . . . . . . . . viiWho should read this publication . . . . . . . viiPublications . . . . . . . . . . . . . . vii

Chapter 1. Introduction to Tivoli StorageFlashCopy Manager messages . . . . . 1Tivoli Storage FlashCopy Manager message format . 1Tivoli Storage FlashCopy Manager messages prefixes 2

Chapter 2. FMM messages. . . . . . . 3FMM common messages . . . . . . . . . . 3FMM messages for Microsoft Management Console 182FMM messages for IBM XIV Storage Systems andRocket Device Adapter Pack storage systems . . . 183

Chapter 3. FMF messages . . . . . . 189

Chapter 4. FMX messages . . . . . . 205

Chapter 5. FMY messages . . . . . . 235

Chapter 6. FMV messages . . . . . . 263

Appendix. Accessibility features forthe Tivoli Storage Manager productfamily. . . . . . . . . . . . . . . 549

Notices . . . . . . . . . . . . . . 551

Glossary . . . . . . . . . . . . . 555

© Copyright IBM Corp. 1995, 2015 iii

iv IBM Tivoli Storage FlashCopy Manager: Messages

Tables

1. Messages prefixes by component . . . . . . 2

© Copyright IBM Corp. 1995, 2015 v

vi IBM Tivoli Storage FlashCopy Manager: Messages

About this publication

IBM® Tivoli® Storage FlashCopy® Manager provides the tools and information thatis required to create and manage volume-level snapshots on snapshot-orientedstorage systems while the applications that contain data on those volumes remainonline. Optionally, backups can be sent to Tivoli Storage Manager storage.

This publication contains explanations and suggested actions for messages that areissued by all Tivoli Storage FlashCopy Manager components:v Tivoli Storage FlashCopy Manager for UNIX and Linuxv Tivoli Storage FlashCopy Manager for VMwarev 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 Serverv Tivoli Storage FlashCopy Manager for Microsoft SQL Server

Who should read this publicationThe target audience for this publication is system administrators who service IBMTivoli Storage FlashCopy Manager components. In this publication, it is assumedthat you have a working knowledge of Tivoli Storage FlashCopy Manager.

PublicationsThe Tivoli Storage Manager product family includes IBM Tivoli Storage FlashCopyManager, IBM Tivoli Storage Manager for Space Management, IBM Tivoli StorageManager for Databases, and several other storage management products from IBM.

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

© Copyright IBM Corp. 1995, 2015 vii

http://www.ibm.com/support/knowledgecenter

http://www.ibm.com/support/knowledgecenter

viii IBM Tivoli Storage FlashCopy Manager: Messages

Chapter 1. Introduction to Tivoli Storage FlashCopy Managermessages

IBM Tivoli Storage FlashCopy Manager components issue messages with theprefixes FMM, FMF, FMX, FMY, and FMV. Explanations and suggested actions areavailable for messages that are issued by Tivoli Storage FlashCopy Managercomponents.

Tivoli Storage FlashCopy Manager message formatMessages 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 imageidentify each element of the message.

Unable To Obtain RSS Feed.

FMM 50004 E

Message PrefixMessage NumberMessage Type*

Message Text

Explanation

System Action

User Response

Explanation: An attempt to read an RSS feedwas made but could not be established.

System Action: Processing will continue.

User Response: Ensure that there is aninternet connection.

I = InformationE = ErrorS = Severe ErrorW = Warning

*

The severity codes give an indication of the severity of the issue that generated themessage. The severity codes and their meanings are as follows:

Code Severity MeaningS 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, 2015 1

Code Severity MeaningW 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 TivoliStorage FlashCopy Manager for VMware environments, some logs append an extraprefix to the message.

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

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 causedthe 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 prefixesMessages have different prefixes to help you identify the component that issues themessage. 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 forUNIX and Linux

v Tivoli Storage FlashCopy Manager forWindows Microsoft Management Console(MMC) Snap-in and Base System Services

v Tivoli Storage FlashCopy Manager forVMware

FMF Tivoli Storage FlashCopy Manager forWindows Microsoft Management Console(MMC) Snap-in and Base System Services

FMX Tivoli Storage FlashCopy Manager forMicrosoft Exchange Server

FMY Tivoli Storage FlashCopy Manager forMicrosoft SQL Server

FMV Tivoli Storage FlashCopy Manager VolumeShadow 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 StorageFlashCopy Manager components:v Tivoli Storage FlashCopy Manager for UNIX and Linuxv Tivoli Storage FlashCopy Manager for Windows Microsoft Management Console

(MMC) Snap-in and Base System Servicesv 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 forVMware.

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

Tivoli Storage FlashCopy Manager V4.1.2 common messages are listed inascending numeric order. The complete message is documented, including messageID, message text, explanation, system action, and user response.

FMM0001E Profile not specified.

Explanation: Cannot locate the profile.

System action:

User response: Ensure that a profile is available.(Oracle) Note that the BACKINT call must have thefollowing form: backint –p init<SID>.utl .

FMM0004E Function not defined. [ function ]

Explanation: BRTOOLS, BRBACKUP, or BRARCHIVEpassed an invalid argument to Data Protection for SAP.

System action:

User response: Ensure that you have the correctversion of BR*Tools installed. Valid functions are: –fbackup or –f restore or –f password or –f delete or –finquire.

FMM0005I Start of program at: time.

Explanation: The operation started at the timedenoted.

System action:

User response: None.

FMM0006E Type for backup not defined [ type ].

Please use 'file' or 'file_online'.

Explanation: Data Protection for SAP expects as thebackup type parameter only file or file_online.

System action:

User response: If you start Data Protection for SAPmanually to do a backup, ensure that the type option(–t) receives the correct arguments (file or file_online).If your Data Protection for SAP has been invoked byone of the SAP database utilities (for example,**BRBACKUP**), ensure that the SAP backup profileinit<SID>.sap is customized correctly.

FMM0007E Mode mode requires the environmentvariable environment variables to be set.

Explanation: Not all environment variables requiredhave been set. At least environment variables are missing.

System action:

User response: Set the missing environment variables.

FMM0008E The environment variable name is notset correctly. The current value is "value".

Explanation: The value of the environment variablename is wrong.

System action:


User response: Set name to an appropriate value.

FMM0009E The option 'option' must be specifiedafter the '–t FAKE' option. This is truefor all fake relevant options.

Explanation: The attempt by the AdministrationAssistant to start a backup or restore simulation failed.

System action: Processing ends.

User response: Contact IBM support.

FMM0010E The option 'option' contains an invalidargument




FMM0011E Semantic errors were detected in thefake definition: 'definition'




FMM0012I command: 'command'

Explanation: A backup or restore simulation wasstarted by the Administration Assistant. The commandline options are shown in the message.

System action: Processing continues.


FMM0020I End of program at: time.

Explanation: The operation ended at the timedenoted.

System action:


FMM0021I Elapsed time: elapsed time.

Explanation: The time needed for the completeoperation was elapsed time.

System action:


FMM0023I Time: current time Done: saved bytes(percent) of bytes. Estimated end time: endtime.

Explanation: Finished saving a specific object atcurrent time. The saved bytes amount of the total numberof bytes have been saved. percent shows the percentage.This call will be completed at the estimated end time.

System action:


FMM0024I Return code is: return code.

Explanation: Finished saving a specific object atcurrent_time. The saved_bytes amount of the totalnumber of bytes have been saved. percent shows thepercentage. This call will be completed at the estimatedend_time.

System action:

User response: For return codes other than 0, checkthe run log for warnings or error messages.

FMM0027I Time: current time Object: current numberof total number in process: file_name Size:size, MGMNT–CLASS: management class,TSM–Server: server name .

Explanation: Data Protection for SAP started savingcurrent number files at current time. The total number offiles to save is total number. The file file name iscurrently being processed. The files are transferred tothe Tivoli Storage Manager server server name, whichstores them in the management class management class.

System action:


FMM0032E Error opening file file name: system errordescription

Explanation: A system error occurred during openingof the file file name. system error description describes theerror in more detail.

System action:

User response: Read the system error description.

FMM0048E No password for node node name onserver server name given on commandline. When entering passwords in batchmode, you must supply values for allstanzas in the profile.

Explanation: The batch mode of the passwordfunction requires a data set for all Tivoli StorageManager server stanzas in the profile.

System action:

FMM0009E • FMM0048E


User response: Check the profile for active serverstanzas. Use that information and try it again.

FMM0049I Enter the password for node node nameon server server name:

Explanation: The password for the node node name onthe Tivoli Storage Manager server server name has to beentered for storing it in the DP for SAP configurationfile.

System action:

User response: Enter the password for thecorresponding Tivoli Storage Manager server.

FMM0050I Enter password for node node name onserver server name again:

Explanation: In order to avoid typing errors, you haveto enter the password twice.

System action:

User response: Enter the password again.

FMM0051I Password successfully verified for nodenode name on server server name.

Explanation: The password for the node node name onthe Tivoli Storage Manager server server name waschanged successfully.

System action:


FMM0052E Password verification for node node nameon server server name failed.

Explanation: The password you entered for the nodenode name on the Tivoli Storage Manager server servername was wrong.

System action:

User response: Enter the password again. If this errorstill exists, contact your Tivoli Storage Manageradministrator.

FMM0053I Time: current time Object: current numberof total number complete: file name with:bytes saved with description objectdescription.

Explanation: Data Protection for SAP completedsaving current number file at current time. The totalnumber of files to be saved is total number. The file file_name with the size bytes is saved with the descriptionobject description.

System action:


FMM0054I Time: current time Object: current num oftotal num complete: file name with: bytesrestored with description objectdescription .

Explanation: Data Protection for SAP completedrestoring of current num file at current time. The totalnumber of files to be restored is total num. The file filename with the size bytes is restored with the descriptionobject description.

System action:


FMM0055I Object object name with size saved withdescription description.

Explanation: The object object name was savedsuccessfully.

System action:


FMM0056I Object object name with size restored withdescription description.

Explanation: The object object name was restoredsuccessfully.

System action:


FMM0057I Time: current time Object: object namewith: size saved with descriptiondescription.

Explanation: The object object name was savedsuccessfully.

System action:


FMM0058I Time: current time Object: object namewith: size restored with descriptiondescription.

Explanation: The object object name was restoredsuccessfully.

System action:


FMM0059E Data Protection for SAP cannot find theclient options file.

Explanation: Data Protection for SAP requires a clientoptions file (<server>.opt) for each Tivoli StorageManager server. The client options files must reside inthe same directory. This directory must also contain aclient options file 'dsm.opt'. The environment variable

FMM0049I • FMM0059E

Chapter 2. FMM messages 5

DSMI_CONFIG must specify this directory.

System action:

User response: Set the environment variableDSMI_DIR to the Tivoli Storage Manager APIinstallation path. Set the environment variableDSMI_CONFIG to the path of the client options files.

FMM0060E The command parameter parameter is notrecognized.

Explanation: The command parameter parameter is notrecognized.

System action:

User response: Check the command syntax andreenter the command.

FMM0061W The output file file name is not valid.

Explanation: The specified output file file name couldnot be created.

System action:

User response: Check that file name is a valid filename on your operating system. Also check that theapplication has the appropriate permissions to createthe file within the specified directory. The directorymust already exist. If the file already exists, rename theold one.

FMM0062E The input file filename is not valid.

Explanation: Unable to read the input file file namecorrectly.

System action:

User response: Check the path and name of the inputfile and the appropriate file access permission.

FMM0063E The UTL file file name is not valid.

Explanation: Unable to read the input file file namecorrectly.

System action:

User response: Check the path and name of theprofile (UTL file) and the appropriate file accesspermission.

FMM0064E The option 'option' is not recognized.

Explanation: The option is not recognized.

System action:


FMM0065E The argument is missing for option'option'.

Explanation: Every option requires an argument.

System action:


FMM0101I Enter 'cont' to continue or 'stop' to cancel.

Explanation: If Data Protection for SAP is running inunattended mode (profile keyword BATCH), itterminates the current run if operator intervention isrequired.

System action:

User response: Enter 'cont' or 'stop'.

FMM0102I Your reply: 'reply'.

Explanation: The reply you made is confirmed.

System action:


FMM0104I Deleting the data container 'dcid' fromthe backup 'snapid' in the repository.IBM Tivoli Storage FlashCopy Managerfound that the volumes of this datacontainer do not contain a validsnapshot in the storage system.

Explanation:

System action:


FMM0105I If the newest FlashCopy targets of themirror copy sources are space efficientvolumes, then they will grow up to thesize of the sources.

Explanation: Be aware that the AIX® LVM mirrorsynchronization will change all the tracks of the mirrorcopy.


User response: If you are using space efficient targetvolumes for the mirror copy to be synchronized, thenverify the FlashCopy backups and provide enoughstorage for the growth. You can also evaluate to deletethose backups. If multiple target sets are used, then allthe other in the chain have to be deleted as well.

FMM0060E • FMM0105I


FMM0106I The newest snapshot of the mirror copywill grow up to the size of the sources.

Explanation: Be aware that the AIX LVM mirrorsynchronization will change all the tracks of the mirrorcopy.


User response: Verify the snapshot backups andprovide enough storage for the growth. You can alsoevaluate to delete those backups.

FMM0122I Backup ID: backup identifier

Explanation: The backup identifier uniquely identifiesthe backup that has been created.



FMM0123E Option -i <backup_list> not specified.

Explanation: The function –f getresources requires thespecification of the option –i <backup_list> too.

System action:

User response: Ensure that you transfer the list of thefiles to back up when you call the function –fgetresources. Note that in this case the splitint call musthave the following form: <path>/splitint –p<path>/init<SID>.fcs –f getresources –i <backup_list>...

FMM124E The LUN 'LUN name' on the datastore'datastorename' is not part of a storagesubsystem supported by IBM TivoliStorage FlashCopy Manager.

Explanation: IBM Tivoli Storage FlashCopy Managercannot backup the specified datastore because itcontains at least one LUN of a storage subsystemwhich is not supported.


User response: At least one LUN of the specifieddatastore is not part of a storage subsystem that issupported by IBM Tivoli Storage FlashCopy Manager.Remove the LUN from the datastore.

FMM0127E The backup corresponding to thisconsistency group cg cannot be deletedas it is not the oldest in the cascade ofdependent flashcopy maps.

Explanation: The specified backup is not the oldest ina cascade of flashcopy maps and cannot be deleted as ithas dependencies with the remaining maps in thecascade.

System action: Process stops.

User response: This operation can be retried when

there are no longer any more dependencies on thisbackup.

FMM128E The 'disk names' virtual disk(s) of thevirtual machine 'VM name' have a disktype which is not supported by IBMTivoli Storage FlashCopy Manager. Thevirtual machine is not included in thebackup.

Explanation: The specified virtual disks of thespecified virtual machine have a type which is notsupported by IBM Tivoli Storage FlashCopy Manager.The specified virtual machine will not be included inthe backup and not be restorable.


User response: Change the disk type to a type that issupported by IBM Tivoli Storage FlashCopy Manager.Please refer to the User's manual or the Pre-Installationchecklist for details.

FMM129E The following error was returned by theVSphere API: 'vSphere error'.

Explanation: The VSphere API issued the specifiederror.


User response: Try to interpret the vSphere errormessage and to fix the cause of the issue.

FMM0136I Start of the reconciliation between theIBM Tivoli Storage FlashCopy Managerrepository and the storage system.

Explanation: IBM Tivoli Storage FlashCopy Manageris checking the validity of the backups listed in therepository in the storage system.

System action:


FMM0137I End of the reconciliation.

Explanation: IBM Tivoli Storage FlashCopy Manageris finished checking the validity of the backups listed inthe repository in the storage system.

System action:


FMM0138I Time stamp: current_time.

Explanation: IBM Tivoli Storage FlashCopy Managerperforms several tasks in sequence (for example,initiate the FlashCopy of source volumes on theproduction system and mount file systems on thebackup system). Tracking the various time stampsallows analysis of how long each task took.

FMM0106I • FMM0138I


System action:


FMM0142I Snapshot started ...

Explanation: The command with the 'flashcopy'function has been issued on the production system, andthe program splitint waits until this action has finished.

System action:


FMM0143I Snapshot successful.

Explanation: The command for the snapshot–basedcopy of the volume pairs has completed successfully onthe production system.

System action:


FMM0144W Information from DP for mySAP wasnot found.

Explanation: The exchange data between IBM TivoliStorage FlashCopy Manager and Tivoli StorageManager for ERP was not found. The information isexchanged through the call of the IBM Tivoli StorageFlashCopy Manager's function ?set_bki_info? bybackint before the Tivoli Storage Manager backup. Forolder versions, the information is first exchanged afterthe Tivoli Storage Manager backup during theexecution of the unmount function. Either the TivoliStorage Manager for ERP you have installed does notsupport IBM Tivoli Storage FlashCopy Manager, orTivoli Storage Manager for ERP has failed after asuccessful FlashCopy and mount.

System action:

User response: Check the run logs of tsm4acs. Thiserror could have various reasons and should beresolved depending on the specific situation: Case 1:tsm4acs has finished successfully. Result: The backupon disk (FlashCopy target volumes) as well as the onedone to the Tivoli Storage Manager server are valid.However, IBM Tivoli Storage FlashCopy Managercannot show the backup ID in its report when usingthe function 'inquire'. Reason for warning: It is verylikely that Tivoli Storage Manager for ERP (AIXversion) does not have IBM Tivoli Storage FlashCopyManager support (prior to version 3.1.0.3). Action:Install the appropriate Tivoli Storage Manager for ERPversion. Case 2: tsm4acs has terminated abnormally.Result: Carefully check the run log of tsm4acs for anyFMM, ANS or ANR error messages. Most likely, thebackup on disk (FlashCopy target volumes) is valid(check with splitint –f inquire whether PSI isPSI_MOUNT_DONE or PSI_UNMOUNT_DONE), butthe backup to the Tivoli Storage Manager server isinvalid. Cause: Problems with the network or on the

Tivoli Storage Manager server caused Tivoli StorageManager for ERP to fail when running a backup.Action: Depending on the error message, eliminate thereason for not getting a successful backup to the TivoliStorage Manager server.

FMM0147I The IDS control file exists and a newbackup cycle entry has been created.

Explanation: At the start of the function –fgetresources, IBM Tivoli Storage FlashCopy Managerinserts a record in the IDS control file for the newbackup cycle. This record is updated as the status ofthe new backup cycle changes (such as FlashCopytarget volumes/file systems being mounted orunmounted).

System action:


FMM0148E The backup ID was not passed by DPfor mySAP. This snapshot backupcannot be used for snapshot restore.

Explanation: Before this error, the warning IDS1041Wis displayed. The backup ID is mandatory for using asnapshot backup for the restore.

System action:

User response: To use snapshot restore, ensure thatyou have installed DP for SAP (backint) version 3.3.10or higher.

FMM0149E The IDS control file is corrupt!

Explanation:

System action:

User response:

FMM0150I The IDS control file 'ids_control_file' doesnot exist, it will be created.

Explanation: IBM Tivoli Storage FlashCopy Managerwrites the first record to the IDS control file specified inthe entry IDS_CONTROL_FILE of the profile.

System action:


FMM0151E The IDS control file has no entry.

Explanation: IBM Tivoli Storage FlashCopy Managerhas found the IDS control file, but it has no records.This error occurs when you start one of the functionsinquire, withdraw or unmount before you have run the'flashcopy' function for the first time.

System action:

User response: The problem is resolved after you run



at least one tsm4acs with a successful FlashCopy.

FMM0152E The IDS control file must be read orinserted before update.

Explanation: IBM Tivoli Storage FlashCopy Managerhas detected a logical error when processing the IDScontrol file.

System action:

User response: Contact Tivoli Storage Manager forERP support.

FMM0153W The value of the field 'field_name' in thefile 'file_name' is empty.

Explanation: The program tsm4acs updates the IDSrepository after the Tivoli Storage Manager backup butalso in case of a disk–only backup. A temporary file iscreated with the following format: >>> backint_dataBID <backup id> UTL <name of the application profileused> INF <DPF backup ID> EBC <log directory> EBB<backup type> EBR <first active log> <<< backint_data>>> input_file <file list> <<< input_file If one of thefields of the topic ?backint_data? is empty (that is,missing), this message is displayed. If the backup ID isempty, the process terminates with error IDS1036E.

System action:


FMM0154W Info data from DP for mySAP/tmp/bki<SID>.ids cannot be read.

Explanation: Before the unmount process, IBM TivoliStorage FlashCopy Manager reads /tmp/bki<SID>.ids,which contains information about the backup that wasdone by Tivoli Storage Manager for ERP. Among theinformation read is: v Backup ID v Util file used for thebackup v A list of the files used for the backup v Thebackup type This message is issued if Tivoli StorageManager for ERP terminated unsuccessfully for somereason.

System action:

User response: Ensure that Tivoli Storage Manager forERP runs successfully.

FMM0155I The maximum number of backup cyclesin the IDS control file has been reached.

Explanation: The maximum number of backupscontrolled via the parameter BACKUP_MAX will beexceeded with the new inserted record. If theparameter is not set, the program uses the defaultvalue of 30.

System action:


FMM0156I Delete backup cycle with BSEQ_N =beseq_n and all the associated files ...

Explanation: The program deletes the oldest recordwith the backup sequence number <bseq_n> becausethe maximum number of records has been reached. Inaddition, the oldest reports and traces associated withthat backup cycle are deleted.

System action:


FMM0157W Directory Path 'directory' for the reportfiles does not exist. Using the currentdirectory.

Explanation: The directory entry of the parameterLOG_TRACE_DIR in the profile could not be found.The current directory is used for the log and trace files.

System action:

User response: To avoid directories cluttered withreports and traces, the parameter LOG_TRACE_DIRshould be used, or the directory it specifies must becreated if necessary.

FMM0158I Start of listing of importing volumegroups/mounting file systems ...

Explanation: After initiating the FlashCopysource/target volumes on the production system, IBMTivoli Storage FlashCopy Manager makes thecorresponding target volumes available to the backuphost. A list of mount points or volume groups isshown.

System action:


FMM0159I End of listing.

Explanation: This message marks the end of the list ofmount points or volume groups.

System action:


FMM0160I The unmount process will be skippedbecause the progress status indicator(PSI) has a value of 'psi'.

Explanation: When the 'withdraw' function is started,the unmount process is performed only if the PSI has avalue of PSI_MOUNT_STARTED orPSI_MOUNT_DONE.

System action:

User response: The documentation shows thepermissible functions depending on the backupprogress status indicator.



FMM0162E The version of the splitint programmust be the same on the backup andproduction system.

Explanation: The version of IBM Tivoli StorageFlashCopy Manager on the production system isdifferent from the version on the backup system.

System action:

User response: Ensure that you install the sameversion of IBM Tivoli Storage FlashCopy Manager onthe production and backup systems. You obtain theversion number when you start splitint withoutparameters.

FMM0163I Enter the password for the user 'user ID':

Explanation: The password for the user ID <user ID>has to be entered. It is encoded and stored in a filespecified in the parameter CONFIG_FILE. Note thatthis user ID and password must be the same on theproduction and backup systems. The IBM TivoliStorage FlashCopy Manager program splitint uses theuser ID to execute a remote shell on the productionsystem.

System action:

User response: Enter the password for thecorresponding user ID.

FMM0164I Enter the password for the user 'user ID'again:

Explanation: To avoid typing errors, you must enterthe password twice.

System action:

User response: Enter the password again.

FMM0165I The password entry does not match,please try again.

Explanation: The two entered passwords are notidentical. You must enter the password again.

System action:

User response: Enter the password again. You arepermitted three attempts before the programterminates.

FMM0166E No password stored.

Explanation: The two entered passwords are notidentical. You have tried three times, and thepasswords were different in each case.

System action: You must start the splitint programwith the function -f password again. If no password isstored, or it is invalid, splitint fails when the 'flashcopy'function is used.

User response:

FMM0167E The config file named 'config_file' couldnot be opened. Please call 'splitint' withthe function 'password' to create thisfile.

Explanation: IBM Tivoli Storage FlashCopy Manageris unable to read the configuration file <config_file>.

System action:

User response: This error could have various reasons.Try the following: 1. Call splitint with the 'password'function to create the file. 2. Check the path of theconfiguration file. The path must be specified in theprofile (parameter CONFIG_FILE). 3. Make sure thatthe file access permissions are set correctly.

FMM0172I Start of listing of exported volumegroups/unmounting file systems ...

Explanation: A list of unmount points or exporteddisk groups is shown. Due to the use of the unmountfunction on the backup host, IBM Tivoli StorageFlashCopy Manager unmounts the file systems andexport volume groups on the backup host that hadbeen imported or mounted when the IBM TivoliStorage FlashCopy Manager 'flashcopy' function wasexecuted.

System action:


FMM0173I Start of withdraw of the target–sourcepairs ...

Explanation: The command with a withdraw has beenissued from the backup system to the primary CopyServices server for the storage system.

System action:


FMM0177E You cannot run the function 'function' ifthe progress status indicator (PSI) has avalue of 'psi'.

Explanation: The backup cycle was left in a state thatdoes not allow IBM Tivoli Storage FlashCopy Managerto start the specified function.

System action:

User response: The documentation shows thepermissible functions depending on the backupprogress status indicator.



FMM0182E The option –f flashback can only beused on the production system.

Explanation:

System action:

User response:

FMM0183E Topic named 'topicname' could not befound in the file 'filename'.

Explanation: IBM Tivoli Storage FlashCopy Managerwas able to read the file <filename> but the expectedentry for the topic <topicname> was not found.

System action:

User response: If the affected file is in the directorydenoted by the parameter VOLUMES_DIR, checkwhether the topic name has the format: >>>volumes_set_# Where # is a placeholder for the volumeset number (1, 2, etc.) If the affected file is another file,you likely have another error prior to this one.Otherwise, contact Tivoli Storage Manager for ERPsupport.

FMM0184E The source volume <serial number>cannot be specified as a target volumein the .fct file.

Explanation: IBM Tivoli Storage FlashCopy Managerfound one of the source volumes in the list of targetvolumes in the init<SID>.fct file.

System action:

User response: Ensure that the target volumes list ininit<SID>.fct does not contain any of the sourcevolumes.

FMM0185E No target volumes were specified forthe set 'volumes_set_#' in the file'filename'.

Explanation: IBM Tivoli Storage FlashCopy Managerhas read file <filename> in the directory specified byVOLUMES_DIR. The format of the file is correct, butthe list of target volumes is missing.

System action:

User response: See the description of the targetvolumes file in the documentation.

FMM0186E The backup ID (timestamp) is empty.This snapshot backup cannot be usedfor a snapshot restore.

Explanation: Before this error, the warning IDS1041Wis displayed. The backup ID (timestamp) is mandatoryfor using a FlashCopy backup for the restore. Theprogram tsm4acs was not able to generate a timestamp.

System action:

User response: Check for preceding errors. Checkwhether the backup to Tivoli Storage Manager endedsuccessfully.

FMM0187I Creating a semaphore for the criticalpart of importing/exporting ...

Explanation: When multiple production systems run abackup via a single backup system at the same time,IBM Tivoli Storage FlashCopy Manager ensures that thecritical parts of the code run for a single instance of theprogram at a time. These phases are: 1. When theFlashCopy has been done and resources (volumegroups and file systems) are being enabled 2. Before theFlashCopy relationship is withdrawn and resources(volume groups and file systems) are being disabled.For this synchronization process, a semaphore with thefixed key 0x88886666 is created

System action:


FMM0188I Trying to set the semaphore for thecritical part of importing/exporting ...

Explanation: If the IBM Tivoli Storage FlashCopyManager semaphore is already allocated, the programwaits until it is released. Otherwise, the program sets itand pass into the critical part of the run. Anotherinstance arriving at this point now has to wait for therelease of the semaphore.

System action:


FMM0189I Semaphore released.

Explanation: After the program has passed the criticalpart of the run, the semaphore is released.

System action:


FMM0190W The semaphore could not be created.System error sys_errno: sys_message

Explanation: If IBM Tivoli Storage FlashCopyManager could not create the semaphore, the systemerror number and message are issued as a warning.The concurrent run of multiple production systemswith a single backup system will not work properly.

System action:

User response: Check the system error number andmessage with the system administrator.

FMM0182E • FMM0190W


FMM0191W The semaphore could not be initialized.System error sys_errno: sys_message

Explanation: If IBM Tivoli Storage FlashCopyManager could not initialize the semaphore, the systemerror number and message are issued as a warning.The concurrent run of multiple production systemswith a single backup system will not work properly.

System action:


FMM0192W The semaphore could not be allocated.System error sys_errno: sys_message

Explanation: If IBM Tivoli Storage FlashCopyManager could not allocate the semaphore, the systemerror number and message are issued as a warning.The concurrent run of multiple production systemswith a single backup system will not work properly.

System action:


FMM0193W The semaphore could not be released.System error sys_errno: sys_message

Explanation: If IBM Tivoli Storage FlashCopyManager could not allocate the semaphore, the systemerror number and message are issued as a warning.The concurrent run of multiple production systemswith a single backup system will not work properly.

System action:


FMM0196I This is your last chance to stop theSnapshot Restore. Enter 'c[ont]' tocontinue, 's[top]' to cancel.

Explanation: IBM Tivoli Storage FlashCopy Managerasks the user a last time before the program beginswith the restore process. The original data isoverwritten with the data of the snapshot backup.

System action:

User response: Be sure that you want to restore fromthe FlashCopy backup.

FMM0199W One or more errors were founddisabling the production systemresources.

Explanation: Before the actual snapshot restore to thedatabase volume occurs, IBM Tivoli Storage FlashCopyManager does the following: 1. Unmounts the databasefile systems 2. For LVM mirroring: v Remove the mirror

copies from the logical volumes v Remove the mirrorphysical volumes from the volume groups 3. Removethe volume group from the AIX ODM One or more ofthese operations have ended with errors. IBM TivoliStorage FlashCopy Manager issues a warning but thesnapshot restore continues.

System action:


FMM200E The following remote mirrorrelationships are not assigned to aconsistency group: 'list of rc relations'.

Explanation: IBM Tivoli Storage FlashCopy Manageris configured to take the FlashCopy from the remotecluster. However the remote mirror relationships listedin this message are not assigned to a consistency group.

System action: The software process ends.

User response: Add the remote mirror relationshipsidentified in this message to the one unique consistencygroup containing all the remote relationships.

FMM0201E The NLS catalog could not be loaded.Make sure that the catalog<fully_qualified_catalog_name> exists.

Explanation: DP for Snapshot Devices uses an EnglishNLS catalog for the LVM and storage–system parts ofthe product. The installation process copies the catalogto the displayed path.

System action:

User response: Check for errors during the installationprocedure.

FMM0202E You cannot run the function 'function' ifthe restore status indicator (RSI) ontarget set 'id' has a value of 'RSI_START'.

Explanation: If the restore status RSI of the target sethas a value of RSI_START, then a snapshot restore isstill running in the background. You cannot start aFlashCopy backup again until the background copy tothe database volume is finished. In this case the RSIvalue is either RSI_DISKONLY or in case of LVMmirroring RSI_DISKANDLVM.

System action:

User response: Wait until the FlashCopy backgroundprocess is finished.

FMM203E The following Metro or Global Mirrortarget volumes are in different clusters:'listOfVdisks'.

Explanation: For a remote FlashCopy to be started,IBM Tivoli Storage FlashCopy Manager softwarerequires the Metro Mirror or Global Mirror target

FMM0191W • FMM203E


volumes to be in the same SVC cluster.


User response: Move the Metro Mirror or GlobalMirror target volumes identified in this message to aunique target SVC cluster.

FMM204E Parameter TAKEOVER_HOST_NAME isrequired in the storage section of theprofile for a restore into the takeoverhost.

Explanation: For a remote restore on the takeover hostto be started, IBM Tivoli Storage FlashCopy Managersoftware requires the parameterTAKEOVER_HOST_NAME to be specified in thesection DEVICE_CLASS of the profile.


User response: Specify the parameterTAKEOVER_HOST_NAME in the sectionDEVICE_CLASS for remote FlashCopy backups usingthe same value as defined in the storage systems.

FMM0205I The database is now ready for Snapshot.

Explanation:

System action:

User response:

FMM206E The source volumes are in multipleremote consistency groups.

Explanation: The remote FlashCopy cannot start whenthe source and target volumes are in multiple remoteconsistency groups.

System action: The software process ends withoutstarting the remote FlashCopy.

User response: Change the relationship between thesource and target volumes. For the remote FlashCopyto start, the source and target volumes must be in thesame remote consistency group.

FMM207E The following source volumes are eithernot in a remote mirror relationship ornot the master volume: 'list of volumes'.

Explanation: IBM Tivoli Storage FlashCopy Manageris configured to take the FlashCopy from the remotecluster. However the volumes listed in this message arenot in a remote mirror relationship or they are not themaster volume in a relation.


User response: For the source volumes identified inthe message, place the volumes in a remote mirrorrelationship or define the source volume as the mastervolume.

FMM208E The state 'cgstate' of the Metro Mirrorconsistency group 'cgname' is not validfor a consistent FlashCopy backup.

Explanation: For a remote FlashCopy to be started,IBM Tivoli Storage FlashCopy Manager softwarerequires the Metro Mirror consistency group to be in aconsistent synchronized state.


User response: The consistency group that containsthe Metro Mirror relationships, between the source andtarget volumes, should be started before the FlashCopybackup begins. In addition, the Metro Mirrorconsistency group should be in a consistentsynchronized state.

FMM210W The following Global Mirrorconsistency group is still copying:'cgname'.

Explanation: For a remote FlashCopy to be started,IBM Tivoli Storage FlashCopy Manager softwarerequires the Global Mirror consistency group to be in aconsistent synchronized state.

System action: The software process continues.

User response: The consistency group that containsthe Global Mirror relationships, between the source andtarget volumes, should be started before the FlashCopybackup begins. In addition, the Global Mirrorconsistency group should be in a consistentsynchronized state.

FMM211I Waiting 'resttime' seconds, but notexceeding the value TIMEOUT_FLASHof 'timeout' seconds ...

Explanation: For a remote FlashCopy to be started,IBM Tivoli Storage FlashCopy Manager softwarerequires the Global Mirror consistency group to be in aconsistent synchronized state. When the consistencygroup is still copying, IBM Tivoli Storage FlashCopyManager runs maximal the time specified by theparameter TIMEOUT_FLASH to wait until theconsistency group becomes the state 'consistentsynchronized'.

System action: None.


FMM0212I New assigned Backup SequenceNumber backup sequence number

Explanation:

System action:

User response:



FMM0213E IBM Tivoli Storage FlashCopy Managerdoes not overwrite theACS_REPOSITORY repository pathcreated with Tivoli Storage Manager forAdvanced Copy Services as this wouldinvalidate all FlashCopy backupscreated with Tivoli Storage Manager forAdvanced Copy Services. If you specifya different path for parameterACS_REPOSITORY, you can continue torestore FlashCopy backups created withTivoli Storage Manager for AdvancedCopy Services until the target set isreused by IBM Tivoli Storage FlashCopyManager. Optionally, you can removethe current ACS_REPOSITORY if it isacceptable to lose FlashCopy backupscreated with Tivoli Storage Manager forAdvanced Copy Services. In either case,backups to Tivoli Storage Managercreated by Tivoli Storage Manager forAdvanced Copy Services remainavailable for restore.

Explanation: The value repository path for parameterACS_REPOSITORY points to a repository that wascreated by Tivoli Storage Manager for Advanced CopyServices. Backups created with Tivoli Storage Managerfor Advanced Copy Services can not be restore withIBM Tivoli Storage FlashCopy Manager.

System action: Processing stops.

User response: Specify a different path for theACS_REPOSITORY. The backups created with TivoliStorage Manager for Advanced Copy Services willremain intact and can be restored using Tivoli StorageManager for Advanced Copy Services. If all thebackups created with Tivoli Storage Manager forAdvanced Copy Services are no longer required pleasedelete the entire directory and try again.

FMM0214W The restore status indicator (RSI) has avalue of 'RSI_INVALID' on target set 'id'.

Explanation: If the restore status RSI of the target sethas a value of RSI_INVALID, this means that asnapshot restore was initiated but did not terminate.Nevertheless, IBM Tivoli Storage FlashCopy Managerissues this warning and continue with the FlashCopybackup.

System action:

User response: Check whether the FlashCopy backupended successfully.

FMM215E The state of the Global Mirrorconsistency group has not become thevalue 'consistent synchronized' insidethe required periode of time.

Explanation: For a remote FlashCopy to be started,

IBM Tivoli Storage FlashCopy Manager softwarerequires the Global Mirror consistency group to be in aconsistent synchronized state. When the consistencygroup is still copying, IBM Tivoli Storage FlashCopyManager waits, for the maximum amount of timespecified by the parameter TIMEOUT_FLASH, for theconsistency group to change to the 'consistentsynchronized' state. If the consistency group does notchange to the 'consistent synchronized' state, this errormessage is displayed.


User response: The consistency group that containsthe Global Mirror relationships, between the source andtarget volumes, should be started before the FlashCopybackup begins. In addition, the Metro Mirrorconsistency group should be in a consistentlysynchronized state.

FMM216E The state 'cgstate' of the Global Mirrorconsistency group 'cgname' is not validfor a consistent FlashCopy backup.

Explanation: For a remote FlashCopy to be started,IBM Tivoli Storage FlashCopy Manager softwarerequires the Global Mirror consistency group to be in aconsistent synchronized state.


User response: The consistency group that containsthe Global Mirror relationships, between the source andtarget volumes, should be started before the FlashCopybackup begins. In addition, the Global Mirrorconsistency group should be in a consistentsynchronized state.

FMM217E The primary source volume with serialnumber 'sernumber' is attached to thelocal host. A remote backup can only berestored on the takeover host.

Explanation: Remote restore cannot be performedfrom the host on the local site. Perform restore from thetakeover host on the remote site instead.


User response: Retry remote restore on the takeoverhost at the remote site.

FMM218E The storage device has not theminimum required firmware version'version'.'release'.'revison' installed.

Explanation: For a remote FlashCopy to be started onGlobal Mirror with Change Volumes, IBM TivoliStorage FlashCopy Manager software requires aminimum firmware level on the storage device.


User response: Upgrade the firmware version on the



storage device and try the operation again.

FMM219E A timeout occurred while waiting forthe 'cgname' consistency group thatcontains the Global Mirror relationshipswith Change Volumes to besynchronized on remote site.

Explanation: For a remote FlashCopy to be started ona Global Mirror with Change Volumes, IBM TivoliStorage FlashCopy Manager requires the Global Mirrorconsistency group to be in a consistent synchronizedstate.


User response: The consistency group that containsthe Global Mirror relationships, between the source andtarget volumes, must be started before the FlashCopybackup begins. In addition, lower the Cycling Periodtime and try the operation again.

FMM220E The Global Mirror 'cgname' consistencygroup must have change volumesassigned.

Explanation: For a remote FlashCopy to be started ona Global Mirror, IBM Tivoli Storage FlashCopyManager requires that the Global Mirror consistencygroup has the change volumes function assigned.


User response: Create change volumes for theconsistency group that contains the Global Mirrorrelationships.

FMM0225I Enabling the volumes and filesystems ...

Explanation: After the FlashCopy, the target volumesattached to the backup machine are imported in theoperating system and the file systems are mounted.

System action:


FMM226E The following line could not be parsed:infile line

Explanation: The specified line contains a syntax error.It cannot be parsed.


User response: Correct the syntax on the line andretry the operation.

FMM227E The address of the datastore 'datastoreURL' is not valid. It is not part of thebackup.

Explanation: The specified datastore that is part ofthis input file cannot be found. It will not be included

in the backup and not be restorable.

System action: Processing continues but the specifieddatastores will not be included in the backup.

User response: Correct the input file so that itcontains a valid datastore URL if this datastore is to beincluded in the backup.

FMM228E No virtual machines are available forprocessing after the input file isevaluated.

Explanation: After the input file has been evaluated,there are no virtual machines that can be processed.


User response: Verify that the input file contains allthe virtual machines that should be evaluated. Modifyyour input file so that there are virtual machines toprocess.

FMM229E The datastore 'datastore name' containsLUNs from more than one storagesubsystem. IBM Tivoli StorageFlashCopy Manager can support LUNsfrom only one storage subsystem.

Explanation: The specified datastore contains LUNsfrom different storage subsystems.


User response: Modify the datastore so that itcontains only LUNs from one storage subsystem.

FMM230E The backup type 'backup type' is notvalid.

Explanation: The specified backup type is not valid.


User response: Change the value to a valid backuptype.

FMM231W The raw device-mapping disk(s) 'disknames' of the virtual machine 'VM name'are excluded from backup. A laterrestore of the virtual machine ispossible, but the restore does notinclude these disks.

Explanation: The specified virtual disk(s) of thespecified virtual machine are raw device-mapping diskswhich are not included in the hardware snapshotbackup. Hence, a restore of the virtual machine onlyrestores its standard virtual disks but not the rawdevice-mapping disks.


User response: The raw device-mapping disks might

FMM219E • FMM231W


be re-added manually after the virtual machine hasbeen restored.

FMM232I Deleting the remote mirror relationshipsfor the consistency group: 'cgname'.

Explanation: For a remote FlashCopy backup to berestored into the takeover host, IBM Tivoli StorageFlashCopy Manager software requires to delete theremote copy relationships if the SVC version used isearlier than 6.2.



FMM233W For the virtual machine 'VM name' thebackup mode SNAPSHOT_INCL_MEMis changed to SNAPSHOT_EXCL_MEMbecause it has independent disk(s)attached: 'disk names'.

Explanation: In principle, VSphere does not supportsnapshots including the virtual machine's memory forvirtual machines with independent disks attached.However, snapshots excluding the virtual machine'smemory are supported. For the specified virtualmachine the snapshot mode is changed from includingto excluding memory to allow the backup process toproceed.


User response: A snapshot that excludes the virtualmachine's memory is not as consistent as a snapshotthat includes the virtual machine's memory. Snapshotconsistency also depends on the application and theprecautions in place to ensure a consistent state beforethe backup is performed. As an alternative, the backupmode can be set to SUSPEND.

FMM234W The raw device-mapping disk(s) 'disknames' of the virtual machine 'VM name'were excluded during backup. Thus therestored virtual machine does notinclude these disks.

Explanation: The specified virtual disk(s) of thespecified virtual machine are raw device-mapping disksthat are not included in the snapshot backup. When thevirtual machine is restored those are removed from itsconfiguration.


User response: The raw device-mapping disks mightbe re-added manually after the virtual machine hasbeen restored.

FMM235I Stopping the remote mirrorrelationships for the consistency group:'cgname'.

Explanation: For a remote FlashCopy backup to berestored into the takeover host, IBM Tivoli StorageFlashCopy Manager software requires to stop theremote copy relationships if the SVC version used is 6.2or higher.



FMM0236I Disabling the volumes and filesystems...

Explanation: Before the snapshot restore from thebackup to the production volumes, the productionvolumes and file systems are disabled. The followingactions are started: v Unmount v Remove devices v

Remove logical volumes v Vary off the volume group v

Export volume groups.

System action:


FMM237I Starting the remote mirror relationshipsfor the consistency group: 'cgname'.

Explanation: For a remote FlashCopy backup to berestored into the takeover host, IBM Tivoli StorageFlashCopy Manager software requires to stop theremote copy relationships if the SVC version used is 6.2or higher. After the restore is complete, IBM TivoliStorage FlashCopy Manager will restart the remotemirror relationships.



FMM238W The original resource pool path cannotbe found: 'resource pool name'. The virtualmachine 'VM name' is restored to theroot resource pool of the host 'host name'.

Explanation: The named virtual machine cannot beassociated to the vApp or resource pool. The vApp orresource pool that it was associated to during thebackup process is not available at restore time. In theintervening time between backup and restore, the vAppwas deleted, renamed, or moved.


User response: After the restore process is completed,the virtual machine can be reassigned to either theappropriate resource pool or vApp.

FMM232I • FMM238W


FMM239W The raw device mapped disk(s) 'disknames' of the virtual machine 'VM name'were excluded during backup. Thus,they have been removed from theconfiguration of the attached virtualmachine.

Explanation: The specified virtual disk(s) of thespecified virtual machine are raw device mapped diskthat are not included in the snapshot backup. When thevirtual machine is attached those are removed from itsconfiguration.


User response: Raw device mapped disks might bere-added manually to the attached virtual machine.

FMM0240E The parameterHARDWARE_ID_LVM_MIRROR forthe target set 'target_set_id' is set in the.fct–file 'file_name', but the productionlogical volumes are not mirrored.

Explanation: The HARDWARE_ID_LVM_MIRRORparameter should only used in an LVM mirrorenvironment.

System action:

User response: If you want to use this feature youneed to mirror the production logical volumes onsource volumes residing on different hardware units.Otherwise, remove the parameterHARDWARE_ID_LVM_MIRROR parameter from the.fct file.

FMM0261I A disk–only backup (option –d) wasinvoked, forcing the parameter'FLASHCOPY_TYPE' of the .fcs–file to'COPY'.

Explanation: If you specified a disk–only backup viathe parameter -d and the parameter'FLASHCOPY_TYPE' of the .fcs file has the value ofNOCOPY, IBM Tivoli Storage FlashCopy Manager setsthe value to COPY.

System action:


FMM265W A new background monitor has beenstarted. The currently registeredbackground monitor will shut downnow and the new background monitorwill be used for further processing.

Explanation: A second background monitor has beenregistered at the management daemon. Since only onebackground monitor is allowed to be registered thecurrently registered background monitor will be shutdown now.

System action: The old background monitor will beshut down.

User response: Check your configuration. Only onebackground monitor should be running.

FMM0266E The storage device <storage device> is notsupported.

Explanation:

System action:

User response:

FMM267I Adding the remote mirror relationshipsto the consistency group: 'cgname'.

Explanation: For a remote FlashCopy backup to berestored into the takeover host, IBM Tivoli StorageFlashCopy Manager software requires to delete theremote copy relationships if the SVC version used is 6.1or lower. After restore completes, IBM Tivoli StorageFlashCopy Manager adds the remote mirrorrelationships to the consistency group.



FMM0268E The information of the source / targetvolumes could not be found.

Explanation: The executable file 'splitint' is startedautomatically as a daemon (sometimes referred as thebackground monitoring process) to monitor thebackground copy. An attempt to obtain the status of thecopy process has failed.

System action:

User response: Check the error log filesplitint_[p|b]_runagent_jjjjmmddHHMMSS.log in thedirectory specified in the parameter LOG_TRACE_DIRof the .fcs file. Check the availability of the storagesystem using the applicable tool (STORWATCHSpecialist, DS Storage Manager, or SVC console). Checkthe parameters in the .fcs file: v

COPYSERVICES_PRIMARY_SERVERNAME v

COPYSERVICES_SERVERPORT v

COPYSERVICES_USERNAME Also verify theavailability of the CIM agent and its connection to thestorage system as described in the storage–systemdocumentation.

FMM0281W Warning: Could not connect to theadmin assistant.

Explanation:

System action:

User response:

FMM239W • FMM0281W


FMM0282E The incremental FlashCopy cannot berefreshed. Possible reasons are: 1. Youadded a new source volume 2. You triedto start an offline FlashCopy Backupafter an online FlashCopy BackupProblem solution: Run the withdrawfunction with option '–n TargetSetID'and afterwards restart the FlashCopyBackup.

Explanation:

System action:

User response:

FMM0283E The incremental FlashCopy cannot berefreshed. The source/target pairs arenot in an incremental FlashCopyrelation. Problem solution: Run thewithdraw function with option '–nTargetSetID' and afterwards restart theFlashCopy Backup.

Explanation:

System action:

User response:

FMM0285W All source/target pairs are in anincremental FlashCopy relation. DP forSnapshot Devices will override thevalue 'flashcopy type' of the parameterFLASHCOPY_TYPE to 'INCR'.

Explanation:

System action:

User response:

FMM0286I All source/target pairs are in anincremental FlashCopy relation.

Explanation:

System action:

User response:

FMM0287I No source/target pairs are in anincremental FlashCopy relation.

Explanation:

System action:

User response:

FMM0288I Not all source/target pairs are in anincremental FlashCopy relation.

Explanation:

System action:

User response:

FMM0309E Cannot read file: filename.

Explanation: IBM Tivoli Storage FlashCopy Manageris unable to read the data file <filename>.

System action:

User response: Check the access permissions of theaffected file and try again.

FMM0310E Cannot write file: filename.

Explanation: IBM Tivoli Storage FlashCopy Manageris unable to write to the data file filename. The affectedfiles could be: v <LOG_TRACE_DIR>/splitint_b_<date_time_stamp>.log v <LOG_TRACE_DIR>/splitint_p_ <date_time_stamp>.log v

<LOG_TRACE_DIR>/splitint_b_<date_time_stamp>.trace v <LOG_TRACE_DIR>/splitint_p_ <date_time_stamp>.trace v <config_file> v

<ids_control_file> v the field value EXCHANGE_FILEin a backup cycle record.

System action:

User response: Check the access permissions of theaffected file and try again.

FMM0311E Request canceled by user

Explanation: (Oracle) BACKINT terminated at user'srequest. (DB2) Program terminated at user's request.

System action:


FMM312E The 'datastore name' datastore is notattached to a host.

Explanation: The specified datastore is not attached toa host. The current operation cannot continue.


User response: Exclude the datastore from the currentoperation or attach it to a host.

FMM0313E Environment variable env_var is notcorrect!

Explanation: This error can occur when theenvironment variable is set but contains a non–existentdirectory path.

System action:



User response: Check the value of the environmentvariable and try again.

FMM0314E File not found or not accessible:'filename'.

Explanation: The file <filename> was not found or isnot accessible to IBM Tivoli Storage FlashCopyManager.

System action:

User response: Check path, name and the permissionsof the file and try again.

FMM0315E The effective user ID of the processcould not be set to the user 'userid'.

Explanation: One of the following cases can cause thiserror: v The access rights for splitint are not set to 4750.Because the s–bit is not set, IBM Tivoli StorageFlashCopy Manager cannot switch between the users'db2<sid>' and 'root' during the execution of theprogram. v The file system that splitint is installed inwas mounted with the NOSUID option.

System action:

User response: v Check the splitint file in the directory/usr/tivoli/tsm/acssap/db2/x.y.z, and set the accessrights for splitint with chmod 4750 splitint. After theinstallation, the command ls –l splitint.... outputs a linesuch as: -rwsr–x––– 1 root dba 1918611 Apr 11 17:09splitint (This is what setup.sh would do if you hadused it.) v If the file system that splitint is installed inwas mounted with the NOSUID option, mount the filesystem with SUID allowed.

FMM0318W Warningcolon; File 'file name' still existson the backup system.

Explanation: IBM Tivoli Storage FlashCopy Managerchecks at the start of the function flashcopy if any ofthe files passed in the file list still exist on the backupsystem. If so, this warning is issued. Normally, none ofthe files should exist because the withdraw function,which should run before the FlashCopy, unmounts thefiles systems, varies them offline, exports the volumegroups, and removes the devices.

System action:

User response: Always run the function withdrawbefore starting the FlashCopy again.

FMM0320W The free space in the file systemcontaining the directory path is onlyamountMB.

Explanation: The existing free space of the filesystems containing the following directories is checked:v The database home directory and v The directoryspecified by the parameter LOG_TRACE_DIR in the

.fcs file and v The directory containing the idssave filespecified by the parameter IDS_CONTROL_FILE in the.fcs file. IBM Tivoli Storage FlashCopy Manager warnsyou if the free space of these file systems falls below 50MB. If it is under 5 MB an error is issued and theprogram fails, throwing an exception.

System action:

User response: Ensure that the free space on these filesystems is large enough.

FMM0321E IBM Tivoli Storage FlashCopy Managerrequires a free space of at least 5 MB inthe file system containing the directorypath.

Explanation: If the free space of the checked filesystems (see the explanation for IDS1310W) is under 5MB this error message is issued and the program failsthrowing an exception.


User response: Ensure that the free space on thedatabase file system is large enough.

FMM0322E The environment variable env var couldnot be set!

Explanation:

System action:

User response:

FMM0323E File 'file' was not found on the targetdisks.

Explanation:

System action:

User response:

FMM0324W Environment variable env var has value'value'.

Explanation:

System action:

User response:

FMM0325E Environment variable env var could notbe unset! Unset this variable and restart.

Explanation:

System action:

User response:



FMM0326I Environment variable env var issuccessfully unset.

Explanation:

System action:

User response:

FMM0327E Operating system error error_no: messagetext

Explanation: IBM Tivoli Storage FlashCopy Managerencountered an unexpected–message error during theexecution of a system function. The correspondingoperating system error and message text are displayed.The message appears, for example, as a result of v Anincorrect user ID on the parameterLOGON_HOST_PROD in the .fcs file v An incorrectpassword given for the user ID on the parameterLOGON_HOST_PROD in the .fcs file v An incorrectTCP/IP name on the parameter LOGON_HOST_PRODin the .fcs file (for example: connection timeout) v Afailure allocating memory using the function malloc,and the operating system cannot satisfy the request

System action:

User response: Check the specified error message.

FMM329E The LUN 'LUN name' is needed for thisoperation but cannot be accessed.

Explanation: The specified LUN is required for thecurrent operation but cannot be reached.


User response: Verify that the LUN is attached to theESX host and that the connection is working correctly.

FMM330E The datastore with the name'datastorename' was not found. It is notpart of the backup.

Explanation: The specified datastore could not befound but it is part of the input file. It will not beincluded in the backup and not be restorable.


User response: Correct the infile so that it containsvalid datastore names if this datastore is to be includedin the backup.

FMM0331I The file 'filename' is locked, waiting onesecond and retry!

Explanation: IBM Tivoli Storage FlashCopy Managersaves control information for the FlashCopy process inan internal repository that consists of several files.Some of these files may need to be written concurrentlyby several processes. To ensure consistency, IBM Tivoli

Storage FlashCopy Manager uses a lock mechanism.

System action:


FMM0332I Suspend the database activity.

Explanation:

System action:

User response:

FMM0340I Complementary LVM/ASM mirror itemsthat are not needed for the snapshot:backup_items were found.

Explanation: Backup items are storage elements suchas LUN identifiers on storage area network (SAN) ornetwork share paths on network-attached storage(NAS). Backup items are identified by Tivoli StorageFlashCopy Manager OS agent "acsgen" and are basedon the backup procedure of the application thatrequests the backup or restore operation. A snapshotitem is the smallest entity identifiable in a snapshot.Backup items either all or a subset are assigned to thecorresponding snapshot items. A subset is assigned inan AIX LVM mirroring or Oracle ASM environment.


User response: Processing continues..

FMM0341W The status information for the fsnamefile system cannot be read. Thefollowing error message was generatedby the operating system: txtmsg.

Explanation: The system call "stat" was not successfulbecause of a specific error message.


User response: Evaluate the operating system-specificwarning message to resolve the problem.

FMM0347E The update of the IDS repository failed.

Explanation: IBM Tivoli Storage FlashCopy Managerfailed to update the backup or restore status indicator(BSI/RSI) during the monitoring of the backgroundcopy process.

System action:

User response: Check the traces for details about thisfailure. One possible cause is a full file system.

FMM348E The following auxiliary vdisk: 'aux vdisk'is mapped to host 'host name'. It shouldbe mapped to takeover host 'takeoverhost' only.

Explanation: Auxiliary vdisks should be mapped only



to takeover host and not to any other hosts.


User response: Remove all host maps for the auxiliaryvdisks except the host map to the takeover host.

FMM0349E The target set 'targetSetID' does notmatch the source volumes.

Explanation: IBM Tivoli Storage FlashCopy Managerchecks whether the target set for the FlashCopy backupcontains a target volume for each source volume,located in the same hardware unit and with the samesize.

System action:

User response: Check the volume list of this target setand ensure that the volumes are in the same hardwareunit and have the same size as the source.

FMM0350E A background copy process of type'CopyType' is still running on target set'targetSetID'.

Explanation: IBM Tivoli Storage FlashCopy Managerfails if a background copy is still running for the samelogical FlashCopy group (see the documentation).However, any target set (state AVAILABLE) that doesnot yet belong to a logical FlashCopy group (stateAVAILABLE) can be selected.

System action:

User response: Check the backup status of theFlashCopy backups that may be running.

FMM0351I The target set with ID 'targetSetID' isselected for this run.

Explanation: IBM Tivoli Storage FlashCopy Manageruse two procedures for the selection of a target set.

System action:


FMM0352E No target set found to accept a backupof type 'copy_type'.

Explanation: If all the target sets are being used withthe same type of logical FlashCopy group (either INCRor COPY), you will not find a target set to make aFlashCopy with a different copy type.

System action:

User response:

FMM0353E Background copy process on the oldesttarget set 'target set' still running.

Explanation:

System action:

User response:

FMM0354E The copy type argument 'copy_type' isnot valid.

Explanation: The argument (FLASHCOPY_TYPE) ofthe command line option –C <FLASHCOPY_TYPE>can have the following values: COPY, NOCOPY andINCR. Any other value is not valid. Furthermore, INCRis only valid for an SVC configuration with version4.2.1 of the SVC master console.

System action:

User response: Specify one valid value.

FMM0355E Unable to connect to the copy servicesserver 'csname'.

Explanation: For a FlashCopy backup to be taken,IBM Tivoli Storage FlashCopy Manager softwarerequires to connect to the storage system using theparameter COPYSERVICES_PRIMARY_SERVERNAMEfor a local backup andCOPYSERVICES_REMOTE_SERVERNAME for aremote backup.


User response: Ensure to have LAN connectionbetween the host running the IBM Tivoli StorageFlashCopy Manager software and the copy servicesstorage server.

FMM0356E You cannot run a Snapshot restore fromtarget set 'targetSetID from' if the sourcesare involved in a relationship of type'copytype' with the target set 'targetSetID'.

Explanation: IBM Tivoli Storage FlashCopy Managerexploits the feature ?Multiple Relationship FlashCopy?of the storage system. This means that for IBM TivoliStorage FlashCopy Manager the source set of volumescan participate in multiple snapshot relationships withseveral target sets of volumes. However, there are somelimitations: v A source can have up to 12 targets v Atarget can only have one source v A target cannot be asource at the same time

System action:

User response: To start a snapshot restore (in reverse,from the target to the source volumes) you have towithdraw the relationship with the specified target set.



FMM0357I FlashCopy type is 'copy_type'.

Explanation: IBM Tivoli Storage FlashCopy Managerhas detected a discrepancy in the FlashCopyspecification.

System action:


FMM0358E An invalid value 'copy_type' has beenspecified for the FlashCopy type in theprofile '.fcs file'.

Explanation: The parameter FLASHCOPY_TYPE ofthe IBM Tivoli Storage FlashCopy Manager profile (.fcsfile) can have the following values: COPY, NOCOPYand INCR. Any other value is not valid. INCR is onlyvalid for an SVC configuration starting with version4.2.1 of the SVC master console.

System action:

User response: Specify one valid value.

FMM0361E The target set must be specified over theoption –n, if the parameterEXTERNAL_LVM_PLUGIN is set.

Explanation:

System action:

User response:

FMM364E Parameter 'parameter ' is mandatory.

Explanation: The specified parameter is missing.


User response: Specify the named parameter.

FMM365E The data center with the name 'dcname'was not found.

Explanation: The specified data center could not befound in the vCenter server.


User response: Specify a valid datacenter in the infiledefining the domains.

FMM366E The following line in the domain inputfile could not be parsed: 'inputline'.

Explanation: The input file defining the domainscontains unexpected keywords.


User response: Verify the format of the input filedefining the domains.

FMM367I The scope is being limited to thefollowing data center(s): 'dcnames'.

Explanation: The input file defining the domains isbeing used. It limited the snapshot process to the scopeof these data centers.



FMM368I Stopping the consistency group 'cgname'and all its older dependents.

Explanation: Usually IBM Tivoli Storage FlashCopyManager re-uses the oldest set of target volumes for thebackup. However if for some reason it is not the case,IBM Tivoli Storage FlashCopy Manager will stop all theolder FlashCopy mappings than the one been used toavoid that the space-efficient volumes grow up to itsdefined virtual size.



FMM0378E The value of the parameter'parameter_name' in the device section ofthe profile is invalid.

Explanation: This message is displayed when aninvalid value is found for one of the parameters of thedevice section of the profile.

System action:

User response: Change the value according to thevalues explained in the section Parameters of the IBMTivoli Storage FlashCopy Manager.

FMM0384W The parameterIGNORE_LVM_MIRROR_CHECK_ ERROR is set toYES. All errors on AIX LVM mirroringchecking will be ignored.

Explanation:

System action:

User response:

FMM0389E Errors occurred during the deletion ofone (or more) backups.

Explanation: One (or more) backups that werespecified to be deleted could not be deleted.


User response: Review the preceding error messagesfor information about how to resolve this issue.



FMM390E The virtual machines with the specifiedinstance UUIDs have not been found inthe backup. Update the input file withvalid instance UUIDs. Listing missingUUIDs: instance uuids

Explanation: Virtual machines with the instanceUUIDs specified in the input file were not found in thebackup.


User response: Replace the instance UUIDs in theinput file with valid values.

FMM391E The 'datastore name' datastore could notbe attached to the 'hostname' host. Pleaselook up the message user response inthe users guide for a step-by-step guidehow to solve this problem.

Explanation: The specified datastore could not beattached to the specified host. Please look up themessage user response in the users guide for astep-by-step guide how to solve this problem.


User response: Open the "Add datastore" wizard inthe vSphere Clients "Datastores" view. Select the ESXhost which was specified in the raised error message.Select "Disk/LUN" on the next page. On the "SelectDisk/LUN" page select a disk whose VMFS Labelcolumn contains the datastore name as specified in theraised error message. On the next page select "Formatthe disk". This will erase the backup contained on thistarget disk! Specify an arbitrary datastore name on the"Properties" page. It will be overwritten by the nextFCM backup. Finish the wizard. Repeat this for alldisks whose VMFS Label column contains the datastorename as specified in the raised error message. A newFCM backup can be performed afterwards.

FMM392E The 'datastore name' datastore could notbe attached.

Explanation: The specified datastore could not beattached.



FMM393E The target instance UUID 'target instanceuuid' specified in the input file cannotbe found. Add a valid target instanceUUID to the input file.

Explanation: The target instance UUID specified in theinput file was not found.


User response: Specify a valid target instance UUID.

FMM394E Redirected restores are not allowed fordistributed virtual machines. The virtualmachine 'VM name' spans multipledatastores and is distributed. Do notspecify a target VM name or a targetdatastore for the restore operation.

Explanation: Redirected restores are not allowed fordistributed virtual machines. The specified virtualmachine spans multiple datastores and is thusdistributed. Please do not specify a target VM name ora target datastore for the restore operation.


User response: Do not specify a target VM name ortarget datastore for the restore operation.

FMM0395E This license does not allow to use LVMmirrors.

Explanation: The use of DB2 ACS or IBM TivoliStorage FlashCopy Manager in an LVM mirrorenvironment requires the extended license of IBMTivoli Storage FlashCopy Manager. Starting with V5.5,the DB2 version of IBM Tivoli Storage FlashCopyManager (DP for Snapshot Devices) is a licensed,functionally enhanced version of the DB2 AdvancedCopy Services (DB2 ACS) product initially providedwith DB2 Enterprise V9.5. Conversely, DB2 AdvancedCopy Services can be regarded as a functionallyrestricted version of IBM Tivoli Storage FlashCopyManager.

System action:

User response: Contact IBM Tivoli support to acquirethe required license.

FMM0396E DB2 for Advanced Copy Services doesnot support file systems that cannotenable freeze or thaw operations.

Explanation: During a snapshot backup, DB2(R) forAdvanced Copy Services detected that at least one filesystem does not support freeze and thaw operations. Ifa file system cannot be frozen during the snapshot orFlashCopy(R) operation, then the consistency of the filesystem must be verified on the offload system bymounting the volumes that contain the snapshot orFlashCopy. This feature is not supported by DB2 forAdvanced Copy Services. It is only available with IBMTivoli Storage FlashCopy Manager.

System action: The current snapshot backup isdeleted, and processing ends.

User response: Install and license IBM Tivoli StorageFlashCopy Manager, or change all file systems to a typethat supports freeze and thaw operations. Restart thesnapshot backup.



FMM0397E You cannot freeze filesystems of typeJFS.

Explanation: This message may indicate, for example,that profile parameter LVM_FREEZE_THAW is set toYES but at least one of the file systems involved is aJFS file system. The freeze/thaw feature is onlyavailable for JFS2 file systems. It is used to suspend allI/O on the file systems while taking a snapshot ofthem. JFS file systems do not support the freeze/thawfeature. Therefore, the parameter LVM_FREEZE_THAWis not allowed to be YES if any JFS file systems areused.

System action:

User response: There are two options to resolve thisproblem: 1. If you need to use JFS file systems, youmust explicitly set the profile parameterLVM_FREEZE_THAW to NO in the CLIENT section ofthe profile. 2. Move the data from the JFS file systemsto JFS2 file systems. The profile parameterLVM_FREEZE_THAW can then be set to YES.

FMM0398E Consistency group cgname is not valid(state: status) to perform a FlashCopyrestore.

Explanation: IBM Tivoli Storage FlashCopy Managerfunction restore requires the FlashCopy consistencygroup to be in an Idle_Or_Copied or Copying state inorder to be valid for restore.


User response: Try the restore operation again using adifferent backup version.

FMM0399W Timestamp –>timestamp<– cannot beconverted.

Explanation: The status of the background copy iswritten by the background monitoring process daemonto a file named fc_exchange.'bseq_number' in thedirectory that contains the IDSAVE specified by theparameter IDS_CONTROL_FILE. The filefc_exchange.'bseq_number' has, for each volume pair,the entry 'volume_pair: target source size stateYYYY–MM–DD–HH.MM.SS YYYY–MM–DDHH.MM.SS rate', where: v target is the serial number of thetarget volume v source is the serial number of thesource volume v state can be 'active' if the backgroundcopy is running or ' none' if the background copy isfinished v YYYY–MM–DD–HH.MM.SS representsapproximate times for the start and end of thebackground process (in seconds since 00:00:00 GMT,January 1, 1970, which is the time standard theoperating system uses) v rate is the transfer rate withinthe storage system To calculate the transfer rate someconversion is needed. When doing this conversion, anerror occurred. The rate value is invalid.

System action:

User response: Check the date and time setting of themachine.

FMM0400I The process is waiting for BRBACKUP.

Explanation: The process is waiting for BRBACKUP toset a table space in the begin/end backup mode.

System action:


FMM401I The 'original VM name' virtual machinehas been registered with the new name,'new name'.

Explanation: The specified virtual machine in thebackup has been made available with the specified newname.


User response: No action is required.

FMM402I The 'datastore name' datastore with thenew datastore name 'new datastore name'was successfully attached to the 'ESXhost name' ESX host.

Explanation: A datastore from the backup has beenmade available on the specified ESX host.



FMM403I All the virtual disks (exclusive of RDMdisks) on the virtual machine 'source vmname' are attached to the target virtualmachine 'target vm name'.

Explanation: All virtual disks (exclusive of RDMdisks) of the specified virtual machine have beenattached to the specified target virtual machine.



FMM404I The virtual disks on the virtual machine'source virtual machine name' with the diskkeys 'diskkeys' are attached to the targetvirtual machine 'target virtual machinename'.

Explanation: The specified virtual disks of thespecified virtual machine have been attached to thespecified target virtual machine.





FMM0405I The process waited num_sec seconds forBRBACKUP in util_file_onlinecommunication.

Explanation: This message indicates the total amountof time the process waited for BRBACKUP to set atable space in "begin backup" or "end backup" mode.The wait time given is the sum of the wait times for alltable spaces participating in the backup.

System action:


FMM406W The 'vm name' virtual machine is adistributed VM because the 'virtual diskname' disk is located in the 'disk directory'datastore directory, which is not the'working directory' VM working directory.

Explanation: One of the disks within the virtualmachine is in a directory that is not the workingdirectory.


User response: Be aware that the limitations of virtualmachines spanning multiple datastores apply.

FMM407E The maximum number of SCSI targetsfor a virtual machine is exceeded.

Explanation: All SCSI targets are in use.


User response: Remove some SCSI targets.

FMM408E The disks with the 'diskkeys' disk keyscannot be found in the backup and arenot attached.

Explanation: The specified disk keys cannot be foundin the backup and are not attached.


User response: Specify valid diskkeys.

FMM409E There is not enough free space availablein the 'datastore name' target datastore tocomplete this operation. space needed isrequired to complete this operation.space available is free.

Explanation: Not enough free space is available in thespecified target datastore.


User response: Choose another target datastore ormake more space available in the specified datastore.

FMM0410E Cannot open or delete switch file 'filename'. Check permissions.

Explanation: If Data Protection for SAP is not installedcorrectly (as the root user on UNIX or Linux oradministrator group on Windows) then Data Protectionfor SAP is not able to open the necessarycommunication file to the SAP system.

System action:

User response: Check the file permission.

FMM0411E Maximum time waiting for BRBACKUPexpired.

Explanation: The SAP database utilities did notrespond within the expected time.

System action:

User response: Contact your SAP administrator.

FMM0412E BRBACKUP wasn't able to switchrequested tablespace in BEGIN/ENDBACKUP mode.

Explanation: Data Protection for SAP could notcontinue the backup, because BRBACKUP was not ableto switch the requested table space in BEGIN or ENDbackup mode. This is necessary for locking the tablespace.

System action:


FMM0413E Error while requesting tablespaceswitch.

Explanation: BRBACKUP could not switch table spacein BEGIN or END backup mode.

System action: Contact your SAP administrator.

User response:

FMM0414E Error while requesting tablespaceswitch.

Explanation: BRBACKUP reported an error whiletrying to switch a table space in BEGIN or ENDbackup mode.

System action:


FMM415E The 'datastore name' datastore cannot befound. In the input file the nameddatastore is specified as a targetdatastore for the restore operation.

Explanation: The specified datastore has not beenfound but is needed as a target datastore for the restore



operation. A backup with the specified ID cannot befound.


User response: Specify a valid target datastore in theinput file.

FMM416E The 'vm name' virtual machine could notbe restored to the 'target datastore'datastore using 'target vm name' VMname. A VM with the same namealready exists in the datastore.

Explanation: The specified virtual machine could notbe restored because another virtual machine with thesame name already exists in the target datastore.


User response: Specify another target datastore ordelete the existing virtual machine in the specifieddatastore.

FMM417I The 'source vm name' virtual machine issuccessfully restored to the 'datastorenames' datastore(s) and registered withthe name 'registered vm name'.

Explanation: The specified virtual machine has beensuccessfully restored to the specified datastores.


User response: No action is required

FMM418I The attached virtual disk with the 'diskkey' key is successfully detached fromthe 'virtual machine name' virtualmachine.

Explanation: The attached virtual disk with thespecified key has been successfully detached from thevirtual machine with the specified name.



FMM419E The configured vCenter server supportsthe 'found API version' API version. Therequested operation is available sincethe 'needed API version' API version andis not supported by the configuredvCenter server.

Explanation: The requested operation is not availablein the API version supported by the vCenter server.


User response: The requested operation cannot beused with this vCenter server. If this operation isneeded you must upgrade the API.

FMM420E The 'ESX hostname' ESX host supportsthe 'found API version' API version. Therequested operation is available sincethe 'needed API version' API version andis not supported by the ESX host.

Explanation: The requested operation is not availablein the API version supported by the specified ESX host.


User response: The requested operation cannot beused with this ESX host If this operation is needed youmust upgrade the API.

FMM421E The restore operation cannot becompleted because the 'vm name' virtualmachine with 'vm instance uuid' instanceUUID is not powered off.

Explanation: The restore operation cannot becompleted because the specified virtual machine is notpowered off.


User response: Power off the specified virtualmachine.

FMM422E A virtual disk was not found for the'diskkey' disk key as specified in theinput file.

Explanation: No virtual disk was found for thespecified disk key.


User response: You must specify a valid diskkey.

FMM423I The 'diskname' virtual disk on the 'virtualmachine name' virtual machine wassuccessfully restored.

Explanation: The specified virtual disk wassuccessfully restored.



FMM0424I Start Snapshot backup destination backuptype sid host productive host backup host listsid list

Explanation:

System action:

User response:



FMM0425I flashcopy type Start Snapshot backgroundcopy

Explanation:

System action:

User response:

FMM426I The following virtual machine questionhas been answered to with 'answer':question

Explanation: The specified question has beenanswered with the specified value.


User response: Nothing

FMM0427I Stop Snapshot background copy

Explanation:

System action:

User response:

FMM0428I Start Withdraw

Explanation:

System action:

User response:

FMM0429I Stop Withdraw

Explanation:

System action:

User response:

FMM0430I Enabling the volumes and filesystemsfinished

Explanation:

System action:

User response:

FMM431E One or more vmware snapshotoperations failed.

Explanation: The snapshot operation for one or morevirtual machines failed.


User response: Verify the log for preceding errormessages containing the specific name of the virtualmachines involved and the description of the error.

FMM432E The vmware snapshot operation for thevirtual machine with instance uuid'instance uuid' failed: 'error'.

Explanation: The snapshot operation failed on thespecified virtual machine.


User response: Check the error message.

FMM433W The vmware power on operation for thevirtual machine 'vmref' failed: 'error'.

Explanation: The operation power on after the poweroff for the purpose of taking a snapshot failed on thespecified virtual machine.


User response: Check the vmware specific errormessage.

FMM434W The remove operation of the vmwaresnapshot 'snapref' failed: 'error'.

Explanation: The snapshot remove operation failed.


User response: Check the vmware specific errormessage.

FMM435E The virtual machine 'VM name' can notbe restored because the backup is in useby an offloaded TSM backup. Therestore of a distributed VM is notallowed if an offload TSM backup is inprogress. Wait until the offload backupis complete.

Explanation: The restore of a distributed VM is notallowed if an offload TSM backup is in progress. Waituntil the offload backup is complete.


User response: Wait until the offload backup iscomplete.

FMM436E The virtual machine 'VM name' couldnot be restored because the backup isalready in use by an other VM. Therestore of a distributed VM is notallowed if the mounted datastore isalready in use by a VM. Detach thisbackup. Try the operation again.

Explanation: The restore of a distributed VM is notallowed if the mounted datastore is already in use by aVM. Detach this backup. Try the operation again.




User response: Detach this backup. Try the operationagain.

FMM437E The virtual disks cannot be added orreplaced on the 'vm name' virtualmachine with 'vm instance uuid' instanceUUID identifier. The specified virtualmachine is suspended.

Explanation: The resource configuration of a virtualmachine cannot be modified while it is suspended.


User response: Resume the specified virtual machinethen try again.

FMM438E The virtual disks cannot be removedfrom the 'vm name' virtual machine with'vm instance uuid' instance UUIDidentifier. The specified virtual machineis suspended.

Explanation: The resource configuration of a virtualmachine cannot be modified while it is suspended.


User response: Resume the specified virtual machinethen try again.

FMM439W The vmware snapshot operation for thevirtual machine with instance uuid'instance uuid' failed: 'error'. The backupof this virtual machine will be crashconsistent only.

Explanation: The vmware snapshot operation failedon the specified virtual machine.



FMM440I The following virtual machine questionhas been answered to with 'answer':question

Explanation: The specified question has beenanswered with the specified value.


User response: Nothing

FMM441W The VMware snapshot operation for thevirtual machine with 'instance uuid'instance UUID cannot be completed:'error'. Trying the VMware snapshotagain without quiescing the file system.

Explanation: The VMware snapshot operation was notsuccessful on the specified virtual machine.



FMM451E The disk with the 'diskkeys' disk key is araw device-mapping disk which mustnot be attached.

Explanation: The specified disk is a rawdevice-mapping disk which must not be attached toanother virtual machine.

System action: Processing ends with error.

User response: Specify only diskkeys that representstandard virtual disks.

FMM0452E This version of Data Protection forSAP(R) has expired.

Explanation: This is a test version that has expired.

System action:

User response: Order a release version of the productor contact your IBM/Tivoli Sales Representative.

FMM0453W This version of Data Protection forSAP(R) will expire in number days.

Explanation: This is a test version with a time limit. Itwill expire in number days.

System action:

User response: Order a release version of the productor contact your IBM/Tivoli Sales Representative beforethe version expires.

FMM0454I *** This copy is NOT FOR RESALE. ***

Explanation: This version is not for resale.

System action:


FMM0455E License file file name does not exist.

Explanation: The license file agent.lic was not foundwhere expected.

System action:

User response: Make sure that the agent.lic file residesin the same directory as the init<SID>.utl file.

FMM0456E Unable to access license file file name.

Explanation: The license file could not be accessed.

System action:

User response: Make sure the access permissionsallow read/write access.



FMM0457E License file file name contains invaliddata/checksum.

Explanation: The license file is invalid.

System action:

User response: Make sure you have the right agent.licfile for the right platform installed. agent.lic files areplatform dependent.

FMM0458I Fake–Mode is activated.

Explanation: This message signals that the currentoperation is a simulated operation. Simulations can beperformed using the Administration Assistant.

System action:


FMM459E One or more suspend operations failed.

Explanation: One or more suspend operations failed.


User response: Check preceding error messages.

FMM0460E No mux file is found with the namename

Explanation: A mux file is a data structure holdinginternal metadata needed for restore puposes. Eachbackup image gets a mux file assigned.

System action:

User response: Check the logs for further information.If the problem cannot be resolved contact your IBMsupport personnel.

FMM0461I Created tracefile 'tracefile' for process ID'id'.

Explanation: The named trace file has been created.

System action:


FMM0503E Unexpected error occurred.

Explanation: An unexpected error occurred.


User response: Gather information from the trace fileand log file and contact your IBM servicerepresentative.

FMM504I A software snapshot including memoryis created of the 'vm name' virtualmachine with the 'vm instance uuid'instance UUID.

Explanation: A software snapshot including memoryis created of the specified virtual machine.



FMM505I A software snapshot excluding memoryis created of the 'vm name' virtualmachine with the 'vm instance uuid'instance UUID.

Explanation: A software snapshot excluding memoryis created of the specified virtual machine.



FMM506I The 'vm name' virtual machine with the'vm instance uuid' instance UUID issuspended.

Explanation: The specified VM is suspended.



FMM507I The software snapshot of the 'vm name'virtual machine with the 'vm instanceuuid' instance UUID is removed.

Explanation: The software snapshot of the specifiedvirtual machine is removed.



FMM508E The 'vm name' virtual machine might bethe virtual machine containing IBMTivoli Storage FlashCopy Manager andcannot be part of the backup. Rename itor specify the virtual machinecontaining IBM Tivoli StorageFlashCopy Manager in the 'profileparameter name' profile parameter in theprofile.

Explanation: The virtual machine that contains IBMTivoli Storage FlashCopy Manager cannot be part of abackup. The specified virtual machine might containIBM Tivoli Storage FlashCopy Manager.


User response: Rename the specified virtual machineor add the name of the IBM Tivoli Storage FlashCopyManager virtual machine to the profile.



FMM0509E More than one instance of thisexecutable are running now.

Explanation: You have to wait until previous backupis done before you can run this backup.


User response: Wait until previous backup is doneand try again.

FMM0510E acsgen has to be started from the CLIwith the required '-D' parameter.

Explanation: acsgen requires the '-D' parameter tostart.

System action: Processing fails.

User response: Retry the operation using the '-D'parameter.

FMM0511I ====>Performing IBM Tivoli StorageFlashCopy Manager v1 command.

Explanation: This message is displayed starting thespeicified function (BACKUP, WITHDRAW orRESTORE) of DP for Snapshot Devices.



FMM512E The virtual machine containing thevCenter server cannot be part of thebackup. The 'vm name' virtual machineis part of the backup but it is specifiedas the vCenter server virtual machine inthe 'profile parameter name' parameter inthe profile.

Explanation: The virtual machine specified in theprofile as vCenter server virtual machine has beenfound to be part of the backup.


User response: Rename the specified virtual machineor change the specified name of the vCenter servervirtual machine in the profile.

FMM513E The 'vm name' virtual machine might bethe virtual machine containing thevCenter server and cannot be part of thebackup. Rename it or specify the virtualmachine containing the vCenter serverin the 'profile parameter name' profileparameter in the profile.

Explanation: The specified virtual machine issuspected to contain the vCenter server and can thusnot be part of the backup.


User response: Rename the specified virtual machineor add the name of the vCenter server virtual machineto the profile.

FMM514E The virtual machine that contains IBMTivoli Storage FlashCopy Managercannot be part of the backup. The 'vmname' virtual machine is part of thebackup but it is specified as the virtualmachine containing IBM Tivoli StorageFlashCopy Manager in the 'profileparameter name' parameter in the profile.

Explanation: The virtual machine specified in theprofile as IBM Tivoli Storage FlashCopy Manager ispart of the backup.


User response: Rename the specified virtual machineor change the specified name of the IBM Tivoli StorageFlashCopy Manager virtual machine in the profile.

FMM0515E Filesystem consistency check failed.

Explanation: Filesystem consistency check on thefilesystems processed by Flashcopy failed. This meansthat there were some inode changes on the filesystemwhen executing DP for Snapshot Devices backup onthe production system.

System action: Please ensure that you do not makeany changes to the production system duringFlashCopy backup, that may cause changes to theinodes on the database filesystems. This will result ininconsistency in the database filesystems beingprocessed by Flashcopy. Examples of operationsresulting in inode changes are: When a file is created ordeleted. When a write() call occurs to a file openedwith O_SYNC and the write causes a new disk blockallocation. When fsync() or sync() functions are called.When a write causes an indirect or double-indirectblock to be allocated. Another way to get around thisproblem is to use raw logical volumes for yourdatabases.

User response: Please execute the backup commandagain.

FMM0516E The initialization of the ODM APIfailed with ODM error numberodmerrno: description.

Explanation: IBM Tivoli Storage FlashCopy Manageruses the ODM API library for the logical volumemanager. The specified error occurred when trying toinitialize this library.


User response: Validate the specific error description.



FMM0517E Failed to get the ID of the volume groupvgname using the AIX command:command.

Explanation: IBM Tivoli Storage FlashCopy Manageruses the displayed command to get the volume groupID. The command failed.


User response: Check the state of the AIX ODM andof the volume group. Run this command from the AIXcommand line.

FMM0518E Failed to get the ID of the logicalvolume lvname using the AIX command:command.

Explanation: IBM Tivoli Storage FlashCopy Manageruses the displayed command to get the logical volumeID. The command failed.


User response: Check the state of the AIX ODM andof the logical volume. Run this command from the AIXcommand line.

FMM0519E The volume with the serial ID serialid isnot assigned to the backup host.

Explanation: IBM Tivoli Storage FlashCopy Managerimports the data from the target set volumes into thebackup system. This requires the SAN to assign thevolumes to the backup host.


User response: Make sure the target storage volumesare assigned to the backup host.

FMM0520W Trying to find the process that haslocked the ODM ...

Explanation: IBM Tivoli Storage FlashCopy Managerchecks whether the AIX ODM is locked by otherprocesses on the host prior to making persistentchanges.



FMM0521I Waiting the maximum seconds secondsuntil the ODM lock is released byanother application.

Explanation: IBM Tivoli Storage FlashCopy Managerwill retry to lock the ODM after the specified time.



FMM0522E The storage system ID could not befound for the volume volume.

Explanation: IBM Tivoli Storage FlashCopy Managerwas not able to find the storage ID for the specifiedvolume.


User response: Use the GUI or the command line toverify that the volume exists.

FMM0523E The file systems needed for the mountoperation are missing.

Explanation: IBM Tivoli Storage FlashCopy Managerwas not able to find the file systems in the localrepository.


User response: Use the inquire function to verify thestate of the backup to be mounted.

FMM0524E The pathname directory path or fullyqualified file name was not found inany of the current active file systems.

Explanation: The backup process cannot find thespecific path from the list of files or directories that isspecified when you start the backup operation.

System action: Processing ends..

User response: Use the OS shell commands to checkthe status of this path. Ensure that the underlaying filesystem is mounted and try the operation again.

FMM0525E Mount point mount_point_name is notrecognized by the system.

Explanation: A file system that is participating in thebackup operation is not recognized by the system. Thisproblem can be caused by an inconsistency in thesystem, for example in the /etc/filesystems file.


User response: Use the command-line shell for youroperating system to check the status of this mountpoint, and try the operation again..

FMM0539E Either Oracle control file or redo log fileis in the same volume group (v1) withwhich Oracle datafiles are.

Explanation: Either Oracle control file or redo log fileis in the same volume group with Oracle datafiles.


User response: Make sure you don't have control filesand redo log files in the same volume group withOracle datafiles.



FMM0540E A null logical volume has been detected.

Explanation: A null logical volume was detected.


User response: Verify the target database informationis specified correctly in the Setup File.

FMM0542I Mounting disk group : dg1.

Explanation: This message indicates the mount of thenamed disk group.


User response: If this messages is immediatelyfollowed by an error message the error might relate tothe named disk group.

FMM0543I Mounting filesystem : fs1.

Explanation: Currently attempting to mount the filesystem.


User response:

FMM0544E Serial number for the device v1 is notfound.

Explanation:


User response:

FMM0545I Trying to find new devices to match thesource device. This process will takesome time.......

Explanation: Currently trying to find a target deviceto match with the source device.


User response:

FMM0546I Removing device : parm1

Explanation: DP for Snapshot Devices will remove thelogical devices from the Device Configuration database(ODM) on the backup system after the backup endedand prior to the withdraw of the relationships of thevolumes.


User response:

FMM0547I Configuring the target volume wouldcause duplicate physical volume ID :pvid1.

Explanation: A different set of target volumes thatwere previously associated with the same sourcevolumes was detected.


User response: Perform one of the following: Deletethe disk on the backup system only: 1. find the diskusing the AIX lspv command 2. run smitty and choosethe following from the menu: devices- fixed disk-remove a disk- select the disk to be removed 3. pressreturn Clear the pvid of each physical volume hdisk byissuing the aix chdev command with the followingarguments:chdev -1 (hdisk#) -a pv=clear

FMM0548E Removing device parm1 failed.

Explanation: DP for Snapshot Devices will remove thelogical devices from the Device Configuration database(ODM) on the backup system after the backup endedand prior to the withdraw of the relationships of thevolumes. The rmdev command failed.


User response: Check the specific error message.Consult the AIX system documentation. Check if thedevice is member of one active volume group. Checkfor proceeding errors.

FMM0549W Removing the mount point directorymntpt1 failed with rc: rc1.

Explanation: An error occurred while trying toremove a mount point. Processing continues.


User response:

FMM0550E The physical volume ID pvid1 isduplicate on the production machine.

Explanation: The output of the command lspv showsthat two logical devices (hdisk/vpath) have the samephysical volume id.


User response: Perform one of the following: a) If thehdisks with the same pvid belong to the samemultipath, convert the hdisk device volume group to aSubsystem Device Driver vpath device volume group.b) If the problem is the result of a corrupt ODM,consult the AIX Troubleshooting documentation c) Ifthe physical volume involved neither belongs to avolume group nor it contains file systems to beimported in the future, then you can clear the pvid byissuing the aix chdev command with the followingarguments:chdev -l hdisk# -a pv=clear



FMM0551W The umount command failed with rc rc1for mount point mntpt1.

Explanation: An error occurred while trying toremove a mount point. Processing continues.


User response:

FMM552E A backup with the 'backup_id' ID cannotbe found.

Explanation: No backup with this ID exists.


User response: Specify a valid backup ID. Validbackup IDs can be obtained by the inquire command.

FMM0553E Failed to suspend I/O on a logicalvolume device with errno errno forlogical volume: lv.

Explanation: An error occurred while trying tosuspend I/O on a JFS log logical volume device. I/Oon this logical volume will not be suspended whileestablishing FlashCopy backup. This may result in aninconsistent database snapshot during backup.However, processing will continue.


User response: Please contact AIX support to find outwhy the suspend I/O on a logical volume devicefailed.

FMM0554E Failed to resume I/O on a logicalvolume device with errno errno forlogical volume: lv.

Explanation: An error occurred while trying to resumeI/O on a JFS log logical volume device.

System action: Processing stops..

User response: Try running the DP for SnapshotDevices "resume" command. If the failure persists,please contact AIX support to find out why the resumeI/O on a logical volume device failed.

FMM555E Multiple backup IDs were specified inthe input file. You can specify only onebackup ID in the input file.

Explanation: More than one backup ID was specifiedin the input file.


User response: Specify just one backup ID in theinput file.

FMM0556I Flashcopy type is set to NOCOPY.Removing disk meta data for all targetdisks... This backup is NOT valid for aFlashCopy restore. Please restore fromTSM Server.

Explanation: Target PVIDs are cleared. This processremoves disk metadata for all target disks. These targetvolumes can now be used as targets for source volumesfrom multiple databases. However, this backup is notvalid for a FlashCopy restore. You can only restorefrom TSM Server.



FMM0557W Removing the file system on the mountpoint mntpt1 failed with rc: rc1.

Explanation: An error occurred while trying toremove a file system during the FlashCopy restore.Processing continues. The restore will repair thisproblem.



FMM0558I Flashcopy type is set to COPY or INCR.Leaving disk meta data intact for alltarget disks... This backup is valid for aFlashCopy restore.

Explanation: The target PVIDs are not cleared.Thisprocess leaves disk metadata intact for all target disks.This backup can be used for a FlashCopy restore.



FMM0559E Command lslv failed for the logicalvolume v1.

Explanation: The LVM command lslv failed with thespecified logical volume.


User response: Try to run the same command fromthe command line and verify that it works. Check thatthe file system /tmp contains enough space.

FMM0560E Unsupported file system has beendetected.

Explanation: The file system that database allocated isan unsupported type.


User response: Make sure that the mount point existsand the file system is supported.



FMM0561E The file or directory objname must not belocated on the volume group v1.

Explanation: This volume group is not supported byIBM Tivoli Storage FlashCopy Manager. The file ordirectory displayed is located in this volume group.


User response: Make sure that volume group is notrootvg.

FMM562E No backup ID was found in the inputfile. Specify a valid backup ID in theinput file.

Explanation: No backup ID was specified in the inputfile.


User response: Specify a valid backup ID in the inputfile.

FMM0563E An physical disk for the volume groupv1 was not found.

Explanation: A physical disk from the specifieddatabase volume group was not found in the DeviceConfiguration database.


User response: Check the specific error message.Consult the AIX system documentation. Check if thisdevice is member of one active volume group. Checkfor proceeding errors.

FMM0564I Exporting volume group fnm1 failed.

Explanation: The specified volume group could not beexported after the vary off.


User response: Check the error message displayed bythe operating system. Check that the volume groupwas vary off before the exporting.

FMM0565I Importing volume groups now...

Explanation: Processing an importing volume groupcommand.


User response:

FMM0566I Newly imported volume group: vg1

Explanation: DP for Snapshot Devices has successfullyimported this new volume group on the backup systemafter the FlashCopy.


User response:

FMM0567E Logical Volume cannot be found for thefile fnm1.

Explanation: An error has occurred determining thelogical volume of a file in the list of database files.


User response: Check the specific error message.Cosult the AIX system documentation.

FMM0568I Removing volume group fnm1 ....

Explanation: Attempting to remove the identifiedvolume groups.



FMM0569I Varied off and exported volume group :fnm1

Explanation: The specified volume group was variedoff and exported successfully.



FMM0570I Finding the serial numbers ...

Explanation: DP for Snapshot Devices get as input alist of database files to be backed up and from them itfigures out the logical volumes, the volume groups andthe serial number of the physical volumes where theproduction database is residing.



FMM571E The vmcli executable file 'vmclipath' doesnot exist. The installation seems to becorrupt.

Explanation: The vmcli component cannot be found.


User response: Verify that the vmcli executable fileexists and is in the correct directory. Reinstall theproduct.

FMM0572E No volume group was found.

Explanation: The AIX command lsvg failed on thebackup system and the new added volume groups afterthe FlashCopy could not be figured out.


User response: Check the operating system errorissued by lsvg. Consult the AIX documentation.



FMM0573E Volume group vg1 can not be found.

Explanation: The AIX command lsvg failed on theproduction system and the source volumes of theproduction database could not be found out.


User response: Check the operating system errorissued by lsvg. Consult the AIX documentation.

FMM0574E Quorum of the volume group vg1 mustbe off.

Explanation: In a highly-available LVM mirrorenvironment, DP for Snapshot Devices requires that thequorum of the volume group is set to off. If a mirror isinactive due to a failure, the database should continueworking properly.


User response: Set the quorum of the volume groupoff.

FMM0575E Logical volume vg1 must have at least 2copies.

Explanation: If the parameter for working with LVMmirror is active, then DP for Snapshot Devices requiresthat two copy of each logical volume are existing.


User response: Create a copy of each logical volumeon separate hardware units. Ensure that you have foreach source volume a target volume for the FlashCopyin the same hardware unit.

FMM0576E Logical volume vg1 must have theparallel or striped scheduling policy.

Explanation: DP for Snapshot Devices requires theparallel or striped scheduling policy. With the parallelscheduling policy, there is no primary or secondarymirror. All copies in a mirror set are just referred to ascopy, regardless of which one was created first.


User response: Set the scheduling policy of this logicalvolume to 'parallel'.

FMM0577E Logical volume vg1 must have mirrorwrite consistency on.

Explanation: Mirror write consistency ensures dataconsistency among mirrored copies of a logical volumeduring normal I/O processing. If a system or volumegroup is not shutdown properly, then mwc will identifywhich logical partitions may be inconsistent. DP forSnapshot Devices requires that this capability be set forthe logical volumes of the production database.


User response: Set mirror write consistency on.

FMM0578E None of the mirror copies of the logicalvolume lv resides completely on thespecified hardware unit essid.

Explanation: DP for Snapshot Devices requires that allthe partitions of one mirror set must be residing onphysical volumes of one hardware unit.


User response: You have to reconfigure the allocationon the production system.

FMM0579E Some of the partitions of vg1 are staleon the specified hardware unit identifier.

Explanation: DP for Snapshot Devices checks first allthe logical volumes for stale partitions and issues firstonly a warning if it finds some. The mirror set that isresiding in the hardware unit that was chosen for theFlashCopy on this specific run, have to be free fromstale partitions.


User response: Check the reason why you are havingstale partitions. Synchronize the logical volumes of theproduction database.

FMM0580I Could not determine the number ofpaths to target volumes. Using defaultvalue of 1.

Explanation: DP for Snapshot Devices supports SDD(Subsystem Device Driver). SDD is a pseudo devicedriver designed to support the multipath configurationenvironments in the storage system and is used toenhance data availability. DP for Snapshot Devices willdetermine the number of multiple paths queryng theDevice Configuration database (ODM).


User response: If you want to use the advantage ofSDD, check the Subsystem Device Driver User's Guidefor a correct configuration.

FMM0581E Failure in changing the mount point mp,return code rc from command chfs.

Explanation: In a high-available LVM mirrorenvironment, DP for Snapshot Devices will use therecreatevg command to create the volume groups afterthe FlashCopy on the backup system. Becauserecreatevg inserts the prefix ./fs....at the begin of themount point, DP for Snapshot Devices must remove itcalling the command chfs.... to the original names.


User response: Check the specific error message.



Consult the AIX system documentation. Check forproceeding errors.

FMM0582E The same hdisk vg1 can not beassociated with two different vpaths(serial numbers vg2 and vg3). commandchfs.

Explanation: IBM Tivoli Storage FlashCopy Managerhas encountered a corrupted configuration in yoursystem.


User response: By issuing the command 'lsvpcfg' youcan identify that error. Check the Subsystem DeviceDriver User's Guide for a correct configuration.

FMM0583E lsvg command failed.

Explanation: DP for Snapshot Devices uses thecommand lsvg to determine the physical and logicalvolume of the volume group. That command has failed.



FMM0584I Recreating the new volume groups....

Explanation: In a highly-available LVM mirrorenvironment, DP for Snapshot Devices will use therecreatevg command to create the volume groups afterthe FlashCopy on the backup system.



FMM0585E The command lvm_queryvg failed.

Explanation: DP for Snapshot Devices uses the systemroutine lvm_queryvg to read information of the VGDAof the volumes.


User response: Check the specific error message.Consult the AIX system documentation. Check forproceeding errors.

FMM0586E The number of new volume groups islimited parm1.

Explanation: DP for Snapshot Devices can support adatabase with maximum 256 volume groups.


User response: You have to reconfigure yourproduction database.

FMM0587I Varying on volume group fnm1 failed.

Explanation: Post to the importvg or recreatevg , DPfor Snapshot Devices will vary on the database volumegroup on the backup system. The command varonvghas failed.


User response: Check the specific error message.Consult the AIX system documentation. Check forproceeding errors.

FMM0588E Invalid option found in the Setup File.

Explanation: The parameter value is invalid.


User response: Correct the value and restart theprocessing.

FMM0589I Flushing the buffers to disk...

Explanation: Currently synchronizing to force thebuffers to disk.


User response:

FMM0590I Unmounting the file system mntpt1...

Explanation: Currently attempting to unmount the filesystem from the mount point.


User response:

FMM0591I Bringing up the volume groups...

Explanation: The new resources are being activatedafter the FlashCopy.

System action:


FMM0592I Too many file systems located.

Explanation: The number of file systems exceeds the4096 limit.


User response: Reconfigure the production database.

FMM0598E Although the pvid pvid is contained inthe descriptor area of the volume groupvgname, no logical devices (hdisk/vpath)has this on the production system.

Explanation: The output of the command lspv showsthat no physical volume hdisk/vpath exist with this



pvid, although the pvid was found on the descriptorarea of the volume group.


User response: You very likely have an ODMcorruption for the involved volume group. Check thisvolume group with the command lsvg -l <vgname>and lsvg -p <vgname>. Depending on the error, youhave to take different actions. Consult the AIXtroubleshooting documentation to repair the ODM.

FMM0599E Physical volume hdisk is in thedescriptor area of the volume groupvgname but does not belong to thisvolume group.

Explanation: The output of the command lsvg -p<vgname> does not show that the hdisk/vpath belongto this volume group, but its pvid is registried in thedescriptor area of the volume group.


User response: If the hdisks with the same pvidbelong to the same multipath, convert the hdisk devicevolume group to a Subsystem Device Driver vpathdevice volume group. If you have an ODM corruption,check the involved volume group with the commandlsvg -l <vgname> and lsvg -p <vgname>. Dependingon the error, you have to take different actions. Consultthe AIX troubleshooting documentation to repair theODM.

FMM0600W The major number of the volume groupvgname could not be determined.

Explanation: The command "getlvodm" used todetermine the major number of the specified volumegroup failed. The option -V of the command importvgwill not be used on a FlashCopy restore of this backup.


User response: Check for error messages of thecommand getlvodm.

FMM0601W Major number major already exists onthe production machine. The systemwill assign the next available majornumber to the volume group vgname.

Explanation: DP for ESS found that the major numberof the given volume group is being used by anotherdevice. The importvg command will be issued withoutthe option -V <major number>, then the system willgenerate the next available major number automatically.


User response: Check the major numbers on thesystem with the command "ls -al /dev".

FMM0602E Production database does not reside ona LVM mirror environment. The profileparameter 'profile_param' is not allowedin an environment without LVMmirroring.

Explanation: The LVM mirroring capability of DP forESS is on, but the database logical volumes do not havea mirror copy.


User response: Set the parameter for LVM mirroringoff or setup your system in an high-available LVMmirror environment.

FMM0603E Error reading the status information ofthe file system fsname: txtmsg.

Explanation: The system call stat failed. Check thespecific error message. In some cases the user will needadministrator rights to execute that command.


User response: Check the specific error message.Ensure that the user has enough rights.

FMM0604W The file system fsname is not of typejfs2. The freeze/thaw function will beapplied only on file systems of typejfs2.

Explanation: The freeze/thaw function will be appliedonly on file systems of type jfs2.



FMM0605E Error freezing the file system fsname:txtmsg.

Explanation: The function FREEZE on this file systemfailed.

System action: Check the specific error of theoperating system appended at the end of this message.


FMM0606E Error thawing the file system fsname:txtmsg.

Explanation: The function THAW on this file systemfailed.

System action: Check the specific error of theoperating system appended at the end of this message.




FMM0607I Freezing filesystem : fs1.

Explanation: Currently attempting to freeze the filesystem.


User response:

FMM0608I Thawing filesystem : fs1.

Explanation: Currently attempting to thaw the filesystem.


User response:

FMM0609I Performing snaprestore of the sourcevolume srcvol to the snapshot snapid(LUN lunpath).

Explanation: The function snaprestore will revert thesource volume to the specified snapshot name. Thismessage will appear for every LUN involved in therestore process. The snap restore is made based on thevolume.


User response:

FMM0610I Performing snapshot of the sourcevolume srcvol (LUN lunpath).

Explanation: A snapshot will be taken from thisvolume. This message will appear for every LUNinvolved in the snapshot process, however whenseveral LUNs belong to the same volume, only onesnapshot of this volume is taken.


User response:

FMM0611I The snapshot snapid was generated forthe source volume srcvol (LUN lunpath).

Explanation: A snapshot with the name displayed wastaken from this volume. This message will appear foreach LUN involved in the snapshot process, howeverwhen several LUNs belong to the same volume, onlyone snapshot of this volume is taken.


User response:

FMM0612E File system fsname thawed automaticallybecause the specified timeout limit wasexceeded. Specify the profile parameterTIMEOUT_FLASH, to increase thetimeout limit. The default value of thisparameter is 120 seconds.

Explanation: The THAW function on the file systemfsname failed because the file system thawedautomatically after the timeout value specified by theTIMEOUT_FLASH parameter was already exceeded.


User response: Increase the timeout value for theTIMEOUT_FLASH parameter.

FMM0613E File system fsname can not be freezedbecause the timeout limit was exceeded.Specify the profile parameterTIMEOUT_FLASH, to increase thetimeout limit. The default value of thisparameter is 120 seconds.

Explanation: The FREEZE function cannot be appliedto file system fsname because the timeout limit specifiedby the TIMEOUT_FLASH parameter was alreadyexceeded.


User response: Increase the timeout value for theTIMEOUT_FLASH parameter.

FMM614E The process failed to update theusability state of the snapshot backup.

Explanation: IBM Tivoli Storage FlashCopy Managercannot update the IBM Tivoli Storage FlashCopyManager repository.


User response:

FMM0615E Unable to open file file1.

Explanation: An error was detected when trying toopen the file. The file may not exist.


User response: Make sure the file exists.

FMM0616I Performing fctype FlashCopy of sourcevolume src1 to target volume tgt1

Explanation: A FlashCopy from the source volume tothe target volume was requested.


User response:

FMM617W The locale 'locale' for the host is notsupported by the VCenter server. Adefault locale will be used.

Explanation: The specified locale is not supported bythe VCenter server.

System action: Processing continues with the defaultlocale.

FMM0607I • FMM617W


User response: Set the locale to setting supported bythe VCenter server.

FMM618E The suspend operation for the virtualmachine with the instance UUID'instance uuid' failed: 'error'.

Explanation: The suspend operation failed on thespecified virtual machine.



FMM0619I Performing FlashCopy withdraw ofsource volume src1 from target volumetgt1

Explanation: A FlashCopy withdraw of the sourcevolume from the target volume was requested.


User response:

FMM0620E No target volume is available.Terminating......

Explanation: No target volume was found.


User response: Make sure the target volumes reside inthe same Logical Subsystem (LSS) as the sourcevolumes and that the target volumes are available tothe backup system. Also, make sure the syntax iscorrect in the .fct file.

FMM0635E A required parameter tgtv1 is missing inthe Setup File.

Explanation: A required parameter in the Setup Filehas not been specified. This may be caused by incorrectsyntax in the Setup File.


User response: Make sure all the required parametersare present in the Setup File and that no space existsbetween the parameter and the colon(:).

FMM0643I Executing system command 'parm1'

Explanation: IBM Tivoli Storage FlashCopy Manageris performing the command parm1 and waiting for theresults from the operating system.



FMM0644E Error on running command: parm1

Explanation: An error was detected while running asystem command.


User response: Gather log file information and contactyour IBM service representative.

FMM0647I User abort; Exiting Flashcopy Restore.

Explanation: The user has chosen to terminate theFlashcopy Restore operation.

System action: Restore processsing is terminated.

User response: Flashcopy Restore overwrites anyexisting data on all the source LUNs, including (but notnot limited to) all filesystems and raw volumes onthem. Make sure all necessary data from the sourceLUNs is backed up, and restart the procedure.

FMM0648I User input was yes; ContinuingFlashcopy Restore.

Explanation: The user has chosen to continue theFlashcopy Restore operation.

System action: Restore processsing continues.


FMM0649I You are about to perform a FlashcopyRestore operation. All data on thesource volumes, including (but notlimited to) filesystems and raw volumes,will be lost. Do you want to continue?Please enter Yes or No.

Explanation: Flashcopy Restore overwrites anyexisting data on all the source LUNs, including (but notnot limited to) all filesystems and raw volumes onthem. Make sure all necessary data from the sourceLUNs is backed up, and restart the procedure.

System action: System waits for a valid user response.

User response: Please enter "Yes" to continue, or "No"to abort the restore operation.

FMM0650I A Flashcopy Restore operation has beenrequested, with Prompt=No. All data onsource volumes, including (but notlimited to) filesystems and raw volumes,will be lost. Continuing FlashcopyRestore operation.

Explanation: Flashcopy Restore overwrites anyexisting data on all the source LUNs, including (but notlimited to) all filesystems and raw volumes on them. Itis strongly recommended that this operation beperformed with Prompt set to Yes. The user has chosento perform this operation with Prompt set to no.



System action: Restore operation continues.


FMM651E The 'prefix' prefix is not contained in thestring 'searchstring' in the input file.

Explanation: A Syntax error occured in the input file.


User response: The named prefix cannot be found inthe string. The prefix is required in the input file.

FMM0652E Invalid license is detected.

Explanation: An invalid license was found.


User response: Check if there is a mismatch betweenthe executables (for the production system and backupsystem) and the license file(agent.lic).

FMM653I The 'operation' request processedsuccessfully.

Explanation: This message is for informationalpurpose only.



FMM654E The following instance UUIDs have notbeen found in the datastores that areincluded in the backup. They are notpart of the backup.instance uuids

Explanation: The specified instance UUIDs have notbeen found in the datastores that are included in thebackup. They are not part of the backup.

System action: Processing continues but the specifiedinstance uuid's are not part of the backup.

User response: Specify valid instance UUIDs of virtualmachines that are listed in the input file.

FMM655E The 'prefix' prefix in the input file is notallowed for single disk restoreoperations.

Explanation: A syntax error occured in the input file.


User response: Add the correct prefix to the input file.

FMM0656E An error has been detected whenrunning the TSM Backup Archive Clientcommand line interface.

Explanation: An error was detected when running theTSM Backup Archive Client Client command lineinterface.


User response: Make sure the TSM Backup ArchiveClient is correctly installed and that the environmentalvariables are set correctly.

FMM0657E A memory allocation error has occurred.

Explanation: Enough memory was not available tocontinue processing.


User response: Ensure that your system has sufficientreal and virtual memory. Close unnecessaryapplications.

FMM665E There are multiple NFS serversinvolved: the NFS server 'nfsserver1' forthe file 'filename' is different from theprevious NFS server 'nfsserver2'.

Explanation: In NAS environments, the files passedfrom the application or database during the fist phase(partition) of the snapshot backup must reside in asingle NAS storage system.


User response: Move the file systems and files of onesingle application or database instance to a single NASstorage system.

FMM0666E Could not open trace file v1.

Explanation: There were some problems openingtracefile. Please make sure you can open the trace filewhich was specified in the setup file.

System action: Processing terminates.


FMM0667E Could not create the trace object.

Explanation: There were some problems creating traceclass object.



FMM0668E Invalid trace flag: v1.

Explanation: Some invalid trace flags are defined inthe setup file.





FMM0672E Error while querying volume propertiesof volume volserial. Please verify that thevolume specified in the target volumesfile exists.

Explanation: None.


User response: Contact the administrator of thestorage subsystem with the information provided inthis message.

FMM0673E A Flashcopy background copy is inprogress between source volume: sourcevolume and target volume: target volume.

Explanation: A Flashcopy background copy from aprevious operation is not complete for the given sourceand target volumes.

System action: Command will fail.

User response: Please wait until the background copyis complete and retry the command.

FMM0674E A Flashcopy association exists betweensource volume: source volume and adifferent target volume: target volume.

Explanation: A Flashcopy association exists betweenthe source volume and a target other than thedesignated target volume.

System action: Restore command will fail.

User response: Please withdraw the Flashcopyassociation between the source volume and the targetvolume and retry the restore command.

FMM0675E An unexpected error was encountered.function name : function-name function :function-desc return code : rc file :file-name (line-number)

Explanation: None.


User response: Contact the administrator with theinformation provided in this message.

FMM0676E program-name: cannot open file file-spec:error.

Explanation: IBM Tivoli Storage FlashCopy Managercannot open the file.

System action: IBM Tivoli Storage FlashCopyManager cannot complete the requested operation.

User response: Retry the operation. If the problemcontinues, check with your system administrator.

FMM0710E Unable to close trace output filefile-name.

Explanation: An error occurred during the closing of atrace output file-name (for example, not enough diskspace).


User response: Check the options.doc file for adescription of possible causes of the error, or see yoursystem administrator.

FMM0711E Unable to write to trace file tracefile.Tracing disable d.

Explanation: An error occurred when writing to thespecified tracefile.

System action: Tracing is disabled. Processingcontinues.

User response: Ensure the device that contains thetracefile is available, has sufficient space for the tracefileand the user has write permission to the targetdirectory. Retry the command.

FMM0712E Invalid trace file name (name too long).

Explanation: A TRACEFILE option in the preferencesfiles used a file name that is too long.

System action: Client program did not initialize.

User response: Change the file name used as theTRACEFILE so that it is equal to or less than 255characters in length.

FMM0727E Specifying the trace file 'link' as asymbolic link is not allowed.

Explanation: Trace file 'linkname' cannot be a symboliclink.

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.

FMM0728E Symbolic link 'linkname' to 'target' wassuccessfully deleted.

Explanation: Log 'linkname' cannot be a symbolic link.

System action: The symbolic link 'linkname' is deleted,the log is recreated, and processing stops.

User response: Check the location of the new file. Tospecify the location of log files, refer to the user'smanual for the 'errorlogname' option, the'schedlogname' option, and the 'DSM_LOG'environmental variable.



FMM0729E Unable to delete symbolic link 'link'.



User response: Delete the symbolic link 'linkname'.

FMM0739E Invalid trace keyword - 'keyword'

Explanation: A TRACEFLAG option in the userconfiguration file or on the command line is incorrect.

System action: Client program did not initialize ortracing was not enabled in the applet.

User response: Correct the value. See the entry forTRACEFLAGS in the Trace Facility Guide document fora list of valid trace flags.

FMM0740E Unable to open trace output filefile-name.

Explanation: A TRACEFILE option in the userconfiguration file or on the command line used adirectory path and file-name combination to which youdo not have write access.


User response: Change the TRACEFILE value so thatit is a location to which you have write access.

FMM0741E The physical volumes of the volumegroup v1 were not found.

Explanation: DP for Snapshot Devices will issue thecommand 'lsvg -M <vgname>' in a LVM mirrorenvironment to determine on which physical andlogical volumes is residing the production database.This command failed.


User response: Check the return code of lsvg. Consultthe AIX system documentation.

FMM0742E Varying off volume group fnm1 failed.

Explanation: After the unmount of the database filesystems, DP for Snapshot Devices will vary off thedatabase volume groups on the backup system. Thecommand varoffvg has failed.


User response: Check the specific error message.Consult the AIX system documentation. Check forproceeding errors during the unmount process.

FMM0743I <fn1> VOLUME GROUP : fn2 COPIES :fn3 SCHED POLICY : fn4 STALE PPs :fn5 MIRROR WRITE CONSISTENCY:fn6

Explanation:


User response:

FMM0744I <lvname><copy><pv><serialno><status>

Explanation: Finding the source volumes of theproduction database in a LVM mirror environment, DPfor Snapshot Devices will display a list of all the logicalvolumes with the number of copies, the physicalvolumes, the serial number and the status. The status isonly displayed for the case of stale.



FMM0745W Logical volume vg1 has vg2 stalepartitions.

Explanation: DP for Snapshot Devices checks first allthe logical volumes for stale partitions and issues firstonly a warning if it finds some. The mirror set that isresiding in the hardware unit that was chosen for theFlashCopy on this specific run, have to be free fromstale partitions.


User response: Check why you are having stalepartitions. If necessary, synchronize the logical volumesof the production database.

FMM0746E The source volume with serial numbercmd is not attached to the productionsystem.

Explanation: The specified physical volume wasfound during the FlashCopy backup as part of thedatabase volumes on the production system. Now,during the FlashBack Restore, it is no longer found onthe production system.

One of the reasons this may occur is if you are in aremote mirror environment and are trying to restorethe backup on an incorrect host - local backup ontakeover host or remote backup on local host.


User response: Logon with the user root and issue thecommand lsvpcfg. Check if the volume is displayed.Use the storage-system user interface to find out towhich host this volume is attached. You will be able torestart the FlashBack restore anytime, as long as youhave a valid disk backup on the target volumes.



FMM0747E The source volume with serial numbercmd belongs to another volume group.

Explanation: The specified physical volume wasfound during the FlashCopy backup as part of thedatabase volumes on the production system. Now, onthe FlashBack restore, DP for Snapshot Devices found itas member of another volume group and can notproceed with the restore.


User response: You must remove this volume fromthe other volume group if you want to use thespecified FlashCopy backup for the FlashBack restore.You will be able to restart the FlashBack restoreanytime, as long as you have a valid disk backup onthe target volumes.

FMM0748W The logical volume lv on the mountpoint mp was renamed or newly added.

Explanation: DP for Snapshot Devices found adifference between the names of the logical volumeswhich were on the production database at the time ofFlashCopy backup and the current logical volumes atthe time of the FlashBack Restore.


User response: DP for Snapshot Devices will ask youduring the FlashBack Restore if you are sure tocontinue, before all the file systems and logical volumesare removed. After that, DP for Snapshot Devices willonly reconstruct the file systems which were backed upwith FlahCopy. You have to add manually all theadditional system changes that were made after theFlashCopy backup.

FMM0749I List of the current file systems on thebacked up volume groups ...

Explanation: Prior the start of the FlashBack restore,DP for Snapshot Devices will display a list of all thefile systems which are currently on production databasesystem.



FMM0750I List of file systems which will berestored...

Explanation: Prior the start of the FlashBack restore,DP for Snapshot Devices will display a list of all thefile systems which were on production database systemat the time of the FlashCopy backup.



FMM0753W The newly added volume cmd will bedeleted from the database volume grouprc.

Explanation: The reducevg command removesphysical volumes from a volume group. DP forSnapshot Devices will call this command during theFlashBack Restore to remove the physical volumesadded to the database volume groups after theFlashCopy backup.



FMM0754I Logical volume lv was removed duringFlashcopy Restore, because it was newlyadded since last backup, needs to berecreated manually.

Explanation: DP for Snapshot Devices found adifference between the names of the logical volumeswhich were on the production database at the time ofFlashCopy backup and the current logical volumes atthe time of the FlashBack restore.


User response: DP for Snapshot Devices will ask youduring the FlashBack restore if you are sure to continuebefore all the file systems and logical volumes will beremoved. After that, DP for Snapshot Devices will onlyreconstruct the file systems which were backed up withFlahCopy. You have to add manually all the additionalsystem changes that were made after the FlashCopybackup.

FMM0755I The following commands should be runafter the FlashCopy process inbackground is finished to synchronizethe LVM copies:

Explanation: IBM Tivoli Storage FlashCopy Managerwill not automatically synchronize the copies after thereconstruction of the LVM mirror. A basic commandwill be created and printed out.


User response: You have to start the synchronizationof the LVM mirror manually after the FlashCopyprocess in background has finished. If necessary youhave to add additional parameter to the commands toimprove the performance of the synchronization.

FMM0756E Error converting the hdisk devicevolume group vg to a Subsystem DeviceDriver vpath device volume group.

Explanation: On the function FlashCopy backup, DPfor Snapshot Devices will use the command hd2vp toconvert the hdisk device volume group to a SubsystemDevice Driver vpath volume group. This will take effectafter the importvg and prior to the mount of the file



systems on the backup system.


User response: Check the return code and the errormessage of the hd2vp command. Consult the AIXsystem documentation.

FMM0757W The rmlv command lv ended with returncode rc.

Explanation: For the function FlashBack Restore, DPfor Snapshot Devices will use the command rmlv toremove the logical volumes onto which the productiondatabase should be restored. This will take effect afterthe unmount and prior to the exportvg and the actualFlashCopy.


User response: Check the return code and the errormessage of the rmlv command. Consult the AIX systemdocumentation. You will be able to restart theFlashBack restore anytime, as long as you have a validdisk backup on the target volumes.

FMM0758E DP for Snapshot Devices encountered aproblem when using the FlashCopyfunction of the Copy Services.

Explanation: DP for Snapshot Devices requested for aset of source/target volume pairs a FlashCopy to bedone by the Copy Services. If the request fails withinthe storage system for one or more pairs with anon-zero return code, then DP for Snapshot Deviceswill provide the return code and then terminate.


User response: In order to identify which volume(s)were the cause of the problem you need to view theCopy Services status log for failures, there you find thefailing volume(s) along with details about possiblecauses of the problem.

FMM0759E The file system fs already has an entryin the /etc/filesystems.

Explanation: On the backup system after theFlashCopy, DP for Snapshot Devices found that thespecified file system still exist in the /etc/filesystems.


User response: Normally the command "exportvg"will remove the corresponding file systems from the/etc/filesystems. Check for errors during the unmountand withdraw process.

FMM0760W The reducevg command cmd ended withreturn code rc.

Explanation: The reducevg command removesphysical volumes from a volume group. DP forSnapshot Devices will call it 1. on FlashBack restore toremove the physical volumes added after theFlashCopy backup. 2. on FlashBack restore with LVMmirroring to remove the physical volumes which areresiding on the hardware unit that is not yet involvedin the FlashBack. 3. on FlashCopy backup with LVMmirroring if the environment variable IMPORTVG isset, to remove the physical volumes which are residingon the hardware unit that is not yet involved in theFlashCopy.


User response: Check the return code and the errormessage of the reducevg command. Consult the AIXsystem documentation.

FMM0761W The extendvg command cmd ended withreturn code rc.

Explanation: The extendvg command adds physicalvolumes to a volume group. DP for Snapshot Deviceswill call it to add the volumes which are residing onthe hardware unit that is not yet involved in theFlashBack to the database volume groups.


User response: Check the return code and the errormessage of the extendvg command. Consult the AIXsystem documentation.

FMM0762W The mklvcopy command cmd endedwith return code rc.

Explanation: DP for Snapshot Devices will call thecommand mklvcopy to add a copy of a logical volumeon the physical volumes residing on the secondhardware unit. This call will only take effect in a LVMmirroring environment, after the FlashBack restore wasinitialized. The FlashBack restore and the recovery willcontinue, but the second copy of the logical volumeswill be missing.


User response: Check the return code and the errormessage of the mklvcopy command. Consult the AIXsystem documentation. Check for errors during thedisabling process (unmount, rmfs, rmlv, varyoffvg,exportvg). You will be able to restart the FlashBackrestore anytime, as long as you have a valid diskbackup on the target volumes.



FMM0763I Removing copies from the logicalvolumes ...

Explanation: On the function FlashBack restore, DPfor Snapshot Devices will use the command rmlvcopyto remove the copies of the logical volumes residing onthe second hardware unit. This will take effect after theunmount and prior to the exportvg and the actuallyFlashCopy reverse.



FMM0764I Removing physical volumes from thevolume groups ...

Explanation: On the function FlashBack restore, afterthe rmlvcopy and prior to the exportvg and theactually FlashCopy reverse, DP for Snapshot Deviceswill use the command reducevg to remove the physicalvolumes residing on the second hardware unit.



FMM0765I Adding physical volumes to the volumegroups ...

Explanation: On the function FlashBack restore, afterthe FlashCopy reverse and the import of the volumegroups, DP for Snapshot Devices will add the physicalvolumes residing on the second hardware unit to thedatabase volume groups.



FMM0766I Adding copies to the logical volumes ...

Explanation: On the function FlashBack restore, DPfor Snapshot Devices will use the command mklvcopyto add the copies of the logical volumes on the secondhardware unit. This will take effect after the importvgand the extendvg.



FMM0767W The command cmd ended with returncode rc.

Explanation: The execution of the system commandended with the displayed return code.


User response: Check the return code and the errormessage of the specified command. Consult the AIXsystem documentation.

FMM0768E Importing the volume group from hdisklogdev failed.

Explanation: DP for Snapshot Devices will use thecommand "importvg" on the function FlashCopybackup. This command will be issued on the backupsystem after the actually FlashCopy and the run of theconfiguration manager(cfgmgr). It takes a volumesfrom each volume group building up the productiondatabase, reads its VGDA and makes this informationavailable to the operating system.


User response: Check the return code and the errormessage of the importvg command. Consult the AIXsystem documentation.

FMM0769E Recreating the volume group from thehdisks hdisks failed.

Explanation: DP for Snapshot Devices will use thecommand "recreatevg" on the function FlashCopybackup if the production database is residing on anhigh-available LVM mirror environment. Thiscommand will be issued on the backup system after theactually FlashCopy and the run of the configurationmanager (cfgmgr). The difference to the command"importvg" is that recreatevg will create the volumegroup only with the specified volumes. These arebuilding up exact the one copy on the hardware unitwhere the FlashCopy was issued.


User response: Check the return code and the errormessage of the recreatevg command. Consult the AIXsystem documentation.

FMM0770I Removing the logical device logdev withthe same PVID pvid in the ODM.

Explanation: There is still another logical device(hdisk or vpath) in the state defined with the samePVID as one of the source volumes.



FMM0771I Could not mount all the filesystemsoriginally present.

Explanation: This message will appear if running thefunction FlashBack restore, a file system was found thatwas added after the FlashCopy backup.

System action:

User response: The user is responsible for create thenew file system after the FlashCopy reverse, but beforethe recovery, if this file system was already used fromthe production database.



FMM0772W The database volume groups do notcontain currently any file system.

Explanation: This message will appear if running thefunction FlashBack restore, none file system was foundon the original database volume group. Following that,DP for Snapshot Devices will display a list of the filesystem which are residing on the FlashCopy targetvolumes. These will be restored by means of FlashBack.

System action:


FMM0773W One or more errors were founddisabling the production systemresources. However, the FlashBackrestore will continue.

Explanation: This message will appear if, whenrunning the function FlashBack restore, an error occursunmounting the existing file systems and removing thevolume groups. However, DP for Snapshot Devices willcontinue with the FlashBack restore.

System action:


FMM774I The 'diskname' virtual disk on the 'virtualmachine name' virtual machine issuccessfully restored to the 'target virtualmachine' virtual machine and is added toits configuration.

Explanation: The specified virtual disk has beensuccessfully restored.



FMM0775E The label of the logical volume lvname ismissing. Set it using chlv -L mountPointlogicalVolume.

Explanation: IBM Tivoli Storage FlashCopy Managerrequires the label of the logical volume to be set.Otherwise there will be an error importing the volumegroups on the backup system.


User response: Set the label of the logical volumeusing: chlv -L mountPoint logicalVolume.

FMM0776I Number of volumes to be processed byFlashcopy: v1

Explanation: Number of volumes to be processed byFlashcopy.



FMM0777E An unexpected error was encounteredprocessing a function. function name :function-name function : function-descreturn code : rc file : file-name(line-number)

Explanation: None.



FMM0778E SVC virtual disk v1 is not valid. Pleaseverify that the volume specified in thetarget volumes file exists.

Explanation: The specified virtual disk is not found inthe list of virtual disks provided by the connected SVCcluster.


User response: Ensure that of this virtual disk existsin the SVC.

FMM0779E The source v1 and target v2 virtual disksare in different SVC clusters.

Explanation: The SVC's source and target virtual diskshave to be assigned to the same SVC cluster forFlashCopy.


User response: Ensure that of the source and targetvirtual disks are in the same SVC.

FMM0780E The source v1 and target v2 virtual disksare of different size.

Explanation: The SVC's source and target virtual diskshave to be of the same size for FlashCopy.


User response: Ensure that of the source and targetvirtual disks are in the same SVC.

FMM0781E An error was returned calling anoperation of the Common InterfaceModel(CIM). function name :function-name received msg : function-descCIM return code: 0xCIM-rc file : file-name(line-number) If the received messagecontains 'CIM Error', then please collectthe CIM Agent logs and send them toCIM support.

Explanation: A error occurred calling a CIM operationof the disk subsystem.




User response: Please see section about the CIMreturn codes and its description in the manual.

FMM0782E A memory allocation error has occurredin file filename, line number linenumber.




FMM0783E The execution of command 'lscfg' failed.Please verify that the command 'tset -I-Q' is not set in the users environmentfiles .profile, .login.dbenv_<hostname>.sh,.dbenv_<hostname>.csh and.sapenv_<hostname>.sh,.sapenv_<hostname>.csh.

Explanation: If the command 'tset -I -Q' is set in theusers environment files .profile, .dbenv_<hostname>.sh,and .sapenv_<hostname>.sh, then the command 'lscfg'will fail with the output 'Not a terminal' and will notreturn any configuration. This will cause the IBM TivoliStorage FlashCopy Manager script 'hdwmap.sh' to fail.


User response: Ensure that the command 'tset -I -Q' isnot set in the users environment files .profile,.dbenv_<hostname>.sh, and .sapenv_<hostname>.sh .

FMM0784I The ONTAP filer version on thisappliance is: n.

Explanation: None.

System action: Process continues.


FMM0785W The option fractional reserve on volumevol_name was reduced to less than 100percent.

Explanation: N series extremely recommends thatwhen the fractional reserve is set to less than 100percent you actively monitor space consumption andthe rate of change of data in the volume to ensure youdo not run out of space reserved for overwrites. In thatcase, if you run out of overwrite reserve space, writesto the active file system fail and the host application oroperating system might crash.


User response: Ensure that you monitor the spaceconsumption. Consult NetApp for tools to monitoravailable space in your volumes.

FMM0786I Removing the snapshot snapshot name ofsource volume source volume (LUN LUNpath)

Explanation: The removal of the specified snapshot ofthe source volume was requested.



FMM0787E The snap restore for volume volnamewith snapshot name snapname woulddestroy later snapshots that are requiredfor other applications or for volumeclones.

Explanation: N series will delete newer snapshots of avolume when a specific snapshot is used for snaprestore.


User response: Prior a snap restore, ensure that newersnapshots are not used in other applications or involume clones.

FMM0788W IBM Tivoli Storage FlashCopy Managerdid not find any snapshots for volumevolname on the N series filer.

Explanation: No snapshots for this volumes in the Nseries filer found.



FMM0789W IBM Tivoli Storage FlashCopy Managerdid not find any information about theN series volume volname.

Explanation: Trying to get information about thisvolume did not return any data.



FMM0790E The snapshot name snapname for volumevolname was not found in the snapshotlist on the N series filer.

Explanation: Snapshot identified by this name doesnot exist.





FMM0791W Function refreh incremental FlashCopycannot be accomplish because noconsistency group found for thesevolumes.

Explanation: A refresh of the incremental FlashCopycan only be done when the consistency group and thecorrespondent FlashCopy relation were establishedpreviously.



FMM0792E The list of volumes passed contain pairswhich belong to different consistencygroups in the scope of one singlecluster.

Explanation: IBM Tivoli Storage FlashCopy Managerhandles for each operation only one consistency groupper cluster at the same time. If the set of volumes in abackup or restere operation contain pairs that belong todifferent consistency group inside one single cluster,then the process of the operation will be stopped.

System action: Process stopped.

User response: If you added volumes to theproduction database or to the target set, ensure thatthey are not in any FlashCopy relation.

FMM0793W No FlashCopy relationships found inthe storage system.

Explanation: The copy services server (mostly a CIMObject Manager) does not have any FlashCopy relationobjects.

System action: Process may stop.

User response: This is not necessarily a message thatimplies the stop of the process.

FMM0794E The state status of the consistency groupis bad to achive a valid disk backup.

Explanation: IBM Tivoli Storage FlashCopy Managerfunction monitoring will expect that the FlashCopy arein one of the state Idle_Copied or Copying.

System action: Process will stop.

User response: Verify using the storage GUI the stateof the FlashCopy. If this state was generated by an useraction, try to start the copy process through the storageGUI, then re-start the IBM Tivoli Storage FlashCopyManager moniotoring fuction.

FMM0795E Error initializing the connection to thecopy services server.

Explanation: IBM Tivoli Storage FlashCopy Managercould not initialize the connection to the copy servicesserver.


User response: Check previous error to identify theexact problem during the initialization.

FMM0796I Trying to connect to primary copyservices server 'cs_primary'.

Explanation: None.

System action: Process will continue.


FMM0797I Trying to connect to primary 'cs_prim'and/or secondary 'cs_sec' copy servicesserver.

Explanation: None.



FMM0798I The primary copy services server'cs_prim' is not responding. Thefollowing CIM error was reported:cim_err_msg Working with secondarycopy services server 'cs_sec'.

Explanation: None.



FMM0799E The primary copy services server'cs_prim' is not responding. Thefollowing CIM error was reported:cim_err_msg

Explanation: IBM Tivoli Storage FlashCopy Managercannot connect to the primary copy services server.


User response: Check that the primary copy servicesserver and the CIMOM on it is up and running.

FMM0800E Neither the primary 'cs_prim' nor thesecondary copy services server 'cs_sec'are responding. The following CIMerror was reported: cim_err_msg

Explanation: IBM Tivoli Storage FlashCopy Managercannot connect either to the primary nor to thesecondary copy services server.




User response: Check that one of both primary orsecondary copy services server and the CIMOMrunning on it is up and running.

FMM0801W The FlashCopy direction in theconsistency group cs_name is switched.A withdraw will be done prior tocontinue.

Explanation: The FlashCopy direction of source andtarget volumes in the consistency group is switched.This can be caused through the restore process. Awithdraw will be done prior to continue.



FMM0808E Operating system command 'command'failed; rc=rc.

Explanation: None.


User response: Check the return code from theoperating system for more information about thefailure. Issue the failing command manually to see ifthe same failure occurs.

FMM0809E The primary and secondary copy serviceservers are down.

Explanation: None.


User response: Start at least one of the copy serviceservers.

FMM0810E Cannot open the command output filev1 for writing.

Explanation: Can't open this file for writing.


User response: Make sure you have enough space onyour system and write permission to the file.

FMM0811E The LUN are already in use.

Explanation: None.


User response: Release LUN in order to reuse them.

FMM0812I The backup DB2 UDB previewcommand indicates there are sufficientresources for a backup operation.

Explanation: None.



FMM0836E Error while invoking the diskmapper.

Explanation: Invokation of diskmapper failed.



FMM0837E The path 'v1' is not a character device.

Explanation: The path queried from the ASM instanceis not a valid character device.


User response: Check the setup of you ASM instance.

FMM0838W The following files have been found inthe diskgroup allthough they do notbelong to the database and are notcontained in the negative list: 'files'.

Explanation: Additional files have been found whichdo not belong to the database and which are notcontained in the negative list.

System action: The mentioned files will be containedin the backup.

User response: If you do not want these files to becontained in the backup please remove them from thediskgroup. If you want them to be included please addthem to the negative list.

FMM0839E Not all disks of the failure group'failureG' of diskgroup 'diskG' were foundon the configured storage subsystem.This failure group is excluded fromfurther processing.

Explanation: Disks of the specified failure group couldnot be found on the storage subsystem that wasconfigured. Thus, this failure group cannot participatein the FlashCopy operation.


User response: Ensure that all disks of the specifiedfailure group reside on the storage subsystem that wasconfigured within the IBM Tivoli Storage FlashCopyManager configuration.



FMM0840E Not enough failure groups forredundancy type 'redType' in diskgroup'diskGroup'. 'foundFG' have been foundbut 'neededFG' are needed for thisredundancy type. Please make sure thatthe currently selected DEVICE_CLASScontains enough failure groups for aconsistent flashcopy and ensure thatthey are online.

Explanation: There are not enough online failuregroups for the redundancy type of the diskgroup onthe current storage device. The backup would not berestorable.


User response: Please make sure that the currentlyselected DEVICE_CLASS contains enough failuregroups for a consistent flashcopy and ensure that theyare online.

FMM0841E Not all disks reside on the same cluster.Disks were found on the cluster with id:'first cluster id' and on the cluster with id'second cluster id'.

Explanation: The disks of the diskgroups needed forthe flashcopy do not reside on one storage device.


User response: If you specified failure groups in theprofile ensure that the disks they are located on resideon the same storage device. If you did not specify anyensure that all diskgroups needed for the flashcopyreside on the same storage device.

FMM0842E The ASM diskgroup 'diskGroup' couldnot be dropped but is still available inthe ASM instance. Restore will bestopped.

Explanation: The specified diskgroup could not bedropped but it is still available in the ASM instance. Arestore could lead to an inconsistent state of thediskgroup.


User response: Check the state of the specifieddiskgroup and try to drop it manually.

FMM0843E The ASM diskgroup 'diskGroup' couldnot be unmounted and is still mountedin the ASM instance. Unmount will bestopped.

Explanation: The specified diskgroup could not beunmounted and is still mounted in the ASM instance.Continuing with the unmount operation could lead toan inconsistent state of the diskgroup.


User response: Check the state of the specifieddiskgroup and try to unmount it manually.

FMM0844E No target volume is available for serial'serial'.

Explanation: No target volume was found for thespecified serial.


User response: Ensure your backup system is in aconsistent state and that mapping new volumes to thebackup system works properly.

FMM0845E The volume manager of your profile isnot set to ASM, the found value is'serial'. Ensure that you have set the rightvolume manager in your profile.

Explanation: The value for volume manager in theprofile is wrong.


User response: Set the volume mangager in the profileto ASM.

FMM0846E You have SDD installed on your system,but SDD is currently not supported bythis product when using Oracle ASM.

Explanation: The value for volume manager in theprofile is wrong. SDD is not supported for ASM, onlySDDPCM and MPIO are supported for ASM.


User response: Install SDDPCM or use MPIO only.

FMM0847E Error occured while checking the'db2nodes.cfg' on the production systemand on the clone system. The'db2nodes.cfg' on the production systemcontains production system entries entries,whereas the 'db2nodes.cfg' on the clonesystem contains clone system entriesentries.

Explanation: The DB2 partition configuration file(db2nodes.cfg) on the production system has a differentnumber of partition configuration entries than itscounterpart on the clone system.


User response: Verify the number of partitionconfiguration entries of the DB2 partition configurationfile (db2nodes.cfg) on the production system as well ason the clone system. The number of entries within eachof these files have to have identical.



FMM0848E Error occured while checking the'db2nodes.cfg' on the production systemand on the clone system. The databasepartition partition number configured onthe production system is not configuredon the clone system.

Explanation: The DB2 partition configuration file(db2nodes.cfg) on the production system has a partitionconfigured which is not configured in the DB2 partitionconfiguration file (db2nodes.cfg) on the clone system.


User response: Verify that all partitions configured inthe DB2 partition configuration file (db2nodes.cfg) onthe production system are configured denoted by thesame partition number on the clone system as well.

FMM0849E Error occured while checking the'db2nodes.cfg' on the production systemand on the clone system. The hostname'host name' where partition partitionnumber resides is contained in the'db2nodes.cfg' on the production systemas well as on the clone system. Eitherthe setup of the 'db2nodes.cfg' file onthe clone system is wrong or the clonesystem was configured on the same hostas the production system.

Explanation: The DB2 partition configuration file(db2nodes.cfg) on the production system contains atleast for the named partition the same host entry likeits counterpart on the clone system.


User response: Verify that the DB2 partitionconfiguration file (db2nodes.cfg) on the clone system isvalid. Further ensure, that the mount agent (processcredentials: acsgen -D -M) is running on the clonesystem, which has to be a different host than theproduction system.

FMM0850I To synchronize the volume groups thathave stale partitions you can use thefollowing commands:

Explanation: IBM Tivoli Storage FlashCopy Managerdoes not automatically synchronize the copies after thereconstruction of the LVM mirror during a FlashCopyrestore. A basic command will be created and printedout.


User response: You have to start the synchronizationof the LVM mirror manually for example after aFlashCopy restore when the background copy processin the storage system has finished. If necessary youhave to add or change parameters to the commands toimprove the performance of the synchronization.

FMM0851E The copyservices timeout value offsname minutes was reaced whilewaiting for an answer of thecopyservices CIM agent. Specifyincrease the value of the profileparameter COPYSERVICES_TIMEOUTin the DEVICE_CLASS section of theprofile, to increase the timeout limit.The default value of this parameter is 6minutes.

Explanation: The communication with thecopyservices CIM agent terminated after the timeoutvalue specified by the COPYSERVICES_TIMEOUTparameter was already exceeded.


User response: Increase the timeout value for theCOPYSERVICES_TIMEOUT parameter.

FMM0852E It is not allowed to establish a secondincremental FlashCopy relation from asource volume source volume to a targetvolume target volume while anotherincremetal FlashCopy relation from thesame source volume to a different targetvolume already exists.

Explanation: The IBM System Storage® DS8000® doesonly support to have one incremetal FlashCopy relationfrom a source to a target.


User response: Use a different value for profileparameter FLASHCOPY_TYPE (COPY or NOCOPY) orreuse the existing incremental relations by using thesame device class and target set for the restart of thebackup operation.

FMM0853E During the mount operation IBM TivoliStorage FlashCopy Manager identifiedthat the following source volumes arevisible on the backup or cloning system'host name'. This can be caused bymisconfiguration in the storage systemor by misconfiguring the IBM TivoliStorage FlashCopy Manager backup orcloning system to the same host as theproduction system. List of visible sourcevolumes: source volumes

Explanation: The IBM System Storage DS8000 doesonly support to have one incremetal FlashCopy relationfrom a source to a target.





FMM0854E During the mount operation IBM TivoliStorage FlashCopy Manager identifiedthat the following target volumes arenot visible on the backup or cloningsystem 'host name'. List of missing targetvolumes: target volumes

Explanation: The IBM System Storage DS8000 doesonly support to have one incremetal FlashCopy relationfrom a source to a target.



FMM0855E During the mount operation IBM TivoliStorage FlashCopy Manager identifiedthat the following target volumes arenot visible on the ESX host 'host name'.List of missing target volumes: targetvolumes Either the volumes could not beassigned to the host correctly or youused PRE_ASSIGNED_VOLUMES forthe TARGET_SETS parameter in yourDevice Class section and the targetvolumes are not assigned to this ESXhost.

Explanation:


User response: Check the error log for detailedinformation.

FMM0856E The datastore 'datastore name' cannot beattached to the ESX host: 'host name', thedatastore is already attached to anotherESX host. You must detach the datastore that is currently attached to theESX host and try the task again.

Explanation:


User response: Check the error log for detailedinformation.

FMM0857E The virtual disks of the source virtualmachine 'source vm name' cannot beattached because a disk is alreadyattached to a target virtual machine.Detach all virtual disks of the sourcevirtual machine and try the attach taskagain.

Explanation: Because a virtual disk is already attachedto the target virtual machine, the virtual disks of thesource virtual machine cannot be attached.


User response: On the target virtual machine, detachall virtual disks. Try to attach the virtual disks from thesource virtual machine to the target virtual machineagain.

FMM1000E syntax error in line line : 'statement'

Explanation: The statement statement in the DataProtection for SAP profile is unknown or incorrect.

System action:

User response: Correct the error and try again.

FMM1001E syntax error in file 'file name'. Exitingprogram.

Explanation: A syntax error has been detected in thefile file name and the action has been halted.

System action:

User response: Correct the error(s) in the file file nameand try again.

FMM1002E BACKUPIDPREFIX must benumber_of_characters characters !

Explanation: The length of BACKUPIDPREFIX mustbe number_of_characters characters.

System action:

User response: Enter a BACKUPIDPREFIX with therequired length (for example, SAP___, FMM___).

FMM1003W Please set redolog_copies to a numberbetween min_copies and max_copies a.Now it is set to act_copies.

Explanation: Data Protection for SAP currentlysupports 1 to 9 copies of offline (redo) log files.

System action:

User response: Adapt the REDOLOG_COPIES settingsin the Data Protection for SAP profile.

FMM1004W You should specify theBACKUPIDPREFIX before theTRACEFILE statement. So that theBACKUPIDPREFIX can be used in thetracefilename.

Explanation: The BACKUPIDPREFIX is used to buildthe Name of the tracefile. Therefore,BACKUPIDPREFIX must be specified before theTRACEFILE statement.

System action:

User response: Define a 6–characterBACKUPIDPREFIX in the Data Protection for SAPprofile (for example, SAP___, FMM___)



FMM1006E The SERVERNAME must be less thanmax_char characters.

Explanation: You have used a SERVERNAME withmore than max_char characters.

System action:

User response: Use a shorter SERVERNAME.

FMM1007E The NODENAME must be less thanmax_char characters.

Explanation: You have used a NODENAME withmore than max_char characters.

System action:

User response: Use a shorter NODENAME.

FMM1008E The MANAGEMENTCLASSNAMEmust be less than max_char characters.

Explanation: You have used aMANAGEMENTCLASSNAME with more thanmax_char characters.

System action:

User response: Use a shorterMANAGEMENTCLASSNAME.

FMM1009W Please set MULTIPLEX to a numberbetween 1 and max_multiplex. Now it isset to act_multiplex.

Explanation: You have set multiplexing to anunsupported number. Data Protection for SAP nowuses act_multiplex.

System action:

User response: Set multiplexing to a number between1 and max_multiplex.

FMM1011W The sortfilename 'sortfile_filename' shouldbe absolute!

Explanation: None.

System action:

User response: Specify an absolute file name, forexample /oracle/C21/dbs/sortfile.

FMM1012E Configfile not found or permissiondenied: 'configuration_filename'.

Explanation: Data Protection for SAP is unable to readthe file configuration_filename.

System action:

User response: This error could have various reasons,try the following: 1. Check the path of theconfiguration file. The path must be specified in the

profile (parameter CONFIG_FILE). 2. Make sure thatthe file access permissions are set correctly.

FMM1013E Profile not found or permission denied:'profile_filename'.

Explanation: Data Protection for SAP is unable toopen the profile profile_filename.

System action:

User response: (Oracle) Ensure that the SAP backupprofile init<SID>.sap contains a valid entry util_par_filefor the Data Protection for SAP profile. (DB2) Ensurethat the vendor environment file contains a valid entryXINT_PROFILE. Furthermore, this file must be readableby Data Protection for SAP.

FMM1014I Operation function was completedsuccessfully.

Explanation: This information message in thesummary log indicates that the requested operationcompleted.

System action: The operation was completed.


FMM1015E Operation function completed with error.

Explanation: This information message in thesummary confirms that a requested operation failed.

System action: The operation failed.

User response: Check the summary log and thedetailed log used by the failed operation in order toidentify the failure.

FMM1016W The tracefilename 'file name' could not beopened for writing!

Explanation: The trace file could not be opened forwriting.

System action:

User response: Ensure that you have specified acorrect path for the trace file.

FMM1017E The server server is already defined.Please use another name or specifyTCP_ADDRESS!

Explanation: The named server was already definedin the profile. Server stanzas with identical names arenot allowed unless the keyword TCP_ADDRESS isdefined in one of them.

System action:

User response: Update the profile accordingly and tryagain.



FMM1019E Failed to respond to a message receivedfrom XINT.

Explanation: This messages indicates an internal error.

System action:

User response: Contact IBM Support.

FMM1021E component_name terminates theconnection due to a previous error.

Explanation: A serious error has occurred whichcaused a shutdown of the communication channelbetween the component_name process and thisapplication.

System action:

User response: Look for previous error messages todetect the root cause of the problem.

FMM1022E component_name terminates theconnection due to a previous error.

Explanation: See message FMM1021E.

System action:

User response: See message FMM1021E.

FMM1023W Could not establish connection to logserver log server name.

Explanation: In the Data Protection for SAP profile,log server log server name is specified (keywordLOG_SERVER). However, a connection to the servernamed could not be established. No log records aresent to the log server.

System action:

User response: Complete the following checks:

v Check that the server name defined with keywordLOG_SERVER is spelled correctly in the DataProtection for SAP profile.

v Make sure there is a SERVER section in the profilefor the log server defined with keywordLOG_SERVER.

v Check the corresponding SERVER section and correctany setup problems.

v Make sure that the log server named is available.

FMM1024E The file filename occurs twice in the<infile>

Explanation: The named file name occurs multipletimes in the infile which is a violation of the interfacespecification.

System action:

User response: Check the logs for further information.

If the problem cannot be resolved contact your IBMsupport personnel.

FMM1025E You must use consistency groups whenusing ASM. Set the profile parameter'profile param' accordingly.

Explanation: The profile specified that consistencygroups should not be used. However, ASM requires theuse of consistency groups.


User response: Update your profile accordingly.

FMM1026E Writable snapshots must be used whenrunning in an LVM mirroringenvironment. Update the profileparameter 'profile param' accordingly.

Explanation: The profile specified that writablesnapshots should not be used. However, writablesnapshots must be used in LVM mirroringenvironments.


User response: Update your profile accordingly.

FMM1027E The mount operation failed. Althoughan unmount operation can clean up thebackup system, in some cases this is notpossible and the cleanup must beperformed manually. In this case, theunmount operation should be startedafter cleanup in order to start anothermount operation.

Explanation: The mount operation failed. Although anunmount operation can clean up the backup system, insome cases this is not possible and the cleanup must beperformed manually. In this case, the unmountoperation should be started after cleanup in order tostart another mount operation.


User response: To cleanup your backup system, try tounmount the backup using tsm4acs. If the unmountoperation does not succeed, clean up your backupsystem manually and use tsm4acs again to unmountthe backup.

FMM1029W Device 'device' could not be opened.Received error message from theoperating system: 'error_message'. Thisdevice might cause the currentFlashCopy Manager operation to fail.

Explanation: The specified device could not beopened.




User response: Check the device for errors.

FMM1030E The operating system refused a requestfor memory allocation.

Explanation: IBM Tivoli Storage FlashCopy Managerrequires access to memory in order to store informationas processing proceeds. In this case, more memory wasrequested than the operating system would allocate.Possible reasons include:

v The system is low on memory.

v The process in which the program runs has exceededthe maximum memory that it is allowed to allocate.

v Some other error condition occurred that caused theprogram to think it is out of memory.

System action: IBM Tivoli Storage FlashCopyManager cannot complete the requested operation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units.

For UNIX systems that support resource limits, checkto see b if the memory resource limit is too low byentering the following command: ulimit -a

Based on the resulting data, you can ask the UNIXsystem root user to increase resource limits so that itwill override the current default. The UNIX system rootuser has the authority to increase resource limits.

FMM1031I The tape backup received this ID:'tape_backup_id'.

Explanation: The tape backup received the specifiedID. The backup is available for restore from tape withthis ID as soon as the tape backup completedsuccessfully.


User response: No action required.

FMM1032E The nodes of PARTITION_GROUP'partition_group_name' are associated withmultiple device classes: 'first_device_class','second_device_class'

Explanation: Multiple device classes are used with thesame partition group. Only one device class can beused for all nodes that belong to one partition group.


User response: Use only one device class for thespecified partition group in the profile.

FMM1033W The backup 'backup_id' is not expiredbecause it is still valid in the repository.You can either manually delete thisbackup or set the parameterMAX_VERSIONS to ADAPTIVE. Notethat this parameter setting turns offsnapshot expiration.

Explanation: The specified backup is still valid andcannot be expired.


User response: Manually delete the specified backupor set the parameter MAX_VERSIONS to ADAPTIVE.Note that this parameter setting turns off snapshotexpiration.

FMM1039E Aborting backup. Another backup withID 'backup_id' is already mounted onbackup server: 'host'.

Explanation: After the backup completes, a mountoperation is required to verify that it is a valid backup.Another backup with the same mountpoints is alreadymounted on the same backup server. As a result, themount operation is not attempted and the backup endsto prevent it from failing.


User response: You can either unmount the specifiedbackup from the specified backup server, or if anautomated tape backup is running, wait until itcompletes.

FMM1040E An exception occured in the operatingsystem adapter component, exceptiontext: extext.

Explanation: An exception occured in the operatingsystem adapter component.



FMM1041E Failed to identify the default DB2instance of user DB2 instance owner.Please set the DB2 environment variableDB2INSTANCE correctly.

Explanation: The default DB2 instance could not beidentified.


User response: The environment variableDB2INSTANCE has to be set to a valid value.



FMM1042E The entry in the FLASH_DIR_LIST fileis not a valid file or directory: entry.

Explanation: It is also possible to flash or clone nondatabase related files or directories. IBM Tivoli StorageFlashCopy Manager checks whether the files ordirectories specified in the FLASH_DIR_LIST exist priorthe flash or cloning operation is started.


User response: Verify the reported invalid entry in theFLASH_DIR_LIST file and revise the entry accordingly.

FMM1043E The environment is set up for the wrongdatabase instance: 'wrong instance'.Expected instance 'expected instance'.

Explanation: The name of the instance returned by thedbms does not match the expected instance name. Theexpected instance name is taken either from theenvironment variable ORACLE_SID or can beoveridden with the command line option '-d<database_name>'.


User response: Make sure the environment variableORACLE_SID is set correctly or specify the instancename with the command line option '-d<database_name>'.

FMM1044E The section CLONING is missing fromthe profile.

Explanation: To perform any of the cloning realatedfunctions the section CLONING must be added to theIBM Tivoli Storage FlashCopy Manager profile.


User response: Add the section CLONING to the IBMTivoli Storage FlashCopy Manager profile.

FMM1045E The parameter TARGET_SETSVOLUMES_DIR must not be used forcloning operations.

Explanation: TBD_AU


User response: TBD_AU

FMM1046E FlashCopy Cloning is not supportedwith FLASHCOPY_TYPE NOCOPY.Please specify COPY or INCR instead.

Explanation: TBD_AU



FMM1047E Expected keyword 'expected keyword' butfound 'wrong keyword'.

Explanation: During IBM Tivoli Storage FlashCopyManager profile parsing a wrong keyword was foundwhereas another keyword was expected.


User response: Check the IBM Tivoli StorageFlashCopy Manager profile section containing thewrong keyword and adjust it accordingly.

FMM1048E Device section 'device section' can not beused for cloning. Either add'USE_FOR_CLONING <SID>' to reservethis device class for cloning operationsor choose another device class.

Explanation: The referred device class cannot be usedfor cloning operations.


User response: A possible solution is to either add'USE_FOR_CLONING <SID>' to reserve this deviceclass for cloning operations or to choose another deviceclass instead.

FMM1049E No DEVICE_CLASS found that can beused for the current FlashCopy Cloningoperation with the clone database namespecified with the command line option-C <Clone DBname>.

Explanation: No device class section in the IBM TivoliStorage FlashCopy Manager profile could be foundwhich is eligible for cloning operations.


User response: Check the value of the'USE_FOR_CLONING' argument of theDEVICE_CLASS parameter in the CLONING section ofyour profile.

FMM1050E The mandatory argument argument aspart of the device class parameter deviceclass does not exist.

Explanation: For some operations, e.g. cloning, adedicated device class section must be specified in theIBM Tivoli Storage FlashCopy Manager profile. This isdone by attaching a special mandatory argument stringto the device class parameter.


User response: Add the mandatory argument to thefavoured device class section parameter.



FMM1051E The keyword 'use_for_cloning_keyword' isneeded for the keywordTARGET_NAMING in the device class'device class' because this device class isused for cloning.

Explanation: The keyword TARGET_NAMINGrequires the specified keyword if the device class isused for cloning.


User response: Specify the specified keyword forTARGET_NAMING.

FMM1052E The parameter TARGET_NAMING ofthe device class 'device class' is notconfigured for cloning of the databaseinstance 'instance'.

Explanation: To be able to use a dedicated deviceclass for cloning operations it has to have setup for thatspecial type of operations. To mark it accordingly, thedevice class argument 'USE_FOR_CLONING' followedby the name (or SID) of the database instance to becloned has to have attached to the device class profileparameter TARGET_NAMING.


User response: Update the favoured device classparameter in the IBM Tivoli Storage FlashCopyManager profile.

FMM1053E Failed to identify the default DB2instance of user 'user name'. Theenvironment variable DB2INSTANCE ismissing.

Explanation: The default DB2 instance could not bedetected due to the required environment variableDB2INSTANCE is not set.


User response: Set the DB2 environment variableDB2INSTANCE accordingly.

FMM1054E Failed to attach to the DB2 instance'instance'.

Explanation: The process was unable to attach to thespecified DB2 instance.


User response: Check the application logs as well asthe DB2 diag log (db2diag.log) for further details. If theissue could not be resolved please contact your DB2administrator.

FMM1055E Failed to get the DB2 database managerconfiguration.

Explanation: The process was unable to get the DB2database manager (instance) configuration.



FMM1056E Failed to detach from the DB2 instance'instance'.

Explanation: The process was unable to detach fromthe specified DB2 instance.



FMM1057E Failed to query the DB2 client settings.

Explanation: The process was unable to query theDB2 client settings.



FMM1058E Failed to set the DB2 client parameters.

Explanation: The process was unable to set the DB2parameters.



FMM1059E Recovery of the DB2 database 'databasealias' failed.

Explanation: The database rollforward recovery failed.


User response: Check the application logs as well asthe DB2 diag log (db2diag.log) for further details.



FMM1060E Failed to set the DB2 databaseconfiguration for database 'database alias'.

Explanation: The process was unable to set the DB2database configuration.



FMM1061E Failed to get the DB2 databaseconfiguration for database 'database alias'.

Explanation: The process was unable to get the DB2database configuration.



FMM1062E Failed to mount the database on host'hostname'. This is the output of thefailed command:output

Explanation: The process was unable to mount thedatabase instance.


User response: Examine the output of the failedcommand to get further details about the root cause ofthis failure.

FMM1063E Failed to identify the log path forpartition partition number.

Explanation: The process was unable to detect the logpath for a dedicated database partition.



FMM1064E Failed to identify the current workingdirectory.

Explanation: The process was unable to detect thecurrent working directory. An indication for that issueis that read or search permission was denied for acomponent of the directory name.


User response: Check the application logs as well asthe access rights and permissions of the workingdirectory.

FMM1065E Failed to change working directory to'directory' Error: error number: error text.

Explanation: The process was unable to change thecurrent working directory. Indicators for that issue arethat the search access is denied for the named directory,that the named directory does not exist or that thenamed directory is not a directory.


User response: Check the application logs as well asthe access rights and permissions of the new workingdirectory and whether the directory does exist.

FMM1066E Failed to create symbolic link from'directory/new instance' to 'instance' Error:error number: error text.

Explanation: The process was unable to create asymbolic link to the specified location. Indicators forthat issue are that an object of that name already exists,that insufficient access rights and privileges prevent thecreation of the link or there might be no free space lefton the file system containing the directory.


User response: Check the application logs as well asthe access rights, privileges and free space of the filesystem where the link is to be placed.

FMM1067E Entry in the storage path file 'file' is nota valid file or directory: 'directory'.

Explanation: TBD_AU



FMM1068E The clone instance on the clone systemis running.

Explanation: Actually, the clone instance on the clonesystem is running. Prior another operation can bestarted the clone instance needs to be stopped.


User response: Stop the clone instance.

FMM1069E The clone instance on the clone systemis not running.

Explanation: Actually, the clone instance on the clonesystem is not running. Prior another operation can bestarted the clone instance needs to be started.


User response: Start the clone instance.



FMM1070E Due to a mount agent is alreadyregistered on backup system 'backupsystem' additional mount agents have tohave registered using different deviceclasses.

Explanation: On the same backup system multiplemount agents can only run on that sytemsimultaneously if they are supporting different deviceclasses.


User response: Specify a not already used device classusing the '-s <device class>' option when starting themount agent on the backup system.

FMM1071E A mount agent is already registered onbackup system 'backup system' using thedevice class 'device class'. Additionalmount agents have to have registeredusing different device classes.

Explanation: On the same backup system multiplemount agents can only run on that sytemsimultaneously if they are supporting different deviceclasses.


User response: Specify a not already used device classusing the '-s <device class>' option when starting themount agent on the backup system.

FMM1072E Due to another mount agent is alreadyregistered on backup system 'backupsystem' using device class 'device class'and node(s) 'list of nodes' additionalmount agents on host 'backup system'have to have registered using differentnodes instead of 'list of nodes'.

Explanation: Multiple mount agents on the samebackup system can run simultaneously only if they aresupporting different device classes. Multiple mountagents on different backup systems using the samedevice class can run simultaneously only if they aresupporting different nodes.


User response: Specify a not already used deviceclass, whereas all participating backup system have tohave considered, using the '-s <device class>' optionwhen starting the mount agent on the backup system.If the same device class should be used on differentbackup systems specify the nodes of the backup systemusing the the '-N <comma separated list of nodes>'option when starting the mount agent on the backupsystem.

FMM1073E The clone database name database namecommandline specified with the commandline option -C does not match with thedatabase names database namecloningsection specified in theDEVICE_CLASS parameter of theCLONING section.

Explanation: The database names specified with thecommand option -C and with one of theDEVICE_CLASS profile parameters have to haveidentical.


User response: Correct either of the database names.

FMM1074E A FlashCopy clone was requested forclone database database name and deviceclass device class but the parameterCLONE_DATABASE YES is notspecified in this device class section.

Explanation: For cloning operations the IBM TivoliStorage FlashCopy Manager profile parameterCLONE_DATABASE set to YES has to have specified inthe corresponding device class section.


User response: Please use a device class that hasspecified the parameter CLONE_DATABASE YES.

FMM1075E A FlashCopy backup was requested fordevice class device class but theparameter CLONE_DATABASE YES isspecified in this device class.

Explanation: For FlashCopy backup operations thecorresponding IBM Tivoli Storage FlashCopy Managerprofile device class section must not contain theparameter CLONE_DATABASE set to YES.


User response: Please use a device class that has notspecified the parameter CLONE_DATABASE YES.

FMM1076E The target set 'target set' is used for abackup with ID 'backup ID'. It cannot beused as target set for cloning.

Explanation: Target sets used for FlashCopy backupsare not eligible for cloning.


User response: Please delete the FlashCopy backupfirst.



FMM1077E The target set 'target set' is used for aclone with ID 'backup ID'. It cannot beused as target set for backup.

Explanation: Target sets used for clones are noteligible for FlashCopy backups.


User response: Please delete the clone first.

FMM1078E The operation name cannot be starteddue to the FlashCopy clone(s) 'target set'is/are still copying data in the storagesystem from source to target.

Explanation: As long as a background copy process isrunning no other operations using the same target setscan be started.


User response: Either wait until the background copyin the storage system has finished or delete the clone(s)immediately and restart the operation.

FMM1079E The data container 'container ID' isalready subject of the operation.

Explanation: This error is not expected.


User response: Collect all IBM Tivoli StorageFlashCopy Manager logs and traces (from productionand backup system) and send them to IBM Tivolisupport.

FMM1080E The database to be cloned has to havespecified, because multiple databaseshave been found within this instance.

Explanation: If multiple database instances found onone system, the one to be cloned has to have specified.


User response: Specify the database to be cloned byspecifying the command option '-d' followed by thedatabase name.

FMM1081E Unable to detect the databaseenvironment.

Explanation: The operation requires specialenvironment settings, e.g. the database instance ownerenvironment.


User response: Please run the command as databaseinstance owner.

FMM1082E Checking the clone system status of thedatabase 'database name' failed.

Explanation: Most of the cloning functions requiresome state and integrity checks on the productionsystem as well as on the backup/clone system prior therequested operation starts. The requested operationcontinues if the integrated check routine succeeded.


User response: Check the application logs for furtherdetails.

FMM1083E Flashcopy of the database failed with rcreturn code.

Explanation: The FlashCopy backup, part of thecloning workflow, failed.



FMM1084E Database profile 'profile name' not found.

Explanation: The named database profile does notexist or is not accessible by the current user.


User response: The database profile name can bespecified in the profile for IBM Tivoli StorageFlashCopy Manager with the parameterTARGET_DATABASE_PARAMETER_FILE. Verify thatthe parameter is specified correctly and that the currentuser has read permssions. The default for the value ofthis paraemeter (if not specified in the profile for IBMTivoli Storage FlashCopy Manager) is$ORACLE_HOME/dbs/init$ORACLE_SID.ora.

FMM1085E No database control file found.

Explanation: During the creation of a database cloneno database control file was found on the flashcopiedvolumes.


User response: Ensure that at least on control filecopy resides on the same volumes as the data file orthe online redo log files.

FMM1086E Failed to start the database in nomountmode. This is the output of the failedcommand:

Explanation: The process was unable to start thedatabase instance without mounting the database files.


User response: Examine the output of the failed



command to get further details about the root cause ofthis failure.

FMM1087E Failed to rename the database. This isthe output of the failed command:'command output'

Explanation: During the rename of the database fromthe production instance name to the clone instancename an error has occured.



FMM1088E For cloning functions the name of theclone database must be specified.

Explanation: For all cloning functions the name of theclone database must be specified.


User response: Specify the option '-C <clone databasename>'.

FMM1089E For cloning functions the name of theclone instance owner must be specified.

Explanation: For all cloning functions the name of theclone instance owner must be specified.


User response: Specify the option '-u <clone instanceowner>'.

FMM1090E For the pre-processing function thepre-processing configuration file mustbe specified.

Explanation: For the pre-processing function the nameof the pre-processing configuration file is required.


User response: Specify the option '-X <configurationfile>'.

FMM1091E For the post-processing function thepost-processing configuration file mustbe specified.

Explanation: For the post-processing function thename of the post-processing configuration file isrequired.


User response: Specify the option '-Y <configurationfile>'.

FMM1092E Script terminated with errors. Returncode is: return code

Explanation: The execution of a script terminated withan error.



FMM1093E Script 'script name' could not assigned toeither shell scripts or SQL scripts.

Explanation: For FlashCopy cloning pre-processingand post-processing tasks, either shell scripts or SQLscripts can be used. These scripts will be entered eitherin the pre-processing configuration file or in thepost-processing configuration file. The identifierwhether it is a shell script or a SQL script is adedicated suffix string of the script itself. Is the suffixstring of type 'sh' then it is handled internally as a shellscript, whereas if the suffix string is of type 'sql' it ishandled internally as a SQL script. Other suffix stringsare not eligible. Such scripts will not be handled orexecuted.


User response: Check the script entries in either thepre-processing or post-processing configuration file andadjust the contained script names accordingly.

FMM1094E Script file 'script name' not found.

Explanation: A script file to be executed as part ofeither pre-processing or post-processing could not befound.


User response: Check the script entries in either thepre-processing or post-processing configuration file andadjust the contained script names accordingly.

FMM1095E The physical location of thepre-processing or post-processingconfiguration file and the script 'scriptname' is different.

Explanation: The physical location of thepre-processing or post-processing configuration file andtheir containing scripts to be executed has to haveidentically..


User response: Ensure the pre-processing orpost-processing configuration file and their containingscripts are stored under the same physical location.



FMM1096E The script 'script name' is a symboliclink.

Explanation: The named script entry in either thepre-processing or post-processing configuration file is asymbolic link, which is not allowed.


User response: Ensure that any script entry in eitherthe pre-processing or post-processing configuration fileis not a symbolic link.

FMM1097E The user 'user name' is not owner of thescript 'script name'.

Explanation: If the named pre-processing orpost-processing script is owned by the root-user,anyone can execute that script. Further, if the namedpre-processing or post-processing script is not ownedby the root-user, it can only by executed by the userwho owns that script.


User response: Check the ownership of the namedscript and if necessary adjust them accordingly.

FMM1098E The user 'user name' configured for script'script name' is actually not applied onthe system.

Explanation: The named user, who is configured toexecute the named script does not exist on the system.


User response: Check the applied user on the systemand either update the pre-processing or post-processingconfiguration for a different existent user or add theconfigured user credentials to the system.

FMM1099E The pre-processing or post-processingconfiguration file 'file name' is not found.

Explanation: The named pre-processing orpost-processing configuration file is containing thescripts to be executed could not be found on thebackup/clone system, where the pre-processing orpost-processing will be executed.


User response: Check the name of the specifiedpre-processing or post-processing configuration file andcheck whether it exists on the backup/clone system.

FMM1122E The pre-processing or post-processingconfiguration file 'file name' does notcontain any data record.

Explanation: The named pre-processing orpost-processing configuration file is empty whichmeans it does not contain any entry to be processed.


User response: Either specify the correctpre-processing or post-processing configuration file oradd one or multiple valid data records (scripts) to it.

FMM1123E Failed to open the database: output

Explanation: After creating a database clone IBMTivoli Storage FlashCopy Manager was not able toopen the database.



FMM1154E The only valid profile values for thekeyword 'keyword' are 'val1' and 'val2'.

Explanation: Invalid values were given in the profilefor the specified keyword.


User response: Change the profile so that therecommended values for the specified keyword arevalid.

FMM1158T Service service not completed

Explanation:

System action:

User response:

FMM1161E Failed to recover the database. This isthe output of the failed command:

Explanation: The recovery of the database has failed.



FMM1162E Failed to determine the online redo logs.Output of the failed command: output

Explanation: IBM Tivoli Storage FlashCopy Managerfailed to detect the names of the online redolog files ofthe database.





FMM1163W Script terminated with warnings.

Explanation: The execution of a script terminated withone or multiple warnings. The overall operation mightbe finished successfully. Nevertheless, to avoidsubsequent more critical issues it is highlyrecommended to check and resolve the root cause ofthe warning to guarantee the operational consistency ofthe system in the future.



FMM1164I Renaming file system <old file systemname> to <new file system name>

Explanation: The named file system is going to berenamed.



FMM1165I Recovering the database database name.

Explanation: The named database is going to berecovered.



FMM1166I Switching LOGRETAIN and USEREXIToff for database database name.

Explanation: The log archiving for the nameddatabase is switched off.



FMM1167I Creating relocate configuration file fordatabase database name.

Explanation: The relocate configuration file requiredas input for the relocate database command is going tobe created for the named database.



FMM1168I Creating the storage path directories fordatabase database name.

Explanation: The storage paths for the nameddatabase are going to be created.



FMM1169I Relocating database partitions partitionlist of database database name.

Explanation: The named database partitions of thespecified database are going to be relocated.



FMM1170I Cloning database database name.

Explanation: The named database is going to becloned.



FMM1171I No rename required.

Explanation: The original database name and thecloned database name is equal. Therefore, no re-namingof the cloned database name is required.



FMM1172I Preparing recovery of database databasename.

Explanation: The named cloned database is going tobe prepared for the recovery.



FMM1173I Renaming database old database name tonew database name.

Explanation: The cloned database is going to berenamed.



FMM1174I Checking the clone system status of thedatabase database name.

Explanation: The system status of the named databaseis going to be checked, e.g. whether the database isrunning.



FMM1175I Successfully checked the clone systemstatus of the database database name.

Explanation: The system status of the named databasewas checked successfully. Operation can continue.

FMM1163W • FMM1175I




FMM1176I Restore control file file name.

Explanation: The named control file is going to berestored.



FMM1177I Performing media recovery.

Explanation: A media recovery is going to be started.



FMM1178I Opening the clone instance instancename.

Explanation: The clone instance is going to be opened.



FMM1179I Function 'function name' does notconsider the post-processingconfiguration file.

Explanation: The post-processing configuration file isnot considered, e.g. if a pre-processing operation wasstarted.



FMM1180I Function 'function name' does notconsider the pre-processingconfiguration file.

Explanation: The pre-processing configuration file isnot considered, e.g. if a post-processing operation wasstarted.



FMM1181I Executing script type script 'script name'.

Explanation: The named script is going to beexecuted. The type of the script is of either 'shell' or'SQL'.



FMM1182I Script terminated successfully.

Explanation: The script has terminated successfully.



FMM1183E The parameter 'keyword' must have alength of 'length' characters. "

Explanation: An invalid length was specified in theprofile for the value of the specified keyword.


User response: Change the specified profile parameterto an allowed length.

FMM1200E Profile parameter 'keyword' is set to YESbut freeze/thaw is not supported by theunderlying file system.

Explanation: The freeze and thaw operation is notsupported by the used file sytem but the profileoptions specify that it be used.


User response: Change your profile so that it does notuse freeze and thaw.

FMM1201E There are no Tivoli StorageManager–Servers available.

Explanation: Data Protection for SAP cannot locate aTivoli Storage Manager server. This may be due to aconfiguration problem or to a problem while trying toconnect to the Tivoli Storage Manager server. Mostprobably, a preceding error message points to the causeof the problem.

System action:

User response: Look for and respond to precedingerror messages. You may also want to check the DataProtection for SAP profile and the IBM Tivoli StorageManager client options and client system options files.

FMM1202E You must specify eitherMAX_SESSIONS, or all three specificsession options(MAX_ARCH_SESSIONS,MAX_BACK_SESSIONS, andMAX_RESTORE_SESSIONS).

Explanation: Information on the number of TivoliStorage Manager client sessions to be established byData Protection for SAP is missing from the profile.

System action:

User response: In the Data Protection for SAP profile,either specify a value for keyword MAX_SESSIONS, orspecify values for the three specific session parameters



(MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, andMAX_RESTORE_SESSIONS). Any of the specificoptions can be specified in combination withMAX_SESSIONS. Then, it overrides the value ofMAX_SESSIONS for the specific function.

FMM1203E Not enough sessions available (sessionsrequired and max_sessions available).

Explanation: The sum of available sessions specifiedin the various server statements (parameter SESSIONS)does not cover the required number of sessions(parameter MAX_SESSIONS).

System action:

User response: Change the values of thecorresponding parameters in the Data Protection forSAP profile, so that the condition mentioned in theexplanation is fulfilled.

FMM1205E If you want num_redoREDOLOGCOPIES you should give meat least num_mc different ArchiveManagement Classes.

Explanation: Data Protection for SAP requires that thenumber of different Archive Management Classes(parameter BRARCHIVEMGTCLASS) on the TivoliStorage Manager servers is equal to or greater than thenumber of redo log or log file copies (parameterREDOLOG_COPIES).

System action:

User response: Define at least as many differentArchive Management Classes as log file copiesrequested.

FMM1206W If you want num_redoREDOLOGCOPIES you should give meat least num_mc different ArchiveManagement Classes.

Explanation: The message appears during aBRBACKUP run. A BRARCHIVE run afterwards wouldfail.

System action:

User response: Define at least as many differentArchive Management Classes as log file copiesrequested.

FMM1207E Directory backup not supported.

Explanation: This option is not yet available.

System action:

User response: Wait for a future release of DataProtection for SAP, which supports this option.

FMM1208W Retrying object: 'file name'. Retry count:[retry_num].

Explanation: An error occurred while processingobject file name. Data Protection for SAP is repeating theaction according to the number of retries specified inthe profile. retry_num is the current retry count.

System action:

User response: If the problem persists check for andrespond to preceding error messages.

FMM1209E Object not found or not accessible:'objectname'.

Explanation: The object cannot be located.

System action:

User response: The backup integrity is affected.Contact SAP or IBM Support.

FMM1210E Input file not found or not accessible:'file name'.

Explanation: Data Protection for SAP cannot locate thetemporary file named. This file contains the list ofOracle objects to be backed up or restored. It is passedto DP for SAP by one of the BR*Tools utilities.

System action:

User response: Ensure that you have the correctversion of BR*Tools installed. For details, check withthe release notes (RELNOTE).

FMM1211E There is something wrong with yourCONFIG_FILE 'file name'.

Explanation: There is a problem with your DataProtection for SAP configuration file setup.

System action:

User response: Check the file permission and the filename specified in the Data Protection for SAP profilekeyword CONFIG_FILE.

FMM1212W The file 'file name' is not found in themanual sorting file.

Explanation: The file you want to back up was notfound in the manual sorting file.

System action:

User response: Check and correct the manual sortingfile so that it contains all the files you are backing up.



FMM1213E The value 'wrongvalue' of the keyword'keyword' is not allowed if'dependentkeyword' is set to'dependendvalue'. "

Explanation: The profile keyword and value dependon another profile keyword and value. The dependenyis broken and needs to be fixed.


User response: Change the profile value of thespecified keyword.

FMM1214E TSM Error for session to server servername: error text

Explanation: An error occurred from one of the TSMServers.

System action: Processing for the IBM Tivoli StorageManager Server specified stops. Processing on otherservers continues.

User response: Check the error text and IBM TivoliStorage Manager Server name stanza in the profile filefor the server name specified in the error.

FMM1215I Average transmission rate was gb perhour GB/h (mb per second MB/sec).

Explanation: The average transmission rate isdisplayed.

System action:


FMM1216E There are no backup managementclasses available.

Explanation: The BRBACKUPMGTCLASSES you havespecified in your init<SID>.utl file are not correct.

System action:

User response: Check the management classes on theTSM server and specify correct ones.

FMM1217E There are no archive managementclasses available.

Explanation: The BRARCHIVEMGTCLASSES youhave specified in your init<SID>.utl file are not correct.

System action:

User response: Check the management classes on theTSM server and specify correct ones.

FMM1218E Environment variable TEMP not set

Explanation: The required environment setup isincomplete.

System action:

User response: Set the environment variable TEMPand try again.

FMM1219E The paths of the disks found in theASM instance indicate that the OracleASMLib is not used. This setup iscurrently not supported.

Explanation: The ASM instance has not been set upwith ASMLib. This environment is currently notsupported.


User response: Set up your ASM instance with disksmanaged by ASMLib.

FMM1220E The execution of the system command'syscommand' ended with a return codeother than 0. The output of thecommand was: 'commandoutput'.

Explanation: A system command returned a non-zeroreturn code.



FMM1221E The parameter 'keyword' must have avalue other than 'value' to be able toexecute a mount operation.

Explanation: The mount operation cannot be executedwith the current settings in the profile. Please modifyyour profile.


User response: Modify your profile according to themessage.

FMM1222E Version mismatch error. Please checksetup (version_1:version_2).

Explanation: Different components with inconsistentversions are used.

System action:

User response: Check your setup or contact IBMSupport.



FMM1223W A Problem occurred during send ofperformance data to the AdministrationAssistant.

Explanation: There was a problem sending theperformance data to the Administration Assistant overthe network.

System action:

User response: Check your setup or contact IBMSupport.

FMM1224W Unable to initialize connection toAdministration Assistant.

Explanation: No operational data could be sent to theAdministration Assistant during database backup orrestore.

System action:

User response: Check the logs for further informationand try again.

FMM1227I Average compression factor was number.

Explanation: The data transferred had beencompressed by the factor number.

System action:


FMM1228W Server server name can not be used withpassword access method GENERATE inthis environment. The process isrunning with user ID userid but theeffective user ID is userid effective.

Explanation: The user ID and the effective user ID ofthe process are different. In order to utilize thepassword access method GENERATE the IDs must beequal.

System action:

User response: Under UNIX and Linux, change thevalue of the "PASSWORDACCESS" parameter in filedsm.sys from 'generate' to 'prompt'.. Under Windows,change the value of the "PASSWORDACCESS"parameter in file server name.opt from 'generate' to'prompt'.

Reset the node's password on the Tivoli StorageManager server.

In an Oracle environment, run

backint -f password

In a DB2 environment run

backom –c password

This will prompt you for the TSM password and thenwill encrypt it in the Data Protection for SAP configfile.

This step needs to be repeated each time yourpassword expires.

FMM1229E Value for parameter BUFFSIZE (actualcur_number, maximum max_number) istoo large for BUFFCOPY modePREVENT.

Explanation: To utilize the BUFFCOPY modePREVENT the value for the parameter BUFFSIZE mustnot be larger than max_number.

System action:

User response: In the Data Protection for SAP profile,specify a BUFFSIZE less or equal to max_number if youneed to prevent copying buffers when passing databetween Tivoli Storage Manager components. If youneed large buffers you can set option BUFFCOPY toSIMPLE or AUTO. As a consequence, buffers arecopied when data is passed between Tivoli StorageManager components.

FMM1230E The following file was not processed:path.

Explanation: The operation was terminated due to aprevious error. As a consequence, the file named couldnot be processed. The cause of the error should befound in an earlier message.

System action:

User response: Check for and respond to precedingerror messages.

FMM1231E Maximum number of retries for filefilename exceeded.

Explanation: The number of retries configured in theprofile keyword 'FILE_RETRIES' for the named filewere reached.

System action:

User response: Check the logs for further informationabout the root cause of the retries. Resolve these issuesand perform the operation again.

FMM1232I Executing operation 'operation' on host'host name'.

Explanation: The specified operation on the namedhost was started.





FMM1233I Operation 'operation' completed.

Explanation: The specified operation completed.



FMM1234E The directory 'directory' containing theXPYV components of the installation ismissing.

Explanation: A required component could not befound. The installation seems to be corrupted.


User response: Reinstall. Your installation seems to bedamaged.

FMM1235E Logical volume 'logicalvolume' notavailable on system.

Explanation: A required logical volume was not foundon the system.



FMM1236E The section DB2STANDBY is missingfrom the profile.

Explanation: To perform a DB2 standby backup orrestore functions the section DB2STANDBY must beadded to the IBM Tivoli Storage FlashCopy Managerprofile.


User response: Add the section DB2STANDBY to theIBM Tivoli Storage FlashCopy Manager profile.

FMM1237E Unable to perform mount request. Therequested mount point 'mountpoint' isalready in use.

Explanation: The attempt to mount a volume failedsince the required mount point is already in use.


User response: Unmount any filesystem that iscurrently mounted at this mountpoint. Then retry.

FMM1239W Logical volume 'logicalvolume' of volumegroup 'volumegroup' contains unmountedfilesystem.

Explanation: This warning lists all filesystems of thevolume groups contained in the backup that arecurrently not mounted. In case of a restore thesefilesystems will be overwritten and all its data isreverted to the point in time when the backup wastaken.



FMM1240E Unable to mount the followingfilesystems: mointpoints

Explanation: The listed filesystem could not bemounted.


User response: Check why the listed filesystems couldnot be mounted, then issue the command again.

FMM1241E Unable to unmount the followingfilesystems: mointpoints

Explanation: The listed filesystem could not beunmounted.


User response: Check why the listed filesystems couldnot be unmounted, then issue the command again.

FMM1242E Error while parsing the profile: It is notallowed to have an ORACLE sectionwithout a CLIENT section.

Explanation: It is not allowed to have an ORACLEsection without a CLIENT section.


User response: Just specify the missing profilekeyword.

FMM1243E Only a single device class name isallowed for the profile parameterparameter in combination with thekeyword keyword.

Explanation: The profile parameter 'DEVICE_CLASSdevice_class_name USE_FOR_CLONING dbname' inthe CLONING section can only be assiged to onedevice class name. This is different to the usage of theDEVICE_CLASS parameter in the CLIENT sectionwhere a list of device class names can be specified. ForCloning this is not allowed.


User response: Only use a single device class namewith the DEVICE_CLASS parameter in the CLONINGsection.

FMM1244E The DB2 alias 'alias' could not be foundin the database directory. Please checkthe value of the profile parameterparameter.

Explanation: The DB2 alias specified with the profileparameter DB2_ALIAS in the DB2STANDBY sectioncould not be found in the DB2 database directory on



the DB2 HADR standby system.


User response: Please verify that the DB2 aliasspecified with the profile parameter DB2_ALIAS in theDB2STANDBY section can be found in the DB2database directory DB2 HADR standby system. Use the'db2 list db directory' command to list the catalogeddatabase aliases.

FMM1245E There is no mount agent suitable forcloning with device class 'device class'started. Function cloning requires adedicated mount agent that was limitedto a specific device class using theoption '-s <device class>'.

Explanation: Function cloning requires a dedicatedmount agent that was limited to a specific device classusing the option '-s <device class>'.


User response: Make sure that mount agent wasstarted with option '-s <device class>'.

FMM1246E The database name has to havespecified, because multiple databaseshave been found within this instance.

Explanation: If multiple databases found in onedatabase instance, the one for that a snapshot backupshould be restored or deleted has to have specified.


User response: Specify the database name of thedatabase for that a snapshot backup should be restoredor deleted by specifying the command option '-d'followed by the database name.

FMM1247E A FlashCopy Backup is not allowedbecause FlashCopy Clone(s) 'clones'is/are active with FlashCopy TypeNOCOPY.

Explanation: You have created a FlashCopy Clonewith the parameter ALLOW_NOCOPY_FLASHCOPYset to YES in the CLONING device class. With thissettings it is no longer allowed to perform FlashCopyBackups on the same SVC cluster.


User response: If you want to start a new FlashCopyBackup on the same SVC cluster it is required to deleteall FlashCopy Clone(s) that were created withFlashCopy Type NOCOPY first.

FMM1248E A FlashCopy Clone with FlashCopyType NOCOPY is not allowed becauseFlashCopy Backup(s) 'backups' is/areactive.

Explanation: You want to create a FlashCopy Clonewith the parameter ALLOW_NOCOPY_FLASHCOPYset to YES in the CLONING device class. With thissettings it is not allowed to have FlashCopy Backupson the same SVC cluster.


User response: If you want to start a new FlashCopyClone with the parameterALLOW_NOCOPY_FLASHCOPY set to YES in theCLONING device class it is required to delete allFlashCopy Backup(s) on the same SVC cluster first.

FMM1249E The LUN's of the datastores requestedfor backup are spread across multiplestorage subsystems. IBM Tivoli StorageFlashCopy Manager can support LUNsfrom only one storage subsystem.

Explanation: The virtual machines selected for backupare contained in datastores that are spread acrossmultiple storage subsystems.


User response: Ensure the datastores and virtualmachines which have been selected for backup are allcontained on one storage subsystem.

FMM1250I The 'user name to log-in to the file server'ID is connecting to the following fileserver: 'remote hostname of the file server' .

Explanation: For ID used to log on to the file server,the name is provided. In addition, the remote hostnameof the file is provided. These values are stored in thefollowing parameters for the configuration profileDEVICE_CLASS section:COPYSERVICES_PRIMARY_SERVERNAME andCOPYSERVICES_USERNAME



FMM1251I A snapshot is taken for the followingvolume: 'name of the volume'.

Explanation: The volume identified in this message isgoing to be backed up with a snapshot. If multiplevolumes are going to be backed up with snapshots,each volume is identified in separate messages.





FMM1252I Deleting snapshot 'name of the snapshot todelete' for volume 'name of the volume'

Explanation: The snapshot that has been identified isgoing to be deleted because the corresponding backuphas been deleted.



FMM1253E The 'target instance uuid' target instanceUUID that is specified in the input filecannot be found or the UUID isassigned to a template. Edit the inputfile and specify a valid target instanceUUID.

Explanation: The target instance UUID specified in theinput file was not found.


User response: Specify a valid target instance UUID.

FMM1254I The 'snap name' snapshot of the fileset'fileset name' in the 'file system device name'file system was created.

Explanation: A GPFS™ snapshot with the specifiedparameters was successfully created.



FMM1255E The process cannot continue. Revertingchanges.

Explanation: An error occured. The changes that canbe undone will be reversed now.



FMM1256I The 'snap name' snapshot of the fileset'fileset name' in the 'file system device name'file system was restored.

Explanation: The GPFS snapshot with the specifiedparameters was successfully restored.



FMM1257E The file server does not recognize thevolume with the following serialnumber: 'identifier'.

Explanation: When the software attempted to back upthe files, the file server specified with theCOPYSERVICES_SERVER_NAME parameter did notfind the volume with the serial number identified in

the error message. The file server that hosts the volumeis specified with the COPYSERVICES_SERVER_NAMEparameter in the DEVICE section. A possibleexplanation is that the volume is stored locally and noton the NetApp or N-Series file server specified with theCOPYSERVICES_SERVER_NAME parameter.


User response: Verify that the file server that isspecified in the configuration is the file server thathosts the volumes that are used for the currentoperation. To check the file server specified in theconfiguration, start the setup script or open the profileconfiguration file. In the DEVICE section, theCOPYSERVICES_SERVER_NAME parameter is used tospecify the file server.

FMM1258I The following volume is offline: volumename

Explanation: Because the volume is already offline,the volume cannot be taken offline.


User response: There are no additional tasks or stepsto complete.

FMM1259I The following clone volume alreadyexists: volume name

Explanation: Because the clone volume already exists,the clone volume cannot be created.



FMM1260E The GPFS file system 'device name' iscurrently mounted on the system at:'current mount point'. The GPFS filesystem must be mounted at: 'defaultmount point', the default mount point.

Explanation: Only the default mount points aresupported for GPFS snapshot and restore functions.

System action: The operation stops and cannotcontinue until this error is resolved.

User response: To resolve this issue, mount the GPFSfile system without specifying the mount pointargument. The GPFS file system is mounted at thedefault mount point. After you resolve this problem,run the backup again.

FMM1261E Key value set for undefined key columnkey_value. Command was: command

Explanation: The call to request output data ofcommand 'command' was set up incorrectly. If a keyvalue is specified a key column must be defined, too.



System action: The operation stops.


FMM1262W The snapshot snapshot_name of the filesystem filesystem_name cannot be deletedbecause the file system is not known tothe local cluster.

Explanation: IBM Tivoli Storage FlashCopy Managercannot delete the snapshot of the file system nordetermine whether the snapshot is still availablebecause the file system is not known to the localcluster.

System action: The meta-information on this snapshotis kept in the repository. The snapshot is not listed inthe list of available snapshots unless the force option isissued with the query command.

User response: To remove the record from therepository without mounting the file system in the localcluster use the delete-force option when issuing thedelete request.

FMM1263W The snapshot snapshot_name of the filesystem filesystem_name cannot be deletedbecause the file system is not mounted.

Explanation: IBM Tivoli Storage FlashCopy Managercannot remove the snapshot from the file system nordetermine whether the snapshot is still available in thefile system because the file system is not currentlymounted in the local cluster.


User response: Issue the mount command to mountthe file system. The device agent removes the snapshotfrom both the file system and the repository.

To remove the record from the repository withoutmounting the file system, use the delete-force optionwhen issuing the delete request.

FMM1264W The snapshot snapshot_name of the filesystem filesystem_name cannot be deleted.Error information: error_information

Explanation: A request to delete the snapshotsnapshot_name of the file system filesystem_name cannotbe completed. An error occurred when processing thedelete command.


User response: Resolve any problems indicated by theerror_information error. After you resolve the issue, the

device agent removes the snapshot from both the filesystem and the repository.

FMM1265W The filesystem_name file system isunknown to the local cluster. Therefore,IBM Tivoli Storage FlashCopy Managercannot run the reconciliation process forthe following snapshots: list_of_snapshots

Explanation: IBM Tivoli Storage FlashCopy Managercannot find snapshots of the filesystem_name file systembecause this file system is not known in the localcluster.

System action: The meta-information for thesnapshots listed are stored in the repository.

User response: To remove the record from therepository without mounting the file system, use thedelete-force option when issuing the delete request.

FMM1266W The filesystem_name file system is notmounted. Therefore, IBM Tivoli StorageFlashCopy Manager cannot run thereconciliation process for the followingsnapshots: list_of_snapshots

Explanation: IBM Tivoli Storage FlashCopy Managercannot find snapshots of the filesystem_name file systembecause the file system is not currently mounted in thelocal cluster.

System action: The meta-information for thesnapshots listed are stored in the repository.

User response: Issue the mount command to mountthe file system so that the reconciliation process can beperformed.

To remove the record from the repository withoutmounting the file system, use the delete-force optionwhen issuing the delete request.

FMM1267W IBM Tivoli Storage FlashCopy Managercannot determine whether the snapshotsnapshot_name snapshot of the filesystem filesystem_name is still available.Error information: error_information

Explanation: During the reconciliation process, anerror_information error occurred when trying todetermine whether the snapshot_name snapshot is stillavailable in the filesystem_name file system.

System action: The meta-information for this snapshotis kept in the repository.

User response: Resolve any problems indicated by theerror_information error. After you resolve this issue, thereconciliation will be run.



FMM1268E A relative file name 'file name' was foundin the infile. Relative file names are notsupported.

Explanation: Replace all relative file names withabsolute file names in the infile.


User response: Verify that only absolute file names arespecified in the infile.

FMM1269E For GPFS snapshots, the value parametervalue is not valid for the parameter nameparameter.

Explanation: If IBM Tivoli Storage FlashCopyManager is configured for the General Parallel FileSystem (GPFS), the current value specified for theparameter name parameter is not allowed.

System action: If this condition is detected during abackup operation, the operation stops.

If this condition is detected while configuring IBMTivoli Storage FlashCopy Manager, you are promptedfor a different value of the parameter name parameter.

User response: Specify a different value for theparameter name parameter.

If the parameter name parameter is not specified in yourprofile, and the default value is used, explicitly set it toa value different from parameter value.

FMM1270I The following volume is mapped toinitiator group: volume name.

Explanation: Because the volume is already mapped, anew mapping is not created.



FMM1271I The following volume is online: volumename

Explanation: Because the volume is already online, noactions taken and processing continues.



FMM1272E The following VMs listed in the instantrestore input file are not part of thebackup: vms_in_infile

Explanation: The instant universal unique identifier(UUIDs) listed in the instant restore input file are notpart of the backup.


User response: Use only instant UUIDs in the inputfile that are part of the backup.

FMM1273E The source volume with serial numbercmd is not attached to any known ESXhosts.

Explanation: The specified physical volume wasfound during the FlashCopy backup as part of the datastore volume on the production system. Now, duringthe instant restore, the volume is no longer found onany of the ESX hosts.


User response: Attach the missing volume to thecorrect ESX host on the storage system.

FMM1274E The file system filesystem_name cannot bemounted. If the file system is to bemounted remotely, ensure that themounting cluster has the correctpermissions to mount the file system.Additional information:command_and_command_output

Explanation: The file system specified cannot bemounted. Both the system command that is used andthe command output are listed.


User response: When you mount a file systemremotely, check that the cluster that is to mount the filesystem is authenticated with the owning cluster(command: mmauth add). In addition, ensure that thecorrect permissions to mount the file system aregranted (command: mmauth grant). In DB2 pureScale®

environments, read/write permission is required.Examine the command output to determine the causeof the problem, resolve the problem, and try theoperation again.

FMM1275E The ' vm_name' virtual machine islocated on the following data stores :list_of_datastors. In the input file not allof these data stores were specified. Youmust specify all listed data stores in theinput file or exclude this virtualmachine so that the instant restore cancontinue.

Explanation: The virtual machine is located on morethan one data store. Not all of the data stores are listedin the instant restore input file.


User response: Add the missing data stores to theinstant restore input file or exclude the VM from theinstant restore.



FMM1276E Cluster cluster_name cannot mount thefile system filesystem_name in read/writemode. If the file system is to bemounted remotely, ensure that themounting cluster has the correctpermissions to mount the file system inthe mode requested.

Explanation: The file system specified cannot bemounted in read/write mode.


User response: When you mount a file systemremotely, check that the cluster that is to mount the filesystem has been granted sufficient permissions tomount the file system in read/write mode (command:mmauth grant). Resolve the problem and try theoperation again.

FMM1278W The power on VM task for VM 'vmname'failed.

Explanation: The VM was selected to power on afterinstant restore but a the power on VM task failedduring execution.


User response: power on the Virtual Machinemanually

FMM1279E The 'volume name' LUN cannot bemapped by using the initiator group'initiator group': error message

Explanation: The mapping cannot be created becausethe initiator group does not exist.


User response: Ensure that the initiator group existson the storage system and try the operation again.

FMM1280E The mapping for the 'volume name' LUNcannot be removed by using theinitiator group 'initiator group': errormessage

Explanation: The initiator group that is used toremove the mapping must be available and fullyoperational.


User response: Ensure that the initiator group existson the storage system and is fully operational.

FMM1283E The file file name is listed in the backupinfile but is not on a GPFS file system.The backup operation cannot continue.

Explanation: If IBM Tivoli Storage FlashCopyManager is configured for the General Parallel File

System (GPFS), the files that are listed in the backupinfile must be on a GPFS file system.

System action: If a differnce between the backup infileand the GPFS file system is detected during a backupoperation, the backup operation stops.

User response: Correct the infile list by removing anyincorrect file names, and try the backup operationagain.

FMM1284E The operation instant restore cannot bestarted for backup with id 'backupid' dueto the FlashCopy backup is still copyingdata in the storage system from sourceto target.

Explanation: As long as a background copy process isrunning it is not possible to do an instant restore forthis backup.


User response: Wait until the background copy in thestorage system has finished and restart the operation.

FMM1501E Only one LUN per ASM failure group isallowed with DS8000 storage. 'LUNcount' LUN's have been found in failuregroup 'failure group name' of diskgroup'diskgroup name'.

Explanation: For DS8000, only a single LUN perfailure group is allowed. The specified failure groupconsists of more than one LUN. This environment isnot supported.


User response: Reduce the number of LUN's in eachfailure group to one.

FMM1502E Oracle ASM with SVC is not supportedwith the setting 'profile_value' for theprofile parameter 'profile_param'.

Explanation: Preassigned volumes cannot be usedwith SVC and Oracle ASM.


User response: Specify the name of the backup serveras defined in the storage subsystem for the specifiedprofile parameter.

FMM1503E The single disk restore operation to thesource virtual machine 'vm name' withinstance UUID 'source vm instance uuid' isnot possible since 'number snapshots'VMware snapshots have been found onthe source virtual machine but none areallowed.

Explanation: The single disk restore operation to the



specified virtual machine is not possible since VMwaresnapshots have been found for this virtual machine.This virtual machine must not have any snapshots forthe single disk restore operation.


User response: Remove the VMware snapshots fromthe specified virtual machine.

FMM1504E The single disk restore operation of thevirtual machine 'vm name' with instanceUUID 'source vm instance uuid' is notpossible since 'number snapshots'VMware snapshots have been found forthis virtual machine as it is contained inthe backup but none are allowed.

Explanation: The single disk restore operation of thespecified virtual machine is not possible since VMwaresnapshots have been found for this virtual machine.This virtual machine must not have any snapshots atthe backup point in time to allow a single disk restoreoperation to the source virtual machine.


User response: If a single disk restore to the sourcevirtual machine should be performed with this virtualmachine a new backup needs to be created. Thespecified virtual machine is not allowed to haveVMware snaphots during the creation of that backup.

FMM1505E Operation aborted because a differentoperation by this database client isalready running.

Explanation: Different concurrent operations of thesame type were started for the same database. This isnot supported. The current operation is aborted. Thismessage is also issued when a cooperative operation oftwo or more participating partitions was started, butthe profile settings used for the various partitions donot match.

System action:

User response: Wait until the currently runningoperation has ended and try again. Make sure thatmultiple operations are not started concurrently for adatabase. If this is a cooperative operation with two ormore participating partitions, check that the profilesettings of the various partitions (for example,DEVICE_TYPE, MAX_VERSIONS, etc.) do not differ. Ifthey do, fix the profile settings, cancel the currentoperation, and start the operation again. Also,investigate the possibility of sharing the same profileamong all partitions.

FMM1506E Error: 'description' on host 'hostname'while executing command 'command'.

Explanation: The system tried to execute thecommand cited. During execution, an error occurred.The output received from the command shell is listedfollowing the message.

System action:

User response: Determine the cause of the problemfrom the command and the output listed in themessage, and resolve the problem.

FMM1507E The process needs to run with rootauthority.

Explanation: The current process requires rootauthority.

System action:

User response: Start the process under an accountwith root authority.

FMM1508E The service service_name has terminateddue to a previous error. Please check alllogs for additional information.

Explanation: The cited service is no longer available.

System action:

User response: Check the appropriate logs for thecause of its termination.

FMM1509E Authentication failure. The passwordspecified is not authorized for accessingcomponent. Please verify that thepasswords specified in the passwordfiles on the different production andbackup/cloning systems are correct.

Explanation: To access the named component, apassword is required. However, the password providedcould not be verified.

System action:

User response: Make sure that the password files usedby the different components of the system match.

FMM1510I New connection received from hosthostname.

Explanation: The server received a new connectionrequest.

System action:




FMM1512E An error occurred during shutdown:Error information

Explanation: During shutdown of the component, aproblem occurred. The error information is given.

System action:

User response: Resolve the problem indicated by theerror information.

FMM1513I *****> Database client connected:instance instance, databasedatabase_namepartition_numbernodename

Explanation: This message follows a messageFMM1511I and indicates the connection of one of thedatabase clients taking part in the operation. Adatabase client is an instance of the snapshot backuplibrary representing a single partition of the database.

System action:


FMM1514I *****> Device client connected.

Explanation: This message follows a messageFMM1511I and indicates the connection of one of thedevice clients taking part in the operation. A deviceclient is an instance of the device agent for the storagedevice.

System action:


FMM1515I Client is logging to file_name

Explanation: The client's log messages are written tothe indicated file.

System action:


FMM1516I Deleting container container.

Explanation:

System action:

User response:

FMM1517I Deleting target data container definedby container_description.

Explanation: The data in the container indicated isremoved.

System action:


FMM1518E Internal error: The system is trying touse the same device agent, although thesynchronization mode is notPARALLEL.

Explanation: The system has been told to use thesame device agent for multiple database clients, but thedatabase indicated serial synchronization mode. Thissetup is not supported.

System action:

User response: Contact your IBM support personnel.

FMM1519E A failure occurred during initializationof one or more of the nodesparticipating in this operation. Pleasecheck the logs for more information.

Explanation: Some problem occurred during theinitialization of a new operation. The problem may bewith any component required for this operation.

System action:

User response: Check the acsd log file for messagesFMM1515I to determine the log file names of theparticipating agents. Check the log files of eachcomponent for the cause of the problem.

FMM1520E Volume volume_name is shared acrosspartitions. Volume sharing is notallowed.

Explanation: At least two partitions own data residingon the volume indicated. This setup is not supported.

System action:

User response: With the current disk layout of thedatabase, the requested function cannot be used. If youwant to use the function, change the disk layout of thedatabase so that each data volume is dedicated to apartition.

FMM1521I Retaining number backups

Explanation: When enforcing profile parameterMAX_VERSIONS, the indicated number of backups iskept.

System action:


FMM1522E The requested meta–information(subject="description") is not available.

Explanation: Some meta–information about eachbackup is stored in the repository. An error occurredwhen trying to retrieve part of this information.

System action:




FMM1523W Warning: The following containers werereused without being explicitly released:description

Explanation: The containers defined by thedescription are used by the current backup. They wereused before by a different backup. This message isexpected in SAN environments where data containersare usually kept until they are reused. In this case, thismessage does not indicate a problem.

System action:


FMM1525E The process service_name is in aninconsistent state. Please check forprevious errors and restart the processafterwards.

Explanation: The process indicated cannot continuewith inconsistent data.

System action:

User response: Check the logs for messages pointingto the cause of the inconsistency. After resolving anyproblems, restart the process.

FMM1526E A configuration file (profile) must beprovided.

Explanation: An operation was started withoutproviding a profile.

System action:

User response: Check the user documentation on howto provide the profile to the current process. Start theprocess again using a valid configuration file.

FMM1529E The device 'device_type' is not supportedby the wizard.

Explanation: The device type represents a certain typeof storage device. While using the setup wizard, adevice type was entered that is not supported by thecurrent version of the wizard.

System action:

User response: Refer to your user documentation for alist of the device types that are supported by default.Specify one of the supported types.

FMM1530E Failed to launch the device agent fordevice_type. Please consult your userdocumentation to make sure that allrequirements for the specified deviceare met.

Explanation: The system was unable to launch theappropriate device agent for the type indicated becausesome of its requirements are not met.

System action:

User response: Refer to your user documentation andmake sure that the system is set up correctly for thespecified device type.

FMM1534E Unexpected version actual_version of therepository located at path. Expectedversion: supperted_version

Explanation: The server located the repository in thepath indicated. However, the version of the repositorylocated on disk does not match the current version ofthe server.

System action:

User response: Make sure to use the correct instanceof the server. Ensure that the path of the repository wasspecified correctly. Refer to the release notes for a list ofpossible incompatibilities.

FMM1535E Unexpected characteristics(bitwidth=bitwidth repository) of therepository located at path. Expectedbitwidth: bitwidth expected

Explanation: The repository located in the pathindicated was saved to disk using a bit width differentfrom the bit width the server is using to load therepository.

System action:


FMM1536E The repository located at path is notvalid.

Explanation: A repository could not be found at thelocation indicated by path.

System action:

User response: Ensure that the path of the repositorywas specified correctly. Do not edit any files in therepository path.

FMM1537E The repository located at path waswritten with an incompatible protocol(protocol_version incompatible). Expectedprotocol: protocol_version expected

Explanation: The repository found at the locationindicated was written to disk using the protocolversion named. However, the server currently supportsthe expected protocol version.

System action:

User response: Ensure that the path of the repository



was specified correctly. Do not edit any files in therepository path.

FMM1538E Unexpected repository type. The path'path' does not point to a repository oftype "protocol_type".

Explanation: The repository located in the pathindicated was written to disk using a protocol differentfrom the protocol supported by the server process.

System action:


FMM1539E Root privileges required. Could notchange user ID to root.

Explanation: The requested operation requires rootprivileges. However, the process could not acquirethem.

System action:

User response: Make sure the appropriate privileges(s–bit) are granted to the executable.

FMM1540E /etc/inittab entries are limited to 127characters. Please consult your userdocumentation for information onmanually completing the installationprocedure.

Explanation: The command line generated by thesetup function exceeds 127 characters. This situationrequires user intervention. The setup function did notupdate /etc/inittab.

System action:

User response: Refer to your user documentation forinformation on what entries to add to /etc/inittab.

FMM1541E /etc/inittab was not updated becausesome of the processes have apparentlybeen added. Please re–run the setupafter calling the setup script with option'–a disable' if you want to change to astandard setup.

Explanation: During the automatic setup, entries forthis product were detected in /etc/inittab. This is anindication that the product was not previouslyuninstalled.

System action:

User response: Run the setup with option '–a disable'and then start the installation process again. If theentries in /etc/inittab should be retained, refer to youruser documentation for information on how to

complete the installation manually.

FMM1542E Failed to uninstall because some of theprocesses to be uninstalled are stilllisted in /etc/inittab. Please re–run thesetup after stopping the component bycalling the setup script with option '–astop'.

Explanation: Before uninstalling the product, theaffected processes must be stopped. This is done byrunning the setup script with the option '–a stop',which will remove the entries from /etc/inittab andstop the processes.

System action:

User response: Refer to your user documentation forinformation on the uninstall process. Run the setupwith the option '–a stop' and then continueuninstalling.

FMM1543E The component is still referenced withinthe /etc/inittab. In order to terminate thecomponent re–run the setup script withoption '–a stop'.

Explanation: The setup utility detected that theproduct is still active in the system. Apparently, itsentries in /etc/inittab are not yet removed.

System action:

User response: Call this process again with the option'–f stop'.

FMM1544E New entries cannot be added to/etc/inittab because it already containstoo many entries starting with 'ac'.Please refer your user documentation fora manual setup of this package.

Explanation: During setup, an unusually high numberof entries beginning with 'ac' were detected in/etc/inittab. /etc/inittab was not modified.

System action:

User response: Determine if these entries areexpected, or if they were added due to a problem. Ifthese entries are required, refer to your userdocumentation for information on how to complete theinstallation manually.

FMM1545E oldprod is currently running.

Explanation: This failure happens during(de)installation and indicates that not all TSM for ACScomponents could be stopped.

System action:

User response: Check that no backup or restore iscurrently running and retry the operation. If you have



customized the process of starting TSM for ACS, itmight be necessary to manually stop it by undoingthose customization steps.

FMM1546E IBM Tivoli Storage Manager for AdvancedCopy Services was not started.

Explanation: This failure happens during installationand indicates that not all TSM for ACS componentscould be started successfully.

System action:

User response: Check that all TSM for ACScomponents have the appropriate access rights andretry the operation. Contact the support function if theoperation continues to fail.

FMM1547E Failed to remove the data associatedwith the deleted backup backup_id.

Explanation: The backup named was deleted.However, its data could not be removed from therepository and from the storage device.

System action:

User response: Look for a previous message pointingto the cause of the problem. Resolve any problemsindicated there. Once the cause of this problem isresolved, the daemon will take care of the deletedbackups eventually.

FMM1548E Failed to monitor the data associatedwith the deleted backup backup_id.

Explanation: A background daemon is supposed tomonitor the states of backups in order to determine ifdata needs to be deleted from the storage device.However, the monitor was not able to access theappropriate data.

System action:

User response: Look for a previous message pointingto the cause of the problem. Resolve any problemsindicated there. Once the cause of this problem isresolved the daemon will take care of the deletedbackups eventually.

FMM1549E Failed to load component_name

Explanation: The system was unable to load thenamed component of the product.

System action:


FMM1550W Unable to perform backgroundmonitoring for backup 'backup id' fortime.

Explanation: Background monitoring for the namedbackup id is suspended for the named period of timedue to it is locked or the background monitor is notrunning.

System action:

User response: Check if the background monitor isrunning.

FMM1553I Component_name is logging to path

Explanation: The file denoted is the log file of thenamed component.

System action:

User response: If you need to check the log of theindicated component, look for this message to identifythe log file to examine.

FMM1554W The agent 'component_name' terminatedwith exit code number.

Explanation: The process denoted ended with thegiven exit code.

System action:

User response: Check the agent's log for any messagespointing to a problem. Resolve any problem indicated.

FMM1555I Profile successfully created.

Explanation: The profile wizard created a new profile.

System action:

User response: The setup script recognizescomponents being restarted so that the new settingsbecome active..

FMM1556E Some data of backup backup_id areunavailable. It is impossible to restorethe data requested.

Explanation: The system detected that some of thedata originally contained in the backup is no longeravailable. The occurrence of this message depends onthe type of storage device employed. For example, if anearlier backup data was restored from an N–Seriesdevice, some data of a later backup will be destroyed.

System action:

User response: The backup is no longer complete andcannot be used for the requested operation. Try theoperation with a different backup.



FMM1557I Device client is logging to path

Explanation: The device agent's log messages arewritten to the file named.

System action:


FMM1558E There are no mount agents registeredfor participant(s) participant_list

Explanation: During a snapshot backup run, TSM forACS detected that for the listed participant(s) no TSMfor ACS device agent was started with the 'force mount'(–F) option. Typically, a participant corresponds to aDB2 partition. The current snapshot backup run will bedeleted.

System action:

User response: Make sure that for each participant(DB2 partition) a TSM for ACS device agent is startedwith the mount force option (–M) on the offloadsystem.

FMM1559E Failed to verify consistency ofDataContainer (data_container)

Explanation: During a snapshot backup run, TSM forACS detected that the listed data container (typically anAIX volume group or an N Series volume) could not beimported/mounted successfully on the offload system.The current snapshot backup run will be deleted.

System action:

User response: Check the TSM for ACS device agentlog/trace file for errors and restart the snapshot backupafter the problem is corrected.

FMM1560E Not all file systems have been validatedby the mount agents!

Explanation: During a snapshot backup run, TSM forACS detected that not all file systems could bemounted successfully on the offload system. Thecurrent snapshot backup run will be deleted.

System action:

User response: Check the TSM for ACS device agentlog/trace file for errors and restart the snapshot backupafter the problem is corrected.

FMM1561E Profile name profile_name does not pointto a file.

Explanation: The profile specification should be afully qualified filename. Otherwise, it is assumed to berelative to the current directory of the command thatissues the message, which may not be the desireddirectory.

System action:

User response: Correct the name.

FMM1562E Deleting the backup as requested isimpossible while any part of it ismounted.

Explanation: A request was sent to delete a backup.However, some parts of the backup were still mounted.Presumably, a restore operation or an off–loaded tapebackup is pending or in progress. Please note that anoffloaded tape backup requires the snapshot backups ofall partitions of the database.

System action:

User response: Wait until the operation in progresshas ended, then issue the delete request again.

FMM1563I The snapshot backup defined bytimestamp timestamp for instanceinstance, database database_name, andpartition partition_number cannot berestored.

Explanation: This message appears when backups arequeried for a restore. It indicates that a snapshotbackup was encountered that is not in a restorablestate. For example, snapshot backups created with aFLASHCOPY_TYPE of NOCOPY are not restorable.When queried for restore, unrestorable snapshotbackups are not returned to the caller and thereforecannot be selected for restore.

System action:


FMM1564W Backup id is marked for deletion. Youneed to unmount before it can bephysically deleted.

Explanation: A snapshot backup with the named idcan only be deleted if all of its assigned file systems areunmounted successfully.

System action:

User response: Issue the offload agent with thecommand '–f unmount'. After all resources are freed,the deletion of the snapshot backup will be started.

FMM1567I Reconciliation for device class 'deviceclass' completed successfully.

Explanation: The reconciliation process for thespecified device class was successful. The backuprepository was synchronized with the existing backupson the storage device specified by the DEVICE_CLASSparameter.





FMM1568I Removing backup backup_id from therepository because it has not been foundon the storage device duringreconciliation.

Explanation: During reconciliation the backup with idbackup_id has not been found on the storage device.Therefore it is deleted from the repository to keep therepository and the valid backups on the storage insync.

System action:


FMM1569I Updating backup backup_id in therepository because some data was notfound on the storage device duringreconciliation.

Explanation: Backup data with the identifier backup_idis no longer available on the storage device. Dependingon storage device settings, the space from olderbackups might be reused to create new backups. Thisinformation is updated in the IBM Tivoli StorageFlashCopy Manager repository.



FMM1570W The following container could not bedeleted from the storage box duringreconciliation: volume_name.

Explanation: The volume volume_name could not bedeleted from the storage box. It is not needed anymorebecause there is no corresponding backup in therepository.

System action:

User response: Ignore the warning or try to delete thevolume from the storage device manually.

FMM1571W The specified value for 'recon_interval' is0. Be aware that every time abackground monitor is started areconcile will be scheduled so that otherbackground operations will never bescheduled. This should be used fortesting purposes only.

Explanation: If RECON_INTERVAL is 0 every time abackground monitor is started it will startreconciliation. Other background operations as deletionor monitoring will never be scheduled.

System action:

User response: Change RECON_INTERVAL to a valuegreater than 0 if you want to avoid this behavior.

FMM1572I Starting reconciliation for device class'device_class_name'

Explanation: The reconciliation will be started for thedevice class device_class_name of the profile.

System action:


FMM1573I The container 'volume_name' has beensuccessfully deleted from the storagebox. It didn't belong to any backup inthe repository.

Explanation: The volume volume_name has beensuccessfully deleted from the storage box duringreconciliation because it didn't belong to any backup inthe repository.

System action:


FMM1574I Backup for hardware isolation key iscreated using DEVICE_CLASS deviceclass.

Explanation: The current snapshot backup is using thespecified device class.



FMM1575E product name cannot be used to performdual backups. Update your profile toperform either a disk–only backup oruse TSM for ERP to perform a dualbackup.

Explanation: The backup cannot be started with thecurrent configuration. TSM for ERP 6.1 or later is notinstalled or configured in /usr/sap/<SID>/SYS/exe/run. Instead, /usr/sap/<SID>/SYS/exe/run/backintpoints directly to the IBM Tivoli Storage FlashCopyManager backint. Offloaded backups from a snapshotto IBM Tivoli Storage Manager is not allowed with thisconfiguration.


User response: Update your profile to perform eithera disk–only backup or use TSM for ERP to perform adual backup. .

FMM1576W The backup backup id is skipped fromexpiration processing because it ismounted.

Explanation: A new backup request was started whilethe specified backup is mounted on a backup system.The target set of the mounted backup cannot be reusedfor a new backup.




User response: If you encounter an error messageFMM1579E after this warning message, unmount themounted backup before attempting a new backup.Otherwise, no action is required as long a valid targetset is specified for the new backup.

FMM1577W The backup backup id is skipped fromexpiration processing because amandatory Tivoli Storage Managerbackup from this image is pending.

Explanation: A new backup request was started whilethe specified backup is currently pending to beoffloaded to tape on a backup system. The backuptarget set that is currently pending cannot be reused fora new backup.


User response: If you encounter an error messageFMM1579E after this warning message, start theoffloaded tape backup before attempting a new backup.Otherwise, no action is required as long a valid targetset is specified for the new backup. If you do not wantto start the offloaded tape backup, update the usabilitystate for this backup by issuing the tsm4acs -fupdate_status command with the TSM_BACKUP=nooption.

FMM1578W A backup is skipped from expirationprocessing because of the followingerror:

Explanation: A new backup request was started whilethe specified backup is currently locked by anotheroperation.


User response: If you encounter an error messageFMM1579E after this warning message, wait until theoperation that is locking the backup completes beforeattempting a new backup. Otherwise, no action isrequired as long a valid target set is specified for thenew backup.

FMM1579E Failed to find a suitable target set fordevice class device class.

Explanation: An available target set was not locatedand an attempt was made to use the target set of theoldest backup. However, this oldest backup target set isin a MOUNTING or MOUNTED state which preventsreuse. A target set containing a snapshot taken with theparameter TSM_BACKUP set to MANDATE will alsoprevent reuse, execpt when the Tivoli Storage Managerbackup is complete.


User response: Make sure enough target sets areavailable and verify the state of the existing target sets.

FMM1580E Specifying a target volume serialnumber is mandatory for parameter'TARGET_VOLUME'.

Explanation: The parameter 'TARGET_VOLUME'expects three values being defined. If these are notpresent this error occurs.

System action:

User response: Specify the following values forparameter 'TARGET_VOLUME': <target volume serialnumber> <source volume serial number> <sourcevolume size>. Only the first value is mandatory. Ifsource volume information is omitted, dashes must beentered in both fields as placeholders. Examples:TARGET_VOLUME 401FCA90 40EFCA90 Size=2.0_GBTARGET_VOLUME 401FCA909 - -

FMM1581E Error while parsing parameterTARGET_VOLUME target volume paramin volumes file: the parameterTARGET_VOLUME allows at mostthree parameters.

Explanation: The parameter 'TARGET_VOLUME'expects three values being defined. If there are morethis error occurs.

System action:

User response: Correct the specified values forparameter 'TARGET_VOLUME' according to thispattern: <target volume serial number> <source volumeserial number> <source volume size>. Only the firstvalue is mandatory. If source volume information isomitted, dashes must be entered in both fields asplaceholders. Examples: TARGET_VOLUME 401FCA9040EFCA90 Size=2.0_GB TARGET_VOLUME 401FCA909- -

FMM1582I The target set target set will be used forthe current backup.

Explanation: IBM Tivoli Storage FlashCopy Managerallows to define target sets by a target set definition file(SVC and DS8000) or by a certain naming conventionby that IBM Tivoli Storage FlashCopy Managerdetermines the name of the target from the name of thesource volume and the name of the target set to beused for the current operation (SVC only). Thismessage reflects which target set is applied for thecurrent snapshot backup based on the given conditions.

System action:

User response: Specify means of target set selection bythe profile parameter 'TARGET_SETS' and a target setdefinition file.



FMM1583W Backup agents were requestingincompatible Tivoli Storage Managerbackup options. The composed statesare: 'states'.

Explanation: A backup of a partitioned database wasattempted. Offloaded backups to Tivoli StorageManager use options that are different from optionsused with the partition backup. However, TivoliStorage Manager backup options for all partitionsshould be identical. This can occur when differentdevice classes are used to back up different partitions,and those device classes are associated with differentTivoli Storage Manager backup options. The productautomatically determines the correct Tivoli StorageManager backup options for this operation to prevent afailure.

System action: The operation continues with warning.

User response: Update the configuration so that allpartitions use the same Tivoli Storage Manager backupoptions during future operations.

FMM1584E Snapshot backup referenced by ID'backup id does not exist.

Explanation: The specified backup ID was not foundin the local snapshot repository.


User response: Use the inquire function to verify thatthe specified backup ID is valid.

FMM1586E Not enough sessions available.

Explanation: The sum of available sessions specifiedin the various server statements does not cover therequired numbe r of sessions.


User response: Change and adapt the values of thecorresponding parameters in the IBM Tivoli StorageManager for Enterpri se Resource Planning profile.

FMM1588E The master password you provided doesnot meet the minimum complexityrequirements. Acceptable masterpasswords are a minimum of minlengthcharacters and must contain at least onenumber and one letter.

Explanation: For security reasons, the masterpassword must meet minimum length and complexityrequirements. The master password must be aminimum of 8 characters and must contain at least onenumber and one letter. The use of special symbolsincreases the strength of the password.

System action: The password you provided is notadopted.

User response: Define a strong password that meetsthe minimimum length and complexity requirements.

FMM1999E A restore operation is not allowed for abackup that was originally performedwith FLASHCOPY_TYPE NOCOPYfrom target volume targetVolume on SanVolume Controller Versionversion.release.revision. Use San VolumeController Version 5.1 or later.

Explanation: A restore from backups performed withthe FLASHCOPY_TYPE NOCOPY value is onlysupported for San Volume Controller Version 5.1 orlater.


User response: Run the restore operation again with abackup that was originally performed withFLASHCOPY_TYPE INCR or FLASHCOPY_TYPECOPY.

FMM2000I Successfully connected tocomponent_name on port portnumber.

Explanation: One of the Data Protection for SAPmodules BACKINT or theThe backup library libtdp_r3initiated a successful connection to the backgroundprocess component_name on port portnumber.

System action:


FMM2001E Socket error while connecting tocomponent_name at host: reason.

Explanation: The background process component_nameis not running.

System action:

User response: Start component_name manually and tryagain.

FMM2002E The group permissions of the user'username' are not sufficient. TheOracle(R) executables have the groupownership 'group' but the specified userdoes not belong to that group.

Explanation: The specified user has not enoughpermissions to use the Oracle(R) executables.


User response: Add the specified group to thespecified user.



FMM2003I File file_name BID deleted.

Explanation: The file file_name with the backup ID<BID> was deleted from the Tivoli Storage Manager.

System action:


FMM2004E Socket error while listen to port portnumber - error: error text.

Explanation: The application was unable to listen tothe port specified.


User response: Check if the process was alreadystarted. Do not start a second instance of the sameprocess. Check if the port specified is in use by anotherapplication and specifiy a different port number.

FMM2005W The virtual machine 'vm name' withinstance UUID 'source vm instance uuid'will be processed without the requestedbackup mode since the 'device names'devices are directly passed through tothe virtual machine.

Explanation: The specified virtual machine haspassthrough devices, also known as VMDirectPath.VMware is not able to suspend/resume or createsnapshots on such virtual machines. Thus this virtualmachine will be processed without doing so.


User response: If the specified virtual machine backupmode should be processed as requested remove thepassed through devices from this virtual machine.

FMM2006W The virtual machine 'vm name' withinstance UUID 'source vm instance uuid'will be processed without the requestedbackup mode since fault tolerance isturned on.

Explanation: The specified virtual machine has faulttolerance turned on. VMware is not able tosuspend/resume or create snapshots on virtualmachines with fault tolerance turned on. Thus thisvirtual machine will be processed without doing so.


User response: If the specified virtual machine backupmode should be processed as requested turn faulttolerance off for this virtual machine.

FMM2007E Unknown Port: port

Explanation: The port specified for communicationbetween component_name and BACKINT or the backuplibrary is unknown.

System action:

User response: Check the port value specified whencomponent_name was started. Additionally, check theenvironment variable PROLE_PORT for the BACKINTenvironment. These two values must match.

FMM2008E Unable to connect to component_name.

Explanation: Internal error.

System action:


FMM2009I Deleting backup version_number and allolder backups.

Explanation: All full database backups and theircorresponding log file backups will be deleted fromTivoli Storage Manager storage, if their version numberis less than or equal to version_number.

System action:


FMM2010E Error occurred processing FRONTEND.

Explanation: An error occurred during the frontendprocessing.

System action:

User response: Check the frontend script/programand the settings in the Data Protection for SAP profile(keyword FRONTEND) and try again.

FMM2011E Error occurred processing BACKEND.

Explanation: An error occurred during the backendprocessing.

System action:

User response: Check the backend script/programand the settings in the Data Protection for SAP profile(keyword BACKEND) and try again.

FMM2012E The specified user name or password isnot correct, authentication failed.

Explanation:

System action:

User response: Enter the correct user name andpassword.



FMM2013I Starting FRONTEND program.

Explanation: The frontend program is executing.

System action:


FMM2014I FRONTEND program finished.

Explanation: The frontend program is finished.

System action:


FMM2015I Starting BACKEND program.

Explanation: The backend program is executing.

System action:


FMM2016I BACKEND program finished.

Explanation: The backend program is finished.

System action:


FMM2017I Blocksize is set to num_bytes bytes

Explanation: The operational blocksize is num_bytesbytes.

System action:


FMM2018I The file system 'file system' was addedsuccessfully to the remote cluster 'remotecluster name'.

Explanation: The specified file system was addedsuccessfully to the remote cluster and is now ready tobe mounted.

System action: Processing continues

User response:

FMM2019I The snapshot of file system 'file system'was mounted successfully to 'path'.

Explanation: The specified snashot of the specified filesystem was mounted successfully.


User response:

FMM2020I The file system 'file system' was removedsuccessfully from remote cluster 'remotecluster name'.

Explanation: The specified file system was removedsuccessfully from the remote cluster.


User response:

FMM2021I The file system 'file system' wasunmounted successfully.

Explanation: The specified file system was unmountedsuccessfully.


User response:

FMM2022E Unable to change mode of file file name:description

Explanation: Unable to change mode of file file name.description may contain the system error text.

System action:

User response: Check the description. If the errorpersists, contact your service representative.

FMM2023I The 'vm name' virtual machine with the'vm instance uuid' instance UUID isresumed.

Explanation: The specified virtual machine isresumed.



FMM2024E Error in connection to component_name.

Explanation: The connection to component_nameterminated unexpectedly. This message might bedisplayed due to previous errors or after an unexpectedtermination of the component_name process.

System action:

User response: Check for other error messages andrestart component_name if necessary. Try again. If theproblem persists, contact IBM Support.

FMM2025E Failed to respond to a message receivedfrom component_name.

Explanation: This is an internal error.

System action:




FMM2026E Unexpected exception in handler:handler.

Explanation:

System action: This is an internal error.


FMM2027I Using TSM–API version your API version(compiled with compiled with version).

Explanation: Version information about the TSM–API.

System action:


FMM2028W Unable to terminate a session due to thefollowing error: session.

Explanation: This is an internal error during cleanupthat has no effect on the success of the service.

System action:


FMM2029E Could not instantiate the bufferallocator because of the followingincompatibility issue: expression.


System action:


FMM2031E A buffer allocator cannotsimultaneously satisfy all of thefollowing properties: list of properties


System action:


FMM2033E Cannot instantiate allocator of typeallocator type with the followingadditional properties: list of properties


System action:


FMM2086W The following failure groups were notneeded during the backup: serial. Eitherthey are misspelled in the profile orthey are not online. You might want tocheck them.

Explanation: The specified failure groups have notbeen used for the backup. Either they have not been

found or they are not online.


User response: You might want to check if the failuregroups you specified in the profile are spelled right. Ifthey are spelled right you might want to check if all ofthem are online.

FMM2087W The diskgroup 'dg' contains 'fg total'failure groups, but currently only 'fgonline' of them are online. Just theonline failure groups can be included inthe backup. During restore just theonline failure groups would be restoredand the others would be dropped.

Explanation: Not all of the failure groups of thespecified diskgroup are online. Just the failure groupswhich are online can be included in the backup. Duringa restore the failure groups included in the backup arerestored, the others are dropped.


User response: You might want to check if all failuregroups of the specified diskgroup are online and if notbring the online to include all of them in the backup.

FMM2088I The diskgroup 'dg' and its online failuregroups: fg are now dropped.

Explanation: The specified diskgroup and its failuregroups are dropped. Usually the customer will have torecreate the failure groups which were not included inthe backup after having restored successfully.


User response: After having restored you might wantto recreate the failure groups which have not beenrestored.

FMM2089W The diskgroup 'dg' contains failuregroups which are currently offline: fg.The diskgroup cannot be dropped fromthese failure groups. Please ensure thatthey do not become available during therestore process.

Explanation: The specified failure groups are currentlyoffline. ASM cannot drop a diskgroup from failuregroups which are offline. If these failure groups getonline during the restore process this could result in aninconsistent state.


User response: Please ensure that the specified failuregroups do not become online again during the restoreprocess.



FMM2090E The device 'dev' could not be removed.Please ensure that you are not accessingthe ASM or database instance forexample by an open sqlplus console.

Explanation: The specified device could not beremoved from the OS because it is still in use. Thismight be caused by accessing the ASM or databaseinstance for example by an open sqlplus console.


User response: Please ensure that you don't access thedatabase or ASM instance by any open SQL consoles.

FMM2091W For the virtual machine 'vm name' thebackup mode mode is changed to ASISbecause it has raw device-mappingdisks attached. As a consequence, thebackup of the specified virtual machineis only crash consistent.

Explanation: In principle, raw device-mapping disksare not included in the IBM Tivoli Storage FlashCopyManager backup. When you restore the virtualmachine, it is not possible to revert to the VMwaresnapshot. Because when the VMware snapshot wastaken, the raw device-mapping disks were still part ofthe virtual machine configuration. The requestedVMware snapshot is skipped before the actualhardware snapshot is performed for this virtualmachine.

System action: Processing continues. The backup ofthe specified virtual machine is performed but withcrash consistency only.

User response: To process the specified virtualmachine backup mode as requested (including theVMware snapshot), remove the raw device-mappingdisks from the virtual machine configuration before thebackup.

FMM2092W A restore of the virtual machine 'vmname' does not recover the existingVMware snapshots because it has rawdevice-mapping disks.

Explanation: In principle, raw device-mapping disksare not included in the IBM Tivoli Storage FlashCopyManager backup. When you restore the virtual machineit is not possible to revert to the existing VMwaresnapshots. Because at the time when the VMwaresnapshots were taken, the raw device-mapping diskswere still part of the virtual machine configuration.


User response:

FMM2093W The virtual machine 'vm name' has rawdevice-mapping disks attached. Whenyou restore this virtual machine fromthe hardware snapshot the achievedconsistency level is crash consistencyonly. This limitation does not applywhen you restore the virtual machinefrom the offloaded Tivoli StorageManager backup.

Explanation: In principle, raw device-mapping disksare not included in the IBM Tivoli Storage FlashCopyManager backup. When you restore the virtual machinefrom the hardware snapshot backup, it is not possibleto revert to the VMware snapshot. Because at the timewhen the VMware snapshot was taken, the rawdevice-mapping disks were still part of the virtualmachine configuration. When the hardware snapshotbackup is offloaded to Tivoli Storage Manager andrestored from there, this limitation does not apply.


User response: Restore the virtual machine from theoffloaded Tivoli Storage Manager backup to maintainfile system level consistency.

FMM2094W A file layout change was detectedduring the backup of the virtualmachine 'vm name', this change wasprobably caused by a VMware StorageVMotion operation. The virtual machineis excluded from the backup and cannotbe restored from this backup.

Explanation: A VMware Storage VMotion operationmight interfere with the snapshot backup process. It ispossible, that files are migrated to another data storethat is not included in the backup while the backup isin progress. As a result, these files cannot be restored ata later time.


User response: Ensure that a storage migration is notoccurring on the virtual machine and rerun the backuptask.

FMM2095E The backup is unusable because all thevirtual machines that it contains havebeen invalidated due to an interferingVMware Storage VMotion operation.

Explanation: A VMware Storage VMotion operationmight interfere with the snapshot backup process. It ispossible, that files are migrated to another data storethat is not included in the backup while the backup isin progress. As a result, these files cannot be restored ata later time.


User response: Ensure that a storage migration is notoccurring on the virtual machines you selected for



backup and rerun the backup task.

FMM2096W The offload agent ('bexname') was notstarted. As a consequence, the snapshotbackup is not automatically offloaded toIBM Tivoli Storage Manager.

Explanation: The offload agent periodically checks fornew snapshot backups that are ready to offload to IBMTivoli Storage Manager. If the offload agent is notrunning as a daemon process, then the offload backupis not automatically triggered.


User response: Ensure that the offload agent is startedby verifying that an entry is made to the inittab or byconfiguring an upstart job. The setup scripts used byIBM Tivoli Storage FlashCopy Manager can performthis task. Alternatively, you can manually trigger anoffload backup or you can run a scheduled script tostart the offload agent. For more information, see theIBM Tivoli Storage FlashCopy Manager Installation andUser's Guide.

FMM2913I The version delete setting is configuredto retain number backup generations.Checking for expired backups.

Explanation: The profile parameter MAX_VERSIONSis configured to retain number backup generations. DataProtection for SAP is checking if surplus backups exist.



FMM4000W The attributes of file 'file name' cannot berestored. Reason: errno(error_num)error_desc.

Explanation: The file file name was restoredsuccessfully but one or more file attributes (permission,ownership, date/time) of the file file name cannot berestored correctly.

System action:

User response: Check the error number error_num andthe error description error_desc to avoid this problem inthe future. An initial solution could be to set theappropriate correct permission for the file file namemanually.

FMM4001E File 'file name' cannot be created. Reason:errno(error_num) error_desc

Explanation: The file file name to be restored could notbe created/written. It is possible, that you do not havethe appropriate rights for writing the file file name tothe destination path.

System action:

User response: Check the error number error_num andthe error description error_desc to avoid this problem inthe future. Furthermore, check the write permission ofthe user who started the restore.

FMM4002E Error during write of file ' file_name'.Reason: errno(error_num) error_desc

Explanation: An error occurs during the restoreprocess of the file file name.

System action:

User response: Check the error number error_num andthe error description error_desc to avoid this problem inthe future.

FMM4003E Operation mount will be aborted.Physical volume(s) with conflictingphysical volume id(s) have been foundon the target host 'host_name' list_of_pvids

Explanation: Physical volume(s) with one or more ofthe physical volume id's which are part of this mountoperation do already exist on the target host.Continuing would cause conflicting physical volumeid's.


User response: Cleanup the target system. Remove thespecified volume(s) containing the same physicalvolume id(s).

FMM4005E Error allocating memory block for filefile name. BLOCKSIZE may be too large.

Explanation: Unable to request new memory blocksduring the backup of file file name.

System action:

User response: Verify that you have set a valid valuefor BLOCKSIZE. If you are not sure what value isvalid, comment it out so the default value is used.Furthermore, you can check if you have enough RAMavailable with your machine. Also, check the memoryusage during backup. It may be necessary to stopanother application, increase memory, or change theconfiguration.

FMM4007E File 'filename' cannot be read Reason:errno(error_num) error description

Explanation: Data could not be read due to somesystem error. Check error description for furtherinformation. If this error recurs, this might indicatesome hardware problems.

System action:

User response: Contact your system administrator.



FMM4008E File 'filename' cannot be opened. Reason:errno(error_num) error_text

Explanation: Could not open the file file name due tosome system specific problems.

System action:


FMM4009E Not enough space to write File 'filename'.Possible reasons: disk full or ulimitexeeded.

Explanation: The system rejected a request to writedata into file file name. The storage media might nothave enough free space to keep the file or the systemrejected writing the file due to administrative resourceconstraints such as ulimits.

System action:


FMM4010E SAP requires the file filename to be aregular file.

Explanation: To be able to support SAP environmentsthe named file has to be a regular file.

System action:


FMM4011W The backup device type (filetype backupdevicetype backup devsubtype) differs fromthe restore device type (filetype restoredescr1 descr2) for name.

Explanation: A mismatch between the device typesduring backup and restore was detected.

System action:

User response: Check the logs for further information

FMM4012E Unexpected EOF for file 'filename' afterreading number Bytes.

Explanation: The end of file was reachedunexpectedly.

System action:


FMM4013I CreateFile() withdwFlagsAndAttributes='attribute'.

Explanation: A file with the nmed attribute wascreated.

System action:


FMM4014E File 'filename' cannot be accessed.Reason: errno<(number) errormsg

Explanation: A named file could not be accessedeither for reading or writing.

System action:

User response: Check the file permissions and ifnecessary adjust them accordingly. Try again.

FMM4015E Failed to attach the volumes 'volumes' tothe host 'hostname'.

Explanation: IBM Tivoli Storage FlashCopy Managerwas not able to attach these volumes to the host formount.


User response: Verify the CIM error.

FMM4016W The mapping between volume 'vol' andthe host 'hostname' was not found in theCIMOM.

Explanation: IBM Tivoli Storage FlashCopy Managerdid not found the map volume to host in the CIMOM.



FMM4017E Failed to detach the volumes 'volumes'from the host 'hostname'.

Explanation: IBM Tivoli Storage FlashCopy Managerwas not able to detach these volumes from the hostafter the unmount.


User response: Verify the CIM error.

FMM4018E Parameter parameter name requires avalue in the range between min and max.

Explanation: The value specified for the namedparameter does not comply with the defined range ofvalues.

System action:

User response: Check the named profile keyword andmake appropriate adjustments.



FMM4019E The hostname 'hostname' must bedefined as a host entry in the IBM SANVolume Controller.

Explanation: IBM Tivoli Storage FlashCopy Managerwas not able to find the hostname specified as a validhost entry in the IBM SAN Volume Controller. Thisvalue is specified in the profile by the parameterBACKUP_HOST_NAME.


User response: Verify the value specified in the profileand ensure that it is a valid host in the IBM SVCVolume Controller.

FMM4021E The FlasCopy mapping for the sourceand target volumes 'src' and 'tgt' wasfound, however the consistency group ismissing.

Explanation: IBM Tivoli Storage FlashCopy Managerwas not able to find the consistency group for theexisting mapping of the soruce and target volumesspecified.


User response: The state found in the storagesubsystem is not supported for a re-start of theFlashCopy. The consistency group and the FlashCopymappings are created by IBM Tivoli Storage FlashCopyManager and re-use during refreshing of theFlashCopy. A manually cleaup should be evaluated inthis case.

FMM4022E The LUN serial numbers Lun serials thatwere used by the original datastore arenow in use by the following datastores:new datastore names Ensure that the LUNsare not in use by other datastores, byremoving the datastores that areconained by these LUNs from thevCenter Server.

Explanation: After a backup the datastore was deletedand the disks are reused to create new datastores. IBMTivoli Storage FlashCopy Manager overwrites thecontent of disks during an instant restore. Therefore,verify that the disks are not in use to ensure that theinstant restore can complete successfully.


User response: Identify the datastores that arecurrently using these LUNs and delete the datastores inthe vCenter Server, then retry the operation again.

FMM4023E The new datastorename datastore, whichwas identified to be overwritten by theinstant restore, does not use all theLUNs of the original datastore. Removethis datastore and corresponding virtualmachines from the vCenter Server andretry the instant restore operation again.

Explanation: After a backup the datastore was deletedand some of the disks has been reused to create a newdatastore. This message is issued to alert you to the factthat the newly created datastore and virtal machineswill be overwritten.


User response: Delete the datastore that is named inthis error message from the vCenter Server, then try theinstant restore operation again.

FMM4024E This backup version was created with aprevious version of the product thatdoes not support datastore restore(instant restore). Create a new backup toenable the instant restore function. Youcan restore the backup by using avirtual machine restore operation.

Explanation: The instant restore failed because thebackup version was old and does not support instantrestore. It is still possible to use a virtual machinerestore function.


User response: Create a new backup of yourdatastores to enable instant restore for the datastores. Itis still possible to do a virtual machine restore from anold backup.

FMM4175E San Volume Controller VDisk vdisk isnot online. Please retry this commandafter bringing this volume back online.

Explanation: Either the source or the target VDisk isno longer online.


User response: Please retry the command afterbringing the VDisk back online.

FMM4176E A restore is not allowed fromspace–efficient target volumetargetVolume on San Volume ControllerVersion version.release.revision. Use SanVolume Controller Version 5.1 or later.

Explanation: Restore from Space–efficient targetvolumes is only supported on San Volume ControllerVersion 5.1 or later.




User response: Run the restore operation with abackup that was performed using a full volume target.

FMM4177E User specified copy type usrCopyType isin conflict with the copy type fcCopyTypefor the previously establishedFlashCopy. Please retry the operation forthis copy type specifying a differenttarget set.

Explanation: The previously established FlashCopymaps are used for a specified copy type for all backupsthat use the same copy type.


User response: Run the operation again with adifferent target set in order to use this copy type.

FMM4178E The directory 'directory' containing theCIM components is missing.

Explanation: The CIM components (a collection ofdifferent libraries) must reside in a directory within aspecific pegasus-directory. The directory has to becreated under the pegasus-directory where the deviceagent can be found.


User response: Make sure that the pegasus-directoryis created under the location where the device agentexists. If this required pegasus-directory is notavailable, it can be manually copied from the defaultFlashCopy Manager installation directory to therequired location.

FMM4179E Metro mirror or global mirror remotecopy relations for source 'source vdisk' donot have a consistency group defined.

Explanation: Metro mirror or global mirror remotecopy relations have not been added to a consistencygroup.


User response: Add the metro mirror or global mirrorremote copy relations to a consistency group. Try theoperation again.

FMM4180W The current number of metro mirror orglobal mirror remote copy relations'current num of rc relations' is differentfrom the number at the time of backup'original num of rc relations'.

Explanation: The number of metro mirror or globalmirror remote copy relations is different from that atthe time of backup.


User response: Add the missing metro mirror or

global mirror remote copy relations to the consistencygroup. Try the operation again.

FMM4183I Performing flashcopytype FlashCopy ofsource volume source to target volumetarget.

Explanation: Indicates which type of FlashCopy isperformed and which source and target volumes areused.

System action:


FMM4184I CIM Agent version for hwType:'version.release.revision'.

Explanation: Provides the CIM Agent version.

System action:


FMM4185E The mandatory source and targetFlashCopy mapping source / target cannotbe satisfied because the volumes do notmatch.

Explanation: The source to target mappings specifiedin the target volumes file are invalid. Either thevolumes are located in different SAN VolumeController clusters or the volume size does not match.

System action:

User response: Correct the target volumes file and trythe operation again.

FMM4186E For the sources source no matching targetLUN could be found in the selectedtarget set.

Explanation: The selected target set from the targetvolumes file has no matching volume for the sourcevolume. Either the volumes are located in differentSAN Volume Controller clusters or the volume sizedoes not match.

System action:

User response: Update the target volumes file toprovide target sets which have matching targetvolumes for the source volumes.

FMM4187E The LUN with serial number 'serial' isnot known by the configured CIMAgent 'primaryserver' of storage systemtype 'hardwaretype'.

Explanation: The device agent communicates with thestorage CIM agent to get information about the LUNs.However, the connected CIM Agent did not findinformation for the LUN identified by this serial



number. Verify that the correct device class is used, andthat the missing LUN resides on the specified CIMagent of the specified storage system type.


User response: Verify with the storage GUI or CLIthat the CIM agent is working and the concerned LUNis available. Another cause of this error is when thestorage system of the disks are not of the type specifiedby the parameterCOPYSERIVICES_HARDWARE_TYPE. See thedescription of this parameter in the User's Guide. UseAIX commands to figure out the type of the storage.For example, lscfg -pvl 'hdisknnn' or lsdev -Cc disk.Ensure that each copy of the database is residing ondisks of the same storage system type. Ensure that theright device class has been used and that the missingLUN resides in the specified CIM agent of the specifiedstorage system type.

FMM4188E The target volume named volname is notknown by the CIM Agent in the clustercluster.

Explanation: The device agent communicates with thestorage CIM agent to get information about the LUNs.However, the connected CIM Agent did not findinformation for the LUN identified by this volumename and cluster name.


User response: Verify with the storage GUI or CLIthat the CIM agent is working and the concerned LUNis available.

FMM4189E The cluster id clustername; specified bythe parameter parname; is not known bythe CIM Agent.

Explanation: The FlashManager device agentcommunicates with the storage CIM agent to getinformation about the LUNs. However, for the clusteridentified by this id or name no information was foundin the CIM agent current connected.


User response: Verify with the storage GUI or CLIthat the CIM agent is working and the concernedcluster is available.

FMM4190I All source/target pairs are in anincremental FlashCopy relation.

Explanation: The FlashManager device agent foundalready established FlashCopy relations and will try tore-use them.



FMM4191I No source/target pairs are in anincremental FlashCopy relation.

Explanation: The FlashManager device agent was notable to find FlashCopy relations for the volumesinvolved in this backup. The relations will now beestablished.



FMM4192I Not all source/target pairs are in anincremental FlashCopy relation.

Explanation: The FlashManager device agent foundsome of the FlashCopy relations established, some not.The missing relations will be established.

System action:


FMM4193E The DB2 instance owner instanceownercould not be found in /etc/passwd.

Explanation: This function is only allowed for DB2.Your DB2 instance must have the same name as theDB2 instance owner as specified in /etc/passwd.


User response: Please make sure you start thisfunction as DB2 instance owner.

FMM4194I All virtual machines that are locatedwithin the 'datastore name' data store arepowered down and unregistered.

Explanation: All virtual machines that are locatedwithin the specified data store are powered down andunregistered.



FMM4195I The 'vm name' virtual machine issuccessfully restored and registered atthe 'ESX host name' ESX host.

Explanation: The specified virtual machine wassuccessfully restored and registered.


User response: No action is required

FMM5000E Tivoli Storage Manager Error:error_message

Explanation: During a connection of Data Protectionfor SAP to Tivoli Storage Manager server, a TivoliStorage Manager error error_message occurred.

System action:



User response: Use the Tivoli Storage ManagerMessages guide and correct the Tivoli Storage Managerserver error. Try your last action again.


Explanation: During a connection of Data Protectionfor SAP to Tivoli Storage Manager server, a TivoliStorage Manager error error_message occurred.

System action:

User response: Use the Tivoli Storage ManagerMessages guide and correct the Tivoli Storage Managerserver error. Try your last action again.

FMM5002E Tivoli Storage Manager Error duringinquire of mux file backup_id:error_message

Explanation: See FMM5001E.

System action:

User response: See FMM5001E.



System action:


FMM5004W Tivoli Storage Manager Error:error_message


System action:


FMM5005E Tivoli Storage Manager Error.


System action:




System action:




System action:




System action:




System action:




System action:




System action:


FMM5012E Cannot open Tivoli Storage ManagerAPI message text file. Check ifDSMI_DIR is set correctly. Currentvalue of DSMI_DIR is: dsmi dir

Explanation: The Tivoli Storage Manager API isunable to open the message text file. This file isrequired in order to issue messages. By default, itshould reside in the Tivoli Storage Manager APIinstallation directory. If the Tivoli Storage Manager APIis installed in another location, use the DSMI_DIR theenvironment variable to specifiy the correct location.


User response: Verify that the DSMI_DIR environmentvariable points to the correct location and that theTivoli Storage Manager API installation is complete.



FMM5013E Value for name is too long. Currentvalue: value

Explanation: The value of the environment variablename has too many digits.

System action:

User response: Check if the variable is set correctly.



System action:


FMM5015W Data description, file name could not berestored, because it was backed up witha newer version (objInf_supportinformation).

Explanation: The TSM server hosts backups (datadescription) which were made with a new version ofbackint or backom, which ignores this data in furtherprocessing.

System action:

User response: Upgrade the product.

FMM5016I Time: current time New TSM sessioncreated: MGMNT–CLASS:management_class, TSM–Server:server_name, type: session_type

Explanation: A new session to TSM server server_namehas been established at current_time. Data will be storedin management class management_class.

System action:


FMM5017E Internal Tivoli Storage Manager Error:Transaction succeeded although it wasexpected to fail.

Explanation: An internal Tivoli Storage Manager erroroccurred.

System action:

User response: Retry the action. If the error occursagain contact IBM Support.

FMM5018E The requested buffer has a size(current_size bytes) that is smaller thanrequested requested_size.

Explanation: The request for a new buffer wassuccessful. The buffer, however, does not have therequested size.

System action:

User response: Check if the system is running low onmemory and retry the action. If the error occurs againcontact IBM Support.

FMM5019E Error during delete of object filename:object

Explanation: A named file could not be deleted from aTSM server.

System action:


FMM5020E Error while deleting objects : objects

Explanation: One or more named objects could not bedeleted from a TSM server.

System action:


FMM5021W No data is deleted on the TSM Serverbecause the environment variable"XINT_FUNCTION_DELETE" is set to"DISABLE".

Explanation: The delete function was disabledtemporarily.

System action:

User response: If the delete function has to bere–activated, unset the environment variableXINT_FUNCTION_DELETE and try again.

FMM5022W Error during version delete. Not allbackups that should have been expiredcould be removed.

Explanation: The database backup finishedsuccessfully. Nevertheless, the deletion of expiredbackup sets failed.

System action:


FMM5637I SAN Volume Controller CIM Agentversion is: version.msgnl;

Explanation: The San Volume Controller CIM Agentversion.





FMM5651E Incorrect copy type copyType has beenspecified for space–efficient targetvolume targetVolume. Please retry thiscommand using NOCOPY copy type.

Explanation: It is inefficient to perform COPY orINCR type of flashcopy backup with space–efficienttarget volumes as it will force the space–efficientvolumes to grow to full size on the very first backup.Use NOCOPY copy type instead.


User response: Please retry the command usingNOCOPY copy type.

FMM5667E A Flashcopy Restore operation is inprogress between source volumesourceVolume and target volumetargetVolume. Please retry this commandafter the restore operation completes.

Explanation: It is not possible to perform otherFlashcopy backup or restore operations using thissource until the currently running FlashCopy restoreoperation completes.


User response: Please retry the command after theFlashcopy restore operation completes.

FMM5668E The input target volume targetVolume isalready in a flashcopy relationship witha volume other than the input sourcesourceVolume. Please retry this commandwith a different target volume.

Explanation: It is not allowed to use a given volumeas the target for more than one flashcopy relationship.


User response: Please retry the command using adifferent target volume.

FMM6199E Failed to determine the database id.Output of the failed command: output

Explanation: The attempt to determine the database idwas unsuccessful. Requirements for this operation are acomplete and functional database software installationand a valid control file.


User response: Check the output of the failedcommand for further information about the root cause.Resolve these issues and perform the operation again.

FMM6201I Checking status of database.

Explanation: The actual status of the database will bechecked to ensure a valid state for the subesquentoperation.

System action:


FMM6202E The log mode for this database isNOARCHIVELOG.

Explanation: The log mode for this database isNOARCHIVELOG.

System action:

User response: Change the log mode for this databaseto ARCHIVELOG.

FMM6203E The Oracle database is currently inread–only mode.

Explanation: The Oracle database is currentlydesignated as read–only. Processing stops.

System action:

User response: Remove the read–only mode of theOracle database and try again.

FMM6204E The Backup type is online but themount mode is either nomount orstartup restricted.

Explanation: The Backup type is online but the mountmode is either nomount or startup restricted.

System action:

User response: Change the mount mode to startupmount.

FMM6205I Changing Oracle mode to: mode.

Explanation: The operational mode of the Oracledatabase is changed to the named mode.

System action:


FMM6206E No table space was found for the Oracledatabase.

Explanation: No table space was found for the Oracledatabase.

System action:

User response: Make sure the correct database systemidentifier (SID) is specified.



FMM6207E Oracle database data files were notfound. More details: errormsg

Explanation: IBM Tivoli Storage FlashCopy Managerwas unable to determine the names of the data filesthat are used by the database.


User response: Check the errormsg for moreinformation about the cause of this problem.

FMM6208E Oracle database control files were notfound.

Explanation: Oracle database data files were notfound.

System action:

User response: Make sure the correct database systemidentifier (SID) is specified.

FMM6209E The database failed to shutdown duringthe flashcopy operation.

Explanation: The database attempted to shutdownbecause the backup type parameter is set to offline. Thedatabase failed to shutdown.

System action:

User response: Manually shutdown the database youare trying to back up, then run the operation again.

FMM6210E Failed to open the output file: filename

Explanation: The named output file could not beopened.

System action:

User response: Either the file doesn't exist or thepermissions are not sufficient for the requestedoperation. Check that the directory exists where anattempt is being made to access the output file and thatsufficient permissions are granted. Try again.

FMM6211E Failed to copy the database controlfile.Please check log file 'filename'.

Explanation: The Oracle database control file doesn'texist.

System action:

User response: Make corrective actions regarding theinformation to be found in the named log file and tryagain.

FMM6212I Suspend database.

Explanation: The Oracle database to be flashed isgoing to be supended.

System action:


FMM6213E An error occurred while attempting an'alter system suspend' action. Moredetails: errormsg

Explanation: An error occurred while attempting an'alter system suspend' action. Details can be found inthe named message.

System action:

User response: Make sure the Oracle database to bebacked up is running, then try to suspend the systemwith a command line invocation. If the systemsuspends successfully, run the operation again.

FMM6214I Resume database.

Explanation: The Oracle database to be flashed isgoing to be resumed.

System action:


FMM6215E An error occurred while attempting an'alter system resume' action. Moredetails: errormsg

Explanation: An error occurred while attempting an'alter system resume' action. Details can be found in thenamed message.

System action:

User response: Make sure the Oracle database to bebacked up is running, then try to resume the systemwith a command line invocation. If the system resumessuccessfully, run the operation again.

FMM6216E Failed to get Oracle version information.

Explanation: Failed to get Oracle version informationusing sqlplus.

System action:


FMM6217I Database switched to next logfile.

Explanation: The database switched to the next logfile.

System action:




FMM6218E Backup ID to delete not specified.

Explanation: To delete a backup a valid backup id hasto be specified.

System action:

User response: Specifiy a valid backup id and tryagain.

FMM6219I Backup to Tivoli Storage Manager:filename

Explanation: Backing up the named file to TivoliStorage Manager.

System action:


FMM6220E Another clone with clone database name'clone database name' is already mountedon a clone server using device class'device classes'.

Explanation: The requested 'create_clone' commandcannot continue due to another clone with the specifiedname is still mounted on a clone server using thespecified device class(es).


User response: Either issue explicitly the 'delete_clone'command to release resources on the clone server or, ifpossible, issue the 'refresh_clone' command, whichimplicitly triggers the deletion of a clone prior startinga new one.

FMM6221I Database profile: filename

Explanation: Using the named database profile.

System action:


FMM6222E Database profile 'filename' not found.

Explanation: The named database profile was notfound.

System action:

User response: Check if the named profile exists andtry again.

FMM6223I Detected control file: filename

Explanation: The named Oracle control file wasfound.

System action:


FMM6224I Create control file copy: control file

Explanation: A named Oracle control file copy will becreated.

System action:


FMM6225I Create database parameter file 'filename'from SPfile.

Explanation: A named Oracle database parameter filewill be created.

System action:


FMM6226E Default directory for database parameterfile 'filename' not found.

Explanation: The name Oracle parameter file couldnot be found within the default directory.

System action:

User response: Ensure a valid Oracle parameter fileexists in the default directory and try again.

FMM6227I Parameter 'database_control_file_restore'is set to yes in the profile. You will needto do the incomplete recovery after therestore.

Explanation: The Oracle database control file isrequested for restore.

System action:


FMM6228E The database seems to be running.Restore not possible.

Explanation: A running Oracle database was detectedand therefore a restore is not possible.

System action:

User response: Check if the started restore operationis valid. If yes, stop the running database and try again.

FMM6229I Restoring control file controlfile

Explanation: The named control file will be restored.

System action:




FMM6230I Set table space files in backup mode.

Explanation: The table space files of the participatingtable spaces will be set in backup mode.

System action:


FMM6231I End backup mode for table space files.

Explanation: The backup mode for table space files ofthe participating table spaces will be reset.

System action:


FMM6232I Looking for the latest backup.

Explanation: An attempt is being made to pick themost current valid backup image for the requestedoperation.

System action:


FMM6233I Restoring backup with ID id.

Explanation: The backup with the named id will berestored.

System action:


FMM6234E No backup found which could berestored.

Explanation: There was no snapshot backup foundwhich can be restored.

System action:

User response: Verify your environment. If one ormultiple valid snapshot backup exist and the restorestill fails, contact your IBM support personnel.

FMM6235I Deleting backup with ID id.

Explanation: The named snapshot backup is going tobe deleted.

System action:


FMM6236E Failed to delete backup with ID id.Reason: reason

Explanation: The snapshot backup with the named idcould not be deleted.

System action:

User response: Check the logs and the named output

for further information. If the problem cannot beresolved contact your IBM support personnel.

FMM6237E Backup failed. Please check RMAN log.

Explanation: The offloaded backup to Tivoli StorageManager using RMAN failed.

System action:

User response: Make corrective actions regarding theinformation to be found in the named log file and tryagain.

FMM6238E Failed to switch logfiles. This is theoutput of the failed command: output

Explanation: The command failed.

System action:

User response: Check the logs and the named outputfor further information. If the problem cannot beresolved contact your IBM support personnel.

FMM6239E Failed to detect read mode. This is theoutput of the failed command: output


System action:


FMM6240E Failed to create a pfile from spfile. Thisis the output of the failed command:output


System action:


FMM6241E The tablespace file 'filename' is a link butnot a real file.

Explanation: The named tablespace file has to be areal file. Instead, a link was detected.

System action:

User response: Verify your environment. If theproblem cannot be resolved contact your IBM supportpersonnel.



FMM6242E Raw devices are not supported.('devicename')

Explanation: Raw devices are currently not supported.

System action:

User response: For further details on this issue,contact your IBM support personnel.

FMM6243E Failed to excute sql cmd 'command' onhost 'hostname'. This is the output of thefailed command: output

Explanation: The named sql command failed.

System action:


FMM6244I Received an information message fromthe adapter: info_message

Explanation: Indicates that this information messagewas received from a device adapter.

System action:


FMM6245I source volume ID: serialnumber capacity:size

Explanation: The physical volume with the serialnumber shown has a capacity of size.

System action:


FMM6246I Total managed capacity: size

Explanation: The total amount of all physical volumesprotected by IBM Tivoli Storage FlashCopy Manager isshown.

System action:


FMM6247W No serial number has been found fordevice: devicename

Explanation: The serial number of the specified devicecould not be resolved.


User response: No serial number has been found forthe specified device. Please ensure that is available onyour host.

FMM6248W No device has been found for thecharacter device 'devicename' with majornumber 'major' and minor number'minor'.

Explanation: No corresponding device has been foundfor the character device with 'devicename'. That meansthat no corresponding hdisk has been found in the OSfor the ASM device which is matched using minor andmajor number of the device.


User response: Ensure that an hdisk exists in /devwhich has the mentioned minor and major numbers.

FMM6249W The diskgroup 'dg' contains failuregroups which are currently offline: fg.These failure groups cannot be includedin the flashcopy.

Explanation: The specified failure groups are currentlyoffline. They cannot be included in the flashcopy andare thus not counted as valid failure groups.


User response: If you have to less failure groups toperform a flashcopy you may want to bring thesefailure groups online so that they can be included inthe flashcopy.

FMM6250E Error during initialization: descritpion

Explanation: An error resulting in the nameddescription was detected during the initialization phaseof a snapshot backup.

System action:

User response: Check the logs for further information.After resolving the issue try again.

FMM6251E Error during start of backup: description

Explanation: An error resulting in the nameddescription was detected during the start of a snapshotbackup.

System action:


FMM6252E Error during partitioning: description

Explanation: An error resulting in the nameddescription was detected during the partitioning phaseof a snapshot backup.

System action:




FMM6253E Error during preparation of snapshot:description

Explanation: An error resulting in the nameddescription was detected during the preparation phaseof a snapshot backup.

System action:


FMM6254E Error during creation of snapshot:description

Explanation: An error resulting in the nameddescription was detected during the creation of asnapshot backup.

System action:


FMM6255E Error during verification of snapshot:description

Explanation: An error resulting in the nameddescription was detected during the verification phaseof a snapshot backup.

System action:


FMM6256E Error during write of meta–information:description

Explanation: An error resulting in the nameddescription was detected during write ofmeta–information assigned to a snapshot backup.

System action:


FMM6257E Error during retrieval of meta data:description

Explanation: An error resulting in the nameddescription was detected during retrieval of meta dataassigned to a snapshot backup.

System action:


FMM6258E Error during query–initialization:description

Explanation: An error resulting in the nameddescription was detected during the snapshotquery–initialization phase.

System action: Check the logs for further information.After resolving the issue try again.

User response:

FMM6259E Error during retrieval of queryinformation: description

Explanation: An error resulting in the nameddescription was detected during retrieval of queryinformation of a snapshot backup.

System action:


FMM6260E Error during end of query: description

Explanation: An error resulting in the nameddescription was detected during the end of query forsnapshot phase.

System action:


FMM6261E Error during start of restore: description

Explanation: An error resulting in the nameddescription was detected during the start of thesnapshot restore phase.

System action:


FMM6262E Error during restore: description

Explanation: An error resulting in the nameddescription was detected during the restore of asnapshot backup.

System action:


FMM6263E Error during end of restore: description

Explanation: An error resulting in the nameddescription was detected during finishing of a snapshotrestore operation.

System action:

User response: Check the logs for further information.



After resolving the issue try again.

FMM6264E Error during start of delete: description

Explanation: An error resulting in the nameddescription was detected during the start of thesnapshot delete phase.

System action:


FMM6265E Error during end of delete: description

Explanation: An error resulting in the nameddescription was detected during finishing of a snapshotdelete operation.

System action:


FMM6266E Restoring Oracle control files failed.Oracle control files are on raw volumesin the production server and those aresupposed to be created manually on thebackup server. It failed because of eithercontrol files are not created on thebackup server or created incorrectly.Please check log file 'filename'.

Explanation: On the production server the Oraclecontrol files reside on raw volumes. On the backupserver they need to be restored in order to perform thebackup to Tivoli Storage Manager. This process did fail.

System action:

User response: Examine the content of the filename. Itcontains the output from the Oracle RMAN. A possiblereason could be that the raw devices for the controlfiles have not been created on the backup server.

FMM6267E Restoring Oracle control files failed.Please check log file 'filename'.

Explanation: On the backup server the Oracle controlfiles need to be restored in order to perform the backupto Tivoli Storage Manager. This process did fail.

System action:

User response: Examine the content of the filename. Itcontains the output from the Oracle RMAN.

FMM6268W The lun 'lunname' of failure group'failuregroupname' has not been found onthe storage device.

Explanation: The specified lun has not been found onthe currently selected storage device. If it is containedin a failure group you expect to reside on the selected

storage device please ensure that is is available. If thefailure group is not contained on the currently selectedstorage device you can ignore this message.


User response: Ensure that the specified lun exists onthe storage device if you expect the failure group toreside on the currently selected DEVICE_CLASS in theprofile.

FMM6269I The diskgroup 'diskgroupname' with'redundanctype' redundancy and'failuregroupnumber' failure groups hasbeen partitioned with failure groups'failuregroupnames'.

Explanation: The specified diskgroup has beenpartitioned. In this message the found failure groupsand the total number of failure groups is mentioned. Itcan be used to check if all failure groups which wereexpected to be included in the flashcopy are listed.



FMM6270E INFILE name is required.

Explanation: For this function an INFILE name has tobe specified either in the profile or via command lineparameter.


User response: Either specify an INFILE parameter inthe client section of the profile or add parameter -I<infile name> to the command.

FMM6271W Specified partition(s) 'partition list'already offloaded to Tivoli StorageManager.

Explanation: The provided database partitions werealready offloaded to Tivoli Storage Manager. Thebackup for those partitions will not be started again.


User response: Provide different partitions to beoffloaded.

FMM6272I Update snapshot backup with ID'snapshot backup ID'.

Explanation: The usability state of the given snapshotbackup was updated successfully according theprovided state parameter.





FMM6273E Valid usability state values are 'yes' or'no'.

Explanation: An invalid value was specified for theusability state.


User response: Specify either 'yes' or 'no' as a usabilitystate value. Upper or lower case letters are allowed.

FMM6274E Operation failed because a resource istemporarily unavailable. Please restartthe operation.

Explanation: The launchpad could not fulfil theservice request due to unavailable resources.


User response: Ensure the launchpad was not stoppedin the middle of a running operation. Check the logsfor additional hints regarding the failure. Afterresolving the issue try again.

FMM6275E The requested process can currently notbe started.

Explanation: The launchpad could not fulfil theservice request due to the requested process, either formount vs. unmount or for offloaded tape backup couldnot be started.


User response: Check the logs for additional hintsregarding the failure. After resolving the issue tryagain.

FMM6276E Another mount agent service iscurrently running.

Explanation: The requested action could not be starteddue to another mount agent service (mount, unmount,tape backup) is currently running. Only one service at atime will be handled by a mount agent on a backupserver.


User response: Wait until the currently runningservice is finished and try again.

FMM6277E Partition 'partition number' is alreadyhandled by the mount agent instancerunning on 'hostname'.

Explanation: A partition can only be handled by asingle mount agent instance.


User response: Check the environment on the backupsystem(s). Make sure the partition is only associatedwith a single mount agent instance on the backup

system(s). There must be a one to one relation betweenthe mount agent and a dedicated partition.

FMM6278E No mount agent on a backup server isset up to handle partition 'partitionnumber' within the current operation.Make sure that the mount agent isstarted correctly and verify that thehostnames listed in db2nodes.cfg matchwith the hostname of the backup server.If the hostnames do not match, start themount agent with the -H hostnameoption.

Explanation: A partition was detected that will not behandled by the mount agent(s) on the participatingbackup server(s). The mount agent(s) are set up byusing the command option for partitions to be handled(-N). However, one (or more) partitions where notassigned to a corresponding mount agent. Thecorresponding mount agent is determined bycomparing the hostnames from db2nodes.cfg file (in theDB2 instance directory) with the hostname of thebackup server. This error message displays when thesehostnames do not match.


User response: Check the environment on the backupsystem(s). Make sure the partition is only associatedwith a single mount agent instance on the backupsystem(s). If the hostnames in the db2nodes.cfg file (inthe DB2 instance directory) do not match the hostnameof the backup server, start the mount agent with the -Hhostname option and specify the hostname listed in thedb2nodes.cfg file.

FMM6279E No mount agent is setup on a backupserver to handle the current operation.Make sure that the mount agent isstarted correctly.

Explanation: No mount agent (the process signatureis: acsgen -D -M) on the participating backup server(s)was detected that could handle the current operation.This can also happen if the password for authenticationto the ACS daemon was changed.


User response: Check the environment on the backupsystem(s) and make sure that the mount agent isstarted correctly. If you change the password forauthentication to the ACS daemon at the prodructionhost, then you have to change the password on thebackup host as well to match to the prodution host.

FMM6280E A usability state argument is missing.

Explanation: The 'update_status' function requires ausability state argument.




User response: Specify a usability state argument.

FMM6281E The usability state 'state' is unknown ornot supported.

Explanation: The specified usability state to beupdated is either unknown or not supported.


User response: Specify a valid usability state and tryagain.

FMM6282E query archive unsuccessful.

Explanation: The offload agent was unable to checkfor files that have already been archived before.


User response: The offload agent calls the dsmc queryarchive command which fails. Check the setup of yourBackup Archive client and try again.

FMM6283E offloaded tape backup unsuccessful.

Explanation: At least one error message occuredduring offloaded tape backup.


User response: Review the dsmerror.log file (anddsmsched.log file for scheduled events) to check forerror messages and their impact to the operation..

FMM6284W offloaded tape backup successful withwarnings.

Explanation: At least one warning message occuredduring offloaded tape backup.

System action: none

User response: Review the dsmerror.log file (anddsmsched.log file for scheduled events) to check forwarning messages and their impact to the operation..

FMM6285I Start saving file number files ...

Explanation: Tape backup processing started.

System action:


FMM6286E The clone database name 'cloneSID' hasbeen specified multiple times in theprofile. Please check the values of thekeyword 'keyword'.

Explanation: One clone database name has beenspecified multiple times for the specified profilekeyword.


User response: Just specify each clone database nameonce for the specified profile keyword.

FMM6287E The keyword 'keyword1' instead of'found_keyword' is needed for thekeyword 'keyword2'. "

Explanation: The specified keyword has beenmisspelled.


User response: Correct the specified keyword.

FMM6288E The command line option –s<DEVICE_CLASS> is not allowed forfunction function name.

Explanation: For this function the command lineoption –s <DEVICE_CLASS> is not allowed.


User response: Restart the command withoutspecifying the command line option –s<DEVICE_CLASS>.

FMM6289I The 'datastore name' data store wassuccessfully added to the 'ESX host name'ESX host.

Explanation: A data store was made available on thespecified ESX host.



FMM6290I The 'datastore name' data store wassuccessfully unmounted from the 'ESXhost name' ESX host.

Explanation: A data store has been detached from thespecified ESX host.



FMM6291E One or more Oracle control files arelocated outside ASM disk groups. Thefollowing Oracle control files are notlocated within ASM disk groups: controlfile names

Explanation: There is an unsupported configurationwith one or more Oracle control files that are locatedoutside the ASM disk groups.


User response: Reconfigure the Oracle ASMenvironment so that all control files are stored on ASMdisk groups.



FMM6292E The Oracle version of this database,version number, does not meet therequired version, 11gR2, for ASMdatabase cloning with a SID differentfrom the source database.

Explanation: To create a clone of an Oracle databaselocated on a ASM volume manager, with a SID that isdifferent from the source database, an Oracle databaseversion 11.2 or later is required.


User response: Either create a clone database that hasthe same SID as the source database, or upgrade theOracle database software to 11.2 or later.

FMM6293E You cannot rename the ASM disk groupdisk group name as it is still mounted.

Explanation: You cannot rename the mounted ASMdisk group. To rename an ASM disk group, it must bedismounted.


User response: Check why the ASM disk group ismounted. Unmount the disk group and try again.

FMM6294E Execution was stopped. ASM disk groupname disk group name on a clone systemwill exceed 30 bytes limit.

Explanation:


User response: Tivoli FlashCopy Manager can notcontinue clone operation since it should generate diskgroup name for a clone database adding_CLONEDBSID to an original disk group name andthis group name exceeds maximum allowed lenghth(30 bytes). Decrease original database ASM disk groupname or clone database SID in such way that resultingconcatination originaldbdiskgroup_cloneSID will notexceed the limit. Retry clone operation.

FMM6295E Unable to rename disk group old diskgroup name to new disk group namebecause a disk group with the newname exists already.

Explanation: When you clone an Oracle ASMdatabase the disk groups are renamed on the clonesystem to avoid name conflicts when multiple clonesare created. The current action cannot be processedbecause a disk group with the name exists.


User response: Check which database the disk groupwith the new group name belongs to. If this disk groupis a leftover from a previous cloning operation, you candelete it manually. Alternatively you can specify a

different SID for the new clone database, or move thedatabase with the disk group to another host.

FMM6501I Initializing 'function' request.

Explanation: The offload agent will be initialized for anew function request.

System action:


FMM6502I Executing 'function' request.

Explanation: The offload agent is executing a functionrequest.

System action:


FMM6503I Terminating 'function' request.

Explanation: The offload agent is terminating afunction request. This also includes a cleanup ofrequired resources.

System action:


FMM6504E The 'function' request failed.

Explanation: The request for the named functionfailed unexpectedly.


User response: See the Tivoli Storage FlashCopyManager log files on the production and backupservers for further details. The log files are in theACS_DIR/logs directory. After you resolve theproblem, start the operation again. and respond to anyerror messages found there.

FMM6505E Forced 'function' requires the instance,database, and backup ID filterarguments.

Explanation: If a function is started with the option'–F' (forced) the filter arguments for the instance,database and snapshot backup ID must also bespecified. Specifying these arguments ensures that theworkflow is applied to one specific snapshot backuponly.


User response: Specify the instance (–i), database (–d),and backup ID (–B) filter arguments.



FMM6506I Backup backup id was created withoption TSM_ONLY. It is marked fordeletion after the first TSM backupattempt.

Explanation: The backup corresponding to <backupid> has been deleted. This is because the backup wasmade with TSM_BACKUP option TSM_ONLY and theTSM backup associated with this snapshot image hasrecently completed (successfully or unsuccessfully).

System action:


FMM6507E Function 'function' is not supported.

Explanation: The function request is not supported bythe offload agent.

System action:

User response: Check the specified function.

FMM6508I Initializing partition(s) 'partitions(s)' ofdatabase 'database name' as type.

Explanation: The participating database partitions willbe initialized on the target system. Valid initializationtypes are snapshot, standby and mirror.


User response:

FMM6509E Failed to initialize partition 'partition(s)'of database 'database name'.

Explanation: The offload agent was not able toinitialize one or more database partitions.

System action:

User response: Check the offload agent log as well asthe DB2 diagnostic log (db2diag.log) for further details.

FMM6510I Partition(s) 'partition list' of database'database name' initialized successfully.

Explanation: The participating database partitionswere initialized successfully.

System action:


FMM6511E A backup–ID option must not bespecified when starting the off–loadedbackup.

Explanation: A backup ID was specified when youused the 'tape_backup' function to request anoff–loaded backup. The data to be off–loaded istypically under the control of a versioning mechanismof either the backup mover or Tivoli Storage Manager.

Backups that are queued for off–loading are processedin the order that is required by this mechanism. Aspecific backup cannot be selected for this purpose.Therefore, a specific backup cannot be selected whenyou request an off–loaded backup.


User response: Do not specify a backup ID (options–B or –T) in combination with the function'tape_backup'.

FMM6512I The 'function' request for database'database name' with partitions(partition(s)) processed successfully.

Explanation: The selected function for theparticipating partitions of a database was processedsuccessfully.

System action:


FMM6513I The resources of database 'database name'with partitions (partition(s)) are alreadymounted.

Explanation: All required file systems are alreadymounted on the target system.

System action:


FMM6514E The specified filter did not result in amatch in the snapshot repository.

Explanation: The repository does not contain asnapshot backup that can be associated with the givenfilter arguments.

System action:

User response: Check all specified filter argumentsand try again.

FMM6515E A snapshot backup currently offloadedto tape is no longer mounted.

Explanation: A tsm4acs tape_backup workflowconsists of the steps: mount, tape backup, unmount.When entering the unmount–phase, tsm4acs could notfind the snapshot backup that was just backed up totape. In principle, the tape backup might have finishedsuccessfully but some kind of a failure was detectedthat prevents the tape_backup cleanup phase fromcompleting.

System action:

User response: Check the tsm4acs log as well as theappropriate device agent log for further details.



FMM6516E Another 'function' request for a snapshotbackup is already running.

Explanation: tsm4acs has detected that anotherrequest, such as mount or tape_backup, for a snapshotbackup is running.

System action:

User response: A new tsm4acs request can only bestarted if the old request has finished.

FMM6517I A snapshot backup is already mounted.

Explanation: The tsm4acs mount–request will not beexecuted due to an already mounted snapshot backupon the offload system.

System action:


FMM6518I No snapshot backup is currentlymounted.

Explanation: The tsm4acs unmount–request will notbe executed because there is currently no snapshotbackup mounted on the offload system.

System action:


FMM6519I There is no snapshot backup currentlypending to be offloaded to tape.

Explanation: The 'tape_backup' request cannot beexecuted because there is no snapshot backup in theTAPE_BACKUP_PENDING state.



FMM6520I Starting database instance 'instance name'.

Explanation: The database instance on the targetsystem will be started.

System action:


FMM6521I Database instance 'instance name' wasstarted successfully.

Explanation: The database instance on the targetsystem was started.

System action:


FMM6522W Database instance 'instance name' alreadystarted.

Explanation: The database instance on the targetsystem is already running.

System action:

User response: The offload agent workflow shouldnot be affected. In general, no action is required.

FMM6523E Database instance 'instance name' couldnot be started.

Explanation: The database instance on the targetsystem could not be started.

System action:

User response: Check the DB2 diagnostic log(db2diag.log) for further details.

FMM6524I Stopping database instance 'instancename'.

Explanation: The database instance on the targetsystem will be stopped.

System action:


FMM6525I Database instance 'instance name' wasstopped successfully.

Explanation: The database instance on the targetsystem was stopped.

System action:


FMM6526W Database instance 'instance name' alreadystopped.

Explanation: The database instance on the targetsystem was already stopped.

System action:

User response: Check the DB2 diagnostic log(db2diag.log) for indication of whether an unexpectedfailure was the cause. Also check the tsm4acs log forindications that the workflow, which includesshutdown of the database instance on the targetsystem, reported unexpected failures.

FMM6527E Database instance 'instance name' couldnot be stopped.

Explanation: The database instance on the targetsystem could not be stopped.

System action:

User response: Check the DB2 diagnostic log



(db2diag.log) for further details.

FMM6528E The file containing the list of partitionsand hosts to be off–loaded could not becreated.

Explanation: The 'rah' host file is used by DB2 todetermine the database partitions that must beprocessed in a DPF environment. By default, this file is'db2nodes.cfg'. tsm4acs uses a temporary 'rah' host fileto be able to handle only a subset of partitions.

System action:

User response: The temporary 'rah' host file used bytsm4acs will be created under '$HOME/sqllib', where$HOME is the home directory of the DB2 instanceowner. Ensure that the appropriate permissions are setand enough free space is available.

FMM6529I Database instance 'db instance' alreadystarted.

Explanation:

System action:

User response:

FMM6530E The default database path could not bedetermined.

Explanation: The value of the default database path(DFTDBPATH) stored in the database managerconfiguration could not be retrieved.

System action:

User response: Check the DB2 diagnostic log(db2diag.log) for details. Further, verify the databasemanager configuration to be issued by the DB2 instanceowner as follows: db2 get dbm cfg | grepDFTDBPATH. Also for a more detailed analysis, enablethe trace facility for the offload agent and re–executethe function.

FMM6531I Cataloging database 'database name' onpath 'path'.

Explanation: The database on the target system willbe cataloged.

System action:


FMM6532I Database 'database name' on path 'path'cataloged successfully.

Explanation: The database on the target system wascataloged successfully.

System action:


FMM6533E Failed to catalog database 'database name'on path 'path'.

Explanation: The database on the target system couldnot be cataloged.

System action:

User response: Check the DB2 diagnostic log(db2diag.log) for further details. Additionally, for amore detailed analysis enable the trace facility of theoffload agent and re–execute the function.

FMM6534E A snapshot backup is already mounted.

Explanation: A mount–request is not executed becausea snapshot backup is already mounted on the offloadsystem.


User response: Unmount the previously mountedbackup, then start the mount request again.

FMM6535E The snapshot backup with ID 'identifier'does not qualify for restore operations.

Explanation: Due to its characteristics the specifiedsnapshot backup can not be restored. Common reasonsare the copy type of the flashcopy is NOCOPY or thebackground copy operation has not been finished yet.


User response: Use a different backup for the restoreoperation or wait until the background copy has beencompleted or use the force option to enforce a reversalof the direction of the copy relation (not supported byall storage devices).

FMM6536W The 'vm name' virtual machine is ignoredand cannot be part of the backup sinceit is not connected to the vCenter server.

Explanation: The specified virtual machine is notconnected to the vCenter server and cannot be includedin the backup. It will not be restorable.


User response: Connect the virtual machine orexclude it from the backup to get rid of this warning.

FMM6537I Database 'database name' on path 'path'already cataloged.

Explanation: The database on the target system wasalready cataloged.

System action:




FMM6539W The retry threshold for the snapshotbackup was exceeded.

Explanation: If tsm4acs is running in the daemonmode (–D), only one attempt will be made to offload atape from a snapshot backup. This restriction wasimposed to prevent an excessive number of offloadretries for a snapshot backup.

System action:

User response: A snapshot backup for which the retrythreshold was exceeded can only be offloaded to tapeusing the manual mode of tsm4acs (–f tape_backup).

FMM6540I Start time: Starting backup of database'database name', partition(s) 'partition(s)'with the following options: METHODoffload backup method SESSIONS numberof sessions OPTIONS options BUFFERSnumber of buffers BUFFERSIZE buffer sizePARALLELISM degree of DB2 parallelism

Explanation: The off–loaded tape backup was startedusing the 'db2 backup database' command. The set oflisted backup parameters gives a brief summary aboutthe options and values that were used for the backup.

System action:


FMM6541I End_time Instance Database PartitionSnapshot_ID Tape_backup_ID

Explanation: The backup is finished. A backup resulttable for all participating partitions of the database willbe generated.

System action:


FMM6542I end timeinstance namedatabasenamepartitionsnapshot idtape backup id

Explanation: One entry of the backup result tablereflects one partition of the database. The backup for adatabase partition succeeded if a valid tape backup ID(DB2 tape backup timestamp) was inserted. If the tapebackup for a partition failed, the tape backup ID is setto '–'.

System action:


FMM6543E The disks could not be attached to therequested target virtual machine: 'vmname'. Please make sure to use the ESXhost where the target virtual machine isrunning as auxiliary ESX host. ESX host'esx hostname' has been used for thisoperation.

Explanation: The disks could not be attached to thespecified target virtual machine.


User response: Ensure to use the ESX host where thespecified target virtual machine is running as auxiliaryESX host.

FMM6544I Snapshot backup suspend time: suspendtime

Explanation: The snapshot backup suspend timespecifies the minimum recovery time for allparticipating partitions.

System action:


FMM6545I Write control file ctrlfile

Explanation: The offload agent is writing the Oraclecontrol file to a local file system.

System action:


FMM6546I Write database parameter file parameterfile

Explanation: The offload agent is writing the databaseparameter file to a local file system.

System action:


FMM6547I Do not overwrite database parameterfile.

Explanation: The offload agent will not overwrite thedatabase parameter file.

System action:


FMM6548I Start backup of database instance'instance'.

Explanation: The offloaded tape backup of the nameddatabase instance was started.

System action:


FMM6549I Finished backup of database instance'instance' successfully.

Explanation: The offloaded tape backup of the nameddatabase instance finshed successfully.

System action:




FMM6550I Resetting the database logs to preparethe change of the database id.

Explanation: In order to enable the change of thedatabase id the database is brought into a consistentstate by resetting the logs.



FMM6551I Changing the database id. This will stopthe database.

Explanation: In order to create a unique clone of thedatabase the database id is going to be changed. Afterthis process the database will be stopped and may berestarted by IBM Tivoli Storage FlashCopy Manager tocontinue with further steps.



FMM6552I Successfully changed database id fromold database id to new database id.

Explanation: The database id has been changed aspart of the cloning operation. For reference the old andnew value are displayed.



FMM6553E Failed to changed database id. This isthe output of the failed command: erroroutput

Explanation: The attempt to change the database idhas failed. The output of the operation is shown belowthis message.


User response: Check the output of the failedoperation to determine the root cause. Performcorrective actions and try again.

FMM6554E The original virtual machine withinstance UUID 'target instance uuid' isneeded for this single disk restoreoperation but was not found. Pleasespecify a target virtual machine.

Explanation: The original virtual machine with thespecified instance UUID is needed for this single diskrestore operation but was not found.


User response: Specify a valid target virtual machine

or make the original virtual machine with the specifiedinstance UUID available.

FMM6555I Selected snapshot backup with ID 'id'.

Explanation: The snapshot backup with the named idwas selected to work with. The format of a snapshot idin that context is: <instance>,<database>,<timestamp>.

System action:


FMM6556E Failed to retrieve meta data.

Explanation: The metadata assigned to a snapshotbackup could not be retrieved.

System action:


FMM6557I The 'function' request for database'dbname' processed successfully.

Explanation: The offload agent has completed thenamed function successfully.

System action:


FMM6558I The resources of database 'dbname' arealready mounted.

Explanation: The offload agent has detected that allrequired resources of the named database are alreadymounted.

System action:


FMM6560E Backint could not be found at 'directory'.

Explanation: The offload agent was unable to find thebackint executable file needed for offloading the data toTivoli Storage Manager.

System action:

User response: The offload agent expects the backintexecutable at the default TSM for ERP installationlocation. Ensure that backint can be found accordinglyand try again.

FMM6561W Failed to initialize partition 'partition(s)'of database 'database name'. Restoreremaining partitions.

Explanation: The offload agent was not able toinitialize one or more database partitions.




User response: Restore the remaining partitions. If allpartitions are restored and this warning persists checkthe offload agent log as well as the DB2 diagnostic log(db2diag.log) for further details.

FMM6562I Changing the database shared memoryof partition(s) 'partitions(s)' of database'database name' to size.

Explanation: The size of the database shared memoryof the participating database partitions will be changedon the target system.


User response:

FMM6563E Failed to change the size of the databaseshared memory of partition 'partition(s)'of database 'database name'.

Explanation: The offload agent was not able to changethe size of the database shared memory one or moredatabase partitions.

System action:

User response: Check the offload agent log as well asthe DB2 diagnostic log (db2diag.log) for further details.

FMM6564I Successfully changed the size of thedatabase shared memory of Partition(s)'partition' of database 'database'.

Explanation: The size of the database shared memoryof the participating database partitions were changedsuccessfully.

System action:


FMM6565E Another operation of IBM Tivoli StorageFlashCopy Manager is preventingaccesss to this backup.

Explanation: Another operation has the access to thisbackup and it is preventing the current function to beexecut ed.


User response: Verify the summary log and retry thecall of the function.

FMM6566E The 'option' option is not supported bythe 'function' operation.

Explanation: An option that is specified in thecommand line is not supported by the operationnamed.


User response: Check the command syntax and use

only the options that are supported by the operationrequested.

FMM6567E More than one database is in thedatabase instance 'instance_name'. Specifythe name of the database to beprocessed via the '-d' option of script'fcmprereqchecker.sh'.

Explanation: If two or more databases are in thedatabase instance, the database to be processed by IBMTivoli Storage FlashCopy Manager must be explicitlyspecified.


User response: Check the command syntax andspecify the database to be processed.

FMM6568E The binary 'binary_name' was not foundin the path of the user 'username'.

Explanation: The named binary is expected in thepath of the user, but was not found.


User response: Ensure that the environment is set upcorrectly for the user ID named.

FMM6570E The 'name' name is reserved. You mustspecify another name.

Explanation: The DEVICE_CLASS section name mustbe unique therefore you cannot reuse the name of anexisting section.

System action:

User response: Choose a different DEVICE_CLASSsection name.

FMM6571E When the system was trying todetermine the database instance path, anerror occurred: error_information Checkwhether the DB2 instance is set upcorrectly.

Explanation: However, an unexpected condition wasdetected that prevented the system from determiningthe database instance path.


User response: Check the error information that isgiven in the message and resolve the problem. Restartthe operation.

FMM6572E Error code return_code was returned fromshell command 'command'. Commandoutput: command_output Output fromshell: shell_output

Explanation: A shell command ended with an error.




User response: Check the return code and thecommand and shell output information. Resolve theissue. Restart the operation.

FMM6573E No valid application environment wasdiscovered for the user 'user'.

Explanation: A valid application environment was notdetected for the user. The named user ID must be anowner of an Oracle database or of a DB2 instance.


User response: Check the environment of the user IDnamed. Check the environment for the user ID, andensure that a valid database or instance owner ispassed to IBM FlashCopy Manager PrerequisiteChecker.

FMM6574W The task progress cannot be displayedor updated because the followingproblem occurred:

Explanation: The problem indicates that the taskprogress cannot be created or updated in the vCenterServer.



FMM6575E The file 'filename' is not located in anASM disk group.

Explanation: All files belonging to an ASM databasemust be located in ASM disk groups.

System action: The layout check fails.

User response: Ensure that all files of the ASMdatabase are located in ASM disk groups.

FMM6576E Control file 'filename' is located in datafile disk group 'diskgroup'.

Explanation: Control files must be located in aseparate disk group from the data files.


User response: Ensure that control files are located ina separate disk group from the database data files.

FMM6577E Redo log file 'filename' is located in datafile disk group 'diskgroup'.

Explanation: Redo log files must be located in aseparate disk group from the data files.


User response: Ensure that redo log files are locatedin a separate disk group from the database data files.

FMM6600E Unexpected error during 'function'.

Explanation: The offload agent has terminatedunexpectedly due to an internal error while executingeither a mount or an unmount request.

System action:

User response: Check the logs of the involvedcomponents (management agent, offload agent, deviceagent) for further details and descriptions regarding thefailure.

FMM6601W The 'ds name' datastore with the 'vmnames' virtual machines is ignored andcannot be part of the backup since it hasthe type type that is not supported.

Explanation: The specified virtual machine ordatastore cannot be part of a backup.


User response: Specify a virtual machine or datastorethat has a supported type such as VMFS or NFS.

FMM6602W The virtual disk 'disk name' of the virtualmachine 'VM name' exists in a typedatastore that is not supported. Thisvirtual machine will be excluded fromthe backup.

Explanation: The specified virtual machine ordatastore cannot be part of a backup.


User response: Specify a virtual machine or datastorethat has a supported type such as VMFS or NFS.

FMM6603W The 'ds name' virtual machine is ignoredand cannot be part of the backup sinceit is a placeholder entity that ismanaged by VMWare Site RecoveryManager (SRM).

Explanation: The specified virtual machine cannot bepart of the backup operation. This virtual machine is aplaceholder that is part of a VMWare Site RecoveryManager (SRM) protection group on the protectedvCenter server.


User response: Specify a virtual machine that is notdefined as an a VMWare Site Recovery Manager (SRM)placeholder and try the operation again.

FMM6801E DB2 Library not specified

Explanation: IBM Tivoli Storage FlashCopy Managertries to load the DB2 API library specified by theDB2_LIBRARY parameter. However the value of theparameter is empty or invalid.




User response: Verify the value of the DB2_LIBRARYparameter in the profile.

FMM6802E Failed to load DB2 library 'library name'dlopen error: dlopen error

Explanation: An error occured when loading the DB2API library. A text description displays.


User response: Verify that the DB2_LIBRARY profileparameter contains the fully qualified name of the DB2API library. Evaluate the error description.

FMM6803E DB2 Library 'library name' could not beloaded.

Explanation: An error occurred when attempting toload the DB2 API library. See the previous error.


User response: See the previous error descriptions.

FMM6804E DB2 Library symbols 'library name' couldnot be loaded: rc _ return code

Explanation: IBM Tivoli Storage FlashCopy Managerwas not able to load the API functions from the DB2API library specified by the DB2_LIBRARY parameter.


User response: Verify that the DB2_LIBRARYparameter contains the correct DB2 API library.

FMM6805I The production TCP/IP node 'tcp node'will be cataloged.

Explanation: The production node directory wascataloged because it was empty or it was not found.



FMM6806E Unable to catalog production TCP/IPnode 'tcp node' as 'node alias'.

Explanation: An error occurred while cataloging thisTCP/IP node using the specified node alias. Check thedb2diag.log file for more details.

System action: Proccessing stops.

User response: Evaluate the error in the thedb2diag.log file.

FMM6807I The production TCP/IP node 'tcp node'has been cataloged successfully as 'nodealias'.

Explanation: The node was cataloged successful.

System action: Proccessing continues.


FMM6808I The production database 'database name'will be cataloged.

Explanation: The production database 'database name'will be cataloged in the database directory on thesystem.



FMM6809E Unable to catalog production database'database name' as 'new database name'.

Explanation: The database 'database name' could not becataloged as database 'new database name' on the targetsystem.


User response: Check the DB2 diagnostic log(db2diag.log) for more information regarding thisproblem. Try the operation again after resloving thecause of the error.

FMM6810I The production database 'database name'has been cataloged successfully as 'newdatabase name'.

Explanation: The database 'database name' has beencataloged as database 'new database name' successfullyon the target system.



FMM6811E Parsing error in file 'filename' at line 'linenumber' at position 'position'. Expectedone of 'valid possibilities' but found 'line'.

Explanation:


User response:

FMM6812E Unable to connect to the productiondatabase 'database name'.

Explanation: A connection to the production database'database name' was not established. This can be causedby incorrect user rights or by the database instance notbeing started.





FMM6813E Unable to disconnect from theproduction database 'database name'.

Explanation: The product was unable to disconnectfrom the production database 'database name'.



FMM6814I A attachment to the production databaseinstance 'database instance' has beenmade.

Explanation: The client has successfully attached tothe production database instance 'database instance'.



FMM6815I A connection to the production database'database name' has been made.

Explanation: The client has successfully connected tothe production database 'database name'.



FMM6816I TBS container name=tablespace containername

Explanation: The tablespace container 'tablespacecontainer name' was detected.



FMM6817E Tablespace container 'tablespace containername' is in exception state.

Explanation: The tablespace container 'tablespacecontainer name' is in a state (such as OFFLINE) thatprevents further processing.



FMM6818I Set client connection to Node 'nodenumber'.

Explanation: Connection settings for the client processusing node 'node number' are performed.



FMM6819E No data was obtained from DatabaseMonitor.

Explanation: Snapshot information from the databasemanager operational status was not collected.



FMM6820E The 'hostname' ESX server has not beenfound in the vCenter server.

Explanation: The specified ESX host cannot be foundin the vCenter server.


User response: Specify another ESX host.

FMM6821E Attachment to the production DB2instance for user user failed. Verify thatthe database manager on the productionsystem has started.

Explanation: The attachment of the instance user tothe production DB2 instance failed.

System action: Operation fails.

User response: Verify that the database manager onthe production system has started.

FMM6822E Some tablespace containers are in anexception state.

Explanation: Some DB2 tablespace containers are inan exception state.


User response: Check the db2diag.log file for moredetails about this error. Try the operation again afterthe cause of this error has been corrected.

FMM6823I The attachment to the productiondatabase instance 'database instance' hasbeen detached.

Explanation:

System action:



User response:

FMM6824I The connection to the productiondatabase 'database name' has beendisconnected.

Explanation: The connection to the productiondatabase has been disconnected.

System action: No specific system behavior.


FMM6825E A DB2 API call failed with thefollowing error: error code

Explanation: A call to the DB2 API failed. The errorcode is given with this message.

System action: Operation failed.

User response: Check the db2diag.log file for moredetails and refer to the DB2 user manual regarding thisDB2 error code.

FMM6826E DB2 Library 'library name' could not beunloaded.

Explanation: Unable to unload the DB2 library.


User response: Check the application logs anddb2diag.log files for more details about this error.

FMM6827E Tablespace 'tablespace' is in state 'state'.Snapshot backup is not possible.

Explanation: The current state of the tablespace doesnot allow a snapshot backup to occur.


User response: Change the tablespace to a NORMALor BACKUP PENDING state and run the operationagain.

FMM6828E Some tablespaces are not in 'NORMAL'state. Snapshot backup is not possible.

Explanation: A snapshot backup cannot be takenunless some tablespaces are in a NORMAL state.


User response: Change the tablespaces to a NORMALstate and run the operation again.

FMM6829I Connecting to the production database'database name' ...

Explanation: A connection to the production databasewill be established.



FMM6830I Disconnecting from the productiondatabase 'database name' ...

Explanation: Disconnecting from the productiondatabase.



FMM6831I Attaching to the production databaseinstance 'database instance' ...

Explanation: Attaching to the production databaseinstance.



FMM6832I Detaching from the production databaseinstance 'database instance' ...

Explanation: The production database instance hasbeen detached.



FMM6833E The RMAN executable was not found oris not executable by the current user.Could not verify the connection to theOracle catalog database.

Explanation: Either the current user ID is not anOracle user or the Oracle environment variables are notset correctly.

System action:

User response: Verify that you are logged in as thedatabase instance user and that your environmentvariables are correctly specified.

FMM6901I Response to Init request.

Explanation: This message indicates the progress ofthe flow within the device agent.

System action:


FMM6902I Response to Partition request.


System action:




FMM6903I Response to Prepare Flash request.


System action:


FMM6904I Response to Restore request.


System action:


FMM6905I Response to Flash request.


System action:


FMM6906I Response to Verify request.


System action:


FMM6907I Response to Complete Restore request.


System action:


FMM6908I Response to Expiration request.


System action:


FMM6909I Response to Monitor request.


System action:


FMM6910E Could not set user ID to userid. Errorerror – errormsg.

Explanation: The user id of the device agent processcould not be switched internally to the named user id.

System action:

User response: Check the permissions of the binaryand try again.

FMM6911E The effective user ID userideff of theprocess could not be set to the useruserid. Error error – error_msg. Check thatthe device agent executable has the s–bitset.

Explanation: Due to insufficient permissions of thedevice agent executable, the user id of the device agentprocess could not be switched internally to the nameduser id.

System action:

User response: Check that the device agent binary hasthe s–bit set and try again.

FMM6912E Background operation shutting down inorder to give precedence to a concurrentoperation.

Explanation: A background operation is endingbecause some interactive operation using the sameresources was started. Once the operation takingprecedence has ended, the background operation isresumed.

System action:


FMM6913E Wrong parameter provided with option'–c'.

Explanation: A program was called with anunsupported parameter value.

System action:

User response: If the program was called from thecommand line or from a script, correct the call.Otherwise, contact your IBM support personnel.

FMM6914E Invalid option '–K' specified.

Explanation: A program was called with anunsupported parameter value for the internal option'–K'.

System action:

User response: If the program was called from thecommand line or from a script, correct the call.Otherwise, contact your IBM support representative.



FMM6915E Could not change directory to path.

Explanation: An executable file needs to change to thenamed working directory, however, changing to thedirectory did not succeed.

System action:

User response: Make sure authorization is setcorrectly for the executable file to access the requiredpath.

FMM6916E Program program, function function:received signal signal, exiting.

Explanation: The program received a signal that forcesthe operation to end.


User response: Run the last operation again.

FMM6917E Failed to find volume group for file:path

Explanation: The file named could not be located. Itsfile system or volume group could not be determined.

System action:

User response: Make sure that the database meets therequirement for snapshot backups. Make sure that thedata is located on a file system under the control of thestorage device.

FMM6918E Error when reading the correlation listor during the FlashCopy of the volumepairs.

Explanation: A problem occurred either while readingthe correlation list or while flashing the volume pairs.

System action:

User response: Check the relations of the(source/target) volume pairs.

FMM6919E Failed to cancel the copy relationship ofvolume pairs: rc=return_code.

Explanation: Withdrawing the copy relations of thedetermined volume pairs failed.

System action:

User response: Check the log and trace files fordetails.

FMM6920E After 'withdraw done' was finished theupdate of the IDS repository failed:rc=return_code.

Explanation: The IDS repository could not beupdated.

System action:


FMM6921E Failed to monitor the FlashCopy.

Explanation: The task for monitoring the progress ofthe background copy process of the volume pairsfailed.

System action:


FMM6922E Failed to allocate memory.

Explanation: Not enough memory was available tocontinue processing.

System action:

User response: Ensure that the system has sufficientreal and virtual memory. Close unnecessaryapplications.

FMM6923I Object_name control object alreadyinitialized.

Explanation: The internal control object is alreadyinitialized and is used for the following process flow.

System action:


FMM6924E Failed to initialize object_name controlobject.

Explanation: The internal control object could not beinitialized.

System action:


FMM6925E Function call 'function_name' failed.

Explanation: A call to the named internal functionfailed.

System action:


FMM6926I Adding 'path' to the Disk Mapper inputlist.

Explanation: The named file is added to the DiskMapper input list.

System action:




FMM6927E Failed to find N–Series volume for file'path'. Error: error_information.

Explanation: The matching N Series volume for aspecified file could not be found due to an error.

System action:


FMM6928E File system not found. Failed to findNFS mount point for file: 'path'.

Explanation: The file system base for a mount point ofa specified file could not be found.

System action:


FMM6929E Not a file system of type NFS. Failed tofind N–Series volume for file: 'file'.

Explanation: The named file is not located on an NFSmounted file system.

System action:

User response: Make sure that the database meets therequirement for snapshot backups. Make sure that thedata is located on a file system under the control of theN Series storage device.

FMM6930E Volume information missing. Failed tofind N–Series volume for file: 'path'.

Explanation: The volume information could not becollected for the named file.

System action:


FMM6931E Function call 'function_name' failed.Error: error_information.

Explanation: A call to an internal function failed dueto the specified error.

System action:


FMM6932E Function call 'function_name' failed withrc_return_code. Error: error_information.

Explanation: A call to an internal function failed withthe specified return code due to the stated error.

System action:


FMM6933I Volume 'volume_id', snap ID _snapshot_id.

Explanation: The snap ID is associated with thespecified volume.

System action:


FMM6934I The snapshot 'snapid' was generated forthe source volume 'volname'.

Explanation: A snapshot with the name displayed wastaken from this volume. In a SAN environment, thismessage appears for each LUN thhat is involved in thesnapshot process. However, when several LUNs belongto the same volume, only one snapshot of this volumeis taken.

System action:


FMM6935I Unmounting 'mount_point'.

Explanation: Unmounting the specified mount point.

System action:


FMM6936E Failed to unmount 'mount_point'.

Explanation: Failed to unmount the specified mountpoint.

System action:


FMM6937I Mounting 'mount_point'.

Explanation: Mounting the specified mount point.

System action:


FMM6938E Failed to mount 'mount_point'.

Explanation: Failed to mount the specified mountpoint.

System action:




FMM6939I Prepare for snap restore, volume'volume_id', snap ID _ snapshot_id.

Explanation: Preparation for a snap restore of thespecified volume with the associated snap ID is beingperformed.

System action:


FMM6940I Prepare flash of group 'group_id'.

Explanation: Preparation for a snapshot copy of agroup of the specified volumes is being performed.

System action:


FMM6941I <server name><user name><separator><hwnas nseries><timeout>

Explanation: A list of storage device parameters.

System action:


FMM6942E The storage device 'number' is nothandled by this device agent.

Explanation: The specified storage device cannot behandled with this device agent.

System action:

User response: Contact your IBM support.

FMM6943I Hardware version installed:version.information

Explanation: The specified version of the installedhardware is indicated.

System action:


FMM6944I NLS and tracing are already initialized.

Explanation: The logging and tracing facilities arealready initialized and are used further internally.

System action:


FMM6945I File system 'PATH' was alreadyunmounted.

Explanation: The specified file system was alreadyunmounted.

System action:


FMM6946E The environment variable 'ODMDIR' isnot specified. Verify that the DB2registry parameter DB2ENVLISTcontains the value 'ODMDIR'. To set theDB2ENVLIST you need to issue thecommand: db2set -i <DB2 instancename> DB2ENVLIST='<current envlist>ODMDIR'

Explanation: The environment variable 'ODMDIR'must set in the user's environment where the snapshotbackup or restore is started. In general, this is the casefor default operating system installations.

System action:

User response: allations. User response: Check thetrace files where the runtime environment is written. Ifan entry for the ODMDIR environment variable cannotbe found, set it manually as described in the messagetext.

FMM6947W File system 'mount_point' is alreadymounted.

Explanation: A file system that should be mounted isalready mounted.

System action: Operation continues.


FMM6948E The container 'container' has alreadybeen created. Please specify anothername.

Explanation: A container with the specified namealready exists. Container names must be unique.


User response: Specify a unique container name.

FMM6949E Creation of the container 'container'failed because no preceding group hasbeen found, or the preceding group isnot valid. Current group is: 'group'. Firstspecify a valid group using the'command' command.

Explanation: Acsgen received a new containermessage but did not receive the required GROUPinformation.


User response: Group information needs to beprovided using the GROUP command before thecontainer information is provided.



FMM6950W The output file 'path' is not valid.

Explanation: The device agent's log file could not becreated. The messages will be logged to STDOUT aswell as to the acsd log file.

System action:

User response: Check the permissions of thedirectories and that there is enough free space in thefile system. Check the acsd log and trace files fordetails.

FMM6951E Version mismatch error. Please checksetup (version:information).

Explanation: The versions of acsd and the deviceagent are different.

System action:

User response: Check the log and trace files fordetails. If the problem cannot be resolved, contact yourIBM support.

FMM6952E Error in connection to IBM TivoliStorage FlashCopy Managermanagement agent.

Explanation: The IBM Tivoli Storage FlashCopyManager management agent (acsd) could not bereached from within the device agent.

System action:


FMM6953E Error while parsing path script. Thekeyword 'keyword' is not supportedduring function_name.

Explanation: The script could not be parsedsuccessfully due to an incorrect keyword for the givenaction.

System action:

User response: Check the indicated script.

FMM6954E Error while parsing script. The keyword'keyword' is not supported.

Explanation: The script could not be parsedsuccessfully due to an incorrect keyword.

System action:

User response: Check the indicated keyword.

FMM6955E 'container_id' is not a valid container.Please specify a valid container.

Explanation: Error in communication protocolbetween the device agent and the storage deviceadapter.

System action:


FMM6956E The usability state 'usability_state' is notsupported.

Explanation: Error in communication protocolbetween the device agent and the storage deviceadapter. The given usability state <usablility_state> isnot valid.

System action:


FMM6957E Script has continued without waiting.

Explanation: The script should wait before continuingexecution.

System action:


FMM6958I Output from script:

Explanation: The output of the script.

System action:


FMM6959I Script 'path' returned with codereturn_code.

Explanation: The indicated script returned with thespecified return code.

System action:


FMM6960E Non–zero return code from script 'path'.

Explanation: The script returned with a non–zeroreturn code, which could indicate a warning or anerror.

System action:




FMM6961E Specify a script for removing data.

Explanation: To remove data, you must specify ascript.

System action:

User response: Create and specify an appropriatescript.

FMM6962I Response to File System Service request(request).

Explanation: A file system service request (request) ishandled by the device agent and a response message issent back to the management agent.

System action:


FMM6963I Performing snapshot of the sourcevolume 'source volume'.

Explanation: This message reports that a newsnapshot operation is in progress.

System action:

User response: Watch for additional messagesregarding the success of the snapshot operation.

FMM6964I Number of volumes to be processed bysnapshot: 'number'.

Explanation: The number of volumes to be processedby FlashCopy

System action:


FMM6965I Snapshot started ...

Explanation: The command with the 'flashcopy'function has been issued on the production system, andthe program splitint waits until this action has finished.

System action:


FMM6966I Snapshot successful.

Explanation: The command for the snapshot–basedcopy of the volume pairs has completed successfully onthe production system.

System action:


FMM6967E The directory directory has nested mountpoints that are stored on more than onevolume group. This is currently notsupported.

Explanation: The application sent a request torecursively backup all data stored beneath <directory>.IBM Tivoli Storage FlashCopy Manager cannot fulfillthis backup request because the data stored in thisdirectory path resides on file systems that are stored onmultiple volume groups. This is currently notsupported.

System action:

User response: Migrate the data underneath<directory> to a single file system or migrate the filesystems mounted underneath this directory tree to acommon volume group. Note that the directorystructure could also contain links to files residing inother file systems. In this case you might be able toresolve this problem by simply removing those links.

FMM6968E 'command_1' is not a valid keyword,expected 'command_2'.


System action:


FMM6969E Found non–database files on the filesystems to restore. Please provide anegative list or perform restore withoption 'no_check' to allow overwritingthose files.

Explanation: Although the previously mentioned fileswere not requested to be restored, they would beoverwritten, because they reside on a file system thatwill be entirely overwritten during restore. In order toallow overwriting those files during restore they needto be added to a 'negative list' or the checking toprevent files from being overwritten needs to bedisabled.

System action:

User response: Edit the 'CLIENT' section of theprofile. You can either set the parameter'NEGATIVE_LIST' to 'NO_CHECK', to allow IBM TivoliStorage FlashCopy Manager to overwrite any fileresiding on a file system that will be restored, or youcan set the parameter 'NEGATIVE_LIST' to point to afile (the 'negative list') which contains a list of all filesand directories that are allowed to be overwritten. Anydirectory you add to the 'negative list' is processedrecursively.



FMM6970I Snapshot restore successful.

Explanation: The snapshot restore of a snapshotbackup finished successfully.

System action:


FMM6971E Adding the key 'key' to the container'container' failed because it alreadyexists. Please use the 'command'command if you want to update the key.


System action:


FMM6972E Updating the key 'key' in the container'container' failed because it does notexist. Please use the 'command' commandif you want to add the key.


System action:


FMM6973E The group 'group' has already beencreated. Please specify another name.


System action:


FMM6974E 'group' is not a valid group. Pleasespecify a valid group.


System action:


FMM6975E Adding the key 'key' to the group 'group'failed because it already exists. Pleaseuse the 'command' command if you wantto update the key.


System action:


FMM6976E Updating the key 'key' in the group'group' failed because it does not exist.Please use the 'command' command ifyou want to add the key.


System action:


FMM6977E The #'first_command' 'parameter' commandhas to be preceeded by a#'second_command' command.


System action:


FMM6978E 'command' is not a valid keyword whenupdates to containers and groups areexpected.


System action:


FMM6979E Script has continued without waiting.Expected output 'command' from scriptbut was: 'output'.


System action:


FMM6980W Received a warning from the adapter:warning

Explanation: A warning message has been receivedfrom the storage device with the parameters:<warning>.

System action:

User response: Check the content of the warning.



FMM6981E Received an error from the adapter: error

Explanation: An error message has been received fromthe storage device with the parameters: <error>.

System action:

User response: Check the content of the errormessage.

FMM6982W The script 'adapter_name' returned withcode 1. The logfile might contain furtherwarnings.

Explanation: The storage device adapter had a returncode of 1.

System action:

User response: Please check the device agent logfilefor further warnings.

FMM6983E The following backup items were notassigned to corresponding snapshotitems: backup_items

Explanation: Backup items are storage elements suchas LUN identifiers on storage area network (SAN) ornetwork share paths on network-attached storage(NAS). Backup items are identified by IBM TivoliStorage FlashCopy Manager OS agent "acsgen" and arebased on the backup procedure of the application thatrequests the backup or restore operation. A snapshotitem is the smallest entity identifiable in a snapshot.Backup items either all or a subset are assigned to thecorresponding snapshot items. A subset is assigned inan AIX LVM mirroring or Oracle ASM environment.


User response: Evaluate the storage adapter-specificmessages to resolve the problem.

FMM6984E Error during prepare phase. Nothingknown about group 'group_name'. It hasnot been created in the partition phase.


System action:


FMM6985E Unable to connect to the copy servicesservers 'server name' and 'backup servername'.

Explanation: The attempt to connect to the storagedevice failed for both the primary and the secondaryserver.

System action:

User response: Verify that the storage device isoperational and accessible to the network. Make surethere are no firewall issues. Verify that the profilesettings for theCOPYSERVICES_PRIMARY_SERVERNAME andCOPYSERVICES_SECONDARY_SERVERNAMEparameters are valid.

FMM6986E No matching target LUNs could befound in the selected target set for thesource volumes 'volume list' .

Explanation:

System action:

User response:

FMM6988I Executed command: 'command'

Explanation: Shows the command executed in the log.


User response: Not needed.

FMM7048I The default port to connect toserver_name will be used.

Explanation: A server port for the connection to thenamed server was not explicitly specified. Therefore,the default port is used.

System action:

User response: Make sure the named server islistening to the default port. In the case of connectionfailures, specify the server port in the profile.

FMM7049I The default for environment variablePROLE_PORT will be used.

Explanation: The port for the internal communicationof Data Protection for SAP is set during installation.The message indicates that this port is being used.

System action:


FMM7050E The 'datastore name' datastore has notbeen found in the datacenters definedin the domain. It is not part of thebackup.

Explanation: The specified datastore has not beenfound in the datacenters that are defined for the currentdomain. It will not be included in the backup and notbe restorable.


User response: If the specified datastore is to be



included in the backup extend the domain to thedatacenter where it resides.

FMM7051E The environment variableXINT_PROFILE is not set. It must be setand contain the fully qualified path tothe *.utl file to be used.

Explanation: The way Data Protection for SAP worksis specified in a profile. When called, Data Protectionfor SAP looks for the environment variableXINT_PROFILE which must contain the fully qualifiedpath to the profile.

System action:

User response: Check the environment forXINT_PROFILE of the user who started Data Protectionfor SAP.

FMM7052E Only one line of effective input isallowed in the input file 'input filename'for the requested operation.

Explanation: Only one line of effective input isallowed in the input file for the requested operation.


User response: Reduce the number of effective lines inthe input file to one.

FMM7053E Service setup failed due to previouserror.

Explanation: Initialization of the product failed due toprevious errors.

System action:

User response: Check the product log file for furtherdetailed messages.

FMM7054I The datastore pattern 'datastore pattern'will be expanded within the defineddomain.

Explanation: The specified datastore pattern will beexpanded within the defined domain. Datastores thatmatch the pattern but are outside of the domain willnot be considered.


User response: Not needed.

FMM7055E Service open failed due to previouserror in data mover.

Explanation: The command could not be started dueto previous errors.

System action:


FMM7056E Service open failed because configuredTSM server could not be accessed.

Explanation: The command could not be startedbecause the TSM server defined in the profile could notbe accessed.

System action:


FMM7057E Service open failed because allconfigured sessions are currently in use.

Explanation: The command could not be startedbecause all configured sessions in the profile arecurrently in use.

System action:

User response: With Oracle RMAN the number ofchannels configured either in SAP profile or the RMANscript must be less or equal to the maximum number ofallowed sessions (MAX_SESSIONS). If multiple serversare used see the User's Guide for further details. Alsocheck the Data Protection for SAP log file for furtherdetailed messages.

FMM7058E Service open failed because more thanone file was found with the same name.

Explanation: The command could not be startedbecause two or more files with the same name werefound.

System action:


FMM7059E Service open failed because the file wasnot found.

Explanation: The command could not be startedbecause a file specified was not found.

System action:


FMM7060I Data Protection for SAP(R)version.release.modification.level (buildbuild_number)beta build_date session:process id

Explanation: This message is to verify the version ofthe shared library used for backup. On UNIX andLinux systems this message will be written multipletimes into the log per backup depending on the RMAN



setup. On Windows, it is written just once.

System action:

User response: None, if the right version is used. Ifthe version within the log does not match the installedversion, see 'RMAN Problem Resolution' in the DataProtection for SAP(R) Installation and User's Guide.

FMM7061I Continuing to restore from next datacopy.

Explanation: A saved data copy could not be restoredfrom the primary data source. Due to multiple datacopies available, the unit will switch to the nextavailable data copy and continue to restore.

System action:

User response: Although the data could be restored itshould be investigated, why one of the data sourceswere not available.

FMM7062E To create number_copies redo log copiesat least number_sessions sessions andnumber_mgmtclasses differentBRARCHIVE management classes arerequired. But currently onlyconfigured_sessions sessions are available.

Explanation: If each redo log file should be storedmultiple times then for each copy a dedicated sessionand management class at the Tivoli Storage Managerserver is required. Currently there are more redo logcopies requested with the profile parameterREDOLOG_COPIES than sessions and/or managementclasses are available.


User response: Check the profile parameterMAX_ARCHIVE_SESSIONS or if not set check thevalue of parameter MAX_SESSIONS. Increase the valueto be at least as large as number_copies. Ensure theoverall number of sessions and management classesthat are configured over all server stanzas in the DataProtection for SAP profile is at least as large asnumber_copies.

FMM7063W The profile parameterBACKUPIDPREFIX is no longer validfor Data Protection for SAP HANA andwill be ignored.

Explanation: Starting with version 6.4.1.1 it is nolonger possible to specifiy the backup ID prefix forData Protection for SAP HANA. The first six charactersof the backup ID are now generated automatically.


User response: Remove the parameterBACKUPIDPREFIX from the profile.

FMM7064W Seems the previous operation was notcompleted successfully. Cleaning up.

Explanation: Internal states indicate that an operationis still running while a new one has started. This maybe caused by database processes that did not terminatecorrectly. Data Protection for SAP is going to clean upthese internal states to avoid potential problems.


User response: Check if any database processes fromprevious backup or restore operations are still active.Consult the users guide of the database about how toclean up such processes.

FMM7065W The executable 'executable_name' wascalled using the obsolete functionspecification 'obsolete_function'. You mustuse the updated function specification'-f function' instead.

Explanation: An operation was started using anobsolete function. The obsolete function is accepted, butit will be rejected in a future release of the product.


User response: For future operations, use the updatedfunction specification that is identified in the message.

FMM7301W Data exchange file from Data Protectionfor Snapshot Devices for SAP, filenamedoes not exist.

Explanation: The referenced file is expected by DataProtection for SAP(R) to exist and to containinformation from Data Protection for Snapshot Devicesfor SAP(R) about the actual snapshot operation.

System action:

User response: The absences of this files indicates aproblem during the snapshot operation performed byData Protection for Snapshot Devices for SAP(R). Pleasecheck the logs of DP for Snapshot Devices for SAP(R)to determine the cause of the problem and try again.

FMM7302W The 'vm template name' virtual machinetemplate with the 'vm instance uuid'instance UUID is ignored and is notpart of the backup since it is a template.

Explanation: The specified VM template is not part ofthe backup and will thus not be restorable.





FMM7303W Profiles for Data Protection for SnapshotDevices for SAP are different. backup:file name backup restore: file name restore

Explanation: During backup the profile used by DPfor Snapshot Devices can be determined automatically.For restore and inquire operations the profile for DP forSnapshot Devices must be specified in the profile usingthe parameter FCS_FILE. For restore DP for SnapshotDevices must use the same profile as for backup.

System action:

User response: Correct the entry for the FCS_FILEparameter in the profile (init<SID>.utl).

FMM7304I Performing DISK ONLY backup.

Explanation: The data for this backup is stored onsnapshot–type disks only and will not be sent to TSM.

System action:


FMM7305E Error during call to Data Protection forSnapshot Devices for SAP: error message

Explanation: DP for Snapshot Devices could notprocess the requested operation successfully. Processingmay not stop at this point. Depending on the type ofrequest (backup to both TSM and snapshot disks or tosnapshot disks only, restore of data which is availablein both modes) there are possibilities to recover fromthis error and continue operation.

System action:

User response: Use the information from error messageand the output of DP for Snapshot Devices todetermine the cause of the problem and try again.

FMM7307W Data Protection for Snapshot Devicesfor SAP reported an error during asnapshot–type operation. Do you wantto continue backing up to TSM?

Explanation: The backup was requested to be storedon both the TSM server and the snapshot–type disks.The snapshot operation has failed. Backup can continueto save data on the TSM server only.

System action:

User response: Enter 'stop' if you want to solve thecause of this error and to try again. Enter 'cont' if youwant to save this data on the TSM server only.

FMM7308E DISK ONLY backup has failed.

Explanation: The current backup tried to store data onsnapshot–type disks only and did not finishsuccessfully.

System action:

User response: Check the output from DP forSnapshot Devices prior to this error message to detectthe root cause of this error and try again.

FMM7309W Data Protection for Snapshot Devicesfor SAP reported an error during asnapshot–type operation. Do you wantto continue restoring from TSM?

Explanation: The data you wanted to be restored islocated on the TSM server and on snapshot–type disks.The snapshot operation has failed. The process cancontinue to restore data from the TSM server.

System action:

User response: Enter 'stop' if you want to resolve thecause of this error and to try again. Enter 'cont' if youwant to restore from the TSM server.

FMM7310W Data Protection for Snapshot Devicesfor SAP reported an error during asnapshot–type operation. CAUTION:Not all filesystems are available. Do youwant to retry the operation?

Explanation: In contrast to message FMM7309W notall file systems are mounted. In this case it is notpossible to continue the restore from the TSM server.

System action:

User response: Enter 'stop' if you want to terminatethis restore process. Enter 'cont' if you want to retry thesnapshot process.

FMM7311I Profile used by Data Protection forSnapshot Devices for SAP: profile name.

Explanation: The message shows the name of theprofile used by DP for Snapshot Devices.

System action:


FMM7312W Profile for Data Protection for SnapshotDevices for SAP not specified in profile.For restore this must be specified.

Explanation: For restore and inquire operation inconjunction with DP for Snapshot Devices thisparameter is mandatory. Without this parameter arestore using DP for Snapshot Devices is not possibleand Data Protection for SAP will continue toinquire/restore from the TSM server only.

System action:

User response: Add the parameter FCS_FILE to theData Protection for SAP profile.



FMM7313W Inquire results from Data Protection forSnapshot Devices for SAP are notavailable.

Explanation: Data Protection for SAP queried DataProtection for Snapshot Devices for SAP for existingsnapshot backups. This query has failed.


User response: If Data Protection for SAP is runningin unattended mode (profile parameter BATCH set toYES), it immediately restores from tape when data isavailable. Otherwise you are prompted whether torestore from tape.

FMM7314E The data you want to restore is notavailable on the TSM server.

Explanation: Data Protection for SAP(R) was unableto retrieve information from DP for Snapshot Devicesabout available backups on snapshot–type disks. Thismessage may be issued in consequence of messageFMM7305E.

System action:

User response: Check the output from DP forSnapshot Devices to determine the cause of the errorand try again.

FMM7315W The copy process for the files you wantto restore is not finished. If youcontinue the operation, the files will berestored from the TSM server.

Explanation: The snapshot process running in thebackground has not finished moving the files from thesource to the target volumes. A snapshot restore ofthese volumes is currently not possible.

System action:

User response: After that message you will be asked ifyou want to continue or stop this operation. If youwant to wait until the snapshot process has finishedchoose 'stop' and the restore attempt will terminate. Ifyou choose 'continue' an attempt is made to restore thedata from TSM if available.

FMM7316I The following backup types for theBACKUPID backup id have been found:– TSM – Snapshot

Explanation: The backup for the backup ID Backup IDwas stored on the Tivoli Storage Manager as well as onsnapshot–type disks. For restore both data sources canbe used.

System action:


FMM7318E The Data Protection for SnapshotDevices for SAP profile file name is notvalid.

Explanation: The profile for DP for Snapshot Devicesspecified in init<SID>.utl could not be accessed.

System action:

User response: Check the file name and thepermissions for this file and try again.

FMM7319I Start TSM restore.

Explanation: The restore uses data from Tivoli StorageManager.

System action:


FMM7320I Start restore from snapshot.

Explanation: The restore is using data fromsnapshot–type disks.

System action:


FMM7321E The Data Protection for SnapshotDevices for SAP profile file name foundin parameter FCS_FILE of the DP forSAP(R) profile can not be used torestore this backup.

Explanation: In the Data Protection for SAP profile theFCS_FILE parameter is set. However, the profile is nota Data Protection for Snapshot Devices for SAP profile,or the profile does not point to the same DataProtection for Snapshot Devices for SAP configurationfile which was used by the preceding Data Protectionfor Snapshot Devices for SAP splitint operation.

System action:

User response: Check the FCS_FILE parameter toensure that a valid Data Protection for SnapshotDevices for SAP profile is used. The configuration filemust be the same configuration that Data Protection forSnapshot Devices for SAP used when running itssnapshot function in the preceding brbackup task. Thefile names are listed in preceding message FMM7303W.

Verify that all SAP profiles used by Data Protection forSnapshot Devices for SAP point to the same controlfile. The control file is defined by the value of theIDS_CONTROL_FILE parameter in the Data Protectionfor Snapshot Devices for SAP profile.



FMM7322E Request for a partial restore or restorefrom snapshot with "brrestore –m all" isnot supported. In case of brrestoreattempt rerun with –m full.

Explanation: DP for Snapshot Devices can only restorethe whole content of a backup and not only a subset ofa disk backup as requested. Most likely this is causedby running brrestore with the option '–m all'.

System action:

User response: Restore complete backups only: runbrrestore with the option '–m full'.

FMM7323W Request for a partial restore or restorefrom snapshot with "brrestore –m all" isnot supported. If you want to restore thebackup: – with FlashCopy restore enterstop and rerun brrestore with "–m full"– from TSM enter cont

Explanation: This message has the same reason asmessage FMM7322E, but in this case the data is alsoavailable from the TSM server. So you may continue torestore this data without the snapshot functionalityfrom TSM server.

System action:

User response: Enter 'stop' if you want to try torestore a different set of files. Enter 'cont' if you want torestore this data from TSM server.

FMM7324E Restore of multiple backup ID's in onerun from a snapshot is not possible.

Explanation: The data requested for this restorebelongs to multiple backup IDs.

System action:

User response: Make sure the files you want to restorebelong to one single backup ID and try again.

FMM7325E Redirected restore from a snapshot isnot possible.

Explanation: A restore of a snapshot to a differentlocation on the same host was attempted. This is notsupported.


User response: Either restore the snapshot to theoriginal location or restore from tape (if available).

FMM7535W Error while executing command. Reason:errno(error number) explanation

Explanation: A command could not be executedsuccessfully.

System action:

User response: Check the explanation explanation andthe preceding output of the command execution todetect the cause of the error.

FMM7536I Execute command 'command name':

Explanation: The command command name is executedby the application. This message is followed by theoutput of the command executed.

System action:


FMM7540E None of the INCREMENTAL_LEVELparameters specified in the profile canbe used for the current operation.

Explanation: The application of a'INCREMENTAL_LEVEL' entry within the profile canbe restricted by a number of optional conditions, e.g.by time frame. If this error occurs none of theINCREMENTAL_LEVEL entries within the profilematches the conditions currently given (current time,given weekday).

System action:

User response: Check the conditions specified for the'INCREMENTAL_LEVEL' entries within your profile. Itneeds to be ensured that exactly one entry matches anyimaginable condition at any time.

FMM7541E The environment variable ORACLE_SIDmust be set.

Explanation: The current operation requires theenvironment of the Oracle database instance owner.Among other settings this includes the environmentvariable ORACLE_SID.

System action: Operation aborts.

User response: Ensure the operation is performed bythe Oracle database instance owner and verify that theenvironment for this user is set correctly. Among otherenvironment variables that are required to run anOracle database the variable ORACLE_SID must be set.

FMM7542I A level number incremental backupusing Oracle RMAN has started.

Explanation: Oracle RMAN will be started to performan incremental backup with the specified level.





FMM7543I Recreate database control file 'file_name'.

Explanation: CURRENTLY UNUSED



FMM7544E The copy of the database control file'file_name' was not found.

Explanation: The current operation does expect a copyof the database controlfile to be at the specifiedlocation. This file is created by IBM Tivoli StorageFlashCopy Manager before Data Protection for SAP isstarted. But the file was not found.


User response: Verify that the target directory doesexist and is not full. Make sure that the directory is notcleaned automatically at the time of the operation.

FMM7545I Please enter the password for the user'user_name' to connect against therecovery catalog database'catalog_database_identifier':

Explanation: Oracle RMAN stores information aboutall backups in a recovery catalog database. Theidentifier to connect against this database and the userid for this connection must be specified in the profile.The password for this connection must be specifiedafter this prompt. It is then stored encrypted in theconfiguration file.

System action: Wait for user response.

User response: Enter the correct password.

FMM7546E Failed to verify the password. This isthe output of the failed command:

Explanation: The verification of the password enteredhas failed. This may be due to missconfiguration of theconnection to the recovery catalog database or just bymisstyping the password.


User response: Check the further ouput to find theroot cause. Retry the operation and enter the correctpassword.

FMM7547E Failed to verify the password. This isthe output of the failed command:

Explanation:


User response:

FMM7548E Incremental backups require IBM TivoliStorage FlashCopy Manager V3.1 orhigher.

Explanation: To perform offloaded backups usingOracle RMAN the offload operation must be performedusing IBM Tivoli Storage FlashCopy Manager Version3.1 or higher.


User response: Ensure the required version of IBMTivoli Storage FlashCopy Manager is installed andconfigured.

FMM7549E Database 'identifier' is still running onhost 'host_name'.

Explanation: Another instance of the database wasfound to be running on the backup server where theoffloaded backup should be performed.


User response: Verify the configuration if theoffloaded backup was attempted on the correct backupserver. Check if the running database instance is aleftover from a previous backup attempt. In this casemanually shutdown the instance and retry.

FMM7550E Operation was cancelled by OracleRMAN. Please check the log for moredetails.

Explanation: The operation was cancelled by OracleRMAN.


User response: Check the log output preceeding thismessage for more details about the root cause of thiserror.

FMM7551E Failed to determine the database ID:

Explanation: The process failed to determine the id ofthe database in the recovery catalog database.


User response: Check the log output following thismessage for more details about the root cause of thiserror.

FMM7552E Failed to determine the SCN:

Explanation: The process failed to determine therestore point in time in the recovery catalog database.


User response: Check the log output following thismessage for more details about the root cause of thiserror.



FMM7553I Restoring files from backup with IDbackup_ID using Oracle RMAN ...

Explanation: Oracle RMAN was started to restore alldatafiles from the backup identified by backup_ID.



FMM7554E The password to connect against therecovery catalog database 'identifier' isnot set.

Explanation: The password for the recovery catalogdatabase was not found in the config file. It is stored inencrypted form in the config file. To store the passwordin the config file the function '$ndash;fcatalog_password' must be used.


User response: Run 'backint –p <profile> $ndash;fcatalog_password' to store the password in the configfile. Then retry the operation.

FMM7555E Files from different RMAN backups cannot be restored within a singleoperation.

Explanation: The current operation attempted torestore files that have been stored by RMAN indifferent backups. This type of restore is not supported.


User response: If files from different backups arerequired only the files from one backup can be restoredat a time. Restore files from other backups in separateruns.

FMM7556E Restore of RMAN backups to a differentlocation is not supported.

Explanation: The current operation attempted torestore database files to a location that is different fromthe location at backup time. This type of restore is notpossible with backups that have been performed byOracle RMAN from a flashcopy backup.


User response: Restore the files to the same locationfrom where they have been backed up. If you wantcreate a clone of the database, use the $longfcm;cloning functionality.

FMM8201E SIMULATION CANCELED BYPRODUCTION OPERATION!!!

Explanation: The current operation was a simulationperformed via the Administration Assistant. Thissimulation was canceled since a production operation(backup or restore) has been started.

System action:

User response: Check your backup schedule and runsimulations only when no other operations arescheduled.

FMM8202E There are no target sets specified in thevolumes file that can be used with devicesection and parameter 'value'.

Explanation: The volumes file (specified with theVOLUMES_FILE parameter in the device section) doesnot contain a target set definition which can be used ina context where parameter is set to value.


User response: Add target set definitions to thevolumes file (specified with the VOLUMES_FILEparameter) that are appropriate for the context.

FMM8203E There are no volume sets specified inthe volumes file that can be used with'device class' and STORAGE_SYSTEM_IDset to 'hardware id'.

Explanation: The volumes file (specified with theVOLUMES_DIR parameter in the device section) doesnot contain a volume set definition for a storage deviceidentified with hardware id.


User response: Add an appropriate volume setdefinition to the volumes file or update and identify anexisting volume set for use with the specified hardwareID.

FMM8204E All volume sets that are specified in thevolumes file identified in 'device class'require that the parameterSTORAGE_SYSTEM_ID also bespecified in the device section of theprofile.

Explanation: A STORAGE_SYSTEM_ID is specified forall volumes sets in the volumes file (specified with theVOLUMES_DIR parameter in device section). This istypically the case in mirroring environments. In thissituation, the STORAGE_SYSTEM_ID parameter mustalso be specified in the device class.


User response: In mirroring environments, add theSTORAGE_SYSTEM_ID parameter to the device class.In non-mirroring environments, you can remove theSTORAGE_SYSTEM_ID parameter from the volumesset definition.



FMM8205E There are no target sets specified in thevolumes file that can be used with devicesection .

Explanation: The volumes file (specified with theVOLUMES_FILE parameter in the device section) doesnot contain a target set definition.

System action: Command will fail

User response: Add target set definitions to thevolumes file specified with the VOLUMES_FILEparameter.

FMM8206W The parameter profile parameter refers tothe device class section(s) 'device class'which do not exist currently in theprofile. Currently existing device classsections are: 'existing device class' If youproceed the missing device classsections are added to the profileautomatically. If this is not intended,you must modify the specified deviceclass names.

Explanation: The specified profile parameter isreferring to one or multiple device class sections thatare not specified in the profile.


User response: You must add the missing device classsection to the profile or adjust the specified profileparameter.

FMM8207E Directory target dir does already exist. Toperform IBM Tivoli Storage FlashCopyManager tape backup this directorymust not exist. After deleting thisdirectory run an unmount and performthe tape backup again.

Explanation: During tape backup process the path ofthis directory is required to set up backup DB2properly

System action:

User response: Delete the directory. Afterwards runfcmcli -f unmount to clean up the backup system. Startfcmcli -f tape_backup again.

FMM8268E The database resides on'database_volume_mgr' volumes but theprofile specifies 'profile_volume_mgr' asthe volume manager.

Explanation: The files to be backed up were found ona volume manager that is different from the volumemanager specified in the profile.


User response: Specify the correct volume manager inthe profile.

FMM8300I Function_name returned with codereturn_codereturn_information.

Explanation: This message indicates that the namedAPI function ended with the specified returninformation.

System action:

User response: If the return information indicates aproblem, look for preceding error messages in the logfiles. Otherwise, no response is required.

FMM8301E Product_name: Exception caught infunction function_name. Errorinformation: 'error_information'

Explanation: The named product implementing theDB2 Advanced Copy Services API received an error inthe named API function. The error information isshown.

System action:

User response: Analyze the error information to findthe cause of the problem. Resolve any problemsindicated.

FMM8302E Product_name: Exception caught infunction function_name. Moreinformation may be available in filelog_file_name. Error information:'error_information'


System action:

User response: Analyze the error information and theappropriate log files to find the cause of the problem.Resolve any problems indicated.

FMM8303E No segment_name section found for theinstance 'id'.

Explanation: An error was detected while parsing thenamed profile segment name section.

System action:

User response: Check the named profile segmentname section and make appropriate adjustments.



FMM8304W The following error occured whileverifying the configuration for section'section':

Explanation: An error was detected while parsing thenamed profile section.

System action:

User response: Check the named profile section andmake appropriate adjustments.

FMM8305E Invalid option option in options string:'options_string'.

Explanation: An invalid option was found whileparsing the options string specified in the 'db2'command.

System action:

User response: Correct the command and try again.

FMM8306E The keyword keyword is not allowedmultiple times within the profile.

Explanation: The keyword indicated was found morethan once in the profile. However, this keyword mustnot be specified multiple times.

System action:

User response: Correct the profile.

FMM8307E The parameter keyword must be specifiedin the profile.

Explanation: A required keyword is missing in theprofile.

System action:


FMM8308E Single argument required for parameterkeyword.

Explanation: The keyword indicated requires a singlevalue. However, two or more values are found in theprofile.

System action:


FMM8309E Missing argument for parameterkeyword.

Explanation: In the profile, a value is missing for thenamed parameter.

System action:


FMM8310E The keyword keyword is not allowed.

Explanation: An invalid keyword was detected in theprofile.

System action:


FMM8311E For parameter keywortd, both server andport must be specified.

Explanation: A value of the named parameter ismissing from the profile.

System action:

User response: As the value for the specifiedparameter, specify both server and port.

FMM8312E Error while parsing parameter keyword.In order for 'value1' to be valid 'value2' isrequired to be an existing directory.

Explanation: Value1 was found to be an invalid valuefor the parameter named. For this specific parameter, afile name can be specified whose path must alreadyexist in the system.

System action:

User response: Specify the name of a file in anexisting path.

FMM8313E Product_name: interface problem infunction function_name: Invalid value ofparameter: value

Explanation: The named product detected an interfaceproblem in the named API function. An invalid valuewas found for parameter in one of the API datastructures.

System action:


FMM8314E Product_name: interface problem infunction function_name: The session isalready in use by a different operation.

Explanation: The named product detected an interfaceproblem in the named API function. Either the sessionhandle is used for various operations simultaneously,or the functions are called in an order not supported bythe current version of the library.

System action:




FMM8315E Function_name: The following object isnot under the control of product_name:path

Explanation: The named product implementing theDB2 Advanced Copy Services API detected a problemin the named API function: The path passed by thedatabase is not under the control of the product.

System action:

User response: Make sure the database to be backedup meets the requirements for employing snapshotbackups.

FMM8316E Product_name: interface problem infunction function_name: Empty group listpassed by DB2.

Explanation: The named product detected an interfaceproblem in the named API function: The databasepassed a group list containing no elements.

System action:


FMM8317W Product_name: Verification ofconfiguration requested by user. Nobackup started.

Explanation: The user requested a verification of theconfiguration. The backup flow continued withouterrors up to the point where the snapshot wouldactually be done and was then cancelled. The system isready for a snapshot backup, but no action beyondverification has been taken so far.

System action:


FMM8318E Product_name: interface problem infunction function_name: Not enoughspace provided to write meta data.

Explanation:

System action:


FMM8319W Error while deleting old versions. Thisproblem does not affect the newbackup. Error information:'error_information'

Explanation: After a successful backup, the systemtries to remove older backups of the database accordingto the value of profile parameter MAX_VERSIONS.However, a problem occurred while trying to removeexpired backups. The new backup is not affected bythis problem.

System action:

User response: Check the appropriate log files inorder to determine the cause of the problem. Resolveany problems indicated. In case the storage device runsout of storage because outdated snapshot backups havenot been removed, delete these snapshot backupsmanually.

FMM8320I Deleting full backup backup_id –backup_key.

Explanation: After a successful backup, the systemtries to remove older backups of the database accordingto the value of profile parameter MAX_VERSIONS.During this process, the full backup listed is removed.

System action:


FMM8321I Deleting partial backup backup_id fornode host:partition_number.

Explanation: After a successful backup, the systemtries to remove older backups of the database accordingto the value of profile parameter MAX_VERSIONS.During this process, the backup listed for the namedpartition is removed.

System action:


FMM8322E Interface problem: Current databasepartition number is not listed in thepartition list.

Explanation: The partition list passed by the databasedoes not contain the named partition participating inan operation.

System action:


FMM8323E Product_name: Problem occurred whileprocessing function_name. Please checklog file log_file_name for moreinformation. Error information:'error_information'


System action:

User response: Analyze the error information and theappropriate log files to find the cause of the problem.Resolve any problems indicated.



FMM8324E Product_name: Problem occurred whileprocessing function_name: Device agentreturned code return_information.

Explanation: The named product implementing theDB2 Advanced Copy Services API received an errorfrom the device agent in the named API function. Thedevice agent's return information is given.

System action:

User response: Check the appropriate log files to findthe cause of the problem. Resolve any problemsindicated.

FMM8325E Failed to determine hostname.

Explanation: The system was not able to determinethe host name of the machine.

System action:

User response: Make sure the system setup allows forquerying the hostname via system functiongethostname(). Ensure that the requirements for doingsnapshot backups are met.

FMM8326E Failed to create log directory path.

Explanation: The log path indicated is not available inthe system and could also not be created.

System action:

User response: Check the properties of the pathindicated and make sure that its properties and theproperties of the parent directory are set accordingly.Make sure all prerequisites for doing snapshot backupsare met.

FMM8327E Invalid value specified for parameterkeyword: value

Explanation: A parameter value is not valid.

System action:

User response: In case the parameter was specified inthe profile correct the profile. In case the parameter wasspecified as a command line option, correct the entry.

FMM8328E Product_name must be licensed to setparameter keyword to a value of value.

Explanation: Selected functions are supported onlywith a full TSM license.

System action:

User response: If you need the functionalityrequested, obtain a full TSM license and install thelicense file. Otherwise, in case the parameter wasspecified in the profile, correct the profile or, in case theparameter was specified as a command line option,correct the entry.

FMM8330E Parameter keyword requires 'YES', 'NO',or AUTO.

Explanation: For the named parameter, only thevalues, 'YES', 'NO' and 'AUTO' are accepted.


User response: Correct the profile or the call asappropriate.

FMM8331E The parameter keyword1 is not allowed ifkeyword2 is set to value.

Explanation: There is a dependency betweenparameters keyword1 and keyword2. If the latter is set tothe value named, keyword1 must not be specified.

System action:


FMM8332E Failed to parse parameter keyword. Fileand path names in the profile need tobe fully qualified.

Explanation: As the value of the parameter indicated,a fully qualified file or path name is expected.However, the specified value is not a fully qualifiedpath.

System action:


FMM8333E In order to enable the parameterkeyword1 you need to set keyword2 tovalue.

Explanation: There is a dependency betweenparameters keyword1 and keyword2. If keyword1 isspecified, keyword2 must be given the specific valueindicated in the message.

System action:


FMM8334E Profile section section_name is requiredfor function operation.

Explanation: The specified profile section is requiredin order to perform the requested operation. However,it is not included in the profile.

System action:




FMM8335E Profile section section_name refers to avalue for keyword that differs from theone used at backup time. Expectedvalue: value.

Explanation: The profile parameter named must notchange its value between backup and restore. However,in the named profile section, the parameter has a valuedifferent from the value it had at backup time. Thisvalue is given in the message.

System action:

User response: Correct the profile by setting theindicated parameter to the value indicated in themessage.

FMM8336E Invalid value specified for optionkeyword: value

Explanation: An option value is not valid.

System action:

User response: Correct the call.

FMM8337E Error while parsing profile: Missingsection name.

Explanation: The profile is organized into namedsections. However, a section name was not found.

System action:

User response: Check that the profile name isspecified correctly or that the default profile is a validprofile. Refer to your user documentation for the syntaxof the profile or use the profile wizard to create a newprofile.

FMM8338E Error while parsing profile: Sectionsection_name is not allowed to be nested.

Explanation: In the profile, the named section startsbefore the previous section ends. However, the sectionin question cannot be nested.

System action:


FMM8339E Error while parsing profile: Profilesection section_name is not valid.

Explanation: An invalid section name was found inthe profile.

System action:


FMM8340E Error while parsing profile: Profilesection section_name must not bespecified more than once.

Explanation: In the profile, only a single section withthe name indicated can be specified. However, duringparsing, a second occurrence was detected.

System action:


FMM8341E Error while parsing profile: Profilesection section_name missing.

Explanation: The required profile section indicatedwas not found in the profile.

System action:


FMM8343W The profile parameter keyword profileparameter of device type provile section haschanged its value from (original)value1 to(current) value2.

Explanation: The profile parameter named must notchange its value between backup and restore or delete.However, in the named profile section, the parameterhas a new value value2 different from the value value1it had at backup time. Both values are given in themessage.

System action:

User response: Check the log file for problems thatmay result from the change of parameter values. If so,you may want to change the profile, restoringparameter profile parameter keyword to the value it hadwhen creating the backup in order to perform a specificoperation.

FMM8344E Path path is listed more than once forpartitioning.

Explanation: This is a DB2 – TSM interface problem.

System action:


FMM8345E Error while parsing parameter keyword.'path' is required to be type_information.

Explanation: A path of the type indicated in themessage is expected as a value of the named parameter.However, the specified path was not found to be of thecorrect type.

System action:




FMM8349I Deleting incomplete backup backup_id –backup_key.

Explanation: After a successful backup, the systemtries to remove older backups of the database accordingto the value of profile parameter MAX_VERSIONS.During this process, the incomplete backup listed isremoved. A backup becomes incomplete when parts ofits data expire. This can happen when a backup that ismarked 'destructively restorable' is restored.

System action:


FMM8350E Parameter parameter requires 'NO','TSM', or 'DP4SAP'.


System action:


FMM8351E Parameter parameter requires 'AUTO' ora decimal value.


System action:


FMM8352E Parameter parameter requires a decimalvalue.


System action:


FMM8353E Parameter parameter requires a valuegreater than '0'.


System action:


FMM8354E Parameter parameter requires 'NO' or'YES'.


System action:


FMM8355E Parameter parameter requires 'ALL' or acomma separated list of decimal values.


System action:

User response: Check the profile keywordDBPARTITIONNUM and make appropriateadjustments.

FMM8356E product_name: interface problem infunction function: Invalid call sequence;the library was not initialized.

Explanation: An invalid internal call sequence wasdetected during execution of a dedicated function.

System action:


FMM8357E product_name: interface problem infunction function: Invalid call sequence;the operation was not initialized.

Explanation: An invalid internal call sequence wasdetected during execution of a dedicated function.

System action:


FMM8358E Parameter name requires 'ONLINE' or'OFFLINE'.

Explanation: The parameter name only accepts thevalues ONLINE or OFFLINE.


User response: Correct the value for the parameterspecified in the profile.



FMM8359E The profile parameter parameter has thewrong value 'value profile'. The expectedvalue is 'value expected'.

Explanation: A profile parameter (or keyword) has awrong value assigned. An alternate value is expected.

System action:

User response: Check the named TSM for ERP profilekeyword and make appropriate adjustments.

FMM8360E Invalid keyword specified in the profile.

Explanation: The value specified for a keyword iseither wrong or is missing.

System action:

User response: Check the named TSM for ERP profilekeyword and make appropriate adjustments.

FMM8361E Found files on the file systems tobackup for which backup was notexplicitly requested. Please provide anegative list or clean your file systems.

Explanation: Although the previously mentioned fileswere not requested to be part of the backup, they willbe copied because they reside on a file system that willbe backed up in its entirety. In order to allow backingup those files, they need to be added to a 'negative list'or the checking for such files needs to be disabled.Note that in case of a restore, these files wouldtypically be restored, even if this was not desired.

System action:

User response: Edit the 'CLIENT' section of theprofile. You can either set the parameter'NEGATIVE_LIST' to 'NO_CHECK', to allow IBM TivoliStorage FlashCopy Manager to back up any file storedin a file system that will be backed up, or you can setthe parameter 'NEGATIVE_LIST' to point to a file (the'negative list') that contains a list of all files anddirectories that are allowed to be processed duringbackup. Any directory you add to the 'negative list' isprocessed recursively. Note that there is only one'negative list' for backup and restore. See FMM6969Efor restore.

FMM8362E The trace parameters YES, NO, ON, andOFF cannot be set in conjunction withother trace parameters.

Explanation: The values YES, NO, ON and OFF inconjunction with the TRACE keyword do not allowfurther trace flags to be set. They are mutuallyexclusive.

System action:

User response: Check the TSM for ERP profilekeyword TRACE and make appropriate adjustments.

FMM8363E The value value is not a valid trace flag.

Explanation: The value specified for the TRACEkeyword is invalid.

System action:

User response: Check the TSM for ERP profilekeyword TRACE and make appropriate adjustments.

FMM8364E Error while parsing parameterCONFIG_FILE. Directory 'directory' fornode 'node' does not exist.

Explanation: The base directory containing the TSMfor ERP configuration file(s) for any participating DB2partition does not exist or cannot be accessed.

System action:

User response: Ensure that the directory denoting thebase part of the CONFIG_FILE value (left part of the%DB2NODE substring) exists and has the rightpermissions.

FMM8365E The server stanza for LOG_SERVER'server' is missing.

Explanation: A TSM server stanza used by theLOG_SERVER keyword is missing either in the optionfile (dsm.opt) or in the system options file (dsm.sys).

System action:

User response: Either the value of the LOG_SERVERkeyword in the TSM for ERP profile has to be adjustedor an entry must be made or adjusted in theappropriate option file.

FMM8366E The values for parameter parameter areexpected to be in the range 0 to 6.

Explanation: The values of the keyword USE_AT haveto be in the range of 0 to 6.

System action:

User response: Check the TSM for ERP profilekeyword USE_AT and make appropriate adjustments.

FMM8367E You cannot freeze the filesystemwithout suspending or shutting downthe database.

Explanation: Check the TSM for ERP profile keywordUSE_AT and make appropriate adjustments.

System action:

User response: Ensure either to suspend the databaseor to bring the database offline and try to freeze thefilesystem again.



FMM8368E An invalid argument is specified forkeyword keyword.

Explanation: The specified argument could not beconverted into an equivalent integer value.

System action:

User response: Check the keyword argument and tryagain. If the problem cannot be resolved contact yourIBM support personnel.

FMM8369E Failed to execute program. Reason: reason.

Explanation: The execution of program failed.

System action:


FMM8370E The profile optionTARGET_DATABASE_SUSPEND= OFFLINE is notallowed for an online database backup.

Explanation: A snapshot backup of a database thatwas not suspended can only be done in offline mode.

System action:

User response: Start the BRBACKUP utility with theoption '–t offline -d util_vol' and try again.

FMM8371E The profile parameter NEGATIVE_LISTis not allowed. Use BR–TOOLS option"–n" to specify the negative list.

Explanation: The negative list value has to bespecified in the init<SID>.sap profile via the option'util_vol_nlist = (nfile_name1, nfile_name2, ...) |no_check'.

System action:

User response: Adjust the init<SID>.sap profileaccordingly and try again.

FMM8372E The profile optionTARGET_DATABASE_SUSPEND=YESrequires a backup of typevolume_online. To solve this problemeither the profile parameterTARGET_DATABASE_SUSPEND can beset to OFFLINE or NO or the brbackupbackup device type should be set toutil_vol_online. Keep in mind, whenyou set the profile parameterTARGET_DATABASE_SUSPEND toNO, the snapshot backup will bemounted on a backup system to verifyits consistency. Make sure that a backupsystem is configured in that case.

Explanation: A snapshot backup of a database thatwas suspended can only be done in online mode.

System action:

User response: Start the BRBACKUP utility with theoption '–t online -d util_vol' and try again.

FMM8373W The operation will execute the forceoption (–F).

Explanation: Start the BRBACKUP utility with theoption '–t online -d util_vol' and try again.

System action:


FMM8374W Operation will terminiate with error,because backint was executed withverify option (–V).

Explanation: The verify option simulates therequested option and does not create a valid backup orrestore. In order to prevent the calling process fromregarding the current operation as successful, the verifyoption will always yield a nonzero return code.

System action:

User response: Do not use the verify option if youwant to create a backup or restore.

FMM8375E The value of the environment variableORACLE_SID is not allowed to havemore than number digits.

Explanation: The length of the ORACLE_SID valueviolates the defined range.

System action:

User response: Check the current value ofORACLE_SID and if necessary, correct it according tothe allowed length. Try again.

FMM8376E Verification of snapshot failed. Reason:reason

Explanation: The snapshot backup could not beverified successfully.

System action:


FMM8377E Function function does not supportmultiple backup ids within a singleoperation.

Explanation: TSM for ACS was requested to performa volume function operation simultaneously for a set ofobjects that were backed up with multiple volume



backup requests. This is currently not supported.

System action:

User response: Use backups stored on the TSM serverto perform redirected restores or adjust the restorecommand.

FMM8378E Redirected restore of volume backups isnot supported yet.

Explanation: TSM for ACS does not support restoresto an alternate data location. The restore always needsto be made to the original data location.

System action:

User response: Use backups stored on the TSM serverto perform redirected restores.

FMM8379E Infile contains an invalid value: 'value'

Explanation: Each record of the infile has to starteither with the string '#NULL' or with the backup Id.

System action:

User response: Ensure each record of the infilesatisfies the requirements. If the problem cannot beresolved contact your IBM support personnel.

FMM8380E The profile option TSM_BACKUP=YESrequires a snapshot backup of allpartitions of the database.

Explanation: The profile option TSM_BACKUP=YESimplies offloading a snapshot backup to TSM. If thisoption is specified, all database partitions have to bepart of the snapshot backup.

System action:

User response: Specify the 'ALLDBPARTITIONNUMS' clause as part of the DB2 backupcommand and try again.

FMM8381W The following error occured whileverifying the configuration for server'server_name' in the profile:

Explanation: The profile section for server server_nameis not correct. The actual error is following thismessage.

System action:

User response: Adjust the profile and correct the errorfollowing this message.

FMM8382E The previous errors can be prevented bycompleting restore with negative list setto 'no_check'.

Explanation: An error occurred while inspecting filesystems for files that should be excluded during the

backup/restore operation. This error precedes thecurrent message. Note that the file system inspectioncan be turned off by setting the parameter'NEGATIVE_LIST' to 'NO_CHECK'.

System action:

User response: Resolve the root cause for this problem(previous error) or change the value of the parameter'NEGATIVE_LIST' to 'NO_CHECK'. Note that changing'NEGATIVE_LIST' to 'NO_CHECK' implies that TSMfor ACS would potentially back up all files residing onthe requested file systems. This is true even if theywere not explicitly requested and resided on therequested file systems, and even if they were notexplicitly requested during the backup. At restore timeall of these objects would typically be restored. For DB2and native Oracle: Edit the TSM ACS profile and setthe parameter 'NEGATIVE_LIST' to 'no_check'

For SAP(R) for Oracle: Edit the BR*Tools profile *.sapand set the parameter 'util_vol_nlist' to 'no_check'.

FMM8383E BR–Tools are required to set theenvironment variable BI_RUN forvolume backups.

Explanation: This is a unique ID from a BR*Tools run(normally it is the name of the BR*Tools log). If thisvariable is set then BACKINT recognizes that a callfrom BR*Tools 7.10 or higher was triggered.

System action:

User response: Ensure that BR*Tools 7.10 or later isused and rerun the operation.

FMM8384E Failed to determine theAPPLICATION_TYPE of the profile.Please invoke wizard with option –m<application type>.

Explanation: 'acsd –f wizard' was invoked to modifyan existing profile, and the APPLICATION_TYPE couldnot be identified by inspecting this profile. This isrequired in order to properly adjust the profile.

System action:

User response: Provide the application type wheninvoking the wizard with options 'acsd –f wizard –m<application type>'. The preferred method, however, isto call the setup script without options.

FMM8385E In order to create a new profile thewizard needs to be invoked with option–m <application type>.

Explanation: 'acsd –f wizard' was invoked to create anew profile. In this case it is required to specify theapplication type with option –m.

System action:

User response: Provide the application type when



invoking the wizard by using the options 'acsd –fwizard –m <application type>'. Alternatively, you canuse the database–specific version of the setup script(setup_<database>.sh) to create a new profile andconfigure TSM for ACS.

FMM8386E Parameter parameter name requires adecimal value of 0 or greater.


System action:


FMM8387W The following extra files are found inthe directories to be backed up: 'filename'

Explanation: The extra files were not requested to bepart of the backup. The files may be copied if they arelocated in a file system that is to be backed up in itsentirety. If the files are in a file system that does notparticipate in the backup they are not copied.

System action:

User response: To avoid generating this message, editthe 'CLIENT' section of the profile. You can set theparameter 'NEGATIVE_LIST' to 'NO_CHECK'. Then,IBM Tivoli Storage FlashCopy Manager backs up anyfile that is stored in a file system participating in thebackup. Alternatively, you can set the'NEGATIVE_LIST' parameter to point to a file('negative list') containing a list of all files anddirectories that are allowed to be processed during thebackup. Any directory that you add to the 'negativelist' file is processed recursively. Note there can be onlyone 'negative list' file for both backup and restoreoperations.

To avoid false warnings for files in the nested filesystems that do not participate in the backup, add themount points of the nested file systems to the 'negativelist' file.

To avoid false warnings for files or directories that arepointed to by symbolic links and that do not participatein the backup, add the file system mount points ofthese files to the 'negative list' file.

Note: FlashCopy Manager does not automaticallyinclude nested file systems and files pointed to bysymbolic links in the FlashCopy backup operation.

FMM8388W Additional files to restore werediscovered on the file systems: 'file list'

Explanation: A FlashCopy restore operation isperformed with the profile parameter NEGATIVE_LISTset to WARN. This operation replaces complete filesystems with the content of the file systems at the time

of backup. Each file that currently resides on the filesystems to be restored (but were not part of theoriginal backup) will be listed.



FMM8389W The following volume groups / filesystems are currently not accessible:volumegroups/filesystems

Explanation: The listed volume groups or file systemsare not accessible. TSM ACS tries to verify that onlydatabase files reside in the volume groups or filesystems that will be restored. But it was encounteredthat it was not possible to access the file systems (in thevolume groups) to verify the database files because thefile systems are not mounted or the volume groups arenot imported, or both. This warning message isfollowed by message FMM9390E which gives moreinformation.

System action:

User response: This is just a warning message. Followthe instructions of the user response of FMM8390E.

FMM8390E Because some of the databasefilesystems are currently not accessible,TSM ACS failed to validate that onlydatabase files will be overwrittenduring restore.. Import volume groupsand/or mount all filesystems and restartthe restore. If you cannot mount thefilesystems as a consequence of adisaster or a failing previous restoreoperation, this error can be preventedby completing restore with negative listset to 'no_check'.

Explanation: TSM ACS tries to verify that onlydatabase files reside in the volume groups / filesystems that will be restored. But it was not possible toaccess the file systems (in the volume groups) to verifythe database files because the file systems are notmounted and/or the volume groups are not imported.

System action:

User response: Import all volume groups and mountall file systems that contain database files.

If a disaster or a failed previous restore operationprevents importing and mounting, the negative listcheck cannot be completed. You must change the valueof the parameter 'NEGATIVE_LIST' to 'NO_CHECK'.Note that changing 'NEGATIVE_LIST' to 'NO_CHECK'implies that TSM for ACS would potentially back up allfiles residing on the requested file systems. This is trueeven if they were not explicitly requested and residedon the requested file systems, and even if they were notexplicitly requested during the backup. At restore timeall of these objects would typically be restored.



For DB2 and native Oracle: Edit the TSM ACS profileand set the parameter 'NEGATIVE_LIST' to 'no_check'

For SAP(R) for Oracle: Edit the BR*Tools profile *.sapand set the parameter 'util_vol_nlist' to 'no_check'.

FMM8391E 'bytes_requested' bytes were requested tobe read from the file 'filename' but only'bytes_read' bytes could be read.

Explanation: The specified number of bytes requestedto be read from the specified filename could not beread.


User response: Check if the file size is smaller thanthe number of requestd bytes.

FMM8392E An error occured while restoring the file'filename'

Explanation: The restore operation failed for theidentified file. The restore process continues with theother files.


User response: A restore failure occurs for differentreasons. Please check for previous error messages thatprovide more information about the reason.

FMM8393E The keyword TARGET_SET requires atarget set name as argument.

Explanation: The keyword TARGET_SET specifiedwithin the target set definition file needs to be followedby an argument defining the unique name of the targetset.

System action: Please have a look into your target setfile (.fct) and correct the entry accordingly.

User response:

FMM8394E Error while parsing TARGET_SET targetset name: Illegal number of arguments.

Explanation: The keyword TARGET_SET specifiedwithin the target set definition file needs to be followedby exactly one argument defining the unique name ofthe target set. No additional arguments are allowed.

System action:

User response: Please have a look into your target setfile (.fct) and correct the entry accordingly.

FMM8395E Error while parsing TARGET_SET targetset name in volumes file: A multipartition backup requires the use of thekeyword PARTITION in the target setsection.

Explanation: On a partitioned DB2 environment, the

TARGET_VOLUME entries within the target setdefinition file need to be enclosed by nested'PARTITION' sections to determine for which partitionthis target volume(s) apply.

System action:

User response: Modify your target set definition fileaccordingly. Example: >>> TARGET_SET SET_1 >>>PARTITION NODE0000 TARGET_VOLUME 40913158 -- TARGET_VOLUME 40A13158 - - <<< >>>PARTITION NODE0001 TARGET_VOLUME 40B13158 -- TARGET_VOLUME 50913158 - - <<< <<<

FMM8396E Error while parsing TARGET_SET targetset name in volumes file: It is notallowed to specify a portion of a targetset without keyword PARTITION, ifthis keyword is used for other portitionsin the same target set definition.

Explanation: On a partitioned DB2 environment, theTARGET_VOLUME entries within the target setdefinition file need to be enclosed by nested'PARTITION' sections to determine for which partitionthis target volume(s) apply. As soon as embeddedPARTITION subsections are used this means that ALLTARGET_VOLUME entries need to be enclosed inPARTITION subsections.

System action:

User response: Correct your target set definition fileaccordingly.

FMM8397E Error while parsing TARGET_SET targetset name in volumes file: the parameterPARTITION requires exactly oneparameter.

Explanation: On a partitioned DB2 environment, theTARGET_VOLUME entries within the target setdefinition file need to be enclosed by nested'PARTITION' sections. The keyword 'PARTITION'needs to be followed by the unique name of thepartition.

System action:

User response: Check whether all PARTITIONsubsections within your target set definition file have aunqiue partition name and correct the entries ifnecessary.

FMM8398E Error while parsing statement 'parametername' in profile. The statement 'from orto' is required to be in the form hh:mm.

Explanation: The optional conditions 'FROM' and 'TO'of the profile parameter 'parameter name' need to befollowed by a time in the format 'hh:mm'.

System action:



User response: Please check your profile and correctthe times accordingly.

FMM8399E The mode mode of parameter parameter isonly supported for device_type .

Explanation: The requested mode mode is onlysupported for device_type.

System action:

User response: Choose a supported mode..

FMM8400E Error while parsing statement 'deviceclass' in profile. The statement partitionnumber is required to be a number.

Explanation: The optional condition'ON_PARTITIONN' of the profile parameter'DEVICE_CLASS' needs to be followed by an integernumber.

System action:

User response: Please check your profile and correctthe 'ON_PARTITIONN' entries accordingly.

FMM8401E DEVICE_CLASS device class wasencountered multiple times within asingle DEVICE_CLASS statement.

Explanation: The parameter 'DEVICE_CLASS' of the'CLIENT' section allows to enlist multiple device classeswhich are then applied in a round robin process.However, each enlisted device class must not occurmultiple times within the same enumeration.

System action:

User response: Please check your profile and correctthe 'DEVICE_CLASS' entries accordingly.

FMM8402E No DEVICE_CLASS found that can beused for the current operation.

Explanation: The application of a 'DEVICE_CLASS'entry within the 'CLIENT' section of the profile can berestricted by a number of optional conditions, e.g. bytime frame of DB2 partition number. If this error occursnone of the DEVICE_CLASS entries within the profilematches the conditions currently given (current time,given partition, given weekday).

System action:

User response: Check the conditions specified for the'DEVICE_CLASS' entries within your profile. It needsto be ensured that exactly one entry matches anyimaginable condition at any time.

FMM8403E The keyword keyword was foundmultiple times without qualifier qualifier.

Explanation: If the parameter keyword is specifiedwithout additional qualifiers it is representing theglobal default. This global default can be defined onlyonce. All other entries of parameter keyword need to berestricted by additional conditions.

System action:

User response: Please check your profile. Theparameter keyword must not occur multiple timeswithout additional conditions.

FMM8404E The following statement containsincompatible options statement.

Explanation: The parameter statement within the'CLIENT' section of the profile is followed byadditional options which are contradictory to eachother.

System action:

User response: Please check the parameter statementwithin your profile. For example, it is not possible tocombine the options 'MANDATE' and 'TSM_ONLY'.

FMM8405E The following statement is missingmandatory options statement.

Explanation: The parameter statement within the'CLIENT' section of the profile must be followed by anoption defining the mode of how offline backups arehandled.

System action:

User response: Please check the parameter statementwithin your profile. It needs to include either 'NO','YES', 'MANDATE', or 'TSM_ONLY' as an option.

FMM8406E There are two object type associated withpartition partition name.

Explanation: The profile associates the same partitionwith multiple objects of object type. The name of thepartition and of the object type are identified in thismessage.

System action: The operation fails.

User response: Update the profile so that eachpartition is listed as a member of only one object ofobject type.

FMM8407E An illegal partition number has beenspecified for parameter candidate name.

Explanation: The parameter parameter expects integerpartition numbers as argument.

System action:



User response: Please check the parameter parameterwithin your profile and correct it accordingly.

FMM8408E The parameter parameter is not allowedas a name for a target set.

Explanation: One possible distinctness of theparameter 'TARGET_SET' is to specify target setdefinitions via a naming convention instead of a targetset definition file (for SVC only). The argumentparameter does not meet these naming conventions.

System action:

User response: Please check the arguments of theparameter 'TARGET_SET' within your profile andcorrect them accordingly.

FMM8409E The parameter TARGET_NAMING isrequired to contain the wildcards sourceand targetset.

Explanation: The parameter 'TARGET_NAMING'needs to follow particular conventions including thewildcards source and targetset to be valid.

System action:

User response: Please check the arguments of theparameter 'TARGET_NAMING' within your profile andcorrect them accordingly.

FMM8410I Invoking suspend script suspend script.

Explanation: The suspend script has been invoked.This script suspends the application immediately beforethe actual FlashCopy process is initiated.

System action:

User response: Watch for additional messagesregarding the success of the suspend operation.

FMM8411I Script returned with return code returncode

Explanation: A suspend or resume operation failedand issued the corresponding error code.

System action:

User response: Please check for more information inthe output that preceeds this message.

FMM8412I Start resume script resume script.

Explanation: The resume process has started.Applications which have been suspended immediatelybefore the actual FlashCopy operation are resumedafter this process completes.

System action: Watch for additional messagesregarding the success of the resume operation.

User response:

FMM8413I Continue script script to resume.

Explanation: The identified script is resuming theoperation.

System action:

User response: Watch for successive messagesinforming about the success of the resume operation.

FMM8414E Error while parsing profile profile:Delimiter 'delimiter' missing.

Explanation: A syntax error has been detected withinyou profile.

System action:

User response: Please check the syntax and format ofyour profile.

FMM8415E A size has been specified for the file'file' in the infile, but the requested fileis not a raw device.

Explanation: A size was specified (in the infile) for thestated file. However, the file does not refer to a rawdevice. A size specification is allowed for raw devicesonly.

System action:

User response: Verify that the correct entries arespecified in the infile.

FMM8416E The specified backup ID 'backup id' musthave 16 characters.

Explanation: The backup ID is expected to be exactly16 characters.

System action:

User response: Verify the given backup ID. If itcontains 16 characters, make sure that it does notcontain any special characters.

FMM8417E File 'file' has not been found in anybackup.

Explanation: No backup version of the file to berestored is available.

System action: Processing continues to restore otherrequested files that are available.

User response: If you have provided the names of thefiles please check for wrong names in the input. If therestore was started by SAP BR*Tools the version of thisfile might have been deleted on the Tivoli StorageManager server.



FMM8418E The backup ID 'backup id' has not beenfound.

Explanation: The backup ID was not found in thebackup repository. As a result, the requested backupcannot be restored.


User response: If you have provided backup ID pleasecheck for wrong entries in the input. If the restore wasstarted by SAP BR*Tools this backup might have beendeleted on the Tivoli Storage Manager server.

FMM8419E File 'file' was not found in the backupidentified with backup ID 'backup id'

Explanation: The specified file was not found in thebackup and was removed from the list of files to berestored.

System action:


FMM8420E Full file-based backups into therepository are not allowed when'ALLOW_FULL_FILE_BACKUP' is set to'NO'.

Explanation: If you want to use 'FlashcopyManager' toperform a backup with options util_file orutil_file_online, set the optionALLOW_FULL_FILE_BACKUP to YES in the profile.

System action:

User response: Correct the setting for the parameterwithin your profile. You can also change backupoptions.

FMM8421I Modifying existing profile 'profile file' forapplication 'application type' ...

Explanation: An existing profile was found by theprofile wizard and will be modified during subsequentconfiguration actions.

System action:


FMM8422I Creating new profile 'profile file' forapplication 'application type' ...

Explanation: No existing profile was found. Theprofile wizard will create a new profile.

System action:


FMM8424E Operation not allowed for thisparameter.

Explanation: An invalid value was entered for thecurrent parameter.

System action:

User response: Enter a valid value for this parameter.View help for a parameter by entering a question mark("?").

FMM8426I Saving profile 'profile' ...

Explanation: The profile wizard writes the profile tothe file system.

System action:


FMM8428W No help available for this parameter

Explanation: No help information is available for thecurrent parameter.

System action:

User response: Check the product documentation forhelp information about this parameter.

FMM8431E Application Type 'application type' is nota valid type.

Explanation: An invalid application type wasspecified in the profile wizard command.

System action:

User response: Issue the command again using a validapplication type. Supported application types are DB2,SAP, ORACLE, SAP_ORACLE, GENERIC, andVMWARE.

FMM8432E Invalid function: function invalid(supported: function supported)

Explanation: The function specified for the profilewizard -f option is invalid.

System action:

User response: Issue the command again and specifya valid function. The only supported function is"password".

FMM8433E Wrong system mode: system mode(supported: PS | BS | PSBS)

Explanation: The system mode specified in the profilewizard is invalid. These three system modes aresupported: PS - the wizard creates a profile for theProduction System BS - the wizard creates a profile forthe Backup System PSBS - the wizard creates profilesfor both the Production and the Backup System



System action:

User response: Issue the command again and specifya valid system mode. Supported system modes are PS,BS, PSBS.

FMM8435W Annotation file 'file' could not be loaded.

Explanation: The annotation file is required by theprofile wizard for displaying more expressive promptsand online help. However, if this file is missing thewizard is still operational.

System action:

User response: The annotation file is integral part ofthe product. If it is missing this means your productinstallation is corrupt. Please perform a reinstallation. Ifthe warning message still occures please contact yoursupport line.

FMM8436W Problems occured on final validation ofprofile. Incorrect parameters have beenmarked in the written profile. Pleasecheck.

Explanation: Profile parameters for that a user-definedvalue is obligatory have been skipped withoutspecifying a value.

System action:

User response: Please rerun the profile wizard for thegiven profile and ensure you specify a valid value foreach parameter marked with *input mandatory*.

FMM8437I Verifying password...

Explanation: After a password has been entered thewizard is verifying it by performing a test connectionto the according entity.

System action:

User response: Wait for outcome of the verification. Ifthe verification is successfull the wizard proceeds withthe next password or writes the password files. If theverification fails the user is asked whether he wants toretry or ignore the issue.

FMM8439E Could not read password filename fromprofile 'profile'. File does not exist.(Check options -p, -b)

Explanation: If the filename for the password file isnot explicitly specified by the option '-b' the wizardtries to read this information from the profile. Theprofile being consulted is either the default profile'profile' or the profile specified by option '-p'. If thiserror occurs there is either no default profile availableor the profile specified by option '-p' does not exist.

System action:

User response: Check options '-p' and '-b'.

FMM8440E 'number of disks' disks have been foundfor datastore 'datastore name'. Only onedisk per datastore is supported for thefollowing environments: IBM DS8000IBM NSeries NetApp.

Explanation: The specified datastore cannot be backedup by IBM Tivoli Storage FlashCopy Manager becauseof environmental limitations. See error message formore detail.


User response: Reduce the number of disks of thedatastores to include in the backup to one or useconsistency groups in case the IBM XIV® storagesystem is used.

FMM8441E Please specify either only backup id's oronly backup id's with files.

Explanation: You specified some backup id's with filesand some backup id's without files.

System action:

User response: Please specify either only backup id'sor only backup id's with files.

FMM8445E Invalid cloning mode: cloning modeinvalid (supported: cloning_only |backup_cloning)

Explanation: The given cloning mode is invalid. Thesetwo cloning modes are supported: cloning_only - forpure cloning configurations backup_cloning - forconfiguring a database instance for cloning andbackup/restore

System action:

User response: Issue the command again and specifya valid cloning mode.

FMM8446E The restore operation requires thecommand line option -P <Partitiongroup> to be specified.

Explanation: For restore operations in DB2 DPFenvironments where the profile parameterPARTITION_GROUP is used, it is required to specifythe command line option -P <Partition group> on therestore command.

System action:

User response: Issue the command again and specifya valid partition group.



FMM8448E Another device class already existsunder the given name 'name'. Pleasespecify another name.

Explanation: DEVICE_CLASS sections must be namedunique. The specified name is already in use foranother device class.

System action:

User response: Choose another device class namewhich is not already in use by another device classsection.

FMM8450E The entry in InFile is not a valid file ordirectory: 'entry'.

Explanation: The files or directories specified in theInFile have to exist prior the backup operation isstarted.


User response: Verify the reported invalid entry in theInFile and revise the entry accordingly.

FMM8464W The specified host name or IP address'host' cannot be associated with a localnetwork interface on this system.

Explanation: The attempt to establish a listeningTCP/IP server socket failed for the given host/portcombination. The provided host name or address isexpected to resolve to a local network interface.

System action:

User response: An attempt to bind a TCP/IP serversocket to the specified host on the specified port (or thedefault port if the port is not specified) was notsuccessful. This test is successfully only when thespecified host or IP address corresponds to a localnetwork interface.

FMM8465E The value value for parameter parameteris out of valid range (min - max).


System action:


FMM8503E No ESX host that can be used for instantrestore was found.

Explanation: No ESX host can be found. An ESX hostis needed to add data stores and to register virtualmachines as part of the instant restore operation.


User response: Add an ESX host to your virtualenvironment.

FMM8504E The 'datastore name' data store cannot bemounted on the following ESX hosts:'ESX host list'. There are no other ESXhosts to try.

Explanation: The specified data store cannot beattached to any of the listed ESX hosts. The processingcannot continue.


User response: Configure your storage and networkso that the specified data store can be mounted on oneof the specified ESX hosts.

FMM8505E The 'data store name' data store ismounted on the following disconnectedESX hosts: 'ESX host list'. The data storecannot be unmounted when these ESXhosts are in the disconnected state.

Explanation: The specified data stores are mounted atthe specified ESX hosts. These ESX hosts aredisconnected. Therefore the data stores cannot beunmounted and the instant restore operation cannotproceed.


User response: Remove the specified ESX hostscompletely from your vSphere environment orreconnect them.

FMM8506E The configured storage device cannot beused in a VMware NAS environments.

Explanation: The configured storage device cannot beused in a VMware network-attached storage (NAS)environment.


User response: Check the IBM Tivoli StorageFlashCopy Manager requirements to ensure that youuse a supported storage device.

FMM8507W The original data store cluster cannot befound: 'datastore cluster name'. The datastore 'datastore name' is restored to theroot directory of data center 'data centername'.

Explanation: The named data store cannot beassociated to the specified data store cluster. The datastore cluster that it was associated to during the backupprocess is not available at restore time. In theintervening time between backup and restore, the datastore cluster was deleted, renamed, or moved.




User response: After the restore process is completed,the data store can be reassigned to the appropriate datastore cluster.

FMM8510E Database instance 'instance name' couldnot be started because the defaultdatabase profile could not be found.

Explanation: Even for an offline backup the databasemust at least be mounted. If the profile for the Oracledatabase is not specified with profile parameterTARGET_DATABASE_PARAMETER_FILE then IBMTivoli Storage Manager will start the database in mountmode using the default profile. The message indicatesthat both the PFILE (parameter file) and the SPFILE(server parameter file) for this database instance couldnot be found.


User response: The current operation must beexecuted by the oracle instance owner. Check if theenvironment for the current user is set up properly.Especially verify the environment variablesORACLE_SID and ORACLE_HOME.

FMM8511I The command is: command name

Explanation: This is an information message echoingthe command.

System action:


FMM8512I Return code is: return code

Explanation: This message shows the return code ofthe Backup Object Manager. Valid return codes: 0 Therequested action was performed successfully. 1 Therequested action was performed successfully; however,some warnings were issued. 2 or greater The requestedaction could not be performed due to errors. In thiscase, an error message should be logged, too.

System action:

User response: None if the return code is 0. If thereturn code is greater than 0, analyze the error and/orwarning messages. Resolve errors before starting theaction again.

FMM8513W 'TDP_DIR' is not set. The temporarypath will be used.

Explanation: The environment variable 'TDP_DIR' isnot set and therefore, the log will be written to thesystem's temporary path instead.

System action:

User response: Set the 'TDP_DIR' environmentvariable.

FMM8514W 'TDP_DIR' is not set correctly. Thetemporary path will be used.

Explanation: The variable TDP_DIR is set but containsan invalid path. All run logs will be written to themachines temporary directory instead.

System action:

User response: Check and reset the environmentvariable TDP_DIR.

FMM8515W Volume volume group is shared acrosspartitions. This might result in severerestrictions during the restore operation.Consult the manual for details.

Explanation: The specified volume group containsdata from multiple partitions. As a consequence,individual database partitions cannot be restored. ForDB2, this means that you cannot use the native DB2restore and recovery commands. Instead, you mustrestore your database using 'tsm4acs -f restore'.

System action: The operation continues.

User response: No action is required for backupoperations. Restore operations need to be performedusing 'tsm4acs -f restore' instead of using the nativeinterface commands.

FMM8516E The restore operation terminatedbecause more objects than requestedwould have been restored.

Explanation: Multiple partitions were residing on thesame volume group at backup time. A restore can onlybe performed with 'tsm4acs -f restore'. Also, a partitiongroup must be specified with this command.

System action: The operation terminates.

User response: Run the restore operation again using'tsm4acs -f restore -P <partition group>'.

FMM8517E Function 'name' cannot operate onmultiple partitions simultaneously. Runthe operation again with a singlepartition.

Explanation: The operation started so that multipledatabase partitions were used (for example tsm4acswas started with option '-P <partition group> and thespecified partition group was representing multipledatabase partitions). This is not supported for thespecified function.

System action: Operation will fail.

User response: Run the operation again so that it usesonly one database partition.



FMM8518E Unable to stop db2.

Explanation: A restore was started while the databasewas still up and running.


User response: Stop the database and restart therestore operation.

FMM8519E Unsupported database / applicationtype.

Explanation: The requested operation wasimplemented on an application that does not supportthis operation.


User response: Consult the user manual on how toperform the operation you requested.

FMM8520E No command was specified.

Explanation: backom was called without a commandline.

System action:

User response: Check the command syntax andcorrect the call.

FMM8521E Command option 'command option'requires an argument.

Explanation: A command option requiring anargument was specified without an argument.

System action: Check the command syntax andcorrect the call.

User response:

FMM8522E Invalid command 'command'.

Explanation: backom was called with an invalidcommand.

System action:


FMM8523E Error during action.

Explanation: An error occurred while performing thenamed action.

System action:

User response: Look for other error messages in orderto analyze the problem.

FMM8524E An online restore of the Tablespace isnot allowed.

Explanation: Either the database setup or the kind ofbackup prevents an online table space backup.

System action:

User response: If you need to do a table space restoreit must be done offline.

FMM8525E The DB2 instance name can consist of atmost characters characters.

Explanation: The name given for the DB2 instancedoes not comply with the DB2 naming conventions.

System action:

User response: Correct the DB2 instance name.

FMM8526E The DB2 database alias can consist of atmost characters characters.

Explanation: The name given for the DB2 alias doesnot comply with the DB2 naming conventions.

System action:

User response: Correct the DB2 alias name.

FMM8527E Invalid node. Specify it in the formatnode format.

Explanation: The name given for the DB2 node doesnot comply with the DB2 naming conventions. Nodenumbers must be specified in the displayed format, forexample 'NODE0000' or '0000'.

System action:

User response: Correct the DB2 node number.

FMM8528E Invalid timestamp. Specify thetimestamp as 'yyyymmddhhmmss'.Wildcards '*' or '?' are permitted.

Explanation: Specify the timestamp in the format'yyyymmddhhmmss'.

v yyyy is the year, specified as four digits.

v mm is the month, specified as two digits.

v dd is the day of the month, specified as two digits.

v hh is the hour of the day, 00 to 23.

v mm is the minute of the hour, 00 to 59.

v ss is the second of the minute, 00 to 59.

You can use wildcards '*' and '?'. * is a wildcard for anynumber of digits. ? is a wildcard for exactly one digit.

System action:

User response: Correct the timestamp.



FMM8529E Invalid log sequence number. Specify itin the format log sequence format.

Explanation: The information on the log sequencenumber(s) does not comply with the expected format.Accepted log sequence numbers are for example '123'or 'S0000123.LOG'.

System action:

User response: Correct the log sequence number(s).

FMM8530E Profile 'file name' does not exist or cannotbe accessed.

Explanation: Either an existing file could not beopened, or a file could not be created.

System action:

User response: Check the attributes of the file and/orits directory. For backup processing, read access isrequired for the files to be backed up. For restoreprocessing, write access is required for the targetlocation of the files to be restored.

FMM8531E Directory 'file path' does not exist orcannot be accessed.

Explanation: A file path cannot be accessed.

System action:

User response: Check the attributes of the file and/orits directory. For backup processing, read access isrequired for the files to be backed up. For restoreprocessing, write access is required for the targetlocation of the files to be restored.

FMM8532E Invalid log chain number. Specify it inthe format log chain format.

Explanation: The information on the log chainnumber(s) does not comply with the expected format.Accepted log chain number(s) are for example '123' or'C0000123'.file path .

System action:

User response: Correct the log chain number(s).

FMM8533E A timestamp range is not allowed forcommand 'command'.

Explanation: A timestamp range is not allowed forcommand restore database, restore tablespace, restoretablespace online and restore DB2 history file. Only asingle timestamp argument can be used.

System action:

User response: Correct the timestamp commandoption.

FMM8534E Command option 'command option' ismissing.

Explanation: A command was issued withoutspecifying a required command option.

System action: Check the command syntax andcorrect the call.


FMM8535E Invalid output mode. Specify one of thekeywords keyword list.

Explanation: Only the listed keyword values areallowed with the output mode command option –m.

System action:

User response: Correct the output mode commandoption.

FMM8536E Wildcard characters are not allowed forcommand 'command'.

Explanation: For the BackOM commands 'restoredatabase', 'restore tablespace', 'restore tablespace online'and 'restore DB2 history file' it's not allowed to specifythe wildcard characters '*' and '?' in a timestampcommand option.

System action:

User response: Correct the timestamp commandoption.

FMM8537E The path 'path' is not absolute.

Explanation: A command line argument requires afully qualified path which was not given.

System action:

User response: Specify the fully qualified path.

FMM8538E The Tablespace Definition Information'file name' cannot be processed.

Explanation: The TDI file could not be parsed becauseof errors. There are more specific parser error messagesbefore this message occurs.

System action:

User response: Check for and respond to precedingerror messages in the Backup Object Manager log.

FMM8539E The parameter PARTITION_GROUP isnot allowed in the client section fornon-SAP environments. TheDB2_WORKLOAD parameter mustspecify SAP.

Explanation: The parameter PARTITION_GROUP was



specified in the client section of the profile, but theapplication is not a DB2 system running SAP.


User response: You cannot use the parameterPARTITION_GROUP in your environment. All databasepartitions must reside on dedicated volume groups.

FMM8540I Using component_name at host name:port

Explanation: The component_name service named isused for the current action.

System action:


FMM8541I Using profile 'profile path'.

Explanation: The profile named is used for the currentaction.

System action:


FMM8542E Profile 'profile path' cannot be read.

Explanation: The Backup Object Manager tried to usethe profile named but the profile was not available orcould not be read. The location of the profile isspecified via command line as argument to option '–e'or in environment variable 'XINT_PROFILE'.

System action:

User response: Make sure that the profile is availableat the location specified in option '–e' on the commandline or in environment variable 'XINT_PROFILE'. Checkthe attributes of the profile and the correspondingdirectory and make sure that the file can be accessed.

FMM8543I Querying TSM for file(s) 'file list'.

Explanation: The Backup Object Manager checks if thefiles listed are available on the TSM server(s) specifiedin the corresponding profile.

System action:


FMM8544I Application agent is terminating.

Explanation: An operation is entering the cleanupphase and application agents are disconnecting.



FMM8545I No image type image(s) found.

Explanation: A request could not be satisfied becausethe files to be processed are not available on the TSMserver.

System action:

User response: Check if the file(s) were specifiedcorrectly in the request.

FMM8546E Environment variable 'environmentvariable' is not set or not set correctly.

Explanation: A required environment variable is notset at all or has a value that is not allowed.

System action:

User response: Check the documentation for theappropriate values of the environment variable namedand set its value accordingly.

FMM8547E Nothing to restore.

Explanation: A restore operation was started but nodata was found to restore. This typically occurs whenan invalid backup ID is used.


User response: Specify another backup to restore.

FMM8548I Elapsed time: time value

Explanation: After restore and delete, the time elapsedduring the action is displayed.

System action:


FMM8549E Unable to create file 'file name'.

Explanation: During restore, the file to be restoredcannot be created in the target location.

System action:

User response: Check if there is sufficient spaceavailable for the file to be restored. Check the attributesof the target directory; write access is required. If thetarget file already exists, check that write access isgranted

FMM8550W Environment variable 'environmentvariable' for output mode has wrongvalue. Using default.

Explanation: The default output mode can beoverridden by the named environment variable.Accepted values are "short", "normal", or "detailed".The system default is "short" for actions on DB2 logfiles, "normal" otherwise.

System action:



User response: Specify an appropriate value for theenvironment variable named, or remove theenvironment variable.

FMM8551E Not all data written to 'file path'.

Explanation: Restoring raw or DB2 log file data endedbefore all data retrieved from TSM could be written tothe file named. The file is incomplete. named.

System action:

User response: Make sure there is sufficient space forthe data to be restored.

FMM8552E File 'file path' could not be closed.

Explanation: After restoring raw or DB2 log file data,the target file could not be closed.

System action:

User response: Retry the action.

FMM8553E The file 'filename' has not been found.This file is required for the device agentto function. Check your installation.

Explanation: One of the components that is requiredto be installed with the product is missing.


User response: Install the product again.

FMM8554E Unable to create directory for detailedlogs: name of directory.

Explanation: The specified directory could not becreated. Detailed log information for future operationswill not be available.

System action: The product continues to operate, butdetailed log information will not be written. Thisreduces the capability to diagnose errors.

User response: Create the specified directorymanually and start 'acsd' again.

FMM8555E Variable 'DB2DBDFT' or commandoption 'alias' is required.

Explanation: The password command needs thename/alias of the database, for which the DataProtection for SAP configuration file has to be adapted.

System action:

User response: Either set the environment variableDB2DBDFT or provide the command option 'alias' withthe password command and try again.

FMM8556E Unable to get hostname.

Explanation: The machines hostname could not bedetermined.

System action:

User response: Check the TCP/IP configuration of themachine.

FMM8557E The config file 'initfile name.bki' couldnot be created.

Explanation: Data Protection for SAP tries to createthe configuration file named if it is not present at thelocation specified by the Data Protection for SAP profilekeyword CONFIG_FILE. However, the file cannot becreated. This may either be caused by an incorrect pathspecified by keyword CONFIG_FILE, or the user maynot have the appropriate permissions for creating thefile.

System action:

User response: Make sure the path specified bykeyword CONFIG_FILE is correct and the permissionsare set appropriately.

FMM8558I Setting TSM password for partition'partition number' on host 'host name'.

Explanation: The Data Protection for SAP TSMpassword is set on the host named for the DB2partition indicated.

System action:


FMM8559W For partition 'partition number' switch tohost 'host name' and issue the commandagain.

Explanation: When verifying the TSM password, theData Protection for SAP configuration file is modified.If the Data Protection for SAP profile keywordCONFIG_FILE points to an NFS mounted (UNIX orLinux) or a shared (Windows) path accessible to allhosts in a DB2 ESE (EEE) environment, for example theinstance home, all configuration files of the variouspartitions can be modified simultaneously. If, incontrast, keyword CONFIG_FILE points to a local path,only the configuration files of the local partitions canbe modified. In this case, the password verificationneeds to be done from each host. The message indicatesthe partitions whose associated configuration files arenot accessible. In order to avoid this administrativeoverhead, it is recommended to place the DataProtection for SAP configuration files in a file systemshared by all hosts hosting a partition of the database.

System action:

User response: Make sure to verify the TSM



password(s) for all partitions of the database.

FMM8560E Partition 'partition number' not found inthe database configuration.

Explanation: The DB2 partition specified could not befound in the database configuration.

System action:

User response: Check the configuration of the DB2ESE(EEE) environment (db2nodes.cfg, environmentvariable DB2NODE) and try again.

FMM8561W Database 'alias' not listed in the systemdatabase directory.

Explanation: The database alias does not exist. Becausethere is a dependency between the alias and thesettings for Data Protection for SAP there might beproblems during database backup or restore runs.Nevertheless, the Data Protection for SAP configurationfile (initalias.utl) will be created and adapted.

System action:

User response: Check if the alias specified does matchto an entry in the DB2 system database directory.Further, check the argument for the Data Protection forSAP profile keyword CONFIG_FILE and if necessaryadapt it appropriately.

FMM8562E Target 'volume' is missing in the targetset ('target set name') that has beenspecified for restore. Review the errorexplanation for corrective actions.

Explanation: Prior to starting a restore, all targetvolumes that contain backup data are checked to makesure they are still listed in the target set definition file.The target set defintition file is specified in the profilewith the VOLUMES_DIR or VOLUMES_FILEparameter. This error might also occur if the backupwas performed with the TARGET_NAMING parameterspecified.

System action: The operation will fail.

User response: Verify that all target volumes used forthe backup have not been used for other purposes.Once you verify that the backup is still valid, set theoption RESTORE_FORCE to YES in the appropriatedevice section and run the operation again. This erroris now ignored for this operation. Alternatively you canadd the missing target volumes to the target setdefinition and run the restore operation again. Beaware that corrupt data might be restored if one of thevolumes within the target set was used for otherpurposes.

FMM8563E The target name 'backup volume' couldnot be identified from source name'source volume' and target set 'target set'using the current naming convention.Please review the error explanation forcorrective actions.

Explanation: You are attempting a restore operationwith option TARGET_NAMING defined in the profile.Before the restore operation begins, all volumes thatcontain backup data are checked to make sure they arestill defined in the profile. If the naming conventionspecified with option TARGET_NAMING changed afterthe backup was created, this checking action fails.


User response: Verify that all target volumes used forthe backup have not been used for other purposes.Once you verify that the backup is still valid, set theoption RESTORE_FORCE to YES in the appropriatedevice section and run the operation again. This erroris now ignored for this operation. Alternatively canupdate the naming convention specified with optionTARGET_NAMING to its original form and run therestore operatin again. Be aware that corrupt datamight be restored if one of the volumes within thetarget set was used for other purposes.

FMM8564E The backup selected for restore resideson target set 'name'. Either this target setdefinition no longer exists in the profileor the manner in which the target setswere specified has changed. Pleaseconsult the user manual for correctiveactions.

Explanation: You have chosen to restore a backupwhich resides on a target set that has been removedfrom the target set definition prior to this restoreoperation. This occurs when you reuse the volumesassociated with this target set for other purposes or byaccidentally changing the target set definition.

System action: The operation will fail

User response: Verify that all target volumes (of thespecified target set) used for the backup have not beenused for other purposes. Once you verify that thebackup is still valid, set the option RESTORE_FORCEto YES in the appropriate device section and run theoperation again. This error is now ignored for thisoperation. Alternatively, you can add the missing targetset to your target set definition file (whenTARGET_SETS is set to VOLUMES_FILE orVOLUMES_DIR) or you can append the name of thistarget set to the list of target sets specified with theTARGET_SETS option.



FMM8565E More than one DEVICE_CLASSstatement is eligible for the currentoperation. This is not allowed.

Explanation: Multiple DEVICE_CLASS statements arespecified in the CLIENT section. This is allowed only ifeach of those statements is restricted for use withdifferent times and dates. For DB2, it is also possible torestrict the use of a device class to a particularpartition.


User response: Modify the USE_AT, FROM-TO, andON_DBPARTITIONNUMS entries of theDEVICE_CLASS statements in the profile so that atmost, only one device class is used at a time.

FMM8566E The specified DEVICE_CLASSstatements are inconsistent. As a result,these pairs are ambiguous: pairs

Explanation: Multiple DEVICE_CLASS statements arespecified in the CLIENT section. This is allowed only ifeach of those statements is restricted for use withdifferent times and dates. For DB2, it is also possible torestrict the use of a device class to a particularpartition.


User response: Modify the USE_AT, FROM-TO, andON_DBPARTITIONNUMS entries of theDEVICE_CLASS statements in the profile so that atmost, only one device class is used at a time.

FMM8567E A node configured inPARTITION_GROUP is not present inthe db2nodes.cfg file or does not resideon this host. To restore nodes that resideon a different host you need to start therestore from this host directly.

Explanation: One of the specified nodes has not beenfound in the db2nodes.cfg file or does not reside onthis host.


User response: Try the operation again with differentnodes specified on the command line or in the profileor rerun the restore on the correct host. Also, check thesettings in the db2nodes.cfg file.

FMM8568I All nodes from db2nodes.cfg will berestored.

Explanation: All nodes that are specified in thedb2nodes.cfg file will be restored during this operation.



FMM8569I Only some nodes specified in thedb2nodes.cfg file will be restoredAdditional restore operations might berequired on other hosts.

Explanation: Some nodes that are specified in thedb2nodes.cfg file will be restored during this operation.



FMM8570E Unable to start db2.

Explanation: DB2 could not be started successfully.


User response: Check the application logs and DB2logs. Try this operation again when the cause of theerror is corrected.

FMM8571E Unable to initialize db2.

Explanation: The DB2 instance could not beinitialized.


User response: Check the application logs and DB2logs. Try this operation again when the cause of theerror is corrected.

FMM8572I Output of db2inidb: output.

Explanation: The db2inideb command outputdisplayed.



FMM8573I The password file 'filename' has beenupdated successfully.

Explanation: The password file has been updated withnew or altered passwords.

System action: The password file is updated.


FMM8574E Syntax error: syntaxerror

Explanation: The syntax of this command is not valid.

System action: The password file is not updated.

User response: Check the syntax of your commandincluding its arguments. The correct syntax isdocumented in the User's Guide.



FMM8575E In this command multiple passwordswere set for 'server'. Only one passwordcan be set for each server.

Explanation: Each command can set a serverpassword only once.


User response: Check the command's list ofserver/password arguments for duplicates.

FMM8576E The profile section 'sectionname' does notneed a password.

Explanation: This profile section does not need apassword.


User response: Please check the arguments of yourcommand. In must not contain password definitions forprofile sections other than ORACLE, DB2STANDBY,and DEVICE_CLASS.

FMM8577E The 'directory' file does not exist whichis mandatory for the correct operation ofthe related storage device adapter.

Explanation: Storage device adapters based on thegeneric device adapter framework are required toprovide a customparameters.cfg file. It is expected to bebundled with the storage device adapter. If the file ismissing this indicates a corrupted installation of thestorage device adapter.


User response: Ensure that the storage device adapterhas been properly installed. If necessary, contact thevendor of the storage device adapter.

FMM8578E The backup operation cannot be runbecause the RMAN backup script 'filename' does not contain the keyword"backup" on a single line of text.

Explanation: The Oracle RMAN backup script that isspecified with the profile parameterDATABASE_BACKUP_SCRIPT_FILE must contain thekeyword "backup" on a single line. During an offloadbackup, IBM Tivoli Storage FlashCopy Manager adjuststhis script to contain the incremental level. If thekeyword "backup" is missing or is not placed alone ona single line of text, then the modification of the scriptfails.


User response: Check the script and make sure that itcontains the keyword "backup" on a single line with noother text.

FMM8583E Multiple possible values for parameter'INCREMENTAL_LEVEL' detected:ambigous statements

Explanation: Multiple specifications of the parameter'INCREMENTAL_LEVEL' with overlapping time spanshave been detected in the profile.


User response: The parameter'INCREMENTAL_LEVEL' can be specified multipletimes within the profile to use different values atdifferent days of the week or different times during theday. But these multiple definitions must not overlap.Correct the time specifications. Try the operation again.

FMM8584I Delete command completed successfully.

Explanation: The object(s) specified with the deletecommand were successfully deleted from the TSMserver.

System action:


FMM8585W Delete command completed successfully,but had warning(s).

Explanation: The object(s) specified with the deletecommand were deleted with warning(s) from the TSMserver.

System action:

User response: Check the Backup Object Manager logfile for further detailed messages and if required, dothe requested interventions manually.

FMM8586I Delete command was aborted.

Explanation: The delete command was aborted by theuser. No object(s) were deleted from the TSM server.

System action:


FMM8587E Delete command failed due to an error.

Explanation: The delete command failed duringexecution. Not all objects were deleted from the TSMserver.

System action:

User response: Check the Backup Object Manager logfile for further detailed messages and try to resolve theerror which led to the delete failure. Retry the action. Ifthe error still exists, contact the IBM Support.



FMM8588E Delete command has not been started orno delete result information is available.

Explanation: This message indicates that an operationdid not complete successfully. Typically, some othererror condition was detected before.

System action:

User response: Contact the IBM Support.

FMM8589E Query command failed due to an error.

Explanation: The query command failed duringexecution. Not all queried objects can be displayed.

System action:

User response: Check for and respond to precedingerror messages in the Backup Object Manager log. Inthe absence of preceding error messages, contact IBMSupport.

FMM8596E The virtual machine 'vm name' withinstance UUID 'source vm instance uuid'cannot be backed up because it isdistributed across multiple datastores.Distributed virtual machines are notsupported for the followingenvironments: IBM DS8000 IBMNSeries NetApp.

Explanation: The specified virtual machine cannot bebacked up by IBM Tivoli Storage FlashCopy Managerbecause of environmental limitations. See error messagefor more detail.


User response: Exclude the specified virtual machinefrom the backup or use consistency groups in case theIBM XIV storage system is used.

FMM8601E The following device class sections aremissing in the profile:

Explanation: Some profile parameters refer to deviceclass sections that are not specified in the profile.


User response: Add the missing device class sectionsto the profile or adjust the specified profile parameters.

FMM8602E The parameter profile parameter isreferring to device class section 'deviceclass' which does not exist in the profile.

Explanation: The specified profile parameter isreferring to a device class section that is not specifiedin the profile.


User response: Add the missing device class section to

the profile or adjust the specified profile parameter.

FMM8603E Parameter illegal option is not a validparameter for keyword profile parameter.

Explanation: One of the specified parameters isinvalid.


User response: Correct the invalid parameter in theprofile.

FMM8610I Restoring type ...

Explanation: The restore of type has started.

System action:


FMM8611I Do you want to overwrite the existingdatabase (y/n)?

Explanation:

System action:

User response:

FMM8612I Continuing restore ...

Explanation: The database restore continues.

System action:


FMM8613E Terminating restore ...

Explanation: An error occurred, and the databaserestore terminates.

System action:

User response: Check for and respond to precedingerror messages in the Backup Object Manager and theshared library run logs. Additional information may befound in the DB2 diagnostic log (db2diag.log).

FMM8614E The virtual machines 'vm1' and 'vm2'have the same UUID 'uuid'. UUID's needto be unique within a backup run.

Explanation: The two specified virtual machines havethe same UUID. IBM Tivoli Storage FlashCopyManager cannot process two virtual machines with thesame UUID.


User response: Update the UUID of one of the virtualmachines.



FMM8615I Restore command completedsuccessfully.

Explanation: The object(s) specified with the restorecommand were successfully restored from the TSMserver.

System action:


FMM8616W Restore command completedsuccessfully with warnings.

Explanation: The object(s) specified with the restorecommand were restored with warning(s) from the TSMserver.

System action:

User response: Check the Backup Object Manager logfile for further detailed messages and if required, dothe requested interventions manually.

FMM8617I Restore command was aborted.

Explanation: The restore command was aborted bythe user. No object(s) were restored from the TSMserver.

System action:


FMM8618E Restore command failed due to an error.

Explanation: The restore command failed duringexecution. Not all objects were restored from the TSMserver.

System action:

User response: Check the Backup Object Manager logfile for further detailed messages and try to resolve theerror which led to the restore failure. Retry the action.If the error still exists, contact the IBM Support.

FMM8619E Restore command has not been startedor no restore result information isavailable.

Explanation: This message indicates that an operationdid not complete successfully. Typically, some othererror condition was detected before.

System action:


FMM8621I Restoring file 'file name' ...

Explanation: The system started restoring the fileindicated.

System action:


FMM8622I Deleting type ...

Explanation: The deletion of type has started.

System action:


FMM8623I Deleting file 'file name' ...

Explanation: The system started deleting the fileindicated.

System action:


FMM8626W The Tablespace Definition Information'file name' could not be deleted.

Explanation: The system tried to remove the TDIimage from TSM, but did not succeed.

System action:

User response: Try to remove the image manuallyusing the Backup Object Manager raw delete facility.

FMM8628E Found VM with name 'vmname' indatastore 'dsurl' but not in the backup orin the infile.

Explanation: All VMs included in the Datastore torestore have to be part of either the VMs included inthe backup or the vms in the exclude list in the infile.

System action:

User response: Add the VM to the exclude list of theinfile

FMM8629E The 'variable name' environment variableis not set.

Explanation: The specified environment variable is notset, processing cannot continue for the requestedoperation.


User response: Ensure that when you run the productthat you use the correct user ID so that theenvironment variable is set.



FMM8630E The command option 'option' must be anumber.

Explanation: An invalid argument was specified forcommand option option.

System action:

User response: Correct the command syntax.

FMM8631I Backup command completedsuccessfully.

Explanation: The backup operation completedsuccessfully; the backup image can be used forrestoring. In the case of a full database backup, the TDIimage was generated and stored to TSM, too.

System action:


FMM8632W Backup command completedsuccessfully with warnings.

Explanation: The backup operation completedsuccessfully; the backup image can be used forrestoring. However, some problems occurred.

System action:

User response: Check the warning messages and takecorrective actions if necessary.

FMM8633E The configured VCenter server is the'found API version' version, which is notsupported by IBM Tivoli StorageFlashCopy Manager.

Explanation: The configured vCenter server has anunsupported API version.

System action: Processing ends;

User response: Use another vCenter server that has asupported API version or upgrade this vCenter serverto a supported API version.

FMM8634E Backup command failed due to an error.

Explanation: No backup was made due to previouserrors.

System action:


FMM8635E The command option 'option' must be afloating point number.


System action:


FMM8636E The command option 'option' must beone of values.


System action:


FMM8637I Type state backup of 'alias' started ...

Explanation: A backup operation of database alias oftype type has started.

System action:


FMM8638I Type state backup of tablespace(s)tablespace#1,...,tablespace#n of 'alias' started...

Explanation: A backup operation of table space(s)tablespace#1 ... tablespace#n of database alias of type typewas started.



FMM8639I Including log files in backup image ...

Explanation: The DB2 log files are stored as part ofthe backup image.

System action:


FMM8640I Using number buffers with a size of size...

Explanation: For backup or restore operations, theindicated number of buffers of the size displayed areused.

System action:


FMM8641I Using number session(s) ...

Explanation: For backup or restore operations, theindicated number of TSM sessions is used.

System action:




FMM8642I Using a degree of parallelism of number...

Explanation: For backup or restore operations, thedegree of parallelism is displayed.

System action:


FMM8643I Using vendor library at 'lib path' ...

Explanation: For backup or restore operations, thenamed vendor library is used.

System action:


FMM8644W Offline backups cannot include logfiles. The option –L is being ignored.

Explanation: An offline backup operation was started,requesting the DB2 log files to be included. This is notpossible with an offline backup. The backup is donewithout including DB2 log files.

System action:

User response: Make sure to backup DB2 log filesseparately.

FMM8648I number of files in this run file(s) werestored successfully in this run on the'hostname' node. A total number of storednumber of files totally files out of totalnumber of files files are stored in the databackup that is identified by the external'backup id' backup ID.

Explanation: This is a progress message.


User response: N/A

FMM8649E The automatic deletion of backups isnot supported. Change the value of theparameter name parameter to 0.

Explanation: The automatic deletion of backups is notsupported.


User response: Ensure that the value of the specifiedparameter is set to 0. As a consequence, backups arenot automatically deleted.

FMM8650E To restore from all found_copies detectedredo log copies, required_sessions sessionsmust be opened. But currently onlyconfigured_sessions are allowed.

Explanation: For the object that should be restored

overall found_copies copies have been found on theTivoli Storage Manager server. To allow transparentfailover to other copies in case of errors Data Protectionfor SAP must be able to open required_sessions sessions.But the current configuration allows to open onlyconfigured_sessions sessions.


User response: Check the profile parameterMAX_RESTORE_SESSIONS or if not set check thevalue of parameter MAX_SESSIONS. Increase the valueto be at least as large as found_copies. Ensure the overallnumber of sessions that are configured over all serverstanzas in the Data Protection for SAP profile is at leastas large as found_copies.

FMM8651W Your version of DB2 does not supportincluding log files. The option –L isbeing ignored.

Explanation: A backup was started, requesting theDB2 log files to be included, but your version of DB2does not support this feature. For including DB2 logfiles in the backup image, DB2 V.8.2 or later is required.

System action:

User response: Make sure to backup DB2 log filesseparately.

FMM8652I DB2 version 'version' with number bitsdetected.

Explanation: The indicated DB2 version was detectedby Backup Object Manager.

System action:


FMM8653I Using autonomic buffer size andnumber of buffers ...

Explanation: The buffer size and the number ofbuffers used for backup or restore is automaticallydetermined by DB2.

System action:


FMM8654I Using an autonomic buffer size withnumber buffers ...

Explanation: The buffer size used for backup andrestore is automatically determined by DB2. Thenumber of buffers to be used was specified in the callto the Backup Object Manager.

System action:




FMM8655I Using an autonomic number of bufferswith a size of size ...

Explanation: The number of buffers to be used forbackup and restore are determined by DB2. The buffersize to be used was specified in the call to the BackupObject Manager.

System action:


FMM8656I Using an autonomic degree ofparallelism ...

Explanation: The number of DB2 processes (UNIX orLinux) or threads (Windows) used for reading orwriting data from/to table space containers duringbackup and restore is determined by DB2.

System action:


FMM8657W Number is not a valid partition numberfor a non–partitioned database.Assuming partition 0.

Explanation: The partition number specified in thecall to Backup Object Manager does not denote a validpartition of the database. Therefore, the defaultpartition 0 will be used by DB2 and by Backup ObjectManager.

System action:

User response: If your database is not partitioned donot specify the partition number for further actions.

FMM8658E Number is not a partition number of thedatabase or does not denote a partitionon this host.

Explanation: The partition number specified does notdenote a valid database partition or is not the partitionlocated on the system where Backup Object Manager iscalled. Backup Object Manager can only operate onpartitions residing on the same host.

System action:

User response: Either change number to a partitionnumber of a local partition, or start Backup ObjectManager from the same host where the partitionresides.

FMM8659I Creating tablespace definitioninformation ...

Explanation: The table space definition information(TDI) is being created in memory.

System action:


FMM8660I Saving tablespace definitioninformation ...

Explanation: The table space definition information(TDI) is being stored on the TSM server.

System action:


FMM8661W Could not create Tablespace DefinitionInformation.

Explanation: The system could not collect the tablespace definition information. The backup was madewithout TDI. As a result, the backup can be used forrestoring the system, but it cannot be used for restoringto a different location.

System action:

User response: Ensure that your database is enabledto accept CLI connections.

FMM8662W Could not save Tablespace DefinitionInformation.

Explanation: The system could not save the TDI onTSM. The backup was made without TDI. As a result,the backup can be used for restoring the system, but itcannot be used for restoring to a different location.

System action:


FMM8663W The Tablespace Definition Informationcontains device containers of a typeunsupported by BackOM redirectedrestore.

Explanation: A backup of a database using devicecontainers was requested. The backup was successful, itcan be used to restore the system, but it cannot be usedfor restoring to a different location. Restoring to adifferent location is not supported with devicecontainers.

System action:


FMM8664E Connecting to 'alias' using CLI failed.The return code was return code.

Explanation: The system tried to connect to thedatabase named via the CLI. The operation did notsucceed and returned the error code indicated.

System action:

User response: Ensure that your database is enabledto accept CLI connections.



FMM8665I The backup timestamp is: timestamp

Explanation: The DB2 backup finished successfullywith the timestamp timestamp.

System action:


FMM8666I Redirecting container of tablespace tablespace with ID id.

Explanation: The named table space is restored to thelocation requested.

System action:


FMM8667W Tablespace tablespace with ID id was notredirected because its container onsource system SID is not located in apath starting with 'path'.

Explanation: The named table space of type SMS wasnot redirected because the definition of the table spacecontainer in the source system does not match thedatabase characteristics that Backup Object Managerexpects and that are cited in the message. Therefore,Backup Object Manager tries to restore the table spaceto a location identical to the location in the originalsystem.

System action:

User response: Make sure that the table spacementioned can be restored to the original location. Thisrequires that the user initiating the redirected restorehas the appropriate permissions for placing the tablespace container in this location and that the table spacecan be restored without overwriting other data. Inorder to avoid this situation in the future, theadministrator of the source system may want torecreate the table space according to the databasecharacteristics Backup Object Manager expects.

FMM8668I Tablespace Definition Informationcreated successfully.

Explanation: The metadata concerning the phyiscaldatabase layout necessary for automatic redirectedrestores driven by BackOM were created successfully.

System action:


FMM8669I Free space of device with ID idcontaining the container storage path'storage_path' are free_space.

Explanation: After assigning a container storage pathto a dedicated device the remaining free space iscalculated and returned to the user.

System action:


FMM8670I Remaining free space of device with ID'id' after assigning container'container_name' of size size are free_space.

Explanation: After assigning or creating a tablespacecontainer on a dedicated device the remaining freespace is calculated and returned to the user.

System action:


FMM8671I Using automatic storage path(s)storage_path.

Explanation: A dedicated automatic storage path willbe used.

System action:


FMM8672I Redefining container path(s) ofautomatic storage tablespace tablespacewith ID id.

Explanation: The path(s) an automatic storagetablespace uses as a starting point for the container(s)will be redefined.

System action:


FMM8673E The Datastore name 'dsname' is notunique within one Backup.

Explanation: The backup contains more then oneDatastore with the same name


User response: replace the Datastore name withDatastore URL in the infile

FMM8674E A syntax error was detected in thefilename file: token

Explanation: A syntax error was detected in thespecified file. This storage device adapter file cannot bemodified. If this file was not accidentally edited, thiserror indicates that there is a version conflict betweenIBM Tivoli Storage FlashCopy Manager and the storageadapter in use.


User response: Verify that the specified file is notcorrupted or modified. Also, verify that the storagedevice adapter file is compatible with the version ofIBM Tivoli Storage FlashCopy Manager that is installed.



FMM8675E The default value for the parameter_nameparameter in the filename file is missing.

Explanation: A default value is mandatory for thespecified parameter in the specified file. This storagedevice adapter file cannot be modified. If this file wasnot accidentally edited, this error indicates that there isa version conflict between IBM Tivoli StorageFlashCopy Manager and the storage adapter in use.


User response: Verify that the specified file is notcorrupted or modified. Also, verify that the storagedevice adapter file is compatible with the version ofIBM Tivoli Storage FlashCopy Manager that is installed.

FMM8676E The 'datastore name' datastore alreadyexists on the datacenter.

Explanation: The datastore name is already defined onthe ESX host and is unavailable.


User response: Ensure that the datastore is removedfrom the ESX host before you run the instant restoreoperation.

FMM8681E One of the target datastores is notavailable on the ESX host. The datastorecannot be found by using the originalURL 'datastoreurle' or any other URL.

Explanation: The target datastore is not availablebecause the LUNs might not all be mounted correctly.


User response: Before you run a restore operation,ensure that all target datastores needed for thisoperation are available on the ESX host and that allassigned LUNs are mounted correctly.

FMM8682W The current user ID does not havepermissions to create or update tasks inthe vCenter.

Explanation: The task progress cannot be created orupdated in the vCenter because of missing privileges.


User response: Ensure that the user ID used toconnect to the vCenter has privileges to create andupdate tasks in the vCenter. These privileges must beassigned at datacenter level or higher in the inventoryhierarchy.

FMM8690E Free space check for container 'path'failed. Only free bytes free space left ondevice with ID 'id' but required bytesrequired.

Explanation: The system requires a table spacecontainer of the size indicated at the path named, butthere is not sufficient free space available to create it.

System action:

User response: Try to make available the free spacerequired, for example by 1. Removing some files on thevolume or file system the container is to reside on. 2.Increasing the size of the file system the container is toreside on. 3. Shrinking the size of the containerrequested so that it fits in the free space. Note: BackupObject Manager assumes that a small part (0.05%) ofthe free space will be required by the operating systemfor administrative use. As a consequence, only 99.95%of the free space on the volume or file system isactually available.

FMM8691E The password file 'file name' cannot beread.

Explanation: The IBM Tivoli Storage FlashCopyManager password file is unusable.

System action: The operation exits withoutcompleting.

User response: Check the file permission. If the filehas been changed on the production system, make surethe file has been copied to backup or clone systems. Ifthe problem persists, recreate the password file byentering the command 'fcmcli –f password' on theproduction system and copy it to backup or clonesystems.

FMM8692E The requested data could not beretrieved.

Explanation: The TDI data of a backup image couldnot be retrieved and displayed.

System action:

User response: Look for and respond to precedingerror messages.

FMM8693E More than one Tablespace DefinitionInformation file matches your query.

Explanation: More than one TDI file matching thesearch criteria was found on TSM.

System action:

User response: Specify additional BackOM commandoptions to restrict the result set.



FMM8700E Internal parser error in TablespaceDefinition Information parser.

Explanation: An unexpected error occurred in the TDIparser.

System action:


FMM8701E This parser cannot process TablespaceDefinition Information version version.

Explanation: The current version of Backup ObjectManager is not compatible with the version the TDIimage was created with. As a consequence, the TDIdata cannot be processed.

System action:

User response: Check the release notes for theappropriate migration procedure.

FMM8702E Too many errors. Bailing out.

Explanation: The TDI parser encountered a number oferrors. Restoring is stopped.

System action:


FMM8703E Out of memory.

Explanation: The TDI parser encountered a token thatcannot be read into the main memory. The TDI imagecannot be processed, and restoring is stopped.

System action:


FMM8704E Error while reading input file.

Explanation: The TDI parser tried to read more datafrom disk or from TSM, but did not succeed.

System action:

User response: Ensure that the TDI image to beprocessed exists at the expected location and that thesystem has sufficient privileges to read it.

FMM8705E Error in line line number.

Explanation: The TDI parser encountered a syntaxerror in the line indicated. As a consequence, the TDIimage cannot be analyzed.

System action:

User response: Respond to the error message andcorrect your TDI image.

FMM8706E The container at 'path' is inappropriatefor tablespace tablespace.

Explanation: The container at the location indicatedcannot be added to the table space named because ofincompatible properties.

System action:

User response: Check the properties of the containerand the table space. Ensure that the IDs of thecontainers are unique for the table space named.

FMM8707E Missing statement keyword in block blockname near line line number.

Explanation: A keyword is missing in the namedblock ending at the line given.

System action:

User response: Insert the required statement in theblock.

FMM8708E The [TDI] header block must be thefirst block.

Explanation: The TDI image does not start with therequired header ([TDI] block). Only comments orwhitespace are allowed before this block.

System action:

User response: Ensure that the [TDI] block is the firstblock in the TDI image.

FMM8709E The required block block name ismissing.

Explanation: The named block is missing in your TDIimage.

System action:

User response: Insert the missing block using validvalues.

FMM8710W Duplicate block block name ignored atline line number.

Explanation: At the line indicated, a block beginswhose name was encountered before. The systemignores the duplicate block; it uses the data from thefirst occurrence of duplicate blocks.

System action:

User response: Make sure that block names areunique within a TDI image.



FMM8711W Duplicate statement keyword ignored inline line number.

Explanation: At the line indicated, a duplicatestatement was encountered within a block. The systemignores the duplicate statement.

System action:

User response: Make sure to not specify duplicatestatements within a block.

FMM8715E Failed to create directory 'path'. Reason:reason

Explanation: The path indicated could not be created.

System action: The operation stops. The operationcannot continue until the error is resolved.

User response: Check the properties of the pathindicated and make sure that its properties and theproperties of the parent directory are set accordingly.

FMM8727E No instance found managing database'database name'.

Explanation: The DB2 instance, which manages thenamed database 'image_name' could not be detected.



FMM8728E Could not attach to instance 'instance'.

Explanation: BackOM was not able to attach to theinstance instance.

System action:

User response: First, check the system environmentfor possible instance candidates. Try the action again byadditionally specifying the BackOM command option'–i <instance name>'.

FMM8729I Checking system resources ...

Explanation: Prior to starting the redirected restore byBackOM the existing system resources, e.g. free spaceof a file system will be checked.

System action:


FMM8730I Scaling tablespace containers to numberpercent ...

Explanation: All table space containers will beincreased by the percentage indicated during the tablespace container redefinition step.

System action:


FMM8731I Normalizing tablespace containers ...

Explanation: All containers of a table space will be ofthe same size after redefinition.

System action:


FMM8732E The Tablespace Definition Informationused with the redirected restoreoperation contains an invalid databasealias.

Explanation: There is an invalid database aliasspecified in the alias statement of the TDI image.

System action:

User response: Provide a valid alias.

FMM8733E The Tablespace Definition Informationused with the redirected restoreoperation contains an invalid instancename.

Explanation: There is an invalid database instancespecified in the <instance> statement of the TDI image.

System action:

User response: Provide a valid instance name.

FMM8734E The Tablespace Definition Informationused with the redirected restoreoperation contains an invalid partitionnumber.

Explanation: There is an invalid partition numberspecified in the <Node> statement of the TDI image.

System action:

User response: Provide a valid partition number.

FMM8736E Tablespace tablespace must have at leastone container.

Explanation: The TDI image defines the table spacenamed without containers.

System action:

User response: Ensure that there is at least onecontainer associated with every table space.

FMM8737E Tablespace tablespace has containers withthe combined storage too small.

Explanation: The number of used pages of the tablespace named exceeds the combined size of its tablespace containers defined in the TDI image.

System action:

User response: Ensure that every table space has



containers of a combined size that is sufficient to holdthe used pages of the table space.

FMM8738E The container at path has a page sizethat is incompatible with its tablespace.

Explanation: The container indicated does not havethe same page size as its table space according to thedefinitions in the TDI image.

System action:


FMM8739E The type of the container at path isincompatible with its tablespace.

Explanation: The container indicated cannot be usedwith its associated table space according to thedefinitions in the TDI image. SMS table spaces can onlyhave path containers, and DMS table spaces must havefile or device containers.

System action:

User response: Ensure that the appropriate types ofcontainers are used with each table space.

FMM8740E The path path of a container must not berelative.

Explanation: In the TDI image, the named pathdefining a container does not seem to be a fullyqualified path.

System action:

User response: Ensure that all paths in your TDI arefully qualified.

FMM8741E The container at path would overwriteexisting files or directories.

Explanation: The TDI image contains the definition ofthe container indicated whose location is already inuse. This is only allowed when restoring to the sourcedatabase. Restoring to a different location is stopped.

System action: Ensure that all path containers definedin the TDI image point to non–existing paths and allfile containers point to non–existing files.

User response:

FMM8742E The container at path is a devicecontainer which is not supported.

Explanation: In the TDI image, a device container isdefined. However, device containers are not supportedby Backup Object Manager.

System action:

User response: Do not use device containers.

FMM8743I Local Tablespace Definition Informationcheck returned return code.

Explanation: The TDI with the target database tablespace definition was checked. If the return code givendoes not equal 0 errors occurred.

System action:

User response: In the case of a non–zero return code,contact IBM Support.

FMM8744I Tablespace Definition Informationreplacement check returned return code.

Explanation: The system checked whether the tablespace definitions of the target TDI can replace thedefinitions of the source TDI. If the return code givendoes not equal 0 the table space definitions of thetarget TDI are not valid.

System action:

User response: In the case of a non–zero return code,contact IBM Support.

FMM8745E The Tablespace Definition Informationis invalid.

Explanation: The TDI with the target table spacedefinitions is not valid. Restoring to a different locationis stopped.

System action:

User response: Check the Backup Object Manager logfor the return code of the validation. Check for andrespond to preceding error messages in the BackupObject Manager log.

FMM8746I The Tablespace Definition Informationis valid.

Explanation: The TDI with the target table spacedefinition is valid. Processing continues.

System action:


FMM8747E Not all tablespaces of the originaldatabase are contained in the TablespaceDefinition Information.

Explanation: At least one table space of the originaldatabase is missing in the TDI definitions of the targetdatabase. However, a new location must be given forall table spaces of the original database. Therefore,restoring to a different location is stopped.

System action:

User response: Provide the information on themissing table spaces and their containers.



FMM8748E The Tablespace Definition Informationdoes not define enough storage to holdall the data of the original database.

Explanation: The target TDI has at least one tablespace whose containers are too small to hold the dataof the source database.

System action:

User response: Increase the container size or addmore containers to the table spaces.

FMM8749E The page size of a tablespace in theTablespace Definition Information doesnot match the one of the originaldatabase.

Explanation: The target TDI contains at least one tablespace with a matching ID in the source TDI, but theirpage sizes do not match.

System action:

User response: Ensure that table spaces have the samepage sizes in both the source and the target TDI.

FMM8750E The number of used pages of atablespace in the Tablespace DefinitionInformation does not match the one ofthe original database.

Explanation: The target TDI contains at least one tablespace with a matching ID in the source TDI, but thenumber of used pages of the target table space does notmatch the number of used pages in the originaldatabase.

System action:

User response: Ensure that the number of used pagesof a table space is the same in both the source and thetarget TDI.

FMM8751E The tablespace type in the TablespaceDefinition Information does not matchthe one of the original database.

Explanation: The target TDI holds at least one tablespace with a matching ID in the source TDI, but thetable space types are different.

System action:

User response: Ensure that the type of a table space isthe same in both the source and the target TDI.

FMM8752E BackOM does not support redirectedrestore with device containers.

Explanation: The target TDI contains at least onedefinition of a device container. However, devicecontainers are not supported by Backup ObjectManager's redirected restore function.

System action:

User response: Do not use the Backup ObjectManager's redirected restore facility for devicecontainers.

FMM8753E A container cannot be created at path.

Explanation: Either the location where the table spacecontainer is to be created does not exist, or thepermissions of the user are not sufficient.

System action:

User response: Check the location and thepermissions.

FMM8755I Getting reference Tablespace DefinitionInformation from TSM ...

Explanation: Retrieving the appropriate TDI to beused by internal checking routines from the TSMserver.

System action:


FMM8756W Could not get reference TablespaceDefinition Information from TSM. Noinput validation is done.

Explanation: The system could not find a TDI imagematching the database backup to be restored on TSM.The restore action will be continued, but the input datacannot be validated before the restore starts.

System action:


FMM8757I Performing redirected restore from'source alias' to 'target alias' ...

Explanation: Redirected restore of source alias to targetalias is starting.

System action:


FMM8758E The Tablespace Definition Informationdoes not contain data for tablespace'tablespace'.

Explanation: A definition of the table space named isexpected to be provided in the TDI, but could not befound.

System action:

User response: Ensure that all table spaces of thesource database are also defined in the target TDI.



FMM8759E Redirecting of at least one containerfailed.

Explanation: The system tried to create the containersfor a table space, but at least one of them could not beredirected to a different location. Usually, the locationof one of the table space containers is not allowed. Alist of containers the system tries to create can be foundin the Backup Object Manager log. One of them failed.

System action:

User response: Check for and respond to further errormessages in the Backup Object Manager log.

FMM8760E Directory 'directory' could not be created.

Explanation: The system tried to create the directoriesto place the containers in, but at least one failed.

System action:

User response: Ensure that the system has sufficientprivileges to create the directories at the desiredlocations.

FMM8761E The container at path does not have theminimum size of two extends.

Explanation: A table space container to be createdmust have at least the size of two extends.

System action:

User response: Correct the size of the container to becreated.

FMM8762I Set tablespace container with ID id andname 'tablespace_container'.

Explanation: Backup Object Manager redirects a tablespace container to the ID and name indicated.

System action:


FMM8763E The extent size of a tablespace in theTablespace Definition Information doesnot match the one of the originaldatabase.

Explanation: The extend sizes of corresponding tablespaces defined in the source and target TDIs must beequal. However, for at least one table space differentextend sizes are defined in the source and targetdatabases.

System action:

User response: Define matching extend sizes forcorresponding table spaces.

FMM8765I Checking redirected restore from 'sourcealias' to 'target alias' ...

Explanation: The system is testing whether theoriginal database can be restored to the target location.The system checks the following conditions:

v Does the file system where the table space containersare to be created has sufficient free space. (Ifspecified, normalizing and scaling are alsoconsidered.)

v Are there are existing files and directories that areidentical to the containers that are defined for thetarget database. This would indicate that a databaseof same name and of same structure already exists,and data could be ovewritten.

v Do the structures of the source and target databases(table space types, page sizes, extend sizes) allow fora redirected restore.

System action:


FMM8766I Check successful. Redirected restorepossible with these settings.

Explanation: The redirected restore test finishedsuccessfully. Thus, the redirected restore operation canbe started with the options specified for the test run.

System action:


FMM8767W Warnings occurred.

Explanation: The redirected restore test detected oneor more minor conflicts. These conflicts may or maynot prevent a successful redirected restore operation.Nevertheless, it is recommended to resolve them.

System action:

User response: Check for and respond to precedingwarning messages in the Backup Object Manager log.

FMM8768E Check failed. Redirected restore notpossible with these settings.

Explanation: The redirected restore test detected oneor more major errors which will prevent a successfulredirected restore with these settings.

System action:


FMM8769E Found multiple Tablespace DefinitionInformation matching the giventimestamp. Additional search conditionsneeded.

Explanation: More than one TDI file for a database



backup image was found on the TSM server. In such ascenario, the integrity of the metadata assigned to adatabase backup images is violated and prevents anautomatic redirected restore driven by BackOM.

System action:


FMM8770I Getting Tablespace DefinitionInformation used with the redirectedrestore operation from TSM...

Explanation: The system is retrieving the TDI imagefrom the TSM server.

System action:


FMM8771E The Tablespace Definition Informationused with the redirected restoreoperation could not be retrieved.

Explanation: The TDI image specified could not befound.

System action:

User response: Provide the correct location of the TDIimage.

FMM8772E The selected database has a structurethat prevents automatic cloning.

Explanation: You tried to clone an SAP database usingredirected restore, but the database does not have thedefault directory structure of an SAP database. Thecloning facility of Backup Object Manager redirectedrestore cannot be used for this system.

System action:

User response: You may use either the interactive orthe batch mode of Backup Object Manager redirectedrestore.

FMM8773E The interactive modification of thecontainers failed.

Explanation: You tried to interactively change thelocation of containers, but this operation failed.



FMM8776E You are not allowed to delete thiscontainer.

Explanation: You tried to delete the last container of atable space. However, at least one container must beavailable to every table space.

System action:

User response: Make sure that there is at least onecontainer defined for every table space.

FMM8798E Due to errors, you cannot continue theoperation.

Explanation: You tried to start a restore operationafter redefining the containers interactively, but errorswere detected in the input data. The operation cannotcontinue.

System action:

User response: Check all table spaces with '!!' errormarks in the list and correct the definitions of theircontainers. Then continue.

FMM8799E A container must have a size of at leasttwice the extent size (minimum size forthis tablespace).

Explanation: The container size specified is too small.The minimum size of a container is twice the extentsize.

System action:

User response: Correct the container size.

FMM8800I The command is: command

Explanation: Displays the command that was issued.The following commands are possible: Backup, Restore,Archive/Retrieve.

System action:


FMM8801I Time: time ––– PID: PID_Number

Explanation: Displays the process id of the DB2process which called the shared library.

System action:


FMM8802I Found number type image(s) on TSMserver.

Explanation: For restore and delete operations DataProtection for SAP queries TSM for backup images bymeans of a timestamp and shows the number of foundimages.

System action:




FMM8803I The DB2 image size for this session isabout 'size'.

Explanation: The estimated size of the data to bebacked up is displayed.

System action:


FMM8804W The recovery log could not be written.

Explanation: After every backup or restore, DataProtection for SAP writes a record into the recovery logfile tdprlf.<SID>.node_name.log. It is located in the pathpointed to by environment variable TDP_DIR.

System action:

User response: Check, if the permissions are setcorrectly and if there is sufficient free space in your filesystem.

FMM8805I The restore was cancelled by the user.Existing data not overwritten.

Explanation: The existing database is still operational.

System action:


FMM8806I product version.release.modification.level(build_numberbeta) build_date

Explanation: Writes version information into theproduct log file.

System action:


FMM8807I Archive log file 'log number' of chain 'logchain number'.

Explanation: Writes information about the log file tobe archived into the product log file.

System action:


FMM8808I Retrieve log file 'log number' of chain 'logchain number'. Seeking for TSM image'image'.

Explanation: Writes information about the log file tobe retrieved into the product log file.

System action:


FMM8810I Cleaning up resources of process'PID_number'.

Explanation: All resources used by the product will bereleased.



FMM8812I Committed TSM sessions of this backuprun will be deleted.

Explanation: During a backup with multiple sessions,an error occurred. The backup operation is stopped.TSM sessions already committed during this operationare being deleted from the TSM server in order toprevent them from being considered restorable.

System action:


FMM8813E Error deleting committed TSM sessions.

Explanation: One or more committed TSM sessionscould not be deleted during the postprocessing of thefailed backup run.

System action:

User response: Use the Backup Object Manager todelete the file(s) manually.

FMM8814I Inquired TSM with mask 'search mask'.

Explanation: The string denoted is used to inquireTSM for backup images.

System action:


FMM8815I Information for Log Manager:DB2_instance DB2_database_nameDB2_database_aliaslog_and_log_chain_number partition

Explanation: The information listed is provided to theDB2 Log Manager.

System action:


FMM8816I DB2 version 'version' detected.

Explanation: TSM for ERP is running on a systemwhere DB2 version version is set up.

System action:




FMM8817I No corresponding committed TSMsession(s) found. Nothing will bedeleted.

Explanation: The cleanup of a failed TSM for ERPdatabase backup could not find any partial TSMbackup image of that run already stored on the TSMserver for deletion.

System action:


FMM8818W Invalid value specified forBACKOM_LOCATION.

Explanation: The BackOM executable was not startedfor collecting database metadata due to an invalidspecification.

System action:

User response: Check the value of the TSM for ERPconfiguration parameter BACKOM_LOCATION. Theparameter can be found in the vendor environment fileand must contain the fully qualified name of theBackOM executable.

FMM8819I The TSM objects matching with mask'search mask' will be deleted.

Explanation: The cleanup of a failed TSM for ERPdatabase backup will delete any partial TSM backupimage of that run already stored on the TSM server andmatching search mask .

System action:


FMM8820E No valid TSM session found.

Explanation: A running TSM for ERP workflow couldnot continue due to a missing TSM session.

System action:


FMM8821I Using option(s) 'options'.

Explanation: The options string specifies vendoroptions that DB2 provides to the TSM for ERP libraryas part of the calling function. These could be optionsdirectly provided as part of the database backup orrestore command or options made persistent in thedatabase configuration, here the parametersVENDOROPT, LOGARCHOPT1 or LOGARCHOPT2.

System action:


FMM8822I Configuration parameter(s): parameters

Explanation: The list specifies a set of runtimeparameters that the TSM for ERP library is using forthe calling workflow.

System action:


FMM8823W Configuration parameterSRC_DB_ALIAS requires parameterSRC_DB_INSTANCE and vice versa.

Explanation: To be able to recover a database after aredirected restore using the built–in DB2 rollforwardcommand, TSM for ERP needs both SRC_DB_ALIASand SRC_DB_INSTANCE.

System action:

User response: Include both parametersSRC_DB_ALIAS and SRC_DB_INSTANCE in the TSMfor ERP vendor environment file and retry the databaserecovery.

FMM8824I Partitioning backup image intosegments of maximum 'size'.

Explanation: The backup image is partitioned intosegments equal to the maximum size value. Thispartitioning is implemented per backup session.


User response: No user response is required.

FMM8825I Creating commit object for sessionsession_id comprising overall numbersegment(s).

Explanation: A commit object is created at the end ofbackup processing. This commit object guarantees theintegrity of the backup object segments that compose abackup session. This action occurs on a per sessionbasis where all backed up segments of a session arestored within that commit object. The commit object isused internally by Tivoli Storage Manager forEnterprise Resource Planning.



FMM8826I Found database image 'image_name'partitioned into number segment(s).

Explanation: The database backup image image_namewas found on Tivoli Storage Manager. This image ispartitioned into number segments.





FMM8827E Missing commit object.

Explanation: The commit object cannot be located onTivoli Storage Manager. The commit object is aprerequisite when restoring segmented backup images.It ensures that a valid database is not destroyed oroverwritten by an incomplete database restore.


User response: Check IBM Electronic Support foradditional information: http://www.ibm.com/software/sysmgmt/products/support/index.html?ibmprd=tivman

FMM8828E A backup object segment associatedwith backup image 'image_name' ismissing.

Explanation: The integrity of the backup image'image_name' is violated due to a missing backup objectsegement.


User response: The backup image 'image_name' cannotbe used for restore. Specify an older backup image forrestore. In addition, start a new database backup assoon as possible.

FMM8831E The properties of the virtual machine'vm name' could not be fetched throughthe vSphere API because they are notset.

Explanation: The properties of the virtual machinecould not be fetched through the vSphere API becausethey are not set on the corresponding object.


User response: Check if the according auxiliary ESXhost is in an operational state.

FMM8832I Note: The GSKit installation is notremoved from ${HOSTNAME} becauseit might be in use by other IBM TivoliStorage FlashCopy Manager instances. Ifneeded, the GSKit can be manuallyuninstalled. For more information, seethe Installation and User's Guide.

Explanation: GSKit is remotely installed on thebackup or cloning system by using SSH. Multipleinstances of IBM Tivoli Storage FlashCopy Managermight exist on the remote system so GSKit is notuninstalled to avoid breaking other instances of IBMTivoli Storage FlashCopy Manager.

System action: Processing continues. GSKit remainsinstalled on the backup or cloning system.

User response: GSKit can be manually uninstalled onthe backup or cloning systems if needed. The user

guide provides details about the necessary steps.

FMM8833W The environment variable'SHLIB_PATH' does not include the path'/usr/lib' which is required for thecorrect operation of GSKit. Ensure thatthe path is added to allow the correctoperation of IBM Tivoli StorageFlashCopy Manager.

Explanation: The environment variable 'SHLIB_PATH'must include the path '/usr/lib' to ensure that theGSKit libraries are found.

System action: Processing continues but IBM TivoliStorage FlashCopy Manager might be non-operational.

User response: Add the path '/usr/lib to theenvironment variable 'SHLIB_PATH'.

FMM8834E An earlier version of GSKit is running:'version'. This version cannot be used forTransport Layer Security (TLS) version1.2.;

Explanation: In a DB2 application environment, IBMTivoli Storage FlashCopy Manager application agentuses the GSKit libraries that are shipped with DB2. Forolder versions of DB2 this GSKit version might be olderthan the one that is shipped with IBM Tivoli StorageFlashCopy Manager. Earlier versions of GSKit do notsupport TLS version 1.2 and therefore TLS version 1.2protocol cannot be enforced.

System action: IBM Tivoli Storage FlashCopyManager cannot operate when you use thisconfiguration.

User response: Either upgrade your DB2 installationto use a newer GSKit version, the minimum version is8.0.14.21 or set the ENFORCE_TLS12 profile parameterto "NO". Run the setup script to configure thisparameter.

FMM8835I Starting synchronous reconcileoperation.

Explanation: The reconciliation process is started andthe processing waits until the reconciliation hasfinished.

System action: Processing waits until reconciliationhas finished.


FMM8836I The reconcile operation has finished.

Explanation: The reconciliation process has finishedand the processing will continue.

System action: Processing will continue.




FMM8837I The synchronous reconcile operation hasterminated. Normal processingcontinues.

Explanation: The reconciliation process has terminatedwith error. The processing will continue. Thereconciliation process will be restarted later. The IBMTivoli Storage FlashCopy Manager repository maycontain invald backup entries until the nextreconciliation process is scheduled.



FMM8838I Starting synchronous delete operation.

Explanation: The delete process is started and theprocessing waits until the delete has finished.

System action: Processing waits until delete hasfinished.


FMM8839I The delete operation has finished.

Explanation: The delete process has finished and theprocessing will continue.



FMM8840I The synchronous delete operation hasterminated. Normal processingcontinues.

Explanation: The delete process has terminated witherror. The processing will continue. The delete processwill be restarted later. The IBM Tivoli StorageFlashCopy Manager repository may contain invaldbackup entries until the next delete process isscheduled.



FMM8841W No IBM Tivoli Storage FlashCopyManager offload daemon was runningin the last minutes minutes. Make surethat the IBM Tivoli Storage FlashCopyManager offload daemon process isrunning.

Explanation: The IBM Tivoli Storage FlashCopyManager offload daemon was not running on the IBMTivoli Storage FlashCopy Manager host since thespecified time interval. This offload daemon process isrequired if IBM Tivoli Storage FlashCopy Managersnapshot backups should be sent to Tivoli StorageManager.

System action: Processing will continue. But the

offloaded backup to Tivoli Storage Manager may notstart.

User response: Verify that the IBM Tivoli StorageFlashCopy Manager offload daemon process is running.Restart this daemon process if it is not running.

FMM8842W The 'lunserial' Logical Unit Number(LUN) was added to the 'dsName'datastore after the backup wascompleted. This LUN will be detachedfrom the vSphere environment.

Explanation: One or more LUNs was added to thedatastore after the backup operation was completed.Tivoli Storage FlashCopy Manager detaches theseLUNs from the ESX host to mount the datastore whenyou perform an instant restore of this datastore.



FMM8843E The virtual machine could not berestored using 'target vm name' VMname. A VM with the same namealready exists in the datacenter.

Explanation: The specified virtual machine could notbe restored because another virtual machine with thesame name already exists in the datacenter.


User response: Specify another virtual machine nameor delete the existing virtual machine in the vCenter.

FMM8899E Interface problem in function function:Value 'value' of parameter 'parameter' isnot supported with DB2 version 'version'.

Explanation: An unknown action code during theprogram execution was encountered.

System action:


FMM9001E Internal error: error

Explanation: The following internal error: error hasbeen encountered.

System action:


FMM9002E Parameter 'all' is not supported.

Explanation: The provided parameter is notsupported. This error can be caused by nodes that arespecified without being separated by commas.


User response: Make sure the specified nodes are



separated by commas, then try the command again.

FMM9003E Incompatible components installed:component name one, component name two

Explanation: The components mentioned in themessage text can not be used together. This may be theresult of an incomplete upgrade.

System action:


FMM9004E Location of the message catalog couldnot be figured out.

Explanation: Data Protection for SAP locates themessage catalog over the install directory. When DataProtection for SAP is exploited through a library likeDB2 or Oracle/RMAN, then the environment variableXINT_NLS_CATALOG_PATH is mandatory.


User response: The environment variableXINT_NLS_CATALOG_PATH may be required..

FMM9005E A not supported by B

Explanation: The installed version of product B doesnot support product A. Most likely you need toupgrade product B.

System action:

User response: Contact the IBM Support.

FMM9006E Internal error while readingenvironment variable: variable


System action:


FMM9007W An error occurred while terminating theapplication: the error

Explanation: While terminating the application, anerror occurred. This has no impact on the success of theoperation.

System action:


FMM9008E This product requires at least versionnumber of product name to be installed.

Explanation: The version of the application productname is not supported by this application. Most likelyapplication product name needs to be upgraded.

System action:


FMM9009W The following products are notcompatible: product name first (productversion first) and product name second(product version second).

Explanation: This message is similar to FMM9008E.But in this case it's not obvious which one of theproducts needs to be upgraded.

System action:


FMM9010E Could not determine installationdirectory for program. Please restart theprocess using a fully qualified name.

Explanation: The name of the path where a givenprogram is located could not be determined.

System action:


FMM9011E There was no response received withinnumber seconds; timeout is expired. Youcan increase the timeout by specifyingthe profile parameter timeoutphase for thecurrent phase of the backup or restoreoperation.

Explanation: The communication between twoprogram components was suspended or stopped,which can lead to a timeout.

System action:

User response: Increase the timeout by specifying theprofile parameter TIMEOUT_<PHASE> for the currentphase of the backup or restore operation. If this doesnot solve the probblem please contact your IBMsupport personnel.

FMM9012E One of the requested data containers isalready the subject of a restore.

Explanation: A restore of the same data has alreadybeen requested.


User response: Multiple restore operations are usuallyprevented by the database system. If there are nomultiple restore operations performed concurrently,then contact IBM support for this problem.

FMM9013E Concurrent restore of objects beingbacked up with multiple device agentsis not supported.

Explanation: This special restore scenario isunsupported.



System action:


FMM9014E Failed to load library: library reason:reason

Explanation: The ACS library could not be loaded.

System action:


FMM9015E Failed to locate functions in library:library reason: reason

Explanation: One or more functions could not befound in the ACS library.

System action:


FMM9016E The database is not mounted.

Explanation: The database must be mounted so thatIBM FlashCopy Manager Prerequisite Checker can berun.


User response: Mount the database and start IBMFlashCopy Manager Prerequisite Checker again.

FMM9017E The file system 'mountpoint' on volumegroup 'volume group' contains data andredo log files from the same databaseinstance.

Explanation: FlashCopy Manager does not supportlog and data files on the same volume group.

System action: The volume group layout check fails.

User response: Change the database layout so that thedata and redo log files are on separate volume groups.

FMM9018E The volume group 'volume group'contains file systems with data files,and file systems with redo log files.

Explanation: FlashCopy Manager does not supportlog and data files on the same volume group.

System action: The volume group layout check fails..

User response: Change the database layout so that thedata and redo log files are on separate volume groups.

FMM9019E The following control files are notincluded in any database or redo log filevolume groups: List of Controlfiles

Explanation: The control files must be on the volumegroup where the database redo log files or the datafiles are stored.


User response: Change the database layout so that thecontrol files are on the data or redo log files volumegroups.

FMM9020E The following database File Type filesare on the root volume group: List ofFiles

Explanation: The database redo log files and data filesmust be on a volume group that does not contain theroot filesystem.


User response: Change the database layout so thatdata files and redo log files are on volume groups thatdo not contain the root filesystem.

FMM9021E Querying the operation systeminformation for the following files andfile systems failed: List of Files

Explanation: IBM FlashCopy Manager PrerequisiteChecker was not able to get OS information like logicalvolume or volume group from the listed files. Maybethe files are on file system that is not managed by aLogical Volume Manager.


User response: Change the database layout so thatdata and redo log files are on file systems that aremanaged by a Logical Volume Manager.

FMM9022I The Volume Group layout check(fcm.volume_group_layout) validates ifthe prerequisites of the database volumegroup layout, that are listed in thePre-installation Checklist PDF, arefulfilled.

Explanation: The volume group layout must be set upas described in the Pre-installation Checklist PDF.


User response:

FMM9023E The volume group 'volume group'contains database files as well as thefile or folder 'volume group':

Explanation: The volume group layout is wrong, thelisted file or folder must not be on a volume group thatcontains database data files or log files.


User response: Change the database layout so that thelisted folder is not on a data or log volume group.



FMM9024E The following control files are includedin a data file volume group: List ofControlfiles

Explanation: The control files must not be on thevolume group where the database data files are stored.


User response: Change the database layout so that thecontrol files are not on the data volume groups.

FMM9025I The database version check(fcm.db_Version) validates if thedatabase level is supported byFlashCopy Manager.

Explanation: The database must be on a supportedlevel, see the Pre-installation Checklist PDF for moredetails.


User response:

FMM9026I The application check(fcm.application_environment) validatesif the application is DB2 or Oracle DB.

Explanation: The supported applications are Oracle,DB2, and Custom Applications (CAA).


User response:

FMM9027I The storage management networkconnection check (storage.validatePort)validates if storage management can bereached through the TCP/IP network.

Explanation: FlashCopy Manager must be able to bereach the storage management through the network.


User response:

FMM9028E The file system 'volume group' containsdatabase files and the file or folder'volume group':

Explanation: The file system layout is wrong, thelisted file or folder must not be on a file system thatcontains database data files or log file s.

System action: The file system layout check fails..

User response: Change the database layout so that thelisted folder is not on a data or log file system.

FMM9029E The file system 'mountpoint' containsboth data and redo log files from thesame database instance.

Explanation: FlashCopy Manager does not supportlog and data files on the same file system.

System action: The file system layout check fails.

User response: Change the database layout so that thedata and redo log files are on separate file systems.

FMM9030E The following database File Type filesare on the root file system: List of Files

Explanation: The database redo log files and data filesmust be on a file system other than the root filesystem.


User response: Change the database layout so thatdata files and redo log files are not on the rootfilesystem.

FMM9031E The file system 'volume group' containsboth data files and redo log files.

Explanation: FlashCopy Manager does not supportlog and data files on the same file system.


User response: Change the database layout so that thedata and redo log files are on separate file systems.

FMM9032E The following control files are includedin the file system where the databasedata files are stored: List of Controlfiles

Explanation: The control files must not be on the filesystem where the database data files are stored.


User response: Change the database layout so that thecontrol files are not on a file system for database files.

FMM9033E The following control files are notincluded in a file system for database orredo log files: List of Controlfiles

Explanation: The control files must be on a file systemwhere database redo log files or the data files arestored.


User response: Change the database layout so that thecontrol files are on a file system for data or redo logfiles.



FMM9034I File system layout check(fcm.volume_group_layout): This checkvalidates if the prerequisites of thedatabase file systems layout that arelisted in the Pre-installation ChecklistPDF, are fulfilled.

Explanation: The file system layout must be set up asdescribed in the Pre-installation Checklist PDF.


User response: For more information about thePre-installation Checklist, see http://www.ibm.com/support/docview.wss?uid=swg21427692. Follow thelink to the requirements technote for your specificrelease or update level; the Pre-installation Checklist isavailable there.

FMM9035I The current profile does not specifypreprocessing or postprocessing scripts.For consistent application backups, youmust specify these scripts at thecommand-line when you enter a backupcommand. Alternatively, edit the profilein advanced mode (-advanced option) tospecify the scripts.

Explanation: For consistent backups of yourapplication, IBM Tivoli Storage FlashCopy Managerneeds to quiesce the application before you take thehardware snapshot and resume the applicationafterward. For custom applications, scripts must beprovided to quiesce or resume the application. IBMTivoli Storage FlashCopy Manager starts these scripts atthe appropriate moment. The implementation of thescripts is application-specific.


User response: Depending on the specifics of yourapplication, ensure that you have the rightpreprocessing and postprocessing scripts in place. Forconsistent application backups, ensure to specify thesescripts at the command-line when you issue a backupcommand. Alternatively, specify the scripts in theprofile by editing it in advanced mode (-advancedoption). Specify the scripts with the parametersPRE_FLASH_CMD and POST_FLASH_CMD. Thesettings of these parameters can be overridden with thecommand-line options -E and -Q when you enter abackup command.

FMM9036E The file system File System is not ofexpected type File System Type

Explanation: The mixture of file system types that thedatabase is located on is not supported.

System action: The file system type check fails..

User response: Make sure that the database is locatedon supported file systems.

FMM9037E The following volume group(s) containan unsupported mix of file systemtypes: Volume Groups

Explanation: The mixture of file system types in avolume group is not supported.

System action: The file system type check fails..

User response: Do not mix file system types in onevolume group.

FMM9038E The file system File System in volumegroup Volume Group does not belong tothe database

Explanation: Only file systems that contain databasefiles (such as data files, log files etc.) must be includedin the volume groups the database resides on.


User response: Ensure to not include additional filesystems in the volume groups the database resides on.

FMM9039W As no database environment was foundfor user User, the Application Type is setto Custom Application (CAA). Thevolume group layout(fcm.volume_group_layout) and filesystem type checks (fcm.fileSystemType)cannot be run.

Explanation: When the environment variableDB2INSTANCE for the database user is set, theApplication Type is DB2. When the environmentvariable ORACLE_SID for the database user is set, theApplication Type is Oracle. When the environmentvariable ORACLE_SID for the database user is set andthe binary brbackup is found in the user path, or theenvironment variable SAPDATA_HOME is set, theApplication Type is Oracle_SA

System action: The Application Type defaults toCustom Application (CAA).

User response: Change the user environment to matchyour setup if your Application Type is not CustomApplication (CAA).

FMM9040I Starting check for property 'property'

Explanation: IBM FlashCopy Manager PrerequisiteChecker processing for the named property is starting.The property name refers to a value in the "Property"column of the prerequisite checker's output.





FMM9041I Completing check for property 'property'

Explanation: IBM FlashCopy Manager PrerequisiteChecker processing for the named property is complete.The property name refers to a value in the "Property"column of the prerequisite checker's output.



FMM9042W The volume group layout(fcm.volume_group_layout) and filesystem type checks (fcm.fileSystemType)cannot be run because the database ison Oracle ASM disk groups.

Explanation: The volume group layout and file systemtype checks cannot run on databases that are on OracleASM disk groups.

System action: The fcm.volume_group_layout andfcm.fileSystemType checks are not processed.

User response: Run the fcm.volume_group_layout andfcm.fileSystemType checks manually.

FMM9043W The volume group layout(fcm.volume_group_layout) and filesystem type checks (fcm.fileSystemType)cannot be run because the database is aDB2 PureScale database.

Explanation: TThe volume group layout and filesystem type checks cannot run on DB2(R) PureScaledatabases.



FMM9044W The volume group layout(fcm.volume_group_layout) and filesystem type checks (fcm.fileSystemType)cannot be run because the database is aDB2 DPF (Database PartitioningFeature) database.

Explanation: The volume group layout and file systemtype checks can not be run on DB2(R) DPF (DatabasePartitioning Feature) databases.



FMM9045I The volume group layout support check(fcm.is_vg_layoutcheck_supported)validates if the volume group layout(fcm.volume_group_layout) and filesystem type checks (fcm.fileSystemType)can be run on the database.

Explanation: The volume group layout and file systemtype checks can not be run on DB2(R) DPF (DatabasePartitioning Feature) databases, DB2 PureScaledatabases, and Oracle databases that are on OracleASM disk groups.


User response: In each of these cases, you must runthe fcm.volume_group_layout and fcm.fileSystemTypechecks manually.

FMM9046I The file system type check(fcm.fileSystemType) validates if thefiles to be managed by IBM TivoliStorage FlashCopy Manager are insupported filesystems.

Explanation: Depending on the environment, differentfilesystem types may be supported. For a list ofsupported filesystems, please refer to thePre-installation Checklist PDF.



FMM9198E While processing path path_name, anerror occurred. The following errorinformation was received:detailed_error_information

Explanation: This message indicates that a problemoccurred while processing the following path:path_name. If you are protecting data for DB2applications, this path contains one or more of thedatabase files to be included in the operation. If youare protecting data for Oracle databases or the CustomApplication Agent, this path was provided in the in-filespecified with the flag "-I <infile_name>" in thecommand.


User response: To help resolve the problem thedetailed_error_information is available. After you resolvethe issue, enter the command again.

FMM9199E The following command returned withan error: command The return code fromthis command is return_code Thefollowing command output wasreceived: command_output Additionalsupport information: An exception wasthrown at position: position(line).



Explanation: This message indicates that the commandreturned with the error indicated by return_code. Anyadditional command_output is provided.


User response: To help resolve the problem thecommand_output is available. After you resolve theissue, enter the command again.

FMM9200E Additional support information: Anexception was thrown at position:position(line).

Explanation: This error message typically follows aprevious error. If so this error message can be ignored.Otherwise contact IBM Support.

System action:




System action:




System action:




System action:


FMM9204E Additional support information: Anexception was thrown at position:file(line) (text_description).

Explanation: This error message typically follows aprevious error. If so this error message can be ignored.

Otherwise contact IBM Support.

System action:


FMM9205E Additional support information: Unableto instantiate name at file(line).


System action:


FMM9206E Additional support information: Unableto use actual when expecting expected atfile(line).


System action:


FMM9207E Additional support information: Anexception was thrown at position:file(line).


System action:


FMM9208E System error errno: errno text at position:file(line).

Explanation: A system call failed with errno.

System action:

User response: Check errno and errno text with yousystem administrator. If you cannot resolve theproblem, contact IBM Support.

FMM9209E Additional support information: Nohandler registered for message typemessage. Thrown at position: file(line).


System action:




FMM9210E ESD_AbortDispatchingException thrownat position: file(line).

Explanation: An internal error occurred.

System action:


FMM9211E Additional support information: Anexception was thrown at position:file(line). (State state)


System action:


FMM9212E Additional support information: Nohandler registered for message type(message_type, classname). Thrown atposition: file(line).


System action:


FMM9213E A memory allocation request failed atposition: file(line).

Explanation: This error message indicates anout–of–storage condition. It may occur due to aprevious error, or it may be owed to a large size of theinternal buffers.

System action:

User response: Check for and respond to precedingerror messages. You may also want to reduce the sizeof the internal buffers (keyword BUFFSIZE in the DataProtection for SAP profile).

FMM9214E Additional support information: Anexception was thrown from a destructor.


System action:


FMM9215E The maximum string length supportedfor name is length.

Explanation: The supported string length of a systemcomponent, e.g. file name or hostname has beenviolated.

System action:

User response: Check the components involved in theoperation. If the problem cannot be resolved contactyour IBM support personnel.



System action:




System action:




System action:


FMM9219E Additional support information: Invaliderror type type encountered.


System action:




FMM9220E Additional support information: Secondcall of call.

Explanation: This error message typically follows aprevious error. If so this error message can be ignored.Otherwise contact your IBM Support.

System action:

User response: Contact your IBM Support.

FMM9221E The operation ended prematurely withreturn code rc. An exception was thrownat position: file(line).

Explanation: An operation could not be finishedsuccessfully due to an unexpected termination.

System action:


FMM9222E A snapshot–type operation wasinterrupted, Additional supportinformation: An exception was thrownat position: file(line).

Explanation: A snapshot operation could not befinished successfully due to an unexpected interruption.

System action:


FMM9223E The operation will be aborted.

Explanation: An internal error during an operationleads to an abort of that operation.

System action:


FMM9224E The operation will be aborted. Checkfor other error messages in the log files.

Explanation: An internal error during an operationleads to an abort of that operation.

System action:


FMM9225E The keyword 'keyword' has not beenfound in the line 'line' of the file'file_name'. Please change it back to theoriginal value if you modified it.

Explanation: Occurs for example if the entries in thefile /etc/inittab have been modified before a secondinstallation.

System action:

User response: Change the modified line in thefile_name back to the original value, keyword gives a hintto what is expected.

FMM9226E The ASM instance with SID='instance id'is not available. Please check if theASM_INSTANCE_ID is set to the rightASM instance, if yes start it and checkthe availability.

Explanation: The ASM instance with the specified SIDcould not be accessed.


User response: Check if the ASM instance with thespecified SID is available and started.

FMM9227E The ASM diskgroup 'diskgroup' has notbeen found. Ensure that it is available.

Explanation: The specified diskgroup is needed forthe backup but it has not been found in the ASMinstance.


User response: Please ensure that the diskgroup isavailable in your ASM instance and that it is mounted.

FMM9228E Excpected ASM file but found file: 'file'

Explanation: ASM files were expected, but a non-ASMfile has been found. This might occur if your databaseresides on ASM and non-ASM files.


User response: Please ensure that you do not have amixed environment with ASM and non-ASM files.

FMM9229E Excpected file but found ASM file: 'file'

Explanation: Non-ASM files were expected, but anASM file has been found. This might occur if yourdatabase resides on ASM and non-ASM files.


User response: Please ensure that you do not have amixed environment with ASM and non-ASM files.



FMM9230E The SSL/TLS certificate provided by theserver is missing a valid subject DN orissuer DN field.

Explanation: The subject DN or issuer DN field of thecertificate provided by the server is missing. Both fieldsare mandatory fields to allow a validation of thecertificate.

System action: The task stopped before successfullycompleting.

User response: Import a valid server certificate to thekey ring database 'fcmcert.kdb'.

FMM9231E The SSL/TLS certificate provided by theserver is not proving its supposedidentity.

Explanation: The SSL/TLS certificate provided by theserver is not issued for the server that was supposed toconnect. The alternative name or subject CN field of thecertificate does not match the hostname or IP addressof the server that was actually connected.


User response: Revalidate the correctness of thecertificate that has been imported to the key ringdatabase 'fcmcert.kdb'. Its alternative name or subjectCN field needs to match the hostname or IP address asstated in the IBM Tivoli Storage FlashCopy Managerprofile (GLOBAL section, parameter ACSD).

FMM9300E Additional support information:Aborting 'send' operation. See previouserror.

Explanation: This error may have been caused byprevious errors.

System action:

User response: Check for previous errors and correctthem.

FMM9301E Additional support information: Statestate does not match state pattern pattern.


System action:


FMM9302E Additional support information: Aprocess ended unexpectedly. Checkprevious error messages.

Explanation: This error message typically follows aprevious error. If so this error message can be ignored.

Otherwise contact your IBM Support.

System action: Processing ends


FMM9306I Dumping callstack.

Explanation: This message is always preceded by anerror message indicating the problem. It providesadditional information that might help IBM Support toanalyze the cause of the problem.

System action:

User response: If you need to call IBM Support,provide the information given in this message togetherwith the error information.

FMM9307E Did not find a winsock dll compatiblewith version major_winsock_version.minor_winsock_version. Version found islow_byte_availableversion.high_byte_available_version.

Explanation: The product failed to load theappropriate winsock dll.

System action:


FMM9308E A socket request timed out afterprocessing number of bytes bytes. file(line).

Explanation: A socket request was issued with atimeout and the requested action could not becompleted within the time specified. It was cancelledafter processing number of bytes bytes.

System action:

User response: If you need to call IBM Support,provide the information given in this message togetherwith the error information.

FMM9309E Operation terminated due to an explicitabort request.

Explanation: An operation was terminated due tocustomer intervention.

System action:


FMM9310E Could not add backup_id to therepository at path.

Explanation: The system was not able to addinformation on the named backup to the repositorylocated in the path indicated.

System action:

User response: Make sure the repository path is set



correctly. If you need to correct the repository location,restart the server executable afterwards. If the problempersists contact your IBM support personnel.

FMM9311E Could not find backup_id in therepository at path.

Explanation: Information on the backup denoted bythe backup ID could not be found in the repositorylocated in the path indicated.

System action:

User response: Make sure the repository path is setcorrectly. If you need to correct the repository location,restart the server executable afterwards. If the problempersists contact your IBM support personnel.

FMM9312E backup_id is currently locked in therepository at repository.

Explanation: The information on the backup denotedby the backup ID is currently locked by a differentprocess. Make sure to run only a single operation usinga specific backup at a time.

System action:

User response: Wait for the other operation to finishor abort this operation. Then start again. If the problempersists contact your IBM support personnel.

FMM9313E Failed to update backup_id in therepository at path.

Explanation: The information on the named backupcould not be updated in the repository located at thepath named.

System action:

User response: Check the logs for other messagespointing to the cause of this problem. Resolve anyproblems indicated. If the problem persists contact yourIBM support personnel.

FMM9314E Could not remove backup_id from therepository at path.

Explanation: An attempt to remove the informationon the backup named from the repository located at thepath indicated failed.

System action:

User response: Check the logs for other messagespointing to the cause of this problem. Resolve anyproblems indicated. If the problem persists contact yourIBM support personnel.

FMM9315E Could not access the repository at 'path'because it is currently locked by anotherprocess.

Explanation: When starting up, the server tried toload the repository located at the path named.However, the repository was locked by a differentprocess. This can happen if two server processes try touse the same repository. This is not supported.

System action:

User response: Make sure each instance of the serveruses its own repository.

FMM9316E The name 'name' refers to an existing fileor directory, but it does not appear to bea valid repository. In order to continueyou need to specify either a non existingdirectory or the path of an existing validrepository.

Explanation: The server could not locate its repositorywhen it started.

System action:


FMM9317E The specified backup id 'backup_id' musthave char_count characters. If thespecified amount of characters exists,make sure there are no specialcharacters.

Explanation: The length of the specified backup id isincorrect.

System action:

User response: Correct the length of the backup id tomatch the specified length.

FMM9318E The file 'filename' has not been found. Itis required for the device agent tofunction. Check your installation.

Explanation: The specified file has not been foundeven though it was included in the installation.

System action:

User response: Check that the specified file isavailable in the specified location. Consider installingthe product again in order to make the file available.

FMM9319E Operation is terminated.

Explanation: The current operation is stopped. Seeother errors in the log file.


User response: Check for other errors in the log file. If



no other errors are found, contact your product supportteam.

FMM9320W Warning: Backup of previous profileversion failed (file access error).

Explanation: Before writing a new version of theprofile, the previous version is renamed into<profilename>.bck. Due to an error renaming failed sothat the original profile is just overwritten by the newrevision. As a consequence, no backup of the previousversion is available.


User response: Ensure the backup variants of yourprofile (extensions .bck and .bck2) are writable.

FMM9327I Note: No FCM server certificate foundin key database and no self-signedcertificate file${GSKIT_SELFSIGNED_CERT_FILENAME}found to be imported. If not using CAsigned certificates, import self-signedcertificate from Production System (PS).For details, refer to the User's Guide.

Explanation: Except when using CA signed certificatesthe public part of the self-signed server certificate needsto be imported to the key database of the IBM TivoliStorage FlashCopy Manager installation on backup andcloning system nodes (BS/CS).

System action: If a CA signed certificate is installed tothe key database on production system (PS), themessage can be ignored; IBM Tivoli Storage FlashCopyManager correctly operates. If no CA signed certificateis installed on PS, IBM Tivoli Storage FlashCopyManager fails to operate until the self-signed servercertificate has been deployed to the backup and cloningsystem nodes.

User response: Copy the self-signed server certificatefile 'fcmselfcert.arm' from the IBM Tivoli StorageFlashCopy Manager instance installation path onproduction system (PS) to the IBM Tivoli StorageFlashCopy Manager installation path on your backupor cloning system. Rerun the setup script toautomatically import the file to the key database.

FMM9328E An error occurred in the securecommunication layer when running thefollowing function: function. GSKitreturn code: numeric return code. GSKiterror: return value.

Explanation: Information about the error is providedin the return value.


User response: Resolve the problem identified in thereturn value. Try the operation again.

FMM9329E An error occurred when the softwaretried to link the SSL Implementation toGSKit. GSKitWrapper error: 'linker error'

Explanation: Information about the error is providedin linker error.


User response: Resolve the problem identified in thelinker error. Try the operation again.

FMM9330E Error: Invalid Server name. The servername must be longer than min butcannot exceed max characters. Thecurrent length is len.

Explanation: The server name specified in the profileis not valid.


User response: Correct the servername specified inyour profile.

FMM9331E Error: Invalid User name. The user namemust be longer than min but cannotexceed max characters. The currentlength is len.

Explanation: The user name specified in the profile isnot valid.

System action: Processing will end.

User response: Correct the user name specified inyour profile.

FMM9332E Error: Invalid User password. Run'fcmcli -f password' to create thepassword. The password must be longerthan min but cannot exceed maxcharacters. The current length is len.

Explanation: The specified password is not valid.


User response: Run 'fcmcli -f password' to set thecorrect password.

FMM9333E Error: Invalid Secondary Server name.The server name cannot exceed a lengthof max characters. The current length islen.

Explanation: The Secondary Server name specified isnot valid.


User response: Correct the Secondary Server namespecified in your profile.



FMM9334E Error: Invalid Server installationdirectory. The path to install directorycannot exceed a length of maxcharacters. The current length is len.

Explanation: The Server install directory is invalid.


User response: Correct the Server install directory.

FMM9335E Error: Invalid Java home directory. Thepath to the Java Home directory cannotexceed a length of max characters. Thecurrent length is len.

Explanation: The Java™ Home directory is invalid.


User response: Correct the Java Home directory.

FMM9336E Error: Invalid Port number. The portnumber cannot be higher than max. Thecurrent port is port.

Explanation: The specified port is invalid.


User response: Correct the port number in yourprofile.

FMM9337W The given port number port is already inuse by another process.

Explanation: The specified port is currently occupiedby another process. The port might be still occupiedduring later operation which will cause the product isnot able to operate properly.

System action:

User response: Change port number in your profile.

FMM9339E The specified device class name isalready in use by section section.

Explanation: The specified device class is alreadyreferenced by a section of another type. A given deviceclass may be used exclusively either by a CLIENT or aCLONING section

System action:

User response: Choose another device class namewhich is not in use by another section type.

FMM9340E The FlashCopy Cloning operation failedbecause the FlashCopy mappings usedfor Cloning are dependent on olderFlashCopy mappings from olderFlashCopy Backup or Cloningoperations. You can either wait until theolder FlashCopy mappings are in stateidle_or_copy or you can start theCloning operation with the force option[-F] which will force the olderFlashCopy mappings to be stopped. Inthe latter case you will loose your olderFlashCopy Backups or Clones.

Explanation: When you perform FlashCopy Backupand Cloning operations of the same productiondatabase to multiple FlashCopy target sets then youcan have situations where you cannot always reuse theoldest target set for a new operation. For example youhave started a FlashCopy Backup on space efficienttarget set T1 on Monday and you started a FlashCopyCloning on a full target set T2 on Tuesday. Now youneed to restart the FlashCopy Cloning in the sametarget set T2. This will result in the above errorsituation where you would destroy the FlashCopyBackup from Monday. FlashCopy Manager hasimplemented this error handling so that you cannotdestroy FlashCopy Backups by accident. If you need torestart the FlashCopy Cloning operation urgently andyou accept to loose FlashCopy Backups, then you canstart the FlashCopy Cloning operation with the forceoption [-F] which will destroy the FlashCopy Backupsand allows the FlashCopy Cloning operation to runsuccessfully.

System action:

User response: You can either wait until the olderFlashCopy mappings are in state idle_or_copy or youcan start the Cloning operation with the force flag [-F]which will force the older FlashCopy mappings to bestopped. In the latter case you will loose your olderFlashCopy Backups or Clones.

FMM9341E The name of the clone database ismissing.

Explanation: The device class that is associated withthe clone database requires at least one database nameto be specified.

System action:

User response: Specify one (or more) database names.If more than one database name is specified, separateeach name with a space.

FMM9342E Unmounting of file system 'filesystem' atbackup system does not work.;

Explanation: The GPFS command mmumount -forcewas not able to unmount the file system.




User response: Check what prevents the unmount ofthe remote GPFS file system. Solve this issue and call

the IBM Tivoli Storage FlashCopy Manager unmountcommand again.

FMM messages for Microsoft Management ConsoleFMM messages in the range 50000-50099 are issued by IBM Tivoli StorageFlashCopy Manager for Windows. The messages in this range are related to theMicrosoft Management Console (MMC).

Tivoli Storage FlashCopy Manager V4.1.2 messages that are related to the MicrosoftManagement Console are listed in ascending numerical order. The completemessage is documented, including message ID, message text, explanation, systemaction, and user response.

FMM50001E The product license could not beopened.

Explanation: At least one license is required. If this isa PTF package ensure that it is being installed over anexisting package.


User response: Install the product again by runningSetupFCM. SetupFCM is located in the root of your GAmedia. SetupFCM stores the media location in theregistry when it is run. This will help to ensure that thecorrect licenses can be found.

FMM50002E The product registry key could not beopened.

Explanation: The product registry key is missing.


User response: Reinstall the product to create therequired registry keys.

FMM50003E Unable to connect to the TSM server.

Explanation: Communication with a TSM server couldnot be established using the specified settings.

System action: Does not connect to the TSM server.

User response: Update TSM server settings as needed.Review the TSM BA client dsmerror.log file for details.

FMM50004E Unable To Obtain RSS Feed

Explanation: An attempt to read an RSS feed wasmade but could not be established.


User response: Ensure that there is an internetconnection

FMM50005E No RSS items were available.

Explanation: An RSS feed was read but no items wereavailable.


User response: Try the operation again at a later time.

FMM50006E Email must configured before mail canbe sent.

Explanation: One or more email settings is notconfigured.


User response: Click Settings... to configure email.

FMM50007I Windows PowerShell is not installed.

Explanation: Windows PowerShell is required to runthe selected script.

System action: The selected script will not be run.

User response: Install Windows PowerShell.PowerShell is included with Windows Server 2008 andabove but must be enabled as a feature using WindowsServer Manager. For earlier versions of Windows,PowerShell can be obtained from the Microsoftdownload site.

FMM50008E The application cannot run in safemode.

Explanation: The application requires either Servicesor Drivers that are not available when running in safemode.

System action: The application processing stops.

User response: Restart the system using the normalstartup. When the system is started, run theapplication.

FMM50009E Windows PowerShell 3.0 or above, aprerequisite for Tivoli StorageFlashCopy Manager, is not installed.Install the prerequisite software beforerunning Tivoli Storage FlashCopyManager.

FMM50001E • FMM50009E


Explanation: Microsoft Windows PowerShell 3.0 orabove is a prerequisite for Tivoli Storage FlashCopyManager. This prerequisite is not met so the TivoliStorage FlashCopy Manager software is not going torun.

System action: Install the prerequisite software beforeinstalling and running Tivoli Storage FlashCopyManager.

User response: Microsoft Windows PowerShell isavailable for download from the Microsoft Windowsweb site.

FMM50010E

Explanation: Can not connect to the computer. {0}

System action: Application processing continues.

User response: Ensure that the computer name andcredentials are specified correctly and try again.

FMM50011E {0} will not start with invalidparameters.

Explanation: {0} was started with a bad parameter inthe command line. Bad argument -> {1}

System action: Start {0} with valid parameters.

User response: Ensure the command line parametersare correct and try again.

FMM50012E {0} will not start with invalidparameters.

Explanation: {0} was started with a parameter in thecommand line that specifies a file that does not exist.File -> {1}

System action: Start {0} with valid parameters.

User response: Ensure the command line parametersare correct and try again.

FMM50013E

Explanation: When starting the software, a parameterin the command line specified a SQL Server instancethat does not exist. The SQL Server instances that arenot found are: '{0}'. The available SQL Server instancesare: '{1}'

System action: Start {0} by referencing an availableSQL Server instance.

User response: Review the command line parametersto ensure there are no typographical errors. You canalso test the connection the SQL Server instance that isbeing called, but is not found.

FMM messages for IBM XIV Storage Systems and Rocket DeviceAdapter Pack storage systems

FMM messages in the range 18000-18199 are issued by IBM Tivoli StorageFlashCopy Manager for the following storage systems:v IBM XIV Storage Systemv Rocket Device Adapter Pack storage systems

Tivoli Storage FlashCopy Manager V4.1.2 messages are listed in ascendingnumerical order. The complete message is documented, including message ID,message text, explanation, system action, and operator response.

FMM18000E FcmParserException thrown.

Explanation: The generic command parser of thestorage device adapter failed because an exceptionoccurred. This error message is preceded by anothererror message that specifies the root cause of the issuein more detail.

Operator response: The occurrence of this errormessage indicates that an internal error occurred. Thiserror might be caused by an installation of TivoliStorage FlashCopy Manager that installed with errorsor a recent product update that was interrupted duringthe installation. Reinstall the product to ensure that allof its components are at the same version level.

FMM18003E FcmParserException thrown, see trace_filefor details.

Explanation: The generic command parser of thestorage device adapter failed because an exceptionoccurred. This error message is preceded by anothererror message that specifies the root cause of the issuein more detail. For more information, see the specifiedtrace file for detailed information about the conditionsthat caused this problem.

Operator response: The occurrence of this errormessage indicates that an internal error occurred. Thiserror might be caused by an installation of TivoliStorage FlashCopy Manager that installed with errorsor a recent product update that was interrupted duringthe installation. Reinstall the product to ensure that all

FMM50010E • FMM18003E


of its components are at the same version level.

FMM18005E No value is specified for the mandatoryparameter_key parameter.

Explanation: The generic command parser of thestorage device adapter fails because no value isprovided for the parameter with the specified key. Thiserror is probably caused by a configuration problem.

Operator response: Rerun the setup routines and theTivoli Storage FlashCopy Manager profile configurationwizard to ensure that the profile is consistent andcomplete. Also, verify that the configuration of yourtarget set files is correct if applicable.

FMM18006W The logfilename log file cannot becreated.

Explanation: The log file cannot be created at thespecified location because the path does not exist orwrite permissions are not assigned to the directory.

Operator response: The log file is created in the logssubfolder in the ACS_DIR directory as specified in theprofile configuration file. Ensure that this folder existsand that the correct access rights are assigned to thedirectory. Reconfigure the ACS_DIR parameter in theGLOBAL section of the profile if appropriate.

FMM18007W The message_received message isreceived but the message_expectedmessage is expected.

Explanation: The generic command parser of thestorage device adapter received a message that itcannot handle in its current state. This message isignored.

Operator response: No action is required.

FMM18008E The key parameter is not present in theprofile.

Explanation: The specified parameter is missing in theprofile configuration or no value is assigned to thisparameter.

Operator response: Rerun the setup routines and theTivoli Storage FlashCopy Manager profile configurationwizard to ensure that the profile is consistent andcomplete.

FMM18009E FcmStorageDeviceException thrown.

Explanation: The generic storage device adapter layerreceived an exception from the storage adapterimplementation. This error message is preceded byother error messages that specify the root cause of theissue in more detail.

Operator response: This error is specific to the deviceadapter implementation or the storage device it

interacts with. Review the preceding error message toidentify the root cause as the source can result fromvarious areas.

FMM18010E FcmProfileException thrown.

Explanation: The generic command parser of thestorage device adapter failed because an exceptionoccurred. This error message is preceded by anothererror message that specifies the root cause of the issuein more detail.

Operator response: Rerun the setup routines and theTivoli Storage Manager profile configuration wizard toensure that the profile is consistent and complete.

FMM18011E Unable to read from the standard input(STDIN).

Explanation: The generic command parser of thestorage device adapter failed after receiving messagesfrom Tivoli Storage FlashCopy Manager.


FMM18012E The key key is not allowed after messagemessage.

Explanation: The generic command parser of thestorage device adapter did not receive the message asexpected according to its internal state machine.


FMM18013E FcmStorageDeviceException thrown, seetrace_file for details.

Explanation: The generic storage device adapter layerreceived an exception from the storage adapterimplementation. This error message is preceded byother error messages that specify the root cause of theissue in more detail. The specified trace file providesmore detailed information about the conditions thatlead to this issue.

User response: This error is specific to the deviceadapter implementation or the storage device itinteracts with. Review the preceding error message andthe specified trace file to identify the root cause as thesource can result from various areas.

FMM18005E • FMM18013E


FMM18014E FcmProfileException thrown, seeTraceFile for details.

Explanation: The generic command parser of thestorage device adapter failed because an exceptionoccurred. This error message is preceded by anothererror message that specifies the root cause of the issuein more detail. For more information, see the specifiedtrace file for detailed information about the conditionsthat caused this issue.

Operator response: Rerun the setup routines and theTivoli Storage FlashCopy Manager profile configurationwizard to ensure that the profile is consistent andcomplete.

FMM18016W The logdir log directory cannot becreated.

Explanation: The log file directory cannot be createdat the specified location. This issue can arise becausewrite permissions are not assigned to the directory.

Operator response: The log file directory is created asa subfolder in the ACS_DIR directory as specified inthe profile configuration file. Ensure that this directoryexists and that the correct access rights are assigned tothe directory. Reconfigure the ACS_DIR parameter inthe GLOBAL section of the profile if appropriate.

FMM18017E The Message message received, ends thecurrent operation.

Explanation: This error message indicates that thestorage device adapter was instructed by Tivoli StorageFlashCopy Manager to end the current operation.

Operator response: This message is resulting from aninternal control flow mechanism. This flow is triggeredby an aborted operation at a higher level that istriggered by a user or an error condition. No action isrequired.

FMM18018E The message message is not allowed inthis context.

Explanation: The generic command parser of thestorage device adapter received an unexpected messagethat is not allowed in this context and therefore cannotbe handled.


FMM18020E No additional messages are allowedafter the #END tag. The message messagemight belong to the next section.

Explanation: The generic command parser of thestorage device adapter received an unexpected messagethat is not allowed in this context and therefore cannotbe handled. The occurrence of this error messageindicates an internal error.


FMM18021E When starting the function function, thelist of snapshot items that are receivedfrom Tivoli Storage FlashCopy ManagerOS agent is empty.

Explanation: The snapshot item list is empty.

Operator response: Issue the inquire function to verifythat this backup is valid for the named operation.

FMM18022E No response received from the storagedevice adapter.

Explanation: The response data that is expected fromthe requested call to the storage device adapter is notpresent.

Operator response: Verify the installation andconfiguration of the specific storage device adapter.

FMM18023W When invoking the function function,the list of snapshots that was receivedfrom Tivoli Storage FlashCopy ManagerOS agent is empty.

Explanation: A request for the specified function wasreceived. However, the list of snapshots is empty.

Operator response: This message is a warningmessage and depending on the context no action mightbe required.

FMM18024E The storage adapter implementation didnot provide a complete set ofcapabilities. The missing keys are:missing_keys

Explanation: Each storage device adapterimplementation is expected to provide informationabout its specific capabilities. Tivoli Storage FlashCopyManager must have a fixed set of capabilities that arerequired for handling the storage device according toits specific characteristics. Some or all of thesecapabilities are not provided by the storage adapterimplementation.

FMM18014E • FMM18024E


Operator response: Verify the installation andconfiguration of the specific storage device adapter.Ensure that it is compatible with the version of TivoliStorage FlashCopy Manager that you are using.

FMM18025E The storage adapter implementation didnot provide the expected monitoringinformation for the snapshot_namesnapshot.

Explanation: Some storage device types performbackground copy operations that must be monitored byTivoli Storage FlashCopy Manager. During monitoring,the storage device adapter is periodically polled toprovide an update on the status of the copy operation.This monitoring information was not provided by thestorage adapter implementation as expected.

Operator response: Verify the installation andconfiguration of the specific storage device adapter.Ensure that it is compatible with the version of TivoliStorage FlashCopy Manager that you are using.

FMM18026E The parsed value [value] has an invalidformat that cannot be parsed.

Explanation: The specified value has an unknownformat that cannot be handled by the parser of thegeneric storage adapter layer.

Operator response: The occurrence of this errormessage indicates an internal error. This problem mightbe caused by an installation of Tivoli StorageFlashCopy Manager that installed with errors or arecent product update that was interrupted during theinstallation. Reinstall the product to ensure that all ofits components are at the same version level.

FMM18027E The [target_volume] target volume isspecified multiple times.

Explanation: For the specification of target volumes,each target volume can be specified only once. Theprovided target set contains duplicated target volumes.

Operator response: Review your target set definitionfile and ensure that each target volume occurs onlyonce.

FMM18028E The [source_volume] source volume isspecified multiple times.

Explanation: For explicitly mapping source volumesto target volumes, each source volume can be specifiedonly once. The provided target set contains duplicatedsource volumes.

Operator response: Review your target set definitionfile and ensure that each specified source volumeoccurs only once.

FMM18029E The global unique identifier that isprovided by Tivoli Storage FlashCopyManager must contain a value.

Explanation: When Tivoli Storage FlashCopy Managerrequests a new backup, the device agent API expects aglobal unique identifier to be passed as a parameter.This identifier is not present.

Operator response: The occurrence of this errormessage indicates an internal error. This error might becaused by an installation of Tivoli Storage FlashCopyManager that installed with errors or a recent productupdate that was interrupted during the installation.Reinstall the product to ensure all that all of itscomponents are at the same version level.

FMM18030E The backup ID provided by TivoliStorage FlashCopy Manager mustcontain a value.

Explanation: When Tivoli Storage FlashCopy Managerrequests a new backup, the generic device adapterlayer expects a backup identifier to be passed as aparameter. This identifier is not present.

Operator response: The occurrence of this errormessage indicates an internal error. This problem mightbe caused by an installation of Tivoli StorageFlashCopy Manager that installed with errors or arecent product update that was interrupted during theinstallation. Reinstall the product to ensure that all ofits components are at the same version level.

FMM18031E The mandatory attribute [attribute] ismissing.

Explanation: The generic command parser of thestorage device adapter received a data structure whichis missing the specified attribute. The attribute ismandatory for successfully processing the currentrequest or response to a request.


FMM18032E The adapter implementation did notprovide a result for the delete request ofsnapshot [snapshot].

Explanation: The adapter implementation is expectedto provide an indication how it processed the snapshotsthat were requested to be deleted. The adapterimplementation did not provide a result for thespecified snapshot.

Operator response: The occurrence of this errormessage indicates that an internal error occurred. This

FMM18025E • FMM18032E


error might be caused by an installation of TivoliStorage FlashCopy Manager that installed with errorsor a recent product update that was interrupted duringthe installation. Reinstall the product to ensure that allof its components are at the same version level.

FMM18033E The storage device adapter did notaccept the provided target set.

Explanation: The storage device adapter mustexplicitly accept the target set that is provided by TivoliStorage FlashCopy Manager. Target set definitionsmight not be supported or do not apply to this kind ofstorage device adapter.

Operator response: Verify the installation andconfiguration of the storage device adapter. Ensure thatthe adapter supports the target set definitions and iscompatible with the version of Tivoli StorageFlashCopy Manager that you are using. If the storagedevice adapter does not support target sets, verify thatno target set is specified in the Tivoli StorageFlashCopy Manager profile.

FMM18034E The storage device adapterimplementation requires a newerversion of the device agent API(expectedVersion > actualVersion).

Explanation: The storage adapter implementation wasdeveloped with a newer version of the device agentAPI than the one that is installed. Since thiscombination is potentially incompatible, processingcannot continue.

Operator response: The storage adapter was deployedto an old version of Tivoli Storage FlashCopy Manager.Exchange the storage adapter with an older versionthat is compatible with your Tivoli Storage FlashCopyManager version or upgrade to the latest version ofTivoli Storage FlashCopy Manager.

FMM18035E The storage device adapterimplementation expects an invalidversion of the device agent API: version.

Explanation: The storage adapter implementationexpects a version of the device agent API that is notvalid or no version information is provided.

Operator response: This error indicates an issue withthe storage adapter. Contact the storage adaptervendor.

FMM18036E The device agent API version is notvalid: version.

Explanation: The device agent API reports a versionthat is not valid or is unknown.

Operator response: This error message indicates thatan error occurred. This error might be caused by aninstallation of Tivoli Storage FlashCopy Manager that

installed with errors or a recent product update thatwas interrupted during the installation. Reinstall theproduct to ensure that all of its components areinstalled properly.

FMM18033E • FMM18036E


Chapter 3. FMF messages

Messages with prefix FMF are issued by the IBM Tivoli Storage FlashCopyManager for Windows Microsoft Management Console (MMC) Snap-in and BaseSystem Services component. Tivoli Storage FlashCopy Manager V4.1.2 FMFmessages are listed in ascending numerical order. The complete message isdocumented, including message ID, message text, explanation, system action, anduser response.

FMF0003S An internal processing error hasoccurred.

Explanation: An internal processing error hasoccurred.


User response: Retry the operation. If this errorpersists, contact your service representative.

FMF0004E An unknown error has been detected.

Explanation: An internal processing error hasoccurred that prevents the generation of a message fora return code.



FMF0005E Out of memory. Stop other processesand try the operation again.

Explanation: The machine has run out of memory.


User response: Close unnecessary processes and trythe operation again.

FMF0053E License file (licensefile) could not beopened.

Explanation: An attempt to read from the license filefailed.


User response: Install the product again. This ensuresthat the correct license file is installed.

FMF0054E Read failure on license file (licensefile).

Explanation: An attempt was made to read from thelicense file. This attempt failed.


User response: Reinstall the product. This will ensurethat the correct license file is installed.

FMF0055E Write failure on license file (licensefile).

Explanation: An attempt to write to the license filefailed.


User response: Make sure enough space exists on theworkstation to write to the license file. If enough spaceexists, run the command again.

FMF0056E Data in the license file (licensefile) is notin a valid format.

Explanation: An attempt to read information from thelicense file failed.



FMF0057E The checksum in the license file(licensefile) does not match the licensestring text.

Explanation: An attempt was made to readinformation from the license file. The checksum wasnot valid so it appears that the license file is not at thecorrect level.


User response: Reinstall the product.

FMF0058E The 'Try and Buy' license has expired.

Explanation: This 'Try and Buy' license that wasdetected has expired.


User response: This product is no longer valid for use.A valid license must be obtained before running theproduct.

FMF0100E Incomplete command:

Explanation: This message displays the incompletecommand that was entered.



User response: Re-enter the complete command.

FMF0101E Invalid argument:

Explanation: This message displays the command thatwas entered, up to and including the invalid commandor option argument that was detected.


User response: Re-enter the command specifying avalid argument for the command or option.

FMF0102E Invalid command:

Explanation: This message displays the invalidcommand that was entered.


User response: Re-enter a valid command.

FMF0103E Invalid option for the specifiedcommand:

Explanation: This message displays the command thatwas entered, up to and including the option that wasdetected as invalid for the command.


User response: Re-enter the command specifying validcommand options.

FMF0104E Invalid option:

Explanation: This message displays the command thatwas entered, up to and including the invalid optionthat was detected.



FMF0105E Missing argument:

Explanation: This message displays the command thatwas entered, up to and including the command oroption whose required argument is missing.



FMF0132W Tracing could not be started. Processingwill continue.

Explanation: A problem prevented tracing frombeginning.

System action: Processing will continue with thecommand entered.

User response: Refer to the other messages that

display with this message to determine the problem.

FMF0133W Could not locate installation directory.Attempting to continue...

Explanation: An attempt was made to read theregistry to determine where the Tivoli Data Protectionapplication client was installed. This attempt failed.


User response: There should be other messages alongwith this one. Refer to the other messages to determinethe problem. If the problem can not be determined, itmay be necessary to reinstall the application clientcode. This will ensure that the registry entries are setup correctly.

FMF0134W Could not locate log directory.Processing will continue...

Explanation: An attempt was made to read theregistry to determine where the Tivoli Data Protectionapplication client log is located. This attempt failed.



FMF0150I Operation canceled by user.

Explanation: The user has requested that the IBMTivoli Storage Manager application client end byentering ctrl-C.


User response: None

FMF0151E Errors occurred while processing therequest.

Explanation: Attempting to process the requestentered, an error occurred.


User response: Attempt to determine the source of theerrors from viewing the log file. Correct the problemsand try running the command again.

FMF0152I Performance stats: seconds seconds spentin apicall API calls

Explanation: The indicated number of seconds werespent making API calls for the indicated system.


FMF0101E • FMF0152I


User response: None

FMF0153I Performance stats: seconds seconds spentin function

Explanation: The indicated number of seconds werespent the named function.


User response: None

FMF0154E The IBM Tivoli Storage Managerapplication client cannot work with theversion of the FlashCopy Manager APIyou have installed. Please install versionversion.release.level or greater.

Explanation: The version of the FlashCopy ManagerAPI currently installed on the system is older than theversion used to build the IBM Tivoli Storage Managerapplication client.


User response: Install a version of the FlashCopyManager API at or later than the indicated level. Acopy is distributed with the IBM Tivoli StorageManager application client.

FMF0155E The IBM Tivoli Storage Managerapplication client cannot work with therelease of FlashCopy Manager API youhave installed. Please install releaseversion.release.l evel or greater.

Explanation: The release of the FlashCopy ManagerAPI currently installed on the system is older than therelease used to build the IBM Tivoli Storage Managerapplication client.


User response: Install a release of the FlashCopyManager API at or later than the indicated level. Acopy is distributed with the IBM Tivoli StorageManager application client.

FMF0156E Could not load the FlashCopy ManagerAPI.

Explanation: The FlashCopy Manager API could notbe loaded.


User response: Ensure the FlashCopy Manager API iscorrectly installed. Run the IBM Tivoli Storage Managerapplication client with the /TRACEFLAGS=API/TRACEFILE=filename options and view the tracefileto determine why it could not be loaded. Anotherpossible cause is that the TSMAPI.DLL does not exist inthe system directory. Re-install the FlashCopy ManagerAPI, if this is the case.

FMF0160E An authentication error occurred withyour stored FlashCopy Managerpassword.

Explanation: You were unable to log on to theFlashCopy Manager server due an authentication error.


User response: The stored FlashCopy Managerpassword may have become corrupted. Contact yourFlashCopy Manager server administrator.

FMF0161E Authentication error. The passwordentered is not valid. You are not loggedon to the FlashCopy Manager server.

Explanation: An incorrect password was entered.


User response: Enter the correct FlashCopy Managerpassword and try again.

FMF0162E The passwords entered do not match.Please enter them again.



User response: Enter the passwords again.

FMF0163E The directory path needs to befully-qualified.

Explanation: The /intopath option was specifiedwithout a fully-qualified path.


User response: Enter the command again and specifya fully-qualified path in the /intopath option.

FMF0167E The fully-qualified file name is toolong.

Explanation: An attempt was made to use afully-qualified file name that was too long. Thisattempt failed.


User response: None

FMF0200E File (filename) could not be opened forreading.

Explanation: An attempt was made to open a file forreading. This attempt failed.


User response: None

FMF0153I • FMF0200E

Chapter 3. FMF messages 191

FMF0201E File (filename) could not be opened forwriting.

Explanation: An attempt was made to open a file forwriting. This attempt failed.


User response: None

FMF0202E Read failure on file (filename).

Explanation: An attempt was made to read from afile. This attempt failed.


User response: None

FMF0203E Write failure on file (filename).

Explanation: An attempt was made to write to a file.This attempt failed.


User response: None

FMF0204E File (filename) could not be closed.

Explanation: An attempt was made to close a file.This attempt failed.


User response: None

FMF0205E File (filename) statistics could not beobtained.

Explanation: An attempt was made to obtain filestatistics. This attempt failed.


User response: None

FMF0206E Directory (directory) could not be created.

Explanation: An attempt was made to create adirectory. This attempt failed.


User response: None

FMF0207E Directory path (directorypath) is too long.

Explanation: An attempt was made to use a directorypath that was too long. This attempt failed.


User response: None

FMF0208E There is not enough disk space for theoperation attempted.

Explanation: An attempted operation required moredisk space than was available. The attempt failed.


User response: None

FMF0209E The rename of file (filename1) to(filename2) failed.

Explanation: An attempt was made to rename a file.This attempt failed.


User response: None

FMF0210E The FlashCopy Manager high levelqualifier is too long.

Explanation: An attempt was made to use aFlashCopy Manager high level qualifier that was toolong. This attempt failed.


User response: None

FMF0211E The FlashCopy Manager low levelqualifier is too long.

Explanation: An attempt was made to use aFlashCopy Manager low level qualifier that was toolong. This attempt failed.


User response: None

FMF0212E The FlashCopy Manager filespace nameis too long.

Explanation: An attempt was made to use aFlashCopy Manager filespace name that was too long.This attempt failed.


User response: None

FMF0213E The maximum number of objectsallowed per FlashCopy Managertransaction is too small.

Explanation: In order to maintain backup dataintegrity, multiple backup objects are sent to theFlashCopy Manager server in a single transaction. TheFlashCopy Manager server has indicated that themaximum number of objects allowed per transaction isless than the minimum required by the IBM TivoliStorage Manager application client.


FMF0201E • FMF0213E


User response: Increase the maximum number ofobjects allowed per transaction on the FlashCopyManager server and retry the operation.

FMF0214E The backup object's management classbackup copy group does not exist.

Explanation: The FlashCopy Manager server hasindicated that the backup object's management classbackup copy group does not exist.


User response: Contact your FlashCopy Managerserver administrator.

FMF0215E All backup objects do not have the samemanagement class backup copydestination.

Explanation: In order to maintain backup dataintegrity, multiple backup objects are sent to theFlashCopy Manager server within a single transaction.All backup objects within a single transaction arerequired to have the same management class backupcopy destinations.


User response: Contact your FlashCopy Managerserver administrator.

FMF0216E Unable to obtain space information forvolume (volumename).

Explanation: An attempt was made to obtain spaceinformation for a volume. This attempt failed.


User response: None

FMF0217E The FlashCopy Manager filespace nameis invalid.

Explanation: The filespace name or directorydelimeter is invalid.


User response: Check that the filespace name length,characters, and directory delimeters are valid.

FMF0218E The FlashCopy Manager high levelqualifier is invalid.

Explanation: The high level qualifier name ordirectory delimeter is invalid.


User response: Check that the high level qualifiername length, characters, and directory delimeters arevalid.

FMF0219E The FlashCopy Manager low levelqualifier is invalid.

Explanation: The low level qualifier name or directorydelimeter is invalid.


User response: Check that the low level qualifiername length, characters, and directory delimeters arevalid.

FMF0256E The password in your FlashCopyManager options file has expired. Pleasechange your password on the FlashCopyManager server using the 'changepassword' command and then eitherchange or remove the password value inyour options file.

Explanation: Your FlashCopy Manager password hasexpired. You need to change your password.


User response: Obtain a new password for yourFlashCopy Manager server; node using the changepassword command or by asking your FlashCopyManager Administrator to change your password.

FMF0257E Your password has expired.

Explanation: Your FlashCopy Manager password hasexpired. A new password needs to be obtained.


User response: Obtain a new password for yourFlashCopy Manager node using the change passwordcommand or by asking your FlashCopy ManagerAdministrator to change your password.

FMF0258E You did not enter a valid password.Processing ends.

Explanation: The password that was entered was nota valid password.


User response: Re-enter the command specifying avalid password.

FMF0259E The password you entered forverification does not match thepassword you entered for your newpassword. Your password will not bechanged.

Explanation: The password you entered forverification of your new password does not match thenew password that was entered.




User response: Try again to change your passwordbeing sure to enter the same password for the newpassword and for the verification password.

FMF0260I Password successfully changed.

Explanation: The change password commandcompleted successfully


User response: None

FMF0261I There are no backups for the servernamed servername.

Explanation: There are no backups on the FlashCopyManager server for the specified server name.


User response: None

FMF0262E Errors occurred while processing theVSS operation. Examine the WindowsEvent Logs and DSMERROR.LOG foradditional details.

Explanation: While attempting to process a VSSoperation, an unexpected error occurred.


User response: Attempt to determine the source of theerror by examining the FCM for Windows log file, theFCM Client error log file (DSMERROR.LOG), theWindows Application Event Log, the Windows SystemEvent Log, and the VSS provider log file, if applicable.Additional instructions for Windows VSS operationsare located in the TSM Problem Determination Guide.Correct the problem and retry the operation. If thiserror persists, contact your service representative.

FMF0263E Failed to start Web browser with areturn code of returncode.

Explanation: An attempt was made to start the webbrowser to view the FCM HTML b ook. This attemptfailed.


User response: Start your web browser manually andpoint it to bookfrm.htm in the agent htm directory.

FMF0264I Could not find the default browserdefined. An attempt will be made to useMicrosoft Internet Explorer.

Explanation: An attempt was made to read theregistry to determine the default browser. However, adefault browser is not defined. A determination will bemade where Microsoft Internet Explorer is installed.


User response: It is possible that a default browser isnot defined for the system. This is okay. An attemptwill be made to use Microsoft Internet Explorer.

FMF0265E Could not find Internet Explorer.

Explanation: An attempt was made to read theregistry to determine where Microsoft's InternetExplorer was installed. This attempt failed.


User response: Make sure that the registry is set upcorrectly for Internet Explorer.

FMF0266E Could not find the FlashCopy ManagerHTML books.

Explanation: An attempt was made to read theregistry to determine where the Tivoli Storage Managerbooks were installed. This attempt failed.


User response: It may be necessary to reinstall theapplication client code. This will ensure that theregistry entries are set up correctly.

FMF0267E The verify password entered does notmatch the new password entered.

Explanation: The verify password does not match thenew password.


User response: Retry the command with a matchingverify password.

FMF0292E An unknown error has been detected. rc= rc

Explanation: An error occured without an errormessage. The return code, rc, is displayed.



FMF0300E Invalid restore type.

Explanation: The type of restore requested is invalid.


User response: Re-enter the command specifying avalid restore type.

FMF0301E Invalid backup type.

Explanation: The type of backup requested is invalid.




User response: Re-enter the command specifying avalid backup type.

FMF0351E Invalid trace keyword - 'keyword'



User response: Correct the value.

FMF0357E Unable to open trace output filefile-name.




FMF0366E Unable to close trace output filefile-name.




FMF0367E Unable to write to trace file tracefile.Tracing disabled.



User response: Ensure the device that the tracefileaccess is available and has sufficient space for thetracefile. Retry the command.

FMF0368E Invalid trace file name (name too long).




FMF0383E Specifying the trace file 'link' as asymbolic link is not allowed.




FMF0384E Symbolic link 'linkname' to 'target' wassuccessfully deleted.




FMF0385E Unable to delete symbolic link 'link'.




FMF0476E program-name: cannot open file file-spec:error.

Explanation: FCM cannot open the file.

System action: FCM cannot complete the requestedoperation.


FMF0487E Specifying the error log 'link' as asymbolic link is not allowed.

Explanation: Error log 'linkname' cannot be a symboliclink.

System action: The symbolic link 'linkname' is deleted,the error log is recreated, and processing stops.

User response: Check the location of the new errorlog. To specify the location of the error logs, refer to theuser's manual for the 'errorlogname' option and'DSM_LOG' environmental variable.

FMF0488E Initialization functions cannot open theerror log: log-name. errno = errno-value,

Explanation: The file log-name could not be openedduring initialization. The system set the error codeerrno-value. If the reason given is "access denied," the



current user does not have permission to write to thelog in the directory specified. It is also possible that nospace is available at the given log location.


User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory into which thecurrent user can write. You may also use theERRORLOGNAME option to specify a file to which thecurrent has write permission.

FMF0495E Failure writing to a Tivoli StorageManager log or log-related file: file-name,errno = errno-value, reason

Explanation: A failure was encountered when writingto one of the log files or a related file named file-name.The system set the error code errno-value. reason is thesystem explanation of that error code. Among otherthings, it is possible that no space is available at thegiven log location.


User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory with adequatespace to write the log data.

FMF0496I FCM is converting the log-file fromcontinuous (pruning) mode to wrappingmode. This process may take severalminutes.

Explanation: The log-file was previously in continouosmode where the only size control was through the useof ERRORLOGRETENTION orSCHEDLOGRETENTION option. This is the firstoccasion where ERRORLOGMAX or SCHEDLOGMAXis specified for this log, so its format must be changedand old data saved.

System action: Transition processing continues.


FMF0497I FCM is converting the log-file fromwrapping mode to continuous (pruning)mode. This process may take severalminutes.

Explanation: The log-file was previously in wrappingmode where the size control was through the use of theERRORLOGMAX or SCHEDLOGMAX option. This isthe first occasion where ERRORLOGMAX orSCHEDLOGMAX is not specified for this log, so itsformat must be changed and old data saved.



FMF0498I count log records processed.

Explanation: This is just a progress report to let youknow the process is still ongoing.



FMF0501E Invalid Proxy Configuration Detected:Target Node 'targetnode' is not listed as avalid node to proxy to for Node Name'nodename'.

Explanation: The proxy node configuration on theFCM Server is not correct to support this VSSoperation.

System action: The VSS operation stops.

User response: Contact the FCM Server administratorto have the correct FCM Server GRANT PROXYcommands issued to enable proxy authority for thenodes. If the error persists, contact your servicerepresentative.

FMF0515E Invalid DSMAGENT Nodeconfiguration found for node'dsmagentnode'.

Explanation: The DSMAGENT Node specified is notconfigured properly.


User response: Verify that the DSMAGENT Nodespecified is correct and that the Client AcceptorDaemon (CAD) is running for the DSMAGENT Node.If the error persists, contact your service representative.

FMF0516I The Windows console event handlerreceived a 'event' console event.

Explanation: A console event was received by one ofthe IBM Tivoli Storage Manager processes or programs.The following events can be recevied:

v Ctrl-C - This indicates either the user entered thectrl-c sequence or that one of the Windows serviceswas stopped.



FMF0517I An unexpected error was encountered.FCM function name : function-name FCMfunction : function-desc FCM return code: TSM-rc FCM file : file-name (line-number)

Explanation: None.


User response: Contact the FCM administrator withthe information provided in this message.

FMF0495E • FMF0517I


FMF0518E Backups selected for restore must havethe same backup location (TSM orLOCAL).

Explanation: A VSS restore operation was submittedthat specified multiple backup objects. The backupobjects chosen had different backup locations. This isnot allowed. All backup objects submitted in the sameVSS restore operation must have the same backuplocation, either TSM or LOCAL, but not both.

System action: The VSS restore operation stops.

User response: Retry the VSS restore operationspecifying one backup object at a time.

FMF0519E The VSS operation failed with rc =returncode.

Explanation: There was a failure when FCMperformed the VSS operation.


User response: Verify that the FCM Client AcceptorDaemon (CAD) is installed, configured, and runningproperly on the machine. Retry the operation. If theerror persists, contact your service representative.

FMF0520E Failed to connect to Local DSMAGENTNode 'localdsmagentnode' at address:port'address:portnumber'. Verify that the TSMClient Acceptor Daemon (CAD) isinstalled, configured, and runningproperly.

Explanation: An attempt was made to connect to theTSM Client Acceptor Daemon (CAD) running on thelocal machine. A communication error occurred whenthis connection was attempted.


User response: In order to perform VSS operations,you must have a TSM Client Acceptor Daemon (CAD)and a TSM Remote Client Agent Service (DSMAGENT)installed and configured properly. In addition, the TSMClient Acceptor Daemon (CAD) must be running.Verify that the TSM Client Acceptor Daemon (CAD) isinstalled, configured, and running properly on the localmachine. If the error persists, contact your servicerepresentative.

FMF0521E Pruning functions cannot open one ofthe Tivoli Storage Manager prune files:log-name. errno = errno-value,

Explanation: The file "log-name" could not be openedduring pruning. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thefile in the directory specified. It is also possible that nospace is available at the given file location or anotherTivoli Storager Manager process started by different

user id is performing pruning at the same time.

System action: Pruning stops, processing continues.

User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory into which thecurrent user can write.

FMF0522E DIAG:

Explanation: The message text is provided fordiagnostic purposes and is meant to provideinformation to IBM support in problem determination.



FMF0524S Error 'errtxt' (errno=errno) occurredtrying to write to audit log 'file-name'.The audit log function is disabled.

Explanation: There was an error encountered writingto the audit log (for example, there is not enough spaceon the disk).

System action: Audit logging is disabled for the restof the operation. The return code for the operation isset to 12 to indicate that the contents of the audit logare incomplete.

User response: If this is an out of space conditioneither free up space on the volume or try to write theaudit log to a volume with more space.

FMF0555E Invalid number of snapshots:

Explanation:

System action: Policy was not created.

User response: Specify a number in the range: range:1...9999 or NOLimit

FMF0556E Invalid number of days:

Explanation:

System action: The Policy was not created.


FMF0571E The specified policy was not found:'policy'

Explanation:

System action:

User response: Please make sure that the specifiedpolicy exists.



FMF0572E The specified policy already exists:'policy'

Explanation:


User response: Enter a different name for the policy.

FMF0573E The specified policy could not beupdated: 'policy'

Explanation: This is due to a problem in virtual serverdatabase.

System action:

User response: Make sure that FCM is configuredcorrectly.

FMF0574E The specified policy could not bedeleted: 'policy'


System action:


FMF0575E The specified policy could not becreated: 'policy'


System action:


FMF0576I There were no items found.

Explanation: The query completed successfully, but noresults were found.


User response: Change the specified search criteria.

FMF0581E Volume volume-name could not belocked.

Explanation: The system call to lock the volumefailed.

System action: Processing stopped.

User response: Please verify that no other applicationis accessing the volume. During restore of an imageFCM must have exclusive use of the volume.

FMF0583E Invalid name of policy specified. Validinput characters include alphanumericcharaters and underscore.

Explanation:


User response: Please specify a valid name.

FMF0585E Unable to connect to the TSM ClientAcceptor Daemon (CAD).

Explanation: Possible causes of this message include:The TSM Client Acceptor Daemon (CAD) is notrunning. The VSSALTSTAGINGDIR option setting inthe TDP option file is not set to the same value as theVSSALTSTAGINGDIR option setting in the IBM TivoliStorage Manager Remote Client Agent Service(DSMAGENT) option file. They must be set to the samevalue for successful TDP operations.


User response: Ensure that the TSM Client AcceptorDaemon (CAD) is running. Ensure that theVSSALTSTAGINGDIR option setting in the TDP optionfile is set to the same value as theVSSALTSTAGINGDIR option setting in the IBM TivoliStorage Manager Remote Client Agent Service(DSMAGENT) option file. After correcting theVSSALTSTAGINGDIR option inconsistency, retry theTDP operation.

FMF0588E The value for the BACKUPDESTinationoption is not allowed. IBM TivoliStorage Manager is only licensed to rundata protection operations to aFlashCopy Manager server. It is notlicensed to backup or to restore locallymanaged snapshots.

Explanation: The value for the configuration option isnot allowed. The only allowed value is TSM. IBMTivoli Storage Manager is only licensed to run dataprotection operations to a FlashCopy Manager server. Itis not licensed to backup or to restore locally managedsnapshots.


User response: Set the backup destination to TSM. Inorder to create and restore local VSS backups it isrequired to use and install a fully-featured valid licenseor to purchase an upgrade, and install Tivoli StorageFlashCopy Manager.

FMF0589E You are not allowed to setREMOTEDSMAGentnode option. IBMTivoli Storage Manager is not licensedto perform offloaded VSS backups.

Explanation: The REMOTEDSMAGentnode option isused to perform offloaded VSS backups.




User response: In order to perform offloaded VSSbackups install a valid fully-featured license.

FMF0590E A Data Protection communication errorwith the Tivoli Storage Manager serverhas occurred.

Explanation: Communications with the Tivoli DataProtection server has been lost.


User response: Correct the TCP/IP communicationserror with the Tivoli Storage Manager server and retrythe operation.

FMF0591I Data Protection communications withthe Tivoli Storage Manager server hasbeen successfully recovered.

Explanation: Communications with the Tivoli DataProtection server has been successfully recovered.


User response: Continue with normal operations.

FMF0592E The Data Protection TCP/IP sessionwith the Tivoli Storage Manager serverwas canceled.

Explanation: The Data Protection TCP/IP session withthe Tivoli Storage Manager server was cancelled.


User response: Correct the reason the Tivoli StorageManager server administrator cancelled the session andretry the operation.

FMF0593E IBM Tivoli Storage Manager is notlicensed to perform offloaded VSSbackups.

Explanation: Currently installed license does not allowto perform offloaded VSS backups. In order to use thisfeature it is necessary to install a valid fully-featuredlicense.



FMF0594E You cannot perform offloaded VSSbackups in TSM Server independentenvironment.

Explanation: OFFLOAD option is not available inTSM Server independent environment.


User response: In order to perform offloaded VSS

backups you have to configure Tivoli StorageFlashCopy Manager to manage snapshot backups usinga Tivoli Storage Manager server. To do this you can useTivoli Storage Manager configuration wizard.

FMF0595E The options file 'optfile' does not exist. Itis required for proper operation.

Explanation: The specified TSM API options file couldnot be found. It is required in order to complete thecommand.


User response: Make sure to complete FlashCopyManager configuration and try the operation again.

FMF0598E The application cannot run in safemode.




FMF0599E The application cannot establish aremote powershell connection.

Explanation: The application attempted to establish aremote powershell connection. The operation failed.


User response: Verify you are using the correctcredentials. For more information, see the Microsoftabout_Remote_Troubleshooting Help topic.

FMF0601E There is a problem that causesprocessing to stop. To identify thesource of the problem and the solution,look for details in the service level tracefile.

Explanation: This problem occurs when either thelocal or remote Powershell cmdlet or script reports anerror. Details about the error are not available untilmore trace file information is analyzed.

System action: Application processing stops.

User response: To identify the problem, look forinformation in the service level trace files. For moreinformation about viewing trace files, see theTroubleshooting section of the technical documentationprovided with the software.



FMF0602E While attempting to communicate withthe remote client, a version checkreveals that the versions do not match.

Explanation: During initialization between the localclient and the remote client, version checking revealsthat the versions do not match. This is usually theresult of an upgrade of one client module withoutupgrading other client modules that are part of productsolution.

System action: The calling procedure returns andcontrol is passed back the user.

User response: Check the versions of all TSM Clientproducts that communicate with each other and ensurethat they are all at the same version, release, and level.

FMF5247S File 'file-name' could not be found, or itcannot be read.

Explanation: Common reasons for this error include:

v The default options file does not exist.

v The DSM_CONFIG (or DSMI_CONFIG if you areusing the IBM Tivoli Storage Manager API)environment variable specifies an options file thatdoes not exist.

v You specified the TSMOPTFILE or FCMOPTFILEoption when starting the IBM Tivoli Storage Managerclient, but the option file you provided does notexist.

v You specified the TSMOPTFILE or FCMOPTFILEoption when starting the IBM Tivoli Storage Managerclient, but the configuration file that you provideddoes not have appropriate read permissions for theuser that is running the operation.

v You specified the CONFIGFILE option when startingthe IBM Tivoli Storage Manager client, but theconfiguration file you provided does not exist.

v You specified the CONFIGFILE option when startingthe IBM Tivoli Storage Manager client, but theoptions file that you provided does not haveappropriate read permissions for the user that isrunning the operation.

System action: IBM Tivoli Storage Manager clientprocessing stops.

User response: Make sure that the file you want touse exists, it has the read rights set for the user that isrunning the operation, and it is in the standard fileencoding of the system. For example, on Windows theexpected file encoding is ANSI. Review theconfiguration information in the IBM Tivoli StorageManager client manual specific to your operatingsystem. If the problem persists, ask your IBM TivoliStorage Manager administrator for further assistance.

FMF5814E Invalid command. FCM for Windowsdoes not support OFFLOAD with thecombination specified for backupdestination and version of Windows.

Explanation: The OFFLOAD option was specifiedwith an unsupported backup destination. FCM forWindows only supports offload with a backupdestination of TSM, or if running on a Windows Server2008 or later, backup destination TSM or BOTH.

System action: The backup operation is canceled.

User response: Retry the VSS offloaded backupoperation specifying a valid backup destination.

FMF5815E Invalid command. FCM for Windowsdoes not support INTO option with thespecified backup destination of LOCAL.

Explanation: The INTO option was specified with anunsupported backup destination. FCM for Windowsonly supports INTO with a backup destination of TSM.

System action: The restore operation is canceled.

User response: Retry the VSS restore into operationspecifying a valid backup destination.

FMF5816E Invalid command. The INTO optiononly supports one restore componentper command.

Explanation: The INTO option was specified withmultiple restore components. FCM for Windows onlysupports INTO with a single restore component.


User response: Retry the VSS restore into operationspecifying only one restore component.

FMF5817E The volume/mount point specified inthe INTO option is not valid.

Explanation: The INTO option was specified with aninvalid value.


User response: Retry the VSS restore INTO operationspecifying a valid INTO value.

FMF5945E The following mount point is used as amapped network share for 'share-name':'drive-letter'.

Explanation: When a backup is mounted over amapped network drive letter, the files on the mountedsnapshot cannot be accessed using that drive letter.


User response: Specify an unassigned drive letter ormount point directory.



FMF5956I The logfile log file could not be pruned.Processing will continue.

Explanation: An attempt to prune the log wasunsuccessful.


User response: The log file may not exist. If the logfile exists, view the log for indications of possibleproblems.

FMF5957I The logfile log file was prunedsuccessfully.

Explanation: The log file mentioned prunedsuccessfully.



FMF5970I The operation was canceled by the user.

Explanation: The user has requested that theoperation be canceled.


User response: None

FMF5976E An error was encountered withFlashCopy Manager API initialization,rc = returncode. Examine the dsierror.logfor more information or determine if theFCM API is installed properly.

Explanation: An attempt was made to run setup forthe FCM API. However, errors were encountered.


User response: Examine the dsierror.log file todetermine the problem. If this file does not exist, it ispossible that the FCM API is not installed properly. Ifthis is the case, reinstall the FCM API and try runningthe command again.

FMF5989E No components were found that matchthe criteria specified.

Explanation: None of the items specified match thecomponents found on this machine.


User response: Correct the component specificationand try the operation again.

FMF5990E There were no backups found thatmatch the criteria specified.

Explanation: There are no backups found on theFlashCopy Manager server for the specified criteria.


User response: Correct the backup specification andtry the operation again.

FMF6011E The configuration file specified cannotbe found.

Explanation: The file specified in the /configfileparameter cannot be found.


User response: Ensure the correct file name isspecified.

FMF6012I The configuration file specified cannotbe found. Creating configuration file'configfile' with default settings.

Explanation: The file specified in the /configfileparameter cannot be found. The file specified getscreated with default settings.


User response: None

FMF6013E Mount backup command failed. Themount point and or backup specified isinvalid. Please refer to dsmerror.log forfurther details.

Explanation: The mount backup command failed. Thebackup specified may already be mounted and or thedrive to map to may already be in used

System action: Processing stops

User response: Check to make sure that the backupspecified is not already mounted and that the drive tomap to is available.

FMF6014E Unmount backup command failed.Please refer to dsmerror.log for furtherdetails.

Explanation: The unmount backup command failed.The backup specified may not be mounted.


User response: Check to make sure that the backupspecified is mounted.

FMF6015E Invalid component list. Qualified andnon-qualified objects can not bespecified on the same command.

Explanation: A command was specified with acomponent list that contained qualifed andnon-qualified objects. This is not valid.


User response: Enter the command again with a



component list that contains all qualified or allnon-qualified objects.

FMF6016E Conflicting arguments found. Point inTime options can not be specified onthe same command as qualified objects.

Explanation: A command was specified with the pointin time option and a component list that contained oneor more qualifed objects. This is not valid.


User response: Correct the syntax and retry theoperation.

FMF6017E An invalid duplicate object, 'object', wasfound in the component list. This is notvalid on a RESTORE operation.

Explanation: A command was specified with acomponent list that contained duplicate objects.RESTORE operations do not support this.


User response: Correct the syntax and retry theoperation.

FMF6018E FlashCopy Manager was not able toobtain VSS component information.

Explanation: An error occurred when attempting toenumerate the VSS components for the operation. Thiscould be the result of a VSS Requestor or VSS Writererror.


User response: Stop the TSM Remote Client AgentWindows service then stop and restart the TSM ClientAcceptor Windows service. After that, retry theoperation. If the problem persists, refer to thedsmerror.log file, the dsierror.log file, and/or theWindows Event Log for further details on the error.

FMF6019E In the component list that is specified,the following object is not valid: 'object'.

Explanation: The command that is entered includes acomponent list. The list of components contains one ormore invalid objects. For example, when entering aBACKUP or RESTORE command, if the component listincludes a volume or mount point that is not valid or isnot eligible for back up, this message is displayed. Inaddition, the GUID volume name cannot be specified.For RESTORE, MOUNT BACKUP, or DELETEBACKUP commands, this message is displayed if thecomponent list contains a backup specification that isnot found in the backup inventory.


User response: Verify the correct syntax is used when

entering the command. If the message is displayedagain, verify the volume and mount point names arecorrectly identified. A misspelling can trigger thismessage.

FMF6020I The configuration file cannot be read.Creating configuration file 'configfile'with default settings.

Explanation: The file specified gets created withdefault settings.


User response: None

FMF6021E The value for the preference preference isnot valid. See the FCMCLI HELPUPDATE/INSERT output or the User'sGuide for valid command parameters.

Explanation: The preference being set is not valid.


User response: You can either run the command"fcmcli help update" or view the User's Guide for validUPDATE command parameters.

FMF6026E PASSWORDACCESS is Generate. Eitherthe stored password is incorrect or thereis no stored password. If you do nothave a stored password, use the-TSMPassword=xxx option to set andstore your password.

Explanation: The PASSWORDACCESS option is set togenerate in the client options file. However, nopassword is stored. An initial password needs to bestored.


User response: Invoke the command again using the-TSMPassword option. Any subsequent commandsshould now complete without specifying a password.

FMF6030E The FlashCopy Manager VSS FastRestore operation failed to restore thevolume. Examine the FCMFSFR.LOGfile for more details on the failure.

Explanation: FlashCopy Manager attempted toperform a file-level copy of all files from the snapshotbackup to the original source volume. There was afailure during the file-level copy operation. This can becaused by locked files or files that are in use by theoperating system.


User response: Examine the FCMFSFR.LOG file that islocated in the FlashCopy Manager installation directoryfor specific details on the error. If you are not able to



perform the VSS Fast Restore operation successfully,access the backup using the FCMCLI MOUNTcommand or the equivalent function in the MMCinterface. After mounting the backup, use WindowsExplorer or other operating system commands to copythe needed files.

FMF6031E The option /BACKUPDESTINATION isinvalid when performing data protectionoperations using a FlashCopy Managervirtual server.

Explanation: Data protection commands default to/BACKUPDESTINATION=LOCAL when performedagainst a FlashCopy Manager virtual server. TheFlashCopy Manager supports no other values for thisoption. As a result it is no longer necessary to specifythis parameter. For compatibility with other productsvalues for /BACKUPDESTINATION can be specifiedas long as this is set to its only valid value. This meansthat /BACKUPDESTINATION option can only be setto LOCAL value.


User response: Retry the command removing the/BACKUPDESTINATION option.

FMF6031E


Chapter 4. FMX messages

Messages with prefix FMX are issued by the IBM Tivoli Storage FlashCopyManager for Microsoft Exchange Server. Tivoli Storage FlashCopy Manager V4.1.2FMX messages are listed in ascending numerical order. The complete message isdocumented, including message ID, message text, explanation, system action, anduser response.

FMX0003S An internal processing error hasoccurred.




FMX0004E An unknown error has been detected.




FMX0005E Out of memory. Stop other processesand try the operation again.




FMX0053E License file (licensefile) could not beopened.




FMX0054E Read failure on license file (licensefile).




FMX0055E Write failure on license file (licensefile).




FMX0056E Data in the license file (licensefile) is notin a valid format.




FMX0057E The checksum in the license file(licensefile) does not match the licensestring text.




FMX0058E The 'Try and Buy' license has expired.




FMX0100E Incomplete command:





FMX0101E Invalid argument:




FMX0102E Invalid command:




FMX0103E Invalid option for the specifiedcommand:




FMX0104E Invalid option:




FMX0105E Missing argument:




FMX0132W Tracing could not be started. Processingwill continue.



User response: Refer to the other messages thatdisplay with this message to determine the problem.

FMX0133W Could not locate installation directory.Attempting to continue...




FMX0134W Could not locate log directory.Processing will continue...




FMX0150I Operation canceled by user.

Explanation: The user has requested that the DataProtection for Microsoft Exchange Server applicationclient end by entering ctrl-C.


User response: None

FMX0151E Errors occurred while processing therequest.




FMX0152I Performance stats: seconds seconds spentin apicall API calls



User response: None

FMX0101E • FMX0152I


FMX0153I Performance stats: seconds seconds spentin function



User response: None

FMX0154E The Data Protection for MicrosoftExchange Server application clientcannot work with the version of theTivoli Storage Manager API you haveinstalled. Please install versionversion.release.level or greater.

Explanation: The version of the Tivoli StorageManager API currently installed on the system is olderthan the version used to build the Data Protection forMicrosoft Exchange Server application client.


User response: Install a version of the Tivoli StorageManager API at or later than the indicated level. Acopy is distributed with the Data Protection forMicrosoft Exchange Server application client.

FMX0155E The Data Protection for MicrosoftExchange Server application clientcannot work with the release of TivoliStorage Manager API you haveinstalled. Please install releaseversion.release.l evel or greater.

Explanation: The release of the Tivoli StorageManager API currently installed on the system is olderthan the release used to build the Data Protection forMicrosoft Exchange Server application client.


User response: Install a release of the Tivoli StorageManager API at or later than the indicated level. Acopy is distributed with the Data Protection forMicrosoft Exchange Server application client.

FMX0156E Could not load the Tivoli StorageManager API.

Explanation: The Tivoli Storage Manager API couldnot be loaded.


User response: Ensure the Tivoli Storage Manager APIis correctly installed. Run the Data Protection forMicrosoft Exchange Server application client with the/TRACEFLAGS=API /TRACEFILE=filename optionsand view the tracefile to determine why it could not beloaded. Another possible cause is that the TSMAPI.DLLdoes not exist in the system directory. Re-install theTivoli Storage Manager API, if this is the case.

FMX0160E An authentication error occurred withyour stored Tivoli Storage Managerpassword.

Explanation: You were unable to log on to the TivoliStorage Manager server due an authentication error.


User response: The stored Tivoli Storage Managerpassword may have become corrupted. Contact yourTivoli Storage Manager server administrator.

FMX0161E Authentication error. The passwordentered is not valid. You are not loggedon to the Tivoli Storage Manager server.



User response: Enter the correct Tivoli StorageManager password and try again.

FMX0162E The passwords entered do not match.Please enter them again.




FMX0163E The directory path needs to befully-qualified.




FMX0167E The fully-qualified file name is toolong.



User response: None

FMX0200E File (filename) could not be opened forreading.



User response: None

FMX0153I • FMX0200E

Chapter 4. FMX messages 207

FMX0201E File (filename) could not be opened forwriting.



User response: None

FMX0202E Read failure on file (filename).



User response: None

FMX0203E Write failure on file (filename).



User response: None

FMX0204E File (filename) could not be closed.



User response: None

FMX0205E File (filename) statistics could not beobtained.



User response: None

FMX0206E Directory (directory) could not be created.



User response: None

FMX0207E Directory path (directorypath) is too long.



User response: None

FMX0208E There is not enough disk space for theoperation attempted.



User response: None

FMX0209E The rename of file (filename1) to(filename2) failed.



User response: None

FMX0210E The Tivoli Storage Manager high levelqualifier is too long.

Explanation: An attempt was made to use a TivoliStorage Manager high level qualifier that was too long.This attempt failed.


User response: None

FMX0211E The Tivoli Storage Manager low levelqualifier is too long.

Explanation: An attempt was made to use a TivoliStorage Manager low level qualifier that was too long.This attempt failed.


User response: None

FMX0212E The Tivoli Storage Manager filespacename is too long.

Explanation: An attempt was made to use a TivoliStorage Manager filespace name that was too long. Thisattempt failed.


User response: None

FMX0213E The maximum number of objectsallowed per Tivoli Storage Managertransaction is too small.

Explanation: In order to maintain backup dataintegrity, multiple backup objects are sent to the TivoliStorage Manager server in a single transaction. TheTivoli Storage Manager server has indicated that themaximum number of objects allowed per transaction isless than the minimum required by the Data Protectionfor Microsoft Exchange Server application client.


FMX0201E • FMX0213E


User response: Increase the maximum number ofobjects allowed per transaction on the Tivoli StorageManager server and retry the operation.

FMX0214E The backup object's management classbackup copy group does not exist.

Explanation: The Tivoli Storage Manager server hasindicated that the backup object's management classbackup copy group does not exist.


User response: Contact your Tivoli Storage Managerserver administrator.

FMX0215E All backup objects do not have the samemanagement class backup copydestination.

Explanation: In order to maintain backup dataintegrity, multiple backup objects are sent to the TivoliStorage Manager server within a single transaction. Allbackup objects within a single transaction are requiredto have the same management class backup copydestinations.



FMX0216E Unable to obtain space information forvolume (volumename).



User response: None

FMX0217E The Tivoli Storage Manager filespacename is invalid.




FMX0218E The Tivoli Storage Manager high levelqualifier is invalid.




FMX0219E The Tivoli Storage Manager low levelqualifier is invalid.




FMX0256E The password in your Tivoli StorageManager options file has expired. Pleasechange your password on the TivoliStorage Manager server using the'change password' command and theneither change or remove the passwordvalue in your options file.

Explanation: Your Tivoli Storage Manager passwordhas expired. You need to change your password.


User response: Obtain a new password for your TivoliStorage Manager server; node using the changepassword command or by asking your Tivoli StorageManager Administrator to change your password.

FMX0257E Your password has expired.

Explanation: Your Tivoli Storage Manager passwordhas expired. A new password needs to be obtained.


User response: Obtain a new password for your TivoliStorage Manager node using the change passwordcommand or by asking your Tivoli Storage ManagerAdministrator to change your password.

FMX0258E You did not enter a valid password.Processing ends.




FMX0259E The password you entered forverification does not match thepassword you entered for your newpassword. Your password will not bechanged.






FMX0260I Password successfully changed.



User response: None

FMX0261I There are no backups for the servernamed servername.

Explanation: There are no backups on the TivoliStorage Manager server for the specified server name.


User response: None

FMX0262E Errors occurred while processing theVSS operation. Examine the WindowsEvent Logs and DSMERROR.LOG foradditional details.



User response: Attempt to determine the source of theerror by examining the Data Protection for Exchangelog file, the TSM Client error log file(DSMERROR.LOG), the Windows Application EventLog, the Windows System Event Log, and the VSSprovider log file, if applicable. Additional instructionsfor Windows VSS operations are located in the TSMProblem Determination Guide. Correct the problem andretry the operation. If this error persists, contact yourservice representative.

FMX0263E Failed to start Web browser with areturn code of returncode.

Explanation: An attempt was made to start the webbrowser to view the TSM HTML b ook. This attemptfailed.



FMX0264I Could not find the default browserdefined. An attempt will be made to useMicrosoft Internet Explorer.




FMX0265E Could not find Internet Explorer.




FMX0266E Could not find the Tivoli StorageManager HTML books.




FMX0267E The verify password entered does notmatch the new password entered.




FMX0292E An unknown error has been detected. rc= rc




FMX0300E Invalid restore type.




FMX0260I • FMX0300E


FMX0301E Invalid backup type.




FMX0351E Invalid trace keyword - 'keyword'




FMX0357E Unable to open trace output filefile-name.




FMX0366E Unable to close trace output filefile-name.




FMX0367E Unable to write to trace file tracefile.Tracing disabled.




FMX0368E Invalid trace file name (name too long).



User response: Change the file name used as the

TRACEFILE so that it is equal to or less than 255characters in length.

FMX0383E Specifying the trace file 'link' as asymbolic link is not allowed.




FMX0384E Symbolic link 'linkname' to 'target' wassuccessfully deleted.




FMX0385E Unable to delete symbolic link 'link'.




FMX0476E program-name: cannot open file file-spec:error.

Explanation: DP cannot open the file.

System action: DP cannot complete the requestedoperation.


FMX0487E Specifying the error log 'link' as asymbolic link is not allowed.






FMX0488E Initialization functions cannot open theerror log: log-name. errno = errno-value,

Explanation: The file log-name could not be openedduring initialization. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thelog in the directory specified. It is also possible that nospace is available at the given log location.



FMX0495E Failure writing to a Tivoli StorageManager log or log-related file: file-name,errno = errno-value, reason




FMX0496I DP is converting the log-file fromcontinuous (pruning) mode to wrappingmode. This process may take severalminutes.




FMX0497I DP is converting the log-file fromwrapping mode to continuous (pruning)mode. This process may take severalminutes.




FMX0498I count log records processed.




FMX0501E Invalid Proxy Configuration Detected:Target Node 'targetnode' is not listed as avalid node to proxy to for Node Name'nodename'.

Explanation: The proxy node configuration on theTSM Server is not correct to support this VSSoperation.


User response: Contact the TSM Server administratorto have the correct TSM Server GRANT PROXYcommands issued to enable proxy authority for thenodes. If the error persists, contact your servicerepresentative.

FMX0515E Invalid DSMAGENT Nodeconfiguration found for node'dsmagentnode'.




FMX0516I The Windows console event handlerreceived a 'event' console event.

Explanation: A console event was received by one ofthe Data Protection for Microsoft Exchange Serverprocesses or programs. The following events can berecevied:




FMX0517I An unexpected error was encountered.DP function name : function-name DPfunction : function-desc DP return code :TSM-rc DP file : file-name (line-number)



Explanation: None.


User response: Contact the DP administrator with theinformation provided in this message.

FMX0518E Backups selected for restore must havethe same backup location (TSM orLOCAL).




FMX0519E The VSS operation failed with rc =returncode.

Explanation: There was a failure when TSMperformed the VSS operation.


User response: Verify that the TSM Client AcceptorDaemon (CAD) is installed, configured, and runningproperly on the machine. Retry the operation. If theerror persists, contact your service representative.

FMX0520E Failed to connect to Local DSMAGENTNode 'localdsmagentnode' at address:port'address:portnumber'. Verify that the TSMClient Acceptor Daemon (CAD) isinstalled, configured, and runningproperly.




FMX0521E Pruning functions cannot open one ofthe Tivoli Storage Manager prune files:log-name. errno = errno-value,

Explanation: The file "log-name" could not be openedduring pruning. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thefile in the directory specified. It is also possible that nospace is available at the given file location or anotherTivoli Storager Manager process started by differentuser id is performing pruning at the same time.



FMX0522E DIAG:




FMX0524S Error 'errtxt' (errno=errno) occurredtrying to write to audit log 'file-name'.The audit log function is disabled.




FMX0555E Invalid number of snapshots:

Explanation:



FMX0556E Invalid number of days:

Explanation:





FMX0571E The specified policy was not found:'policy'

Explanation:

System action:


FMX0572E The specified policy already exists:'policy'

Explanation:



FMX0573E The specified policy could not beupdated: 'policy'


System action:


FMX0574E The specified policy could not bedeleted: 'policy'


System action:


FMX0575E The specified policy could not becreated: 'policy'


System action:


FMX0576I There were no items found.




FMX0581E Volume volume-name could not belocked.



User response: Please verify that no other applicationis accessing the volume. During restore of an image DPmust have exclusive use of the volume.

FMX0583E Invalid name of policy specified. Validinput characters include alphanumericcharaters and underscore.

Explanation:



FMX0585E Unable to connect to the TSM ClientAcceptor Daemon (CAD).

Explanation: Possible causes of this message include:The TSM Client Acceptor Daemon (CAD) is notrunning. The VSSALTSTAGINGDIR option setting inthe TDP option file is not set to the same value as theVSSALTSTAGINGDIR option setting in the DataProtection for Microsoft Exchange Server Remote ClientAgent Service (DSMAGENT) option file. They must beset to the same value for successful TDP operations.


User response: Ensure that the TSM Client AcceptorDaemon (CAD) is running. Ensure that theVSSALTSTAGINGDIR option setting in the TDP optionfile is set to the same value as theVSSALTSTAGINGDIR option setting in the DataProtection for Microsoft Exchange Server Remote ClientAgent Service (DSMAGENT) option file. Aftercorrecting the VSSALTSTAGINGDIR optioninconsistency, retry the TDP operation.

FMX0588E The value for the BACKUPDESTinationoption is not allowed. Data Protectionfor Microsoft Exchange Server is onlylicensed to run data protectionoperations to a Tivoli Storage Managerserver. It is not licensed to backup or torestore locally managed snapshots.

Explanation: The value for the configuration option isnot allowed. The only allowed value is TSM. DataProtection for Microsoft Exchange Server is onlylicensed to run data protection operations to a TivoliStorage Manager server. It is not licensed to backup orto restore locally managed snapshots.


User response: Set the backup destination to TSM. In



order to create and restore local VSS backups it isrequired to use and install a fully-featured valid licenseor to purchase an upgrade, and install Tivoli StorageFlashCopy Manager.

FMX0589E You are not allowed to setREMOTEDSMAGentnode option. DataProtection for Microsoft ExchangeServer is not licensed to performoffloaded VSS backups.

Explanation: The REMOTEDSMAGentnode option isused to perform offloaded VSS backups.



FMX0590E A Data Protection communication errorwith the Tivoli Storage Manager serverhas occurred.




FMX0591I Data Protection communications withthe Tivoli Storage Manager server hasbeen successfully recovered.




FMX0592E The Data Protection TCP/IP sessionwith the Tivoli Storage Manager serverwas canceled.




FMX0593E Data Protection for Microsoft ExchangeServer is not licensed to performoffloaded VSS backups.




FMX0594E You cannot perform offloaded VSSbackups in TSM Server independentenvironment.



User response: In order to perform offloaded VSSbackups you have to configure Tivoli StorageFlashCopy Manager to manage snapshot backups usinga Tivoli Storage Manager server. To do this you can useTivoli Storage Manager configuration wizard.

FMX0595E The options file 'optfile' does not exist. Itis required for proper operation.



User response: Make sure to complete Tivoli StorageManager configuration and try the operation again.

FMX0598E The application cannot run in safemode.




FMX0599E The application cannot establish aremote powershell connection.




FMX0601E There is a problem that causesprocessing to stop. To identify thesource of the problem and the solution,look for details in the service level tracefile.

Explanation: This problem occurs when either thelocal or remote Powershell cmdlet or script reports an



error. Details about the error are not available untilmore trace file information is analyzed.



FMX0602E While attempting to communicate withthe remote client, a version checkreveals that the versions do not match.




FMX3528E Data Protection for Microsoft ExchangeServer is only licensed to run dataprotection operations to a Tivoli StorageManager server. It is not licensed toback up or to restore using locallymanaged snapshots.

Explanation: Currently installed license allows tocreate and restore only TSM VSS backups. In order tocreate backups and to restore local VSS backups, DataProtection for Exchange verifies that the ExchangeServer supports VSS backup (that is, it is at leastExchange Server 2010), and that a valid fully-featuredlicense is installed.


User response: In order to create and restore local VSSbackups it is required to purchase and install afully-featured valid license.

FMX5050I A new configuration file has beencreated.

Explanation: The /configfile value specified a filename that does not exist. A new file has been created.



FMX5051I The configuration file cannot be found,using default settings.

Explanation: The /configfile value specified a file thatcannot be found. Default settings will be used.

System action: Processing continues using defaultsettings.

User response: Ensure that the configuration fileexists, and enter the command again.

FMX5052E An error occurred trying to set thepreference preference.

Explanation: An error occurred while writing to thepreferences file.


User response: View any other messages that weredisplayed. Fix any of the problems indicated and enterthe command again.

FMX5053E The value for the preference preference isnot valid. See the TDPEXCC HELP SEToutput or the User's Guide for valid SETcommand parameters.

Explanation: The preference being set is not valid.


User response: Run the "tdpexcc help set" commandor see the User's Guide for valid SET commandparameters.

FMX5054I The preference has been setsuccessfully.

Explanation: The preference was set successfully.


User response: None

FMX5055E The Microsoft Exchange API could notbe loaded.

Explanation: If running on Microsoft Exchange 5.5,the dll that is attempting to load is edbbcli.dll. Ifrunning on a later version of Microsoft Exchange, thedll that is attempting to load is esebcli2.dll.


User response: Ensure that the Microsoft ExchangeServer has been correctly installed.

FMX5056I The logfile log file could not be pruned.Processing will continue.





User response: Ensure that the log file name is validand that the log file exists. If a valid log file name wasspecified, view the log for indications of what theproblem may be.

FMX5057I The logfile log file has been prunedsuccessfully.

Explanation: The specified log file was prunedsuccessfully.



FMX5058W The length of the logf ile name isgreater than the maximum allowed.Processing will continue using a log filename of logfile in the current directory.

Explanation: The log file name entered was not fullyqualified. When the fully qualified log file name wascreated, it was longer than the maximum allowedlength for a log file name.

System action: Processing continues creating andusing a log file in the current directory.

User response: Update the log file name using a fullyqualified path.

FMX5059W The logfile log file cannot be opened forwriting. There will be no logging ofevents.

Explanation: The specified log file could not beopened for append and logging of events will notoccur. The log file may be read-only or the log filename is not valid.

System action: Processing continues without logging.

User response: Determine why the log could not beopened. You may need to ensure that the log file is notread-only, or ensure that a valid drive or partition isspecified in the log file name.

FMX5060E A Tivoli Storage Manager API error hasoccurred. Examine the Windows EventLogs and DSMERROR.LOG foradditional details.

Explanation: A Tivoli Storage Manager API api errorhas occurred.


User response: Try the operation again. If the errorpersists, contact your service representative.

FMX5061E A Microsoft Exchange api error hasoccurred.

Explanation: A Microsoft Exchange api error hasoccurred.


User response: Try the operation again. If the errorpersists, contact your service representative.

FMX5062E The version of Microsoft Exchange thatis running is not a supported version forIBM Tivoli Storage Manager for Mail.

Explanation: IBM Tivoli Storage Manager for Mail hasdetected a version of Microsoft Exchange Server that isnot supported.


User response: Refer to the software requirementssection of the product documentation to view a list ofthe supported versions of Microsoft Exchange Server. Ifthe version of Microsoft Exchange Server running is asupported version, try the operation again. If the errorpersists, contact your service representative.

FMX5063E An error occurred trying to get theMicrosoft Exchange version information.It could be a problem with the registry.Or, a Microsoft Exchange Server is notinstalled on this machine.

Explanation: An attempt was made to read theregistry to determine the level of Microsoft Exchangethat is currently running. This attempt failed.


User response: Determine if the registry has beencorrupted. Also, ensure that the Microsoft ExchangeServer is installed on this machine.

FMX5067E The specified databases do not exist orhave not been dismounted.

Explanation: The mailbox databases that were enteredeither do not exist on the Microsoft Exchange Server orhave not been dismounted.


User response: Verify that the mailbox databases existand that the databases have been dismounted beforestarting the restore.

FMX5068W The database <databasename> does notexist in the storage group <storagegroup>.

Explanation: The database that was entered does notexist in the storage group that was entered.


FMX5057I • FMX5068W


User response: Enter the command again specifying avalid database name that exists in a valid storagegroup.

FMX5069W The database <database> in the storagegroup <storage group> is not dismounted.

Explanation: While examining the list of databases torestore, it was determined that not all of the databaseswithin the specified storage groups were dismounted.

System action: Processing continues skipping over thelisted databases and storage groups.

User response: Ensure that the databases aredismounted and enter the command again.

FMX5070W The Directory Service is not running.The Directory will not be backed up.

Explanation: A request was made to backup theDirectory service. However, the Directory service needsto be running in order to do the backup.


User response: Start the Directory service and enterthe backup command again.

FMX5072W Database <component name> isdismounted -- skipping.

Explanation: A request was made to back up a set ofdatabases. However, some databases are not mounted.The databases need to be mounted for the backup toproceed.

System action: Processing continues, but thedismounted databases are skipped.

User response: Ensure that the database you want toback up is mounted.

FMX5073E None of the databases are backed up.

Explanation: The request to back up a set of databasescould not be completed because at least one of thefollowing conditions is true: 1) all of the databases aredismounted 2) a backup is in progress on anotherreplica 3) a backup has been made more recently thanspecified by the /MINimumbackupinterval parameter


User response: Ensure that the database you want toback up is mounted, or another backup is not inprogress, or change the /MINimumbackupintervalparameter.

FMX5074E The databases entered do not exist, orwere entered with the wrongcapitalization.

Explanation: A request was made to back up a set ofdatabases that do not exist, or the database namesmight not have been entered using the correctcapitalization.


User response: Check the capitalization and spellingof the databases and enter the backup command again.

FMX5087E The PASSWORDACCESS parameter isset to GENERATE, but either the storedpassword is incorrect or there is nostored password. If you do not have astored password, use the-TSMPassword=xxx option to set andstore your password.

Explanation: The client options file has thePASSWORDACCESS option set to GENERATE.Currently, there is no password stored. An initialpassword must be stored.


User response: Enter the command again using the-TSMPassword option. After doing so,subsequentcommands will not require a password.

FMX5140I Database <database> does not exist -skipping.

Explanation: The database that was specified by theuser is not found on this Exchange server.

System action: This database is skipped.

User response: Ensure that the database name isspelled correctly and enter the command again.

FMX5142E The requested database was not found.

Explanation: The databases could not be found on thisMicrosoft Exchange server.


User response: Ensure that the database names arespelled correctly and enter the command again.

FMX5151W The folder 'foldername' cannot be deletedautomatically from the 'mailboxname'mailbox. The folder needs to be deletedmanually. If the folder is not deleted, itwill continue to consume storage space.

Explanation: The folder that needs to be deletedmanually holds the temporary mailbox contents. Thetemporary mailbox has no size limit so the space usagevaries.

FMX5069W • FMX5151W


System action: The mailbox is restored, but thetemporary mailbox is not removed.

User response: You can delete the folder by usingeither the Outlook mail client or Outlook Web Access.

FMX5209I There are no backups matching theserver name servername and thefollowing filespecs:filespecs.

Explanation: There are no database backups on theTivoli Storage Manager server for the specified servername.


User response: None if there are no backups;otherwise, check your spelling and try again.

FMX5228I The LOCALDSMAgentnode preferenceis not set correctly.

Explanation: Data Protection for Exchange has notbeen configured to perform VSS operations. TheLOCALDSMAgentnode preference is not set correctly.


User response: Ensure that theLOCALDSMAgentnode preference is set correctly. Thispreference can be set by running the configurationwizard.

FMX5229E An error occurred while obtaining VSSinformation from the following LocalDSMAgent Node: 'localdsmagentnode'.

Explanation: Data Protection for Exchange attemptedto obtain VSS information through the specifiedLOCALDSMAgentnode, but failed. The specific errormessage encountered is also displayed.

System action: VSS information is not displayed.

User response: Refer to the error message displayedalong with this message.

FMX5237E Unable to communicate with theMicrosoft Exchange Server.

Explanation: An attempt was made to communicatethe with the Microsoft Exchange Server that wasentered. This connection attempt failed.


User response: Ensure that the name of the MicrosoftExchange Server that was entered is valid. Also, ensurethat the Microsoft Exchange Server is running and thatthe Exchange services are started.

FMX5239E Unable to retrieve the componentinformation.

Explanation: An attempt was made to retrieve thestorage group or mailbox database information for theMicrosoft Exchange Server. This attempt failed.


User response: Ensure that the Microsoft ExchangeServer is running properly.

FMX5240E Unable to retrieve database information.

Explanation: Data Protection for Exchange tried toretrieve database information from Microsoft ExchangeServer, but this attempt failed.


User response: Ensure that Microsoft Exchange Serveris running properly.

FMX5241E The Microsoft Exchange InformationStore is currently not running.

Explanation: Data Protection for Exchange tried toretrieve information about the Microsoft ExchangeServer Information Store, but this attempt failed.


User response: To retrieve the Microsoft ExchangeServer information, the Microsoft Exchange InformationStore must be running. Start or restart this service toget the requested information.

FMX5247S File 'file-name' could not be found, or itcannot be read.



v The DSM_CONFIG (or DSMI_CONFIG if you areusing the Data Protection for Microsoft ExchangeServer API) environment variable specifies anoptions file that does not exist.

v You specified the TSMOPTFILE or FCMOPTFILEoption when starting the Data Protection forMicrosoft Exchange Server client, but the option fileyou provided does not exist.

v You specified the TSMOPTFILE or FCMOPTFILEoption when starting the Data Protection forMicrosoft Exchange Server client, but theconfiguration file that you provided does not haveappropriate read permissions for the user that isrunning the operation.

v You specified the CONFIGFILE option when startingthe Data Protection for Microsoft Exchange Serverclient, but the configuration file you provided doesnot exist.

v You specified the CONFIGFILE option when startingthe Data Protection for Microsoft Exchange Server

FMX5209I • FMX5247S


client, but the options file that you provided doesnot have appropriate read permissions for the userthat is running the operation.

System action: Data Protection for Microsoft ExchangeServer client processing stops.

User response: Make sure that the file you want touse exists, it has the read rights set for the user that isrunning the operation, and it is in the standard fileencoding of the system. For example, on Windows theexpected file encoding is ANSI. Review theconfiguration information in the Data Protection forMicrosoft Exchange Server client manual specific toyour operating system. If the problem persists, askyour Data Protection for Microsoft Exchange Serveradministrator for further assistance.

FMX5304E Unable to open a Microsoft Exchangeservice to determine if it is running.

Explanation: An attempt to open a service failed.


User response: Check your Microsoft Exchangeservices and ensure that they are running properly.

FMX5305E Unable to query service information.

Explanation: An attempt to query specific serviceinformation failed.


User response: Check your Microsoft Exchangeservices and ensure that they are running properly.

FMX5350E An unknown Exchange error hasoccurred.

Explanation: An Exchange error has occurred. TheWindows Event Log may contain more information.


User response: If the Windows Event Log does nothelp resolve the problem, verify the Exchange Serverinstallation and retry the operation.

FMX5351E The Exchange server application is notregistered for backup.

Explanation: The Exchange server application must beregistered for backup with the Windows Server. TheWindows NT event log may contain more information.


User response: If the Windows NT event log does nothelp resolve the problem, verify the Exchange Serverinstallation and retry the operation. If the error persists,contact your service representative.

FMX5352E The Exchange server application is notregistered for offline restore.

Explanation: The Exchange server application must beregistered for offline restore with the Windows Server.The Windows NT event log may contain moreinformation.



FMX5353E The Exchange server application is notregistered for online restore.

Explanation: The Exchange server application must beregistered for online restore with the Windows Server.The Windows NT event log may contain moreinformation.



FMX5354E The database was not found.

Explanation: The specified database name was notfound.


User response: Verify the command input and retrythe operation. If the error persists, contact your servicerepresentative.

FMX5355E The database was not found. Ensurethat the database exists and is spelledcorrectly with proper capitalization.

Explanation: The specified database name was notfound.


User response: Ensure that the database exists and isspelled correctly with proper capitalization, and retrythe operation.

FMX5356E The database file name is undefined.

Explanation: Every Microsoft Exchange database mustspecify a database file name.


User response: Verify the database properties andretry the operation.



FMX5357W The truncation of the transaction logfailed.

Explanation: The truncation of the transaction logfailed.


User response: Refer to other messages that aredisplayed to determine the problem.

FMX5358E A Microsoft Exchange API protocol errorhas occurred.

Explanation: An unrecoverable Microsoft ExchangeAPI protocol error has occurred.


User response: Contact your service representative.

FMX5359E Unable to get the TEMP environmentvariable. Ensure that the environmentvariable is set and retry the operation.

Explanation: An attempt was made to get the TEMPenvironment variable for this system. This attemptfailed.


User response: Ensure that the environment variableis set and retry the operation.

FMX5360E The /RECOVer=APPLYRESToredlogsoption is not allowed during a partialrestore.

Explanation: A partial restore was requested with the/RECOVer=APPLYRESToredlogs option. The/RECOVer=APPLYRESToredlogs option is not allowedduring a partial restore.


User response: Enter the command to restore theentire component or enter the command without the/RECOVer=APPLYRESToredlogs option.

FMX5361E It is invalid to have an '*' within adatabase name.

Explanation: An attempt was made to backup adatabase that contains an '*'. It is invalid to have an '*'in a database name.

System action: Processing continues, but this databasewill not be backed up.

User response: Rename the database, otherwise thisdatabase cannot be backed up.

FMX5362W The filespace <filespace> in an invalidfilespace name.

Explanation: The filespace displayed in the messageexists, but is an invalid filespace.

System action: Processing continues, but this filespacewill not be used.

User response: Ensure that the database name doesnot contain invalid characters. Refer to the MicrosoftExchange documentation for the list of invalidcharacters.

FMX5363W RecoveryAgentShell is either at anearlier level or not found. The VMbackup data restore cannot be issued.

Explanation: Warning: To issue the VM backup dataquery or restore, update the software. Please upgrade itto support this feature.

System action: The command is ignored andprocessing continues.

User response:

FMX5364W The license for the Recovery Agent, partof the Tivoli Storage Manager forVirtual Environments, is either not validor not found.

Explanation: Warning: Without a valid license for theRecovery Agent, you cannot use parts of Tivoli StorageManager for Databases: Data Protection for Exchange torecover Microsoft Exchange data from a VM backup.

System action: The software continues to run, but youcannot use Tivoli Storage Manager for Databases: DataProtection for Exchange to recover Microsoft Exchangedata from a VM backup.

User response: Verify that the correct license file is inthe correct directory. If you use the installation wizard,the license file should be saved to the correct directory.

FMX5365W Restoring from the VM backup isdisabled. Restore actions are usuallydisabled because of license issues orcode incompatibility issues.

Explanation: Warning: Until the problem is resolved,you can restore from the backups taken with DataProtection for Exchange.

System action: Until the root cause is identified andthe problem is resolved, the restore action isunavailable. After you fix the problem, a restart is notrequired.

User response: To identify the root cause, verify thatthe .lic file is in the correct path. If the .lic file is not theproblem, check the versions of the code. If the recoveryagent (client) code is not at the same level as the Data



Protection for VMware and Data Protection forExchange software, the restore action is disabled. Youcan upgrade the recovery agent and retry the restore.

FMX5500E The MultiByteToWideChar() functionfailed.



User response: Retry the operation.

FMX5501E The WideCharToMultiByte() functionfailed.




FMX5502E The restore destination directory pathneeds to be fully-qualified. Enter thecommand again and specify afully-qualified path for the /INTOoption.

Explanation: The /INTO option was specified withouta fully-qualified path.


User response: Enter the command again and specifya fully-qualified path for the /INTO option.

FMX5705W An error was encountered with TivoliStorage Manager API initialization, rc =returncode. Examine the dsierror.log formore information or determine if theTSM Client is installed properly.

Explanation: An attempt was made to run setup forthe Tivoli Storage Manager API. However, errors wereencountered. The API is a component of thebackup-archive client, which is also known as the VSSRequestor.


User response: Examine the dsierror.log file to findout more information about the problem. If this filedoes not exist, it is possible that the TSM API is notinstalled properly. If this is the case, uninstall the TSMClient and re-run the configuration wizard.

FMX5706I The logfile_name log file did not needpruning.

Explanation: The log file specified did not exceed themaximum log size and did not need to be pruned.

System action: The log file is not changed.

User response: The log file will automatically bepruned at a later date. If the log file is too large now,lower the number of days the log entries are retained.

FMX5798E MS Exchange API api name failed withHRESULT: api retcode. Check theWindows Application Event log formore details.

Explanation: A Microsoft Exchange API error occurredduring an operation. The specific API function thatfailed, along with the HRESULT code of the failure andpossible message associated with that error, isdisplayed.


User response: If the Windows Event Log does nothelp to resolve the problem, stop and restart theExchange Information Store and retry the operation.

FMX5800E The backup is corrupt. See log file foradditional information.

Explanation: When attempting to process an Exchangebackup on the Tivoli Storage Manager Server, not allrequired objects were present. The operation cannotproceed. The specific backup affected is logged.


User response: Retry the operation with a differentbackup.

FMX5805E The restore failed. The file alreadyexists. Delete the existing files orspecify a different restore (/INTO) path.

Explanation: The specified file already exists in therestore (/INTO) path. The RESTOREFILES command isdesigned not to overwrite existing files.

System action: The restore operation fails andprocessing ends.

User response: If you want to restore the specifiedfile, you must first delete the file that exists in therestore (/INTO) path and retry the operation or specifya different restore (/INTO) path and retry theoperation.

FMX5811E Invalid command. Data Protection forExchange invalid backup type for a VSSbackup request. Supported types arefull, copy, diff, and incr.

Explanation: An invalid backup type was specified onthe VSS backup request. Refer to your Data Protectionfor Exchange User's Guide for supported backup types.


User response: Retry the backup operation specifying



a supported VSS backup type. Supported types are full,copy, diff, and incr.

FMX5814E Invalid command. Data Protection forExchange does not support OFFLOADwith the combination specified forbackup destination and version ofWindows.

Explanation: The OFFLOAD option was specifiedwith an unsupported backup destination. DataProtection for Exchange only supports offload with abackup destination of TSM or if running on a WindowsSystem 2008 or later, backup destination LOCAL, TSMor BOTH.


User response: Retry the VSS offloaded backupoperation specifying a backup destination of TSM.

FMX5815E The VSS operation failed with rc =returncode. Check the dsmerror.log fileand the Windows Event log for moredetails. The VSS Provider logs mightalso contain more information.

Explanation: There was a failure when Data Protectionfor Exchange performed the VSS operation.


User response: Check the dsmerror.log file and theWindows Event log for more details. The VSS Providerlogs might also contain more information. If problemspersist, verify that the Client Acceptor Daemon (CAD)is installed, configured, and running properly on themachine. If necessary, uninstall the TSM Client andre-run the configuartion wizard to reinstall the ClientAcceptor Daemon.

FMX5816E Data Protection for Exchange is not ableto run VSS operations. You must berunning Exchange Server 2010 or later.

Explanation: In order to perform VSS operations, DataProtection for Exchange verifies that the ExchangeServer level is at least Exchange Server 2010.


User response: Verify that the prerequisites identifiedabove are met and retry the operation.

FMX5817E Missing, blank, or invalid LocalDSMAGENT Node Name is notallowed.

Explanation: To run VSS operations, Data Protectionfor Exchange verifies that the Local DSMAGENT NodeName is specified and valid. This error indicates thatthe Local DSMAGENT Node Name is missing, blank,or invalid.


User response: Set the Local DSMAGENT NodeName to a valid value and retry the operation.

FMX5818E Invalid command. Data Protection forExchange only supports restoring VSSbackup types of full, copy, diff, and incr.

Explanation: An invalid backup type was specified onthe VSS restore request. Data Protection for Exchangesupports restoring backups of type full, copy, diff, andincr.


User response: Retry the restore operation specifyinga supported VSS backup type.

FMX5819E Multiple backup objects were found forthe specified components and backupdestination. Use the /OBJECT= and/BACKUPDESTINATION= options toidentify which specific backup object torestore.

Explanation: The backup object specified for the VSSrestore operation was not specific enough to be unique.More information is required to restore the correctbackup object.


User response: Retry the restore operation specifyingthe /OBJECT= and /BACKUPDESTINATION=parameters.

FMX5820E There were no Exchange backups foundon the Tivoli Storage Manager servermatching the specified criteria.

Explanation: A query was issued to the Tivoli StorageManager server to find the Data Protection forExchange backups that match the specified searchcriteria. No backups were found.


User response: Retry the operation using differentcriteria.

FMX5821E The command is not valid. DataProtection for Exchange supportsrestoring the VMVSS FULL backuptype.

Explanation: When the VMVSS restore request isentered, an invalid backup type is specified. The FULLbackup type is supported with Data Protection forExchange restore backups.


User response: Start the restore operation after youspecify a supported VMVSS backup type.



FMX5839E Alternate or recovery database you arerestoring to does not exist.

Explanation: The alternate or recovery database thatwas specified does not exist on the Microsoft ExchangeServer.


User response: Verify that the target database existsand the database has been dismounted before retryingthe restore.

FMX5843I No backups were found for the database<database> that match the specificationsentered. Check that the database name,backup destination, and OBJECTparameters are correct.

Explanation: No backups found for the specifieddatabase that match specified backup destination orOBJECT (if any).


User response: Ensure that the database name isspelled correctly, backup destination and OBJECT (ifany) are specified correctly and enter the commandagain.

FMX5901E mapi32.dll does not exist. If necessary,reinstall the Microsoft MAPICDOdownload.

Explanation: The Messaging ApplicationProgramming Interface (MAPI) library mapi32.dll isrequired for mailbox restore operations.

System action: The mailbox restore operation fails.

User response: Verify that the mapi32.dll file isinstalled on the system. Run the command again.

FMX5902E mapi32.dll has version version.release.Expected expected version.expected releaseor higher. Download and install thelatest Microsoft MAPICDO downloadand retry the operation.

Explanation: The correct version of MessagingApplication Programming Interface (MAPI) librarymapi32.dll is required for mailbox restore operations.

System action: The mailbox restore operation hasfailed.

User response: Verify that the correct version ofmapi32.dll is installed on the system. Run thecommand again.

FMX5906E Loading the MAPI dynamic load libraryhas failed. If necessary, reinstall theMicrosoft MAPICDO download.

Explanation: The mapi32.dll is required for mailboxrestore operations.

System action: The mailbox restore operation fails.

User response: Verify that the mapi32.dll is installedon the system. Run the command again.

FMX5907E Initializing the MAPI subsystem failed.Verify that the mapi32.dll is installed onthe system and that MAPI is enabled foryour mailboxes.

Explanation: The MAPI subsystem is necessary formailbox restore operations.


User response: Verify that the mapi32.dll is installedon the system and that MAPI is enabled for yourmailboxes. Run the command again.

FMX5908E Creating the MAPI profile has failed.Ensure that you have OrganizationManagement privileges, and that youhave an active mailbox.

Explanation: MAPI requires a user with an activeExchange mailbox and Organization Managementprivileges to perform mailbox restore operations.


User response: Either log on as a user withOrganization Management privileges, or add an activemailbox for the current user.

FMX5909E The MAPI subsystem logon has failed.Check that you have an active mailboxand Organization Managementprivileges for this operation.

Explanation: Mailbox restore operations require a userwith Organization Management privileges, and anactive Exchange mailbox.


User response: Either log on as a user withOrganization Management privileges, or add an activemailbox for the current user.

FMX5910E Opening a MAPI mailbox has failed.

Explanation: Data Protection for Exchange attemptedto open a mailbox using MAPI, but the operationfailed. The MAPI mailbox was not opened.


User response: The following causes are some of the



more common causes of this error:

v Mailbox does not exist Resolution: Create thenecessary mailbox.

v Mailbox has never been sent to or logged in toResolution: Ensure that the mailbox is active bylogging in to it or by sending at least one message tothe mailbox.

v Mailbox database is not mounted Resolution: Verifythat the mailbox is mounted, and mount it if it isn'talready mounted.

v Insufficient privilege to access mailbox Resolution:Ensure that the administrative ID that you are usingto restore data has the correct privileges, and has anactive mailbox on the system. Microsoft Exchange2003 requires Exchange Administrators and LocalAdministrators permissions, and Microsoft Exchange2007 requires Exchange Organization Administrators,Local Administrators. Microsoft Exchange 2010requires Organization Management and LocalAdministrators permissions to resolve this issue.

v Exchange server where mailbox database is located isnot available or down Resolution: Verify that accessto Exchange Server using Exchange ManagementConsole (Exchange 2007) or Exchange SystemManager (Exchange 2003).

v Microsoft Information Store service is not runningResolution: Verify that Microsoft ExchangeInformation Store service is running throughcomputer management Services. Start the service if itis not running.

v Microsoft Exchange System Attendant service is notrunning Resolution: Verify that Microsoft ExchangeSystem Attendant service is running throughcomputer management Services. Start the service if itis not running.

FMX5911E The MAPI subsystem has experienced anetwork failure. Verify that you areaccessing the correct Exchange server,and that the Exchange server has theClient Access Role installed. Also checkthat the /CLIENTACCESSSERVERparameter is correct.

Explanation: Data Protection for Exchange tried toconnect to Exchange, but experienced a network failure.


User response: Verify that you are accessing thecorrect Exchange server, and that the Exchange serverhas the Client Access Role installed. Also check that the/CLIENTACCESSSERVER parameter is correct.

FMX5912E The MAPI subsystem has experienced afailure.

Explanation: The MAPI subsystem has experienced anunknown error.


User response: The problem is most likely a problemwith the configuration of the recovery user's mailbox orthe MAPI configuration on your system. Verify thatboth meet the requirements specified in your userdocumentation.

FMX5915W Unable to obtain the MicrosoftExchange Server version running onyour system. Microsoft Exchange 2010 isbeing assumed. Unexpected results mayoccur.

Explanation: An attempt was made to determine thelevel of Microsoft Exchange Server running on thecurrent system. This attempt failed.

System action: Processing continues. However,unexpected results may occur.

User response: If the operation fails or producesunexpected results, verify that Microsoft ExchangeServer is correctly installed on the system, and retry theoperation.

FMX5917I The mailbox history has beensuccessfully updated on the TSMServer.

Explanation: The mailbox location history stored onthe TSM Server was compared to the current mailboxlocation information in the Active Directory andupdated accordingly. This operation is performed tohelp facilitate individual mailbox restore operations.

System action: None

User response: None

FMX5918W The mailbox history did not updatesuccessfully on the TSM Server.

Explanation: An attempt was made to update themailbox location history stored on the TSM Server. Thisoperation is performed to help facilitate individualmailbox restore operations. Problems were encounteredduring the update attempt.

System action: The mailbox history is not updated,but processing continues.

User response: Verify the following:

v the Active Directory configuration

v the Data Protection for Exchange node username andpassword

v the proxynode configuration on the TSM Server

FMX5911E • FMX5918W


FMX5921E Data Protection for Exchange requires auser with Organization Managementprivileges. For mailbox restores, the usermust also have an active mailbox.

Explanation: Mailbox restore operations requires auser with Organization Management privileges, and anactive Exchange mailbox.

System action: Processing stops. No mailboxes arerestored.

User response: Either log on as a user with a mailboxthat has Organization Management privileges, or addan active mailbox for the current user.

FMX5922E The mailbox 'mailboxname' was notfound.

Explanation: The mailbox specified for the mailboxrestore operation or the destination mailbox was notfound in the Active Directory or in the mailbox historyinformation stored on the TSM Server.

System action: The specified mailbox is not restored.

User response: Verify that the specified mailbox nameis correct. Make sure that you are using the mailboxalias when specifying the mailbox name. Aftercorrecting the mailbox name, retry the mailbox restoreoperation. If this mailbox restore is for a deleted ormoved mailbox, you might retry the mailbox restoreoperation using the 'MAILBOXOriglocation' option.Also, make sure that the database is restored into therecovery database properly.

FMX5923E An unknown mailbox name wasspecified or the mailbox backup was notfound in the recovery database. Verifythat the mailbox name is correct. If thespecified mailbox name is correct, verifythat it has been successfully backed up.

Explanation: The mailboxes specified for the mailboxrestore operation were not found in the ActiveDirectory or in the mailbox history information storedon the TSM Server. If the specified mailboxes exist inActive Directory, then the database backup was notfound.

System action: The specified mailboxes are notrestored.

User response: Verify that the specified mailboxnames are correct. Make sure that you are using themailbox alias when specifying the mailbox names. Aftercorrecting the mailbox names, retry the mailbox restoreoperation. If this mailbox restore is for a deleted ormoved mailbox, you might retry the mailbox restoreoperation using the 'MAILBOXOriglocation' option.Also, make sure that the database is restored into therecovery database properly. If specified mailbox nameis correct, verify that it has been successfully backedup.

FMX5924E There were no usable backups found.

Explanation: The mailbox restore operation failedbecause no usable backups were found.

System action: No mailboxes are restored.

User response: Verify that you have specified thecorrect TCPServeraddress and node name, and retrythe operation.

FMX5929E The Microsoft Exchange Server MAPIClient and Collaboration Data Objects(MAPICDO) download is not installed.Download and install the latestMicrosoft MAPICDO from theMicrosoft website before runningmailbox restore operations.

Explanation: Microsoft Exchange Server MAPI Clientand Collaboration Data Objects (MAPICDO) downloadis required for mailbox restore operations.


User response: Verify that the Microsoft ExchangeServer MAPI Client and Collaboration Data Objects(MAPICDO) download is installed.

FMX5930E The requested MAPI message servicewas not found.

Explanation: The MAPI message service was notfound. This is most likely due to the service not beingdefined in your local MAPISVC.INF file.


User response: Verify that the requested MAPImessage service is defined in your local MAPISVC.INFfile. If this error resulted from trying to restore to aPersonal Folders (.pst) file, look for the section "MSPSTMS" in this file. If it is not defined, add the messageservice to your MAPISVC.INF file and run thecommand again.

FMX5932E The recovery database cannot be createdbecause the TEMP environment variableis set to an invalid directory.

Explanation: The TEMP environment variable is set toan invalid directory.


User response: Verify that the TEMP environmentvariable points to valid and accessible directory and tryagain.



FMX5935W The mailbox restore operationcompleted sucessfully; however not allof the mailbox items were restored. Runthe mailbox restore operation again onthe mailboxes that reported partialcompletion, or use mailbox filters torestore a smaller subset of messages.

Explanation: The mailbox restore operation has onlypartially completed. The messages that were restoredwere restored correctly, but some items were notrestored. This failure might be because there were toomany items to restore in one operation.


User response: Run the mailbox restore operationagain on the mailboxes that reported partialcompletion, or use mailbox filters to restore a smallersubset of messages.

FMX5948E An attempt to query detailed managedcapacacity failed.

Explanation:

System action:

User response:

FMX5972T TDPEXCC RESTOREMailboxmailbox-name[,mailbox-name2,mailbox-name3,...] where mailbox-name can be:an alias or display name[/CLIENTACcessserver=client-access-server-name] (default: local ClientAccess Server)[/CONFIGfile=tdpexc.cfg|filename](default: tdpexc.cfg)[/DAGNODe=nodename][/FCMOPTFile=dsm.opt|filename](default: dsm.opt) [/FROMArchive][/KEEPRdb=Yes|No] (default: No)[/LOGFile=tdpexc.log|logfilename](default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)

FMX5975E A valid FlashCopy Manager license filecould not be located. Data protectionoperations to a FlashCopy Managervirtual server are not allowed.

Explanation: To perform data protection operations toa FlashCopy Manager virtual server, a valid license forFlashCopy Manager must be installed in the FlashCopyManager installation directory. This license file isnamed fcmclient.lic.


User response: Verify that the fcmclient.lic file isinstalled and retry the operation.

FMX5976E A valid Data Protection for Exchangelicense file could not be located. DataProtection for Exchange is not licensedto run data protection operations to aTivoli Storage Manager server. With thecurrent licenses only data protectionoperations to a FlashCopy Managerstand-alone server can be run. Use theconfiguration wizard to install or locatethe proper license.

Explanation: To perform data protection operations toa Tivoli Storage Manager server, a valid license forData Protection for Exchange (called excclient.lic) mustbe installed. The Data Protection for Exchange licenseshould be installed in the Data Protection for Exchangeinstallation directory.


User response: Use the configuration wizard to installor locate the proper license.

FMX5977E The /BACKUPDESTINATIONparameter cannot be 'TSM' whenperforming data protection operationsusing a FlashCopy Manager stand-aloneserver.

Explanation: Data protection commands default to/BACKUPDESTINATION=LOCAL when performedagainst a FlashCopy Manager stand-alone server. TheFlashCopy Manager supports no other values for theseparameters. It is not necessary to specify thisparameter.


User response: Retry the command removing the/BACKUPDESTINATION parameter.

FMX5983E The MAPI subsystem has experienced afailure. There are not enough systemresources to complete the selectedoperation.

Explanation: There are not enough system resourcesto complete the selected operation. The WindowsApplication Event log may contain more information.


User response: Ensure there are sufficient systemresources and run the command again.

FMX5986I Database <component> has circularlogging enabled. Cannot performincremental or differential backup -skipping.

Explanation: The database that was specified by theuser has circular logging enabled. Incremental ordifferential backup is not possible.

FMX5935W • FMX5986I



User response: Ensure that the database specifieddoes not have circluar logging enabled and run thecommand again if you want to perform incremental ordifferential backups.

FMX5987E The TSMRDB recovery failed to returndatabase to a consistent state because ofthe following error:<Error message>

Explanation: The recovery database is not in a cleanshutdown state because of a file access error.

System action: The restore operation is stopped.Resolve the file access error before retrying the restoreoperation.

User response: When resolving this problem, do notdelete or change any files or directories created byTivoli Storage Manager software. Attempt to access thefiles and directories referred to in this message. Checkthe setting for the TSMMOUNT environment variable.If you update the value to correct a problem, restart thesystem to ensure that all Tivoli Storage Managerservices are accessing the updated setting.

FMX5988W Recovery agent CLI cannot dismountVMVSS mount points:<Mount point>

Explanation: To debug the problem that caused thedismount failure, see the DSMERROR.LOG file. Theproduct documentation also provides details that canhelp resolve the problem.

System action: The restore operation continues, butthe VMVSS mount point remains on the system. Untilthe mount point is deleted, the subsequent recoveryattempts will fail.

User response: Use one of the following recoveryagent CLI commands to manually dismount theVMVSS mount point. Before executing the command,close any open files or directories on the mountedVMVSS mount point. If the recovery database exists onVMVSS mount point, dismount and remove thedatabase manually. (You can use the Exchangemanagement shell commands to complete this task.)Sample recovery agent CLI commands to manuallydismount the VMVSS mount point:RecoveryAgentShell.exe -c mount del -target everythingRecoveryAgentShell.exe -c mount del -target'your_mount_point'

FMX5994E Data Protection for Exchange is onlylicensed to run data protectionoperations to a Tivoli Storage Managerserver. It is not licensed to back upusing locally managed snapshots.

Explanation: To back up using locally managedsnapshots, a valid FlashCopy Manager license isrequired.


User response: Change the backup destination tobackup to a Tivoli Storage Manager server or obtain theproducts or licenses necessary to enable this feature

FMX6012W The database; database has not beenfound on the Exchange Server. Thedatabase files will be restored. After therestore completes, you can recreate thedatabase on the Exchange Server fromthe restored files.

Explanation: The database has not been found on theExchange Server. The restore will continue to allow VSSwriter to restore the database files.

System action: The restore operation continues, butonly the files are restored.

User response: After the restore completes, you canrecreate the database on the Exchange Server from therestored files.

FMX6027E mapi32.dll has build version build version.Expected expected build version or higher.

Explanation: The correct build version of MessagingApplication Programming Interface library mapi32.dllis required for mailbox restore operations.


User response: Verify that the correct build version ofmapi32.dll is installed on the system. Run thecommand again.

FMX6028W <database name> is a DAG passivedatabase not in Healthy state --skipping.

Explanation: A request was made to back up aDatabase Availability Group (DAG) passive database.The DAG passive database is not in a Healthy state. Inorder to back up a DAG passive database, it must be ina Healthy state.

System action: Processing continues, but the specifieddatabase is skipped.

User response: Ensure that the DAG passive databaseis in a Healthy state and retry the backup operation.

FMX6029W At least one item that has passivedatabase copies was specified forrestore. When restoring this type ofdatabase, care must be taken inhandling the database copies. Consultthe Data Protection for Exchangedocumentation for details.

Explanation: When restoring a Database AvailabiltyGroup (DAG) database, additional steps must be taken



in order to suspend the database copy and update thedatabase copy prior to bringing it online.


User response: Consult the Data Protection forExchange or Microsoft documentation for details.

FMX6030W At least one item that has passivedatabase copies was specified forrestore. When restoring this type ofdatabase, care must be taken inhandling the database copies. If youhave not prepared the passive databasecopies for restore or are unsure of thenecessary steps, please consult the DataProtection for Exchange documentationfor details. Do you want to continuewith the restore operation?

Explanation: When restoring a Database AvailabiltyGroup (DAG) database, additional steps must be takenin order to suspend the database copy and update thedatabase copy prior to bringing it online.


User response: Consult the Data Protection forExchange or Microsoft documentation for details.

FMX6031I Excluding <databaseType> database<databaseName> from backup list becauseof option <optionName>-- skipping.

Explanation: A backup command has been issuedwhere the option /EXCLUDENONDAGDbs,/EXCLUDEDAGACTive, /EXCLUDEDAGPASsive,/MINimumbackupinterval or /PREFERDAGPASsivehas been specifed. The database has met the excludeoption criteria and is skipped from backup.



FMX6032E Cannot create the recovery databasebecause there is an existing recoverydatabase recovery database name on theExchange Server.

Explanation: Data Protection for Exchange cannotcreate the recovery database because there already is anexisting recovery database on the Exchange Server.


User response: Remove the existing recovery databasefrom the Exchange Server. Run the command again.

FMX6033E The option /MOUNTDAtabases=yeswas specified without /RECOver option.

Explanation: A restore command has been issuedwhere the option /MOUNTDAtabases=yes but theoption /RECOver was not specified. This is an invalidcombination.

System action: Processing Stops

User response: Issue a restore command without/MOUNTDAtabases=yes if you do not intent to applylogs.

FMX6038I Excluding storage group <databaseName>from backup list -- skipping.

Explanation: A backup command has been issuedwhere the option /EXCLUDESG has been specifed. Thestorage group has met the exclude option criteria andwill be skipped from backup.

System action: Processing continues, but the specifiedstorage group is skipped.


FMX6039E An error has occurred while mountingor dismounting a database.

Explanation: An error was detected while mountingor dismounting a database.

System action: Errors were detected while mountingor dismounting a database.

User response: Please check the Windows Event Logfor any Exchange errors. If this was a mount problemduring a restore, please verify the correct /RECOVeroption value was used, and the correct sequence of theExchange transaction logs. Please resolve any problems,and retry the operation. If the errors persist, contactyour service representative.

FMX6040W Component <component> requires a fullbackup. Data Protection for Exchangecan not perform an incremental ordifferential backup - skipping.

Explanation: The component that was specified by theuser requires a full backup. An incremental ordifferential backup is not allowed until a full backup isperformed. This situation can occur if a new storagegroup or database has been added and a full backuphas not yet been performed.

System action: This component is skipped.

User response: Perform a full backup on the specifiedcomponent as soon as possible.



FMX6055W Excluded item <databaseName> is notvalid. It will be ignored.

Explanation: A backup command was issued witheither the /EXCLUDESG or /EXCLUDEDB option. Anitem specified in the exclude statement is not a validitem. It will be ignored.

System action: A warning is displayed and processingcontinues.

User response: Correct the invalid item specified onthe exclude option for future operations.

FMX6065E The mount backup command failed.Verify that a valid mount point andbackup is specified. For moreinformation, see the dsmerror.log file.

Explanation: The mount backup command failed. Thebackup specified might be mounted. In addition, thedrive to map to might be in use. The directory tocontain the mount point directories for all snapshotsneeds to be an empty NTFS directory that does notcontain hidden system files or directories.


User response: Check to make sure that the backupspecified is not mounted and that the drive to map tois available. Repeat the command using an emptyNTFS directory as the snapshots mount pointsdirectory.

FMX6066E The UNMOUNT BACKup commandfailed. The specified backup might notbe mounted. For more information, seethe dsmerror.log file.

Explanation: The UNMOUNT BACKup commandfailed. The specified backup might not be mounted, orthere may be a different error.


User response: Check to make sure that the backupspecified is mounted. If so, see the dsmerror.log fileand take the appropriate action.

FMX6067E In the component list that is specified,the following object is not valid: 'object'.Verify the volume and mount pointnames are correctly identified andspelled correctly.

Explanation: The command that is entered includes acomponent list. The list of components contains one ormore invalid objects. For example, when entering aBACKUP or RESTORE command, if the component listincludes a volume or mount point that is not valid or isnot eligible for back up, this message is displayed. Inaddition, the GUID volume name cannot be specified.For RESTORE, MOUNT BACKUP, or DELETEBACKUP commands, this message is displayed if the

component list contains a backup specification that isnot found in the backup inventory.


User response: Verify the correct syntax is used whenentering the command. If the message is displayedagain, verify the volume and mount point names arecorrectly identified. A misspelling can trigger thismessage.

FMX6068I <databaseName> is being backed up by adifferent server -- skipping.

Explanation: A Database Availability Group (DAG)database is skipped from backup if another copy of thesame database is being backed up by a different server.


User response: Check whether the database is beingbacked up by a different server. Also check that there isnot another instance of tdpexcc.exe or other backuprunning.

FMX6076I <databaseName> cannot be backed upbecause its 'BackupInProgress' flag is setto 'True'. Check whether the database isbeing backed up by a different server --skipping.

Explanation: A Database Availability Group (DAG)database is skipped from backup if its'BackupInProgress' flag is set to "True" by Exchangeserver.


User response: Check whether the database is beingbacked up by a different server. Also check that there isnot another instance of tdpexcc.exe or other backuprunning.

FMX6080E Conflict option:

Explanation: This message displays the command thatwas entered, up to and including the conflict optionthat was detected.



FMX6081E Missing, blank, or invalidREMOTEDSMAgentnode is notallowed. Set theREMOTEDSMAgentnode option to avalid value and retry the operation.

Explanation: In order to run VSS operations, DataProtection for Exchange verifies that the Remote

FMX6055W • FMX6081E


DSMAGENT Node Name is specified and valid. Thiserror indicates that the Remote DSMAGENT NodeName is missing or blank. Also, the RemoteDSMAGENT Node Name cannot be the same as theLocal DSM Agent Node Name.


User response: Set the REMOTEDSMAgentnode to avalid value and retry the operation.

FMX6082I The following options are deprecatedand will be ignored: deprecatedOption

Explanation: The option you entered is deprecated.Data Protection for Exchange ignores the option andprocessing continues.

System action: Data Protection for Exchange ignoresthe option and processing continues.

User response: If appropriate, update your scripts toremove references to any deprecated options.

FMX6083W Database <component name> is a recoverydatabase -- skipping.

Explanation: A request was made to back up a set ofdatabases. However, some databases are recoverydatabases. Recovery databases cannot be backed up.

System action: Processing continues, but the recoverydatabases are skipped.

User response: Do not specify recovery databases tobe backed up.

FMX6086W The following values for themailboxfilter option are not supportedand the options are ignored:unsupportedfilter

Explanation: The mailboxfilter option entered is notsupported. Data Protection for Exchange ignores thefilter and processing continues.

System action: Data Protection for Exchange ignoresthe filter and processing continues.

User response: Provide supported value formailboxfilter option

FMX6087E The mailbox 'mailboxname' is ambiguous,multiple mailboxes were found.

Explanation: Multiple mailboxes are found for thespecified display name or alias.


User response: Specify mailbox GUID for restore andtry the operation again.

FMX6088W DP attempted to delete the temporaryfolder 'foldername' from temporarymailbox, but the operation was onlypartially successful. The remainingfolder contents must be deletedmanually.

Explanation: DP uses a temporary mail folder toperform some mailbox restore operations. After theoperation completed, DP attempted to delete thetemporary folder, but the operation only partiallycompleted. This partial failure may be due to the sizeof the mailbox. The MAPI operation deleteFolderreturned MAPI_W_PARTIAL_COMPLETION.

System action: The temporary folder is partiallyremoved, and processing continues.

User response: Manually delete the temporary folder.

FMX6091W The mailbox 'mailboxname' was notfound in the existing recovery database

Explanation: The parameter USEExistingrdb is set toYES, but the mailboxes that were specified for themailbox restore operation are not found in the existingrecovery database.


User response: Verify that the specified mailbox nameis in existing recovery database.

FMX6092W An mailbox name which was not foundin the existing recovery database. Verifythat the mailbox name is correct. If thespecified mailbox name is correct, verifythat it has been in existing recoverydatabase.

Explanation: The mailboxes specified for the mailboxrestore operation were not found in existing recoverydatabase.


User response: Verify that the specified mailbox nameis in existing recovery database.

FMX6093T Recovery database recovery database nameexists on the Exchange Server...

Explanation: The /USEEXISTINGRDB value is YES.Restore the mailbox using the existing recoverydatabase .


User response: no action needed.

FMX6082I • FMX6093T


FMX6094E The option KEEPRdb is set to Yes, butthe mailboxes are not in the samedatabase.

Explanation: The option KEEPRdb is set to Yes, butthe mailboxes are not in the same database.


User response: View any other messages that weredisplayed. Fix any of the problems indicated and enterthe command again.

FMX6095T There is no existing recovery databasefound...

Explanation: The /USEEXISTINGRDB value is YES.but no existing recovery database found.



FMX6096T Existing recovery database recoverydatabase name is being removed...

Explanation: The /USEEXISTINGRDB value is NO.Remove the existing recovery database .



FMX6098E The restore destination is not valid forthe public folder mailbox mailboxname.The mailbox is bypassed during restoreprocessing.

Explanation: The public folder mailbox must berestored to a public folder mailbox that is online on theExchange Server. The public folder must be restored toan existing online public folder. And the online publicfolder must have the same folder path as the publicfolder to be restored. If you specify theMAILBOXRESTOREDESTination option when yourestore a public folder mailbox, you must specify anonline public folder mailbox as the target mailboxname, and do not specify a target folder name.

System action: Restore processing continues, but themailbox is bypassed.

User response: Set theMAILBOXRESTOREDESTination to a valid value andretry the operation.

FMX6099W The value for the mailboxfilter option isnot supported for the public foldermailbox and the option is ignored:unsupportedfilter

Explanation: The mailboxfilter option that you enteredis not supported for the public folder mailbox. Data

Protection for Exchange ignores the filter andprocessing continues.


User response: Provide a supported value for themailboxfilter option

FMX6100E The archive mailbox 'mailboxname' wasnot found.

Explanation: The archive mailbox specified for themailbox restore operation was not found in the ActiveDirectory or in the mailbox history information storedon the TSM Server.

System action: The specified archive mailbox is notrestored.

User response: Verify that the specified mailbox nameis correct. Make sure that you are using the mailboxalias when specifying the mailbox name. Aftercorrecting the mailbox name, retry the mailbox restoreoperation. Also, make sure that the database is restoredinto the recovery database properly.

FMX6101W The value for the mailboxfilter option isnot supported for the archive mailboxand the option is ignored:unsupportedfilter

Explanation: The mailboxfilter option that you enteredis not supported for the archive mailbox. DataProtection for Exchange ignores the filter andprocessing continues.


User response: Provide a supported value for themailboxfilter option

FMX6102E Archive mailbox GUID 'mailboxname' isnot valid as input if /FROMArchive isspecified, or as mailbox restoredestination.

Explanation: Archive mailbox GUID is not valid asinput if /FROMArchive is specified, or as mailboxrestore destination.


User response: Specify the primary mailbox GUID asinput.

FMX6103W A mailbox was not found in therecovery database. Verify that mailbox isvalid and logon at least once.

Explanation: The mailboxes specified for the mailboxrestore operation were not found in recovery database.




User response: Verify that the specified mailbox nameis valid and logon at least once.


Chapter 5. FMY messages

Messages with prefix FMY are issued by the IBM Tivoli Storage FlashCopyManager for Microsoft SQL Server. Tivoli Storage FlashCopy Manager V4.1.2 FMYmessages are listed in ascending numerical order. The complete message isdocumented, including message ID, message text, explanation, system action, anduser response.

FMY0003S An internal processing error hasoccurred.




FMY0004E An unknown error has been detected.




FMY0005E Out of memory. Stop other processesand try the operation again.




FMY0053E License file (licensefile) could not beopened.




FMY0054E Read failure on license file (licensefile).




FMY0055E Write failure on license file (licensefile).




FMY0056E Data in the license file (licensefile) is notin a valid format.




FMY0057E The checksum in the license file(licensefile) does not match the licensestring text.




FMY0058E The 'Try and Buy' license has expired.




FMY0100E Incomplete command:





FMY0101E Invalid argument:




FMY0102E Invalid command:




FMY0103E Invalid option for the specifiedcommand:




FMY0104E Invalid option:




FMY0105E Missing argument:




FMY0132W Tracing could not be started. Processingwill continue.



User response: Refer to the other messages thatdisplay with this message to determine the problem.

FMY0133W Could not locate installation directory.Attempting to continue...




FMY0134W Could not locate log directory.Processing will continue...




FMY0150I Operation canceled by user.

Explanation: The user has requested that the DataProtection for Microsoft SQL Server application clientend by entering ctrl-C.


User response: None

FMY0151E Errors occurred while processing therequest.




FMY0152I Performance stats: seconds seconds spentin apicall API calls



User response: None

FMY0101E • FMY0152I


FMY0153I Performance stats: seconds seconds spentin function



User response: None

FMY0154E The Data Protection for Microsoft SQLServer application client cannot workwith the version of the Tivoli StorageManager API you have installed. Pleaseinstall version version.release.level orgreater.

Explanation: The version of the Tivoli StorageManager API currently installed on the system is olderthan the version used to build the Data Protection forMicrosoft SQL Server application client.


User response: Install a version of the Tivoli StorageManager API at or later than the indicated level. Acopy is distributed with the Data Protection forMicrosoft SQL Server application client.

FMY0155E The Data Protection for Microsoft SQLServer application client cannot workwith the release of Tivoli StorageManager API you have installed. Pleaseinstall release version.release.l evel orgreater.

Explanation: The release of the Tivoli StorageManager API currently installed on the system is olderthan the release used to build the Data Protection forMicrosoft SQL Server application client.


User response: Install a release of the Tivoli StorageManager API at or later than the indicated level. Acopy is distributed with the Data Protection forMicrosoft SQL Server application client.

FMY0156E Could not load the Tivoli StorageManager API.



User response: Ensure the Tivoli Storage Manager APIis correctly installed. Run the Data Protection forMicrosoft SQL Server application client with the/TRACEFLAGS=API /TRACEFILE=filename optionsand view the tracefile to determine why it could not beloaded. Another possible cause is that the TSMAPI.DLLdoes not exist in the system directory. Re-install theTivoli Storage Manager API, if this is the case.

FMY0160E An authentication error occurred withyour stored Tivoli Storage Managerpassword.

Explanation: You were unable to log on to the TivoliStorage Manager server due an authentication error.


User response: The stored Tivoli Storage Managerpassword may have become corrupted. Contact yourTivoli Storage Manager server administrator.

FMY0161E Authentication error. The passwordentered is not valid. You are not loggedon to the Tivoli Storage Manager server.



User response: Enter the correct Tivoli StorageManager password and try again.

FMY0162E The passwords entered do not match.Please enter them again.




FMY0163E The directory path needs to befully-qualified.




FMY0167E The fully-qualified file name is toolong.



User response: None

FMY0200E File (filename) could not be opened forreading.



User response: None

FMY0153I • FMY0200E

Chapter 5. FMY messages 237

FMY0201E File (filename) could not be opened forwriting.



User response: None

FMY0202E Read failure on file (filename).



User response: None

FMY0203E Write failure on file (filename).



User response: None

FMY0204E File (filename) could not be closed.



User response: None

FMY0205E File (filename) statistics could not beobtained.



User response: None

FMY0206E Directory (directory) could not be created.



User response: None

FMY0207E Directory path (directorypath) is too long.



User response: None

FMY0208E There is not enough disk space for theoperation attempted.



User response: None

FMY0209E The rename of file (filename1) to(filename2) failed.



User response: None

FMY0210E The Tivoli Storage Manager high levelqualifier is too long.

Explanation: An attempt was made to use a TivoliStorage Manager high level qualifier that was too long.This attempt failed.


User response: None

FMY0211E The Tivoli Storage Manager low levelqualifier is too long.

Explanation: An attempt was made to use a TivoliStorage Manager low level qualifier that was too long.This attempt failed.


User response: None

FMY0212E The Tivoli Storage Manager filespacename is too long.

Explanation: An attempt was made to use a TivoliStorage Manager filespace name that was too long. Thisattempt failed.


User response: None

FMY0213E The maximum number of objectsallowed per Tivoli Storage Managertransaction is too small.

Explanation: In order to maintain backup dataintegrity, multiple backup objects are sent to the TivoliStorage Manager server in a single transaction. TheTivoli Storage Manager server has indicated that themaximum number of objects allowed per transaction isless than the minimum required by the Data Protectionfor Microsoft SQL Server application client.


FMY0201E • FMY0213E


User response: Increase the maximum number ofobjects allowed per transaction on the Tivoli StorageManager server and retry the operation.

FMY0214E The backup object's management classbackup copy group does not exist.

Explanation: The Tivoli Storage Manager server hasindicated that the backup object's management classbackup copy group does not exist.



FMY0215E All backup objects do not have the samemanagement class backup copydestination.

Explanation: In order to maintain backup dataintegrity, multiple backup objects are sent to the TivoliStorage Manager server within a single transaction. Allbackup objects within a single transaction are requiredto have the same management class backup copydestinations.



FMY0216E Unable to obtain space information forvolume (volumename).



User response: None

FMY0217E The Tivoli Storage Manager filespacename is invalid.




FMY0218E The Tivoli Storage Manager high levelqualifier is invalid.




FMY0219E The Tivoli Storage Manager low levelqualifier is invalid.




FMY0256E The password in your Tivoli StorageManager options file has expired. Pleasechange your password on the TivoliStorage Manager server using the'change password' command and theneither change or remove the passwordvalue in your options file.

Explanation: Your Tivoli Storage Manager passwordhas expired. You need to change your password.


User response: Obtain a new password for your TivoliStorage Manager server; node using the changepassword command or by asking your Tivoli StorageManager Administrator to change your password.

FMY0257E Your password has expired.

Explanation: Your Tivoli Storage Manager passwordhas expired. A new password needs to be obtained.


User response: Obtain a new password for your TivoliStorage Manager node using the change passwordcommand or by asking your Tivoli Storage ManagerAdministrator to change your password.

FMY0258E You did not enter a valid password.Processing ends.




FMY0259E The password you entered forverification does not match thepassword you entered for your newpassword. Your password will not bechanged.






FMY0260I Password successfully changed.



User response: None

FMY0261I There are no backups for the servernamed servername.

Explanation: There are no backups on the TivoliStorage Manager server for the specified server name.


User response: None

FMY0262E Errors occurred while processing theVSS operation. Examine the WindowsEvent Logs and DSMERROR.LOG foradditional details.



User response: Attempt to determine the source of theerror by examining the Data Protection for SQL log file,the TSM Client error log file (DSMERROR.LOG), theWindows Application Event Log, the Windows SystemEvent Log, and the VSS provider log file, if applicable.Additional instructions for Windows VSS operationsare located in the TSM Problem Determination Guide.Correct the problem and retry the operation. If thiserror persists, contact your service representative.

FMY0263E Failed to start Web browser with areturn code of returncode.

Explanation: An attempt was made to start the webbrowser to view the TSM HTML b ook. This attemptfailed.



FMY0264I Could not find the default browserdefined. An attempt will be made to useMicrosoft Internet Explorer.




FMY0265E Could not find Internet Explorer.




FMY0266E Could not find the Tivoli StorageManager HTML books.




FMY0267E The verify password entered does notmatch the new password entered.




FMY0292E An unknown error has been detected. rc= rc




FMY0300E Invalid restore type.




FMY0301E Invalid backup type.






FMY0351E Invalid trace keyword - 'keyword'




FMY0357E Unable to open trace output filefile-name.




FMY0366E Unable to close trace output filefile-name.




FMY0367E Unable to write to trace file tracefile.Tracing disabled.




FMY0368E Invalid trace file name (name too long).




FMY0383E Specifying the trace file 'link' as asymbolic link is not allowed.




FMY0384E Symbolic link 'linkname' to 'target' wassuccessfully deleted.




FMY0385E Unable to delete symbolic link 'link'.




FMY0476E program-name: cannot open file file-spec:error.

Explanation: DP cannot open the file.

System action: DP cannot complete the requestedoperation.


FMY0487E Specifying the error log 'link' as asymbolic link is not allowed.




FMY0488E Initialization functions cannot open theerror log: log-name. errno = errno-value,

Explanation: The file log-name could not be openedduring initialization. The system set the error codeerrno-value. If the reason given is "access denied," the



current user does not have permission to write to thelog in the directory specified. It is also possible that nospace is available at the given log location.



FMY0495E Failure writing to a Tivoli StorageManager log or log-related file: file-name,errno = errno-value, reason




FMY0496I DP is converting the log-file fromcontinuous (pruning) mode to wrappingmode. This process may take severalminutes.




FMY0497I DP is converting the log-file fromwrapping mode to continuous (pruning)mode. This process may take severalminutes.




FMY0498I count log records processed.




FMY0501E Invalid Proxy Configuration Detected:Target Node 'targetnode' is not listed as avalid node to proxy to for Node Name'nodename'.

Explanation: The proxy node configuration on theTSM Server is not correct to support this VSSoperation.


User response: Contact the TSM Server administratorto have the correct TSM Server GRANT PROXYcommands issued to enable proxy authority for thenodes. If the error persists, contact your servicerepresentative.

FMY0515E Invalid DSMAGENT Nodeconfiguration found for node'dsmagentnode'.




FMY0516I The Windows console event handlerreceived a 'event' console event.

Explanation: A console event was received by one ofthe Data Protection for Microsoft SQL Server processesor programs. The following events can be recevied:




FMY0517I An unexpected error was encountered.DP function name : function-name DPfunction : function-desc DP return code :TSM-rc DP file : file-name (line-number)

Explanation: None.


User response: Contact the DP administrator with theinformation provided in this message.



FMY0518E Backups selected for restore must havethe same backup location (TSM orLOCAL).




FMY0519E The VSS operation failed with rc =returncode.

Explanation: There was a failure when TSMperformed the VSS operation.


User response: Verify that the TSM Client AcceptorDaemon (CAD) is installed, configured, and runningproperly on the machine. Retry the operation. If theerror persists, contact your service representative.

FMY0520E Failed to connect to Local DSMAGENTNode 'localdsmagentnode' at address:port'address:portnumber'. Verify that the TSMClient Acceptor Daemon (CAD) isinstalled, configured, and runningproperly.




FMY0521E Pruning functions cannot open one ofthe Tivoli Storage Manager prune files:log-name. errno = errno-value,

Explanation: The file "log-name" could not be openedduring pruning. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thefile in the directory specified. It is also possible that nospace is available at the given file location or anotherTivoli Storager Manager process started by different

user id is performing pruning at the same time.



FMY0522E DIAG:




FMY0524S Error 'errtxt' (errno=errno) occurredtrying to write to audit log 'file-name'.The audit log function is disabled.




FMY0555E Invalid number of snapshots:

Explanation:



FMY0556E Invalid number of days:

Explanation:



FMY0571E The specified policy was not found:'policy'

Explanation:

System action:




FMY0572E The specified policy already exists:'policy'

Explanation:



FMY0573E The specified policy could not beupdated: 'policy'


System action:


FMY0574E The specified policy could not bedeleted: 'policy'


System action:


FMY0575E The specified policy could not becreated: 'policy'


System action:


FMY0576I There were no items found.




FMY0581E Volume volume-name could not belocked.



User response: Please verify that no other applicationis accessing the volume. During restore of an image DPmust have exclusive use of the volume.

FMY0583E Invalid name of policy specified. Validinput characters include alphanumericcharaters and underscore.

Explanation:



FMY0585E Unable to connect to the TSM ClientAcceptor Daemon (CAD).

Explanation: Possible causes of this message include:The TSM Client Acceptor Daemon (CAD) is notrunning. The VSSALTSTAGINGDIR option setting inthe TDP option file is not set to the same value as theVSSALTSTAGINGDIR option setting in the DataProtection for Microsoft SQL Server Remote ClientAgent Service (DSMAGENT) option file. They must beset to the same value for successful TDP operations.


User response: Ensure that the TSM Client AcceptorDaemon (CAD) is running. Ensure that theVSSALTSTAGINGDIR option setting in the TDP optionfile is set to the same value as theVSSALTSTAGINGDIR option setting in the DataProtection for Microsoft SQL Server Remote ClientAgent Service (DSMAGENT) option file. Aftercorrecting the VSSALTSTAGINGDIR optioninconsistency, retry the TDP operation.

FMY0588E The value for the BACKUPDESTinationoption is not allowed. Data Protectionfor Microsoft SQL Server is onlylicensed to run data protectionoperations to a Tivoli Storage Managerserver. It is not licensed to backup or torestore locally managed snapshots.

Explanation: The value for the configuration option isnot allowed. The only allowed value is TSM. DataProtection for Microsoft SQL Server is only licensed torun data protection operations to a Tivoli StorageManager server. It is not licensed to backup or torestore locally managed snapshots.


User response: Set the backup destination to TSM. Inorder to create and restore local VSS backups it isrequired to use and install a fully-featured valid licenseor to purchase an upgrade, and install Tivoli StorageFlashCopy Manager.

FMY0589E You are not allowed to setREMOTEDSMAGentnode option. DataProtection for Microsoft SQL Server isnot licensed to perform offloaded VSSbackups.

Explanation: The REMOTEDSMAGentnode option is



used to perform offloaded VSS backups.



FMY0590E A Data Protection communication errorwith the Tivoli Storage Manager serverhas occurred.




FMY0591I Data Protection communications withthe Tivoli Storage Manager server hasbeen successfully recovered.




FMY0592E The Data Protection TCP/IP sessionwith the Tivoli Storage Manager serverwas canceled.




FMY0593E Data Protection for Microsoft SQLServer is not licensed to performoffloaded VSS backups.




FMY0594E You cannot perform offloaded VSSbackups in TSM Server independentenvironment.



User response: In order to perform offloaded VSSbackups you have to configure Tivoli StorageFlashCopy Manager to manage snapshot backups usinga Tivoli Storage Manager server. To do this you can useTivoli Storage Manager configuration wizard.

FMY0595E The options file 'optfile' does not exist. Itis required for proper operation.



User response: Make sure to complete Tivoli StorageManager configuration and try the operation again.

FMY0598E The application cannot run in safemode.




FMY0599E The application cannot establish aremote powershell connection.




FMY0601E There is a problem that causesprocessing to stop. To identify thesource of the problem and the solution,look for details in the service level tracefile.

Explanation: This problem occurs when either thelocal or remote Powershell cmdlet or script reports anerror. Details about the error are not available untilmore trace file information is analyzed.





FMY0602E While attempting to communicate withthe remote client, a version checkreveals that the versions do not match.




FMY3000I Data Protection for SQL: Starting backuptype backup of database database namefrom server server name.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whena backup is started.

System action: None

User response: None Centrally logged

FMY3001I Data Protection for SQL: backup typebackup of database database name fromserver server name completedsuccessfully.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whena database backup completes successfully.

System action: None


FMY3002E Data Protection for SQL: backup typebackup of database database name fromserver server name failed, rc = return code.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whena database restore fails.

System action: None


FMY3003I Data Protection for SQL: Starting restoretype restore of backup object object nameto database database name on server servername.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whena restore is started.

System action: None


FMY3004I Data Protection for SQL: restore typerestore of backup object object name todatabase database name on server servername completed successfully.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whena database restore completes successfully.

System action: None


FMY3005E Data Protection for SQL: restore typerestore of backup object object name todatabase database name on server servername failed.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whena database restore fails.

System action: None


FMY3006I Data Protection for SQL: Startingbackup for server server name.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logindicating the start of a backup.

System action: None


FMY3007I Data Protection for SQL: Backup ofserver servername is complete. Total SQLbackups selected: number selected TotalSQL backups attempted: numberattempted Total SQL backups completed:number completed Total SQL backupsexcluded: number excluded Throughputrate: rate Kb/Sec Total bytes transferred:bytes Elapsed processing time: time Secs

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logindicating the end of a backup request.

System action: None




FMY3008I Data Protection for SQL: Backup ofserver servername is complete. Total SQLbackups selected: number selected TotalSQL backups attempted: numberattempted Total SQL backups completed:number completed Total SQL backupsexcluded: number excluded Total SQLbackups inactivated: number inactivatedThroughput rate: rate Kb/Sec Total bytestransferred: bytes Elapsed processingtime: time Secs


System action: None


FMY3009I Data Protection for SQL: backup typebackup of database database name fromserver server name canceled by user.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logindicating that a backup request was canceled by theuser.

System action: None


FMY3010I Data Protection for SQL: Starting restorefor server servername.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logindicating the start of a restore.

System action: None


FMY3011I Data Protection for SQL: Restore fromserver server name to server server name iscomplete. Total database backupsinspected: number inspected Totaldatabase backups requested for restore:number requested Total database backupsrestored: number restored Total databaseskipped: number skipped Throughput rate:rate Kb/Sec Total bytes transferred: bytesElapsed processing time: time Secs

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logindicating the end of a restore.

System action: None


FMY3012I Data Protection for SQL: restore typerestore of backup object object name todatabase database name from server servername canceled by user.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logindicating that a backup request was canceled by theuser.

System action: None


FMY3013I Data Protection for SQL: StartingInactivate processing for backup objectsfrom server servername

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whenan inactivate process begins.

System action: None


FMY3014I Data Protection for SQL: Inactivateprocessing complete Total databasebackups inspected: number inspected Totaldatabase backups requested forinactivation: number requested Totaldatabase backups inactivated: numberinactivated Total database skipped:number skipped Elapsed processing time:time Secs

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log toindicate the end of an inactivate command.

System action: None

User response: None

FMY3015I Data Protection for SQL: Inactivatingbackup type backup backup object.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whenan inactivation of a backup object is started.

System action: None


FMY3016I Data Protection for SQL: Databasedatabase name from server server name isexcluded from backup type backupbecause it has a Simple Recovery modelor it is a system master database.

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity log whena Simple Recovery model database or a system master

FMY3008I • FMY3016I


database is automatically excluded from a DataProtection for SQL backup.

System action: None


FMY3528E Data Protection for Microsoft SQLServer is only licensed to run dataprotection operations to a Tivoli StorageManager server. It is not licensed tobackup or to restore using locallymanaged snapshots.

Explanation: Currently installed license allows tocreate and restore only TSM VSS backups. In order tocreate backups and to restore local VSS backups, DataProtection for SQL requires that a valid fully-featuredlicense is installed.


User response: In order to create and restore local VSSbackups it is required to purchase and install afully-featured valid license.

FMY3532E The restore destination directory pathneeds to be fully-qualified.

Explanation: The /relocatedir option was specifiedwithout a fully-qualified path.


User response: Enter the command again and specifya fully-qualified path in the /relocatedir option.

FMY5050I A new configuration file was created.

Explanation: The file specified in the /configfileparameter does not exist. A new file was created.



FMY5051I The configuration file cannot be found,using default settings.

Explanation: The file specififed in the /configfileparameter cannot be found.


User response: Ensure the correct file name isspecified.

FMY5052E An error occurred trying to set therequested configuration option.

Explanation: An error occurred while writing to theconfiguration file.


User response: View any other messages that were

displayed. After reviewing the messages andperforming necessary actions, run the command again.

FMY5053E The value for the option option is notvalid. See the TDPSQLC Help Setoutput or the User's Guide for valid Setcommand parameters.

Explanation: The configuration option being set is notvalid.


User response: Run "TDPSQLC Help Set" or refer tothe User's Guide for valid Set command parameters.

FMY5054I The configuration option was setsuccessfully.

Explanation: The configuration option specified on theSet command was set successfully.


User response: None

FMY5056I The logfile log file could not be pruned.Processing will continue.



User response: The log file may not exist. If the logfile exists, view the log for indications of possibleproblems.

FMY5057I The logfile log file was prunedsuccessfully.

Explanation: The log file mentioned prunedsuccessfully.



FMY5058W The logfile name is greater than themaximum allowed. Processing willcontinue using a logfile name of logfilein the current directory.

Explanation: The logfile name entered was not fullyqualified. When the fully qualified log file name wascreated, it was longer than the possible length of a logfile.

System action: Processing continues by creating andusing a log file in the current directory.

User response: Consider updating the log file nameusing a fully qualified path.

FMY3528E • FMY5058W


FMY5059W The logfile log file cannot be opened forwriting. There will be no logging ofevents.

Explanation: The log mentioned could not be openedfor appends. Therefore, no logging is performed.

System action: Processing continues without logging.

User response: Determine why the log file could notbe opened. The log file may refer to a non-existentdrive or partition, or the log file is marked read-only.

FMY5060E A Tivoli Storage Manager API error hasoccurred.

Explanation: A Tivoli Storage Manager API error hasoccurred.


User response: Retry the operation. If the errorpersists, contact your service representative.

FMY5061E A Microsoft SQL API error has occurred.

Explanation: A Microsoft SQL API error occurred.


User response: Retry the operation. If the errorpersists, contact your service representative.

FMY5063I The logfile_name log file did not needpruning.

Explanation: The log file specified did not need to bepruned.


User response: The log file will automatically bepruned at a later date. If the log file is currently toolarge, decrease the number of days the log entries areretained.

FMY5064W The logfile_name log file could not beopened for writing. The log was notpruned and there will be no logging ofevents.

Explanation: The log mentioned could not be openedfor appends. Therefore, no logging or pruning isperformed.

System action: Processing continues without loggingand without pruning.

User response: Determine why the log file could notbe opened. The log file may refer to a non-existentdrive or partition, or the log file is marked read-only.

FMY5065E The value specified for the /SQLUSeroption does not match the registry entry.

Explanation: A Backup, Restore or Query Sqlcommand was issued with both the/SQLAUTHentication=SQLUserid and the /SQLUSeroption specified. An attempt was made to obtain thesqlpassword value from the registry but the user ID inthe registry does not match the user ID specified withthe /sqluser option.


User response: Issue the command and either specifythe /sqluser value which matches the registry entry orspecify the desired values for both the /sqluser and/sqlpassword options on the command.

FMY5091E PASSWORDACCESS is Generate. Eitherthe stored password is incorrect or thereis no stored password. If you do nothave a stored password, use the-TSMPassword=xxx option to set andstore your password.

Explanation: The PASSWORDACCESS option is set togenerate in the client options file. However, nopassword is stored. An initial password needs to bestored.


User response: Invoke the command again using the-TSMPassword option. Any subsequent commandsshould now complete without specifying a password.

FMY5097I Data Protection for SQL is notconfigured for VSS operations.

Explanation: Data Protection for SQL has not beenconfigured to perform VSS operations.


User response: In order to perform VSS operations,there must be a valid Tivoli Storage Manager AdvancedCopy Services license installed and the Data Protectionfor SQL LOCALDSMAGENTNODE preference must beset correctly. Refer to the Data Protection for SQL User'sGuide for details on configuring the client for VSSoperations.

FMY5098E Error obtaining VSS information fromLocal DSMAgent Node:'localdsmagentnode'.

Explanation: Data Protection for SQL attempted toobtain VSS information through the specifiedLOCALDSMAGENTNODE but failed. The errormessage encountered is also displayed.

System action: VSS information is not displayed.

FMY5059W • FMY5098E


User response: Refer to the error message displayedalong with this message.

FMY5124E Invalid command. Data Protection forSQL only supports VSS backup type ofFULL.

Explanation: An invalid backup type was specified onthe VSS backup request. Data Protection for SQLsupports backup types of FULL when using the VSSbackup method.


User response: Retry the backup operation specifyinga supported VSS backup type.

FMY5125E Invalid command. Data Protection forSQL does not support OFFLOAD withthe Legacy backup method.

Explanation: The OFFLOAD option was specifiedwhen using the Legacy backup method. DataProtection for SQL does not support offload with theLegacy backup method. Data Protection for SQLsupports offload with the VSS backup method only.


User response: Retry the backup operation withoutspecifying the offload option or by specifying the VSSbackup method.

FMY5126E Invalid command. Data Protection forSQL only supports Legacy backups witha backup destination of TSM.

Explanation: An invalid backup destination wasspecified with the Legacy backup method. DataProtection for SQL only supports a backup destinationof TSM when using the Legacy backup method.


User response: Retry the backup operation specifyinga backup destination of TSM.

FMY5127E Invalid command. Data Protection forSQL does not support OFFLOAD withthe combination specified for backupdestination and version of Windows.

Explanation: The OFFLOAD option was specifiedwith an unsupported backup destination. DataProtection for SQL only supports offload with a backupdestination of TSM or if running on a Windows System2008 or later, backup destination TSM or BOTH.


User response: Retry the VSS offloaded backupoperation specifying a backup destination of TSM.

FMY5128E The VSS operation failed with rc =returncode.

Explanation: There was a failure when Data Protectionfor SQL performed the VSS operation.


User response: Verify that the Client AcceptorDaemon (CAD) is installed, configured, and runningproperly on the machine. Retry the operation. If theerror persists, contact your service representative.

FMY5129E Data Protection for SQL is unable to runVSS operations. A valid VSS license filecould not be located.

Explanation: In order to perform VSS operations, it isrequired to purchase and install a valid license.


User response: Verify that the prerequisites identifiedabove are met and retry the operation.

FMY5170E Missing, blank, or invalid LocalDSMAGENT Node Name is notallowed.

Explanation: In order to run VSS operations, DataProtection for SQL verifies that the Local DSMAGENTNode Name is specified and valid. This error indicatesthat the Local DSMAGENT Node Name is missing,blank, or invalid.


User response: Set the Local DSMAGENT NodeName to a valid value and retry the operation.

FMY5171E Invalid command. Data Protection forSQL only supports restoring VSSbackup types of FULL and COPY.

Explanation: An invalid backup type was specified onthe VSS restore request. Data Protection for SQLsupports restoring backups of type FULL and COPY.


User response: Retry the restore operation specifyinga supported VSS backup type.

FMY5172E Invalid command. Data Protection forSQL VSS restore does not supportRESTOREDATE and RESTORETIMEoptions.

Explanation: An invalid option was specified on theVSS restore request. Data Protection for SQLRESTOREDATE and RESTORETIME options are notsupported for VSS restore.




User response: Retry the restore operation withoutspecifying RESTOREDATE and RESTORETIME options.

FMY5177E Invalid DSMAGENT Nodeconfiguration found for node'dsmagentnode'.




FMY5186E The VSS writer didn't return anyselectable backup components for thespecified database(s). Ensure that theSQL Server VSS writer service has beenstarted.

Explanation: The SQL Server VSS writer service didn'treturn any selectable backup components for thespecified database(s).

System action: Backup fails, processing ends.

User response: Ensure that the SQL Server VSS writerservice has been started and that service start type isset to automatic.

FMY5187E Multiple backup objects withconflicting backup desitinations werefound for one or more of the specifieddatabase(s). The /OBJECT and/or/BACKUPDESTINATION optionsshould be used to restore a specificdatabase.

Explanation: The backup object specified for the VSSrestore operation was not specific enough to be unique.More information is required in order to restore thecorrect backup object.


User response: Retry the restore operation specifyingthe /OBJECT= and /BACKUPDESTINATIONparameters.

FMY5188E BOTH may not be specified for/BACKUPDESTINATION, only TSM orLOCAL are valid.

Explanation: The restore command only allowsspecifying backup destinations of TSM or LOCAL foridentifying database(s) to restore.


User response: Retry the restore operation specifying

TSM or LOCAL with /BACKUPDESTINATIONparameters.

FMY5195I Data Protection for SQL: Backup ofserver servername enhanced statistics.Total SQL backups deduplicated: numberdeduplicated Throughput rate: rate Kb/SecTotal bytes inspected: bytes inspectedTotal bytes transferred: bytes TotalLanFree bytes transferred: lanfree bytesTotal bytes before deduplication:prededup bytes Total bytes afterdeduplication: postdedup bytes Datacompressed by: compression ratio%%Deduplication reduction: deduplicationratio%% Total data reduction ratio:reduction ratio%% Elapsed processingtime: time Secs

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logdisplaying additional statistics at the end of a backuprequest.

System action: None


FMY5196I Data Protection for SQL: Backup ofserver servername is complete. Total SQLbackups selected: number selected TotalSQL backups attempted: numberattempted Total SQL backups completed:number completed Total SQL backupsexcluded: number excluded Total SQLbackups deduplicated: numberdeduplicated Throughput rate: rate Kb/SecTotal bytes inspected: bytes inspectedTotal bytes transferred: bytes TotalLanFree bytes transferred: lanfree bytesTotal bytes before deduplication:prededup bytes Total bytes afterdeduplication: postdedup bytes Datacompressed by: compression ratio%%Deduplication reduction: deduplicationratio%% Total data reduction ratio:reduction ratio%% Elapsed processingtime: time Secs


System action: None




FMY5197I Data Protection for SQL: Restore fromserver server name to server server name iscomplete. Total database backupsinspected: number inspected Totaldatabase backups requested for restore:number requested Total database backupsrestored: number restored Total databaseskipped: number skipped Throughput rate:rate Kb/Sec Total bytes transferred: bytesTotal LanFree bytes transferred: lanfreebytes Elapsed processing time: time Secs

Explanation: This is an informational message writtento the Tivoli Storage Manager Server activity logindicating the end of a restore.

System action: None


FMY5198W WARNING: The LOG backup of the'database' database failed, however, thelog may have been truncated. Youshould perform a FULL backup of thedatabase.

Explanation: The LOG backup of the database failed,however, the log may have been truncated. You shouldperform a FULL backup of the database.


User response: You should perform a FULL backup ofthe database.

FMY5204E None of the specified databases exist, orare available for backup.

Explanation: A request was made to backup databaseswhich do not exist, or are not available.


User response: Ensure that all of the databases existand are available, and restart the backup.

FMY5205E The command is not valid. DataProtection for SQL supports restoringthe VMVSS FULL backup type.

Explanation: When the VMVSS restore request isentered, an invalid backup type is specified. The FULLbackup type is supported with Data Protection for SQLrestore backups.


User response: Start the restore operation after youspecify a supported VMVSS backup type.

FMY5247S File 'file-name' could not be found, or itcannot be read.



v The DSM_CONFIG (or DSMI_CONFIG if you areusing the Data Protection for Microsoft SQL ServerAPI) environment variable specifies an options filethat does not exist.

v You specified the TSMOPTFILE or FCMOPTFILEoption when starting the Data Protection forMicrosoft SQL Server client, but the option file youprovided does not exist.

v You specified the TSMOPTFILE or FCMOPTFILEoption when starting the Data Protection forMicrosoft SQL Server client, but the configuration filethat you provided does not have appropriate readpermissions for the user that is running theoperation.

v You specified the CONFIGFILE option when startingthe Data Protection for Microsoft SQL Server client,but the configuration file you provided does notexist.

v You specified the CONFIGFILE option when startingthe Data Protection for Microsoft SQL Server client,but the options file that you provided does not haveappropriate read permissions for the user that isrunning the operation.

System action: Data Protection for Microsoft SQLServer client processing stops.

User response: Make sure that the file you want touse exists, it has the read rights set for the user that isrunning the operation, and it is in the standard fileencoding of the system. For example, on Windows theexpected file encoding is ANSI. Review theconfiguration information in the Data Protection forMicrosoft SQL Server client manual specific to youroperating system. If the problem persists, ask yourData Protection for Microsoft SQL Server administratorfor further assistance.

FMY5400E The Virtual Device Interface is notregistered with the Common ObjectModel.

Explanation: The virtual device interface could not becreated because it is not registered with the commonobject model. The SQL server may not be installedproperly.


User response: Verify that the SQL server is installedproperly and retry the operation. Contact your servicerepresentative if the error persists.



FMY5401E The Virtual Device Interface could notbe created.

Explanation: The virtual device interface could not becreated. The SQL server virtual device interface log orWindows NT event log may contain more information.


User response: If the SQL server messages do notresolve the problem, retry the operation. Contact yourservice representative if the error persists.

FMY5402E The Virtual Device Set could not becreated.

Explanation: The virtual device set could not becreated. The SQL server virtual device interface log orWindows NT event log may contain more information.



FMY5403E The configuration of the Virtual DeviceSet could not be obtained.

Explanation: The configuration of the virtual deviceset could not be obtained. The SQL server virtualdevice interface log, SQL server activity log, SQL servererror log, or Windows NT event log may contain moreinformation.


User response: If the SQL server messages do not helpresolve the problem retry the operation. If the errorpersists, contact your service representative.

FMY5404E The Virtual Device Set could not open avirtual device.

Explanation: The virtual device set could not open avirtual device. The SQL server virtual device interfacelog, SQL server activity log, SQL server error log, orWindows NT event log may contain more information.



FMY5405E An unknown virtual device error hasbeen detected.

Explanation: A virtual device returned and unknownreturn code.\n" The SQL server virtual device interfacelog, SQL server activity log, SQL server error log, orWindows NT event log may contain more information.



FMY5406E The SQL server closed a virtual deviceprematurely.

Explanation: The SQL server aborted the operation onthe selected database. The SQL server virtual deviceinterface log, SQL server activity log, SQL server errorlog, or Windows NT event log may contain moreinformation.



FMY5407E The SQL server aborted the operation.

Explanation: The SQL server aborted the operation onthe selected database. The SQL server virtual deviceinterface log, SQL server activity log, SQL server errorlog, or Windows NT event log may contain moreinformation.



FMY5420E

Explanation: A SQL API error has occurred.

System action: Processing for this operation ends.


FMY5421E Received the following from the MSCOM component: SQL message

Explanation: A SQL error has occurred.



FMY5422E Received the following from the MSSQL server: SQL message






FMY5423E The following string is too long: string




FMY5424E Could not connect to SQL server; SQLserver returned: SQL message




FMY5425E The SQL server is not running: SQLmessage



User response: Start the SQL server and retry theoperation.

FMY5426E The SQL log on does not have theSysadmin role: SQL message

Explanation: An attempt was made to logon to theSQL server but the specified logon name does not havethe Sysadmin role.


User response: Try the operation again and specifyeither a log on name with the Sysadmin role or changethe specified log on name to have the Sysadmin role.

FMY5427E The SQL server version is less than 7.0:SQL message

Explanation: An attempt was made to use DataProtection for SQL Server V2 with a SQL server versionearlier than the version 7.0 level. This is not allowed.


User response: Use the Data Protection for SQL V1client with SQL server earlier than the version 7.0 level,or retry the operation with a SQL server verison 7.0 orlater.

FMY5428E The SQL server is not on the localmachine: SQL message

Explanation: An attempt was made to use theapplication client specifying a SQL server that was noton the local machine.


User response: Retry the operation on the machinewhere the SQL server resides.

FMY5429E Could not obtain an event from SQLserver: SQL message




FMY5430E The SQL Server Name is blank orNULL.

Explanation: In the query to obtain the SQL ServerName, the system returned a blank name. A valid SQLServer Name is necessary to continue the operation.

System action: Processing for the current operationends.

User response: Check the SQL Server Name by usingthe "select @@servername" command from the SQLQuery Analyzer. If that returns NULL, use the"sp_addserver" stored procedure to set the SQL ServerName to the correct value. After setting the SQL ServerName, retry the operation. Contact your servicerepresentative if the error persists.

FMY5431E Multiple dbnames are not allowed.

Explanation: An invalid RESTORE command wasissued. It is not valid to specify multiple databasenames in the <dbname> parameter list when using the/STANDBY, /RELOCATE, or /INTO options.


User response: Enter the command again with a validvalue in the positional parameter or option.

FMY5432E Equal numbers of the /RELOCATE and/TO options must be specified.

Explanation: Unequal numbers of the /RELOCATEand /TO options were specified on a RESTOREcommand.


User response: Re-enter the command specifying thesame number of /RELOCATE and /TO options.

FMY5433E Wildcards are not allowed as part of thefollowing parameters/options:

Explanation: This message displays the positionalparameters and/or options that were specifiedincorrectly.




User response: Re-enter the command specifying thecorrect parameters and/or options.

FMY5434E The following options cannot bespecified together:

Explanation: This message displays the conflictingcommand options that were entered.



FMY5435E This command requires one of thefollowing options:

Explanation: This message displays the options thatwere missing from the command entered.


User response: Re-enter the command specifying oneof the command options required by the command.

FMY5436E A failure occurred on stripe number(stripe number), rc = return code

Explanation: A failure occurred on the numberedstripe.


User response: There should be other messages alongwith this one. Refer to the other messages to determinethe problem.

FMY5450E The specified number of stripes (numberof stripes) is invalid. Processing willcontinue with the maximum number ofstripes (maximum number of stripes).

Explanation: An invalid number of stripes wasspecified.

System action: Processing continues utilizing theallowed maximum number of stripes.

User response: None

FMY5451E A failure occurred on vdev (vdev name),rc = return code

Explanation: A failure occurred on the named virtualdevice.


User response: There should be other messagesdisplayed with this message. Refer to the othermessages to determine the problem.

FMY5452E Unable to delete temporary object:(filespace name) (high level qualifier) (lowlevel qualifier)

Explanation: When a backup fails, the DP agentattempts to delete all temporary backup data objectsfrom the TSM server. This message indicates that thespecified temporary backup data object could not bedeleted from the TSM server. This error is usuallycaused by the loss of all TSM server sessions.


User response: None. A backup of the databaseshould detect the temporary backup data object anddelete it from the TSM server.

FMY5453E The number of TSM sessions (number ofsessions) is invalid for the specifiednumber of stripes (number of stripes).Processing will continue with thenumber of TSM sessions (number ofsessions) as the number of stripes.

Explanation: An invalid number of TSM sessions wasdetected for the specified number of stripes. Thismessage is caused by the circumvention of an internalerror.

System action: Processing continues utilizing thenumber of TSM sessions as the number of stripes.

User response: Try the operation again. Contact yourservice representative if this error persists.

FMY5454E The maximum number of objectsallowed per TSM transaction (number) isinvalid for the specified number ofstripes (number of stripes). Processing willcontinue with number stripes.

Explanation: The maximum number of objectsallowed per TSM transaction is invalid for the specifiednumber of stripes for at least one of the TSM sessions.All TSM sessions must allow at least one more objectper TSM transaction than the number of stripes

System action: Processing continues utilizing the newnumber of stripes.

User response: Reduce the number of stripes. You canalso update the TSM server to increase the maximumnumber of logical files that a client can send to theserver in a single transaction (TxnGrpMax).

FMY5455E The backup is corrupt and can not berestored.

Explanation: The backup being restored is corruptbecause the data object or objects found do notcorrespond to the metadata.




User response: Try the operation again. Contact yourservice representative if the error persists.

FMY5456W The backup is corrupt and is not fullyrestorable. Processing will continue.

Explanation: The backup being restored is corruptbecause the data object or objects found do notcorrespond to the metadata. Depending on the restorecommand and the backup type, a partial restore maybe possible.


User response: Try the operation again. Contact yourservice representative if the error persists.

FMY5457E An unknown SQL API error hasoccurred.

Explanation: A SQL API error has occurred but theassociated error message could not be found. The SQLserver activity log, SQL server error log, or WindowsNT/2000 event log may contain more information.


User response: If the SQL server messages do notresolve the problem, try the operation again. Contactyour service representative if the error persists.

FMY5458W The TSM Server 'backup delete' settingfor node (server node name) is set to NO.It should be set to YES for properoperation. Processing continues.

Explanation: The TSM Server setting that allows TSMclients to delete their own backups is set to NO for thespecified node name. The backup delete value must beset to YES in order for cleanup operations to completesuccessfully. A NO value means that unusable residualdata might be stored on the TSM Server.


User response: Make sure the 'backup delete' settingfor the specified node name is set to YES on the TSMServer. Your TSM Server administrator can change thissetting for your node. The setting can only be changedon the TSM Server.

FMY5459W Database object name excluded frombackup.

Explanation: The specified database was excludedfrom backup by the /EXCLUDEDB setting.

System action: Database isn't backed up.


FMY5460W Database object object name doesn't existor isn't valid.

Explanation: The specified backup object doesn't existor isn't valid.

System action: Processing for this backup object ends.

User response: Make sure the specified backup objectexists.

FMY5500E The MultiByteToWideChar() functionfailed.

Explanation: This is an internal error that indicatescorrupted storage.

System action: Processing for this database ends.

User response: Try the operation again. Contact yourservice representative if this error persists.

FMY5501E The Common Object Model (COM)library failed to initialize.

Explanation: The unsuccessful call wasCoInitializeEx(NULL,COINIT_MULTITHREADED).OLE32.dll or another COM dll may be missing,down-level, or corrupted.

System action: Processing for this database ends.

User response: Verify your Windows NT (version 4 orlater) installation is complete and try the operationagain. Contact your service representative if this errorpersists.

FMY5550I There are no backups matching thefilespec directorypathfilename and theserver name servername.

Explanation: There are no database backups on theTivoli Storage Manager server for the specified servername.


User response: None

FMY5551I There are no backups matching thecriteria specified for server nameservername.

Explanation: There are no database backups on theTivoli Storage Manager server matching the querycriteria for the specified server name.


User response: Specify a broader range of searchcriteria when issuing this query.

FMY5456W • FMY5551I


FMY5552I No matches were found for the criteriaspecified.

Explanation: The SQL Server was searched fordatabases that matched the specified criteria.


User response: Check the specified search criteria(database name, group name, logical filename). Enterthe command again.

FMY5616W Database cannot be backed up becauseits name contains '\', '?', '*', or ':'character(s).

Explanation: Databases whose names containdirectory or volume separator cannot be backed up orrestored.

System action: Database was excluded from backup.

User response: Rename the database and restartbackup.

FMY5617I Database was excluded from backupbecause database name contains '\', '?',':' or '*' character(s).

Explanation: Databases whose names containdirectory or volume separator cannot be backed up orrestored.

System action: Database was excluded from backup.

User response: Rename the database and restartbackup.

FMY5629E No Backups have been selected forrestore.

Explanation: The Restore button was pressed butnothing was selected in the tree or list view.


User response: Make a selection in the tree or listview and press the Restore button again.

FMY5630E Backups from multiple Server instanceshave been selected for restore.

Explanation: The Restore button was pressed and theuser has selected backups from multiple serverinstances.


User response: Make a selection in the tree forbackups belonging to the same server instance only

FMY5631E Restoring full Legacy backups and fullVSS backups in the same restoreoperation is not supported. Retry therestores in separate operations.

Explanation: At least one VSS backup object and oneLegacy backup object were selected for a restore in thesame operation. This is not supported.


User response: Retry the restores specifying theLegacy backups and VSS backups in separateoperations.

FMY5715E Error writing option_name preference tothe configuration file.

Explanation: Could not write the specified preferenceto the configuration file.

System action: Preferences processing ends.

User response: Make sure you have a validconfiguration file, then try to update the preferenceagain.

FMY5716W An error was encountered with TivoliStorage Manager API initialization, rc =returncode. Examine the dsierror.log formore information or determine if theTSM API is installed properly.

Explanation: Errors were encountered during anattempt to run setup for the Tivoli Storage ManagerAPI.


User response: Examine the dsierror.log file todetermine the problem. If this file does not exist, theTSM API may not be installed properly. If the TSM APIis not installed properly, install the TSM API and runthe command again.

FMY5717E Unable to log on to the SQL server.

Explanation: An error occurred while trying to log onto the SQL server.

System action: If running the client from thecommand line, the client ends. If running the clientfrom the GUI, a prompt is displayed to enter the SQLuser ID and password, or to choose Windowsauthentication.

User response: Make sure the SQL server is running.

FMY5718I When the view is refreshed allselections will be lost and an attemptwill be made to expand the new tree tothe currently highlighted item. Do youwant to continue?

FMY5552I • FMY5718I


Explanation: The refresh toolbar button or pulldownmenu item has been selected.


User response: Select Yes to refresh the view or selectNo to leave the current view unchanged.

FMY5719I There are currently no backups on TSM.

Explanation: The SQL server name expansion buttonwas pressed on the Inactivate page.


User response: Either nothing was backed up to aTSM server or all active backups were inactivated.

FMY5720I No databases have been selected forbackup.

Explanation: The Backup button was pressed on theGUI but no databases were selected from the tree orlist.


User response: Select a database and press the Backupbutton again.

FMY5721I No backups have been selected forrestore.

Explanation: The restore button was pressed on theGUI but no backup objects were selected from the treeor list.


User response: Select a backup object and press theRestore button again.

FMY5722I No backups have been selected forinactivate.

Explanation: The Inactivate button was pressed on theGUI but no backup objects were selected from the treeor list.


User response: Select a backup object and press theInactivate button again.

FMY5723E A named mark must be specified.

Explanation: The "Stop At Mark" or "Stop BeforeMark" option was chosen but the named mark was notspecified.


User response: Enter a named mark or choose the"Stop At" option.

FMY5784E A log must be selected to use point intime.

Explanation: A log must be selected before settingpoint in time parameters.


User response: Select at least one log for restorebefore specifying a point in time.

FMY5804I Unable to get information. If data isbacked up to tape check the "Wait forTape Mounts for File Information"checkbox.

Explanation: Processing stops.

System action: None

User response: Try checking the box specified in themessage.

FMY5805W The SQL Server you are restoring fromis different than the SQL server you arecurrently logged on to. Do you want tocontinue?

Explanation: Processing continues.

System action: None

User response: If you want to restore something froma different SQL server, press OK; otherwise pressCancel and log on to the other SQL server.

FMY5915E An attempt to query detailed managedcapacacity failed.

Explanation:

System action:

User response:

FMY5929E An attempt to query total managedcapacacity failed.

Explanation:

System action:

User response:

FMY5958W The selected database <> is offline --skipping.

Explanation: A request was made to backup adatabase which is offline.

System action: Processing continues, but offlinedatabases are skipped.

User response: Ensure that the selected databases areonline and retry the backup.

FMY5719I • FMY5958W


FMY5959E Unable to run data protection operationsto a FlashCopy Manager virtual server.A valid FlashCopy Manager license filecould not be located.

Explanation: In order to perform data protectionoperations to a FlashCopy Manager virtual server, avalid license for FlashCopy Manager must be installedin the FlashCopy Manager installation directory. Thislicense file is named fcmclient.lic.


User response: Verify that the prerequisites identifiedabove are met and retry the operation. If the errorpersists, contact your service representative.

FMY5960E This product is not licensed to run dataprotection operations to a Tivoli StorageManager server. A valid DP for SQLlicense file could not be located. Withthe current licenses only data protectionoperations to a Flash Copy Managervirtual server can be run.

Explanation: In order to perform data protectionoperations to a Tivoli Storage Manager server, a validlicense for TDP for SQL (called sqlclient.lic) must beinstalled. The TDP for SQL license should be installedin the TDP for SQL installation directory.


User response: Verify that the prerequisites identifiedabove are met and retry the operation. If the errorpersists, contact your service representative.

FMY5961E The parameters /BACKUPMETHOD or/BACKUPDESTINATION or both areinvalid when performing data protectionoperations using a FlashCopy Managervirtual server.

Explanation: Data protection commands default to/BACKUPMETHOD=VSS and/BACKUPDESTINATION=LOCAL when performedagainst a FlashCopy Manager virtual server. TheFlashCopy Manager supports no other values for theseparameters. As a result it is no longer necessary tospecify these parameters. For compatibility with otherproducts values for /BACKUPMETHOD and/BACKUPDESTINATION can be specified as long asthey are set to their only valid values. This means that/BACKUPMETHOD can only be set to VSS and/BACKUPDESTINATION can only be set to LOCAL.


User response: Retry the command removing the/BACKUPDESTINATION and /BACKUPMETHODparameters.

FMY5965E Database state does not allow logbackup with TRUNCATE=YES.

Explanation: Database status is not Normal. Log hasto be backed up with truncation turned off.

System action: The backup operation failed.

User response: Back up log with TRUNCATE=NO.

FMY5966E Logical name was not found in thedatabase.

Explanation: The logical name specified duringrelocation was not found in the database.


User response: Specify the correct logical name andretry the operation.

FMY5969E Database state does not allow backuplog tail.

Explanation: Database status is not Normal. By nowwe only support backup the tail of the log whendatabase is not offline or damaged.

System action: The backup operation failed.

User response: Back up the tail of the log whendatabase status is normal.

FMY6060I No matched backup is found accordingto the Query conditions.

Explanation: Information: No matched backup isfound in TSM Server according to the Queryconditions.


User response:

FMY6065E Mount backup command failed. Themount point and / or backup specifiedis invalid. Please refer to dsmerror.logfor further details.

Explanation: The mount backup command failed. Thebackup specified may already be mounted and or thedrive to map to may already be in used. Check if theprovided directory to contain the mount pointdirectories for all snapshots is an empty NTFS directorywithout hidden or system files and / or directories.


User response: Check to make sure that the backupspecified is not already mounted and that the drive tomap to is available. Repeat the command using anempty NTFS directory as the snapshots mount pointsdirectory.



FMY6066E Unmount backup command failed.Please refer to dsmerror.log for furtherdetails.

Explanation: The unmount backup command failed.The backup specified may not be mounted.


User response: Check to make sure that the backupspecified is mounted.

FMY6067E In the component list that is specified,the following object is not valid: 'object'.

Explanation: The command that is entered includes acomponent list. The list of components contains one ormore invalid objects. For example, when entering aBACKUP or RESTORE command, if the component listincludes a volume or mount point that is not valid or isnot eligible for back up, this message is displayed. Inaddition, the GUID volume name cannot be specified.For RESTORE, MOUNT BACKUP, or DELETEBACKUP commands, this message is displayed if thecomponent list contains a backup specification that isnot found in the backup inventory.


User response: Verify the correct syntax is used whenentering the command. If the message is displayedagain, verify the volume and mount point names arecorrectly identified. A misspelling can trigger thismessage.

FMY6103I AlwaysOnPriority is skipping thebackup of availability database namebecause it is not on the preferredreplica.

Explanation: When the AlwaysOnPriority option isspecified SQL Server is queried to see if the currentavailability replica is the preferred replica. The backupof the availability database will only be performed onthe preferred replica. The backup is skipped on allreplicas that are not the primary replica.

System action: Processing for this backup object ends.

User response: No response is needed.

FMY6104I Backup Type backup for database databasename is not supported fromnone-readable secondary replica.

Explanation: Database on none-readable secondaryreplica only supports full backup and copyonly backup.

System action: Run the same backup from primaryreplica or readable secondary replica.

User response: Run the same backup from primaryreplica or readable secondary replica.

FMY6105I Differential backup database databasename from secondary replica is notsupported. Exclude it for backup.

Explanation: Differential backup databases fromsecondary replica is not supported.

System action: Run the same backup from primaryreplica.

User response: Run the same backup from primaryreplica.

FMY6110W Backup of database 'database name' isbypassed because it is offline. Databaseattributes are database attributes.

Explanation: Backup processing bypasses the offlinedatabase.

System action: Backup processing continues but theoffline database is skipped.

User response: Ensure that the selected database isonline or normal database and retry the backup.

FMY6111I Backup of database 'database name' isbypassed because it is a databasesnapshot. Database attributes aredatabase attributes.

Explanation: Backup processing bypasses the databasesnapshot.

System action: Backup processing continues but thedatabase snapshot is skipped.


FMY6112W Backup of database 'database name' isbypassed because it is in restoringstatus. Database attributes are databaseattributes.

Explanation: Backup processing bypasses the databasewith restoring status database.

System action: Backup processing continues but thedatabase with restoring status database is skipped.


FMY6113I Backup of database 'database name' isbypassed because it is a mirroreddatabase. Database attributes are databaseattributes.

Explanation: Backup processing bypasses the mirroreddatabase.

System action: Backup processing continues but themirrored database is skipped.




FMY6114W Backup bypassed some databasesbecause of their status.

Explanation: Backup processing bypasses the offline,snapshot, mirrored, or with restoring state database.

System action: Backup processing continues but somedatabases are skipped.

User response: Ensure that the skipped databases areonline, and retry the backup.

FMY6115I Backup of database 'database name' isbypassed because it is offline. Databaseattributes are database attributes.

Explanation: Backup processing bypasses the offlinedatabase.

System action: Backup processing continues but theoffline database is skipped.


FMY6116I Backup of database 'database name' isbypassed because it is in restoringstatus. Database attributes are databaseattributes.

Explanation: Backup processing bypasses the databasewith restoring status database.

System action: Backup processing continues but thedatabase with restoring status database is skipped.


FMY6117I Actions were taken to fix the errormessages FMY5436E and FMV0328E.

Explanation: This is an informational message to letyou know that the merge error was fixed.

System action: None

User response: None

FMY6200W The data center node is not correctlyconfigured. To correct the problem,re-run the configuration wizard and setthe datacenter node field with the nodethat was used to perform the VMbackups.

Explanation: Warning: Because the data center node isnot configured to match the query and restoreconditions, this warning is reported.

System action: Processing continues, but the data

center node configuration problem persists until youupdate the configuration.

User response: Run the Tivoli Storage Manager forDatabases: Data Protection for SQL configurationwizard. If the status of the Configuring Recovery Agentrule does not indicate Passed, there is a configurationproblem.

FMY6201W The license for the Recovery Agent, partof the Tivoli Storage Manager forVirtual Environments, is either not validor not found.

Explanation: Warning: Without a valid license for theRecovery Agent, you cannot use parts of Tivoli StorageManager for Databases: Data Protection for SQL torecover Microsoft SQL databases from a VM backup.

System action: The software continues to run, but youcannot use Tivoli Storage Manager for Databases: DataProtection for SQL to recover Microsoft SQL databsesfrom a VM backup.

User response: Verify that the correct license file is inthe correct directory. If you use the installation wizard,the license file should be saved to the correct directory.

FMY6202W The TDPVMWareShell command iseither at an earlier level or not found.The VM backup data query or restore isnot issued.

Explanation: Warning: To issue the VM backup dataquery or restore, update the software. Please upgrade itto support this feature.

System action: The command is ignored andprocessing continues.

User response:

FMY6203I The tail-log backup of the databasefrom the secondary replica is notsupported. databases name is excludedfrom the backup process.

Explanation: Tail-log backups of databases from thesecondary replica are not supported.

System action: The database backup operation iscanceled.

User response: Run the backup from the primaryreplica.

FMY6204I The tail-log backup of the database namedatabase from the primary serverremoves the databases from the AAG.Do you want to continue? Enter 'Y' forContinue or 'N' to cancel.

Explanation: The tail-log backup of databases fromthe primary server removes databases from the AAG.

FMY6114W • FMY6204I


System action: If the database is not removed fromthe AAG, the SQL Server reports an error whencompleting the backup.

User response: To continue with the tail-log backupand remove database from the AAG, enter Y. To cancel,enter N.

FMY6205E The tdpsqlc command that was enteredexceeds the maximum length limit. Thelength limit of each option is 1790characters.

Explanation: The length of tdpsqlc command is toolong. It is invalid. When the length limit is exceeded,the command is ignored. There is no truncation.

System action: tdpsqlc command will fail with error.An error message is displayed. The command is notprocessed.

User response: Check the length of tdpsqlc options,especially check the length of multiple databases name.If possible, enter abbreviated parameters and options. Ifmultiple database names are entered, the length of thedatabase names can cause this error.

FMY6206W Database '' was excluded from backupbecause the database name containsspecial string ''.

Explanation: There are certain characters and stringsthat conflict with Data Protection for SQL backupoperations. A database name that contained one of thespecial characters or strings was encountered during abackup operation. Therefore, it was excluded from thebackup.

System action: The database was excluded frombackup.

User response: Rename the database and retry thebackup.

FMY6205E • FMY6206W


Chapter 6. FMV messages

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

FMV0101E Unable to open English messagerepository file name.

Explanation: The default English message repositoryfile cannot be opened. Either the file access permissionsprevent reading the file or the file is not present in theexpected location.

System action: Tivoli Storage Manager is unable tocomplete the requested operation. Processing isterminated.

User response: Make sure the file in your DSM_DIR isset up properly. If the problem continues, see yoursystem administrator for further help.

FMV0102W Unable to open the message repositoryfile name. The American Englishrepository will be used instead.

Explanation: The default message repository file forthe current locale cannot be opened. Either the fileaccess permissions prevent reading the file, the file isnot present in the expected location, or the languagespecified in the option file is not supported on thisworkstation.

System action: Tivoli Storage Manager continuesprocessing using the English language messagerepository.

User response: Make sure the file in your DSM_DIR isset up properly. If the problem continues, see yoursystem administrator for further help.

FMV0103E Error trying to read header record frommessage repository file name.

Explanation: The message repository file headerrecord cannot be obtained.

System action: Tivoli Storage Manager is unable tocomplete the requested operation.

User response: Make sure the file has not been alteredfrom the installation. If the problem continues, see yoursystem administrator for further help.

FMV0105E Error trying to read index for messagenumber from repository file name.

Explanation: The message text for the specifiedmessage number cannot be read.



FMV0106E Message index not found for messagenumber.

Explanation: The message repository file does notcontain the message text for the message number.


User response: Make sure the DSM_DIR is set upproperly and it does not point to an old copy. If theproblem continues, see your system administrator forfurther help.

FMV0107E Error trying to read header for messagenumber from repository file name.

Explanation: The message header information cannotbe obtained for the message number in the messagefile.



FMV0108E Error trying to read text for messagenumber from repository file name.

Explanation: The message text cannot be obtained forthe message number in the message file.




FMV0109E Insufficient memory for allocation ofmessage structure.

Explanation: There is not enough memory in yoursystem to allocate the storage needed for the messagetext.


User response: Stop Tivoli Storage Manager andrestart Tivoli Storage Manager. Then retry theoperation. If unsuccessful, close all unneededapplications and retry the operation.

FMV0110E Unable to open error log file file namefor output.

Explanation: The error log cannot be opened foroutput.

System action: Tivoli Storage Manager is unable tocomplete the requested operation. File permissions maybe set such that writing is not allowed.

User response: Stop and restart Tivoli StorageManager. Then retry the operation. If unsuccessful,make sure the file is not being locked by anotherapplication and that file permissions allow write access.

FMV0113E Message repository file name has aninvalid control record.

Explanation: The message repository file contains anincorrect control information.


User response: Make sure the message file was notaltered from the installation. Check DSM_DIR to makesure it is set up properly.

FMV0118E Unable to open schedule log file 'filename' for output.

Explanation: The schedule log file cannot be openedfor output.


User response: Stop Tivoli Storage Manager andrestart Tivoli Storage Manager. Then retry theoperation. If unsuccessful, make sure the file has notbeen locked by another application.

FMV0119E Error trying to read response string formessage number from repository filename.

Explanation: The response string information for themessage number cannot be obtained from the message

repository file. It is possible the message repository hasbeen corrupted.


User response: Make sure the message file was notaltered from the installation. Check DSM_DIR to makesure it is set up properly.

FMV0120E Message number number contains aninvalid multibyte sequence for thecurrent locale.

Explanation: An illegal multibyte sequence for thecurrent locale was found in the message. Either themessage repository has been corrupted or is coded in alanguage other than that of the current locale.


User response: If the message repository is notcorrupted, process the operation in the supportedlocale.

FMV0121W Unable to open the iconv converter forthe message repository file name. TheAmerican English repository will beused instead.

Explanation: The iconv converter for the defaultmessage repository for the current locale cannot beopened. The iconv converter used to convert fromUTF-8 to the current locale is not installed on this workstation.

System action: Tivoli Storage Manager continuesprocessing using the English language messagerepository.

User response: Make sure the required iconvconverter is installed properly. If the problemcontinues, see your system administrator for furtherhelp.

FMV0201E Invalid parameter was found.

Explanation: The system encountered an internalprogram error due to an invalid parameter.

System action: The system returns to the callingprocedure.

User response: Ask your service representative tocheck the error log.

FMV0202E Not authorized to restore the othernode's data.

Explanation: The client is not authorized to restore theother node's data.


FMV0109E • FMV0202E


User response: Get authorization from the other node.

FMV0203E The objName field has no leadingdirectory separator.

Explanation: The objName field does not have aleading directory separator.


User response: Correct the value for the objName.

FMV0204E Wildcards are not allowed in theobjName directory path.

Explanation: Wildcards are not allowed in theobjName directory path.


User response: Correct the value for the objName.

FMV0205E Unable to open error log file.

Explanation: The system is unable to open the errorlog file.


User response: Verify the DSMI_LOG value andaccess permission. On the AS/400 platform, verify thevalue specified for ERRORLOGNAME in the APIoptions file.

FMV0206E The log file cannot be written to.

Explanation: There was an error writing to the logfile.


User response: Verify the DSMI_LOG value andaccess permission. on the AS/400 platform, verify thevalue specified for ERRORLOGNAME in the APIoptions file.

FMV0207E The log file name was not specified.

Explanation: The system is unable to open the errorlog file.


User response: Verify the DSMI_LOG value andaccess permission. On the AS/400 platform, verify thevalue specified for ERRORLOGNAME in the APIoptions file.

FMV0208E The TCP/IP WINSOCK.DLL file cannotbe found.

Explanation: The TCP/IP WINSOCK.DLL file cannotbe found.


User response: Verify your TCP/IP installation.

FMV0209E An error occurred while loading alibrary.

Explanation: An error occurred while loading alibrary. The TCP/IP DLL load failed.



FMV0210E The TCP/IP load function failed.

Explanation: An error occurred while locating afunction. The TCP/IP load function failed.



FMV0211E The object name pointer is NULL.

Explanation: There is no value provided for the objectname pointer.


User response: Provide an address for thedsmObjName structure.

FMV0212E The data block pointer is NULL.

Explanation: There is no value provided for the datablock pointer.


User response: Provide an address for the DataBlkstructure.

FMV0213E The object attribute pointer is NULL.

Explanation: There is no value provided for the objectattribute pointer.


User response: Provide an address for the ObjAttrstructure.


Chapter 6. FMV messages 265

FMV0214E There is no server session information.

Explanation: The server did not respond with thesession information.


User response: Verify the server status.

FMV0215E There is no server policy information.

Explanation: The server did not respond with thepolicy information.


User response: Verify the server policy definitions.

FMV0216E The dataBlk bufferLen value is zero.

Explanation: The value for the dataBlk bufferLen iszero.


User response: Provide a non-zero value for thebufferLen.

FMV0217E The dataBlk bufferPtr is NULL.

Explanation: There is no value provided for thedataBlk bufferPtr.


User response: Provide an address for the bufferPtr.

FMV0218E The objType is invalid.

Explanation: The value for the objType is invalid.


User response: The value for dsmObjName.objTypemust be:

v DSM_OBJ_FILE or DSM_OBJ_DIRECTORY forBackup, or

v DSM_OBJ_FILE for Archive.

FMV0219E The dsmEndTxn vote is invalid.

Explanation: The dsmEndTxn vote is invalid.


User response: The vote must beDSM_VOTE_COMMIT or DSM_VOTE_ABORT.

FMV0220E An invalid option was found duringoption parsing.

Explanation: An invalid option was found.


User response: Verify the options in dsm.opt, dsm.sys,and the options string. Check the error log for moredetails about the error. on the AS/400 platform, verifythe options in *LIB/QOPTTivoli StorageManager(APIOPT).

FMV0221E There was an error in the Tivoli StorageManager API internals.

Explanation: The system encountered an error in theAPI internals.


User response: Shut down the process and retry theoperation. Verify that any previous dsmInit calls werecleaned up and terminated by a dsmTerminate call. Ifthe problem continues, contact your systemadministrator or service representative.

FMV0222E The repository type is invalid.

Explanation: The repository type is invalid.


User response: For dsmDeleteFS the repository mustbe one of the following:

v DSM_ARCHIVE_REP

v DSM_BACKUP_REP

v DSM_REPOS_ALL.

FMV0223E Filespace name should start with thedirectory delimiter.

Explanation: The filespace name is invalid.


User response: Filespace name should start with thedirectory delimiter.

FMV0224E The object name is either an emptystring or has no leading delimiter.

Explanation: The object name is invalid because of anempty string or there is no leading delimiter.


User response: Verify the format of the dsmObjNamefull path.



FMV0225E Low level qualifier of the object nameshould start with the directory delimiter.

Explanation: The low level qualifier for the objectname is invalid.


User response: Start the low level qualifier of theobject name with the directory delimiter.

FMV0226E The object owner is invalid.

Explanation: The object owner must be either the rootuser, or the object owner must be the same as thesession owner.


User response: Verify the session owner and objectowner.

FMV0227E The dsmBindMC sendType is invalid.

Explanation: The dsmBindMC sendType is invalid.


User response: The sendType must be one of thefollowing:

v stBackup

v stArchive

v stBackupMountWait

v stArchiveMountWait

FMV0228E The dsmSendObj sendType is invalid.

Explanation: The dsmSendObj sendType is invalid.


User response: The sendType must be one of thefollowing:

v stBackup

v stArchive

v stBackupMountWait

v stArchiveMountWait

FMV0229E The dsmDeleteObj delType is invalid.

Explanation: The dsmDeleteObj delType is invalid.


User response: The delType must be dtBackup ordtArchive.

FMV0230E The query Backup objState is invalid.

Explanation: The query Backup objState is invalid.


User response: The qryBackupData.objState must beone of the following:

v DSM_ACTIVE

v DSM_INACTIVE

v DSM_ANY_MATCH

FMV0231E The management class name was notfound.

Explanation: A query or send operation is unable tofind the management class name.


User response: Verify the management class name.

FMV0232E The drive letter is not an alphabeticcharacter.

Explanation: The drive letter is not an alphabeticcharacter. This return code is valid on MicrosoftWindows only.


User response: Verify that the drive designation is analphabetic character. The referenced field isdsmDosFSAttrib.driveLetter.

FMV0233E The Register Filespace name is NULL.

Explanation: There is no value provided for theRegister Filespace name.


User response: Provide a filespace name ondsmRegisterFS.

FMV0234E The new password value is NULL orblank.

Explanation: There is no value provided for newpassword.


User response: Provide a new password ondsmChangePW.



FMV0235E The old password value is NULL orblank.

Explanation: There is no value provided for oldpassword.


User response: Provide an old password ondsmChangePW.

FMV0236E On dsmInit, the owner is not allowed toestablish a session whenPASSWORDACCESS=generate.

Explanation: PASSWORDACCESS=GENERATEestablishes a session with the current login user as theowner. The application should set clientOwnerNamePto NULL when PASSWORDACCESS=GENERATE is ineffect.

System action: The system returns to the callingprocedure. Whether the application can continueprocessing depends on how the application handles theerror.

User response: This message applies to applicationsthat utilize the Tivoli Storage Manager API, and isintended primarily for the vendor of the application forwhich the message is issued. Depending on theapplication, this could be a configuration issue.

Consult the documentation for the application andverify that the application is configured correctly. If theproblem persists, contact the application vendor forfurther assistance.

FMV0237E On dsmInit, the node is not allowedwhen PASSWORDACCESS=generate.

Explanation: PASSWORDACCESS=generateestablishes a session with the current hostname as thenode.


User response: When usingPASSWORDACCESS=generate, set clientNodeNameP toNULL.

FMV0238E The sequence of calls is invalid.

Explanation: Then API requires function calls to bemade in a specific sequence. The function calls werenot made in the expected sequence. The error can betriggered by the following issues:

v An error in the network.

v A bug in the Tivoli Storage Manager API.

v A bug in the Tivoli Storage Manager server.

v A bug in the application (IBM or third party) thatuses the Tivoli Storage Manager API.


User response: An end user can respond in thefollowing ways:

v Check the network for errors.

v Look for clues in the Tivoli Storage Manager serveractivity log file, Tivoli Storage Manager client sidedsierror.log log file, and log files that are specific tothe problem application.

v Search the IBM support pages for APARs that matchthe problem. The Tivoli Storage Manager Managersupport site is at www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

v If the API application is developed by a third party(not IBM), search that third party's support pages forknown issues that match the problem.

If none of the above actions resolve the problem, reportthe problem to the vendor of the application that usesthe Tivoli Storage Manager API.

A developer of an application that uses the TivoliStorage Manager API must investigate the reason forthe problem, including reviewing the Tivoli StorageManager API state diagram. The Tivoli StorageManager API state diagram is in the productdocumentation at https://www.ibm.com/support/knowledgecenter/SSGSG7/welcome

FMV0239E On dsmSendObj, wildcards are notallowed for the objName.

Explanation: On dsmSendObj, wildcards are notallowed for the objName.


User response: Provide a fs, hl, and ll on thedsmObjName.

FMV0240E The filespace to delete/set access cannotbe found.

Explanation: The filespace to delete cannot be found.


User response: Verify the filespace name.

FMV0241E On dsmSendObj, dsmDeleteObj, ordsmUpdateFS the filespace is notregistered.

Explanation: On dsmSendObj, dsmDeleteObj, ordsmUpdateFS, the filespace is not registered.





FMV0242W On dsmRegisterFS the filespace isalready registered.

Explanation: On dsmRegisterFS the filespace isalready registered.



FMV0243E On dsmBeginGetData the objID isNULL.

Explanation: On dsmBeginGetData, the objID isNULL.


User response: Verify the following:

v The dsmGetList is not NULL.

v Each objID is not NULL.

v The dsmGetList numObjId is not zero.

FMV0244E On dsmInit the caller's API version isdifferent than the Tivoli StorageManager library version.

Explanation: On dsmInit the caller's API version has ahigher value than the Tivoli Storage Manager libraryversion.


User response: Install the latest Tivoli StorageManager API library and trusted agent module.

FMV0245E The caller's structure version is differentthan the Tivoli Storage Manager libraryversion.

Explanation: The caller's structure version is differentthan the Tivoli Storage Manager library version.


User response: Ensure that the stVersion field is setwith the value in the header file. Recompile theapplication with the latest header files.

FMV0246E Issue dsmEndTxn and then begin a newtransaction session.

Explanation: This transaction must be ended and anew one must be started due to one of the followingreasons:

v The destination changed.

v The byte limit is exceeded

v The maximum number of objects is exceeded.


User response: Issue dsmEndTxn and start a newtransaction session.

FMV0247E The backup or archive object isexcluded from processing.

Explanation: The backup or archive object is excludedfrom processing.


User response: Verify the objName and Exclude lists.

FMV0248E The backup object does not have a copygroup.

Explanation: The backup object does not have a copygroup.


User response: Verify server policy definitions.

FMV0249E The archive object does not have a copygroup.

Explanation: The archive object does not have a copygroup.


User response: Verify server policy definitions.

FMV0250E Memory used by the Tivoli StorageManager API has been corrupted.

Explanation: Memory used by the Tivoli StorageManager API has been corrupted.


User response: Retry the operation. If the problemcontinues, contact your system administrator or servicerepresentative.

FMV0251E The sendObj Archive description is toolong.

Explanation: The sendObj Archive description is toolong.


User response: The sndArchiveData.descr string mustbe less than or equal to DSM_MAX_DESCR_LENGTH.

FMV0242W • FMV0251E


FMV0252E The sendObj ObjAttr.objInfo is toolong.

Explanation: The sendObj ObjAttr.objInfo is too long.


User response: The objInfo field must be less than orequal to DSM_MAX_OBJINFO_LENGTH.

FMV0253E The sendObj dsmObjName.hl is toolong.

Explanation: The sendObj dsmObjName.hl is too long.


User response: The hl field must be less than or equalto DSM_MAX_HL_LENGTH.

FMV0254E The password, or encryptionPasswordstring provided is too long.

Explanation: The value provided for password orencryptionPassword is too long.


User response: The password or encrypionPasswordfield must be less thanDSM_MAX_VERIFIER_LENGTH.

FMV0255E The sendObj dsmObjName.fs is toolong.

Explanation: The sendObj dsmObjName.fs is too long.


User response: The fs field must be less than or equalto DSM_MAX_FS_LENGTH.

FMV0256E The sendObj dsmObjName.ll is toolong.

Explanation: The sendObj dsmObjName.ll is too long.


User response: The ll field must be less than or equalto DSM_MAX_LL_LENGTH.

FMV0257E On RegisterFS or UpdateFS the fsAttr'sfsInfo is too long.

Explanation: On RegisterFS or UpdateFS the fsAttr'sfsInfo is too long.


User response: The fsInfo field must be less than orequal to DSM_MAX_FSINFO_LENGTH.

FMV0258I On dsmGetNextQObj or dsmGetDatathere is more available data.

Explanation: On dsmGetNextQObj or dsmGetDatathere is more available data.


User response: Call the function again.

FMV0259E The dataBlk buffer is too small for thequery response.

Explanation: The dataBlk buffer is too small for thequery response.


User response: On dsmGetNextQObj ensure that thedataBlk buffer is at least as big as the query responsestructure.

FMV0260E An invalid option keyword was foundduring option parsing.

Explanation: An invalid option keyword was found inthe dsmInit configuration file, the option string,dsm.sys, or dsm.opt.


User response: Correct the spelling of the optionkeywords. Verify that the dsmInit configuration fileonly has a subset of the dsm.sys options. Check theerror log for more details about the error.

FMV0261E The configuration file specified ondsmInit cannot be opened.

Explanation: The configuration file specified ondsmInit cannot be opened.


User response: Verify the file name.

FMV0262E The Include/Exclude definition file wasnot found.

Explanation: The Include/Exclude definition file wasnot found.


User response: Verify the file name on the Inclexcloption.



FMV0263E Either the dsm.sys file was not found, orthe Inclexcl file specified in dsm.syswas not found.

Explanation: Either the dsm.sys file was not found, orthe Inclexcl file specified in dsm.sys was not found.


User response: The dsm.sys file must be in thedirectory referenced by the environment variableDSMI_DIR. Verify the file name on the Inclexcl optionin the dsm.sys file.

FMV0264E Only a UNIX root user can executedsmChangePW or dsmDeleteFS.

Explanation: Only a UNIX root user can executedsmChangePW or dsmDeleteFS.


User response: Run this program as a root user.

FMV0265E You must issue dsmBindMC beforedsmSendObj.

Explanation: You must issue dsmBindMC beforedsmSendObj.


User response: Modify your program.

FMV0266I The dsmEndTxn vote is ABORT, socheck the reason field.

Explanation: After a dsmEndTxn call, the transactionis aborted by either the server or client with aDSM_VOTE_ABORT and the reason is returned.


User response: Check the reason field for the codewhich explains why the transaction has been aborted.

FMV0267E Invalid command line option/value:'option'

Explanation: The option is not valid on this commandline.


User response: Verify that the option and value arenot misspelled and are valid with the currentcommand.

FMV0268E Server problem: Destination notdefined.

Explanation: Server problem: Destination not defined.


User response: Have your service representative checkthe error log.

FMV0270S The data buffer overflowed.

Explanation: The data buffer overflowed. This is aprogramming failure and the client program ends.


User response: Retry the operation. If the problemcontinues, contact your system administrator.

FMV0271E No more files can be restored orretrieved since the destination directoryis full.

Explanation: No more files can be restored orretrieved since the destination directory is full.


User response: Free up disk space, or restore orretrieve the file to another disk.

FMV0272I The operation is finished.

Explanation: The operation is finished.


User response: Proceed with next function call.

FMV0273E The trusted agent execution/ownerpermissions are invalid.

Explanation: The trusted agent execution/ownerpermissions are invalid.


User response: Have your system administrator checkthe installation instructions for the client to ensure thatthe trusted agent permissions are set correctly.

FMV0274S Process killed.

Explanation: Processing stopped. This is aprogramming failure and the client program ends.



FMV0263E • FMV0274S


FMV0275S Trusted agent would block theoperation.

Explanation: The trusted agent blocks the operation.This is a programming failure and the client programends.



FMV0276S The area for the include/exclude patternis too small.

Explanation: The area for the include/exclude patternis too small. This is a programming failure and theclient program ends.



FMV0277S There is no closing bracket in thepattern.

Explanation: There is no closing bracket in thepattern. This is a programming failure and the clientprogram ends.



FMV0278S The transaction will be aborted.

Explanation: The server encountered an error and willabort the transaction.

System action: The transaction will be aborted. Thereason code is passed on the dsmEndTxn call.

User response: Issue the dsmEndTxn with a vote ofDSM_VOTE_COMMIT and examine the reason code.

FMV0279I A file was skipped during a restoreoperation because the file is off line andthe application has chosen not to waitfor a tape mount.

Explanation: A file was skipped during a restoreoperation because the file is off line and the applicationhas chosen not to wait for a tape mount.

System action: File skipped.

User response: Verify the application sets themountWait value correctly on dsmBeginGetData.

FMV0280E Unable to find Trusted Agent module.

Explanation: Tivoli Storage Manager was unable tofind the Tivoli Storage Manager Trusted Agent modulein the specified directory. The name of the TivoliStorage Manager Trusted Agent module is dsmtca.

System action: Tivoli Storage Manager ends.

User response: Make sure the Trusted Agent moduleis in the directory specified by DSMI_DIR.

FMV0282E Password file is not available.

Explanation: The file containing the stored passwordfor the specified server-name is unavailable.


User response: The root user must set and store a newpassword.

FMV0283E High level qualifier of the object nameshould start with the directory delimiter.

Explanation: The high level qualifier for the objectname is invalid.


User response: High level qualifier of the object nameshould start with the directory delimiter.

FMV0284E The number of objects ondsmBeginGetData exceedsDSM_MAX_GET_OBJ |DSM_MAX_PARTIAL_GET_OBJ.

Explanation: The number of objects (numObjId)specified on the dsmBeginGetData call exceedsDSM_MAX_GET_OBJ |DSM_MAX_PARTIAL_GET_OBJ.


User response: Check the number of objects beforecalling dsmBeginGetData. If it is greater thanDSM_MAX_GET_OBJ |DSM_MAX_PARTIAL_GET_OBJ, then issue multipleGet call sequences.

FMV0285E The update action is invalid.

Explanation: The dsmUpdateFS or dsmUpdateObjaction is invalid.


User response: Correct the action value. Valid valuesare defined in dsmapitd.h and documented in ourUsing the API book.

FMV0275S • FMV0285E


FMV0286E The key file is missing.

Explanation: The key file for Tivoli Data Protectionapplication client for Oracle cannot be found.


User response: Ensure that you have ordered theTivoli Data Protection application client which containsTDP for Oracle, and install the key file.

FMV0287E The key file content is invalid.

Explanation: The key file content for Tivoli DataProtection application client for Oracle is invalid.


User response: Ensure that you have ordered theTivoli Data Protection application client which containsthe TDP for Oracle, and install the key file.

FMV0296I Encryption key passwords are not thesame. Please try again...

Explanation: Tivoli Storage Manager found that theencryption key passwords do not match.

System action: You are prompted for the encryptionkey password.

User response: Enter the correct encryption keypassword.

FMV0297E Error opening specified file.

Explanation: The specified file could not be located oropened.

System action: Attempts to open file failed.

User response: Make sure the file exists.

FMV0298E Session Rejected: The specified user idis currently locked

Explanation: The user id you specified is currentlylocked on the server.

System action: Session was not started.

User response: Check with your system administratorto find out why your user id is locked.

FMV0299E Scheduler cannot be started manuallybecause the value ofMANAGEDSERVICES option isSCHEDULE.

Explanation: if MANAGEDSERVICES SCHEDULE isindicated in the option file, the Tivoli Storage Managerscheduler cannot be started in the traditional manner.

System action: Scheduler stopped.

User response: If you are not going to use dsmcad tomanage the schedule anymore, stop dsmcad andremove MANAGEDSERVICES option from the optionfile.

FMV0302I Successfully done.

Explanation: The operation successfully completed.



FMV0304E The password is too short.

Explanation: The new password does not haveenough characters.

System action: The password is not updated on theserver.

User response: Choose a different password. Contactyour Tivoli Storage Manager administrator to lean thepassword requirements.

FMV0305E It is too soon after the previous updateto change the password.

Explanation: The password cannot be changed sincenot enough time has elapsed since the last passwordupdate.


User response: Try to change your password againlater.

FMV0306E The password was previously used.

Explanation: The new password that you entered waspreviously used.


User response: Choose a different password.

FMV0307E The password does not meet therequirements.

Explanation: The new password that you entered doesnot meet the requirements, such as the number ofspecial characters or digits.


User response: Choose a different password. Contactyour Tivoli Storage Manager administrator to learn thepassword requirements.



FMV0308E Remote operation failed to start onobj-name. Status: status reason: reason

Explanation: The request to start a remote operationhas failed for the indicated node and filespace. Thestatus and the reason for the failure are shown.

System action: Tivoli Storage Manager ended thecurrent operation.

User response: Contact your system administrator formore information.

FMV0309E Remote operation failed to start onobj-name. Status: status

Explanation: The request to start a remote operationhas failed for the indicated node and filespace. Thestatus of the failure is shown.

System action: IBM Tivoli Storage Manager ended thecurrent operation.


FMV0311E The tsmBuffHandle is invalid, or thevalue of dataPtr is invalid.

Explanation: An invalid value for a handle or dataPtrhas been passed into the API.


User response: There is a problem with the callingapplication. Verify the values of the tsmBuffHandle anddataptr passed to the API.

FMV0312E The number of bytes copied into thetsmBuffer is larger than the allowedvalue.

Explanation: An invalid number of bytes was copiedto a tsmBuffer.


User response: There is a problem with the callingapplication. Verify the number of bytes copied into thetsmBuffer.

FMV0313E dsmTerminate cannot finish because theapplication is holding on to 1 or moretsmBuffers.

Explanation: An application is trying to terminate asession, but is still holding some tsmBuffers.


User response: The application must return all buffers

for this session by calling tsmReleaseBuffer, and thenissue dsmTerminate.

FMV0314E An internal error occurred in thetsmBuffer array.

Explanation: An internal API buffer array erroroccurred.


User response: Try the operation again. If the problemcontinues, contact your system administrator or servicerepresentative.

FMV0315E Unable to open message text file.

Explanation: The system is unable to open themessage txt file (dscenu.txt or dsmclientV3.cat for AIX).On the AS/400 platform this file isQFMVAPI/QAFMVENU(TXT).


User response: Verify that the dscenu.txt file is in thedirectory pointed to by DSMI_DIR. For AIX, verify thatthe dsmclientV3.cat file has a symbolic link to/usr/lib/nls/msg/<locale>/dsmclientV3.cat .

FMV0316E Unable to use message text file.

Explanation: The system is unable to use the messagetext file (dscenu.txt or dsmclientV3.cat for AIX) becauseof an invalid header. On the AS/400 platform this fileis QFMVAPI/QAFMVENU(TXT).


User response: Install the message text file again.

FMV0317E Unable to use message text file.

Explanation: The system is unable to use the messagetxt file (dscenu.txt or dsmclientV3.cat for AIX) becauseof an invalid control record. On the AS/400 platformthis file is QFMVAPI/QAFMVENU(TXT).


User response: Install the message text file again.

FMV0318E Invalid value for DATEFORMATspecified.

Explanation: An invalid value is specified forDATEFORMAT.


User response: Specify a valid value.



FMV0319E Invalid value for TIMEFORMATspecified.

Explanation: An invalid value is specified forTIMEFORMAT.



FMV0320E Invalid value for NUMBERFORMATspecified.

Explanation: An invalid value is specified forNUMBERFORMAT.



FMV0321E msg parameter for dsmRCMsg is aNULL pointer.

Explanation: The message parameter for dsmRCMsgis a NULL pointer.


User response: Allocate enough space for the messageparameter.

FMV0322E no text available for this return code.

Explanation: The dsmRC parameter for dsmRCMsg isan unsupported return code.



FMV0323E partialObjOffset value for partial objectretrieve is invalid.

Explanation: The partialObjOffset value for partialobject retrieve is invalid.



FMV0324E partialObjLength value for partial objectretrieve is invalid.

Explanation: partialObjLength value for partial objectretrieve is invalid.



FMV0325E Partial Object Retrieve is not supportedon this server.

Explanation: The Tivoli Storage Manager serverspecified by the user does not support partial objectretrieve.


User response: Specify a Tivoli Storage Managerserver which supports the partial object retrievefunction.

FMV0326E This node has exceeded its maximumnumber of mount points.

Explanation: Either no tape or sequential disk mountpoints are permitted for this operation, or themaximum number of mount points allowed are alreadyin use. The operation can not be completed. The TivoliStorage Manager administrator defines the maximumnumber of mount points with the MAXNUMMPproperty of your node definition.

System action: The object is skipped

User response: If you are performing any other TivoliStorage Manager operations that might be using mountpoints, wait until those operations are complete, thentry the failed operation again. Otherwise contact yourTivoli Storage Manager administrator for furtherassistance

FMV0327E A duplicate object was found, operationcannot complete.

Explanation: A duplicate object was found, operationcannot complete.

System action: The requested operation failed.

User response: Try the operation with a different filespecification.

FMV0328E The specified objects failed the mergetest.

Explanation: The specified objects failed the mergetest, operation cannot complete.

System action: The requested operation failed.

User response: See documentation for the merge testparameters.

FMV0330E The dsmSetAccess access Type isinvalid.

Explanation: The dsmSetAccess accessType is invalid.




User response: The accessType must be one of thefollowing:

v atBackup

v atArchive

FMV0331E No files have been previously backedup for this filename/filespace.

Explanation: You tried to set access to files when nofiles for the specified filename, drive or file systemwere previously backed up.


User response: Ensure that the correct drive or filesystem was specified and that files are backed up foryou to set access.

FMV0332E No files have been previously archivedfor this filename/filespace.

Explanation: You tried to set access to files when nofiles for the specified filename, drive or file systemwere previously archived.


User response: Ensure that the correct drive or filesystem was specified and that files are archived for youto set access.

FMV0333E Unknown Remote Mover type

Explanation: The specified Remote Mover type isunknown.



FMV0334E An Operation for the requested nodeand filespace is already in progress.

Explanation: A request has been made to use a datamover to perform an operation for the indicated nodeand filespace. Since an operation for this node andfilespace is already in progress, the new operationcannot be performed.


User response: Retry the operation at a later time.

FMV0335E System resource in use

Explanation: A required resource is in use by anothercommand or process.


User response: Retry the operation at a later time.

FMV0336E Server plugin communication error

Explanation: Communication between a server pluginmodule and a NAS filer failed.



FMV0337E Server plugin detected unsupportedNAS filer operating system.

Explanation: A plugin module detected that a NASfiler is running an unsupported operating system oroperating system level.



FMV0338E An invalid operation was attempted ona node

Explanation: The operation is not valid.



FMV0339E The specified target storage pool is notdefined.

Explanation: The storage pool is not defined.



FMV0340E A target storage pool does not have thecorrect data format for the given nodetype.

Explanation: none



FMV0341E No associated data mover is defined forthe given node.

Explanation: none





FMV0342E The CRC received from the Server doesnot match the CRC calculated by theclient.

Explanation: The server sent a CRC for a buffer. Theclient calculated a CRC for the same buffer. These didnot match. The mismatch indicates a communicationfailure.

System action: In some cases, the client can indicatethe failure to the server and retry the operation.

User response: Check the trace log for additionalinformation and retry the operation. If the problempersists, contact your system administrator.

FMV0343E An invalid operation was attempted ona group leader or group member.

Explanation: An invalid operation was attempted on alogical group.

System action: The current operation stops.

User response: Retry a valid operation.

FMV0344E Cannot Send data with a zero bytesizeEstimate.

Explanation: You cannot send data for an object withsize estimate = 0.


User response: Set size estimate greater than 0 indsmSendObj.

FMV0345E Remote disk not defined.

Explanation: An operation was attempted on a remotedisk that is not defined.


User response: Define the proper remote disk.

FMV0346E Input destination does not matchexpected destination.

Explanation: Input destination does not matchexpected destination.


User response: Retry operation with properdestination.

FMV0347E Data mover is not available.

Explanation: Data mover is not available.


User response: Retry operation with a proper Datamover.

FMV0348E Operation failed because the copycontinue option was set to NO.

Explanation: Operation failed because the copycontinue option was set to NO.


User response: This abort code indicates that a storeoperation, like backup or archive failed because thecopy continue option was set to NO. The sysadmin willneed to resolve the problem on the server end.

FMV0349E Transaction failed because of a problemduring a store operation.

Explanation: Transaction failed because of a problemduring a store operation. This error is typical when thenext storage pool has a different copy storage pool listand we switch to this pool in the middle of atransaction.

System action: Transaction is aborted.

User response: Resend objects in separate transactions.

FMV0350E The current client configuration doesnot comply with the value of theDATAWRITEPATH orDATAREADPATH server option for thisnode.

Explanation: The values of the DATAWRITEPATHand DATAREADPATH server options specify where theclient is allowed to send data, and where data is readfrom. The values for the specified node name shouldcorrespond with the client configuration. For example,you will get this error message if DATAWRITEPATHcontains a LAN value and the client is configured touse LAN-free protocol, or vice versa.


User response: Check the client, server, and storageagent logs to determine why the client was not able tosend data LAN-free. Make sure the client configurationand server options are compatible.

FMV0351E The node or user does not have properauthority to perform this operation

Explanation: The node or user does not have properauthority to perform this operation.

System action: The transaction is ended.



User response: Check the authority for the specifiedobject.

FMV0352E The operation is not permitted due toserver licenses values.

Explanation: The node or user is trying to perform anoperation that either exceeds license values, or is notlicensed.

System action: The session is rejected or thetransaction is cancelled, ending the current operation.

User response: See your system administrator.

FMV0353E When using useTsmBuffers, dataBlkmust be NULL in calls to dsmSendObjand dsmGetObj.

Explanation: The value for dataBlk must be NULLwhen using useTsmBuffers.


User response: There is a problem with the callingapplication. Contact your application provider

FMV0354E Encryption is not allowed when usinguseTsmBuffers.

Explanation: useTsmBuffers does not supportencryption.


User response: Try the operation again, without usinguseTsmBuffers, or disable encryption for this operation.

FMV0355E This object cannot be restored/retrievedusing useTsmBuffers, because it iscompressed.

Explanation: useTsmBuffers does not supportcompression.


User response: Try the operation again, without usinguseTsmBuffers.

FMV0356E This object cannot be restored/retrievedusing useTsmBuffers, because it isencrypted.

Explanation: useTsmBuffers does not supportencryption.


User response: Try the operation again, without usinguseTsmBuffers.

FMV0357E When using useTsmBuffers, arestore/retrieve with partial objectrestore is not allowed.

Explanation: useTsmBuffers does not support partialobject restore.


User response: Make sure the calling application iseither using Partial object restore or useTsmBuffers.

FMV0358E No encryption key was found. If youare using -encryptkey=prompt makesure there is a value in theencryptionPasswordP field and thatbEncryptKeyEnabled is set to true.

Explanation: There was no encryption key found inthe password file, or no key was provided by theapplication.


User response: If you are using -encryptkey=prompt,make sure there is a value in encryptionPasswordP andthat bEncryptKeyEnabled is set to true.

FMV0359E Conflicting encryption key options havebeen specified.

Explanation: When using the ENABLEENCRYPTKEYoption, the parameter bEncryptKeyEnabled for theTivoli Storage Manager API dsmInitExIn_t andtsmInitExIn_t structures cannot be set to bTrue.


User response: Either remove theENABLEENCRYPTKEY option from the options file, orset the parameter bEncryptKeyEnabled to bFalse in theprogram using the Tivoli Storage Manager API.

FMV0360E The CAD cannot start because the valueof the MANAGEDSERVICES option isNONE.

Explanation: The CAD will not start ifMANAGEDSERVICES NONE is set in the option file.The CAD is designed to manage the web client orTivoli Storage Manager schedules. By specifyingNONE, the CAD will not manage any services.

System action: The CAD will stop processing.

User response: Specify either WEBCLIENT orSCHEDULER for the MANAGEDSERVICES option inthe option file then restart the CAD.



FMV0361I DIAG:




FMV0362E There are insufficient Windows systemresources to process this command.

Explanation: This problem can occur during backupof a shared directory. The most likely reason is the'IRPStackSize' setting on the computer that hosts theshared directory is too small.

System action: The file is skipped.

User response: Check the Windows event viewer forevent ID 2011 on the computer that hosts the shareddirectory. This event indicates that the configurationparameter IRPStackSize is too small. IRPStackSize is asetting of type DWORD located in Windows registrykey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters.If the IRPStackSize value is less than 20, orIRPStackSize is not specified, then set the value to 20,restart the system, and try the operation again. Thedefault IRPStackSize value is 15. Attention: Consultwith your Windows system administrator beforemaking changes to the Windows registry or theproblem persists after changing the IRPStackSize valueto 20.

FMV0400E License file could not be opened.

Explanation: The license file was not found, or couldnot be opened because of permissions or the file iscorrupted.


User response: Check permissions on file. See if thelicense file is in the correct place.

FMV0401E Read failure on the license file.

Explanation: The license file was not found, or couldnot be opened because of permissions, or the file iscorrupted.



FMV0402E Write failure on the license file.

Explanation: The license file was not found, or couldnot be opened because of permissions or the file iscorrupted.


User response: Check permissions on file. See iflicense file is in the correct place.

FMV0403E Data in the license file is not in a validformat.

Explanation: The license file is not valid.


User response: User needs to obtain a new license.

FMV0404E The checksum in the license file doesnot match the licenseregistration string.

Explanation: The registration string is not valid.



FMV0405E This is an expired try and buy license.

Explanation: The registration string is not valid.



FMV0410E Oracle passed invalid mode

Explanation: Invalid mode passed by Oracle.



FMV0411E Oracle passed null file name

Explanation: Null filename passed by Oracle.



FMV0412E Wrong data block size

Explanation: Wrong Block Size



FMV0361I • FMV0412E


FMV0413E Object exists

Explanation: Backup or Restore Object already exists.


User response: If backing up an object, be sure togenerate a unique object name.

FMV0414E Not same Oracle handle

Explanation: The handle passed from Oracle is not thesame handle that Tivoli Storage Manager passed back.



FMV0415E End of file reached

Explanation: End of file reached.


User response: None

FMV0416E Wrong Read State

Explanation: The operation must be in READ state.



FMV0417E Runtime API version is outdated

Explanation: Runtime API is lower than compile timeAPI.


User response: Use the WHAT command to find outthe compile time API level. Obtain the same or higherlevel of API library.

FMV0418E Wrong write state

Explanation: The operation must be in WRITE state.



FMV0419E Invalid flag passed

Explanation: Invalid flag passed from Oracle.



FMV0420W Warning! Restoring inactive system stateobjects is not recommended. Do youwish to continue?

Explanation: Restoring inactive system state objectsmay cause system instability. Examples of possibleproblems include:

v Applications that were installed after the time thesystem state was backed up cannot function properlyafter restoring the inactive system state

v Critical operating system updates installed after theinactive system state backup was made can nolonger be available, or may not function correctly.

Restoring inactive system state objects is notrecommended unless you are certain that this is whatyou need to do.

System action: If user responds with yes, the clientwill restore the object. If user responds with no, theclient will cancel the operation.

User response: Reply to the prompt. If you areunsure, reply no, and consult your systemadministrator or operating system vendor beforeproceeding further.

FMV0421W Unable to synchronize the nodepassword with the user id passwordprovided.

Explanation: The node password was not updateddue to the reason described in the error messagepreceding this one.

System action: The node password is not updated onthe server. Next time you run the client you will beprompted for the password again.

User response: See the preceding error message.

FMV0422W The selected journal location is anetwork drive and might not beaccessible from the journal service.Select a location on a local drive.

Explanation: It is not recommended to use a networkdevice as the location where journal databases arestored. Placing journal databases on a network devicecan prevent the journal service from running.


User response: Choose a local drive where journaldatabases will be stored.

FMV0423E Directory 'filespace namepath-namefile-name'cannot be created. Path does not exist.

Explanation: The operating system returned a "pathnot found" status when IBM Tivoli Storage Managerattempted to create the directory needed for AutomatedSystem Recovery (ASR). One possible reason is that a



multi disk system is restored to a single disk system.


User response: Please verify that you are restoring toidentical hardware and try again.

FMV0990W Options file 'file-name' could not befound. Default option values will beused.

Explanation: Common reasons for this warninginclude:

v The default options file does not exist, and

v You did not specify the -OPTFILE option whenstarting the Tivoli Storage Manager client, and

v the environment variable DSM_CONFIG was not set.

System action: Tivoli Storage Manager client assumesdefault values for all client options and continuesprocessing, using the default server name andassociated options found in the dsm.sys file.

User response: If the default system action isacceptable, you can eliminate this message by creatingan empty dsm.opt file in the installation directory.

If you have a client user options file (dsm.opt), eitherplace it in the installation directory or set theDSM_CONFIG environment variable to thefully-qualified path and file name of your options file.

Review the information on configuring Tivoli StorageManager in the Tivoli Storage Manager client manualspecific to your operating system. If the problempersists, ask your Tivoli Storage Manager administratorfor further assistance.

FMV0991I Tivoli Storage Manager scheduler islistening for server requests on port portnumber

Explanation: This message indicates the port numberon which the clients is listens for server requests. If theport number in the message differs from the defaultvalue or what you specified with the TCPCLIENTPORToption, it is because the port was in use by a differentprocess.


User response: Normally no further action is required.If you require Tivoli Storage Manager to use a specificport number, you need to configure your system orapplications so the number is avaible. Restart the TivoliStorage Manager client and confirm it uses the desiredport.

FMV0992E The destination filespace or drive letteris unavailable. For more details pleasesee dsmerror.log.

Explanation: The system is trying to restore or retrieveto a destination that cannot be reached. The specified

filespace name or drive letter is not valid, or does notexist, or you are specifying a local share name thatcannot be resolved.

System action: Objects which are part of this filespaceare not processed.

User response: Try the command again, and specify adifferent destination for the object that was notprocessed.

FMV0993E The source specification "source" hasinvalid format.

Explanation: The file system must be enclosed incurly braces and wildcards cannot be used except atthe lower level.

System action: The command processing isterminated.

User response: Correct the specification and try thecommand again.

FMV0994E Invalid string 'string' for virtual filespace name or group name specification.

Explanation: You entered a virtual file space name ora group name specification that contains wildcardcharacters.


User response: Enter a correct virtual file space nameand a group name and try again. Use the pick optionto display a list of groups from which you can selectone group.

FMV0995E Volume 'volume-name' could not belocked.



User response: Please verify that no other applicationis accessing the volume. During restore of an imageTivoli Storage Manager must have exclusive use of thevolume.

FMV1000E An unsupported communicationsmethod was specified.

Explanation: None.

System action: processing stops.

User response: Specify a communications interfacethat is supported by the Tivoli Storage Manager clienton your operating system. See the Tivoli StorageManager client manual for your operating system forfurther information on configuring Tivoli StorageManager client communications.



FMV1001E Volume being backed up was not asystem volume. Skipped.

Explanation: User specified to back up system volumeonly. This volume was not backed up since this volumeis not a system volume.

System action: Volume was not backed up.

User response: Use All option or use image backupcommand to backup this volume.

FMV1002I MOS image is being created. It maytake a while.

Explanation: Mini Operating System image is beingcreated. It may take a while to create it.

System action: Tivoli Storage Manager is gatheringnecessary information.


FMV1004W Node has exceeded max tape mountsallowed. Operation for 'filespace-name'will be tried again later.

Explanation: Node has exceeded max tape mountsallowed. The operation will be tried again later.

System action: The operation will be retried.

User response: Increase the number of allowed tapemounts for this node on the server to avoid thissituation again.

FMV1005I TCP/IP read error on socket = socket-id,errno = error-code, reason : 'error-reason'.

Explanation: An attempt to receive data using TCP/IPconnection failed. If reason : 'Connection reset by peer',it is possible that the server control connection timedout. This can occur if the file transfer time is greaterthan the IDLETIMEOUT value set on the server.

System action: TCP/IP connection to server fails.

User response: If the timeout was due to a large filetransfer time, you can ignore this message. The clientwill reconnect with the server automatically, finishtransferring the data, and send statistics. You can alsoconsider increasing the IDLETIMEOUT value in theserver options file.

FMV1006I TCP/IP write error on socket = socket-id,errno = error-code, reason : error-reason

Explanation: An attempt to send data using TCP/IPconnection failed.

System action: Connection to server fails.

User response: Retry the operation. If the problempersists, contact your system administrator.

FMV1007E Sending of object 'object-nameobject-nameobject-name' failed. There is nobackup copy group.

Explanation: The management class for this file(object-name) does not have a backup copy group. Eitherthe default management class does not have a backupcopy group, or an INCLUDE statement is attempting tobind the file to a management class that does not havea backup copy group.

System action: Tivoli Storage Manager did not backup the file.

User response: Run DSMC QUERY MGMTCLASS-DETAIL to view information about availablemanagement classes.

v If the file is being bound to the default managementclass, make sure the management class has a backupcopy group.

v If the file is being bound to a management classspecified in an INCLUDE statement, make sure thatthe management class has a backup copy group.

v If you have more than one Tivoli Storage Managerserver, make sure you are connecting to the correctserver.

v If you are unable to find a suitable managementclass, contact your Tivoli Storage Manageradministrator for further assistance.

FMV1008E Sending of object 'object-nameobject-nameobject-name' failed: No Archive CopyGroup

Explanation: The management class for this file(object-name) did not have an archive copy groupspecified.

System action: TSM did not back up the file.


FMV1009W An error occurred processing theoperating system include/excludestatements. The error was detectedwhile processing: subsystemname.

Explanation: The client encountered an error whileobtaining the automatic include/exclude statementsfrom the operating system. Possible reasons for thiserror include:

v The specified registry key cannot be opened forreading

v The entry under this key has incorrect data

System action: Processing continues without the fulllist of operating system include/exclude statements.

User response: Ensure that you have access to thespecified registry key and that entries are a MULTISZvalues that contain:

v Individual files

FMV1001E • FMV1009W


v Directories

v Wild card entries

v Environment variables

v /s switch (the /s switch is used on directory and/orwild card entries and signifies that all subdirectoriesof this directory should be excluded)

If the cause of this message can not be determined orresolved, contact IBM technical support for furtherassistance.

FMV1010E Error processing 'filespace-name':Unsupported file system operation.

Explanation: The file system does not support anoperation required to process the file or directory.

System action: The file or directory is skipped.Depending on the specific error encountered,processing on Solaris clients might stop.

User response: Verify that the file system is supportedby the Tivoli Storage Manager client. If a restore orretrieve failed, retry the operation to another location. Ifthe problem persists, look for other indications ofsystem problems. It may be necessary to run theoperating system utility that checks and repairs filesystem inconsistencies. If the problem still cannot beresolved, contact your Tivoli Storage Manageradministrator for further assistance.

FMV1015E The session is rejected. The server doesnot allow a signon of a client that is notarchive-retention protection enabled.

Explanation: The client cannot establish a connectionto the server because the server is enabled forarchive-retention protection enabled and the client isnot.

System action: The session is not started.


FMV1016I No eligible files matching 'pathname'were found.

Explanation: The backup or archive operationcompleted, but no files were processed. Possiblereasons for this include:

v The directory that was backed up or archivedcontains no files

v The files are excluded from backup or archive

System action: None

User response: Check the path you entered.

FMV1017E Session rejected: TCP/IP connectionfailure.

Explanation: An attempt to connect to the serverusing TCP/IP communications failed. This can be aresult of incorrect TCP/IP option settings in your clientoptions file. This error can also occur if the LANconnection went down or if your system administratorcanceled a backup operation.

System action: Session rejected. Processing stopped.

User response: Retry the operation, or wait until theserver comes back up and retry the operation. If theproblem continues, see your system administrator forfurther help.

FMV1018E Port port number is already in use

Explanation: The port specified by theTCPCLIENTPORT option is in use by a differentprocess.


User response: Contact the server administrator to setup a different port for server-initiated connections.Update the TCPCLIENTPORT with this new portnumber.

FMV1019E The volume could not be opened.

Explanation: An error occurred when Tivoli StorageManager tried to open the volume for a backup orrestore operation.

System action: The requested operation does not run.

User response: Examine the client error log foradditional messages related to this error. Verify that thevolume is available, and is not locked by anotherprocess. Try the operation again. If the problempersists, contact IBM technical support for furtherassistance.

FMV1020E System object backup failed.

Explanation: An error occurred while backing upWindows system object files. The backup did notcomplete.


User response: Ask your system administrator tocheck the error log. Restart the Windows serviceassociated with the system object indicated in the errorlog, and retry the backup operation

FMV1021E System object restore failed.

Explanation: An error occurred while restoringWindows system object files. The restore did notcomplete.




User response: Ask your system administrator tocheck the error log. Restart the machine, and thenrestore the system object indicated in the error logagain.

FMV1022E Cancel failed for node: node-namefilesystem: fs-name operation: op-typeerror: error

Explanation: The request to cancel a remote operationhas failed. The node, filespace, operation and reason forthe failure are shown.

System action: Tivoli Storage Manager operation notcancelled.


FMV1023E Session rejected: Node type mismatch

Explanation: Your node name is associated with adifferent type of operating system (such as OS/2 orAIX) and cannot be used on this system.

System action: Tivoli Storage Manager canceled thecurrent operation.

User response: If you need a new node name, seeyour system administrator to assign a new one to you.Generally, you have a unique node name for eachmachine and operating system pair that requires accessto the server.

FMV1024E Failed to update backup attributes onserver for 'backup type' backup for'filespace namepath-namefile-name', object id'object-id:object-id' return code 'return code'.

Explanation: Tivoli Storage Manager failed to updateattributes for the named backup object on the server.The server may not reflect correct state of the backup.


User response: Check preceding error messages inerror log for more information. Retry the operation. Ifproblem continues, contact your Tivoli StorageManager administrator.

FMV1025E Session rejected: Authentication failure

Explanation: Authentication failure. You entered anincorrect password.


User response: Enter your correct password. If youcannot remember the correct password, see yoursystem administrator to have a new one assigned foryour node name.

FMV1026E The session is rejected: There was acommunications protocol error.

Explanation: An unexpected network message wasreceived by the client. This could be caused by networkproblems or a programming error.


User response: Verify that your communication pathis functioning properly and try the operation again. Ifthe problem persists, contact your Tivoli StorageManager administrator for further assistance.

FMV1028S An internal program error occurred.

Explanation: Tivoli Storage Manager encountered anunexpected condition and can not continue theoperation. This might be a programming error.


User response: Try the operation again. If the problempersists, contact your Tivoli Storage Manageradministrator or IBM technical support for furtherassistance.

FMV1029E Communication with the Tivoli StorageManager server is lost.

Explanation: This message is issued after the sessionwith the Tivoli Storage Manager server is unexpectedlylost. The client error log might contain additionalinformation regarding this problem.


User response:

v Restart the Tivoli Storage Manager client and retrythe operation.

v If the problem persists, review the client error log forother messages that might be related to this problem.

v Verify that network connectivity exists between theTivoli Storage Manager client machine and the TivoliStorage Manager server machine.

v Contact your Tivoli Storage Manager administratorfor further assistance. The Tivoli Storage Manageradministrator can review the Tivoli Storage Managerserver activity log for additional information aboutthe problem.

FMV1030E The operating system refused a TivoliStorage Manager request for memoryallocation.

Explanation: Tivoli Storage Manager requires access tomemory in order to store information as processingproceeds. In this case, more memory was requestedthan the operating system would allocate. Possiblereasons include:






System action: Tivoli Storage Manager cannotcomplete the requested operation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units. Forexample, if a file specification contains several highlevel directories, run the Tivoli Storage Manager taskserially for each directory. If the Tivoli Storage Managertask is an incremental backup, use the option"-memoryefficientbackup=yes".



FMV1031E The attempt to establish a TCP/IPconnection timed out before theconnection was made.

Explanation: The Object of the connection attemptfailed to respond within the the allotted wait time. Inthe case of the B/A client, this message is preceded indsmerror.log by message FMV5216E that gives detailsof the connection that failed. The condition may betemporary.


User response:

v Restart the Tivoli Storage Manager client and retrythe operation.

v Check the client options file and verify thatTCPSERVERADDRESS and TCPPORT specify thecorrect TCP/IP address and port number for yourTivoli Storage Manager server.

v Verify that network connectivity exists between theTivoli Storage Manager client machine and the TivoliStorage Manager server machine.

v If the problem persists, see your Tivoli StorageManager administrator for further assistance.

FMV1032E An attempt to establish a TCP/IPconnection was rejected by the host

Explanation: An attempt to establish a TCP/IPconnection was rejected by the server.


User response: The server was not fully initialized, isnot currently running, was not enabled for TCP/IPcommunications, or an incorrect TCP/IP port number

was specified. If the problem continues, see yoursystem administrator.

FMV1033E An invalid TCP/IP address wasspecified.

Explanation: The TCP/IP address specified by theTivoli Storage Manager client's TCPSERVERADDRESSsetting could not be found on the network. Commonreasons for this error include:

v The TCPSERVERADDRESS client option specifies thewrong TCP/IP address for the Tivoli StorageManager server".

v The machine that hosts the Tivoli Storage Managerserver is not on the network.

v A network problem is preventing the Tivoli StorageManager client from reaching the machine that hoststhe Tivoli Storage Manager server.


User response: Verify that the TCPSERVERADDRESSand TCPPORT settings have the correct values for yourTivoli Storage Manager server. Use your operatingsystem's "ping" (or similar) utility to ensure that yourmachine can locate the machine that hosts the TivoliStorage Manager server across the network. Try theoperating again. If the problem persists, ask your TivoliStorage Manager administrator for further assistance.

FMV1034E The specified TCP/IP host name isunreachable

Explanation: The TCP/IP host name specified in theTCPSERVERADDRESS statement cannot be reached.


User response: Check your options file for the correctTCPSERVERADDRESS statement. See youradministrator for the correct name of the server.

FMV1035S Options file 'file-name' could not befound, or it cannot be read.



v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile you provided does not exist.

v The DSM_CONFIG (or DSMI_CONFIG if you areusing the IBM Tivoli Storage Manager API)environment variable specifies an options file thatdoes not exist.

v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile that you provided is not in the standard fileencoding of the system. For example, on Windowsthe expected file encoding is FMVI.



v You specified the -OPTFILE option when starting theIBM Tivoli Storage Manager client, but the optionsfile that you provided does not have appropriateread permissions for the user that is running theoperation.

System action: IBM Tivoli Storage Manager clientprocessing stops.

User response: Make sure that the options file youwant to use exists, it has the read rights set for the userthat is running the operation, and it is in the standardfile encoding of the system. For example, on Windowsthe expected file encoding is FMVI. Review theconfiguration information in the IBM Tivoli StorageManager client manual specific to your operatingsystem. If the problem persists, ask your IBM TivoliStorage Manager administrator for further assistance.

FMV1036S The option 'option' or the value suppliedfor it is not valid. It was found inoptions file 'file-name' at line number:number The complete entry: 'entry'

Explanation: The specified option in the Tivoli StorageManager options file (file-name) or the command line, isin error. Either the option itself or its value are invalid.For options that include a date or time specification,the format of the date or time might not match theformats specified by the DATEFORMAT orTIMEFORMAT options.


User response: Correct the option name or value. Foroptions that specify dates or times, ensure that thespecified date or time matches the DATEFORMAT andTIMEFORMAT settings. If -DATEFORMAT or-TIMEFORMAT are specified on the command line,they must precede the option that specifies the date ortime. For example, use -DATEFORMAT=3-FROMDATE=yyyy-mm-dd, instead of-FROMDATE=yyyy-mm-dd -DATEFORMAT=3.

FMV1037S Invalid keyword specified

Explanation: Tivoli Storage Manager found anincorrect keyword in the options file.


User response: Correct the options file with validentries.

FMV1038S Invalid option specified.

Explanation: An incorrect option was specified toTivoli Storage Manager.


User response: Correct the options used for runningTivoli Storage Manager.

FMV1039S The include or exclude pattern cannotbe parsed.

Explanation: The pattern is formatted incorrectly or istoo complex for Tivoli Storage Manager to interpret.


User response: Verify that the include or excludepattern is specified correctly. If the pattern is correct,then contact IBM technical support for furtherassistance.

FMV1040S Include/Exclude pattern is missing aclosing bracket

Explanation: The include or exclude pattern isincorrectly constructed. The closing bracket is missing.


User response: Correct the syntax for the pattern.

FMV1041S Include/Exclude pattern must start witha directory delimiter

Explanation: The include or exclude pattern must startwith a directory delimiter.



FMV1042S A beginning or ending directorydelimiter is missing from theInclude/Exclude pattern.

Explanation:

1. The include/exclude pattern has a '...' without abeginning or ending directory delimiter.

2. For Windows, the drive seperator is notimmediately followed by a directory delimiter.



FMV1043S Quotes are not matched

Explanation: The quotes specified in the pattern arenot the same and do not make a set.


User response: Correct the pattern by using matchingquotes in the syntax.

FMV1047E The destination file system isunavailable. The following object wasskipped: File space:'filespace-name'Pathname:' path-name' Filename:'file-name'

Explanation: The client is trying to restore or retrievethe specified object to a destination that is not valid,does not exist, or cannot be reached.



System action: The object is not restored or retrieved.Processing continues with the next object.

User response: Try the command again using adifferent destination.

FMV1048E Device 'volname' is not local

Explanation: The selected path is not a local deviceand therefore is not a valid object for image operations.

System action: The requested logical volumeoperation is not performed.

User response: Choose another object.

FMV1049E 'filename' is not a valid destination filefor image restore

Explanation: The filename you specified is not a validname for a file or it is a directory.

System action: Restore processing stopped.

User response: Specify a correct filename for imagerestore.

FMV1050E Before performing the VSS InstantRestore Tivoli Storage Manager cannotlock the volume 'volume-name'.

Explanation: The volume cannot be locked becauseanother application is accessing the file systems on thevolume.


User response: Stop or suspend the applications thathave handles open on the volume. For a file systemrestore, close applications that are accessing the filesystems that are used for the VSS Instant Restore.

If you cannot close the applications that are accessingthe file system, unmount the file system. After theunmount process is complete, mount the file systemand perform the VSS Instant Restore.

For more information, see the Tivoli Storage Managererror log file DSMERROR.LOG.

FMV1051I Invalid password

Explanation: You entered an invalid password.

System action: Tivoli Storage Manager cannot connectto the server without the correct password.

User response: Enter the password, or ask yoursystem administrator for the correct password.

FMV1052E Direct connection to the Storage Agentis not allowed.

Explanation: You cannot connect directly to theStorage Agent.


User response: To perform Lanfree operations usingthe Storage Agent, specify the ENABLELANFREEoption in your options file, and restart the process.

FMV1053I Existing file space filespace-name hasbeen renamed to filespace-name

Explanation: If the file space is for Windows systemstate, this message is issued when the Tivoli StorageManager backup-archive client detects multiple systemstate file spaces where the names differ only in case.The existence of multiple system state file spaces canoccur if, at some earlier time, your Tivoli StorageManager administrator renamed the system state filespace to the same name but with a different case or thecomputer's name was changed from all upper casecharacters to lower case or mixed case characters. If thefile space name represents a drive volume label, thenthis file space was created by an older Tivoli StorageManager backup-archive client.

System action: If the file space is for Windows systemstate, Tivoli Storage Manager will back up system stateto the file space containing the most recent backup. Theolder file space is renamed as specified in this message.Subsequent system state backups will continue to backup system state to the same (most recently used) filespace. If the file space name represents a drive volumelabel, Tivoli Storage Manager renames the file space tothe corresponding UNC name and continues to backup the drive to this renamed file space.

User response: No further action is necessary.However, if the file space is for Windows system state,then at some future time when you have determinedyou no longer need the older renamed system state filespace, you can ask your Tivoli Storage Manageradministrator to delete the older file space from TivoliStorage Manager storage.

FMV1054E Existing filespace filespace-name cannotbe renamed to new filespacefilespace-name. Tivoli Storage Managerreturn code = retcode.

Explanation: The client was unable to migrate a filespace name from the volume label naming conventionto the UNC naming convention.


User response: Check the client error log and theTivoli Storage Manager server activity log for any othermessages that might help identify the problem. If theproblem cannot be resolved, contact IBM technicalsupport for additional assistance.



FMV1055I Trying to rename existing filespacefilespace-name to new filespacefilespace-name, but drive letters do notmatch, old=drive-letter, new=drive-letter.Ignore the old filespace and backup tothe new filespace.

Explanation: Trying to rename the existing filespacename using the volume label to the UNC formatnaming convention but the drive letters do not match.Leave the existing filespace alone and create a newfilespace.



FMV1056E Share/network path share cannot beresolved. Path does not exist.

Explanation: For backup: Trying to backupshare/network, which either does not exist or does nothave the correct privilege to access the share. Forrestore : Trying to restore to a share/network path thatcannot be resolved. The directory path does not exist.


User response: Retry the command and specify adestination, or restore the directory tree first beforetrying to restore the share point.

FMV1057I File space filespace-name cannot berenamed to new file space filespace-name,because the new file space alreadyexists.

Explanation: The client was unable to migrate a filespace name from the volume label naming conventionto the UNC naming convention because the new filespace already exists on the Tivoli Storage Managerserver.

System action: The operation proceeds using the newfile space. The old file space is ignored.

User response: No action is necessary, but if the datain the old file space is no longer needed, it can bedeleted from the Tivoli Storage Manager server.

FMV1058E The restore destination cannot bereached.

Explanation: Either the destination file system isinvalid or it cannot be reached.


User response: Try the command again using adifferent destination.

FMV1059E Two inactive objects with the sameimage name were selected. Processterminates

Explanation: You selected more than one inactiveversion of the same image object (logical volume). Thesystem has no way to decide which you want torestore.

System action: The requested logical volume restore isnot performed.

User response: Retry the operation, selecting an activeversion or only one inactive version of the volume youwish to restore.

FMV1060E The specified path is not a mountedfilesystem

Explanation: You entered a file system name that doesnot correspond to a mounted file system for thissystem. It is possible the file system name ismisspelled, or simply that the file system is notcurrently mounted.


User response: Retry the operation, using name of amounted file system.

FMV1061E The specified device corresponds to amounted file system; you must specifythe file system by name.

Explanation: You entered a logical device name that ismapped to a mounted file system. This volume mustonly be referenced by its file system name.


User response: Try the operation again, using the filesystem name instead of the device name.

FMV1062E Only a single image may be selectedwhen a destination is entered.

Explanation: You selected more than one image object(logical volume) to be restored. You also specified adestination. The system cannot place more than oneimage into a single destination volume. When morethan one object is selected, each must be restored to itsoriginal location.

System action: The requested logical volume restore isnot performed.

User response: Retry the operation, selecting oneobject to be restored to the given destination, or retrythe operation without entering the destination.



FMV1063E The specified path is not a valid filesystem or logical volume name.

Explanation: None.

System action: The logical volume operation is notperformed.

User response: Try the operation again using a validpath.

FMV1064E An unexpected error occurred whileprocessing the image operation.

Explanation: None.


User response: Examine the client error log for anyadditional messages that may have been issued beforeor after this message. Correct any problems, if possible.If the cause of this message can not be determined orresolved, contact IBM technical support for furtherassistance.

FMV1065E Library version of the image utility doesnot match that of the Tivoli StorageManager API

Explanation: The current system has a mix of installedcomponents.


User response: Re-install all Tivoli Storage Managercomponents

FMV1066E The restore operation completedsuccessfully, but the file system couldnot be remounted.

Explanation: None.

System action: The file system is left unmounted.

User response: Use the mount command to mount thefile system. On AIX, run fsck if requested by theoperating system.

FMV1067E A call to a system function returned anunexpected error.

Explanation: If you are performing a JFS2 snapshotbased operation, it is possible that the snapshot was notlarge enough to contain all the changes made to thefilesystem after the snapshot was created. This couldcause the snapshot to become invalid therebypreventing Tivoli Storage Manager client from readingthe snapshot.


User response: Examine the client error log foradditional messages related to this error. Try the

operation again. If the problem persists, contact IBMtechnical support for further assistance.

If you are performing a JFS2 snapshot based operation,please use the default snapshotcachesize of 100% andensure that the volume group has sufficient disk spaceto allocate snapshots at least as large as the file systemand retry the operation.

FMV1068E Device is not local

Explanation: The selected path is not a local deviceand therefore is not a valid object for image operations



FMV1069E An error occurred while reading datafrom the device

Explanation: An error occurred while reading datafrom the device. Windows Only: This could be due tobad sectors on the drive.


User response: Retry the operation, then check theerror log for more information. Windows Only: Pleaserun chkdsk /r and retry the operation. If the problempersists, a possible workaround is to back up the entiredrive using a regular (non-image) backup. Pleaseensure that all your data is backed up. Then format thedrive using a full format (without the /q quick formatoption). Then restore the data and retry the imagebackup operation.

FMV1070E Write error

Explanation: An error occurred while writing data tothe device.


User response: Re-try the operation, check error logfor more information.

FMV1071E Invalid domain name entered:'domain-name'

Explanation: You entered an invalid domaindomain-name. Check whether the domain name is a filesystem and the file system is mounted. A directorycannot be specified in the domain option, unless it is avirtual mount point.

System action: Processing continues if there are otherfile systems in the domain option to back up.

User response: Enter a valid drive or file system name(domain).



FMV1072E Unable to continue operation; Drive'drive-name' has no volume label.

Explanation: The specified drive-name in the domainlist does not have a volume label.


User response: Use the system format utility to placea unique volume label on all drives on which youintend to run Tivoli Storage Manager.

FMV1073E The file space for domain 'domain-name'could not be found on the TivoliStorage Manager server.

Explanation: The specified file space was expected tobe found on the server, but it no longer exists. It ispossible that a command was issued to delete the filespace from the server while the current operation wasin progress.

System action: Tivoli Storage Manager processingstops.

User response: Try the operation again. If the problemrecurs, check the error log for any other messages thatmight indicate a reason for the failure. Try to correctany indicated problems, then try the operation again. Ifthe problem persists, contact IBM technical support forfurther assistance.

FMV1074W The operation was stopped by the user.

Explanation: The operation was stopped at the requestof the user. This usually occurs when the 'Q' key ispressed two times.



FMV1075E file name(line number)The operatingsystem refused a IBM Tivoli StorageManager request for memory allocation.

Explanation: IBM Tivoli Storage Manager requiresaccess to memory in order to store information asprocessing proceeds. In this case, more memory wasrequested than the operating system would allocate.Possible reasons include:


v The process in which the program runs has exceededthe maximum allocated memory.

v Some other error condition occurred. No memory isavailable.

System action: IBM Tivoli Storage Manager cannotcomplete the requested operation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units. Forexample, if a file specification contains several

high-level directories, run the IBM Tivoli StorageManager task serially for each directory. If the IBMTivoli Storage Manager task is an incremental backup,use the option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, you cancheck if the memory resource limit is too low byentering the following command: ulimit -a

Based on the resulting data, you can ask the UNIXsystem root user to increase the resource limit abovethe current default limit. The UNIX system root userhas the authority to increase resource limits.

FMV1076E The specified directory path 'pathname'could not be found.

Explanation: An invalid or unreachable directory pathwas specified.


User response: Try the operation again using a validdirectory path.

FMV1078S Unknown system error error-codeoccurred.

Explanation: An error unknown to Tivoli StorageManager error-code occurred within the client program.

System action: The client stops.

User response: Check the error log for any othermessages that might indicate a reason for the failure.Try to correct any indicated problems, then try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.

FMV1079E No file specification entered

Explanation: You did not enter a file specification asprompted.

System action: Tivoli Storage Manager did notcontinue with the requested operation.

User response: Enter a file specification to continue.

FMV1081E Invalid search file specification 'string'entered.

Explanation: You entered a file specification or searchstring that contains incorrect characters or containswildcard characters in the drive specification or filesystem name.


User response: Enter a correct file specification asdescribed in the appropriate Using the Backup-ArchiveClient book for the particular operating system.



FMV1082E Invalid destination file specification'file-name' entered

Explanation: You entered a destination file-namespecification that contains incorrect characters or haswildcard characters in the specification.


User response: Enter a correct file specification asdescribed in the appropriate Using the Backup-ArchiveClient book for the particular operating system.

FMV1083E No files have previously been archivedfor 'filespace-name'

Explanation: You tried to retrieve files when no filesfor the specified drive or file system (filespace-name)were previously archived.


User response: Ensure that the correct drive or filesystem was specified and that files are archived for youto retrieve.

FMV1084E No files have previously been backedup for 'filespace-name' or the specified filespace is invalid for the current operatingsystem.

Explanation: You cannot restore files. Either the filespace or drive is invalid, or no backup copies exist.


User response: Specify a valid drive or file space.Verify that backup copies exist.

FMV1086E File not found during Backup, Archiveor Migrate processing

Explanation: The file being processed for backup,archive or migrate no longer exists on the client.Another process deleted the file before it could bebacked up, archived or migrated by Tivoli StorageManager.



FMV1087E Access to the specified file or directoryis denied

Explanation: Access to the specified file or directory isdenied. You tried to read from or write to a file andyou do not have access permission for either the file orthe directory.


User response: Ensure that you specified the correctfile or directory name, correct the permissions, orspecify a new location.

FMV1088E File space 'filespace-name' does not exist

Explanation: The specified file space (domain) isincorrect or does not exist on the machine.


User response: Retry the operation specifying anexisting domain (drive letter or file system name).

FMV1089E Destination directory path lengthexceeds system maximum

Explanation: The path name specified plus the pathname in the restored file name combine to create aname whose length exceeds the system maximum.


User response: Specify a destination path that, whencombined, is less than the system maximum.

FMV1090E The LVM1 device is no longersupported by this client.

Explanation: The selected path refers to a volumedevice managed by LVM version 1. LVM 1 is no longersupported by this version of client and therefore is nota valid object for image operations.


User response: Use earlier versions of the client thatsupport LVM1 to perform the logical volume operation.Alternatively, you can upgrade to LVM2 and migratethe volume to LVM2. LVM2 is supported by this clientfor logical volume operations.

FMV1091E Communications error with serverduring object query

Explanation: An unexpected communications erroroccurred during an object query to the server.


User response: Verify that communications are activebetween the client and server machines. Server outages,processor outages, and communication controlleroutages can cause this error.

FMV1092W No files matching search criteria werefound

Explanation: You entered a search pattern or file namethat cannot be found in the server database.


User response: Ensure that your search pattern iscorrect, or specify a new search string.



FMV1093E Your Tivoli Storage Manager server doesnot support point-in-time processing.

Explanation: The client has requested a point-in-timequery or restore operation, but the Tivoli StorageManager server to which the client is connected doesnot support point-in-time operations.


User response: Make sure that you are connected tothe correct Tivoli Storage Manager server. If you areconnected to the correct server, then try the commandagain without specifying any point-in-time options.

FMV1096S Either the node does not exist on theserver or there is no active policy set forthe node.

Explanation: This error occurs when you try to accessanother node's data. Either the node is not registeredwith the Tivoli Storage Manager server, or there is noactive policy set for the node.


User response: Verify that the node whose data youare trying to access is registered with the Tivoli StorageManager server. If you have more than one TivoliStorage Manager server, make sure you are connectingto the correct server, then try the operation again. If theproblem persists, contact your Tivoli Storage Manageradministrator for further assistance.

FMV1097E The client help text cannot be read fromthe help file.

Explanation: The help file was opened successfullyand its table of contents are available, but there is aproblem reading the text from the help file.


User response: If the DSM_DIR environment variableis set, verify that it points to the directory containingthe current level of Tivoli Storage Manager programfiles, then try the operation again. If the problemrecurs, re-install the Tivoli Storage Manager clientsoftware. If the problem persists, IBM technical supportfor further assistance.

FMV1098E Process terminated; Program memoryexhausted.

Explanation: The program used all available storage.


User response: Free any unnecessary programs (TSRs)that are running, and retry the operation. Reducing thescope of queries and the amount of data returned canalso solve the problem.

FMV1099E File 'filename' not previously archived

Explanation: You tried to give access to a file, whichis not stored on the server.


User response: Ensure that the correct filename isspecified.

FMV1100E File 'filename' not previously backed up

Explanation: You tried to give access to a file, whichis not stored on the server.


User response: Ensure that the correct filename isspecified.

FMV1101E User is not authorized to encryptfile-space namedirectory_pathfile_name.

Explanation: The user is not authorized to encrypt thefile. Normally, only a IBM Tivoli Storage Managerauthorized user or a root user can use IBM TivoliStorage Manager encryption. However, a certaincombination of PASSWORDACCESS andENCRYPTKEY options may allow encryptionoperations by a non-authorized user.

System action: The file is not backed up or restored.

User response: Log in as a root or IBM Tivoli StorageManager authorized user and try the operation again.See IBM Tivoli Storage Manager Backup-Archive ClientInstallation and User's Guide for the correct usage ofthe ENCRYPTKEY option.

FMV1102E An excessive number of command linearguments are passed to the program.

Explanation: This command processing routinereceived more operands than it can use. The rules are:

v Query can contain only one file specification.

v Restore and Retrieve can contain two filespecifications.

v Archive, Incremental, and Selective can contain amaximum of 20 file specifications. To bypass the20-operand limit, use the -REMOVEOPERANDLIMIToption on the failing archive, incremental, orselective command.

Note: The Tivoli Storage Manager Client operates muchmore efficiently if it expands wild cards internally,rather than accepting the expanded list from the shell.


User response: Reduce the number of arguments andretry the operation. For UNIX-based systems, ensurethat you have surrounded the specification containingpattern matching characters with quotes. As analternative, use the -REMOVEOPERANDLIMIT option



on the failing archive, incremental, or selectivecommand.

FMV1103E Invalid management class entered

Explanation: You entered an invalid managementclass.

System action: Tivoli Storage Manager is unable to dothe requested operation.

User response: Retry the operation using a validmanagement class.

FMV1104E The management class for this file doesnot have a valid archive copy group.This file will not be archived.

Explanation: The management class for this file doesnot have an archive copy group specified. This file willnot be archived.


User response: Add a valid archive copy group to themanagement class, and then retry the operation.

FMV1105E The management class for this file doesnot have a valid backup copy group.This file will not be backed up.

Explanation: The management class for this file doesnot have a backup copy group specified. This file willnot be backed up.


User response: Add a valid backup copy group to themanagement class, and then retry the operation.

FMV1106E ENCRYPTKEY SAVE not configuredcorrectly. Encryption not used.

Explanation: This message is issued for TSMAuthorized Users and root users when ENCRYPTKEYSAVE and PASSWORDACCESS PROMPT options areset. Please note that these are the default values. Thesevalues do not allow encryption.

System action: The file is not encrypted.

User response: To save encryption keys, you mustchange configuration values. Add PASSWORDACCESSGENERATE to your system option file.

FMV1107E Invalid option/value: 'option'

Explanation: You specified an incorrect Tivoli StorageManager option or option value.

System action: For the command line client:Processing stops.

For the native GUI client: There is a small set ofoptions critical to the initialization of the client. If an

error is found in one of these, this message is presentedand the client terminates without further processing.

User response: Specify a correct Tivoli StorageManager option as defined in the appropriate Using theBackup-Archive Client book for the particular operatingsystem.

FMV1108E Invalid option (option) for the functioncommand

Explanation: There are two possible reasons for thismessage:

v The option option was specified for a command orsubcommand (function) that cannot make use of thatoption.

v The option appears on the initial command line andis not valid there.


User response: See the Backup-Archive ClientInstallation and User's Guide for correct use of thenamed option.

FMV1110E The client help file file-name could notbe opened.

Explanation: This usually occurs when the help filefile-name cannot be found.


User response: If the DSM_DIR environment variableis set, verify that it points to the directory containingthe current level of Tivoli Storage Manager programfiles, then try the operation again. If the problemrecurs, re-install the Tivoli Storage Manager clientsoftware. If the problem persists, IBM technical supportfor further assistance.

FMV1113E The snapshot cache location is not valid.

Explanation: The snapshot cache location must pointto a local volume that is formatted with NTFS. Thedefault cache location is on the same volume where thesnapshot is being performed. The operation willcontinue without snapshot support.

System action: The client does not execute thesnapshot backup operation.

User response: Specify a different snapshot cachelocation using the SNAPSHOTCACHELOCATIONoption.

FMV1114I Waiting for mount of offline media.

Explanation: The server is waiting for the requestedmedia to become available before the operation cancontinue.

System action: Tivoli Storage Manager waits forrequested data.

FMV1103E • FMV1114I



FMV1115W File 'file-namefile-namefile-name' excludedby Include/Exclude list

Explanation: You can not back up, archive, or migratefiles that are excluded.

System action: Tivoli Storage Manager does notprocess the file.

User response: If the file is intentionally excluded,then this message can be ignored. Otherwise modifythe include/exclude list, restart the client, and try theoperation again. Contact your Tivoli Storage Manageradministrator for further assistance.

FMV1116E The process is running in anon-interactive mode, but requires userinput.

Explanation: This process requires keyboard input,but non-interactive processes are unable to read inputfrom keyboard.


User response: Perform the following actions toresolve this error:

v Run the product in interactive mode.

v Ensure your password is set correctly.

FMV1117E The PICK and LATEST options are notvalid together

Explanation: During a restore, PICK and LATESToptions cannot be used together.


User response: Try again using either the PICK or theLATEST option.

FMV1118I Invalid file space number entered. Tryagain.

Explanation: The number that represents a file spacewas incorrect while you were using the PICK option.

System action: Tivoli Storage Manager waits for yourspecification.

User response: Enter a correct file space number.

FMV1119I Initiating the removal of 'filespace-name'file space.

Explanation: Indicates that file space deletion hasstarted on the specified filespace-name.



FMV1120E Removal of file space 'filespace-name'failed

Explanation: An attempt was made to delete afilespace (either NAS or normal) and it wasunsuccessful.

v Your client registration may not be authorized todelete filspaces on the server. Look for messageFMV1126E.

v The named filespace does not exist on the server.Look for message FMV1122W.

v Other causes which will be made known in messagesfollowing this one


User response: Take action as recommended by othermessages that accompanies this one. If so indicated, tryto remove the file space again. If the problemcontinues, your Tivoli Storage Manager administratorhas the authority to delete the file space for you.

FMV1121I A request for removal of file space'filespace-name' has been successfully sentto the server.

Explanation: Tivoli Storage Manager has requesteddeletion of the specified filespace-name. The deletionprocess may not have actually been completed whenthis message is displayed. To verify successful deletion,consult the server logs.

It is possible for errors to occur on the server duringthe deletion process, or the file space might containarchive objects in deletion-hold status. In either case,the file space will not be deleted.



FMV1122W File space 'filespace-name' does not existon the server. The file space might havebeen deleted by another client usingyour client's node name or anadministrator.

Explanation: The specified filespace-name does not existon the server. Your system administrator deleted thefile space or another client using your client’s nodename might have deleted it.



FMV1123E The vertical screen dimension is toosmall to display the Help directory.Increase your window height.

Explanation: Execution of the HELP commandrequires space for both the user prompts and at leastone line of the HELP directory.



System action: The help directory is not displayed,and the help command cannot complete.

User response: Increase the size of your displaywindow to allow more rows of text to be displayed.

FMV1125E Unmatched Quotes: 'string'

Explanation: The quotes specified in the pattern arenot the same and do not make a set.


User response: Correct the pattern using matchingquotes in the syntax.

FMV1126E The file space cannot be deleted becausethis node does not have permission todelete archived or backed up data.

Explanation: You cannot delete the file space dataunless your Tivoli Storage Manager administrator hasauthorized your node to do so. Authorization permitsyou to delete backup data, archive data, or both.

System action: Delete processing fails.

User response: Use the DSMC QUERY SESSIONcommand to verify your authorization. Ask your TivoliStorage Manager administrator to provide thenecessary authorization or to delete the file space foryou.

FMV1127E Your node does not have permission todelete archived files.

Explanation: You cannot delete archived files unlessyour Tivoli Storage Manager administrator hasauthorized your node to do so.

System action: Tivoli Storage Manager does not deletethe archived files.

User response: Use the DSMC QUERY SESSIONcommand to verify your authorization. Ask your TivoliStorage Manager administrator to provide thenecessary authorization.

FMV1128S The management class assigned todirectories does not exist.

Explanation: The management class named on theDIRMC option does not exist in your assigned policyset on the server. The error log contains an entryshowing the invalid management class name.


User response: Remove the current DIRMC optionfrom the client options file, then run DSMC QUERYMGMTCLASS -DETAIL to view information aboutavailable management classes. Make sure themanagement class you select has a backup copy group.If you have more than one Tivoli Storage Managerserver, make sure you are connecting to the correct

server. If you are unable to find a suitable managementclass, contact your Tivoli Storage Manageradministrator for further assistance.

FMV1129S There is no backup copy group in themanagement class used for directories.

Explanation: The DIRMC option names amanagement class that contains no backup copy group.


User response: Remove the current DIRMC optionfrom the client options file, then run DSMC QUERYMGMTCLASS -DETAIL to view information aboutavailable management classes. Make sure themanagement class you select has a backup copy group.If you have more than one Tivoli Storage Managerserver, make sure you are connecting to the correctserver. If you are unable to find a suitable managementclass, contact your Tivoli Storage Manageradministrator for further assistance.

FMV1130E The drive has no label. The operationcannot continue.

Explanation: Backup or archive of removable mediarequires that the media have a volume label. Anattempt was made to back up or archive data on aremovable volume that has no label.


User response: Create a volume label on theremovable media, then try the operation again.

FMV1131E A duplicate volume label exists. Theoperation cannot continue.

Explanation: For removable media, Tivoli StorageManager uses the volume label as the file space name.To prevent data from different volumes being stored inthe same file space on the Tivoli Storage Managerserver, backup or archive of removable media volumeshaving duplicate volume labels is not allowed.


User response: Change the volume labels on theremovable media volumes so that there are noduplicate labels. Then restart Tivoli Storage Managerand try the operation again.

FMV1132E 'Access rule' Access Rule already definedfor node 'node'. Old rule must be deletedbefore new one can be defined.

Explanation: You are trying to define authorization forthe specified node, which already has authorizationdefined.

System action: Tivoli Storage Manager did notredefine authorization for the specified node.



User response: Update the authorization, or delete theold rule and define a new one, or use the currentauthorization.

FMV1133W An expression might contain a wildcardnot enclosed in quotes.

Explanation: The command cannot be processedbecause a UNIX shell expands a wildcard expression,such as an asterisk (*) or a question mark (?), that hasno quotes.

If the expression contains no wildcard characters andyou wish to place more than the stated limit ofoperands on the Archive, Selective, or Incrementalcommand, add the -REMOVEOPERANDLIMIT optionto the command, and try it again.

System action: Command dependent.

User response: Enclose the wildcard expression inquotes, or add the -REMOVEOPERANDLIMIT optionand enter the command again.

FMV1134E Drive drive-name is an invalid drivespecification

Explanation: The specified drive-name was found to beinvalid; the drive probably has not been defined.

System action: Tivoli Storage Manager skips theinvalid drive and continues to the next drive.

User response: Check the invalid drive.

FMV1135E Drive drive-name1 is a virtual drive ofdrive-name2. It cannot be backed up orarchived.

Explanation: Drive drive-name1 was found to be asubstitute (SUBST) of drive drive-name2. The SUBSTdrive cannot be backed up or archived.

System action: The SUBST drive is skipped.Processing continues with the next drive.

User response: Do not specify any file specificationsfor a drive that is a substitute of another drive. Removeany explicit substitute drives from the DOMAINstatement or use the -<drive:> notation to remove asubstitute drive if ALL-LOCAL is specified.

FMV1136E Not file owner

Explanation: The file cannot be backed up because theclient is not the file owner.

System action: Tivoli Storage Manager skips the file.


FMV1137W Invalid Index 'number' skipped.

Explanation: An incorrect number was entered for theIndex.


User response: Correct the Index entry and retry theoperation.

FMV1138E The 'command-name' command must befollowed by a subcommand

Explanation: You entered an incompletecommand-name.


User response: Enter the correct syntax of thecommand and continue.

FMV1139W 'object-nameobject-nameobject-name' wasrestored as 'temp-name'. A reboot isrequired to complete the restore.

Explanation: The file being restored was in use byanother application, so it could not be immediatelyreplaced. The file will be replaced during the nextreboot of the operating system. It is important to notethat until the reboot occurs, the system or itsapplications might be unstable. The degree ofinstability depends on the criticality of the file to theoperating system or applications.

System action: Tivoli Storage Manager restored thefile with a temporary name, and instructed theoperating system to replace the original file with therestored file during the next boot of the operatingsystem.

User response: Reboot the machine as soon aspossible after the Tivoli Storage Manager restoreoperation ends.

FMV1140E Invalid format for Set Access command.

Explanation: The SET ACCESS command must haveat least three operands, the first of which must beeither BACKUP or ARCHIVE. A validly formed filespecification must follow.

System action: Processing stopped, the command isnot executed.

User response: Use the HELP SET ACCESS commandfor complete details of usage, then enter the SETACCESS command using the correct syntax.

FMV1141W Unknown command - command-name

Explanation: You entered an incorrect command-name.


User response: Enter the correct command.

FMV1133W • FMV1141W


FMV1143E The DIRSONLY and FILESONLYoptions are not valid together

Explanation: The DIRSONLY and FILESONLY optionscannot be used together.


User response: Try again using either the DIRSONLYor the FILESONLY option.

FMV1144W Password authentication not active onserver

Explanation: None.


User response: Because password authentication isturned off on the server, you do not need to update thepassword.

FMV1145E The maximum macro nesting level hasbeen exceeded. Macros may be nestedup to 10 levels.

Explanation: Tivoli Storage Manager allows macros toinvoke other macros, for example, macro 'A' invokesmacro 'B' which, in turn, invokes macro 'C'. This isnesting to 3 levels. The limit is 10 levels (the initalmacro plus nine levels of calls within macros currentlyexecutng). There is no limit to the number of differentmacro calls that may be made within a macro as longas the calls are not nested.

System action: The macro is ignored and an error isreturned.

User response: Reduce the level of macro nesting.

FMV1146E Macro file 'file spec' cannot be opened.

Explanation: A macro command has been entered thatspecifies the macro file name shown. However, that filecannot be opened for reading.


User response: Enter the command with the propermacro name.

FMV1147E File is temporarily unavailable.

Explanation: File is temporarily unavailable.


User response: Check and see if file is locked by otherprocess. If not, retry the command.

FMV1148I 'Command-name' command successfullycompleted

Explanation: The specified command-name wassuccessfully completed.

System action: Tivoli Storage Manager completed thecommand.


FMV1149E No domain is available for incrementalbackup. The domain may be empty orall file systems in the domain areexcluded.

Explanation: An incremental backup was started, butno domain was selected. Possible reasons for thismessage include:

v An attempt was made to back up a file system that isexcluded with the EXCLUDE.FS option.

v The DOMAIN is empty. That is, a DOMAINstatement excludes one or more file systems, but noDOMAIN statements include any file systems.

v DOMAIN ALL-LOCAL is in effect but the systemhas no local file systems.


User response: Verify that the DOMAIN statementsare properly configured and try the backup again.DOMAIN statements can be in client option files(dsm.opt, dsm.sys), client option sets, scheduledefinitions, and scripted Tivoli Storage Managercommands. Corrective actions include:

v Make sure the DOMAIN option settings specify thefile systems you want to back up.

v If a file system that should be backed up is excludedby an EXCLUDE.FS statement, remove theEXCLUDE.FS statement.

v If a file system that should not be backed up is listedin a DOMAIN statement, remove the file systemfrom the DOMAIN statement.

v Make sure the DOMAIN is not empty. That is, if anyDOMAIN statements exclude file systems frombackup, make sure the DOMAIN statements includethe file systems that should be backed up.

FMV1150E Unable to restore current user profilebecause you are running as a localsystem account.

Explanation: The local system account does not have aprofile. Therefore you cannot restore its profile.


User response: Log on to the user whose profile youwant to restore.



FMV1151E 'drive-name1' is not a cluster disk.

Explanation: The indicated file system is not a clusterdisk. Because the CLUSTERNODE option is set to YES,the file system cannot be backed up or archived.


User response: If the CLUSTERNODE option isincorrectly set to YES, then change the option to NOand try the operation again. Otherwise see the clientmanual for further information about configuring theTivoli Storage Manager client to run in a clusterenvironment.

FMV1152W The kernel level is below the requiredlevel for LVM support. No LVMvolumes will be available for imageoperations.

Explanation: The LVM support for image operationsrequires kernel level to be minimum at 2.6. LVMvolumes will not be recognized by the Tivoli StorageManager client.

System action: All subsequent logical volumeoperations on LVM volumes will fail.

User response: Use earlier versions of the client thatsupport LVM1 to perform the logical volumeoperations. Alternatively, you can upgrade the kernel tothe required level to fully utilize logical volumeoperations on LVM2.

FMV1153E 'drive-name1' is a cluster disk.

Explanation: The indicated file system is a clusterdisk. Because the CLUSTERNODE option is set to NO,the file system cannot be backed up or archived.


User response: If the CLUSTERNODE option isincorrectly set to NO, then change the option to YESand try the operation again. Otherwise see the clientmanual for further information about configuring theTivoli Storage Manager client to run in a clusterenvironment.

FMV1154E Object name 'filespacenamepath-namefile-name' contains aninvalid multibyte sequence for thecurrent locale.

Explanation: An illegal multibyte sequence for thecurrent locale was found in the object name. Either thepath or file name has been corrupted or is coded in alanguage other than that of the current locale.

System action: Object skipped.

User response: If the file name and path are notcorrupted, process the file in the locale for which it isvalid.

FMV1155E No domain is available for imagebackup.

Explanation: An image backup was started, but nodomain was specified.


User response: Choose a domain and restart theimage backup. Set the image domain using thedomain.image option in your dsm.opt file, eithermanually, or by using the GUI preferences editor.

FMV1156E NODENAME cannot be the localmachine name when CLUSTERNODE isset to YES

Explanation: When Tivoli Storage Manager is runningas a cluster node, the node name cannot be the localmachine name.


User response: Change the node name either to thecluster name or to any other name, and restart TivoliStorage Manager.

FMV1157E The registry cannot be backed up orrestored when the client is running as acluster node.

Explanation: When the CLUSTERNODE option is setto YES, the registry cannot be backed up or restored.

System action: The registry is not backed up orrestored.


FMV1158E The event logs cannot be backed up orrestored when the client is running as acluster node.

Explanation: When the CLUSTERNODE option is setto YES, the event logs cannot be backed up or restored.

System action: The event logs are not backed up orrestored.




FMV1159E The specified file is being used byanother process

Explanation: The specified file is being used byanother process. You tried to read from or write to afile that is currently being used by another process.



FMV1162E Filesystem could not be mounted

Explanation: The system call to mount the file systemfailed.

System action: The file system remains unmounted.

User response: Use the mount command to mount thefile system. On AIX, run fsck if requested by theoperating system.

FMV1163E Filesystem could not be unmounted.

Explanation: The system call to unmount the filesystem failed.


User response: Make sure the device or file system isnot being accessed, then retry the operation.

FMV1164E Filesystem is not mounted

Explanation: The named file system is not currentlymounted. It must be mounted for Tivoli StorageManager to perform an image backup.


User response: Mount the file system.

FMV1165E Destination is smaller than source

Explanation: The space allocation for the selecteddestination is smaller than the source.

System action: The restore operation is not performed.

User response: Choose a different, bigger destinationor increase the size of the destination file space.

FMV1166E Source and destination are not the samefile system type.

Explanation: The source and destination file systemtypes do not match.


User response: Choose a destination that has the same

file system type as the source.

FMV1168E ERROR: could not create image object.

Explanation: Creation of the image object failed forone of the following reasons:

v The image command was executed by a non-rootuser

v The image plugin library was not found.

System action: The requested logical volume functionis not performed.

User response: Retry the operation after correcting thecause for failure.

FMV1169W There is no table of contents forimage-name.

Explanation: The image item for which a table ofcontents was requested is either a RAW logical volumeor it was backed up without the -TOC option.

System action: No table of contents is displayed.

User response: Select another image object for TOCdisplay.

FMV1170I Invalid selection number entered. Tryagain.

Explanation: You entered a number not shown in thelist of images. It is either less than one or greater thanthe highest item number displayed.

System action: Tivoli Storage Manager waits for youto enter a valid selection.

User response: Enter a number from the list or 'Q' toquit.

FMV1177E Must specify a path for this operation.

Explanation: A path must be specified for thisoperation to execute successfully.


User response: Specify a valid path and execute thecommand again.

FMV1181E There was a communication failure withthe journal service.

Explanation: An error occurred using named pipecommunication with the journal service.


User response: Restart the journal service, then try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.



FMV1183E An unknown error occurred whileprocessing system object 'sys-obj-name':MS API function 'func-name' failed witherror error (error)

Explanation: An unknown error occurred whileprocessing a system object. The error informationcaptured indicates the reason for the failure. Thisinformation can be used to diagnose the problem.



FMV1184W The command subcommand command isnot supported on this client.

Explanation: The command subcommand command isnot supported for the client running on this operatingsystem on this computer.

System action: The command is not processed.


FMV1185E The help search argument you supplied"string" is either too long or containsunmatched quotes.

Explanation: Valid arguments are the names of thingslike section numbers, command names, option namesand message numbers. All of these search argumentsare short and none requires quoting.

System action: The help request is not executed andyou are given another chance to enter a validargument, display the table of contents, or exit help.

User response: Respond to the subsequent prompt asdirected.

FMV1186I The help file contains no message helpsection. Requests for message help willall result in topic not found. Enter asection number, option name, commandname, or a command and subcommand.Otherwise press enter or 't' to displaythe table of contents or 'q' to exit help:

Explanation: The named file does not have the propercontent to support the help command for messages.The initial scan of the help file found no messagessection.

System action: The help command pauses and allowsyou to make another selection.

User response: During installation of Tivoli StorageManager a proper help file was created. Your systemadministrator can assist you with retrieving the originalhelp file to replace the named invalid file.

FMV1187E The named helpfile "filename" hasinvalid content.

Explanation: The named file does not have the propercontent to support the help command. One or moresections could not be identified.

System action: The help command is terminated.

User response: During installation of Tivoli StorageManager a proper help file was created. Your systemadministrator can assist you with retrieving the originalhelp file to replace the named invalid file.

FMV1188E The selected filesystem is managed byHSM, and therefore is not a valid objectfor image operations

Explanation: Due to the nature of HSM, image backupis not allowed on managed filesystems.



FMV1189E The DIRSONLY and V2ARCHIVEoptions are not valid together

Explanation: The DIRSONLY and V2ARCHIVEoptions cannot be used together.


User response: Try again using either the DIRSONLYor the V2ARCHIVE option.

FMV1190E Symbolic link 'linkname' to 'target' wassuccessfully deleted.




FMV1191E Unable to delete symbolic link 'link'.




FMV1192E Specifying the error log 'link' as asymbolic link is not allowed.


System action: The symbolic link 'linkname' is deleted,



the error log is recreated, and processing stops.


FMV1193E Specifying the trace file 'link' as asymbolic link is not allowed.

Explanation: For reasons of security and systemintegrity, the trace file 'linkname' cannot be a symboliclink.


User response: Use the TRACEFILE option to specifythe actual trace file location without the use ofsymbolic links.

FMV1199E The PRESNAPSHOTCMD commandfailed. The image snapshot backup willnot be executed.

Explanation: The command specified by thePRESNAPSHOTCMD option must completesuccessfully in order to execute the image snapshotbackup. If the command completed with a return codeof 0 (zero), it is considered to have completedsuccessfully. If the command completed with any otherreturn code, it is considered to have failed. If thecommand failed then the image snapshot backup is notexecuted.

System action: The client does not execute the imagesnapshot backup operation.

User response: Identify and repair the problem thatcaused the command to fail. If a non-zero return codeis normal for this command, then consider wrappingthe command in a script that always exits with a returncode of zero.

FMV1200W The POSTSNAPSHOTCMD commandcompleted with a non-zero return code.

Explanation: If the command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code, then the image snapshot backupoperation will continue, but with a warning-levelresult. Note that the result of thePOSTSNAPSHOTCMD command will not supercede ahigher result from the image snapshot backupcommand. For example, if the image snapshot backupcommand completed with a return code of 12, theimage snapshot backup will be considered to havecompleted with a return code of 12, regardless of theoutcome of the POSTSNAPSHOTCMD command.

System action: The image snapshot backup continues,but with a warning return code of at least 8.

User response: Identify and repair the problem that

caused the command to fail. If a non-zero return codeis normal for this command, then consider wrappingthe command in a script that always exits with a returncode of zero.

FMV1201E Tivoli Storage Manager cannot build adirectory path because a file exists withthe same name as the directory.

Explanation: None


User response: Remove or rename the file that has thesame name as the directory. Alternatively, you canrestore the directory to a different location.

FMV1202E TOC backup for the image failed. Checklog files.

Explanation: An error occurred during backup of thetable of contents. Check the error log for moreinformation.


User response: Check error log.

FMV1203E Table of Contents not available forselected backup set. Please contactserver administrator.

Explanation: There is no TOC for selected backup set

System action: Expansion of selected backup set willnot be possible. Will only be able to restore the wholebackup set.

User response: Please contact server administrator toregenerate TOC for backup set before backup set can beexpanded.

FMV1204E This client is not supported by theTivoli Storage Manager express server

Explanation: This client is not supported by the TivoliStorage Manager express server. This can occur if:

1. the client is configured as an Tivoli StorageManager express client using the CLIENTVIEWoption

2. the client is trying to connect to an Tivoli StorageManager express server.


User response: Log in using a supported TivoliStorage Manager express client.



FMV1205E This is not a supported Tivoli StorageManager express platform

Explanation: This is not a supported Tivoli StorageManager express platform.


User response: Log in using a supported TivoliStorage Manager express client.

FMV1206E TOC backup of a raw device is notsupported. But the raw device is backedup.

Explanation: TOC backup of a raw device is notsupported. But the raw device is backed up.

System action: Raw device is backed up with no TOCobject.

User response: NONE.

FMV1207E No TOC has been previously backed upfor this file system.

Explanation: The user is trying to query the TOC of afile system. TOC backup for that file system has notbeen previously done.

System action: Query stopped.

User response: Backup the file system again with-TOC option.

FMV1209E The option_name option is not supportedwith the command_name command usingthe -FILELIST option.

Explanation: The specified option is not supportedwith the specified command when the -FILELISToption is also specified.


User response: >Do not specify the offending optionwhen the -FILELIST option is specified with thiscommand.

FMV1212I Invalid Process number entered. Tryagain.

Explanation: You entered a number not shown in thelist of processes. It is either less than one or greaterthan the highest item number displayed.



FMV1213W Snapshot image backup is not possiblefor device device-name. starting staticimage backup.

Explanation: On Linux platforms, snapshot imagebackup is only possible for logical volumes created bythe Linux logical volume manager (LVM). Since thedefault image backup type is snapshot, backing up apartition which is not created using LVM automaticallyleads to a static image backup.

System action: Snapshot image backup will failover tostatic image backup

User response: To avoid this message, use theimagetype option to specify static or dynamic imagebackup.

FMV1214E The logical volume group does not haveenough free space to contain the volumesnapshot.

Explanation: The snapshot is created in the volumegroup that contains the logical volume being backedup. There is insufficient free space in the volume groupto contain the snapshot.

System action: The operation ends.

User response: Decrease the SNAPSHOTCACHESIZEvalue or make additional space available in the logicalvolume group. Then try the operation again.

FMV1215E On volumes that are RAW or formattedFAT32 the snapshot cache locationcannot be located on the same volumethat is being backed up.

Explanation: When the snapshot cache location islocated on the same volume that is being backed up thevolume must be formatted with NTFS. The defaultcache location is on the same volume where thesnapshot is being performed.

System action: The client does not execute the imagesnapshot backup operation.


FMV1216E Not authorized to run Tivoli StorageManager. See the administrator for yoursystem.

Explanation: The system options file for the serverthat you are attempting to connect to contains a userentry, a group entry, or both a user and group entry.Your user ID, or group ID, was not found in any of theentries. You are currently not authorized to run TivoliStorage Manager to this server.

System action: Tivoli Storage Manager initializationfails and the program ends.



User response: See the Tivoli Storage Manageradministrator for your system, and ask to be added tothe user or group list for this server.

FMV1217E Server name not found in SystemOptions File

Explanation: The system options file does not containthe SERVERNAME option.


User response: See the Tivoli Storage Manageradministrator for your system, and make sure that thesystem options file contains the server name.

FMV1218E TCPSERVERADDRESS not defined forthis server in the System Options File

Explanation: The TCPSERVERADDRESS for thisserver is not defined in the server name stanza in thesystem options file.


User response: See the Tivoli Storage Manageradministrator for your system, and make sure that theserver to which you are trying to connect, has a validTCPSERVERADDRESS defined in the system optionsfile.

FMV1219E A virtual node name must not equaleither a node name or the system hostname.

Explanation: A VIRTUALNODENAME option wasentered with a name the same as either a NODENAMEoption or the system host name.

System action: Initialization fails and the programends.

User response: If the virtual node name entered wasthe same as the host name, remove the virtual nodename option. If it was the same as the node nameoption, you can remove either one, depending upon theintended usage. Node name is used to assign analternate name to your system. Virtual node name isused to access another system's server data.

FMV1220E The Tivoli Storage Manager server isout of resources.

Explanation: A lack of a storage resource or amaximum value condition does not allow any newactivity.


User response: Try the operation again at a later time.If the problem continues, contact your Tivoli Storage

Manager administrator to isolate what resource isunavailable. The Tivoli Storage Manager administratorcan check the Tivoli Storage Manager server activity logfor messages that might explain the problem.

FMV1221E Transaction aborted

Explanation: The current transaction between theserver and the client stopped. A server, client, orcommunication failure cannot be recovered.


User response: Retry the operation. If the problemcontinues, see your system administrator to isolate theproblem.

FMV1222E Disk space limit for this process reached

Explanation: The disk space allocated for the clientowner is full.


User response: Free up disk space and retry therestore or retrieve operation.

FMV1223E File is not compressed; System failure.

Explanation: A file that was flagged as compressedwas not compressed, and the system failed.


User response: See your system administrator toreport this problem. This error is a system failure.

FMV1224E File compressed on a different clientmachine that has more memory

Explanation: You are trying to restore a file that wasbacked up and compressed on another clientworkstation that had more memory than your clientworkstation. You cannot restore this file. When the fileis restored, it is expanded and your workstation doesnot have enough memory.

System action: Tivoli Storage Manager canceled theoperation.

User response: Obtain a machine with more memoryand retry the operation.

FMV1225E Insufficient memory for filecompression/expansion

Explanation: Not enough memory is available to dodata compression or expansion. For a restore orretrieve, the file cannot be recalled from the server untilmore storage is made available. For a backup orarchive, try running without compression if storagecannot be made available.




User response: Free up extra storage for the operationto continue, or run the backup or archive processwithout compression enabled.

FMV1226E Destination file or directory is writelocked

Explanation: The file or directory being restored orretrieved from the server cannot be written to becausethe destination is write locked. Another operationmight have the file open and will not allow it to beupdated.


User response: Either determine which operation hasthe file write locked, or restore the file to another nameor location.

FMV1227E Processing stopped; Disk full condition

Explanation: No more files can be restored orretrieved because the destination disk is full.


User response: Free up disk space, or restore orretrieve the file to another disk.

FMV1228E Sending of object 'object-nameobject-nameobject-name' failed.

Explanation: The specified file (object-name) cannot besent to the server. This message is accompanied by atleast one other message that has more specificinformation about why the file could not be processed.


User response: Check previous messages pertaining tothis file that indicate the reason for the failure. Whereapplicable, correct the conditions that prevented the filefrom being sent to the server. The specific correctiveactions will depend on the reason for the failure.

FMV1229E MODE=INCREMENTAL is not valid onfile-space. Image backup not processed.

Explanation: Because the file space has been thesubject of at least one progressive incremental backup,the MODE=INCREMENTAL option (incremental byimage date) cannot be used with the backup imagecommand.

System action: File system skipped.

User response: If an image backup of the named filespace is desired, retry the command without theMODE=INCREMENTAL option. To prevent thisbehavior in the future, delete the file space from theserver and do only BACKUP IMAGE -mode=selectiveand BACKUP IMAGE -mode=incremental from thatpoint on.

FMV1230E Stale NFS File Handle

Explanation: An NFS file system becomes stale.


User response: Check the NFS mounted filesystem.

FMV1231E No file handles available

Explanation: All file handles for your system arecurrently in use. No more are available.


User response: Either free some file handles by endingother processes, or modify your system setup to allowfor more files to be open at the same time.

FMV1232E The file exists and cannot beoverwritten.

Explanation: The file being restored or retrieved existsand cannot be overwritten due to lack of authority oraccess permissions.


User response: Verify that you have sufficient accesspermissions to overwrite the file, then try the operationagain. If the problem persists, contact your systemadministrator or Tivoli Storage Manager administratorfor further assistance.

FMV1233E An invalid file handle was passed;system error.

Explanation: An internal system error occurred: A fileoperation failed because of an invalid file handle.


User response: Try the operation again. If the failurepersists, obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your Tivoli Storage Manageradministrator can help you configure the trace.

FMV1234E Protocol violation

Explanation: A communications protocol erroroccurred. The communication subsystem is notproperly defined or is itself in error.


User response: Verify that the communicationprocesses are operating properly, and then retry theoperation.



FMV1235E An unknown system error has occurredfrom which Tivoli Storage Managercannot recover.

Explanation: An unknown error occurred. This mightbe a low-level system or communication error fromwhich Tivoli Storage Manager cannot recover.


User response: Try the operation again. If the problempersists, review the Tivoli Storage Manager error logfor any related messages. Obtain a service trace thatcaptures the problem and contact IBM technicalsupport for additional assistance. Your Tivoli StorageManager administrator can help you configure thetrace.

FMV1236E An unexpected error occurred.

Explanation: This is usually caused by a low-levelsystem error or communication error from which TivoliStorage Manager cannot recover.


User response: Examine the client error log for anyadditional messages that might be related to thisproblem. Try the operation again. If the problempersists, contact Tivoli Storage Manager technicalsupport for further assistance.

FMV1237E A problem has occurred on the TivoliStorage Manager server.

Explanation: The Tivoli Storage Manager client errorlog and the Tivoli Storage Manager server activity logmight contain additional information about this error.


User response: Try the operation again. If the problempersists, examine the Tivoli Storage Manager clienterror log and Tivoli Storage Manager server activity logfor additional information about this error. If theproblem cannot be resolved, then obtain a SERVICEtrace that captures the problem and contact IBMtechnical support for additional assistance. Your TivoliStorage Manager administrator can help you configurethe trace.

FMV1238S A policy management problem hasoccurred on the Tivoli Storage Managerserver.

Explanation: The Tivoli Storage Manager client errorlog and Tivoli Storage Manager server activity log maycontain additional information about this error.

System action: Processing is stops.

User response: Try the operation again. If the problempersists, examine the Tivoli Storage Manager clienterror log and Tivoli Storage Manager server activity log

for additional information about this error. If theproblem cannot be resolved, then obtain a SERVICEtrace that captures the problem and contact IBMtechnical support for additional assistance. Your TivoliStorage Manager administrator can help you configurethe trace.

FMV1241E File is in use; Write permission denied.

Explanation: The current file cannot be opened towrite to because it is currently being run by anotheroperation.


User response: Stop the operation that is running thefile and retry the operation, or restore or retrieve thefile to a different name or directory.

FMV1242E Too many symbolic links were detectedwhile resolving name

Explanation: While trying to resolve the file name, toomany symbolic links were found.


User response: Ensure that you do not have a loopingsymbolic link for the file.

FMV1243E The file name is too long and can not beprocessed by Tivoli Storage Manager

Explanation: The size limit for file names may vary byoperating system. The most common limit is 256characters. The file name being processed exceeds thelimit supported by Tivoli Storage Manager on thissystem.


User response: Enter HELP FILE SPEC or see theclient manual for the operating system on which youare receiving this error. The "File specification syntax"section of the manual explains file name lengthssupported by Tivoli Storage Manager.

FMV1244E File system is locked by system

Explanation: File system cannot be accessed because itis locked by the system.

System action: Tivoli Storage Manager cannotcomplete the operation.


FMV1245E The file has an unknown format.

Explanation: Tivoli Storage Manager tried to restore orretrieve a file, but it had an unknown format.


User response: The file was either backed up by



another application, or the data is invalid. If the filebelongs to this system, try the operation again. If theproblem persists, contact IBM technical support forfurther assistance.

FMV1246E A command-line argument exceeded themaximum length (maximum length) for asingle token.

Explanation: Command-line arguments may notexceed maximum length characters.


User response: Correct the command and retry theoperation.

FMV1247I Waiting for files from the server...

Explanation: Restore request has been sent to theserver. The wait time depends on how many files youare restoring.

System action: Tivoli Storage Manager waits for filesto restore from the server.


FMV1248E An active restore for the same sourcefile specification exists. Unable tocontinue with this request.

Explanation: Currently, there is an active restore forthe same source file specification. Another restore of thesame source file specification cannot be started.

System action: The requested restore fails.

User response: Start another restore with a differentsource file specification.

FMV1249W Server cannot restart the last restorerequest. Do you want to restore withoutrestart or abort the request?

Explanation: The restart restore token has expired.The server cannot restart the restore from where it lastended.

System action: Processing stopped; waiting for userintervention.

User response: Retry the request without restart orabort the request.

FMV1251E File system/drive not ready

Explanation: The file system/drive was not ready foraccess.


User response: Ensure that the drive is available toTivoli Storage Manager, and then retry the operation.

FMV1252W The server that you are connected todoes not support this function.

Explanation: You attempted to run a backup-archiveclient operation when connected to the virtual server.Backup-archive client operations are not supportedwhen connected to the virtual server.


User response: Connect to a valid server beforeattempting this function.

FMV1253E File input/output error

Explanation: An error was found while reading fromor writing to the file.

System action: File or file system is skipped.

User response: Check your system to ensure that it isoperating properly. For OS/2, run CHKDSK /F for thefailing drive which can be found in dsmerror.log.

FMV1254E File write error

Explanation: An error was found while writing to thefile.


User response: Check your system to ensure that it isoperating properly.

FMV1255E File exceeds system/user file limits

Explanation: A file being restored or retrieved exceedssystem set limits for this user.


User response: Ensure that the system limits are setproperly.

FMV1256E Cannot make file/directory

Explanation: The directory path for files beingrestored or retrieved cannot be created.


User response: Ensure that you have the properauthorization to create the directory for file beingrestored or retrieved. Make sure that you have writeaccess.

FMV1257E An error occurred while preparing thesystem object for restore.

Explanation: This message is typically issued whenthe client is unable to delete the ADSM.SYS stagingdirectory in preparation for restoring the system object.

System action: The system object is not restored.

User response: Check the error log for any other



messages that might indicate a reason for the failure,correct any indicated problems, then try the operationagain. If the problem occurs again, manually delete theADSM.SYS directory, then try the operation again. Ifthe problem cannot be resolved, contact IBM technicalsupport for further assistance.

FMV1258E The image snapshot operation failed.

Explanation: Tivoli Storage Manager was not able totake a snapshot of the specified volume.



FMV1259E The image snapshot operation failed.Diagnostic text: diag_text.

Explanation: An error was encountered during imagebackup snapshot processing. The diagnostic text canvary, depending on the error.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Take any corrective action suggested bythe messages, then try the operation again. If theproblem persists, contact IBM technical support forfurther assistance.

FMV1260E File is being recalled or has beenrecalled.

Explanation: The file is being recalled by anotherprocess or has been recalled.


User response: None

FMV1261W The archive description you specified isthe empty string. Tivoli StorageManager will use the default description(Archive Date: current date).

Explanation: The description option on the archivecommand may not specify a null string.

System action: Processing continues, and thedescription option is ignored.

User response: None. Specify at least one character inthe description

FMV1262E The password is not updated. Either aninvalid current password was suppliedor the new password does not fulfill theserver password requirements.

Explanation: The password is not updated because ofone of the following reasons:

v You entered an incorrect current password or

v You entered a new password that does not fulfill thepassword length requirements. The lengthrequirements are set on the server.


User response: Enter another password.

FMV1263E The active policy set does not containany backup copy groups. The backupoperation can not continue.

Explanation: In order to back up files, the policy setmust contain at last one backup copy group.

System action: Tivoli Storage Manager did not backupthe file.

User response: The Tivoli Storage Manageradministrator needs to update or define at least onemanagement class in your policy set that contains abackup copy group, or else assign you to a differentpolicy domain that contains at least one backup copygroup. Contact your Tivoli Storage Manageradministrator for further assistance.

FMV1264E The active policy set does not containany archive copy group. The archiveoperation cannot continue.

Explanation: In order to archive files, the policy setmust contain at least one archive copy group.

System action: Tivoli Storage Manager did not archivethe file.

User response: The Tivoli Storage Manageradministrator needs to update or define at least onemanagement class in your policy set that contains anarchive copy group, or else assign you to a differentpolicy domain that contains at least one archive copygroup. Contact your Tivoli Storage Manageradministrator for further assistance.

FMV1265E Encountered bad mount or filesystem,processing stopped.

Explanation: The getmnt system call returned an errorindication. Error was encountered trying to determinewhat the mounted file systems are.

System action: Processing stopped. Cannot recover.

User response: There is a bad file system or mountpoint on your system. Look at file systems and mounts,



and correct any errors. If unsuccessful, see your systemadministrator for more information.

FMV1266E Encountered bad mount or filesystem,processing stopped.

Explanation: An error was encountered trying todetermine what the mounted file systems are.

System action: Processing stopped. Cannot recover.

User response: Please, see your system administratorfor more information.

FMV1267E The management class for file file-namedoes not allow migration. This file willnot be migrated.

Explanation: The management class for this file doesnot allow migration

System action: File is skipped.

User response: Either have the Tivoli Storage Manageradministrator change the Space Management Techniquewithin the management class to a value other thanNONE or change the include/exclude list to specify amanagement class with the appropriate SpaceManagement Technique value.

FMV1268E This file has been migrated.

Explanation: The error can result from migrating a filewith hard links. After a file with hard links is migrated,attempts to migrate the alias files yield an error.


User response: If this error is not a result of a hardlinked file migration, then this error might be due tothe previous cancelled migration or recall operation. Inthis case, restart the dsmrecalld daemon and try theoperation again.

FMV1269I File is implicitly excluded.

Explanation: You tried to back up or migrate a filethat is implicitly excluded.

System action: Tivoli Storage Manager will not backup or migrate an implicitly excluded file.


FMV1270E Running this command requires a validNetApp Snapshot Differential c-modelicense file.

Explanation: A NetApp Snapshot Differential c-modelicense file either doesn't exist or isn't valid.



FMV1271E The compressed file is corrupted andcannot be expanded correctly.

Explanation: The compressed file cannot be expandedcorrectly due to one of the following reasons:

v There is a problem on the tape.

v There is a communications problem.

v The compressed file was corrupted on the TSMServer.


User response: 1) The compressed file is corruptedbecause there is a problem on the tape. To know if thisis the problem, please issue the following command onthe TSM Server: audit volume <volume_name> fix=noIf there is any problem reported, you could move thedata from that volume to a new one (see commandMOVE DATA) and try again the restore. 2) There arecommunications problems between the TSM Server andthe TSM Client and the results is that the file iscorrupted during the transmission. If you use a gigabitEthernet adapter on the Server please upgrade the carddriver (AIX platform) or add provided by SUNsuggested changes to some system network optionswhich have resolved this problem (SUN platform). 3)Please verify with your network support if during therestore there are no any problems between the TSMClient/Server that is originating the file corruption.

FMV1272W Adaptive subfile backup has beenconfigured on the client but the serverdoesn't allow this type of backup.Adaptive subfile backup will not beused for this operation.

Explanation: Adaptive subfile backup forced off bythe server.


User response: Set up the server to allow clients toback up subfiles.

FMV1274E Error Loading WINSOCK.DLL

Explanation: Error loading the Windows socketsupport file into memory. This error only applies whenusing TCP/IP communications.


User response: Because this error is caused byinsufficient memory, shut down running applicationsand retry. If the problem persists, see your systemadministrator.

FMV1275E Error Loading Function(s) fromWINSOCK.DLL

Explanation: Error loading one or more functionsfrom the Windows socket support file.




User response: Since this might possibly be caused byinsufficient memory, shut down running applicationsand retry. If the problem persists, see your systemadministrator.

FMV1278W Virtual mount point 'filespace-name' is afile system. It will be backed up as afile system.

Explanation: A virtual mount point that is a filesystem is invalid and should be deleted.

System action: The virtual mount point is ignored.

User response: Delete the virtual mount point.

FMV1279W Virtual mount point 'filespace-name'cannot be used in a file system handledby automounter and is ignored.

Explanation: Virtual mount points cannot be used in afile system handled by automounter. If virtual mountpoints reside in a file system that is processed from anautomounter, the backed up files underneath thevirtual mount points will be expired when the filesystem is unmounted.

System action: The virtual mount point is ignored.

User response: Delete the virtual mount point.

FMV1286E -nasnodename option required for thisoperation.

Explanation: User issued a NAS related command andNASNodename option is missing.

System action: Operation aborted.

User response: Use -nasnodename option with thecommand or place nasnodename option in the optionfile.

FMV1287E Volume could not be locked.



User response: Please verify that no other applicationis accessing the volume. If this volume is beingaccessed by applications that can not be shutdownduring backup then perform an online image backup(snapshot) instead. During restore of an image TivoliStorage Manager must have exclusive use of thevolume.

FMV1288E The (-TYPE) option is required with theSET EVENT command.

Explanation: There is no default value for the -TYPEoption. It must be explicitly entered with the command.

System action: The current command ends.

User response: Enter the SET EVENT command againwith the TYPE option and a value of HOLD, RELEASE,or ACTIVATERETENTION.

FMV1289W Bad areas on 'volume' between sectorshi:lo and hi:lo

Explanation: Some bad sectors within the specifiedrange were detected on the volume during imageoperation.


User response: Make sure the volume data is notcorrupt by using system tools like chkdsk (Windows)or fsck (UNIX).

FMV1300E File 'file_name' cannot be reconstructedbecause a necessary component was notrestored.

Explanation: The subfile backup technique was usedto back up this file. During the restore, a portion of thefile was not be obtained from the server.

System action: The file indicated in the message is notrestored. Restore for all other files continues.

User response: Try to restore the file again byselecting the file for restore from the user interface. Youcan also check the client error log and the serveractivity log for any messages related to the fileindicated in the message.

FMV1301E This operation cannot continue due toan error on the Tivoli Storage Managerserver. See your Tivoli Storage Managerserver administrator for assistance.

Explanation: The Tivoli Storage Manager serverencountered an error condition that prevents the TivoliStorage Manager client operation from continuing. YourTivoli Storage Manager server administrator can reviewthe Tivoli Storage Manager server activity log for moredetails about the error.


User response: Contact your Tivoli Storage Managerserver administrator for assistance. The administratorcan review the Tivoli Storage Manager server activitylog for further information about the conditions thatlead to this error.



FMV1302E No objects on server match query

Explanation: No objects on the server match the queryoperation being performed. If this object is part of abackupset generated on a node, and the node name ischanged on the server, any backup set objects that weregenerated prior to the name change will not match thenew node name.


User response: Ensure the names are properlyentered. If the object is part of a backupset generatedprior to a node name change, ensure that the nodename is the same as the node for which the backup setwas generated.

FMV1303E Client ended transaction

Explanation: The client system ended the operationwith the server and ended the current transaction.


User response: Restart the session.

FMV1304W An active backup version could not befound.

Explanation: An attempt was made to expire anobject, but the Tivoli Storage Manager server wasunable to find an active backup version of the object.This message is preceded by message FMV1228E whichspecifies the object name. For instance, this messagecould be issued if two separate client processes arebacking up the same file system at the same time. Ifone of the processes expires a file, then the TivoliStorage Manager server will make that file inactive. Ifthe second process subsequently attempts to expire thatsame file, the Tivoli Storage Manager server will notfind an active version of the file, so the second processwill issue this message for that file.

System action: The object is not expired. Processingcontinues with the next object.

User response:

v Review the console output, schedule log, or error logand locate the FMV1228E message that immediatelyprecedes this message. FMV1228E will identify theobject that could not be expired.

v Examine the conditions under which the problemoccurred and assess whether those conditions explainthe occurrence of this message. For example, thismessage could appear if multiple instances of theclient were attempting to back up the file systemconcurrently.

v If the reason this message occurred can not bedetermined and the message occurs when theoperation is tried again, then contact IBM support forfurther assistance. Also try searching for this messagenumber on http://www.ibm.com for possiblesolutions.

FMV1305E The Tivoli Storage Manager server hasno data for the object.

Explanation: Tivoli Storage Manager tried to do arestore or retrieve on an object that has no dataassociated with it. If a corrective action is possible, it iswith the Tivoli Storage Manager server.

System action: Tivoli Storage Manager ends thecurrent operation.

User response: Ask the Tivoli Storage Manageradministrator to check the Tivoli Storage Manageractivity log for any messages related to this error thatmight help identify the problem.

FMV1306E You entered an incorrect password.

Explanation: You entered an incorrect currentpassword or you entered a new password that does notfulfill the password length requirements set on theserver.


User response: Retry the session with the correctpassword. If this fails or you have forgotten yourpassword, ask the Tivoli Storage Manager administratorto assign a new password.

FMV1307E Node in use

Explanation: The node you are running on is in useby another operation on the server. This might be fromanother client or from some activity on the server.


User response: Retry the operation, or see yoursystem administrator to see what other operations arerunning for your node.

FMV1308E Expiration date must be greater thantoday's date

Explanation: Archive expiration date is too low, thedate must be greater than today’s date.


User response: Retry archiving the file with anexpiration date that is higher than today’s date.

FMV1309I The requested data is offline.

Explanation: For the restore or retrieve operation, oneor more of the requested files must be recalled fromoffline storage media (generally tape). The wait timedepends on your site’s offline storage managementpolicies.

System action: Tivoli Storage Manager waits foroffline storage media to become available and thencontinues.




FMV1310E Object too large for server limits

Explanation: The object is too large. The configurationof the server does not have any data storage space thataccepts the object.


User response: See your system administrator todetermine the maximum file (object) size for whichyour site’s server is configured.

FMV1311E Server out of data storage space

Explanation: The server does not have any spaceavailable to store the object.


User response: You can take any of the followingactions:

v Request the system administrator to add space to thestorage pool.

v For Tivoli Storage Manager client, setCOMPRESSALWAYS=NO and COMPRESSIon=YESin the options file (DSM.OPT), then the file will beresent uncompressed if it grows during compression.

v For API Applications, consult the application'sdocumentation for recommendations regardingcompression.

v Turn off disk caching in the disk storage pool, andissue MOVE DATA commands to each disk poolvolume to clear out the cached bitfiles.

FMV1312E Server media mount not possible

Explanation: Server media mount not possible. Theserver timed out waiting for a mount of an offlinevolume.


User response: Retry later when server volumes canbe mounted. Ensure that the MAXNUMMP (maximumnumber of mount points) defined on the server for thisnode is greater than 0.

FMV1313E Size estimate exceeded

Explanation: The total amount of data for a backup orarchive operation exceeds the estimated size originallysent to the server for allocating data storage space. Thishappens when many files are growing by largeamounts while the backup or archive operation is insession.


User response: Retry the operation. If the problemcontinues, check what other processes are running on

the client machine that are generating large amounts ofdata. Disable those operations while the backup orarchive operation is taking place.

FMV1314E File data currently unavailable on server

Explanation: The file data is currently unavailable onthe server. A retrieve or restore operation wasattempted. Possible causes are:

v Data was corrupted at the server

v Server found a read error

v File is temporarily involved in a reclaim operation atthe server

v Server requested a tape volume that was markedunavailable.


User response: Retry the operation. If the problemcontinues, see your system administrator to determinethe problem from the server console or the activity log.Check whether any requests were made for a tapevolume that was unavailable. A tape volume may bemarked unavailable if prior read errors wereencountered or the volume is checked out of the tapelibrary.

FMV1315W Unexpected retry request. The TivoliStorage Manager server found an errorwhile writing the data.

Explanation: None.

System action: If the current operation supportsanother attempt, the client tries the operation again.Otherwise, processing stops.


FMV1316E The server does not have enoughrecovery log space to continue thecurrent operation

Explanation: The server ran out of recovery log space.


User response: This error is a temporary problem.Retry later or see your system administrator.

FMV1317E The server does not have enoughdatabase space to continue the currentoperation

Explanation: The server ran out of database space.





FMV1318E The server does not have enoughmemory to continue the currentoperation.

Explanation: The server ran out of memory.


User response: This is a temporary problem. Retrylater or see your system administrator.

FMV1319E An error occurred on the IBM TivoliStorage Manager server while trying torename file space file_space_name

Explanation: None.

System action: Because the file space cannot berenamed, the operation stops.

User response: Check the client error log and the IBMTivoli Storage Manager server activity log for any othermessages that might help identify the problem. If theproblem cannot be resolved, contact IBM technicalsupport for additional assistance.

FMV1320E The specified file space does not existon the server. The file space might havebeen deleted by another client or anadministrator.

Explanation: The specified file space does not exist onthe server. Your system administrator deleted the filespace or another client using your client’s node namedeleted it.


User response: Check the file space name to see if it iscorrect, and retry the operation.

FMV1321S Open Registration failed because thespecified node name is defined in theserver

Explanation: Open registration failed because a nodeis defined in the server with the same name.


User response: Retry with another node name.

FMV1322S Open Registration failed because nodefault domain exists

Explanation: Open registration failed because adefault policy domain does not exist for you to placeyour node.



FMV1323S Open Registration failed because aninvalid node name was specified

Explanation: Open registration failed because thespecified node name contains invalid characters.


User response: Retry with another node name thatdoes not have any invalid characters.

FMV1326S The Tivoli Storage Manager server doesnot currently have space in the storagepool for this file. This may be atemporary condition.

Explanation: This message is typically issued whenthe storage pool in which the data is being placed doesnot have sufficient space to store the data, but thespace will be available soon. For example, a storagepool migration might free up sufficient space to storethe data.


User response: Try the operation at a later time. If thisfails, contact the Tivoli Storage Manager administratorand request more storage pool space.

FMV1327W The snapshot operation for 'volname'failed with error code: retcode.

Explanation: A snapshot could not be taken of thespecified volume.

System action: Snapshot processing stopped.

User response: Check the client error log for any othermessages that might help identify the problem. If theproblem cannot be resolved, contact IBM technicalsupport for additional assistance.

FMV1328W An error occurred generating delta filefor 'file-name'. The return code is retcode.

Explanation: An error occurred that prevented thecreation of the delta file. Possible reasons for this errorinclude:

v The base file cannot be opened for reading

v The file being backed up cannot be opened forreading

v The delta file cannot be opened for writing

v The file being backed up has grown to a size largerthan 2 GB

v A memory file mapping of the file cannot be created

System action: A full backup of the file is made, and anew version of the reference file is stored in the subfilecache.



User response: If the message indicates return code4504, check the delta subfile cache directory for anyresidual delta files. The delta subfile cache directory isspecified by the client option SUBFILECACHEPATH.Search the directory for files named \".dXXXXXXXX\"where \"XXXXXXXX"\ is an eight-digit number. Ifthere are no backup operations in progress, thereshould not be any files in the SUBFILECACHEPATHwith this name. If there are no backup operations inprogress and these files exist, they can safely beremoved. If you continue to receive this message butthere are no residual delta files in the subfile cachedirectory and the file has not grown to a size largerthan 2 GB, then contact IBM technical support forfurther assistance.

FMV1329S Server out of data storage space

Explanation: The server does not have space availableto store the object.


User response: Report to your system administratorthat a storage pool on the server is full.

FMV1330S This node currently has a pendingrestartable restore session. Therequested operation cannot completeuntil this session either completes or iscanceled.

Explanation: This operation can not be completedbecause a restartable restore session is pending. Theoperation is not allowed because the restartable sessionand the current operation affect the same file space.


User response: Issue a query restore to see theconflict. Issue the cancel restore command to delete anyunneeded restartable restore sessions.

FMV1331E Only a Tivoli Storage Managerauthorized user can perform this Action.

Explanation: User must be a Tivoli Storage Managerauthorized user to perform this action. User is notpassword authorized and this action requiresauthorization.


User response: User must be root user, or user mustbe the owner of the executable and the set effectiveuser id bit is set to 'on' ('s' bit).

FMV1332E Run the '... for Administrators' versionof the application.

Explanation: The user must be root or a systemadministrator and use the provided authorization toolsto start IBM Tivoli Storage Manager

System action: IBM Tivoli Storage Managerterminates.

User response: The user must login as the root user orbe a system administrator and use one of the followingauthorization tools to start IBM Tivoli Storage Manager:

v "Tivoli Storage Manager Backup for Administrators"

v "Tivoli Storage Manager Scheduler forAdministrators"

v "Tivoli Storage Manager Scheduler Daemon forAdministrators"

FMV1334W Volume mount point 'filespacenamepath-namedir-name' was not restoredbecause the target directory is notempty.

Explanation: Volume mount points can only berestored if the target directory does not already exist, orif the target directory exists but is empty. If the targetdirectory exists and is not empty, or already is ajunction point, then the volume mount point cannot berestored. On Windows Vista, it is normal to see thesewarnings during system drive restore as there aremany junction points that point to the'%systemroot%\Users' folder.

System action: The volume mount point is notrestored. Processing continues with the next object.

User response: Correct the conflict with thenon-empty directory, then try the operation again. Thisis especially important when this message is issued fora volume mount point that resides in the SYSVOL,since an incomplete SYSVOL restore can result insystem stability problems. See the reference informationfor the RESTORE command in the client manual foradditional information about restoring volume mountpoints.

FMV1335E The RSM database files could not berestored.

Explanation: None.

System action: The RSM database is not restored.Otherwise, processing continues.

User response: Check the client error log for any othermessages that might help identify the problem. Rebootthe system, then try the RSM restore operation again. Ifthe problem cannot be resolved, contact IBM technicalsupport for further assistance.



FMV1336I RSM service must be restarted forchanges to become effective.

Explanation: RSM database files have been restoredfrom the server and imported. The RSM service mustbe restarted for the updates to become effective.



FMV1337I Restarting the RSM service...

Explanation: RSM database files have been restoredfrom the server and imported. Tivoli Storage Manageris about to stop then restart the RSM service.



FMV1338I Restart of the RSM service is completed.

Explanation: RSM database files have been restoredfrom the server and imported. Tivoli Storage Managerhas restarted the RSM service on the user's behalf.



FMV1339E Restart of the RSM service failed.Restart the RSM service manually.

Explanation: RSM database files have been restoredfrom the Tivoli Storage Manager server and imported.Tivoli Storage Manager has tried to restart the RSMservice on the user's behalf but has run into a problem.


User response: Restart the RSM service manually.

FMV1340E An error occurred while backing up theRSM database.

Explanation: An error occurred while backing up theRSM database files. The database will not be backedup.


User response: Check the client error log for any othermessages that might help identify the problem. Try theoperation again. If the problem persists, contact IBMtechnical support for further assistance.

FMV1341E An invalid character appears in theoperand: operand.

Explanation: The operand contains a character that isnot valid in the current locale and code page. It cannotbe translated to its internal wide-character format.


User response: Change the locale of the workstationto match the language in which the operand isrecorded, and try the command again.

FMV1342E Client cache is locked; unable tocontinue with operation.

Explanation: The client cache is currently locked byanother process.


User response: Report the program error to yourservice representative.

FMV1343E The option 'specified-option' can only beentered when 'other-option' has beenentered.

Explanation: The command failed because thespecified option (specified-option) option was entered,but the other option (other-option) was not.

System action: The command is terminated.

User response: Run the command without thespecified option. Alternatively, run the command withthe other option added.

FMV1344E Job is running in the background.Cannot prompt for the Key.

Explanation: When jobs are run in the background,the client cannot prompt for the key.


User response: Run the Job in the foreground.

FMV1345E No objects on server match'object-nameobject-nameobject-name'

Explanation: The specified file (object-name) does nothave a match on the server.


User response: Backup the file and retry theoperation. If the problem continues, see your systemadministrator to isolate the problem through use of theserver console.

FMV1346E The image snapshot operation failed.The SNAPSHOTCACHELocation doesnot contain enough space for thissnapshot image backup.

Explanation: Tivoli Storage Manager was not able totake a snapshot of the specified volume. TheSNAPSHOTCACHELocation points to a location whichdoes not contain the space necessary to manage thesnapshot. This could be due to an unexpected amountof disk activity which is generating more changes thancan be contained in the available space at this



particular point in time, or theSNAPSHOTCACHELocation needs to be changedbecause the specified location is not large enough tohandle the usual amount of changes to the volume.Another reason for this failure can be that the specifiedSNAPSHOTCACHESize is not set to a large enoughvalue to handle the usual amount of changes to thevolume during snapshot image backup.


User response: If the problem persists please increasethe SNAPSHOTCACHESize and/or change the valueof the SNAPSHOTCACHELocation.

FMV1347E The image snapshot operation failed.The percent of space to use, specifiedvia the SNAPSHOTCACHESize, hasbeen exceeded.

Explanation: Tivoli Storage Manager was not able totake a snapshot of the specified volume. The percent ofspace allotted via the SNAPSHOTCACHESize optionwas not enough to perform this snapshot imagebackup. This could be due to an unexpected amount ofdisk activity which is generating more changes thancan be contained in the allotted space at this particularpoint in time. Another reason for this failure can bethat the specified SNAPSHOTCACHESize is not set toa large enough value to handle the usual amount ofchanges to the volume during snapshot image backup.


User response: If the problem persists please increasethe SNAPSHOTCACHESize or, for Windows, changethe value of the SNAPSHOTCACHELocation.

FMV1348E Unable to satisfy theSNAPSHOTFSIDLEWait andSNAPSHOTFSIDLERetries options dueto volume write activity.

Explanation: Tivoli Storage Manager was not able totake a snapshot of the specified volume. The LogicalVolume Snapshot Agent was not able to satisfy theSNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetriesoptions before starting the snapshot of the specifiedvolume.


User response: If the problem persists please modifythe SNAPSHOTFSIDLEWait andSNAPSHOTFSIDLERetries options to better fit thenormal disk write activity of the volume being backedup.

FMV1349E An error occurred during LogicalVolume Snapshot Agent snapshotprocessing.

Explanation: An unrecoverable error occurred duringsnapshot processing. This can be caused by a variety of

errors, so the error and system event logs should bechecked for additional messages.


User response: Check the client error log and thesystem event log for any other messages that mighthelp identify the problem. Try the operation again. Ifthe problem persists, contact IBM technical support forfurther assistance.

FMV1350E The logical volume snapshot agent(LVSA) is currently busy performing asnapshot on this same volume.

Explanation: Another IBM Tivoli Storage Managerprocess is already performing a snapshot of thisvolume.

System action: The operation is stopped.

User response: Please wait until the other IBM TivoliStorage Manager process finishes with the volume andthen retry the operation.

FMV1351E Session rejected: All server sessions arecurrently in use

Explanation: Tivoli Storage Manager has all availablesessions in use and cannot accept a new one at thistime.


User response: Retry the operation. If the problemcontinues, see your system administrator to increase thenumber of concurrently active sessions to the server.

FMV1352E The session is rejected. Your passwordhas expired.

Explanation: The password for Tivoli Storage Manageruser ID has expired. It can be either Tivoli StorageManager node name password or administrative userID password or both.

System action: Tivoli Storage Manager canceled thecurrent operation. You are not allowed to connect to theserver until the password is updated.

User response: Update your password. It may requireupdating the node name password or the corespondentadministrative ID password or both. You may use theSET PASSWORD command, or have the Tivoli StorageManager administrator update your node and/or youradministrative ID.

FMV1353E Session rejected: Unknown or incorrectuser ID entered

Explanation: The user ID, which is either TivoliStorage Manager node name or administrative user ID,



is not known by the server. Possible reasons for thisinclude:

v Your node name is not registered with the TivoliStorage Manager server

v The node name is correct but does not have acorresponding administrative ID with the same nameand client owner authority

v you are attempting to access a file that was migratedto a different node.

System action: Tivoli Storage Manager cancelled thecurrent operation.

User response: Verify that the server is using closedregistration and that your node name is registered withthe server. Ensure that you entered your Tivoli StorageManager user ID correctly. Check that your TivoliStorage Manager node name has a matching admin IDwith client owner authority for the node. If it does not,your Tivoli Storage Manager administrator needs tocreate it. If attempting to access a migrated file, yournode name must be the same node which migrated thefile.

FMV1354E Session rejected: Duplicate ID entered

Explanation: Another process using this node name isactive with the server.

System action: Tivoli Storage Manager cannot connectto the server. Tivoli Storage Manager canceled thecurrent operation.

User response: If you are running a UNIX-basedsystem, ensure that another process is not active withTivoli Storage Manager under the same name. Also,ensure that your node name is unique to the server sothat it cannot be used by another person. See yoursystem administrator to identify the owner of that nodename.

FMV1355E Session rejected: Server disabled.

Explanation: The server is in a disabled state andcannot be accessed for normal activity.


User response: Retry the operation after the serverreturns to an enabled state. If the problem continues,see your system administrator.

FMV1356E The server is not configured to allowopen registration

Explanation: No authorization. Registration isrequired by your system administrator. The server isnot configured to allow open registration.

System action: Session not started.

User response: You must obtain a Tivoli Storage

Manager node and password from your systemadministrator.

FMV1357S Session rejected: Downlevel client codeversion

Explanation: The server version and your clientversion do not match. The client code is downlevel.


User response: See your system administrator to seewhat version of Tivoli Storage Manager to run for yourlocation.

FMV1358S Session rejected: Downlevel server codeversion

Explanation: The server version and your clientversion do not match. The server code is downlevel.


User response: See your system administrator to seewhat version of Tivoli Storage Manager to run for yourlocation.

FMV1359E Session Rejected: The specified nodename is currently in use

Explanation: The node name you specified is in useon the server.


User response: The server is probably performing atask that prevents your node from establishing asession. Retry later or check with your systemadministrator.

FMV1360I Compressed Data Grew

Explanation: The size of the file after compression isgreater than the size of the file before compressed.

System action: Even though the size of the fileincreased, the file is compressed.


FMV1361E Session Rejected: The specified nodename is currently locked.

Explanation: The node name you specified is currentlylocked on the server.


User response: Check with your system administratorto find out why your node name is locked.



FMV1362S SLM LICENSE EXCEEDED: The clientlicenses for Tivoli Storage Manager areexceeded. See your systemadministrator.

Explanation: Adding a new enrollment will exceed theproduct license count for Tivoli Storage Manager.

System action: Execution of the client enrollment orconnection request ends.


FMV1363E Session Rejected: The server does nothave enough memory to allow aconnection to be established.

Explanation: The server does not have enoughmemory to allow your client to establish a connectionwith the server.


User response: Retry later or see your systemadministrator.

FMV1364E Session Rejected: The server does nothave enough recovery log space to allowa connection to be established.

Explanation: The server ran out of recovery log space.


User response: This error is a temporary problem.Retry later or see your system administrator.

FMV1365E Session Rejected: The server does nothave enough database space to allow aconnection to be established.

Explanation: The server ran out of database space.



FMV1366E The session is rejected. The TivoliStorage Manager server has an internalerror.

Explanation: The client cannot establish a connectionto the Tivoli Storage Manager server because of aninternal server error.

System action: The session was not started.

User response: Notify your Tivoli Storage Manageradministrator of this error.

FMV1367E The client is unable to sign on to theTivoli Storage Manager server becausethe server does not allow sign-on ofUnicode clients.

Explanation: The client is not allowed to connect tothe Tivoli Storage Manager server.

System action: The session does not start.

User response: Contact your Tivoli Storage Manageradministrator for assistance in configuring a workingTivoli Storage Manager client for your environment.

FMV1368S Session Rejected: The server is notlicensed for this platform type. See yoursystem administrator.

Explanation: The server is not licensed for therequesting client type.

System action: Execution of the client enrollment orconnection request ends.


FMV1369E Session Rejected: The session wascanceled by the server administrator.

Explanation: The server administrator canceled thecurrent client session.

System action: Execution of the client connectionrequest ends.


FMV1370E The user ID entered does not have thecorrect level of authority to access theclient machine.

Explanation: The user ID entered cannot access thisTivoli Storage Manager client.

System action: The Tivoli Storage Manager operationends.

User response: Grant authority to this user ID on theTivoli Storage Manager server so that it can access thisTivoli Storage Manager client.

FMV1371E File '' cannot be reconstructed fromsubfile components.

Explanation: An error occurred while reconstructingthis file from its subfile components.

System action: The file indicated in the message is notrestored. Restore for all other files continues.

User response: Try to restore the file again byselecting the file for restore from the user interface. Youcan also check the client error log and the serveractivity log for any messages related to the fileindicated in the message.



FMV1372E An inconsistency was detected betweenthe client node and the node that isregistered to the Tivoli Storage Managerserver.

Explanation: The user has probably coded the nodeoption incorrectly. For instance, the node that isregistered to the Tivoli Storage Manager server mightbe a type of NAS, but the node is actually a non-NASclient.


User response: Ensure that the node name is correctin the client options file. Make sure to use a node oftype NAS only with the nasnodename option.

FMV1373W The PRESNAPSHOTCMD command forvolume filespace completed with anon-zero return code.

Explanation: The command specified by thePRESNAPSHOTCMD option must completesuccessfully in order to perform the snapshotbackup/archive operation. If the command completedwith a return code of 0 (zero), it has completedsuccessfully. If the command completed with any otherreturn code, it has failed. If the command failed, thenthe backup is still performed, but without the benefit ofthe snapshot technology.

System action: The client executes the backup/archiveoperation, but without using a snapshot.

User response: Identify and fix the problem thatcaused the command to fail. If a non-zero return codeis normal for this command, then consider wrappingthe command in a script that always exits with a returncode of zero.

FMV1374W The POSTSNAPSHOTCMD commandfor volume filespace completed with anon-zero return code.

Explanation: The command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code. The snapshot-based backupoperation yields a return code of at least 8.

System action: The snapshot-based backup operationcontinues.

User response: Identify and resolve the problem thatcaused the post-snapshot command to fail. If anon-zero return code is normal for this command, thenconsider wrapping the post-snapshot command in ascript that always exits with a return code of zero.

FMV1375W File FilesystemPathFileName skipped byuser

Explanation: You requested that this file be skippedduring the current operation.

System action: The file is skipped during the currentoperation


FMV1376E Error processing 'filespacenamepath-namefile-name'; end-to-enddigest validation failed.

Explanation: Cryptographic digest of the restored orretrieved data did not match the digest generatedduring the backup or archive operation. Possible causesare a transmission error, data corruption, or a hashcollision.


User response: Try the restore operation again. If theproblem persists, contact IBM technical support foradditional assistance.

FMV1377W The client was unable to obtain asnapshot of 'volname'. The operation willcontinue without snapshot support.

Explanation: Tivoli Storage Manager client was unableto create a snapshot of the volume due to some reason.Instead of failing the operation, Tivoli Storage Managerclient will perform a non-snapshot based backup.

System action: Snapshot processing stops.


FMV1378E The snapshot operation failed. TheSNAPSHOTCACHELocation does notcontain enough space for this snapshotoperation.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. TheSNAPSHOTCACHELocation points to a location whichdoes not contain the space necessary to manage thesnapshot. Reasons for failure include:

v An unexpected amount of disk activity which isgenerating more changes than can be contained inthe available space at this particular point in time.

v The SNAPSHOTCACHELocation is not large enoughto handle the usual amount of changes to thevolume.

v The specified SNAPSHOTCACHESize is not set to alarge enough value to handle the usual amount ofchanges to the volume during snapshot backup orarchive operation.




User response: If the problem persists, increase theSNAPSHOTCACHESize or change the value of theSNAPSHOTCACHELocation.

FMV1379E The snapshot operation failed. Thepercent of space to use for theSNAPSHOTCACHELocation, specifiedvia the SNAPSHOTCACHESize, hasbeen exceeded.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. The percentof space allotted via the SNAPSHOTCACHESize optionwas not enough to perform this snapshotbackup/archive operation. Reasons for failure include:

v The SNAPSHOTCACHELocation is not large enoughto handle the usual amount of changes to thevolume.

v The specified SNAPSHOTCACHESize is not set to alarge enough value to handle the usual amount ofchanges to the volume during snapshot backup orarchive operation.


User response: If the problem persists, increase theSNAPSHOTCACHESize or change the value of theSNAPSHOTCACHELocation.

FMV1380W The snapshot operation failed. Thefilesystem write activity prevented theLogical Volume Snapshot Agent fromsatisfying the SNAPSHOTFSIDLEWaitand SNAPSHOTFSIDLERetries options.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. The LogicalVolume Snapshot Agent was not able to satisfy theSNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetriesoptions before starting the snapshot of the specifiedvolume.


User response: If the problem persists, modify theSNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetriesoptions to better fit the normal disk write activity ofthe volume being backed up.

FMV1381W On volumes that are RAW or formattedFAT32 the snapshot cache locationcannot be located on the same volumethat is being backed up.

Explanation: When the snapshot cache location islocated on the same volume that is being backed up thevolume must be formatted with NTFS. The defaultcache location is on the same volume where thesnapshot is being performed. The operation willcontinue without snapshot support.

System action: The client does not execute thesnapshot operation.

User response: Specify a different snapshot cachelocation, using the SNAPSHOTCACHELOCATIONoption.

FMV1382E Server does not allow client-initiatedconnections for this node.

Explanation: The node is not allowed to initiateconnections due to the configuration parameters forthis node on the server. Server is able to initiateconnections to the client scheduler running inprompted mode.

System action: The IBM Tivoli Storage Manageroperation ends.

User response: Contact your systems administrator toenable client-initiated sessions for your node or updatethe SESSIONINITIATION option and run the clientscheduler.

FMV1383E Wrong server port.

Explanation: You were trying to open abackup/archive client session on the server port set upfor administrative sessions only.

System action: The IBM Tivoli Storage Manageroperation ends.

User response: Contact your systems administratorand/or use the correct values for TCP port and TCPAdmin Port.

FMV1384E An object in the transaction has beenbound to an invalid management class.

Explanation: One of the objects in the transaction isbound to a management class that is not part of thisnode's policy, or the management class type is notsupported for this client level.

System action: The current operation ends.

User response: Make sure all objects are bound to avalid management class, or upgrade the client to theproper level.

FMV1385E This server does not support backupoperations.

Explanation: This server only supports archiveoperations, backup is not allowed.


User response: Use only archive operations with thisserver.



FMV1386E Deleting this object: "fshlll" is notallowed.

Explanation: The object is either under a hold andcannot be deleted, or it is on a retention-protectionenabled server and has not expired.

System action: The object is skipped and processingcontinues.

User response: Check the status of the object througha query to see if it is held, or when it expires.

FMV1387E The number of objects in thistransaction exceed TXNGROUPMAXvalues.

Explanation: There are too many objects in thistransaction.


User response: Try the operation again with fewerobjects in the transaction, or increase theTXNGROUPMAX value on the server.

FMV1388E fshlll is already under hold.

Explanation: The specified object is already underhold, and it cannot be placed under a new hold.

System action: This object is skipped and processingcontinues.

User response: Issue a query to see the status of theobjects, and try the operation again, without the objectthat is already held.

FMV1389W Invalid option (option) for the scheduledfunction command

Explanation: There are two possible reasons for thismessage:

v The option option was specified for a scheduledcommand or subcommand (function) that cannotmake use of that option.

v The option appears on a scheduled command but isvalid only on the client scheduler initial commandline, not on commands in a schedule from the server.

System action: The option is ignored.

User response: See the Backup-Archive ClientInstallation and User's Guide for correct use of thenamed option. The system administrator shouldremove the invalid option from the schedule definitionon the server.

FMV1395E The destination filespace or drive letteris unavailable. The following object wasnot processed: Filespace:'filespace-name'

Explanation: The system is trying to restore or retrieveto a destination that cannot be reached. The specified

filespace name or drive letter is not valid, or does notexist, or you are specifying a local share name thatcannot be resolved.

System action: Objects which are part of this filespaceare not processed.

User response: Try the command again, and specify adifferent destination for the object that was notprocessed.

FMV1396E Access to the specified log or trace file(filename) is denied.

Explanation: Access to the specified file is denied. Youspecified a log or trace file name that cannot be writtenby the current user.



FMV1397W The snapshot cannot be taken becausethe SNAPSHOTCACHELocation doesnot have enough space for this snapshotoperation.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume. TheSNAPSHOTCACHELocation points to a location whichdoes not contain the space necessary to create thesnapshot; the disk is probably full. The operationcontinues without snapshot support.


User response: Change the value of theSNAPSHOTCACHELocation, or clean the disk to whichthe SNAPSHOTCACHELocation points.

FMV1398E Initialization functions cannot open oneof the Tivoli Storage Manager logs or arelated file: log-name. errno = errno-value,reason

Explanation: The file "log-name" could not be openedduring initialization. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thelog in the directory specified. It is also possible that nospace is available at the given log location.

On Unix systems, the log must not be in the rootdirectory. Attempts to do so will result in an "accessdenied" error.


User response: Set the DSM_LOG (or DSMI_LOG)environment variable to a directory into which thecurrent user can write. You may also use theERRORLOGNAME option to specify a file to which the



current user has write permission.

FMV1399W The logical volume snapshot agent(LVSA) is currently busy performing asnapshot on this same volume.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume becauseanother process is already performing a snapshot ofthis volume. The operation continues without snapshotsupport.


User response: Wait until the other IBM Tivoli StorageManager process finishes with the volume and then trythe operation again.

FMV1400W The snapshot cache location is not valid.

Explanation: The snapshot cache location must pointto a local volume that is formatted with NTFS. Thedefault cache location is on the same volume where thesnapshot is being performed. The operation willcontinue without snapshot support.



FMV1401W The snapshot virtual volume is notaccessible.

Explanation: The logical volume snapshot agent(LVSA) cannot access the virtual volume duringOFS-enabled backup/archive operation because IBMTivoli Storage Manager was probably started viaterminal services. The operation continues withoutsnapshot support.


User response: Do not use terminal services for thesnapshot. Try the operation again on the local machine.

FMV1402W The snapshot is not supported on aremote, removable, or SAN drive.

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume becauseopen file support is only supported on local fixedvolumes, including volume mountpoints. The operationcontinues without snapshot support.


User response: To take advantage of the open filesupport, you may try the operation again on the localmachine.

FMV1403E Error loading a required filename DLL

Explanation: An error occurred while loading adynamic link library. The DLL load failed.


User response: Verify that your system software is upto date and that all DLLs required by the Tivoli StorageManager client are present.

FMV1404E Error loading one or more functionsfrom a required filename DLL

Explanation: An error occurred while loading afunction from a dynamic link library. The DLL loadfailed.


User response: Verify that your system software is upto date.

FMV1405I 'service-name' service needs to berestarted.

Explanation: The service must be restarted for therestored changes to take effect.

System action: Changes are not effected.

User response: Restart the service.

FMV1406I Performing operation usingpoint-in-time copy of the filesystem:'volname'.

Explanation: IBM Tivoli Storage Manager is taking asnapshot of the specified volume during the backup orarchive operation. This allows the IBM Tivoli StorageManager to access locked or in-use files.

System action: Operation proceeds.


FMV1407I Performing operation usingpoint-in-time copy of the filesystem.

Explanation: IBM Tivoli Storage Manager is taking asnapshot of the specified volume during the backup orarchive operation. This allows the IBM Tivoli StorageManager to access locked or in-use files.

System action: Operation proceeds.


FMV1408W Previous changes have not beencommited. The machine must berestarted before the snapshot can betaken

Explanation: IBM Tivoli Storage Manager was not ableto take a snapshot of the specified volume because a



previous operation required the machine to be restartedfor the changes to take effect, but the machine has notbeen restarted. The operation will continue withoutsnapshot support.


User response: Restart the machine and then try theoperation again.

FMV1410E Unable to access the network path.

Explanation: The network path cannot be accesseddue to a possible network problem.

System action: The client terminates.

User response: Ensure that the network is up and thepath can be accessed using a system command, andretry the operation.

FMV1411E A communication session was dropped.

Explanation: A communication session was droppeddue to a possible network problem.


User response: Ensure that the network is up andretry the operation.

FMV1412E Directory or file has bad EA data orinconsistent data.

Explanation: Directory or file has bad EA data orinconsistent data.


User response: Check failing directory or file for badEA data. Copy the directory to a new location and retrythe operation.

FMV1413W File 'filespace namepath-namefile-name' isnot recognized by the system as a diskfile and cannot be processed. The file isskipped.

Explanation: The client is unable to process file typesthat are not 'disk', such as 'character' and 'pipe'. Thismessage is typically, but not always, issued for filenames that are normally reserved for the operatingsystem. In the Windows environment, reserved namesinclude AUX, CON, NUL, PRN, COMx or LPTx, where'x' is any digit from 1 to 9 (for example, COM1, LPT3,etc.).


User response: Either delete the file if you do notneed it, or else use an EXCLUDE statement in the clientoptions to prevent the client from trying to process thefile. In the Windows environment, normal deletecommands will most likely not work. You will need to

prefix the file name with the characters '\\.\'. Forexample, "del c:\mydir\lpt4" will not work, but "del\\.\c:\mydir\lpt4" will work.

FMV1414W Don't have sufficient authority to deleteopen group on server.

Explanation: An open image group exists on theTivoli Storage Manager server and cannot be deleteddue to missing backup delete rights for this node.


User response: Ask your Tivoli Storage Manageradministrator to grant backup delete rights for yournode.

FMV1417W Protected system state file 'filename' isbacked up to the drive file space, notsystem state file space.

Explanation: Files protected by Microsoft WindowsFile Protection (WFP) or Microsoft Windows ResourceProtection (WRP) are part of the Microsoft VolumeShadowCopy Services (VSS) System Writer which ispart of the system state. These files are normallybacked up as part of the system state, not the filesystem on which the files reside. A problem in theoperating system environment prevented the protectedfile named in the message text from being enumeratedas a system state file and thus backed up as part of thesystem state. The conditions that lead to this messageare not normal. In order to ensure that the file isprotected, it is backed up as part of the file system onwhich it resides.

System action: The file is backed up as part of the filesystem on which it resides.

User response: It is possible to restore the systemusing the file system and system state backups.However the conditions that prevent the system statefiles from being correctly enumerated should beaddressed. On Microsoft Windows 2008 and MicrosoftWindows 2008 R2 you can use the DiskShadow utilitysub-command LIST WRITERS DETAILED to enumeratethe system state files. On other versions of MicrosoftWindows you can use the vshadow utility with the-wm2 option to enumerate the system state files. Verifythat the file indicated in this message is not listed.Note: vshadow is a utility that you can obtain fromMicrosoft. After confirming that the files are notenumerated, contact your operating system technicalsupport for help to diagnose and resolve the issue thatprevents the file from being correctly enumerated aspart of the system state.

FMV1420E Volume map document (tsmvolmap.txt)not found.

Explanation: An error occurred while performing VSSAutomated System Recovery (ASR). Checkdsmerror.log for more information.




User response: Ask your system administrator tocheck the error log.

FMV1421E The image object 'object-type' was notfound on server.

Explanation: The specified image object of typeobject-type could not be located on the server. Theoperation cannot complete without this object.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Take any corrective action suggested bythe messages, then try the operation again. If theproblem persists, contact IBM technical support forfurther assistance.

FMV1423W 'filesystem' is a virtual mount point.Migration is not supported on virtualmount points.

Explanation: Tivoli Storage Manager HSM does notsupport virtual mount points within managed filesystems. Files in the virtual mount point folder can notbe migrated.

System action: Tivoli Storage Manager attempts tocontinue the current operation.

User response: Do not use virtual mount pointswithin file systems that are managed by HSM. Useinclude/exclude rules instead.

FMV1424W Retrying failed image operation forvolume filespace-name.

Explanation: The transaction for image operation forvolume filespace-name failed due to reason described byearlier message(s).

System action: The requested image operation will beretried again.


FMV1425E The image operation for volumefilespace-name cannot be retried becauseof a severe error.

Explanation: None.

System action: The image operation fails for theindicated volume.


FMV1426E An error occurred creating the Registrybackup directory structure

Explanation: The Tivoli Storage Manager client usesan intermediate directory structure on the clientmachine as part of the Windows Registry backupprocess. The client was unable to create thisintermediate directory structure, so the WindowsRegistry could not be backed up. This problem canoccur if you do not have sufficient privileges toperform the backup operations, if the client is unable toallocate more memory from the system, or if acomponent within the directory structure already existsas a file.

System action: The Windows Registry is not backedup.

User response: Check the client error log for any othermessages that might have been logged when thismessage was written, and take the corrective action (ifany) suggested by those messages. Make sure thataccount under which the operation runs has sufficientprivileges. Ensure that the system has sufficientmemory to run Tivoli Storage Manager. Remove theADSM.SYS directory from the root of your systemdrive, then try the operation again. If the problempersists, contact IBM support for further assistance.

FMV1427I Registry Backup function completedsuccessfully.

Explanation: Registry backup was successful.



FMV1428E Backup of the registry failed.

Explanation: None.

System action: The registry is not backed up.


FMV1429I Registry Restore function completedsuccessfully.

Explanation: Registry Restore was successful.



FMV1430W The machine must be rebooted for thechanges to take effect.

Explanation: The Tivoli Storage Manager restoreoperation made changes that will not be in effect untilthe machine is rebooted. It is important to note that



until the reboot occurs, the system or its applicationsmight be unstable.

System action: None


FMV1431E Restore of the registry failed.

Explanation: None.

System action: The registry is not restored.


FMV1432E Keyword Expected after keyword'keyword'.

Explanation: A registry command was incorrectlyentered.

System action: Registry function is not invoked.

User response: Refer to the command reference forthis command.

FMV1433E Extraneous argument 'input' afterkeyword 'keyword'


System action: Registry function not invoked.


FMV1434E Invalid argument 'input' after keyword'keyword'


System action: Registry function not invoked.


FMV1435E An error occurred saving a registry key.

Explanation: None.

System action: The registry is not backed up.


FMV1436E An error occurred replacing a registrykey.

Explanation: None.

System action: The registry key is restored from theserver, but cannot be activated in the registry. Thecurrent registry key remains active.


FMV1437I Event Log Backup function completedsuccessfully.

Explanation: Event Log backup was successful.



FMV1438E Backup of the event logs failed.

Explanation: None.

System action: The event logs are not backed up.


FMV1439I Event Log Restore function completedsuccessfully.

Explanation: Event Log Restore was successful.



FMV1440E Restore of the event logs failed.

Explanation: None.

System action: The event logs are not restored.


FMV1441E Keyword Expected after keyword'keyword'.

Explanation: A event log command was incorrectlyentered.

System action: Event Log function is not invoked.




FMV1442E Extraneous argument 'input' afterkeyword 'keyword'


System action: Event Log function not invoked.


FMV1443E Invalid argument 'input' after keyword'keyword'


System action: Event Log function not invoked.


FMV1444E An error occurred creating the Event Logbackup directory structure

Explanation: The Tivoli Storage Manager client usesan intermediate directory structure on the clientmachine as part of the Windows Event Log backupprocess. The client was unable to create thisintermediate directory structure, so the Windows EventLogs could not be backed up. This problem can occur ifyou do not have sufficient privileges to perform thebackup operations, if the client is unable to allocatemore memory from the system, or if a componentwithin the directory structure already exists as a file.

System action: The Windows Event Logs are notbacked up.

User response: Check the client error log for any othermessages that might have been logged when thismessage was written, and take the corrective action (ifany) suggested by those messages. Make sure thataccount under which the operation runs has sufficientprivileges. Ensure that the system has sufficientmemory to run Tivoli Storage Manager. Remove theADSM.SYS directory from the root of your systemdrive, then try the operation again. If the problempersists, contact IBM support for further assistance.

FMV1445E ERROR: could not create NAS imageobject.

Explanation: Creation of the NAS image object failedfor one of following reasons:

v An unauthorized user invoked the NAS command

v NAS operations are not supported on the currentplatform

v Cannot find the NAS plugin library.

System action: The requested NAS operation is notperformed.

User response: Retry the operation after correcting thecause for failure.

FMV1446E VSS ASR backup document(ASRBackupDoc.xml) not found.

Explanation: An error occurred while performing VSSAutomated System Recovery (ASR). Checkdsmerror.log for more information. Possible causes forthe error are the following:

v You are trying to recover a machine running a legacyoperating system such as windows XP or windows2003. VSS ASR Restore is not supported for legacyoperating systems.

v You are trying to run ASR recovery from a backupcreated by a client earlier than version 6.2.2. Suchbackups do not have ASRBackupDoc.xml file.



FMV1448E The command command is not supportedby the current server.

Explanation: The server to which the client isconnected does not support the command.

1. If the command is "set event," the server does notsupport event-based policy. This command requiresthat the server support event-based policy. Thatsupport is available only at TSM Server levels 5.2.2and above.

2. If the message displays any other command, theserver is configured to support archive retentionprotection and cannot process operations notassociated with that facility.

System action: The command is skipped and otherprocessing continues.

User response: Log in to an appropriate server andretry the command.

FMV1449W A non-critical, unexpected error wasencountered. Deletion of asnapshot(Set/Volume) failed. Probablecause, snapshot does not exists anymore.Continuing Process... Tivoli StorageManager snapShot ID : snapshot-id TivoliStorage Manager function name :function-name Tivoli Storage Managerfunction : function-desc Tivoli StorageManager return code : TSM-rc TivoliStorage Manager file : file-name(line-number)

Explanation: None.


User response: Contact the Tivoli Storage Manager



administrator with the information provided in thismessage.

FMV1450W The -FILENAME option was specifiedwithout a file name. Output will bewritten to filename.

Explanation: The -FILENAME option was specified,but the file name was omitted.

System action: The output is written to the defaultfile.

User response: Reissue the command and specify avalid file name, or use the information that was writtento the default file.

FMV1453W The IMAGEGAPSIZE option is notsupported for non-NTFS file systems.The entire volume will be backed up.

Explanation: None.

System action: The entire volume is backed up.

User response: Refer to the client manual foradditional information regarding the IMAGEGAPSIZEoption.

FMV1454W Used blocks information could not beobtained for name. The entire volumewill be backed up.

Explanation: None.



FMV1458I OBF file for volume name is too smallfor server-free data transfer.

Explanation: The OBF file for volume is very small toinitiate a server-free data transfer. Hence this file willnot be transferred via a server-free data path.



FMV1459E VSS Automated System Recovery (ASR)failed.

Explanation: An error occurred while performing VSSAutomated System Recovery (ASR). Checkdsmerror.log for more information.



FMV1461E Error processing 'filespacenamepath-namefile-name': unsupportedencryption type.

Explanation: The files you are trying to restore orretrieve have been backed up or archived by a laterversion of the Tivoli Storage Manager client. The fileencryption method is not supported by the currentclient.


User response: Restore or retrieve the file with themost recent version of the Tivoli Storage Managerclient.

FMV1462E Unsupported encryption type

Explanation: The files you are trying to restore orretrieve have been backed up or archived by a laterversion of the Tivoli Storage Manager client. The fileencryption method is not supported by the currentclient.


User response: Restore or retrieve the file with themost recent version of the Tivoli Storage Managerclient.

FMV1463E Unexpected error in cryptographylibrary.

Explanation: There was an unexpected error in thecryptography library. See the error log for moreinformation.


User response: Check the error log for FMV1467E todetermine the cause of failure. Verify you Tivoli StorageManager client is installed properly. If needed, reinstallclient and/or API. If the problem still exists, contactTivoli Storage Manager technical support.

FMV1464S Cannot load ICC encryption library.

Explanation: Tivoli Storage Manager is usingcryptography library which is installed automaticallywith the client and is being loaded at runtime. Theclient cannot proceed if the library is not loaded.

System action: Client exits.

User response: Check the error log for FMV1467E todetermine the cause of failure. Verify you Tivoli StorageManager client is installed properly. If needed, reinstallclient and/or API. If the problem still exists, contactTivoli Storage Manager technical support.

FMV1450W • FMV1464S


FMV1465E Conflicting options ERRORLOGMAXand ERRORLOGRETENTION werespecified.

Explanation: Values were specified for both theERRORLOGMAX and the ERRORLOGRETENTIONoptions. These options are mutually exclusive.


User response: Specify a nonzero value forERRORLOGMAX if you wish to have the Tivoli StorageManager error log wrap when it reaches the specifiedmaximum value. Use ERRORLOGRETENTION if youwish you have the error log limited in size on atime-based schedule.

FMV1466E Conflicting options SCHEDLOGMAXand SCHEDLOGRETENTION werespecified.

Explanation: Values were specified for both theSCHEDLOGMAX and the SCHEDLOGRETENTIONoptions. These options are mutually exclusive.


User response: Specify a nonzero value forSCHEDLOGMAX if you wish to have the TivoliStorage Manager scheduler log wrap when it reachesthe specified maximum value. UseSCHEDLOGRETENTION if you wish you have thescheduler log limited in size on a time-based schedule.

FMV1467E ICC routine icc-routine returned: majRC= majRC, minRC = minRC, desc = 'desc'.

Explanation: There was an error within an ICCcryptography library. This message reports return codesand problem description which can be used by TivoliStorage Manager technical support personnel todetermine the cause of the error.

System action: Client exits.

User response: Verify you Tivoli Storage Managerclient is installed properly. If needed, reinstall clientand/or API. If the problem still exists, contact TivoliStorage Manager technical support.

FMV1468E Backing up Automated System Recovery(ASR) files failed. No files will bebacked up.

Explanation: An error occurred while backing up thefiles needed for Automated System Recovery (ASR). Nofiles were backed up.


User response: Ask your system administrator tocheck the error log. Verify that the Windows accountfrom which you are running this command hasadministrator authority and try the command again.

FMV1469E Error processing 'filespacenamepath-namefile-name'; invalidencryption key.

Explanation: The key you entered does not match thekey that was used to encrypt the file during backup.The file can not be restored unless the matching key isentered.


User response: Try the restore operation again andprovide the correct key.

FMV1470E Unable to load GPFS functions neededfor ACL and extended attributessupport: skip path_name

Explanation: The GPFS functions that handle theGPFS ACL and extended attributes were not loaded.

System action: The object is skipped. Processingcontinues with the next object.

User response: Ensure that the GPFS software isinstalled on the system and try the operation again. OnLinux, iensure that there has been an appropriatesymbolic link created in /usr/lib/ directory for theGPFS libgpfs.so shared library.

FMV1471E ASR system information file creationfailed. ASR backup is unsuccessful.

Explanation: An error occurred while creating thesystem information file (asr.sif) needed for AutomatedSystem Recovery (ASR). The ASR backup isunsuccessful.


User response: Ask your system administrator tocheck the error log. Verify that the Windows accountfrom which you are running this command hasadministrator authority and that you have access to thesystem object staging directory <system drive>:\adsm.sys. Try the command again.

FMV1472E Could not add entry to the ASR systeminformation file. ASR backup isunsuccessful.

Explanation: An error occurred while adding an entryto the system information file (asr.sif) needed forAutomated System Recovery (ASR). The ASR backup isunsuccessful.


User response: Ask your system administrator tocheck the error log. Verify that the Windows accountfrom which you are running this command hasadministrator authority and try the command again.



FMV1473E Session rejected: TCP/IP connectionfailure for Shared Memory

Explanation: An attempt to connect to the local serverusing the Shared Memory protocol has failed duringinitial TCP/IP communications. This error can occur ifthe server is not listening on the correct port, or if theserver is down.

System action: Session rejected. Processing stopped.

User response: Retry the operation, or wait until theserver comes back up and retry the operation. If theproblem continues, see your system administrator forfurther help.

FMV1474E An error occurred using the SharedMemory protocol

Explanation: An error has occurred while reading orwriting data through the Shared Memorycommunications protocol.


User response: Check the trace log for additionalinformation and retry the operation. If the problemcontinues, see your system administrator for furtherhelp.

FMV1475E Insufficient authority to connect to theshared memory region

Explanation: The user issuing the command does nothave authority to connect to the shared memorysegment. When the shared memory segment is createdby the server, it will be owned by the effective uid ofthe server process (dsmserv). Only processes runningunder this uid or root will be allowed to connect to thesegment (and thus to the server).

System action: The session is rejected and processingstops.

User response: Run the command under the uid ofthe processing running dsmserv, if possible. Otherwisecontact your system administrator for further help.

FMV1476E CLUSTERNODE is set to YES but theCluster Information Daemon is notstarted.

Explanation: The HACMP™ Cluster InformationDaemon must be started in order to specify theCLUSTERNODE option.


User response: Start the HACMP Cluster InformationDameon.

FMV1477E CLUSTERNODE is set to YES but thecluster load library is not valid.

Explanation: The load library that the operatingsystem provides to obtain the cluster name is not valid.A possible cause is an out-of-date load library whichdoes not contain the proper routines this productexpects.


User response: Ensure that the latest cluster softwareis installed on the system.

FMV1478E CLUSTERNODE is set to YES but thecluster software is not available on thissystem.

Explanation: The load library that the operatingsystems provides to obtain the cluster name is notavailable on this system.


User response: Ensure that the cluster software isinstalled on the system.

FMV1479E CLUSTERNODE is set to YES but thismachine is not a member of a cluster.

Explanation: This machine is not a member of acluster node. Possible causes are that the cluster servicehas not been configured correctly, or that the cluster isin the process of initialization.


User response: Ensure that the cluster software isconfigured properly. If the cluster is in the process ofinitialization, retry the operation at a later time.

FMV1480E CLUSTERNODE is set to YES but thecluster service is not enabled on thissystem.

Explanation: The cluster service has not been enabledon this system.


User response: Enable the cluster service on thesystem.

FMV1481E The CLUSTERNODE option is notsupported on this system.

Explanation: This option is not supported on thissystem.


User response: Disable the CLUSTERNODE option inthe local options file.



FMV1482E An unexpected error (retcode) occurredwhile the program was trying to obtainthe cluster name from the system.

Explanation: An unknown error occurred while theprogram was trying to obtain the cluster name from thecluster service. The error code is the reason codeprovided directly from the cluster service being used inthis operating system environment.


User response: Consult the documentation for yourclustering software for an explanation of the reasoncode. Insure that your clustering service is operational,then try the Tivoli Storage Manager operation again.

FMV1483I Schedule log pruning started.

Explanation: The schedule log pruning function hasbegun.

System action: The schedule log is pruned.


FMV1484I Schedule log pruning finishedsuccessfully.

Explanation: The schedule log pruning functioncompleted with no errors.



FMV1487E An error occurred while backing up theWMI repository. The database will notbe backed up.

Explanation: The Windows event log and TivoliStorage Manager error log might contain additionalinformation related to this error.


User response: Examine the Windows event log andTivoli Storage Manager error log for messages relatedto WMI. Ensure that the Windows ManagementInstrumentation service is started.

FMV1489E The WMI service failed to stop. No fileswill be restored.

Explanation: An error occurred while stopping theWindows Management Instrumentation (WMI) service.The database will not be restored.


User response: Examine the Windows event log andTivoli Storage Manager error log for messages relatedto Windows Management Instrumentation (WMI). Youmight need to quiesce WMI activity or reboot themachine in order to free resources which are preventing

the WMI service from stopping.

FMV1490W File specification 'file-spec' ignored. Afile list has already been specified.

Explanation: A non-option argument (filespecification) was encountered after the -FILELIST hasbeen processed.

System action: The argument is ignored.

User response: You may have either a -FILELIST orexplicit file specifications on this command, but notboth.

FMV1492S Invalid virtual mountpoint filespace-name:File not found.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid because it could notbe found in the file system.


User response: Check the virtual mountpoint in thesystem options file and make sure it exists in the filesystem. Retry the operation.

FMV1493S Invalid virtual mountpoint filespace-name:Access denied.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid because access to itis denied.


User response: Check the VIRTUALMOUNTPOINT inthe system options file and make sure it is accessible.Retry the operation.

FMV1494S Invalid virtual mountpoint filespace-name:Symbolic link.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid because it is asymbolic link and FOLLOWSYMBOLIC is not set.


User response: Set the option FOLLOWSYMBOLIC toYES in the user options file. Retry the operation.

FMV1495S Invalid virtual mountpoint filespace-name:Other error, rc = return-code.

Explanation: The specified VIRTUALMOUNTPOINTin the system options file is invalid.




User response: Make sure the virtual mountpoint is adirectory and accessible from the shell, and retry theoperation.

FMV1496W Duplicate include/exclude option 'optionfile-name' found while processing theclient options file. This might produceunexpected results.

Explanation: Tivoli Storage Manager found aduplicate statement while processing the client optionsfile, which might produce unexpected results.


User response: Verify if you obtained the desiredresults. If not, you need to correct the client options fileby removing the duplicate option statement.

FMV1497W Duplicate include/exclude option 'optionfile-name' found while processing theclient options passed by the server. Thismight produce unexpected results.

Explanation: Tivoli Storage Manager found aduplicate statement while processing the client optionsby the server, which might produce unexpected results.


User response: Verify if you obtained the desiredresults. If not, you need to correct either the clientoptions file or the client options passed by the server.

FMV1498E The IIS services failed to stop. No fileswill be restored.

Explanation: An error occurred while stopping theInternet Information Services (IIS) services. Themetabase will not be restored.


User response: Examine the Windows event log andTivoli Storage Manager error log for messages relatedto Internet Information Services (IIS). You might needto quiesce IIS activity or reboot the machine in order tofree resources which are preventing the IIS service fromstopping.

FMV1499E Creation of table of contents failed.

Explanation: A failure occurred on the server duringcreation of the table of contents.

System action: The table of contents was not created.

User response: This abort code indicates there was aproblem creating a table of contents on the server. Thesysadmin will need to consult the activity log on theserver to determine the cause.

FMV1500E Module dsmtca not found in securedirectory.

Explanation: Tivoli Storage Manager cannot find theTrusted Communication Agent module (dsmtca) in theappropriate directory.


User response: Log on as root user, then create a linkto dsmtca module in /usr/bin with the command: ln -s/usr/tivoli/tsm/client/ba/bin/dsmtca/usr/bin/dsmtca

FMV1501E Trusted agent execution/ownerpermissions are invalid

Explanation: The Trusted Communication Agentexecution/owner permissions are invalid.


User response: Have your system administrator checkthe installation instructions for the client to ensure thatthe Trusted Communication Agent permissions are setcorrectly. This error can be caused by installing TivoliStorage Manager as a non-root user. For the UNIXplatforms that have the installation program(dsm.install), you must run dsm.install while logged inas the root user.

FMV1502E Access to system function required torun has been denied

Explanation: The permissions of the TrustedCommunication Agent do not allow it to be accessedby the user of the Tivoli Storage Manager client.



FMV1503E Valid password not available for server'server-name'. The administrator for yoursystem must run Tivoli Storage Managerand enter the password to store itlocally.

Explanation: The file containing the stored passwordfor the specified server server-name is unavailable.


User response: The administrator for your systemmust set and store a new password.

FMV1504E Error starting the TrustedCommunication Agent process.

Explanation: An error has occurred starting theTrusted Communication Agent process; specifically, thefork() function has failed.




User response: Probable system error. If the problempersists, restart the workstation.

FMV1505W Performing image backup of the entirevolume for volume name. TheIMAGEGAPSIZE option value of imagegap size is being ignored as this level ofthe operating system does not supportused block image backup. Pleaseupgrade to AIX 5.3 Maintenance Level 7or later in order to perform used blockimage backup.

Explanation: AIX 5.3 Maintenance Level 7 or later hassome necessary fixes that are required to support usedblock image backup.


User response: Please upgrade to AIX 5.3Maintenance Level 7 or later in order to perform usedblock image backup.

FMV1506E The Tivoli Storage Manager TrustedCommunication Agent received aninvalid request.

Explanation: The Trusted Communication Agent isinvoked by the Tivoli Storage Manager client and hasreceived an unknown request argument in the call.


User response: It is possible the TrustedCommunication Agent was mistakenly invoked by aprocess other than the Tivoli Storage Manager client. Ifthat is not the case, then this is an internal error. If theproblem recurs, contact your IBM servicerepresentative.

FMV1507E This action requires Tivoli StorageManager administrative authority onthis system.

Explanation: An activity has been attempted that mustbe performed by the Tivoli Storage Manageradministrator (for example, open registration, filespacedelete or password update).


User response: If the activity is required, theadministrator for this system must perform it.

FMV1508E Error allocating semaphores.

Explanation: An error has occurred because thesemaphores you are attempting to allocate have becomeinsufficient.


User response: Ask your system administrator for

assistance, and possibly increase the number ofsemaphores in your system.

FMV1509E Error setting semaphore value orwaiting on semaphore.

Explanation: An error has occurred while attemptingto set or wait on a semaphore.


User response: Probable system error. If the problempersists, restart the workstation.

FMV1510W The specified backupset either does notexist, or does not contain file data.

Explanation: The specified backupset either does notexist, or does not contain file data for the node namespecified. The restore backupset command is limited tobackupsets that contain file data. To restore an imagebackup from a backupset, use the restore imagecommand.


User response: If an incorrect backupset name wasspecified, try the command again with the correctbackupset name. If you are trying to restore an imagefrom a backupset, refer to the restore image commandfor the correct syntax.

FMV1511I Invalid Restore session number entered.Try again.

Explanation: You entered a number not shown in thelist of restartable restores. The number you entered iseither less than one or greater than the highest itemnumber displayed.



FMV1512E Scheduled event 'event' failed. Returncode = value.

Explanation: One or more error conditions wereencountered that prevented the schedule fromcompleting successfully. This message is preceded byother messages that indicate the specific problemsencountered during the operation.

System action: Scheduled event failed.

User response: Check the schedule and error log filesfor the messages that specify what problems wereencountered during the operation. Correct theconditions that caused those messages to be issued. Thespecific corrective actions will depend on the specificerrors encountered.

For more information about return codes, search for



"client return codes" in the product information(www.ibm.com/support/knowledgecenter/SSGSG7/).

FMV1513E The object 'object_name' is skipped fromrename. Error_condition.

Explanation: IBM Tivoli Storage Manager skips thespecified object from renaming because the object withthe same long name but with different attributes existson the server.

System action: The backup operation continues. Thespecified object will expire during the next incrementalbackup.

User response: The object is skipped if one of thefollowing condition occurs:

v The long name object(LN) has a more recent insertdate than the short name object(SN).

v The management classes for LN and SN do notmatch.

v The copy groups for LN and SN do not match.

v LN and SN have different owners.

v The creation date for LN and SN do not match.

v The short name attribute for LN does not match SN.

If you are unable to determine what is wrong, reportthe problem to your service representative.

FMV1514W Encryption key passwords are not thesame.

Explanation: The key passwords are different.

System action: Tivoli Storage Manager allows you totry again.

User response: Enter the correct password.

FMV1515E Loading a table of contents failed.

Explanation: A failure occurred on the server duringloading of the table of contents.

System action: The table of contents was not loaded.

User response: This abort code indicates there was aproblem loading a table of contents on the server. Thesysadmin will need to consult the activity log on theserver to determine the cause.

FMV1519E Your node does not have permission todelete backup files

Explanation: The server does not allow your node todelete backup files.

System action: Tivoli Storage Manager did not deletethe backup files.


FMV1520E Failure writing to the Tivoli StorageManager error log: errno = errno-value,

Explanation: A failure was encountered when writingto the dsmerror log or dsierror log. The system set theerror code errno-value. It is possible that no space isavailable at the given log location.



FMV1521E Failure writing to a Tivoli StorageManager log or log-related file: file-name,errno = errno-value, reason




FMV1522E It is not possible to authenticate withthe client node client-node ! The SpaceManagement Agent version agent-versionrunning on client-node does not matchwith the Space Management Consoleversion console-version you are running !

Explanation: The version of the Space ManagementConsole does not match with the version of the SpaceManagement Agent running on the client nodemachine. To avoid incompatibleness it is necessary torun the console and the agent with the same version.

System action: The Space Management Console exits.

User response: Use Space Management Console withthe same version like the Space Management Agentrunning on the HSM node you want to manage.

FMV1523E An error occurred while connecting toTSA/SMDR service.

Explanation: An error was encountered during a callto the TSA/SMDR service. This message usuallyfollows previous messages that contain more specificinformation about the problem.


User response: Refer to previous messages indsmerror.log for further information. If those messagesare not helpful in identifying the cause of the problem,see your system administrator for further assistance.



FMV1528I Tivoli Storage Manager is converting thelog-file from continuous (pruning) modeto wrapping mode. This process maytake several minutes.

Explanation: The log-file was previously in continuousmode where the only size control was through the useof ERRORLOGRETENTION orSCHEDLOGRETENTION option. This is the firstoccasion where ERRORLOGMAX or SCHEDLOGMAXis specified for this log, so its format must be changedand old data saved.



FMV1529I Tivoli Storage Manager is converting thelog-file from wrapping mode tocontinuous (pruning) mode. Thisprocess may take several minutes.




FMV1530I count log records processed.




FMV1532E Proxy Rejected: Proxy authority has notbeen granted to this node.

Explanation: The node has not been granted proxyauthority to access the node named by theASNODENAME option. The Tivoli Storage Manageradministrator must first grant proxy authority.


User response: The Tivoli Storage Manager serveradministrator must grant proxy authority for this node.See the administrator command "Grant Proxynode".

FMV1533E Proxy Rejected: The node name youspecified in the ASNODENAME optionis locked.

Explanation: The Tivoli Storage Manageradministrator has locked the node you specified as theASNODENAME option.


User response: The Tivoli Storage Manager serveradministrator must unlock the node before you canaccess it. Try the operation later, or check with yourTivoli Storage Manager administrator.

FMV1534E Proxy Rejected: The Tivoli StorageManager server has run out of memory.

Explanation: There is not enough memory available toallow this operation to continue.


User response: Try the operation again. If the problemcontinues, see your system administrator to increase theamount of memory of the server.

FMV1535E Proxy Rejected: ASNODENAME andNODENAME are identical.

Explanation: Tivoli Storage Manager does not allowthe ASNODENAME and NODENAME option values tobe the same.


User response: Use the ASNODENAME option onlyto access another node. It is not necessary to setASNODENAME option to access your own node.Remove ASNODENAME from your option file unlessyou are actually trying to access a node that you havebeen granted authority to access with theadministrative command "Grant Proxynode".

FMV1536E Proxy Rejected: The server has aninternal error.

Explanation: The client cannot proxy to the nodenamed by the ASNODENAME option because of aninternal server error.


User response: See your system administratorimmediately.

FMV1537E The ASNODENAME option is not validwith the FROMNODE option.

Explanation: None.


User response: Remove the ASNODENAME optionfrom the options file or do not use the FROMNODEoption.



FMV1538E The operation that is being attemptedcannot be invoked using theASNODENAME option.

Explanation: None.


User response: Remove the ASNODENAME optionand retry the operation.

FMV1539E The ASNODENAME option cannot beused with the CLUSTERNODE option.

Explanation: None.


User response: Remove the ASNODENAME optionand retry the operation.

FMV1540E Incremental backups using snapshotdifference is not supported on thisversion of the NetApp file server.

Explanation: Incremental backup using Snapshotdifference requires Data ONTAP V7.3 or later. To backup unicode file names, upgrade to Data ONTAP V7.3.3or later or V8.1 or later.


User response: Upgrade the file server to a supportedlevel of Data ONTAP, then retry the operation.

FMV1544E An error in WAS processing hasoccurred.

Explanation: None.

System action: None

User response: Run the following command to see thenodes that can be backed up: dsmc query was-wastype=local Make sure the results are correct foryour environment, then try the operation again. If theproblem persists, contact Tivoli Storage Managertechnical support for further assistance.

FMV1546W Tivoli Storage Manager failed to lockthe WebSphere configuration repository.

Explanation: None.

System action: The lock of the WebSphere®

configuration repository fails.

User response: Ensure that the WebSphere server isrunning. If the server is already running, ensure thatthe repository is unlocked. Ensure that you are backingup the correct node. To see a list of available nodes thatcan be backed up, enter: 'dsmc q was -wastype=local'.

FMV1547W Tivoli Storage Manager failed to unlockthe WebSphere ConfigurationRepository.

Explanation: None.

System action: The unlock of the WebSphereConfiguration Repository fails.

User response: Make sure that the WebSphere serveris running. If the repository is locked, then unlock itand try the operation again. Ensure that the correctnode is being backed up. To see a list of availablenodes that can be backed up, run: 'dsmc q was-wastype=local'.

FMV1548E A supported version of WebSphere isnot installed on this machine.

Explanation: A supported version of WebSphere is notinstalled on this machine. The only version ofWebSphere that is supported is 5.0.x.

System action: None

User response: Install WebSphere 5.0 on the machine.

FMV1549E No application server instances werefound. Unable to perform backup.

Explanation: The application server is not installed onthis machine.

System action: Backup is not performed.

User response: Install the application server.

FMV1550E No network deployment managerinstances were found to back up.

Explanation: Deployment manager is not installed onthis machine.

System action: Back up is not performed.

User response: Install the network deploymentmanager.

FMV1552W A user name and a password have notbeen provided to Data Protection forWebSphere.

Explanation: The dsmc set WASPassword commandhas not been run to provide the user name and thepassword for Data Protection for WebSphere. DataProtection for WebSphere needs the user name andpassword to be able to run when WebSphere security isturned on.

System action: Data Protection for WebSphere cannotrun.

User response: Run the dsmc set WASPasswordcommand to set the WebSphere security user name andpassword.



FMV1553W The user name and password that havebeen provided to Data Protection forWebSphere are invalid.

Explanation: None.

System action: Data Protection for WebSphere cannotrun.

User response: Run the dsmc set WASPasswordcommand to set the WebSphere security user name andpassword.

FMV1555E The WebSphere Application Server(WAS) plug-in level must be at 5.2.1 orgreater to set the WebSphere user andpassword.

Explanation: You must have the backup-archive clientand the WAS plug-in at a level of 5.2.1 or higher to beable to connect to WebSphere when security is enabled.

System action: WebSphere does not set the user andpassword.

User response: Upgrade the WAS plug-in to 5.2.1 orgreater.

FMV1556E Setting the WAS user and passwordfailed.

Explanation: Password validation for the WAS userand password failed.

System action: WAS password validation fails.

User response: Rerun the set WASPassword commandwith the correct values for user and password.

FMV1557W The WAS Server was not running, andthe password file was saved withoutvalidation.

Explanation: If the WAS server is down, then it is notpossible to connect to the server and validate theuser-entered password. The password has still beensaved, but no validation has been performed.

System action: The set WAS password command didnot validate the password. The password has still beensaved, but no validation has been performed. Thepassword may be incorrect.

User response: There are two options:

v Try a backup. If the backup performs a failover, andthere is a incorrect password message in the errorlog, then the password that was entered is incorrect.

v Start the WAS server and rerun the set passwordcommand. Since the server is now up, validation willbe performed as normal and the user notified if agood/bad password was entered.

FMV1560W The WebSphere server is not running.

Explanation: The WebSphere server is not running.The WAS server is running for backup operations.

System action: The WebSphere server is not running.

User response: Start the WAS server and run thebackup again.

FMV1562E WAS Restore failed during EARExpansion.

Explanation: EAR Expansion is performed for aWebSphere Application server after the files have beenrestored.

System action: WAS restore fails.

User response: Run the restore again.

FMV1563W The itsm.was.properties file does notexist.

Explanation: The itsm.was.properties file is used tostore the WebSphere security user name and password.


User response: Run the dsmc set waspasswordcommand to create this file.

FMV1565E No WebSphere EARExpander wasfound. Copy the EARExpander toolfrom the base WebSphere bin directoryto the instance bin directory, then runthe restore operation again.

Explanation: The EAR files are expanded for aninstance of an Application server and the EARExpandertool does not exist in the instance bin directory.

System action: No WebSphere EARExpander found.

User response: Copy the WAS EARExpander toolfrom the base install's bin directory to the bin directoryof the instance. Then run the WAS restore operationagain, after the EARExpander tool has been copied.

FMV1566E The version of WebSphere on themachine does not match the version ofWebSphere that was backed up. Theseversions must match for a WAS restoreoperation.

Explanation: The version of WebSphere on themachine does not match the version of WebSphere thatwas backed up. These versions must match for a WASrestore operation.

System action: The WAS restore operation fails.

User response: Install the correct version ofWebSphere on the machine before performing therestore operation.



FMV1567I A 5.2.2 or higher client is restoring databacked up from a 5.2.0 client. Noversion check can be performed beforethe restore.

Explanation: WebSphere's version information was notstored as part of the backup for 5.2.0. So, a 5.2.2 clientcannot ensure that the version of WAS that is beingrestored is the same version of WAS that is on themachine. A version of WAS that is restored may beincompatible with the version of WAS on the machineand can cause errors in WAS.

System action: No version check is performed.

User response: Make sure that the version of WASthat is being restored is the same as the version of WASthat is installed on the machine.

FMV1568E The CAD attempted to register it'stcpport and tcpip address without usingthe TCPCADADDRESS option.

Explanation: The CAD sent the port and addressinformation to the server, however, there was aproblem registering the information with the server.The problem occurred because no default value for thetcpip address was provided. The server was unable todetermine a default value for the tcpip address becausethe communication method was not tcpip.

System action: The server cannot register theinformation for the CAD. CAD processing willcontinue, but some functions of the CAD may not beworking properly.

User response: Use TCPCADADDRESS in the clientoption file to indicate the proper TCP/IP address forthis CAD.

FMV1569E The CAD attempted to register it'stcpport and tcpip address but theTCP/IP address resolved to the loopbackaddress and was rejected by the server.

Explanation: The CAD sent the port and addressinformation to the server, however, there was aproblem registering the information with the server.The problem occurred because the server detected thatthe address provided resolved to the loopback address.

System action: The server did not register theinformation for the CAD. CAD processing willcontinue, but some functions of the CAD may not beworking properly.

User response: Use TCPCADADDRESS in the clientoption file to indicate the proper TCP/IP address forthis CAD. Loopback address is not valid.

FMV1570E Registering this instance of the Cadwith the server failed. Cad processcontinues.

Explanation: The CAD failed to register addressinformation to the server, due to an error. There shouldbe a message immediately preceding this message thatwould indicate the problem more precisely.

System action: The server did not register theinformation for the CAD. CAD processing willcontinue, but some functions of the CAD may not beworking properly.

User response: Look at messages immediatelypreceding this message to help determine what erroroccurred.

FMV1571E The time-option option cannot be usedwithout specifying the date-option option

Explanation: If the to/from/pit time options isspecified then the corresponding to/from/pit dateMUST also be specified.


User response: Either remove the to/from/pit timeoption or add the corresponding to/from/pit dateoption.

FMV1572E An unexpected error was received fromthe server query, RC=re tcode.

Explanation: An unexpected error was received by theclient. This could be caused by network problems or aprogramming error.


User response: Verify that your communication pathis functioning properly and try the operation again. Ifthe problem persists, contact your Tivoli StorageManager administrator for further assistance.

FMV1573E FROMDATE and TODATE cannot beused with PITDATE.

Explanation: The PITDATE option specifies differentand conflicting date selection criteria from theFROMDATE and TODATE options. Therefore theseoptions cannot be combined.


User response: Determine whether you require thefunctionality of PITDATE or FROMDATE andTODATE, then try the operation again. If you want torestore files as of a certain date and time, use PITDATEand PITTIME. If you want to restore files from a givenrange of dates, use FROMDATE, TODATE,FROMTIME, and TOTIME. Refer to the Tivoli StorageManager client manual for your operating system for



additional information about these options.

FMV1574E Journal Query Failed.

Explanation: The journal daemon was unable toprocess the requested journal query.

System action: Journal backup processing isinterrupted.

User response: Retry the backup, check the journaldaemon errorlog for the cause of the failure. Backup ofother file systems in the domain will continue.

FMV1575E Journal Daemon Communications Error.

Explanation: An error occurred communicating withthe journal daemon.

System action: Journal backup processing isinterrupted.

User response: Retry the backup, check the journaldaemon and client errorlogs for the cause of the failure.

FMV1576W Space Management Agent versionmismatch. The Space ManagementAgent (hsmagent) version agent-versionrunning on 'client-node' client node doesnot match with the Space ManagementConsole (GUI) version console-versionyou are running! To avoid compatibilityproblems, please use the same versionfor the Space Management Console andthe Space Management Agent. Do youwant to proceed?

Explanation: The version of the Space ManagementConsole does not match with the version of the SpaceManagement Agent running on the client nodemachine. To avoid compatibility problems, please usethe same version for the Space Management Console(GUI) and the Space Management Agent (hsmagent).

System action: Prompt the user to exit or continue.

User response: Use Space Management Console (GUI)with the same version like the Space ManagementAgent (hsmagent) running on the HSM node you wantto manage.

FMV1577I The Windows console event handlerreceived a 'event' console event.

Explanation: A console event was received by one ofthe IBM Tivoli Storage Manager processes or programs.The following events can be received:




FMV1578E The specified path 'path' is not valid forbackup or archive.

Explanation: The specified path is a special file systemor part of a special file system. Special file systemscontain dynamic information generated by theoperating system and should not be backed up orarchived. Refer to the Tivoli Storage Manager clientmanual for a complete list of special file systems foryour operating system.

System action: Processing continues if there are otherfile systems to back up.

User response: Do not specify special file systems forbackup or archive.

FMV1579E GSKit function func-name failed witherror-code: session

Explanation: A GSKit function has failed with thespecified error code.

System action: Processing stopped

User response: Make sure you have configured thekey database for SSL communication as described inthe documentation. If the problem persists, contactTivoli Storage Manager customer support.

FMV1580W An Include.Fs statement withperformance algorithm set already existsfor the drive specified. Do you want toreplace the statement?

Explanation: The user tried to create a duplicateInclude.Fs entry on a drive that already has aperformance algorithm associated with it. This isapplicable to the Preference Editor on the MFC GUI

System action: The user can replace the statementwith the new one or they can cancel out of thisoperation

User response: The user is prompted to replace thestatement with the new one or they can say No tocancel out of this operation.

FMV1581W 'object-name' was restored as 'temp-name'.A reboot is required to complete therestore.

Explanation: This is a system file restored and couldnot be immediately replaced. The file will be replacedduring the next reboot of the operating system. It isimportant to note that until the reboot occurs, thechanges will not be in effect.

System action: Tivoli Storage Manager restored thefile with a temporary name, and instructed theoperating system to replace the original file with therestored file during the next boot of the operatingsystem.




FMV1583E The Hardware Utility plug-in modulewas not found or could not be loaded.



User response: Run "dsmc show plugins" at the TivoliStorage Manager command-line client prompt to seethe available plug-ins on the system and verify thepath which is being used to load the plug-ins. If theplugin path is available and the Hardware Utilityplug-in, libPiHDW.a, is present, ensure that theLIBPATH variable is set to the Hardware product'slibrary path, for example, LIBPTH=/usr/opt/db2_08_01/lib.

FMV1584E Error loading system library'libdevmapper.so' required for imageoperations for LVM2 volumes.

Explanation: The system library libdevmapper.sorequired for LVM2 image operations could not beloaded. This error can occur when the library does notexist on the system, or the library is an earlier levelthan is required. This error also occurs when the librarycan not be opened by the Tivoli Storage Manager clientiprocess.

System action: The image operations for LVM2volumes are not available.

User response: Check the installed packages and thelibrary versions on the system. If correct versions areinstalled, check for access related issues. If the systemdoes not have these libraries installed, contact yourLinux OS distributer. Also, refer to Technote 1452629:https://www.ibm.com/support/docview.wss?uid=swg21452629

FMV1587W Unable to read extended attributes forobject object-full-name due to errno:errno-value, reason: errno-explanation

Explanation: The extended attributes of the objectcould not be read. The system set the error codeerrno-value and the reason errno-explanation. If thereason errno-explanation is either "access denied" or"permission denied", the current user does not havepermission to read the extended attributes of the object.


User response: The error is expected if the operationtries to read extended attributes of an object that youdo not own or do not have access to. If the reasonindicates an input/output error, perform the file systemconsistency check procedure and try the operationagain. If the problem persists, contact IBM technical

support for further assistance.

FMV1588W I/O error reading file attribute: attr-namefor: file-name. errno = errno-value,

Explanation: The attribute attr-name of the filefile-name could not be retrieved. The system set theerror code errno-value. If the reason given is "accessdenied," the current user does not have permission toread the file attributes.

System action: Processing continues without backingup the specified file attribute.

User response: Correct the condition causing thephysical error.

FMV1589W Unable to write extended attributes forobject-full-name due to errno: errno-value,reason: errno-explanation

Explanation: The extended attributes of the objectcould not be written. The system set the error codeerrno-value and the reason errno-explanation. If thereason is either "access denied" or "permission denied",the current user does not have permission to write theextended attributes of the object.

System action: Processing continues without restoringthe extended attributes.

User response: The error is expected if the operationtries to write extended attributes to an object that youdo not own or do not have access to. If the reasonindicates an input/output error, perform the file systemconsistency check procedure and retry the operation. Ifthe problem persists, contact IBM technical support forfurther assistance.

FMV1590W I/O error writing file attribute: attr-namefor: file-name. errno = errno-value,

Explanation: The attribute attr-name of the filefile-name could not be set. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to set the fileattributes.

System action: Processing continues without restoringthe specified file attribute.

User response: Correct the condition causing thephysical error.

FMV1592E Failed to initialize SSL protocol.

Explanation: Tivoli Storage Manager was unable toinitialize SSL protocol.


User response: Check for GSKit related messages inthe error log. Make sure you have configured the keydatabase for SSL communication as described in the



documentation. If the problem persists, contact TivoliStorage Manager customer support.

FMV1593E Cannot open the key database.

Explanation: Tivoli Storage Manager was unable toopen the keyfile that is expected to contain the servercertificate for SSL communications.


User response: Make sure you have configured thekey database for SSL communication as described inthe documentation. If the problem persists, contactTivoli Storage Manager customer support.

FMV1594E The key database password is incorrector unavailable.

Explanation: The client was unable to open thecertificate key database using the stored password, orthe stored password could not be read.


User response: Make sure that you configure the keydatabase for SSL communication as described in theClient Installation and User's Guide. Also make surethat the stash file, dsmcert.sth, is readable by thecurrent user.

FMV1595E Bad server certificate.

Explanation: Tivoli Storage Manager was unable toopen SSL connection to server because of a badcertificate. This error usually occurs when the servercertificate cannot be verified by the client.


User response: Make sure you have configured thekey database for SSL communication as described inthe documentation. Make sure to import the correctcertificate from the Tivoli Storage Manager server youare trying to connect to.

FMV1596E SSL protocol is not supported.

Explanation: SSL protocol is not supported on thisplatform.


User response: Refer to Tivoli Storage Managerdocumentation for the list of supported platforms.

FMV1597E The -pick and -deltype=all options arenot valid together.

Explanation: -deltype=all is used to delete an entiredirectory tree. You cannot use -pick to select individualobjects from the tree. -pick is valid only with-deltype=active or -deltype=inactive.


User response: Try the operation again with a validcombination of options. If you want to delete an entiretree, use -deltype=all, but do not use -pick. If you wantto select which backup versions to delete, specify-deltype=active or -deltype=inactive, and use the -pickoption. Also use -subdir=yes if you want the fileselection to include files in subdirectories of the filespecification. See the client manual or command linehelp for additional information.

FMV1598E -deltype=all is not valid for this filespecification.

Explanation: -deltype=all is used to delete an entiredirectory tree. You must specify a fully wildcarddirectory when using -deltype=all.


User response: Try the operation again with a validcombination of options. If you want to delete allbackup versions of an entire directory tree, use-deltype=all and a fully wildcarded file specification. Ifyou want to delete backup versions of partiallyqualified file names, use -deltype=inactive or-deltype=active. Also use -subdir=yes if you want todelete backup versions in subdirectories of the filespecification. See the client manual or command linehelp for additional information.

FMV1599E Cannot load SSL runtime library.

Explanation: Tivoli Storage Manager failed todynamically load SSL runtime library necessary for SSLprotocol


User response: Make sure Tivoli Storage Managerclient is properly installed. Try to reinstall the clientsoftware. If the problem persists, contact Tivoli StorageManager customer support.

FMV1600E Unable to load the Data Protection forLotus Domino library.

Explanation: The Datt Protection for Lotus® Domino®

library could not be loaded.


User response: Ensure that Domino plugin is properlyconfigured and check the error log on the clientmachine for more information.

FMV1601E The Domino plugin operation failedbecause of an internal error.

Explanation: A Domino plugin internal error hasoccurred.


User response: Check the error log on the client



machine for more information.

FMV1602E The Domino plugin operation failedbecause the preferences file was notfound.

Explanation: The Data Protection for Lotus Dominopreference file could not be found.


User response: The Data Protection for Lotus forDomino configuration file (default name domdsm.cfg)could not be found. Check the error log on the clientmachine for more information.

FMV1603E The Domino plugin operation failedbecause of an internal TCP/IP error.

Explanation: A TCP/IP error has occurred.


User response: Check the error log on the clientmachine for more information.

FMV1604E The Domino plugin operation failedtrying to start the dsmdomp addressspace.

Explanation: The dsmdomp address space could notbe started. This is probably an installation error.


User response: Ensure that the lotus/bin directory hasa symbolic link to the tools directory for dsmdomp andthe lotus/notes directory has a symbolic link to thedsmdomp executable. If the problem persists, contactyour System Administrator for further assistance.

FMV1605E The Domino plugin operation failedwhile initializing communications withthe dsmdomp address space.

Explanation: The Domino plugin communicationinitialization failed.


User response: The dsmdomp address space failedduring its initialization. This is likely to be aninstallation error. Ensure that the lotus/bin directoryhas a symbolic link to the tools directory for dsmdompand the lotus/notes directory has a symbolic link to thedsmdomp executable. If the problem persists, contactyour System Administrator for further assistance.

FMV1606E The Domino plugin operation failedwhile starting up the dsmdomp addressspace.

Explanation: The dsmdomp address space could notbe started.

System action: The TDP for Domino processing stops.

User response: The dsmdomp address space failedduring its initialization. This is likely to be aninstallation error. Ensure that the lotus/bin directoryhas a symbolic link to the tools directory for dsmdompand the lotus/notes directory has a symbolic link to thedsmdomp executable. Examine the file/tmp/dsmdomp* for more information. If the problempersists, contact your System Administrator for furtherassistance.

FMV1607E A plugin found in the plugins library isnot supported by the current level of theTivoli Storage Manager client.

Explanation: The plugin is not loaded, and processingcontinues.

System action: The plugin is not loaded, andprocessing continues.

User response: This probably is an installation error.Ensure that the plugins directory contains valid pluginlibraries, and that the correct level of the Tivoli StorageManager client has been installed. If the problempersists, contact your System Administrator for furtherassistance.

FMV1608E Domino plugin operation failed withthe following message: messsage

Explanation: A Domino plugin operation erroroccurred.


User response: Correct the error that caused theoperation to fail.

FMV1609E Domino plugin process failed. Thefollowing messages are associated withthe error. messsage.

Explanation: A Domino plugin operation erroroccurred.


User response: Correct the error that caused theoperation to fail.

FMV1611E A plugin operation failed because of aninternal error.

Explanation: A plugin internal error has occurred.

System action: The plugin operation stops.

User response: If the error persists, run with tracingenabled and contact your System Administrator andIBM for further assistance.



FMV1612E The Domino plugin operation failedbecause of a Tivoli Storage ManagerAPI error.

Explanation: An Tivoli Storage Manager API erroroccurred .


User response: Check error log on the client machinefor more information.

FMV1613E >Could not load the Tivoli StorageManager API.



User response: Check error log on the client machinefor more information.

FMV1614E The Domino plugin 'Try and Buy'license has expired.

Explanation: The 'Try and Buy' license that wasdetected has expired.



FMV1615E The Domino plugin operation faileddue to a license error.

Explanation: Domino plugin license verification failed.


User response: Check the error log for furtherinformation.

FMV1616E The Domino plugin operation failedbecause the Lotus Domino API couldnot be loaded.

Explanation: The Lotus Domino API could not beloaded.


User response: Ensure the Lotus Domino Server isinstalled correctly.

FMV1617E The Domino plugin operation failedbecause of a Data Protection for DominoAPI error.

Explanation: A Data Protection for Domino API erroroccurred during a Domino plugin operation.


User response: For more details, view the followingTivoli Storage Manager error logs.

The API error log (dsierror.log) and the log of DataProtection for Domino activity (domdsm.log). Thedefault location of these logs is the Data Protection forDomino installation directory.

The backup-archive client error log (dsmerror.log), theweb client error log (dsmwebcl.log), and the log ofscheduler activite (dsmsched.log). The default locationof these logs is the backup-archive installationdirectory.

FMV1618E A Domino plugin operation is alreadyin progress. Please wait for operation tocomplete.

Explanation: A Domino plugin operation is inprogress.

System action: The Domino plugin operation stops.

User response: Please wait for the Domino pluginoperation to complete before starting a new Dominoplugin operation.

FMV1619E The IBM Tivoli Storage Managerapplication client cannot work with theversion of the Domino plugin you haveinstalled.

Explanation: The version of the Domino plugincurrently installed on the system is older than theversion used to build the IBM Tivoli Storage Managerapplication client.


User response: Install a version of the Domino pluginat or later than the level of the IBM Tivoli StorageManager application client.

FMV1621E Failed to update backup attributes onserver for local backup for 'filespacenamepath-namefile-name', object id -'object-id':'object-id' return code 'returncode'.

Explanation: Tivoli Storage Manager failed to updateattributes for the named backup object on the server.The server may not reflect correct state of the backup.


User response: Check preceding error messages inerror log for more information. Retry the operation. Ifproblem continues, contact your Tivoli StorageManager administrator.



FMV1622I Number of backup objects cleaned upon server: 'number' number of localsnapshot resources made available:'number'.

Explanation: While performing consistency check forserver's database and the local repository maintainedon the client system, reported inconsistencies werefound. Inconsistent backups cannot be restored,therefore Tivoli Storage Manager deletes all inconsistentbackup objects and frees the space occupied in the localrepository.


User response: Check error log for further details onwhich objects on server were deleted. If numbers lookunusually high check your configuration and if itcontinues, contact your Tivoli Storage Manageradministrator.

FMV1623W Backup of NSF DB2 database wasskipped. NSF DB2 databases notsupported.

Explanation: This version of DP for Domino plugindoes not support NSF DB2 databases.

System action: Backup of NSF DB2 databases isskipped.

User response: Exclude NSF DB2 databases frombackup.

FMV1624E 'value' is an invalid value for option'option' for 'command' command

Explanation: The specified option value is not valid inthis context.

System action: The operation was stopped

User response: Specify a valid value for the option.Consult documentation for valid values.

FMV1626E An unexpected error was encounteredwhen processing a Tivoli StorageManager operation using a hardware orsnapshot function. Tivoli StorageManager function name : function-nameTivoli Storage Manager function :function-desc Tivoli Storage Managerreturn code : TSM-rc Tivoli StorageManager file : file-name (line-number)

Explanation: None.


User response: Contact the Tivoli Storage Manageradministrator with the information provided in thismessage.

FMV1627E SVC virtual disk v1 is not valid.

Explanation: The specified virtual disk is not found inthe list of virtual disks provided by the connected SVCcluster.


User response: Ensure that this virtual disk exists inthe SVC.

FMV1628E The source v1 and target v2 virtual disksare in different SVC clusters.

Explanation: The SVC source and target virtual diskshave to be assigned to the same SVC cluster.


User response: Ensure that the source and targetvirtual disks are in the same SVC.

FMV1629E The source v1 and target v2 virtual disksare of different size.

Explanation: The SVC source and target virtual diskshave to be of the same size.


User response: Ensure that the source and targetvirtual disks are the same size.

FMV1630E An error was returned calling anoperation of the Common InterfaceModel(CIM). Tivoli Storage Managerfunction name : function-name TivoliStorage Manager function : function-descTivoli Storage Manager CIM returncode: 0xCIM-rc Tivoli Storage Managerfile : file-name (line-number)

Explanation: An error occurred when calling a CIMoperation of the disk subsystem.


User response: Please see the section about the CIMreturn codes and their descriptions in the productpublication.

FMV1631E A memory allocation error has occurredin file filename, line number linenumber.






FMV1632I 'option name' not specified, defaults to'deafult value'

Explanation: A value for the option is not spedified,default value wil be used.

System action: The operation continues using defaultvalue for the option

User response: To override the default, specify a validvalue for the option. Consult documentation for validvalues.

FMV1647E 'input spec': Invalid input specificationformat.

Explanation: The specified input for this commmandis invalid.


User response: Verify that the syntax specified withthe parameter is correct.

FMV1648W PREViewsize option value is greaterthan the specified stub size.

Explanation: The PREViewsize CLI option valuespecified must not be greater than the stub size for thefile.

System action: Operation stopped. File skipped.

User response: Change the value of the PREViewsizeaccordingly.

FMV1649E The option 'specified-option' isinconsistent with the option'other-option'.

Explanation: The command failed because thespecified option (specified-option) can not be specified incombination with the option (other-option), which is alsospecified.

System action: The command is terminated.

User response: Run the command without thespecified option. Alternatively, run the commandwithout the other option.

FMV1650I Command: command-string

Explanation: The command string listed in themessagewas issued by the Tivoli Storage ManagerBackup-Archive client.

System action: This message is for auditing purposesonly.

User response: This message is for auditing purposesonly.

FMV1651I Backed Up: fshlll

Explanation: The backup operation for the object wassuccessful.



FMV1652I Archived: fshlll

Explanation: The archive operation for the object wassuccessful.



FMV1653I Updated: fshlll

Explanation: The update operation for the object wassuccessful.



FMV1654E Failed: fshlll

Explanation: The backup, archive, restore or retrieveoperation for the object failed.


User response: This message is for auditing purposesonly. For information about the failure refer to theTivoli Storage Manager Backup-Archive Client errorlog.

FMV1655I Restored: fshlll

Explanation: The restore operation for the object wassuccessful.



FMV1656I Retrieved: fshlll

Explanation: The retrieve operation for the object wassuccessful.


FMV1632I • FMV1656I



FMV1657I Expired: fshlll

Explanation: The active version of the object wasexpired in the Tivoli Storage Manager database.



FMV1658I Deleted: fshlll

Explanation: The object was deleted from the TivoliStorage Manager database.



FMV1659I Skipped: fshlll

Explanation: The object was skipped by the userduring backup or archive processing.



FMV1660I Excluded: fshlll

Explanation: The object was excluded from backup orarchive processing.



FMV1661I Unchanged: fshlll

Explanation: The object has not changed since the lastincremental backup was performed and does not needto be resent.



FMV1662I Agent Node: 'agent_node' Target Node:'target_node'

Explanation: Proxy nodes information.

System action: None

User response: None

FMV1663W The option fractional reserve on volumevol_name was reduced to less than 100percent.

Explanation: Network Appliance stronglyrecommends that when the fractional reserve is set toless than 100 percent you actively monitor spaceconsumption and the rate of change of data in thevolume to ensure you do not run out of space reservedfor overwrites. In that case, if you run out of overwritereserve space, writes to the active file system fail andthe host application or operating system might crash.


User response: Ensure that you monitor the spaceconsumption. Consult Network Appliance for tools tomonitor available space in your volumes.

FMV1664E The snap restore for volume volnamewith snapshot name snapname woulddestroy later snapshots that are requiredfor other applications or for volumeclones.

Explanation: ONTAP will delete newer snapshots of avolume when a specific snapshot is used for snaprestore.


User response: Prior to a snap restore, ensure thatnewer snapshots are not used in other applications orin volume clones.

FMV1665W Tivoli Storage Manager for ACS did notfind any snapshots for volume volnameon the N series filer.

Explanation: No snapshots were found for thisvolume on the N series filer.



FMV1666W Tivoli Storage Manager for ACS did notfind any information about the N seriesvolume volname.

Explanation: The query for information about thisvolume did not return any data.



FMV1657I • FMV1666W


FMV1667E The snapshot name snapname for volumevolname was not found in the snapshotlist on the N series filer.

Explanation: Snapshot identified by this name doesnot exist.



FMV1668E The 'drive-name1' is not a local disk.

Explanation: The specified file system is network diskor network share. Because the CLUSTERNODE optionis set to YES, the file system cannot be backed up orarchived.



FMV1669W The command subcommand command canonly be run in Windows WinPE mode.

Explanation: The command subcommand command isnot supported on a currently running operating system.You must reboot to Windows WinPE mode to run thiscommand.



FMV1670E The file specification is not valid.Specify a valid Network Appliance orN-Series NFS (AIX, Linux) or CIFS(Windows) volume.

Explanation: The file specification is not valid.Incremental backup using snapshot difference using the-SNAPDIFF option can only be performed on NetworkAppliance or N-Series NFS volumes on AIX and Linux,and on CIFS volumes on Windows. Do not specifyeither Network Appliance or N-Series Qtrees or a pathwithin the Network Appliance or N-Series volume.Only full volumes are supported.


User response: Retry the incremental backupoperation using the -SNAPDIFF option. Specify a validNetwork Appliance or N-Series NFS volume on AIX orLinux, or a CIFS volume on Windows.

FMV1671I The cluster database has been restored.Restarting the cluster services on allnodes. This will take a few minutes.

Explanation: After the cluster database is restored, thecluster service on the restoring node is in a pausedstate. The cluster service on other nodes wereshutdown. All services need to be restarted. If some ofthe services cannot be started automatically, restartthem manually.


User response: No action.

FMV1672I Could not take the cluster resourceresource name offline. MS rc retcode. Erroris ignored.

Explanation: Microsoft recommends taking the clusterresources offline during an authoritative clusterdatabase restore. However, the restore can still be doneif the resources cannot be taken offline. The error isignored.



FMV1673W Cluster service on node node name couldnot be started. You must manually startthe service.

Explanation: The cluster database has been restored.During the restore, the cluster service was taken offline.Tivoli Storage Manager failed to restart the clusterservice.


User response: You can manually start the service forthis node.

FMV1674I The cluster database has been restoredbut the cluster service on some nodescould not be started. Use the FailoverCluster Management tool to manuallystart the nodes.

Explanation: The cluster database has been restored.During the restore, the cluster services were takenoffline except for the node being restored. TivoliStorage Manager failed to automatically start thesecluster services. You need to start them manually. Thenodes whose services failed to start are logged in theclient error log.


User response: You can manually start the clusterservices.



FMV1675W Unable to obtain a list of cluster nodesto restart after the cluster database isrestored. The call 'cmd' returned withMS rc retcode. You must restart thecluster service on all the nodes after therestore is finished.

Explanation: Due to an error, Tivoli Storage Managercould not retrieve a list of nodes in the cluster torestart. The cluster services on these nodes need to bestarted manually. The client error log might containadditional information depending on where the failureoccured.


User response: Manually start the cluster services onall nodes.

FMV1676W You are doing an authoritative clusterdatabase restore. The process may seemto be hang before and after the file isrestored. This is because it may need tostart the cluster service if it is not upand take all the resources offline. Afterthe cluster database is restored, thecluster service will be restarted forchanges to be in effect. The clusterservice on all other nodes also havebeen shutdown. They will be restarted.This may take a few minutes.

Explanation: The restore will seem to be paused attime because before the restore, Tivoli Storage Managerensures the cluster service is up on the restoring nodeand all the resources are taken offline. After the clusterdatabase is restored, the cluster service on the restoringnode is in a paused state. The cluster service on othernodes were shutdown. All services need to be retarted.If some of the services cannot be started automatically,you can try to restart them.



FMV1677W Tivoli Storage Manager failed to set thedisks for quick formatting because of anerror. See the error log for more details.The disks will be slow formatted whichwill cause a slower restore process.

Explanation: By default, Tivoli Storage Manager triesto set the QuickFormat value of theHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ASR\RestoreSession keyto perform quick formatted on all the disks. Due to anerror, a slow format will be performed on there-creation of the disks. This process will cause aslower restore process.

System action: None

User response: None

FMV1678E ASR path 'path': not found.

Explanation: You have specified a directory that doesnot exist.


User response: Recheck all spelling and punctuation,particularly the placement of directory delimiters (forexample, "\"). Correct the syntax if it is incorrect, thenretry the operation.

FMV1679W Updating the registry to identify whichvolumes have been restored has failed.This does not affect the volumes thathave already been restored. See theerror log for more details. The error isbeing ignored and processing continues.

Explanation: After restoring the critical volumes,Tivoli Storage Manager tries to update theRestoredVolumes value of theHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ASR\RestoreSession keyto indicate which volumes have been restored. Due toan error accessing the registry, the error is logged butprocessing continues.


User response: None

FMV1680W Function refresh incremental FlashCopycannot be accomplish because noconsistency group found for thesevolumes.

Explanation: A refresh of the incremental FlashCopycan only be done when the consistency group and thecorrespondent FlashCopy relation were establishedpreviously.



FMV1681E DSM_DIR was not set and theASRFILESPATH option was notspecified.

Explanation: The ASR files can be in put in theDSM_DIR path by default or overriden with theASRFILESPATH option. Either one is being set.


User response: Set the DSM_DIR environmentvariable or specify the ASRFILESPATH option on the"RESTORE MACHINEASR" command.



FMV1682W No FlashCopy relationships found inthe storage system.

Explanation: The copy services server (mostly a CIMObject Manager) does not have any FlashCopy relationobjects.

System action: Process may stop.

User response: This is not necessarily a message thatimplies the stop of the process.

FMV1683E The state status of the consistency groupis bad to achive a valid disk backup.

Explanation: Tivoli Storage Manager ACS functionmonitoring will expect that the FlashCopy are in one ofthe state Idle_Copied or Copying.


User response: Verify using the storage GUI the stateof the FlashCopy. If this state was generated by an useraction, try to start the copy process through the storageGUI, then re-start the Tivoli Storage Manager ACSmoniotoring fuction.

FMV1684W Disk Full Error Accessing SubfileCache: exception-name

Explanation: A disk full error occurred attempting toaccess or write to the specified subfile cache file duringa subfile incremental backup. See the client error logfor more detailed information.

System action: Processing continues without subfile.


FMV1685E Incremental backup operation usingsnapshot difference is only available forN series/NetApp filer volumes, is not aNetApp volume.

Explanation: Cannot perform NAS NFS/CIFSincremental backup operation using snapshot differenceon the mounted or mapped volume because thevolume is not a N series/NetApp filer volume.


User response: Retry the incremental backupoperation by specifying an entire NAS NFS or CIFSvolume.

FMV1686I Single Instance Store link 'file-name' willbe restored or retrieved as a normal file.

Explanation: Tivoli Storage Manager restores SingleInstance Store (SIS) links as normal files. If the restoredversion is a duplicate of of the copy in the SISCommon Store, then the SIS Groveler will eventuallyrecreate the SIS link.

System action: Tivoli Storage Manager creates normal

files instead of the reparse point.

User response: None

FMV1687E VSS Instant Restore operation failed.Please examine the Tivoli StorageManager client error log file(DSMERROR.LOG), the WindowsApplication Event Log, the WindowsSystem Event Log, and the VSSprovider log file (if applicable) for moredetails. Consult the VSS providerdocumentation for the meaning of theerror return code.

Explanation: VSS hardware provider failed whileperforming volume-level copy restore operation.


User response: Attempt to determine the source of theerror by examining the Application Client log file, theTivoli Storage Manager client error log file(DSMERROR.LOG), the Windows Application EventLog, the Windows System Event Log, and the VSSprovider log file, if applicable. Additional instructionsfor Windows VSS operations are located in the TSMProblem Determination Guide. Correct the problem andretry the operation. If this error persists, contact yourservice representative.

FMV1688I Sparse attributes for 'file-name' cannot bebacked up correctly because the volumefrom which the file is backed up doesnot support sparse files.

Explanation: If the volume from which a file is backedup does not support sparse files, then the allocatedranges for the sparse file cannot be backed up. This istrue even if a file has its sparse attribute set. Oneexample where this can occur is if a sparse file iscreated on a NAS volume, but the volume is backed upover CIFS, where CIFS does not support sparse files.

System action: The sparse attribute and allocatedranges for the file are not backed up. If the file isrestored, the restored file will not be sparse.

User response: No action is required if you do notneed the sparse attribute and allocated ranges backedup. If you require backup of the file's sparse attributeand allocated ranges, then the volume from which IBMTivoli Storage Manager backs up the file must supportsparse files.

FMV1689E The registry was not updated after VSSASR restore.

Explanation: An error occurred while updating theregistry after VSS Automated System Recovery (ASR).Check dsmerror.log for more information.





FMV1690E The list of volumes passed contain pairswhich belong to different consistencygroups in the scope of one singlecluster.

Explanation: Tivoli Storage Manager ACS handles foreach operation only one consistency group per clusterat the same time. If the set of volumes in a backup orrestore operation contain pairs that belong to differentconsistency group inside one single cluster, then theprocess of the operation will be stopped.

System action: Process stopped.

User response: If you added volumes to theproduction database or to the target set, ensure thatthey are not in any FlashCopy relation.

FMV1691I The option 'option' that was found in theoptions file 'file-name' at the linenumber: number is not supported andwill be ignored by the client.

Explanation: The specified option is valid but notsupported on the current platform and will be ignoredby the client.


User response: You can ignore the message or removethe option from the option file.

FMV1692E The certificate is not trusted.

Explanation: The client was unable to open SSLconnection to the server because the server certificatewas not trusted.


User response: Make sure that you have configuredthe key database for SSL communication as describedin the documentation. If the Tivoli Storage Managerserver is using a self-signed certificate, make sure thatyou import the correct certificate from the server youare trying to connect to. When the server is using acertificate signed by an authority, make sure that theroot certificate of the authority is imported into theclient key database.

FMV1693E The certificate validity period isincorrect.

Explanation: The client was unable to open an SSLconnection to the server because the certificate validityperiod is incorrect.


User response: Report this to the Tivoli StorageManager server administrator. The server must have

the correct certificate installed.

FMV1694E The certificate identity could not beverified.

Explanation: Tivoli Storage Manager was unable toopen an SSL connection to the server because thecertificate identity could not be verified. This happenswhen the certificate ownership information does notmatch the Tivoli Storage Manager domain name or IPaddress.


User response: Make sure that the server domainname or the IP address (the value of theTCPSERVERADDRESS option) is correct. If the problempersists, report it to your Tivoli Storage Manager serveradministrator.

FMV1695E The certificate is not valid.

Explanation: Tivoli Storage Manager was unable toopen an SSL connection to the server because of aninvalid certificate. The client was unable to determinethe exact cause of the failure.


User response: Further analysis of the servercertificate, the client key database, or both, is needed.Refer to Tivoli Storage Manager documentation formore information.

FMV1696E Only root can perform this action.

Explanation: User must be root to perform this action.


User response: Log in as root and try the operationagain.

FMV1700W Database 'database' (save date=date) wassuccessfully recovered.

Explanation: The specified database (which was savedon the specified date) was successfuly recovered.

System action: The specified database was recoveredwith the last saved version.

User response: none.

FMV1704W Option 'option-name' can not be suppliedby application and is ignored.

Explanation: An API application supplied option. Theoption cannot be specified by an application. Theoption can be specified only in the dsm.sys options file.

System action: The supplied option is ignored.Processing continues.

User response: Correct the application configuration.



FMV1705E System Writers writersname do not exist.

Explanation: These writers are an essential part of theoperating system. When they are not available thebackup will complete successfully but the data forthose writers will not get backed up to the IBM TivoliStorage Manager server. This can result in the computernot booting after a restore of the system state.

System action: System state backup stopped.

User response: Verify that these writers exist using'vssadmin list writers' command. Try the operationagain. If the problem persists, contact your systemadministrator or IBM Tivoli Storage Manageradministrator for further help.

FMV1706E Error creating directory ' directory'.

Explanation: The system was unable to create thespecified directory.


User response: Verify that the system has theappropriate permissions to create this directory, andthen restart the operation.

FMV1707E Hard link 'new-file-name' could not becreated for existing file 'exist-file-name'.Microsoft Windows return code:'windows-return-code' 'windows-error-text'

Explanation: Some system state files are hard linksthat point to another file. During system state restore,IBM Tivoli Storage Manager recreates the hard links forrestored system state files. If a file with the same nameas the hard link already exists at the time of the restore,IBM Tivoli Storage Manager attempts to replace the filewith the hard link. This message is issued when IBMTivoli Storage Manager is unable to replace an existingfile with a hard link. The message includes the hardlink name, the system state file name to which the hardlink points and the Microsoft Windows return codeinformation. The return code information indicates whythe file could not be replaced. It is possible for theoperating system or applications to behave erratically ifthe hard link cannot be recreated.

System action: The hard link is skipped, system staterestore continues.

User response: Use the Microsoft Windows returncode information provided in the message to determinethe underlying cause of the error. Based on theunderlying cause of the error and the reason you arerestoring the system state, you can choose to eithercorrect the underlying cause and perform the restoreagain, or you can attempt to manually create the hardlink. Because this error message represents an unusualand unexpected condition, you should give carefulconsideration to the potential consequences of eitherchoice. The hard link can be created manually asfollows: Rename the file that has the same name as the

hard link. Then use the Microsoft Windows utilityfsutil.exe as follows: FSUTIL HARDLINK CREATEhardlinkname originalfilename

FMV1708E Backup operation failed. Only a rootuser can do this operation.

Explanation: Backups initiated by non-root users aredisabled by IBM Tivoli Storage Manager administrator.


User response: Request the IBM Tivoli StorageManager administrator to enable non-root backups.

FMV1712I Changed block tracking not supportedfor disk disk name; Performing FULLbackup of disk.

Explanation: Changed block tracking is not enabled orsupported for the specified disk, so a full backup of thedisk will be performed.

System action: A full backup of the disk is performed.

User response: None

FMV1713W There was a problem getting changedblock tracking information for disk diskname; Performing FULL backup of disk.

Explanation: Changed block tracking is supported forthe specified disk, but there was a problem getting thechanged block tracking information, so a full backup ofthe disk will be performed.

System action: A full backup of the disk is performed.

User response: Review the error log for messages asto why the changed block tracking information couldnot be obtained.

FMV1714I No changed extents found for disk diskname - skipping disk.

Explanation: No changed extents were found for thespecified disk, so there is nothing to backup; The diskwill be skipped.

System action: No data is backed up for the specifieddisk so no data has changed.


FMV1715E A filespace already exists for virtualmachine (VM_name), but with a differentvirtual machine UUID (VM_UUID) thanthe current virtual machine UUID(VM_UUID).

Explanation: A virtual machine with this name wasbacked up, and it has a different virtual machine UUIDthan the virtual machine that is backed up now. Thiscan occur if there are two virtual machines with the



same name that are backed up to the same TivoliStorage Manager data center node name. In this case,the backup can not continue because thebackup-archive client uses the virtual machine name touniquely reference the virtual machine on the TivoliStorage Manager server.

This can also occur if the virtual machine UUIDchanged after a previous backup operation. This is thecase after the following events:

1. Virtual machine VM_1 backed up.

2. Virtual machine VM_1 is restored with a new name:VM_2. A new UUID is assigned to VM_2.

3. Virtual machine VM_1 is deleted.

4. Virtual machine VM_2 is renamed to VM_1.

System action: The backup of this virtual machinefails. The backup process can continue with othervirtual machines.

User response: If there are two or more virtualmachines with the same name in the data centerinventory, you can complete either of the followingactions:

v Rename the virtual machines so that all names in thedata center inventory are unique.

v Backup up virtual machines with the same name todifferent Tivoli Storage Manager servers.

If the VM's UUID changed, run a BACKUP VMcommand with VMBACKUPUPDATEGUID option. TheVMBACKUPUPDATEGUID option updates the UUIDon the Tivoli Storage Manager server.

FMV1716E A VMware vStorage web service tasktimed-out.

Explanation: The TSM client timed-out waiting forVMware vCenter or ESX host to complete a requestedweb service task. Resources could be low or the systemcould be busy.


User response: Please check the VMware vCenter orESX host for errors.

FMV1717E A VMware vStorage web service taskfailed.

Explanation: A VMware vCenter or ESX host webservice task failed.


User response: Please check the VMware vCenter orESX host for errors.

FMV1729E The passed file list 'file-list' is not a validinput file list. Pass standard file list orcollection file list to the dsmrecallcommand.

Explanation: User has passed a invalid file list type tothe dsmrecall command


User response: pass standard file list or collection filelist to dsmrecall command.

FMV1730E The IBM Tivoli Storage Manager serverquery for ordering information failed.

Explanation: Tape optimized recall was not able toretrieve ordering information from the IBM TivoliStorage Manager server.


User response: Check the connection to the IBM TivoliStorage Manager server to see if the IBM Tivoli StorageManager server is available and you have the correctaccess rights configured.

FMV1731E Tape optimized recall for file list 'file-list'failed with rc = code.

Explanation: Tape optimized recall was not able toretrieve ordering information from the IBM TivoliStorage Manager server.


User response: Check all error messages above thismessage to get details about the problem.

FMV1732W File 'file' is from a different file system.writing file to list of unprocessed files:'file-list'.

Explanation: The dsmrecall command specifies a filesystem to process. Files from other file systems areskipped and written into a unprocessed list.

System action: File is skipped and information iswritten to a list of unprocessed files

User response: Check that all files in the input file listare from the correct file system.

FMV1733I A collection file was specified 'file-list'The ordering process is skipped.

Explanation: A collection file was passed as the inputfile list. Ordering is not necessary since it the file isalready ordered. Only the recall is started.

System action: The ordering processed is not started,only recall started.

User response: No further action needed.



FMV1734W The virtual machine 'VM-name' containsone or more independent disks.Backups are not supported in thisconfiguration. Specify the'-vmprocessvmwithindependent=yes'option to exclude these disks from thebackup.

Explanation: Independent disks are not affected bysnapshots so the IBM Tivoli Storage Manager clientdoes not support backing them up.

System action: The virtual machine is not backed up.

User response: Turn off the virtual machine andchange the disk independent mode or remove themfrom the virtual machine. Or specify the'-vmprocessvmwithindependent=yes' option to excludethese disks from the backup.

FMV1735W The virtual machine 'VM-name' containsone or more physical Raw DeviceMappings (RDMs). Backups are notsupported in this configuration. Specifythe '-vmprocessvmwithprdm=yes' optionto exclude these disks from the backup.

Explanation: Physical RDMs are not included insnapshots so the TSM client does not support backingthem up.


User response: Turn off the virtual machine andchange the RDMs to virtual mode or remove themfrom the virtual machine. Or specify the'-vmprocessvmwithprdm=yes' option to exclude thesedisks from the backup.

FMV1737E The PRESNAPSHOTCMD commandfailed.

Explanation: The command specified by thePRESNAPSHOTCMD option must completesuccessfully in order to perform the VSS snapshotbackup. If the command completed with a return codeof 0 (zero), it is considered to have completedsuccessfully. If the command completed with any otherreturn code, it is considered to have failed. If thecommand failed then the VSS snapshot backup is notperformed.

System action: The client does not perform the VSSsnapshot backup operation.

User response: Identify and repair the problem thatcaused the command to fail. If a non-zero return codeis normal for this command, consider wrapping thecommand in a script that always exits with a returncode of zero.

FMV1738W The POSTSNAPSHOTCMD commandfailed.

Explanation: If the command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code, the VSS snapshot backupoperation continues. The operation continues with awarning-level result. The result of thePOSTSNAPSHOTCMD command does not supersede ahigher result from the VSS snapshot backup command.For example, if the VSS snapshot backup commandcompleted with code 12, a lower return code from thePOSTSNAPSHOTCMD command does not alter thereturn code.

System action: The VSS snapshot backup continues,but with a warning return code of at least 8.

User response: Identify and repair the problem thatcaused the command to fail. Consider wrapping thecommand in a script that always exits with a returncode of zero.

FMV1739E Restore of a system drive is notpermitted.

Explanation: The drive to which you are restoringcontains the operating system.


User response: Try the operation again withoutspecifying a system drive.

FMV1740W Unable to read ACLs for object:file_system path name. Check dsmerror.logfor more information.

Explanation: The ACLs of the object are not read.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Try to follow the suggested correctiveactions (if any) and try the operation again.

FMV1741W Unable to read extended attributes forfile_system path name. Check dsmerror.logfor more information.

Explanation: The extended attributes of the object arenot read.


User response: Examine the client error log foradditional messages that might indicate the reason forthe problem. Follow the suggested corrective actions (ifany) and try the operation again.



FMV1742E Expose Snapshot failed for backup'backup-name'.

Explanation: Expose snapshot failed.


User response: See the dsmerror.log file for furtherdetails.

FMV1743E Unexpose snapshot failed for backup'backup-name'.

Explanation: Unexpose snapshot failed.



FMV1744E One or more of the snapshots(volumes)needed for the restore operation werenot found. See dsmerror.log for furtherdetails.

Explanation: One or more of the snapshots needed forrestore were not found on the system.



FMV1745I The virtual machine to restore has oneor more distributed port groups. Furtherconfiguration might be necessary toselect a port number after the restore iscomplete.

Explanation: The virtual machine was saved with oneor more NIC cards backed by distributed port groups.Due to conflicts on restore the port number(s) were notsaved.

System action: The restore continues.

User response: Edit the virtual machine settings andselect a port if needed.

FMV1746E No available LUNs were found.Confirm that the storage adapters areconfigured correctly on the host and thatthe LUNs are not mapped to anothervirtual machine.

Explanation: The virtual machine was stored with aRaw Device Mappings disk backed by a LUN. Therequired LUN is missing or still mapped to anothervirtual machine.

System action: The virtual machine cannot berestored.

User response: Confirm that the Storage Adapters areconfigured correctly on the host and that the LUNs are

not mapped to another virtual machine.

FMV1747E Encryption key password is notavailable.

Explanation: The client is not enabled for encryptedbackup/restore operations by non-authorized users orthe encryption key password is not stored by theadministrator.

System action: Objects that cannot be encrypted ordecrypted are skipped.

User response: Contact the administrator for yoursystem to configure encrypted operations fornon-authorized users.

FMV1748E The virtual machine was stored with aRaw Device Mappings disk backed by aLUN. The required LUN is missing orstill mapped to another virtual machine:LUN UUID lun.

Explanation: The virtual machine was stored with aRaw Device Mappings disk backed by a LUN. Therequired LUN is missing or still mapped to anothervirtual machine.


User response: Find the required LUN and make itavailable to the virtual machine.

FMV1749W Object 'filespace-namehl-namell-name' wasbacked up with invalid file system typeattribute.

Explanation: File system type is used by the client todetermine if an object name is case sensitive or not.Wrong file system type may result in incorrect sortorder of the server tree for case sensitive file systems.Finally some unchanged files may expire and thenre-backed up during full incremental backup.


User response: It is recommended to rename thecorrespondent filespace on TSM server and do the fullincremental backup again.

FMV1750I Volume mount point 'volumemountpoint'is mounted to volume 'volume'. Usingsnapshot volume for 'volume' to backup.

Explanation: The volume mount point resolved to avolume that has been snapped. The same snapshotvolume will be used.





FMV1751E Error processing 'filespace name': The filesystem can not be accessed.

Explanation: The client is unable to access the filesystem. Two common reasons for this are the accountunder which the client is running does not have accessto the root of the file system, or the file system doesnot exist.

System action: The inaccessible file system is skipped.Processing continues with the next file system.

User response: Check the error log for additionalmessages that might yield additional information aboutthe problem that prevents access to the file system.Correct the problem, then retry the operation. If theaccount does not have access to the file system, theneither the system administrator needs to grant access,or an account that has access to the file system must beused. If the file system does not exist, then remove orcorrect the file system specification.

FMV1752E The file system can not be accessed.

Explanation: The client is unable to access the filesystem. Two common reasons for this are the accountunder which the client is running does not have accessto the root of the file system, or the file system doesnot exist.

System action: The inaccessible file system is ignored.

User response: Check the error log for additionalmessages that might yield additional information aboutthe problem that prevents access to the file system.Correct the problem, then retry the operation. If theaccount does not have access to the file system, theneither the system administrator needs to grant access,or an account that has access to the file system must beused. If the file system does not exist, then remove orcorrect the file system specification.

FMV1753E File space 'filespace name' was backed upby an older client version, and cannotbe restored with this client version. Thefile space will be skipped.

Explanation: The backup set format in earlier clientversions for SYSTEM STATE and SYSTEM SERVICES isincompatible with the current client version. Those filespaces will be skipped. The restore might appear topause while the client skips past the objects in thosefile spaces. Other remaining file space data will berestored.

System action: Objects in this file space are skipped.Other remaining file space data will be restored.

User response: Restore this specific file space in thebackupset with a prior level client.

FMV1754E File space 'filespace name' cannot berestored when ASNODENAME optionis in affect. The file space will beskipped.

Explanation: System state data of another node shouldnot be restored to a different node. Those file spaceswill be skipped. The restore might appear to pausewhile the client skips past the objects in those filespaces. Other remaining file space data will be restored.

System action: Objects in this file space are skipped.Other remaining file space data will be restored.

User response: Remove ASNODENAME option beforerestoring this specific file space in the backupset or usethe node name that was used to backup system statedata to restore.

FMV1755W An error communicating with ActiveDirectory has occured. USEDIRECTORYoption will be ignored and processingwill continue.

Explanation: Tivoli Storage Manager attempted toquery Active Directory for Tivoli Storage ManagerServer parameters but an error has occured. This couldbe caused by Active Directory or the Tivoli StorageManager Server's setup.

System action: Tivoli Storage Manager will ignore theUSEDIRECTORY option and continue with clientprocessing.

User response: Make sure your computer is properlyset up to the domain with Active Directory. Also, makesure your Tivoli Storage Manager Administrator hasproperly configured the Tivoli Storage Manager Serverfor your node.

FMV1756W The Journal for 'backup-specification' hasbeen reset: The server filespace wasdeleted since the last backup completed.

Explanation: The client has reset the journal becausethe corresponding server filespace was deleted sincethe last backup completed.

System action: The journal is reset, the current backupwon't use the journal, and the journal won't beavailable for backup until a full incremental backupsuccessfully completes.




System action: The journal is reset, the current backup



won't use the journal, and the journal won't beavailable for backup until a full incremental backupsuccessfully completes.






FMV1759W The Journal for 'backup-specification' hasbeen reset: The policy set was updatedsince the last backup completed.

Explanation: The client has reset the journal for thespecified file system because the node policy set wasupdated since the last backup completed.



FMV1760I Journal for 'backup-specification' enabledfor node 'nodename' and server'servername'

Explanation: The journal for the specified file systemis now valid and will be used by the next fullincremental backup by the specified TSM node andserver.

System action: The next full incremental backup ofthe file system will use the journal.


FMV1761I Journal for 'backup-specification' will beenabled upon successful completion ofthe backup.

Explanation: An active but invalid journal is presentfor the file system being backed up. Once the backupsuccessfully completes the journal will available for useby the next full incremental backup of the file systemwith the same TSM node and server.



FMV1763W Unable to unmount snapshot mountpoint snapshot mountpoint during cleanupof snapshot 'snapshot' of volume 'volume'.Error is 'error'. Operation will continue.Please manually unmount, remove thesnapshot mount point directory anddelete the snapshot after backup iscompleted.

Explanation: During the termination phase of TSMclient operation, it was not possible to unmount thesnapshot for some reason. However, TSM operationwas completed successfully.

System action: Processing continues, and the unmounterror is ignored.

User response: Please manually cleanup the snapshotsas follows: Query the snapshot: snapshot -q -c: <sourceFS>. Snapshot name will be of the format:tsmxxxxxxxxxx. Check if it is mounted: df -k | greptsmxxxxxxxxxx. Unmount the snapshot: umount -ftsmxxxxxxxxxx. Remove snapshot mount point: rmdirtsmxxxxxxxxxx. Delete the snapshot: snapshot -d/dev/tsmxxxxxxxxxx. If snapshot delete fails with"Device Busy" or some other error, unmount thesnapshot source filesystem: umount -f <source FS>.Retry snapshot delete: snapshot -d/dev/tsmxxxxxxxxxx. Check if any logical volumes areremaining: ls -l /dev/tsm*. Remove any remaininglogical volumes: rmlv -f tsmxxxxxxxxxx. Remountsource file system, if previously unmounted: mount<source FS>.

FMV1764W Unable to remove the snapshot mountpoint directory snapshot mountpointduring cleanup of snapshot 'snapshot' ofvolume 'volume'. Error is 'error'.Operation will continue. Pleasemanually remove the snapshot mountdirectory and delete the snapshot afterbackup is completed.

Explanation: During the termination phase of TSMclient operation, it was not possible to remove themount point directory for the snapshot for somereason. However, TSM operation was completedsuccessfully.

System action: Processing continues, and the rmdirerror is ignored.

User response: Please manually cleanup the snapshotsas follows: Query the snapshot: snapshot -q -c: <sourceFS>. Snapshot name will be of the format:tsmxxxxxxxxxx. Check if it is mounted: df -k | greptsmxxxxxxxxxx. Unmount the snapshot: umount -ftsmxxxxxxxxxx. Remove snapshot mount point: rmdirtsmxxxxxxxxxx. Delete the snapshot: snapshot -d/dev/tsmxxxxxxxxxx. If snapshot delete fails with"Device Busy" or some other error, unmount thesnapshot source filesystem: umount -f <source FS>.Retry snapshot delete: snapshot -d



/dev/tsmxxxxxxxxxx. Check if any logical volumes areremaining: ls -l /dev/tsm*. Remove any remaininglogical volumes: rmlv -f tsmxxxxxxxxxx. Remountsource file system, if previously unmounted: mount<source FS>.

FMV1765W Unable to delete the snapshot duringcleanup of snapshot 'snapshot' of volume'volume'. Error is 'error'. Operation willcontinue. Please manually delete thesnapshot after backup is completed.

Explanation: During TSM client operation, it was notpossible to delete the snapshot for some reason.However, TSM operation was completed successfully.One of the reasons that the snapshot delete failedmaybe due to the fact that AIX JFS2 expects thesnapshot delete requests for a given filesystem to beissued in the order of oldest snapshot first, next oldestsnapshot second and so on. If there are other processesusing older snapshots for the same filesystem, it failsthe delete request. Also, TSM only deletes snapshotsthat was created by one of its processes. It will notdelete older snapshots created by other applications orusers. In this case, the user will have to manuallydelete all the older snapshots so that the next TSMcommand can complete successfully.

System action: Processing continues, and the snapshotdelete error is ignored.


FMV1766W Unable to remove the snapshot logicalvolume during cleanup of snapshot'snapshot' of volume 'volume'. Error is'error'. Operation will continue. Pleasemanually remove the snapshot logicalvolume after backup is completed.

Explanation: During the termination phase of TSMclient operation, it was not possible to remove thesnapshot logical volume for some reason. However,TSM operation was completed successfully.

System action: Processing continues, and the snapshotlogical volume remove error is ignored.


FMV1767E Unable to create a snapshot logicalvolume using command: 'cmd'. Error is'error'. Please ensure that the volumegroup has sufficient free partitions tofulfill the allocation request.

Explanation: During the initialization phase of TSMclient operation, it was not possible to create a logicalvolume for the snapshot.

System action: Processing continues, and the createsnapshot logical volume error is ignored. TSMoperation will be performed without the snapshot.

User response: Please ensure that the volume grouphas sufficient free partitions to fulfill the mklvallocation reuest and retry the operation.

FMV1768E TSM was unable to find space for a newsnapshot. Tivoli Storage Managerfunction name : function-name TivoliStorage Manager function : function-descTivoli Storage Manager return code :TSM-rc Tivoli Storage Manager file :file-name (line-number)

Explanation: None.


User response: Previous backups may still bepending. If problem persists contact the Tivoli StorageManager administrator with the information providedin this message.

FMV1769E NetApp file server 'server-name' at DataONTAP version'version.modification.submodification' is notsupported for performing incrementalbackups using snapshot difference.

Explanation: Incremental backup using Snapshotdifference requires Data ONTAP V7.3 or later. However,if you are upgrading from Data ONTAP V7.3.3 or laterto V8.0, you will lose snapshot difference support for



unicode file names. Upgrade to Data ONTAP V8.1 orlater.


User response: Upgrade the file server to a supportedlevel of Data ONTAP, then retry the operation.

FMV1770E Unable to resolve address 'tcpip address'.Error = error code, 'error message'

Explanation: The system was not able to get theTCP/IP v6 address.


User response: Verify the address shown is a TCP/IPv6 address and can be resolved with ping or ping6.

FMV1771W The system state filespace 'filespace name'cannot be restored to a differentlocation.

Explanation: The system state file space cannot berestored to a different location. This file space isskipped.

System action: Objects in the system state file spaceare skipped. Other remaining file spaces are restored.The restore might appear to pause while the clientskips past the objects in this file space.

User response: Restore system state to its originallocation.

FMV1772E Error loading the snapshot plugin. Theplugin might not be installed.

Explanation: The snapshot plugin could not beloaded, possibly because the plugin is not installed.

System action: The snapshot backup is stopped.

User response: On Linux 86/86_64 platform, installthe TIVsm-BAhdw package if it is not already installed.Try the operation again. On AIX platform, install thehdw and snphdw filesets if they are not alreadyinstalled. Try the operation again.

FMV1773W The virtual machine 'VM-name' containsone or more independent disks andthese disks are excluded from the VMbackup.

Explanation: You cannot perform a shapshot ofindependent disks. Specify the option'-vmprocessvmwithindependent=yes' to skip thesedisks.

System action: The virtual machine independent diskswill not be backed up.


FMV1774W The virtual machine 'VM-name' containsone or more physical Raw DeviceMappings (RDM) disks and these disksare excluded from the VM backup.

Explanation: You cannot perform a shapshot ofphysical RDM disks. Specify the option'-vmprocessvmwithprdm=yes' to skip these disks.

System action: The virtual machine physical RDMdisks are not backed up.


FMV1780E writer-name failed to initialize andsubscribe to VSS.

Explanation: IBM Tivoli Storage Manager encounteredan error while creating writer-name under control of theWindows Volume Shadow Copy Service (VSS).Examine the IBM Tivoli Storage Manager error log andApplications Event Log for additional informationabout this error.


User response: Try the operation again. If the errorpersists, examine the IBM Tivoli Storage Manager errorlog and Windows event log for information related tothis error.

Restart the Windows Volume Shadow Copy Service(VSS), and try the operation again.

In some cases, it is necessary to restart the machine toclear the VSS error state.

FMV1782E writer-name failed to be stopped.

Explanation: IBM Tivoli Storage Manager encounteredan error while stopping writer-name. Examine the IBMTivoli Storage Manager error log and ApplicationsEvent Log for additional information about this error.


User response: Try the operation again. If the errorpersists, examine the IBM Tivoli Storage Manager errorlog and Windows event log for information related tothis error.

Restart the Windows Volume Shadow Copy Service(VSS), then try the operation again.

In some cases, it is necessary to retart the machine toclear the VSS error state.

FMV1784E Incremental by snapshot differencecannot be performed on 'volume-name' asit is a vFiler volume.

Explanation: Snapshot difference incremental backupis not supported on vFiler volumes.




User response: Perform snapshot differenceincremental backup on normal NetApp/N-Seriesvolumes only.

FMV1787I The virtual machine NIC is backed by adistributed virtual port group but it ismissing the portgroupKey attribute, TheNIC cannot be restored.

Explanation: The virtual machine NIC is missing therequired portgroupKey attribute.

System action: The virtual machine can be restoredbut the NIC cannot be restored.

User response: After the virtual machine has beenrestored a new NIC card can be added.

FMV1788I The target ESX host is missing therequired distributed virtual port group,the virtual machine NIC cannot berestored. UseVMDEFAULTDVPORTGROUP optionto set to specify new port group. Iftarget ESXi server does not have anyport groups, useVMDEFAULTNETWORK option.

Explanation: The virtual machine NIC was backed bya distributed virtual port group but the target ESX hostis missing this port group.



FMV1789I No Ddistributed virtual port group werefound on the target ESX host. Thevirtual machine NIC cannot be restored.

Explanation: The virtual machine NIC was backed bya distributed virtual port group but the target ESX hosthas no port group available.



FMV1790E Volume 'volname' cannot be backed upbecause 'nosnapdir=on' is set on thefiler.

Explanation: This message is issued when option'nosnapdir=on' is in set for the volume indicated in themessage. When this option is set, the volume snapshotsare hidden and thus cannot be backed up.

System action: The volume indicated in the messageis not backed up. Processing continues with the nextvolume.

User response: To back up the volume, change thevolume on the filer: Set option 'nosnapdir=off'. Then trythe backup operation for this volume again. If thevolume is not backed up, remove it from thebackup-archive client DOMAIN setting.

FMV1794I The option 'cifs.enable_share_browsing= off' is set on the filer 'filerName'.

Explanation: This message is issued when the option'cifs.enable_share_browsing = off' is set on the NASfiler indicated in the message.


User response: Set option 'cifs.enable_share_browsing= on'. Then try the snapshot difference backupoperation again.

FMV1795I Operation will continue without usingsnapshot provider, because file system'volname' does not have writepermissions.

Explanation: The source file system for a snapshotshould be read-write as by definition a snapshot is apoint-in-time snapshot of changing file system.Snapshot creation updates the file system superblockwhich requires the file system to be read-write

System action: Processing continues without usingsnapshot provider.

User response: If the volume needs to be backed upvia snapshot provider, change its permissions toread-write.

FMV1796I The short name for 'fullpath-name' couldnot be set to original short name'file-name': Windows function 'func-name'failed with return code return-code,reason: 'error text'

Explanation: The client cannot set the short name forthe specified object. This is usually because the shortname is already in use by another object located in thesame directory. Another possible reason is that theaccount under which the client is running does nothave the SE_RESTORE_NAME privilege.

System action: The short name for the specified objectis not set. The object will retain the default short name.Otherwise processing continues.

User response: This message is informational and canbe safely ignored. If you require that the object berestored with its original short name, you will need tomove or delete the conflicting object. From anoperating system command prompt, change to thedirectory that contains the object you want to restore.Then use the \"dir /x\" command to identify theconflicting object. Also make sure that you have theSE_RESTORE_NAME privilege. If you need assistance,see your system administrator. After the conflict has



been resolved, try to restore the file again.

FMV1797E Function function-name received anunexpected error from the Microsoft APIMS-function-name: rc=error whileattempting to access the object'object-name'. Error occurred in filefile-name (line-number).

Explanation: An error occurred while processing the'object-name'. The error code indicates the reason for thefailure. This information can be used to diagnose theproblem.

System action: The Tivoli Storage Manager client mayor may not fail the operation, depending on the errorcode.


FMV1798W An error occurred while accessingencrypted data of the object 'object-name',skipping object. Windows system errorcode error, reason 'error-reason'

Explanation: An error occurred while processingencrypted data of the object. The error informationcaptured indicates the reason for the failure. Thisinformation can be used to diagnose the problem.



FMV1799I The last access date for 'fullpath-name'could not be reset because the file isread-only.

Explanation: Option PRESERVELASTACCESSDATEYES is in effect, but the Tivoli Storage Manager clientwas unable to reset the last access date for the specifiedfile because the file's "read only" attribute is enabled.The client cannot reset the last access date for "readonly" files.

System action: The last access date for the specifiedfile is not reset. Otherwise processing continues.

User response: This message is informational and canbe safely ignored. You might want to turn off the "readonly" attribute for the file so that subsequent backupscan reset the last access date. Before turning off theattribute, you should verify that doing so will notimpact the integrity of the file or the applications thatuse the file. You should also make sure that turning offthe attribute will not conflict with the file managementpolicies of your organization.

FMV1800W The last access date for 'fullpath-name'could not be reset: function 'func-name'failed with return code return-code

Explanation: Option PRESERVELASTACCESSDATEYES is in effect, but the Tivoli Storage Manager clientwas unable to reset the last access date for the specifiedfile. The message includes the name of the function thatfailed and the return code from that function.

System action: The last access date for the specifiedfile is not reset. Otherwise processing continues.

User response: If the problem is reproducible, obtain aSERVICE trace that captures an instance of thisproblem. Run the QUERY SYSTEMINFO command andcollect the dsminfo.txt file. Contact IBM support andreport the exact text of this error message. Be sure toprovide support with the dsminfo.txt and dsmerror.logfiles and (if available) the SERVICE trace.

FMV1801E Unable to register the new ID withserver.

Explanation: The reasons of this problem can be lackof client system memory or server protocol error. TheTivoli Storage Manager activity log might contain acorresponding error message with further informationabout the cause.

System action: The new ID is not registered with theserver.

User response: Please check your network connectionand try again after time. If the error appears again,please contact your client machine administrator.

FMV1802E Incremental backup of 'file-name'finished with failCount failure(s)

Explanation: This message is issued after completionof an incremental backup operation for the named filespecification when one or more objects in that filespecification could not be backed up.


User response: Examine the client error log foradditional messages that indicate the reasons that eachfailed object could not be backed up. Take anycorrective action as suggested by the messages.

FMV1803E Archive processing of 'file-space name'finished with failures.

Explanation: This message is issued after completionof an archive operation for the named file specificationwhen one or more objects in that file specificationcould not be archived.


User response: Examine the client error log foradditional messages that indicate the reasons that each



failed object could not be archived. Take correctiveaction as suggested by the messages.

FMV1804E Selective Backup processing of 'file-spacename' finished with failures.

Explanation: This message is issued after completionof a selective backup operation for the named filespecification when one or more objects in that filespecification could not be backed up.


User response: Examine the client error log foradditional messages that indicate the reasons that eachfailed object could not be backed up. Take anycorrective action suggested by those messages.

FMV1805E Unable to restore symbolic link'file-name'.

Explanation: The client operating system is not able tocreate a symbolic link because the link points to afilename that is not given.


User response: Try the restore on a different operatingsystem.

FMV1806W Size exceeded the maximum file sizelimit on your system for 'filespacenamepath-namefile-name' of 'file-size'.

Explanation: You tried to restore or retrieve a file thathas exceeded the maximum file size limitation on yoursystem.

System action: Tivoli Storage Manager cannot restoreor retrieve the file.

User response: Restore or retrieve this file on a systemthat supports the file size. See your systemadministrator.

FMV1807E Unable to recall file from server due toerror from recall daemon.

Explanation: Unable to recall file. The recall daemonreported an error while trying to recall a file. Look inthe recall daemon’s error log for more information. Thiscan happen if the server is down, the connection isbroken, or the file is missing on the server. It is alsopossible that the migration server in the system optionfile has been changed to a different server. The recalldaemon does not check the system option file forchanges once it has started.


User response: See if the server is up, and retry. If theproblem still exists, look in the error log. Also have theworkstation administrator run dsmreconcile against thefile system and see if the file shows up in the

.SpaceMan/orphan.stubs file. If system option file hasbeen changed, stop all recall daemons and restart themaster recall daemon to pick up the changes.

FMV1808E The Logical Volume Snapshot Agent isnot at the correct level. It is possiblethat the Client was upgraded to a newerlevel but the LVSA driver was notupdated at the same time. Use the SetupWizard to configure either Online Imageor Open File support and choose Updatethe Logical Volume Snapshot Agent.

Explanation: The selected operation requires thecurrent level of the Logical Volume Snapshot Agent.Use the Setup Wizard to update the LVSA.

System action: The selected operation is notperformed.

User response: Retry the operation after updating theLogical Volume Snapshot Agent.

FMV1809W A session with the Tivoli StorageManager server has been disconnected.An attempt will be made to reestablishthe connection.

Explanation: This message is issued after the sessionwith the Tivoli Storage Manager server is unexpectedlylost. Some possible reasons that this message might beissued: - There is a problem with the network. - TheTivoli Storage Manager server was shut down. - TheTivoli Storage Manager server administrator cancelledthe client session.

System action: The client will try to reestablish aconnection with the server. If the Tivoli StorageManager server administrator cancelled the session,then the attempt to reestablish the connection will failand message FMV1369E will be issued. If the attemptto reestablish the connection is successful, thenprocessing will continue. If the attempt to reestablishthe connection fails, then the client will continue to tryto reestablish a connection according to theCOMMRESTARTDURATION andCOMMRESTARTINTERVAL client option settings.

User response: If the session was cancelled by theTivoli Storage Manager server administrator and youdo not know why, or if the client is unable toreestablish a session with the Tivoli Storage Managerserver, then contact your Tivoli Storage Manager serveradministrator for further information. Frequentoccurrences of the FMV1809W message can indicate aproblem with the network. If this message is repeatedlyfound in the dsmerror.log, investigate possiblenetworking trouble, such as a failing network interfacecard or router problem. One common problem is themedia speed of the network adaptors: If the networkadaptors are set to "auto-negotiate", try changing themto "100%% full duplex". If the problem persists, then asa temporary measure ask your Tivoli Storage Manager



server administrator increase the COMMTIMEOUT andIDLETIMEOUT option settings on the Tivoli StorageManager server. This might reduce the frequency ofthis message.

FMV1810I A session with the Tivoli StorageManager server has been reestablished.

Explanation: The session with the server has beenreestablished after a connection failure. This message isusually preceded by message FMV1809W.


User response: None. This message is informationalonly.

FMV1811S Tivoli Storage Manager session couldnot be reestablished.

Explanation: The session with the server has beenlost. Attempts to reestablish the session wereunsuccessful. Possible causes include, but are notlimited to the following:

v The server has been halted.

v The network connection to the server is down.

v The communication program that Tivoli StorageManager is interacting with has encountered someproblem.

System action: Processing is stopped.

User response: Check network connection to theserver. Insure that the Tivoli Storage Manager server isrunning. Insure that the communication programunderlying Tivoli Storage Manager is working properly.

FMV1813E Image Backup processing of'filespace-name' finished with failures.

Explanation: The image backup operation failed. Thismessage is usually preceded by other messagesindicating the nature of the failure.

System action: The failing file space is skipped andprocessing continues.

User response: Examine the messages preceding thismessage and the Tivoli Storage Manager Client errorlog for more specific indications about the problem. Acommon cause is that a tape could not be mounted onthe Tivoli Storage Manager server, perhaps due to aninsufficient number of mount points. If there is aproblem with the server, contact your SystemAdministrator for further assistance.

FMV1814E Unable to start the scheduled event'event-name'

Explanation: The scheduled event is no longer validon the server. Either the window has elapsed or theschedule has been deleted.

System action: The client scheduler queries the serverto obtain the next scheduled event.

User response: If the problem continues, contact yoursystem administrator to correct the problem on theserver.

FMV1815E Either the window has elapsed or theschedule has been deleted

Explanation: Scheduled event was no longer valid onthe server.

System action: The client scheduler queries the serverto obtain the next scheduled event.

User response: If the problem continues, see yoursystem administrator to correct the problem on theserver.

FMV1816E Invalid scheduling mode

Explanation: The mode entered for the scheduledevent was not correct.

System action: Event does not occur.

User response: Enter the correct scheduling mode andretry the operation.

FMV1817E Schedule function can only be run by aTivoli Storage Manager authorized user.

Explanation: An attempt to use the schedule functionfailed because of improper authority.


User response: See the Tivoli Storage Managerauthorized user for schedule function information.

FMV1818E The SCHEDULE command is notallowed in LOOP (interactive) mode.

Explanation: The SCHEDULE command may only begiven on the inital command line. Enter the HELPSCHED command for a complete description of theSCHEDULE command.

System action: The client does not execute anyscheduled events.

User response: Start the scheduler from the OSprompt. For example: dsmc schedule Windows clientscan also use the client scheduler service. Read the clientmanual for information on how to use the SCHEDULEcommand and how to use the Tivoli Storage Managerclient scheduler features.

FMV1819E The Tivoli Storage Manager server wasunable to register the address for thisnode.

Explanation: This is a rare situation, and is usually an



indication of a problem with the Tivoli StorageManager server.


User response: Check the error log for any othermessages that might indicate a reason for the failure.Ask your Tivoli Storage Manager server administratorto check the Tivoli Storage Manager server activity logfor any messages that might indicate a problem on theserver. Try to correct any indicated problems, then trythe operation again. If the problem persists, contactIBM technical support for further assistance.

FMV1820E Command line options must bepreceded by a '-'

Explanation: An option was specified without a '–'delimiter.


User response: Enter the command again with a dashpreceding each option.

FMV1821E Unable to start POSTSCHEDULECMD/PRESCHEDULECMD 'command'

Explanation: The requested action required a newprocess to be created. Either an option or a schedule“action” that requested an operating system commandto be executed was entered.

System action: Request is ignored.

User response: Remove the request from the optionsfile or the schedule defined on the server.

FMV1822E Too many objects were selected forrestore. Please select less thanmax_objects objects

Explanation: The restore cannot be performed,because too many objects were selected.

System action: The restore is not performed.

User response: Retry the operation after reducing thenumber of objects selected.

FMV1823E The TESTFLAGS or TRACEFLAGSoption specifies unknown flag name'keyword' or the value supplied is invalidfor the named keyword.

Explanation: Either the testflag or traceflag name isincorrectly spelled, or the value supplied for that flag isnot valid.

System action: If the TESTFLAGS or TRACEFLAGSoption was specified in the client options file or on thecommand line during client initialization, the the clientprogram does not start. If the option was specifiedfrom the command line client while running in LOOP(interactive) mode, then the operation does not run.

User response: Correct the TESTFLAGS orTRACEFLAGS flag name or correct the value specifiedfor the TESTFLAG keyword shown in the message.These options are typically used at the direction of IBMtechnical support or as specified in the Tivoli StorageManager Problem Determination Guide. If you are notsure which flag names to use, review the Tivoli StorageManager Problem Determination Guide for additionalinformation or contact IBM technical support forfurther assistance.

FMV1824E Invalid trace file name (name too long).




FMV1827W Directories cannot be selected with thetable of contents currently loaded on theserver.

Explanation: The table of contents that is currentlyloaded on the server for this volume does not containobjects corresponding to the one and only point-in-timebackup. It contains an incomplete point in time ormultiple points in time.

System action: The directory is not selected forrestore.

User response: To be able to select an entire directoryfor restore, select "Use Latest" or "Use Point in Time"from the Point in Time dialog.

FMV1828E Screen size is too small for using thePICK option.

Explanation: You cannot use the PICK option on aworkstation that has a screen smaller than 20 charactersacross and 10 lines down.

System action: Tivoli Storage Manager did notcomplete the operation.

User response: Retry the operation using aworkstation that has a screen with the minimum size,or do not use the PICK option.

FMV1831E Password expired. The administrator forthis system must run Tivoli StorageManager to update the password.

Explanation: The password expired.


User response: The administrator for this system mustupdate the password.



FMV1832W The option 'option' is no longersupported and will be ignored by TivoliStorage Manager client in this release.

Explanation: The specified option is in the process ofbeing made obsolete and will be ignored by the clientin this release. This option will be removed in the nextrelease and will no longer be valid.


User response: Remove the option from the optionfile. Also check the documentation to see if this optionhas been replaced by a newer option.

FMV1834S Unable to write to 'file-name' for storingpassword

Explanation: Tivoli Storage Manager cannot write tothe specified file-name.


User response: Check access permissions and diskspace. If unsuccessful, see your system administrator.

FMV1835E PASSWORDACCESS is GENERATE,but password needed for server'server-name'. Either the password is notstored locally, or it was changed at theserver.

Explanation: Either the password is not stored locally,or it was changed at the server.

System action: Tivoli Storage Manager prompts youfor the password if Tivoli Storage Manager is runningin the foreground.

User response: If Tivoli Storage Manager was runningas a background process, issue any Tivoli StorageManager command from the foreground. Enter thepassword in answer to the prompt. Then try yourbackground Tivoli Storage Manager command again.

FMV1836I Unable to process Processor Value Unithardware scan info file 'file name', errno,cause.

Explanation: The internal-use data file was notreadable.

System action: Processor Value Unit information isnot sent to the IBM Tivoli Storage Manager server.Processing continues.

User response: No response is necessary. This doesnot affect regular processing. Correct any file accesspermission issues and try the command again. If thefile exists, delete the file and try the command again.

FMV1837S File space filespace-name is ignored.Processing continues.

Explanation: The specified filespace-name in the systemoptions file is invalid.


User response: Check the file space in the systemoptions file and use a valid file space. Retry theoperation.

FMV1838E Error opening user specified options file'filespace-name' .

Explanation: The specified options file-name could notbe located or opened.

System action: Tivoli Storage Manager attempts toopen default option file.

User response: Make sure specified option file existsand is valid.

FMV1839E Cannot read password.

Explanation: An error occurred in setting up the inputfile (for example, the terminal) to be read.


User response: Check the attributes of the terminal.

FMV1852E Server could not load the table ofcontents. Status: status reason: reason

Explanation: A failure occurred when the serverattempted to load a file-level Table of contents for anNDMP volume. No file-level queries can be performedagainst the volume until the problem is solved.

System action: The table of contents is not loaded.

User response: Check the server Activity Log todetermine the cause of failure. Retry the operation aftercorrecting the problem.

FMV1853E Server could not load the Table ofContents. Status: status

Explanation: A failure occurred when the serverattempted to load a file-level Table of contents for anNDMP volume. No file-level queries can be performedagainst the volume until the problem is solved.

System action: The table of contents is not loaded.

User response: Check the server Activity Log todetermine the cause of failure. Retry the operation aftercorrecting the problem.



FMV1862W No table of contents information isavailable on the server for this volume.

Explanation: No objects for the selected volume existon the server that were backed up with table ofcontents information. Consequently no file-level queriescan be performed against the volume.

System action: none

User response: If file-level information is desired, useTOC option during backup.

FMV1865E Session rejected: Named Pipesconnection failure.

Explanation: An attempt to connect to the serverusing Named Pipes communications failed. This mighthave occurred if an incorrect NAMEDPIPENAME wasspecified in the options files or if your systemadministrator canceled a backup operation.


User response: Retry the operation, or wait until theserver comes back up and retry the operation. Ensurethat the value specified on the NAMEDPIPENAMEoption is the same as the one used by the server. If theproblem continues, contact your system administratorfor further help.

FMV1867E The server generated a CRC for verbtype CRC verb which does not match thereceived verb verb received.

Explanation: A cyclic redundancy check (CRC) failedbetween Tivoli Storage Manager client and servercommunication.

System action: The current object is skipped.Processing continues with the next object.

User response: This is an unusual condition, andcould indicate a communications problem between theTivoli Storage Manager client and server. Try theoperation again. If the problem persists, contact IBMfor further assistance.

FMV1871W The server CRC version is server CRCversion which does not match the clientversion client CRC version.

Explanation: This is a rare situation. The server andclient are using different versions of cyclic redundancycheck (CRC) algorithms.

System action: Processing continues without CRCchecking.

User response: Clients can be no more than oneversion downlevel from the Tivoli Storage Managerserver. Make sure the client and server are atcompatible levels. The command line client displaysboth client and server versions when the client starts

and connects to the server. The QUERY SESSIONcommand will also display the server version. From theGUI, use the \"Help/About\" menu item to identifythe client version, and the \"File/ConnectionInformation\" menu item to identify the server version.If the client and server versions are incompatible, thenthe Tivoli Storage Manager server administrator canturn off CRC checking for your node.

FMV1873E An unknown error occurred whileprocessing system object 'sys-obj-name':utility function 'func-name' failed witherror error

Explanation: An unknown error occurred whileprocessing a system object. The error informationcaptured indicates the reason for the failure. Thisinformation can be used to diagnose the problem.



FMV1877E The parsed string is too long for TivoliStorage Manager to process and hasbeen truncated to prevent a bufferoverflow.

Explanation: This is a rare condition. A very longstring would have to be entered by the user in acommand line, dsm.opt file, or filelist. This stringexceeds the maximum input string size of 1024 bytes.

System action: Tivoli Storage Manager truncated thestring to the maximum possible length of 1024, thencontinued with the operation. The operation may faillater due to this truncation.

User response: Check the client error log for othermessages that might have been logged after thismessage was written, and take any corrective actionsuggested by those messages. If the problem persists,contact IBM support for further assistance.

FMV1878E An unknown error occurred whileprocessing system object 'sys-obj-name':Service 'service-name' and its dependentservices could not be stopped.

Explanation: An unknown error occurred whileprocessing a system object. The service listed in themessage and all of its dependent services could not bestopped. Processing cannot complete until the service isstopped.


User response: Manually stop the service and retrythe operation.



FMV1882E Unable to stop service 'service-name';error error

Explanation: The service could not be stopped by theprogram.


User response: Manually stop the service and retrythe operation.

FMV1891W SUBDIR is not a valid option whenusing FILELIST, SUBDIR will beignored.

Explanation: When Specifying FILELIST each entry isa single object and so SUBDIR will not apply.

System action: The option SUBDIR is ignored.

User response: You may have either a -FILELIST orSUBDIR on this command, but not both.

FMV1892W Expire command is not allowed on theTivoli Storage Manager journaledfilespace 'filespace'.

Explanation: You cannot expire files from the serveron a Tivoli Storage Manager journaled filespace.

System action: The expire command will not work onthis filespec

User response: If you want to expire this filepecremove it from the local filesystem.

FMV1895I Highest macro return code was returncode value.

Explanation: This message is issued after allcommands in a client macro have completed. Thereturn code represents the highest return code that wasissued during processing of the macro. In order ofincreasing severity, the return code meanings are:

v 0 - The command completed successfully

v 4 - One or more files were skipped

v 8 - One or more warning messages were issued

v 12 - One or more error messages (except for skippedfiles) were issued


User response: For return codes other than 0, the usermay wish to verify the results of the client operation(s)and take diagnostic and repair actions, as necessary.

FMV1898I ***** Processed count files *****

Explanation: Tivoli Storage Manager has processedthe specified number of files.



FMV1899I ***** Examined count files *****

Explanation: Tivoli Storage Manager has examined thespecified number of files.



FMV1900I Return code is return code value.

Explanation: The return code has been issued for thepreceding client command. In order of increasingseverity, the return code meanings are:





The return code indicates the highest severity messagethat was issued during execution of the clientcommand. For a scheduled event, the event will beconsidered successful if the return code is 0, 4, or 8.The event will be considered to have failed if the returncode is 12.


User response: For return codes other than 0, the usermay wish to verify the results of the client operationand take diagnostic and repair actions, as necessary.

FMV1901I Highest return code was return codevalue.

Explanation: This message indicates the highest returncode of all the client commands that were executed. Inorder of increasing severity, the return code meaningsare:






User response: For return codes other than 0, the usermay wish to verify the results of the client operation(s)and take diagnostic and repair actions, as necessary.

FMV1902E The PRESCHEDULECMD commandfailed. The scheduled event will not beexecuted.

Explanation: The command specified by thePRESCHEDULECMD option must completesuccessfully in order to execute the scheduled event. Ifthe command completed with a return code of 0 (zero),



it is considered to have completed successfully. If thecommand completed with any other return code, it isconsidered to have failed. If the command failed thenthe scheduled event is not executed.

System action: The client does not execute thescheduled event, and the result code of the scheduledevent will be 12.

User response: Identify and repair the problem thatcaused the command to fail. If it is not necessary forthe command to complete before starting the scheduledevent, then consider using the PRENSCHEDULECMDoption, which does not require that the commandcomplete successfully. If a non-zero return code isnormal for this command, then consider wrapping thecommand in a script that always exits with a returncode of zero.

FMV1903W The POSTSCHEDULECMD commandfailed.

Explanation: If the command specified by thePOSTSCHEDULECMD option completed with anon-zero return code, then the scheduled event isconsidered to have completed successfully, but with awarning-level result. Note that the result of thePOSTSCHEDULECMD command will not supercede ahigher result from the scheduled client command. Forexample, if the scheduled client command completedwith a return code of 12, the scheduled event will beconsidered to have completed with a return code of 12,regardless of the outcome of the POSTSCHEDULECMDcommand.

System action: At a minimum, the result code of thescheduled event is 8.

User response: Identify and repair the problem thatcaused the command to fail. If it is not necessary forthe command to complete before posting the result ofthe scheduled event, then consider using thePOSTNSCHEDULECMD option. If a non-zero returncode is normal for this command, then considerwrapping the command in a script that always exitswith a return code of zero.

FMV1904E The archive description may not containany wildcard characters like '?' or '*'.

Explanation: Descriptions for archive files must notcontain wildcard characters.


User response: Enter an archive description that doesnot contain wildcard characters.

FMV1906I Destination must be specified for thisoperation when using FROMNODE.

Explanation: You must specify a destination with aRestore/Retrieve command when using FROMNODEprocessing.


User response: Retry the Restore/Retrieve commandwith a destination specified.

For example, with the Windows backup-archive client:

restore -fromnode=cougar \\cougar\d$\projx\*d:\projx\

Or, with the UNIX and Linux backup-archive clients:

restore -fromn=node1 -fromo=ann "/home/proj/*"/home/gillis/

FMV1907E An error occurred while trying toperform an object merge operation onthe server.

Explanation: For NetWare clients: The Tivoli StorageManager server is unable to perform a NetWare longname conversion. For Unix or Windows image backup:The group used to store associated image componentscould not be closed.


User response: For NetWare: It is possible that a morecurrent level of the Tivoli Storage Manager server canperform the conversion. Contact your Tivoli StorageManager server administrator for assistance. For Unixor Windows: This error indicates an authorizationproblem. Contact your Tivoli Storage Manager serveradministrator for assistance. If the problem still cannotbe resolved, contact IBM technical support for furtherassistance.

FMV1908I The scheduled command completedsuccessfully.

Explanation: The scheduled command completed withreturn code of zero, which is interpreted as success.

System action: The scheduled event is successful. Theresult code for the event is 0.


FMV1909E The scheduled command failed.

Explanation: The scheduled command completed witha non-zero return code, which is interpreted as failure.

System action: The scheduled event is failed. Theresult code for the event is 12.




FMV1912E An invalid registry hive was specified.

Explanation: The specified registry hive is invalid.



FMV1913E An invalid registry subkey wasspecified.

Explanation: The specified registry subkey is invalid.



FMV1914E The specified subkey isn't valid for thespecified hive.

Explanation: The specified registry subkey is invalidfor the specified registry hive.



FMV1915E Too many arguments specified for theBACKUP REGISTRY command.

Explanation: Too many arguments were specified forthe BACKUP REGISTRY command.



FMV1916E Too many arguments specified for theRESTORE REGISTRY command.

Explanation: Too many arguments were specified forthe RESTORE REGISTRY command.



FMV1917E Too few arguments specified for theBACKUP REGISTRY command.

Explanation: Too few arguments were specified forthe BACKUP REGISTRY command.



FMV1918E Too few arguments specified for theRESTORE REGISTRY command.

Explanation: Too few arguments were specified forthe RESTORE REGISTRY command.



FMV1919E The specified eventlog is not valid.

Explanation: The specified eventlog is not valid.



FMV1920E Too many arguments specified for theBACKUP EVENTLOG command.

Explanation: Too many arguments were specified forthe BACKUP EVENTLOG command.



FMV1921E Too many arguments specified for theRESTORE EVENTLOG command.

Explanation: Too many arguments were specified forthe RESTORE EVENTLOG command.



FMV1922E Too few arguments specified for theBACKUP EVENTLOG command.

Explanation: Too few arguments were specified forthe BACKUP EVENTLOG command.



FMV1923E Too few arguments specified for theRESTORE EVENTLOG command.

Explanation: Too few arguments were specified forthe RESTORE EVENTLOG command.





FMV1924E The specified system object is not valid.

Explanation: The specified system object is not valid.



FMV1925E The specified system object type is notvalid.

Explanation: The specified system object type is notvalid.



FMV1926E The specified system object type is onlyvalid on Windows NT.

Explanation: The specified system object type is onlyvalid on Windows NT.



FMV1928E Server-initiated sessions are notavailable in the LAN-free mode.

Explanation: Conflicting optionsSESSIONINIT=serveronly and ENABLELANFREE=yeswere specified. This combination is not allowed.


User response: Use client-initiated sessions or disableLAN-free.

FMV1929E An error occurred saving the registrykey.

Explanation: The active registry key cannot be copiedto the ADSM.SYS staging directory.

System action: The registry backup operation stops.

User response: Check the space available on theWindows boot partition to ensure there is room tocontain a copy of the Windows registry. This mightrequire several megabytes of free space. Also check theWindows permissions on the ADSM.SYS stagingdirectory and ensure that the Windows user which youare using to run Tivoli Storage Manager has full accessto that directory and its contents.

FMV1930W Tivoli Storage Manager Express clientview not supported with a TivoliStorage Manager Enterprise server.CLIENTVIEW option ignored.

Explanation: The Tivoli Storage Manager Express®

client view is only supported when going to a TivoliStorage Manager Express server. When a Tivoli StorageManager Express client connects to a Tivoli StorageManager Enterprise server, the CLIENTVIEW option isignored, and the Tivoli Storage Manager Standardclient view is displayed instead.

System action: The CLIENTVIEW option is ignoredand the Tivoli Storage Manager Enterprise client viewis displayed.

User response: If you intend to use the Tivoli StorageManager Enterprise server, then update yourCLIENTVIEW option to a value of STANDARD.Otherwise, update your TCPSERVERADDRESS optionto point to your Tivoli Storage Manager Express server.

FMV1931E An error saving one or more eventlogs.

Explanation: An error occurred saving one or moreeventlogs.



FMV1932E An error occurred replacing one or moreregistry keys.

Explanation: The registry key or keys being replacedare exclusively held by another process. The registrykeys were previously restored but the system was notrestarted.


User response: This error occurs because the registrykey or keys being replaced are exclusively held byanother process. This can happen if the registry keyswere previously restored but the system was notrebooted. Reboot the system and attempt the restoreoperation again.

FMV1933E Error accessing file or device 'name'.

Explanation: An error has occurred while accessingthe file or device.

System action: Backup set operation is not completed.

User response: Verify that the file or device exists andis accessible.



FMV1934E Backup set 'name' not found.

Explanation: The backup set name was not found onthe server.

System action: The backup set operation is notprocessed.

User response: Verify that the backup set name iscorrect.

FMV1935E Too many arguments specified for theBACKUP NTDS command.

Explanation: Too many arguments were specified forthe BACKUP NTDS command.



FMV1936E Not enough arguments specified for theBACKUP NTDS command.

Explanation: Not enough arguments were specifiedfor the BACKUP NTDS command.



FMV1937E No NTDS server name specified for theBACKUP NTDS command.

Explanation: No NTDS server name was specified forthe BACKUP NTDS command.


User response: Specify NTDS server name at thecommand and retry the operation.

FMV1938E NT Active Directory is not supported inthis OS level.

Explanation: NT Active Directory is not supported inthis OS level.


User response: Install Active Directory beforeperforming backup operation.

FMV1939E File Replication Service backup failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while backing up files under control of theWindows 2000 File Replication Service


User response: Examine the Windows 2000 FileReplication Service Event log to insure the FileReplication Service is operating properly. Restart the

service and retry the backup operation.

FMV1940E File Replication Service restore failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring files under control of theWindows 2000 File Replication Service


User response: Examine the Windows 2000 FileReplication Service Event log to insure the FileReplication Service is operating properly. Restart theservice and retry the restore operation.

FMV1941E System Volume backup failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while backing up files of the Windows 2000System Volume


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the backup operation

FMV1942E System Volume restore failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring files under control of theWindows 2000 File Replication Service


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the restore operation.

FMV1943E The operation is not supported:Downlevel server version.

Explanation: The operation cannot be performedbecause server version is downlevel.


User response: Use correct server version.

FMV1944E Error accessing file or device.

Explanation: An error has occurred while accessingthe file or device.

System action: Backup set operation is not completed.

User response: Verify that the file or device exists andis accessible.



FMV1945E The long namespace has been removedfrom the local filespace. If you wish toproceed with the backup/archiveoperation, rename your filespace on theserver.

Explanation: Tivoli Storage Manager has detected thatthe server namespace is NTW:LONG, but the localvolume does not have long name support. If youwould like to back up the volume using the shortnames, rename the filespace on the server. If you wouldlike to back up using long names, add the longnamespace support back to the volume in question.


User response: Add the long namespace support tothe volume or rename(remove) the correspondingserver filespace.

FMV1946W File exists, skipping

Explanation: The client tried to restore or retrieve thespecified file, but the file already existed in the targetrestore location and the user chose not to replace theexisting file.

System action: The file is skipped, a message islogged in dsmerror.log, and restore or retrieveprocessing continues with the next object.

User response: The file was skipped because eitherREPLACE NO was in effect, causing all existing filesand directories to be skipped, or REPLACE PROMPTwas in effect, and when prompted, the user chose toskip this file or all existing directories and files. Noadditional action is necessary if the decision to skip thefile was deliberate. Otherwise the operation can beretried using either REPLACE ALL (automaticallyreplace existing directories and files) or REPLACEPROMPT (prompt the user whether to replace the file).

FMV1947W The following directory exists and isskipped: file-space_name directory_pathdirectory_name

Explanation: The client tried to restore or retrieve thespecified directory. The directory exists in the targetrestore location and the user chose not to replace theexisting directory.

The directory can be skipped because the optionREPLACE=NO is set, which causes all existing files anddirectories to be skipped. The directory can be skippedbecause option REPLACE=PROMPT is set, and the userchooses to skip this directory when prompted.

System action: The directory is skipped, a message islogged in the dsmerror.log log file, and restore orretrieve processing continues with the next object.

User response: No additional action is necessary.

To replace the files, try the operation again and setoption REPLACE=ALL. You can set

REPLACE=PROMPT and when prompted, choose toreplace the directory.

FMV1948E The Microsoft volume shadow copysystem components could not bequeried.

Explanation: IBM Tivoli Storage Manager encounteredan error while querying the system writers undercontrol of the Windows volume shadow copy service.The Tivoli Storage Manager error log and Windowsevent log might contain additional information aboutthis error.


User response: Try the operation again. If the errorpersists, review the Tivoli Storage Manager error logand Windows event log for information related to thiserror. You might need to restart the volume shadowcopy service, then try the operation again. It might benecessary to reboot the machine to clear the volumeshadow copy error state.

FMV1949E Microsoft volume shadow copysnapshot initialization failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while initializing the Microsoft VolumeShadow Copy Service for backup or restore. The TivoliStorage Manager error log and Windows event log cancontain additional information about this error.


User response: Try the operation again. If the errorpersists, review the Tivoli Storage Manager error logand Windows event log for information related to thiserror. Use the Windows command VSSADMIN LISTWRITERS to determine the status of the VolumeShadow Copy service. You can reboot the machine toclear the volume shadow copy error state. If the systemis a Domain Controller and the Active Directory serviceis stopped, restarting the Active Directory service willresolve the issue.

FMV1950E Backup using Microsoft volume shadowcopy failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while performing a backup operation using theMicrosoft volume shadow copy service. The TivoliStorage Manager error log and Windows event logmight contain additional information about this error.


User response: Review the Tivoli Storage Managererror log and Windows event log for informationrelated to this error. Restart any failing system serviceindicated in the Windows event log. Restart the volumeshadow copy Service. You can use the Windowscommand VSSADMIN LIST WRITERS to determine thestatus of the volume shadow copy service. It might be



necessary to reboot the machine to clear the VolumeShadow Copy error state.

FMV1951E Restore using Microsoft volume shadowcopy failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring with the Microsoft VolumeShadow Copy Service.


User response: Review the Tivoli Storage Managererror log and Windows event log for informationrelated to this error. Restart any failing system serviceindicated in the Windows event log. Restart the volumeshadow copy Service. You can use the Windowscommand VSSADMIN LIST WRITERS to determine thestatus of the volume shadow copy service. It might benecessary to reboot the machine to clear the VolumeShadow Copy error state.

FMV1952E Invalid symbolic link destination'file-name' entered

Explanation: You entered a restore/retrievedestination file-name specification that is a symboliclink. To restore to symbolic link, make sure you set thefollowsymbolic option to yes. Also, check where thissymbolic link points. You can restore/retrieve to asymbolic link that points to an existing object.


User response: Enter a correct file specification.

FMV1954E Backup processing of 'file-space name'finished with failures.

Explanation: This message indicates that the filesystem backup has completed, but encountered errorsduring backup processing.


User response: Examine the client error log foradditional messages related to errors in backing up thefile system. Take any corrective action as suggested bythe messages.

FMV1956E Too few arguments specified for theBACKUP GROUP command.

Explanation: Too few arguments were specified forthe BACKUP GROUP command.



FMV1957E Showmembers and inactive aremutually exclusive parameters on aquery.

Explanation: Showmembers and inactive are mutuallyexclusive parameters on a query.


User response: Specify one of the mutually exclusiveparameters on the query

FMV1958W No base group found, attempting a fullbackup.

Explanation: A differential backup requires a previousfull backup to have been performed.

System action: Processing continues, and a fullbackup is attempted.

User response: None. Perform a full backup beforeattempting a differential backup

FMV1959I Removing previous incomplete group'name' Id:hi-lo

Explanation: A previous group backup failed withoutcleaning up the temporary groups correctly.

System action: The previous incomplete groups areremoved and processing continues.


FMV1971E The remote client agent (dsmagent)could not be started.

Explanation: The remote client agent cannot bestarted. This error message is usually preceded orfollowed by other messages.


User response: Check the error log for any othermessages that might indicate a reason for the failure.Verify that the web client is installed correctly. Try tocorrect any indicated problems, then try the operationagain. If the problem persists, contact IBM technicalsupport for further assistance.

FMV1972E The connection to the remote clientagent (dsmagent) failed. Either the portnumber could not be read, or the portnumber is invalid.

Explanation: An error occurred when trying to readthe port number. A connection to the remote clientagent cannot be made.


User response: Check the error log for any othermessages that might indicate a reason for the failure.Verify that the web client is installed correctly. Try to



correct any indicated problems, then try the operationagain. If the problem persists, contact IBM technicalsupport for further assistance.

FMV1973I VSS writer for system object 'name' doesnot exist. Restore skipped.

Explanation: Microsoft Volume Shadow Copy Servicedoes not detect a writer for this system component.Either the component is not installed or is not running..


User response: Install or enable the affected systemservice and retry the operation.

FMV1974W Error removing previous incompletegroup Id:hi-lo

Explanation: A previous group backup failed withoutcleaning up the temporary groups correctly, and theerror still can not be cleaned up.

System action: The previous incomplete groupsremain and processing continues.


FMV1975W Tivoli Storage Manager server errorreason occurred closing and renamingthe group

Explanation: An error was encountered closing andrenaming the temporary group.

System action: The backup is unsuccessful.

User response: Ensure that the user has the properauthority to update the group and try the operationagain.

FMV1976E The specified system service is notvalid.

Explanation: The specified system service is not valid.



FMV1977E Dsmcad schedule invocation wasunsuccessful. This command will betried again in 10 minutes.

Explanation: Dsmcad was unable to get the validscheduler information from the dsmc schedule process.This could be due to some problems during thescheduler initialization, such as incorrect option usage.

System action: Dsmcad will try to invoke thescheduler again in 10 minutes in order to get the validinformation.

User response: Check the console and error logs to

determine what kind of error occurred during the dsmcprocess and correct the problem.

FMV1978E The Tivoli Storage Manager server isdownlevel and does not support therequested function. See error log forversion information.

Explanation: The function being used requires a morecurrent Tivoli Storage Manager Server.


User response: Upgrade your Tivoli Storage ManagerServer to a level that supports this function. See errorlog for version information.

FMV1979E The Tivoli Storage Manager StorageAgent is downlevel and does notsupport the requested function. Seeerror log for version information.

Explanation: The function being used requires a morecurrent Tivoli Storage Manager Storage Agent.


User response: Upgrade your Tivoli Storage ManagerStorage Agent to a level that supports this function. Seeerror log for version information.

FMV1980E The Tivoli Storage Manager Server andTivoli Storage Manager Storage agentare downlevel and do not support therequested function. See error log forversion information.

Explanation: The function being used requires a morecurrent Tivoli Storage Manager Server and TivoliStorage Manager Storage agent


User response: Upgrade your Tivoli Storage ManagerServer and Tivoli Storage Manager Storage agent to alevel that supports this function. See error log forversion information.

FMV1981E Server :Version ver, Release rel, Levellev.subl Storage Agent:Version SAver,Release SArel, Level SAlev.SAsubl

Explanation: This message supplies extra detail todownlevel messages.


User response: This message supplies extra detail todownlevel messages.



FMV1986E Initialization functions cannot open thetrace file specified.

Explanation: The file "tracefile-name could not beopened during initialization. The specified path may beincorrect. It is also possible that the current user doesnot have permission to write to the tracefile in thedirectory specified. It is also possible that no space isavailable at the given tracefile location.


User response: Make sure the tracefile option pointsto a valid path and that the user has properpermissions to write to the file specified.

FMV1987E A destination file specification is notallowed with this command.

Explanation: Of all the system object restorecommands only RESTORE ASR allows the entry of adestination file specification.


User response: Re-issue the command without adestination file specification.

FMV1988W No filespaces are selected for preview.

Explanation: You requested a preview operationwithout selecting a client filespace.

System action: Tivoli Storage Manager cannot performa preview without a filespace selected.

User response: Select the volumes you want topreview and retry the operation.

FMV1989E Initialization functions cannot open theError Log file specified.

Explanation: The Error Log file could not be openedduring initialization. The specified path may beincorrect. It is also possible that the current user doesnot have permission to write to the logfile in thedirectory specified. It is also possible that no space isavailable at the given logfile location.


User response: Make sure the logfile option points toa valid path and that the user has proper permissionsto write to the file specified.

FMV1990W The 'filesystem name' volume mount pointcan not be accessed. The Tivoli StorageManager return code is 'rc'.

Explanation: The client is unable to access volumemount point. The common reasons for this are that theaccount under which the client is running does nothave access to the volume mount point, or the volume

is mounted onto a cluster volume which is currentlynot available.

System action: The inaccessible mount point isskipped and processing continues. with the next mountpoint or volume.

User response: Check the error log for additionalmessages that might yield additional information aboutthe problem that prevents access to the volume mountpoint. Ensure that the Tivoli Storage Manager client isrunning under an account which as access to thevolume mount point. Ensure that the mount point isnot accessing a clustered volume. Please refer toMicrosoft KB Article 280297 for more information abouthow to configure volume mount points on a clusteredserver.

FMV1991E An error occurred processing registrykey 'key-name', data value 'value-name'.See the client error log for additionalinformation about this error.

Explanation: An unexpected error occurred when theclient tried to read or update the Windows registry.Additional information regarding the error is usuallyplaced in the error log.

System action: The operation might not executecorrectly, depending on the error.

User response: Check the client error log for any othermessages that might have been logged when thismessage was written, and take any corrective actionsuggested by those messages. If the problem persists,contact IBM support for further assistance.

FMV1995W Objects of different types cannot bedeleted at the same time.

Explanation: Deleting objects of different types is notallowed. For example, deleting Backup Sets and regularfile objects at the same time is not possible.

System action: No processing takes place.

User response: Select objects of the same type toperform delete operation.

FMV1996W The volume mount points enumerationon 'filesystem name' volume failed.Windows system error code: error;reason: 'error-reason'.

Explanation: The client was unable to scan thespecified volume for volume mount points. The errorinformation captured indicates the reason for thefailure. A common reason is that the account underwhich the client is running does not have access to thevolume.

System action: The processing continues with the nextvolume.



User response: Ensure that the client is running underan account which has access to the volume and volumemount points. Correct the condition causing the errorand try the operation again. If the problem persists,contact your system administrator or Tivoli StorageManager administrator for further help.

FMV1997W No files have been previously backedup for the VSS component'component-name'.

Explanation: You tried to restore the Microsoft VolumeShadow Copy (VSS) System State component whichdoes not contain file data. This is not necessarily aproblem.


User response: Check the error log for any othermessages that occurred during backup. The logs canindicate a reason for the failure.

FMV1998W Transaction byte limit 'name' is notsupported by the server. Value reset tolimit

Explanation: The TXNBYTELIMIT is larger than theserver supports. The value will be reset to a supportedlimit.

System action: TXNBYTELIMIT is reset, andprocessing continues.

User response: Set the option to a value supported bythe server.

FMV1999E type of the operation processing of'filespace-name' stopped.

Explanation: The client has encountered a conditionwhere it can not continue processing the specified filespace. The Tivoli Storage Manager client error log orschedule log should contain additional messagesrelated to this error.


User response: Check the Tivoli Storage Managerclient error log and schedule log for any additionalmessages related to this error. Take any correctiveaction that might be suggested by the related messages,then try the operation again. If the problem persists,contact your Tivoli Storage Manager administrator forfurther assistance.

FMV2026W Bad sectors were detected on the volume'volname'.

Explanation: Bad sectors are skipped during imagebackup/restore operations.


User response: Make sure the volume data is not

corrupt by using system tools like chkdsk (Windows)or fsck (Unix).

FMV2032I The client VM restore is skipping theunsupported Independent disk : vmdk

Explanation: The VMware vStorage APIs do notsupport snapshoting Independent disks, no backupswere created.



FMV2036W Pruning functions cannot open one ofthe Tivoli Storage Manager prune files:log-name. errno = errno-value,

Explanation: The file "log-name could not be openedduring pruning. The system set the error codeerrno-value. If the reason given is "access denied," thecurrent user does not have permission to write to thefile in the directory specified. It is also possible that nospace is available at the given file location or anotherTivoli Storage Manager process started by different userid is performing pruning at the same time.



FMV2037W Schedule log pruning failed.

Explanation: The schedule log pruning functioncompleted with errors.


User response: Check error log for possible reasons offailure.

FMV2038W Invalid option 'option-name' receivedfrom the Tivoli Storage Manager serverclient options set.

Explanation: The client received an invalid optionfrom the Tivoli Storage Manager server's client optionset. Although most syntax checking for client option setoptions is done by the server, there are still errors thatcan only be detected by the client. These errors include:

v Option value is not correct.

v Options that have been retired by newer versions ofthe Tivoli Storage Manager client.

v Missing brackets or directory delimiters.

v Include and exclude patterns that are too complex.

System action: The option is ignored by the TivoliStorage Manager client.

User response: Contact the Tivoli Storage Managerserver administrator to determine if the option can be



removed from the client option set.

FMV2039E Invalid destination file specification'file-name' entered

Explanation: The destination file specification mustend with directory delimiter when performing a file listrestore, or when the restore specification is for morethan one file, or when the option SUBDIR YES is ineffect.


User response: Specify a destination that ends withdirectory delimiter.

FMV2040E While attempting to communicate withthe remote client, a version checkreveals that the versions do not match.The version is remoteversion but theexpected version is localversion.




FMV2041E Snapshot Differencing support is notavailable on the specified NetApp filer.

Explanation: Incremental by snapshot differencebackup cannot be performed because required supporton the specified NetApp filer is not availble. .



FMV2042W 'symboliclink':is a symbolic link to a fileor directory in another filesytem. ACLsor extended attributes might not bebacked up.

Explanation: The backup or archive operand containsa symbolic link to a file or directory in another filesystem. Processing may lead to loss of ACLs or otherextended attributes because they might not beprocessed.

System action: The file data is backed up. Processingcontinues with the next object.

User response: If you need to ensure that ACLs andother extended attributes are backed up successfully, donot use symbolic links to back up files on other file

systems of different file system types. Instead use TivoliStorage Manager to process the other file systemdirectly.

FMV2043I The virtual machine template 'name' hasalready been backed up.

Explanation: Virtual machine templates are skipped ifno change has occurred since the last backup.

System action: Processing skips this virtual machinetemplate.

User response: To back up this virtual machinetemplate, run an incremental forever full backupoperation.

FMV2044E The template virtual machine 'name'cannot be restored when the TivoliStorage Manager data mover node onthe vStorage Backup Server is connecteddirectly to an ESX/ESXi host.

Explanation: The VMware vStorage API do notsupport template virtaul machine operations whenconnected directly to an ESX/ESXi host.

System action: Processing stops for this templatevirtual machine

User response: Virtual machine template operationsare supported when the IBM Tivoli Storage Managerdata mover node connects directly to a ESX/ESXi host.Modify the VMCHOST to connect the TSM data moverto a vCenter Server.

FMV2045E The VMENABLETEMPLATEBACKUPSoption is not specified. The virtualmachine template 'name' can not bebacked up.

Explanation: The VMENABLETEMPLATEBACKUPStemplate option must specify YES in order for a virtualmachine template to be included in a backup operation.The default value is NO.

System action: Processing stops for this templatevirtual machine

User response: Use the option-vmenabletemplatebackups=yes and run the operationagain.

FMV2046S Error 'errtxt' (errno=errno) occurredtrying to write to audit log 'file-name'.The audit log function is disabled.


System action: Audit logging is disabled for the restof the operation. The return code for the operation is



set to 12 to indicate that the contents of the audit logare incomplete.


FMV2047E An unexpected error was encounteredprocessing a system state/servicesrequest. Tivoli Storage Managerfunction name : function-name TivoliStorage Manager function : function-descTivoli Storage Manager return code :TSM-rc Tivoli Storage Managerexplanation : TSM-msg Tivoli StorageManager file : file-name (line-number)

Explanation: None.

System action: Processing the system state stops.


FMV2048W Named stream of object'object-namepath-name file-name' is corrupt.

Explanation: One or more of the file's named streamsare corrupt.

System action: The named stream is notrestored/retrieved.

User response: The backup copy of the named streamis damaged. The file is restored to as great an extent aspossible, but the file should be examined to verify thatit is usable.

FMV2049W Named stream of object 'object-name' maybe corrupt.

Explanation: One or more of the file's named streamsmay be corrupt.

System action: The named stream isrestored/retrieved to as great an extent as possible.

User response: The backup copy of the named streammay be damaged. The file is restored to as great anextent as possible, but the file should be examined toverify that it is usable.

FMV2050E Tivoli Storage Manager needs to promptfor the password but cannot promptbecause the process is running in thebackground.

Explanation: If PASSWORDACCESS=PROMPT or ifthe password that is stored locally is incorrect, TivoliStorage Manager attempts to prompt the user for thepassword. The attempt to prompt the user fails becauseTivoli Storage Manager is running in the background.

When a process is running in the background,prompting is not allowed.


User response: If RUNASSERVICE=YES, do not setPASSWORDACCESS=PROMPT. UsePASSWORDACCESS=GENERATE.

FMV2051W The local snapshot repository was notfound on location.

Explanation: The specified directory for the localsnapshot location does not exist.


User response: A new local snapshot repository willbe build in the specified directory.

FMV2052E Information about the disk subsystem ismissing.

Explanation: The local snapshot repository could notbe initialized due to missing information about the disksubsystem.


User response: The application ensures that the disksubsystem is initialized properly. Check for precedingerror messages.

FMV2053E A memory allocation error has occurredin file filename, line number linenumber.




FMV2054E Operating system error errno: messagetext.

Explanation: The application encountered anunexpected message error during the execution of asystem function. The respective operating system errorand message text will be displayed.



FMV2055I The local snapshot manager could notbe locked.

Explanation: The local repository is locked by anotherapplication. This process will proceed when the otherapplication unlock the local repository.





FMV2056I Waiting maximal timeout seconds untilthe lock is released by the otherapplication.

Explanation: While the local repository is locked byanother application, the program will wait a specificperiod of time to proceed. For example, in the mySAPenvironment, the wait period is 1 hour.



FMV2057E Local snapshot manager not initialized.

Explanation: The local snapshot repository was usedwithout previous initialization.


User response: The system normally ensures that thelocal repository is initialized. Check for preceding errormessages.

FMV2058E The data container with ID dcID couldnot be updated in the local repository.

Explanation: During a FlashCopy backup the targetset record in the local repository is updated with thecorrespondent properties. A failure occurred duringthat process.


User response: Check for preceding error messageslike memory allocation error or other system error.

FMV2059E Cannot find a target data container thatmatch with the source data container.

Explanation: During a snapshot type backup orhardware function, Tivoli Storage Manager tries to finda target data container that match to the source datacontainer to satisfy the operation. A matching targetdata container could not be found.


User response: See the rules for select one of multipletarget data containers. For example, this message willbe displayed if the user is trying to start a FlashCopybackup of type 'INCR' and all the target sets are beingused for the FlashCopy type 'COPY'. Make sure alsothat the target volumes are available to the backupsystem and the syntax is correct for the following setupfile parameters: 1. shark_target_volume 2.shark_copy_service_code 3. java_home_directory 4.primary_copyservices_servername 5. shark_username 6.shark_password

FMV2060W Cannot find a volume in the target datacontainer dcID to match with the sourcesrcvol.

Explanation: This warning message indicates that forthe specific source not any target volume could befound in this target data container that matches for aFlashCopy operation. If multiple target data containersare being used, the processing will continue checkingthe volumes of the next target data container.



FMV2061W The target data container with ID dcidwas not found in the local repository.

Explanation: An inquire of the data container with thespecified ID could not be satisfied because that targetset does not exists in the local repository.

System action: Processing may continue.

User response: The application that is requesting theinquire will decide whether or not the error should endthe program. Check for following messages.

FMV2062W Could not find a target data container inthe state state to fulfill the requestedcriteria.

Explanation: A data container in the specified statewas not found in the local repository to satisfy specificcriteria requested by the application.


User response: Which criteria have been passed isapplication specific. Check for following messages. Theapplication will decide whether or not that warningshould end the program.

FMV2063W The local snapshot repository alreadyexists on the directory location.

Explanation: An application tried to create the localrepository in a directory that already exists.


User response: The application will decide whether ornot that warning should end the program. Check forfollowing messages.

FMV2064I The local snapshot repository will becreated on the directory location.

Explanation: The local snapshot repository containinginformation about the state of the data containers isbeing created.





FMV2065I The local snapshot repository could notbe created on the directory location.

Explanation: A failure occurred creating the localsnapshot repository.


User response: Look for a operating system errormessage.

FMV2066E Cannot read the .fct file filename.

Explanation: The .fct file containing the target datacontainers was not found or is not accessible.


User response: Check the name, the path and theright of the file.

FMV2067E The exception CLsmException wasthrown. Reason: txt.

Explanation: An unexpected error occurred processinga function of the local snapshot repository.


User response: Check the specific reason.

FMV2068E No target LUNs were found for the datacontainer dcID in the .fct file filename.

Explanation: The program will search in the .fct filefor each specific data container a list of entries with thelabel <PREFIX>TARGET_VOLUME where the prefixdepends on the hardware type. Either you have awrong label for the target volumes of the specified datacontainer or this data container in the .fct file does nothave any target LUNs.


User response: This error can only occurred if theapplication does not have a GUI where the userprovides the input of the target data containers and theformat will automatically be checked. If so, pleasecheck the format of the .fct file.

FMV2069E Cannot read the file filename of the localsnapshot repository.

Explanation: The system keeps some informationabout the state of the data containers locally in a file.This file was not found or is not accessible.


User response: Check the name, the path and theright of the file.

FMV2070E The repository state file filename isempty or has a wrong format.

Explanation: The system keeps some informationabout the state of the data containers locally in a file.This file was found but the expected format of the datain not correct.


User response: Normally the system ensures that theformat of this file is correct. Check for preceding error.

FMV2071E The data container dcID could not beinserted in the local snapshot repository.

Explanation: The system keeps some informationabout the state of the data containers locally in a file.Inserting an entry for a new data container occurred anerror.


User response: This is an unexpected error. Check forpreceding error. If not any other error can be seen,collect the logs and traces and contact the support.

FMV2072E An unexpected error was encounteredprocessing a Tivoli Storage Manageroperation using a hardware or snapshotfunction. Tivoli Storage Managerfunction name : function-name TivoliStorage Manager function : function-descTivoli Storage Manager return code :TSM-rc Tivoli Storage Manager file :file-name (line-number)

Explanation: None.



FMV2073E The file filename of the local snapshotrepository could not be opened forwriting.

Explanation: The system keeps some informationabout the state of the data containers in the localsnapshot repository. Opening a file of this repositoryoccurred an error.


User response: Check the rights permission of thatfile.



FMV2074E Cannot open user input FlashCopytarget file 'fct_file'.

Explanation: The FlashCopy target file that the userprovided cannot be read.


User response: Run the client configuration utility andprovide a valid FlashCopy target user input file.

FMV2075E There is no VTOC data available for thevolume. The volume cannot be backedup.

Explanation: The volume disk label type is not VTOC.It is possible that your disk is formatted with an EFIlabel. The Tivoli Storage Manager client on Solariscurrently supports only VTOC disk labels.

System action: The volume is not backed up.

User response: Do not attempt to backup volumesformatted with a non-VTOC disk label.

FMV2076E program-name: Space Managment can notbe added for file system 'filesystem' Thelength of the file system name exceedsthe maximum length of 'maxlength'which can be stored in a DMAPIattribute.

Explanation: The DMAPI has a limitation in the sizeof data that can be stored in a DMAPI attribute. If thelenght of the file system name exceeds this limit theTivoli Storage Manager client can not add spacemanagement to the file system.

System action: Space management cannot be added tofile system.

User response: Please make sure that the length of thefile system name does not exceed the DMAPI limit.

FMV2077E program-name: Reconcile for file system'filesystem' can not be started for theselected mode in a non-scoutenvironment. Please use Two WayOrphan Check Reconcile instead.

Explanation: The Tivoli Storage Manager clientreconciliation program can not be started in orphancheck or stub restore mode when the HSM system isconfigured to run without the scout daemon.

System action: Reconcile can not run in a non scoutenvironment.

User response: If you have configured a non scoutenvironment you need to use the Two Way OrphanCheck Reconcile.

FMV2078E System state backup is not allowedCLUSTERNODE is set to YES.

Explanation: When the CLUSTERNODE option is setto YES, the backup systemstate command is not valid.

System action: System state backup is stopped.

User response: If the CLUSTERNODE option isincorrectly set to YES, then change the option to NOand try the operation again. Otherwise see thebackup-archive client manual for further informationabout configuring the client to run in a clusterenvironment.

FMV2079E Error processing 'filespacenamepath-namefile-name': error scanningsnapshot

Explanation: This message is issued when the TivoliStorage Manager client is unable to read data from asnapshot used for the backup. If you are performingthe Microsoft Volume Shadowcopy Service (VSS)snapshot backup one possible cause is that theoperating system deleted a VSS snapshot because theshadow copy storage could not grow. If you areperforming the snapshot difference incremental backupon normal NetApp/N-Series volumes one possiblecause is that the base snapshot was accidentallyremoved from the NetApp file server.

System action: Backup processing for the file systemstops.

User response: If you were performing VSSsnapshot-based backup, examine the client error logand the Microsoft Windows system event log for anyother messages that might help identify the problem. Ifthere are no obvious reasons for the failure, try theoperation again,the problem might be caused bytemporary I/O conflicts between VSS and other systemdisk I/O activities. If you were performing snapshotdifference incremental backup, contact your TivoliStorage Manager administrator to verify that basesnapshot was not accidentally deleted.

FMV2080W The value 'option' for the option 'option'is no longer supported and will beignored by Tivoli Storage Managerclient in this release.

Explanation: The specified option value is in theprocess of being made obsolete and will be ignored bythe client in this release. This option value will beremoved in the next release and will no longer bevalid.


User response: Update the option value or remove theoption from the option file. Also check thedocumentation to see if this option has been replacedby a newer option.



FMV2083W No vApps that match the inputspecification were found.

Explanation: A vApp that matches the specified inputor the VAPP value in the DOMAIN.VCD option wasnot found.

System action: The operation is stopped

User response: Make sure the the VAPP value in theDOMAIN.VCD option is correct.

FMV2084I Creating a new vApp

Explanation: The estore is attempting to create thedestination vApp.

System action: This message is for informationalpurposes only.


FMV2085E The virtual machine is configured as afault tolerant virtual machine. As aresult, it cannot be backed up.

Explanation: vSphere does not allow for the snapshotor backup of fault tolerant virtual machines withvStorage API for Data Protection.


User response: To back up a fault tolerant virtualmachine with vStorage API for Data Protection, firstdisable fault tolerant. Then, after the backup completes,enable fault tolerant.

FMV2088E Session rejected: The client does not useunicode.

Explanation: The server cannot accept the clientsession because the client does not use unicode and thenode already contains a unicode filespace. The serverrecords whether or not the client's data is unicode, anddoes not let the node change this attribute.


User response: Logon to the server from a client witha platform that uses unicode data. For example, theoriginal platform that was used to create the existingfilespaces for this node. Alternatively, if the client nodeneeds to change to the platform that is currently beingattempted, contact the server administrator to removethe existing filespaces that contain unicode data and trythe node connection again.

FMV2090I The virtual machine folder could not befound in this path: 'name'.

Explanation: The destination target does not have theoriginal inventory path that was saved with the virtualmachine. As a result, the virtual machine is restored tothe top level of the ESX/ESXi inventory.


User response: None

FMV2091I The virtual machine resource could notbe found in this path: 'name'.

Explanation: The destination target does not have theoriginal resource path that was saved with the virtualmachine. As a result, the virtual machine is restored tothe top level of the ESX/ESXi inventory.


User response: None

FMV2092I The restore process will override theoriginal inventory path that was savedwith this virtual machine.

Explanation: Specifying the -datacenter or -host optionwill override the original inventory path that wassaved with the virtual machine. As a result, the virtualmachine is restored to the top level of the ESX/ESXiinventory.


User response: None

FMV2093E The remote file system agent isdownlevel and does not support thisoperation. NODENAME : nodeMULTI-NODE NAME : multi-nodehostname : host TCP/IP address :tcpaddr:tcpport version :version.release.level..mod

Explanation: None.


User response: Upgrade the remote file system agentto a supported level.

FMV2097E Unable to establish a session with theTivoli Storage Manager server as targetnode 'target' using agent node 'agent'.

Explanation: None.


User response: Ensure that the multi-node name existson the server and that the agent node has the properauthority to target node listed.

FMV2100E Neither source volume id nor targetvolume id is in the volume list.

Explanation: None.





FMV2101E Compressed data grew.

Explanation: The size of data is growing aftercompression


User response: The application must abort thetransaction.

Please turn off compression and try to resend theobject.

FMV2102E File list processing not started

Explanation: An error occured before the file listprocessing was started.



FMV2104E An error occured after processing thefile list.

Explanation: An error occured after the file listprocessing completed.



FMV2105I File list entry not Processed: File ListEntry

Explanation: A file list operation encounted an error.This entry from the file list was not processed.



FMV2106I Connection to primary Tivoli StorageManager server primary server; failed

Explanation: A communication error occured whileattempting to connect to the primary server. The nodeis configured for replication and will attempt to connectto the secondary server.


User response: Contact the Tivoli Storage Managerserver administrator to verify if the primary server isavailable. If the primary server is available, check theTivoli Storage Manager error log for communicationsfailures and correct any configuration issues. If theTivoli Storage Manager server is not available, allow

the node to fail over to the secondary server asconfigured by the primary Tivoli Storage Managerserver administrator.

FMV2107I Attempting to connect to secondaryserver secondary server; at secondary server;: TCP/IP Port;

Explanation: The node is configured for replicationand will attempt to connect to the secondary server.The secondary server address and port are configuredby the primary Tivoli Storage Manager serveradministrator and are saved in the options file.


User response: Contact the Tivoli Storage Managerserver administrator to verify if the primary server isavailable. If the primary server is available, check theTivoli Storage Manager error log for communicationsfailures and correct any configuration issues. If theTivoli Storage Manager server is not available, allowthe node to fail over to the secondary server asconfigured by the primary Tivoli Storage Managerserver administrator.

FMV2108I Connected to secondary server secondaryserver;.

Explanation: The node is configured for replicationand has successfully connected to the secondary server.



FMV2110I Connection to secondary server TivoliStorage Manager secondary server; failed

Explanation: A communications error occured whileattempting to connect to the secondary server. Thenode is configured for replication and an attempt toconnect to the secondary server was made but failed.


User response: Contact the Tivoli Storage Managerserver administrator to verify if the secondary server isavailable. If the secondary server is available, check theTivoli Storage Manager error log for communicationsfailures and correct any configuration issues.

FMV2111E The REPLSERVERNAME entry for thespecified MYREPLICATIONSERVERoption was not found.

Explanation: The MYREPLICATIONSERVER optionmust have a matching REPLSERVERNAME entry inthe options file. The REPLSERVERGUID,REPLTCPPORT, and REPLTCPSERVERADDRESS mustalso be specified. These options are normally set by theTivoli Storage Manager server administrator and savedto the options file during logon to the primary server.




User response: Manually edit the options file to eithercorrect or remove the options.

FMV2112I Secondary server is configured as'read-only'. Backup and Archiveoperations are not supported when thesecondary server is in 'read-only' mode

Explanation: The Tivoli Storage Manager client hasestablished a session with a server that is configured as'read-only'. The Tivoli Storage Manager server isconfigured as a replication server and will not acceptdata from this node.


User response: The Tivoli Storage Manager may beused for Restore, Retrieve and Query operations.Backup and Archive commands will fail. The TivoliStorage Manager server administrator can enableBackup and Archive operations for the node with the'Update Node' command.

FMV2113E The Command; command is not enabledwhen connected to the secondary serverin failover mode.

Explanation: The Tivoli Storage Manager client hasfailed over and established a session with a secondaryserver. The Tivoli Storage Manager server is configuredas a replication server and will not accept data fromthis node. Commands that store data on the server aredisabled.


User response: You can use the Tivoli StorageManager client for Restore, Retrieve, and Queryoperations. Backup and Archive operations will fail.

FMV2114W IBM Tivoli Storage Manager applicationprotection did not copy the VSSManifest files from VM 'VM'.

Explanation: The VSS Manifest files are not found onthe guest machine.

System action: The VSS Manifest files cannot becopied. Verify that the VSS and SQL Writer services arerunning on the guest VM

User response: None

FMV2115I Replication server connectioninformation saved: connection information;

Explanation: This node is configured for replication.The replication server connection information has beensaved to the options file. The replication server optionsare set by the IBM Tivoli Storage ManagerAdministator, sent to the client during logon, and aresaved to the options file.



FMV2116W IBM Tivoli Storage Manager applicationprotection did not back up the VSSManifest files from VM 'VM'.

Explanation: A failure occurred while backing up thefiles that are necessary for application protection.

System action: The back up of this VM failed.

User response: Check the dsmerror.log for additionalinformation. Then try the operation again.

FMV2117E Source volume is of subtype dev-typeand destination is of subtype dev-type.Destination must be larger than source.

Explanation: Logical volumes from scalable volumegroups (subtype DS_LVZ) do not contain an LVCB.That is, the very first block contains user data. AIXLVM volumes from original volume groups (subtypeLVM) contain a Logical Volume Control Block (LVCB)on the first block (512 bytes) of the volume. Whenrestoring to a volume of subtype LVM, the first blockmust be skipped in order to preserve the existing LVCBof the destination volume. That is, the restore operationbegins writing at the second block of the volume. Thismeans that given two volumes of identical size, one ofsubtype DS_LVZ and the other is of subtype LVM, thelatter has one less 512-byte block in which to store userdata. Thus when you restore a volume of subtypeDS_LVZ to a volume of subtype LVM, it is notsufficient for the destination volume to be the same sizeas the source volume. Instead, the destination volumemust be at least one 512-block larger than the sourcevolume.


User response: Make sure that both source anddestination logical volumes are of the same type, orchoose a larger destination volume, or increase the sizeof the destination volume.

FMV2118I A write failure occurred whileattempting to save node replicationfailover values to the options file.

Explanation: A write failure is often a result ofinsufficient access permissions to the options file, butcould also be caused by the lack of available diskspace. The replication server connection informationcan not be saved and failover will not be possible.


User response: Check the local disk for possiblecauses of the write error, and check to see thatsufficient access to the options file is configured.



FMV2119I An invalid replication server addressreturn code rc value = rc-value wasreceived from the server.

Explanation: An invalid replication server addressreturn code indicates that the server was not able toaquire connection information.

System action: Possible server problem.

User response: Check the server log for moreinformation.

FMV2120W The last store operation date reported bythe server replication server; of servercommit date; UTC does not match the laststore operation date of client commit date;UTC stored by the client.

Explanation: The last store operation date reported onthe server does not match the date stored locally on theclient. If connected to the replication server it is likelythat the replication was done before the last storeoperation from the client to the primary server. Hence,the replication is out of date. If connected to theprimary server it is likely that the previous backup wasdone from another machine.


User response: Contact the Tivoli Storage Managerserver administrator. Restoring from an out of datereplica may lead to loss of data. If the primary servercannot be recovered, a full backup to the replica maybe appropriate. If connected to the primary server, themessage can be ignored.

FMV2121I The file space on replication server;started replication at server replicationstart date; The replication completedsuccessfully at server replication completedate;.

Explanation: The last server replication completedsuccessfully.



FMV2122I The file space on replication server;started replication at server replicationstart date;. The replication did notcomplete successfully. The lastsuccessful replication completed at serverreplication last successful date;.

Explanation: The last server replication did notcomplete successfully.


User response: Contact the Tivoli Storage Managerserver administrator. Restoring from an out of date

replica may lead to loss of date. If the primary servercannot be recovered, a full backup to the replica maybe appropriate.

FMV2123W Issue the dsmc SET PASSWORD-type=VCD 'vCloud Director hostname''userid' 'password' command to save anencrypted password.

Explanation: The VCDPW option was found either inan options file or as a command- line entry. Althoughboth methods of entry are allowed, they present asecurity risk because the password is in plain text andis not encrypted.

System action: The option is accepted and the VCDpassword is used in the current session.

User response: To save an encrypted password, issuethe following command: dsmc SET PASSWORD-type=VCD 'VirtualCenter hostname' 'userid' 'password'

FMV2124W Client node replication table is lockedby another process.

Explanation: Another process is using the client nodereplication table. Only one process may use it at a time.

System action: This process does not use the clientnode replication table.

User response: You can serialize processes using theclient node replication table. Or you can reconfigure thecurrent process to use a different table path to avoidcontention.

FMV2126E The Organization VDC node thatcontains snapshots of OrganizationVDC 'org vdc name' of organization 'orgname' was not found.

Explanation: The Organization VDC node contains thebackup data to be restored. The specified organizationand organization VDC are not mapped to thisOrganization VDC node. As a result, the restoreoperation cannot proceed.


User response: Verify that the specified organization,organization VDC, and vApp are correct.

FMV2127E The snapshot data that is required torestore 'vapp name' cannot be retrievedfrom the Tivoli Storage Manager Server.

Explanation: The required snapshot data was unableto be retrieved from the Tivoli Storage Manager Server.

System action: The operation stopped.

User response: Check the dsmerror.log file forinformation about why the data was not retrieved.Then, try the operation again. If the problem persists,



visit the IBM Support Portal for additional informationat http://www.ibm.com/support/entry/portal/.

FMV2128E Failed in creating a restored version ofvApp 'vapp name'.

Explanation: The operation to create a restored vAppon the vCloud failed. The data associated with thevApp snapshot might not be complete.


User response: Check the dsmerror.log file forinformation about why the operation failed. Then, trythe operation again. If the problem persists, visit theIBM Support Portal for additional information athttp://www.ibm.com/support/entry/portal/.

FMV2135E The node on the Tivoli Storage Managerserver is in read only mode.

Explanation: The server has prevented a storeoperation on the Tivoli Storage Manager server. Themost likely explaination for this is the node has failedover to the secondary server.


User response: Contact the Tivoli Storage Managerserver administrator to verify if the primary server isavailable. If the primary server is available, check theTivoli Storage Manager error log for communicationsfailures and correct any configuration issues.

FMV2136E Operation not permitted. The secondaryserver reports the primary server isavailable. Quit and restart the TivoliStorage Manager client and retry thecommand.

Explanation: The server has prevented a storeoperation on the secondary Tivoli Storage Managerserver. The secondary server reports that the primaryserver is available. However, the Tivoli StorageManager client failed over to the secondary server.


User response: Restart the Tivoli Storage Managerclient and verify the primary server connection ismade. If the Tivoli Storage Manager client is unable toconnect to the primary server, contact the Tivoli StorageManager server administrator to verify if the primaryserver is available. If the primary server is available,check the Tivoli Storage Manager error log forcommunications failures and correct any configurationissues.

FMV2138E Failed in restoring the vApp propertiesto vApp: 'vapp name'.

Explanation: The vApp properties were not restoredto the created vApp. This failure might be caused by a

problem in the backed up vApp or in its metadata.

System action: The operation completes. However, itis possible that the restored object does not contain allof the expected content.

User response: Check the backed up vApps on thevCloud. In addition, check the dsmerror.log file for anyadditional messages that might be related to thisproblem. Try the operation again. If the problempersists, visit the IBM Support Portal for additionalinformation at http://www.ibm.com/support/entry/portal/.

FMV2143E vApp verification failed. Datainconsistency was found.

Explanation: During the verification of a vApp, aninconsistency was found in the backup data.

System action: The restore operation was stopped.

User response: Examine the client error log for anyadditional messages that might be related to thisproblem and contact Tivoli Storage Manager technicalsupport for further assistance.

FMV2145W Warning - updating an existing virtualmachine named 'name'. The restoreoperation continues.

Explanation: The virtual machine exists and will beupdated with the disks specified.

System action: The virtual machine will be updatedby the restore operation.

User response: No user action is necessary.

FMV2146E The target vCenter or ESX/ESXi host isno longer supported, for virtual machinebackups, by this version of IBM TivoliStorage Manager.

Explanation: The target vCenter or ESX/ESXi host isno longer supported, for virtual machine backups, bythis version of IBM Tivoli Storage Manager.

System action: Processing stops for this virtualmachine.

User response: Specify another target vCenter orESX/ESXi host that is supported by this version of IBMTivoli Storage Manager.

FMV2147E The virtual machine named 'name'already exists on the target system.

Explanation: The virtual machine cannot be restoredbecause the name already exists on the target system.

System action: Processing stops for this virtualmachine



User response: Use the -vmname option to rename thevirtual machine.

FMV2148I Virtual machine templates cannot bebacked up in incremental mode,switching to full mode.

Explanation: The backup of virtual machine templatesare only supported as full backups.

System action: Processing continues in full mode forthis template virtual machine.

User response: To back up this virtual machinetemplate use full mode.

FMV2149E The restore operation for this virtualmachine to the target ESX/ESXi host isnot supported because virtual machinehardware version is incompatible.

Explanation: The target ESX/ESXi host does notsupport the virtual hardware version of the virtualmachine. As a result, a restore of the specified virtualmachine to this host is not supported.

System action: Processing stops for this virtualmachine.

User response: Specify another virtual machine torestore or specify another target ESX/ESXi host thatsupports virtual hardware version of the virtualmachine.

FMV2150E SetHSMDISABLEAUTOMIGDAEMONSYES in the dsm.opt file to use HSMmulti-server functionality.

Explanation: Set HSMDISABLEAUTOMIGDAEMONSYES in the dsm.opt file to use HSM multi-serverfunctionality.

System action: HSM multi-server processing stops.

User response: SetHSMDISABLEAUTOMIGDAEMONS YES in dsm.opt.

FMV2155W Skipping file 'file-name'. File related to'server-name'.

Explanation: File is already coupled to another server.

System action: HSM continues with normal operation.

User response: Use the correct server to process thefile.

FMV2156E The server 'server-name' was not added tothe environment.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment. There are several causes for this error:

v The file system is not managed by HSM.

v The HSM management is not active for the filesystem.

v The file system is out of space.

v The default IBM Tivoli Storage Manager server forthe file system was not yet added to the multi-serverenvironment.

v The IBM Tivoli Storage Manager server name is notvalid.


User response: Eliminate the possible causes for thisissue and retry.

FMV2157E The server 'server-name' was not removedfrom the environment.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment. There are several causes for this error:

v The file system is not managed by HSM.

v The HSM management is not active for the filesystem.

v The IBM Tivoli Storage Manager server is the defaultserver for the file system and must be removed last.

v The IBM Tivoli Storage Manager server name is notvalid.


User response: Eliminate the possible causes for thisissue and retry.

FMV2158E The server 'server-name' was not added tothe environment. You must first add thedefault IBM Tivoli Storage Managerserver ('default-server-name') for this filesystem.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment. The requested IBM Tivoli StorageManager server is not the default server for the filesystem.


User response: Add the default IBM Tivoli StorageManager server first.

FMV2159I The server 'server-name' was added to theenvironment.

Explanation: The requested IBM Tivoli StorageManager server was added to the multi-serverenvironment.

System action: HSM multi-server processingcontinues.




FMV2160I The server 'server-name' was removedfrom the environment.

Explanation: The requested IBM Tivoli StorageManager server was removed from the multi-serverenvironment.



FMV2161E The server 'server-name' is not a validIBM Tivoli Storage Manager server forthis environment.

Explanation: The requested IBM Tivoli StorageManager server was not added to the multi-serverenvironment.


User response: Check the dsm.sys file for the correctIBM Tivoli Storage Manager server name.

FMV2162E HSM cannot be removed from the filesystem. The IBM Tivoli StorageManager multi-server list is not empty.

Explanation: HSM management was not removedfrom the file system.

System action: HSM processing continues.

User response: Remove all IBM Tivoli StorageManager servers from the multi-server list beforeremoving HSM.

FMV2163E The default IBM Tivoli Storage Managerserver ('server-name') for the file systemwill be removed.

Explanation: The default IBM Tivoli Storage Managerserver will be removed. The IBM Tivoli StorageManager server list for multi-server will be empty afterthis step.

System action: HSM processing continues withoutmulti-server support.

User response: nothing.

FMV2165I The server 'server-name' is the defaultserver and has been removed last.

Explanation: The requested IBM Tivoli StorageManager server was removed from the multi-serverenvironment.


User response: None

FMV2166I The IBM Tivoli Storage Manager server'server-name' is not included in themulti-server environment.

Explanation: The requested IBM Tivoli StorageManager server is not part of the multi-serverenvironment.



FMV2167W Can not read SERVERNAME attribute.

Explanation: IBM Tivoli Storage Manager cannot readthe SERVERNAME attribute from file.



FMV2168W Can not write SERVERNAME attribute.

Explanation: IBM Tivoli Storage Manager cannot writeSERVERNAME attribute to file.



FMV2169E Skipping - Requested server is notincluded in multi-server environmentfor filesystem 'file-system'.

Explanation: The requested IBM Tivoli StorageManager server is not part of the multi-serverenvironment.



FMV2170W Skipping - file linked to another server.

Explanation: The file is already coupled to anotherIBM Tivoli Storage Manager server.

System action: HSM continues with normal operation.

User response: Use the correct server to process thefile.

FMV2171E The DMAPI version 'dmapi-version' is notsupported.

Explanation: The DMAPI version installed on thisnode is not supported from the given TSM client.

System action: Due to this issue the affected HSMprocess ends.

User response: Use the documentation to identify the



supported DMAPI versions. Install a supported DMAPIand retry the HSM command or process.

FMV2172E Command not supported inHSMBACKENDMODE TSMFREE.

Explanation: That command is not supported usingan external HSM backend.

System action: Exit programm

User response: Do not use the command

FMV2173E Volume 'volume name' from vFiler 'vFilername' is mounted using AIX NFSversion 4. This configuration is notsupported for snapshot differenceincremental backups.

Explanation: Snapshot difference incremental backupsare not supported for vFiler volumes mounted usingAIX NFS version 4.

System action: Snapshot difference incrementalbackup fails.

User response: This problem is documented byNetApp BURT 630200. Apply the fix for this once it isavailable from NetApp. Specify "testflagsnapdiffenablevfilernfs4" in dsm.opt file and retry thesnapshot difference incremental backup.

FMV2174E Conflicting options HSMLOGMAX andHSMLOGRETENTION were specified.

Explanation: Values were specified for both theHSMLOGMAX and the HSMLOGRETENTION options.These options are mutually exclusive.


User response: Specify a nonzero value forHSMLOGMAX if you wish to have the Tivoli StorageManager hsm log wrap when it reaches the specifiedmaximum value. Use HSMLOGRETENTION if youwish you have the hsm log limited in size on atime-based schedule.

FMV2175I Data from server 'server-name' should berecalled using the script'dsmMultiServerRemove.pl'.

Explanation: Migrated files must be recalled before aserver can be removed from the multiserverconfiguration.

System action: The server will not be removed.

User response: Check the documentation for detailedinformation about the 'dsmMultiServerRemove.pl'script.

FMV2176E The sample journal configuration file ''could not be copied to ''.

Explanation: The TSM Journal Engine setup wizardtried to create a new journal configuration file bycopying the sample configuration file. However thesample configuration file could not be successfullycopied.

System action: The TSM Journal Engine setup wizardstops.

User response: Manually copy the sample journalconfiguration file "config\tsmjbbd.ini.smp" to"baclient\tsmjbbd.ini", then try the TSM Journal Enginesetup wizard. The "baclient" and "config" directoriescan be found in the directory where you installed theTivoli Storage Manager Backup-Archive Client. Forexample, "C:\Program Files\Tivoli\TSM\baclient" and"C:\Program Files\Tivoli\TSM\config"

FMV2177E The vCloud vApp named 'vapp name'already exists on the target system.

Explanation: The restore vApp command does notsupport restoring a vApp with an existing name.

System action: The restore was not performed.

User response: Execute the required restore commandagain, considering that the given name for the restoredvApp is not used.

FMV2181I Option primary server; saved.

Explanation: This node is configured for replication.The primary server name option is now saved to theoptions file. The replication server options are set bythe IBM Tivoli Storage Manager Administator, sent tothe client during logon, and are saved to the optionsfile.



FMV2182I Option secondary server; saved.

Explanation: This node is configured for replication.The replication server option is now saved to theoptions file. The replication server options are set bythe IBM Tivoli Storage Manager Administator, sent tothe client during logon, and are saved to the optionsfile.





FMV2183E Organization 'Org name' not found in thevCloud Director.

Explanation: The specified Organization is notrecognized by the vCloud Director.

System action: The action requested for theorganization is canceled.

User response: Verify that an organization by thespecified name exists in the vCloud. Organizationnames are case-sensitive.

FMV2184E Organization VDC 'Org vDC name' notfound in organization 'Org name'.

Explanation: The specified organization VDC is notpart of the specified organization.

System action: The action requested for theorganization VDC is canceled.

User response: Verify that an organization VDC bythe specified name exists in the specified organization.Organization and organization VDC names arecase-sensitive.

FMV2185E Failed to log on to the vCloud Directoron 'vCD host name' with user name 'vCDuser name': Authentication failed.

Explanation: The vCloud credentials specified in theVCDUser and VCDPass options were rejected by thevCloud director.

System action: vCloud operations cannot beperformed.

User response: Update the VCDUser and VCDPassoptions with valid credentials for the vCloud Director.

FMV2186E Failed to log on to the vCloud Directoron 'vCD host name' with user name 'vCDuser name': User not found.

Explanation: The vCloud user specified by theVCDUser option does not exist on the vCloud Director.


User response: Update the the VCDUser option witha valid vCloud user name for the vCloud Director.

FMV2187E Failed to establish connection to thevCloud Director on 'vCD host name'.

Explanation: A connection cannot be established tothe vCloud Director on the host that is specified by theVCDHost and VCDPort options.


User response: Verify that the values of the VCDHOst

and VCDPort options are valid, network connectivity tothe host exists, and that the vCloud Director service isrunning.

FMV2188E The vCloud protection runtime libraryis not installed or failed to load.

Explanation: The vCloud runtime library is notinstalled or cannot be loaded.


User response: Verify that the Tivoli Storage Managerfor Virtual Environments vCloud runtime library isinstalled. If neccessary, reinstall Tivoli Storage Managerfor Virtual Environments.

FMV2189E The vCloud protection runtime librarycannot be initialized.

Explanation: The vCloud protection runtime libraryfailed to initialize. This issue might be caused by theJava runtime not being installed.


User response: Verify that Java is installed.

FMV2190E The vCloud protection runtime libraryencountered an internal error.

Explanation: An internal error had occured in thevCloud runtime library.


User response: Check the dsmerror.log file for anyadditional messages that might be related to thisproblem. Try the operation again. If the problempersists, visit the IBM Support Portal for additionalinformation at http://www.ibm.com/support/entry/portal/.

FMV2191E An error occurred creating the defaultVSS staging directory 'path'.

Explanation: The Tivoli Storage Manager client usesan VSS staging directory to store files related to to VSSsnapshot operations. The Tivoli Storage Manager clientwas unable to create this directory structure.

System action: The Tivoli Storage Manager clientstopped.

User response: If the problem persists, contact IBMtechnicalsupport for further assistance.



FMV2192E Failed to read the node configurationinformation from node 'node name'.

Explanation: Node mapping information is requiredfor this vCloud operation. However, the mappinginformation either does not exist or cannot be readfrom the specified node.

System action: The operation is canceled.

User response: Make sure that you are accessing thecorrect node. The node mapping information is storedin the Provider VDC node. If necessary, go to theConfiguration page and click 'Run the ConfigurationWizard' to make corrections to the node mapping.

FMV2193E The required filespace for the vApp'vapp name' backup does not exist.

Explanation: No filespace exists for the specifiedvApp backup.


User response: Make sure that the specified vApp iscorrect. Then, try the restore operation again.

FMV2194E The snapshot data is incomplete forvApp 'vapp name'.

Explanation: Inconsistent data was found in thebacked up vApp. It is not possible to restore thespecified vApp.


User response: Check the dsmerror.log file for anyadditional messages that might be related to thisproblem. If the problem persists, visit the IBM SupportPortal for additional information athttp://www.ibm.com/support/entry/portal/.

FMV2195E The number of VMs that are availablefor restore is different from expectedaccording to the vApp 'vapp name'metadata.

Explanation: Inconsistent data was found in the vAppmetadata. It is not possible to restore the specifiedvApp. More VMs have been backed up than are nowavailable for restore. This may happen due toincomplete node replication or if a file space wasdeleted.


User response: Check the dsmerror.log file for anymessages that may indicate the problem. Run a detailedquery for this vApp to verify that all VMs backupsexist. If node replication is used, ensure it is workingcorrectly. If the problem persists, visit the IBM SupportPortal for additional information athttp://www.ibm.com/support/entry/portal/. Contact

Tivoli Storage Manager administrator for moreinformation.

FMV2196W An incompatible disk configuration isdetected for the following disk: 'diskname'. The individual database restorefor the following database is notsupported:'database name'.

Explanation: One or more database files in thisoperation are located on the dynamic or GUID PartitionTable (GPT) disks. In this configuration, individualdatabase restore is not supported.

System action: Backup of the full VM continues.

User response: To restore the environment to theprevious statue, issue a full VM restore.

FMV2197E The verification test of vApp 'vapp name'indicates that VM data is incomplete inthe vApp. The vApp cannot be restored.

Explanation: Inconsistent data was found in the VMfor the specified vApp. It is not possible to restore thespecified vApp. This may happen due to incompletenode replication or if a file space was deleted.


User response: Check the dsmerror.log file for anyadditional messages that might be related to thisproblem. Run a detailed query for this vApp to verifythat all VMs backups exist. If node replication is used,ensure it is working correctly. If the problem persists,perform a FULL new backup of the vApp and visit theIBM Support Portal for additional information athttp://www.ibm.com/support/entry/portal/. ContactTivoli Storage Manager administrator for moreinformation.

FMV2198I Backup of VMware vCloud DirectorvApp 'vApp name' in Organization VDC'Org VDC name' of organization 'Orgname' completed successfully. VMs:number of VM backed up out of number ofVMs in vApp VMs backed upsuccessfully.

Explanation: The backup operation completed. Thenumber of VMs backed up and the total number ofVMs in the vApp are displayed.


User response: If the number of VMs backed up isless than the total in the vApp please check the errorlogs for more information.



FMV2200I ***** Filling Cache count files *****

Explanation: Tivoli Storage Manager the specifiednumber of files have been added to the disk cache.



FMV2201I ***** Inspecting Cache count files *****

Explanation: Tivoli Storage Manager the specifiednumber of files have been examined in the disk cache.



FMV2202E Disk Full Error Accessing Disk Cache.

Explanation: A disk full error occurred attempting toaccess or write to the specified disk cache file during adisk cache incremental backup. See the client error logfor more detailed information.


User response: This error can be resolved by freeingup space in the file system containing the cache file, orspecifying a different location for the cache file. Use thediskcachelocation option to specify the location of thecache file.

FMV2203E Error Accessing Disk Cache.

Explanation: An error occurred attempting to accessthe specified disk cache file during a disk cacheincremental backup. See the client error log for moredetailed information. Tivoli Storage Manager.



FMV2204E Disk cache restarted.

Explanation: The length of an object name exceededthe configured disk cache key length during a diskcache incremental backup. The backup must berestarted.. Tivoli Storage Manager.

System action: Backup is restarted with a larger keylength to accommodate the object name.

User response: None required. The name of the objectthat caused the failure can be found in the dsmerror.logfile.

FMV2206W The user must have root authority to usethe memory efficient backup disk cachemethod. The operation will continueusing memory efficient backup methodwithout disk caching.

Explanation: None.

System action: The operation continues without usingdisk caching.


FMV2213E Error while querying volume propertiesof volume volserial. Please verify that thevolume specified in the target volumesfile exists.

Explanation: None.



FMV2218I The encryption key password for nodenode name and server server name hasbeen migrated.

Explanation: The format of the Tivoli Storage Managerpassword file has recently changed. The optionMIGRATEENCRYPTKEY is set and the storedencryption key password was automatically migratedto the new format. This message confirms that themigration was successful.

System action: The encryption key password has beenmigrated.

User response: No response.

FMV2219E Cannot backup or archive files intofilespace because it is owned by a TSMAPI application.

Explanation: TSM Client cannot archive or backupfiles into a file space that is used a TSM APIapplication.


User response: Use separate node names for TSMClient and TSM API application(s).

FMV2220E The cluster disk could not be put inmaintenance mode.

Explanation: The system call to put the cluster disk inmaintenance mode failed.


User response: Try the operation again. If the problemcontinues, check the client error log for any othermessages that might have been logged when thismessage was written, and take the corrective action (ifany) suggested by those messages. Examine theWindows event log which may contain additionalinformation. See your system administrator or TivoliStorage Manager administrator for further help.



FMV2221W Java was not able to resolve the IPaddress of your local machine due tonetwork misconfiguration problems!Please verify your network and DNSconfiguration are setup correctly. Notethat on UNIX machines the hostnamemust be reported correctly (the same) forIPv4 and IPv6 communication methodsin the /etc/hosts configuration file.Tivoli Storage Manager processingcontinues.

Explanation: Java was not able to get the local hostaddress due to network misconfiguration problems.


User response: Please verify your network and DNSconfiguration are setup correctly. Note that on UNIXmachines the hostname must be reported correctly (thesame) for IPv4 and IPv6 communication methods in the/etc/hosts configuration file. See your systemadministrator or Tivoli Storage Manager administratorfor further help.

FMV2223W Rejected unauthenticatedserver-initiated session from peer name.

Explanation: For security, the client will not acceptserver-initiated sessions from servers that haveauthentication turned off.

System action: The client-server session is not opened,and the schedule is not executed. The schedulercontinues to wait for contact by a server that hasauthentication turned on.

User response: If the client system is supposed toaccept scheduled events from the prompting TivoliStorage Manager server, either ask the Tivoli StorageManager server administrator to turn authentication on,or do not use server-initiated sessions. If the clientsystem is not supposed to accept scheduled eventsfrom the prompting server, ask the Tivoli StorageManager server administrator to remove the client nodename from the schedule on the prompting server.

FMV2225W User has specified 'SNAPSHOTROOT'option. snapshot provider snapshot backupis not valid in conjunction with thisoption. "SNAPSHOTROOT option willtake precedence and processing willcontinue without the use of a snapshottaken internally by Tivoli StorageManager.

Explanation: The (-SNAPSHOTROOT) option isincompatible with Tivoli Storage Manager snapshotproviders such as Logical Volume Snapshot Agent, VSSsnapshot provider, JFS2 snapshot provider etc. whichprovide a comprehensive snapshot solution withothaving to use the (-SNAPSHOTROOT) option. It isstrongly recommended that the snapshot capabilities

provided by the Tivoli Storage Manager snapshotproviders be used instead of using the(-SNAPSHOTROOT) option. Processing will continuewithout the use of the Tivoli Storage Manager snapshotproviders.

System action: Processing continues without the useof the Tivoli Storage Manager snapshot providers.

User response: See the appropriate Using theBackup-Archive Client book for your operating systemfor correct use of the named option.

FMV2227W Server option 'option-name' 'option-value'has not been applied on the client dueto the client optionSRVOPTSETENCRYPTIONDISABLED.

Explanation: The client optionSRVOPTSETENCRYPTIONDISABLED has been set toYES on the client thereby preventing the Tivoli StorageManager administrator from setting one of thefollowing client options - ENCRYPTKEY GENERATE,EXCLUDE.ENCRYPT, INCLUDE.ENCRYPT.

System action: The option will be ignored.

User response: None required.

FMV2228W Backup of VMware vCloud DirectorvApp 'vApp name' in Organization VDC'Org VDC name' of organization 'Orgname' completed. Some VMs were notbacked up. VMs: number of VM backed upout of number of VMs in vApp VMsbacked up successfully.

Explanation: The vApp backup operation completedsuccessfully. However, one or more VMs for thespecified vApp were not backed up. These VMs willnot be created during the restore operation.

System action: Processing continues to the next vApp.

User response: Check the log file for this vApp formore information about this message. Resolve theproblem, then try the operation again.

FMV2229E Failed to initialize the vCloud protectionenvironment. See the local client errorlog for detailed error messageinformation.

Explanation: The vCloud protection package couldnot be initialized.


User response: Make sure all options that are relatedto the vCloud environment are specified correctly.Check the dsmerror.log file for detailed information.



FMV2230E Failed to create vApp list according tospec 'vApp specification'

Explanation: The vApp list was unable to be retrievedfrom the vCloud Director.


User response: Make sure the values specified in theVCDHost, VCDUser, VCDPW, and DOMAIN.VCDoptions are correct. Make sure the vCloud Director isalive.

FMV2232E Failed to retrieve the list of VMs forvApp 'vApp name' from the vCloudDirector.

Explanation: The VM information for the specifiedvApp was not retrieved from the vCloud Director. Thisfailure might be caused by the vCloud Director notbeing alive or accessible.

System action: The VMs that compose the specifiedvApp are not backed up. Processing continues to thenext vApp.

User response: Make sure that the vCloud Director isalive and accessible. Check the dsmerror.log file forspecific errors that are related to this issue.

FMV2236I The virtual machine 'VM-name' containsone or more disks that exceed the 2 TBmaximum size limit. These disks will beexcluded from the backup.

Explanation: The IBM Tivoli Storage Manager clientdoes not support backing up VMDKs that are greaterthan the supported limit.

System action: The virtual machine is backed up,however the disks exceeding the limit are skipped.

FMV2238E VCDHOST option must be set beforerunning this operation.

Explanation: VCDHOST option is missing.

System action: Operation cannot continue without thisoption being set.

User response: Add the option to the client optionsfile, either via the preferences editor or by manuallyediting the file, or specify the option on the commandline.

FMV2239W The annotations field contained toomany characters and had to betruncated.

Explanation: vSphere limits the size of the annotationsto 2000 characters. Some special characters, such asnew lines, get encoded as multiple characters. This canlead to exceeding the limit even though the size mayappear to be within the limit.

System action: The annotation field is truncated toless than 2000 characters so that the vSphere API willnot reject it.

User response: Take care to avoid creating largeannotations that may exceed the 2000 character limitafter special characters are encoded.

FMV2240T The basic verification of vApp 'vAppname' succeeded.

FMV2241T The extended verification of vApp 'vAppname' succeeded.

FMV2242E No nodes were found that matched theinput specification: node specification

Explanation: An invalid node specification wasentered.

System action: The operation was stopped.

User response: Check documentation how to specifynodes.

FMV2244W The virtual machine contains one ormore disks that exceed the maximumsize limit. Specify the'-VMSKIPMAXVMDKS=yes' option toexclude these disks from the backup.



User response: Specify the'-VMSKIPMAXVMDKS=yes' option to exclude thesedisks from the backup.

FMV2245E Virtual machine backups and restoresare not supported on 32 bit data movers.

Explanation: Virtual machine operations such asbackups and restores are not supported on 32 bit DataMovers.

System action: The operation is not performed.

User response: Update to a 64 bit Data Mover andretry the operation.

FMV2246W Failed to disable maintenance mode forvApp vApp name.

Explanation: The client has tried to disable themaintenance mode of this vApp. This operation failed.


User response: Check whether the vApp is still inmaintenance mode. If yes, disable it manually.



FMV2247E ASNODENAME option must bespecified when running this command.

Explanation: When running vCloud-relatedcommands, ASNODENAME option must specify theProvider vDC node.

System action: Operation cannot continue.

User response: Specify the Provider vDC node asASNODENAME to the command.

FMV2248E Failed to load or initialize the Javaruntime library.

Explanation: The Java runtime library (libjvm),required by the vCloud Protection environment, cannotbe loaded, or initialization of Java runtime environmentfailed

System action: Operation is stopped

User response: For Linux operating system, verify thata link named 'jre', referencing the 'jre' directory underyour Java installation path, exists in the backup-archiveclient 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,modify LD_LIBRARY_PATH to include the path tolibjvm.so (e.g. exportLD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/tivoli/tsm/client/ba/bin:/opt/ibm/java-x86_64-70/jre/bin/classic). For Windows operating system, verify thatthe JRE directory exists under the client installationdirectory. Reinstall the backup-archive client ifnecessary.

FMV2249W A virtual machine named 'vmname' existson this system. Do you want to replacethe existing virtual machine?

Explanation: Restoring this virtual machine will stopand delete the existing virtual machine and all of itsfiles. To protect application data, stop any applicationsthat are running, and then shut down the virtualmachine before you restore it.

System action: If the user chooses to continue, thesystem will stop and delete the existing virtual machineand all of its files.

User response: Choose whether to replace the existingvirtual machine.

FMV2250W A Tivoli Storage Manager core file orcrash report was found: filename

Explanation: The presence of a core dump or crashreport indicates a process has abnormally terminated.

System action: The core file or crash report name isreported in the message. Processing continues.

User response: Review the error log for any other

error messages that may help diagnose the cause of thecore dump. If possible, correct any issues found. As acore dump is generally caused by a programming error,save the file noted in this message and contact IBMtechnical support.

FMV2253W The version of the message catalog,catalogversion, in use by Tivoli StorageManager does not match the version ofTivoli Storage Manager, clientversion

Explanation: A check of the catalog version indicatesthe catalog and Tivoli Storage Manager are not thesame version. This may lead to missing or incorrectmessages being used.


User response: Review the installation of TivoliStorage Manager, verify the message catalog files matchthe installed version of Tivoli Storage Manager.Re-installation of Tivoli Storage Manager may berequired, or a system reboot may be required tocomplete the installtion.

FMV2254E program-name with session id sessidaborted recall for token token. ERRNOerrno : errno-text was set. See messageexplanation.

Explanation: A recall was aborted from HSM. TheERRNO set from HSM explains why the recall wasaborted. Transient errors (The operation must be retriedafter the associated problem was solved): ENOSPC : Nospace left on device. HSM couldn't free space for therecall. ENOMEM : Not enough memory available toacquire the required resocurces for the recall. ESRCH :The internal communication between master anddistributor failed. EACCES : Most common errno. Oneof the failures below: - The recall daemon are exiting.System cleanup ongoing. - Recovery of previouslyfailed nodes is ongoing. - File is immutable and can'tbe opened for write / truncate. - The HSM internalprocessing failed due to issues with the DMAPI.EBUSY : HSM can't acquire exclusive rights on the file.EFAULT : The system detected an invalid address inattempting to use an argument. EINTR : The DMAPIimplementation allows interruption and the processwas interrupted. EINVAL : The requested right is notvalid or the session or token is not valid or token wasDM_NO_TOKEN. Static errors (The operation can't befullfilled. Recall not possible): EIO : The stub file isorphan. ENOENT : The file doesn't exist in the filesystem. EBADF : The file handle does not refer to anexisting or accessible object.

System action: The recall request was aborted fromthe HSM service.

User response: Transient errors: Solve problemindicated from the errno. On GPFS platforms: Usecommand dsmmigfs q -d -n=all to verify HSM andGPFS are running properly. Retry the recall operation if



failed file can be identified. Enable HSM Logging iffailed failed file cannot be identified and wait for newoccurrence. (HSM Logging allows you to map betweenthe token displayed from the FMV message and therecalled file) Static errors: Restore the file from backup.

FMV2260E Failed to lock Tivoli Storage Managerpassword file.

Explanation: In multi-process environment TivoliStorage Manager client locks the password file duringauthentication to avoid conflicts on updating passwordin case the currect password is expired.

System action: processing stops

User response: Try to use MAXRETRIESLOCK testflag to increase number of attempts to lock the file. Thedefault value is 1500.

FMV2261E TSM client failed to lock options file.

Explanation: In multi-process environment TivoliStorage Manager client locks the options file duringinitialization to avoid conflicts on reading or adding anoption.

System action: processing continue

User response: Try to decrease a number of TSMclient processes

FMV2309I Single Sign On login to the vSphereServer failed in function function. APImessage A credential login is nowattempted.

Explanation: The Single Sign On (SSO) login to thevSphere Server failed. Possible reasons for this failureinclude the following situations:

v A time difference exists between the vSphere Serverclock and the client clock that exceeds 10 minutes.

v The SSO server accesses a non-default port. Thisissue can occur when the SSO server is installed onthe same system as the VMware vCenter.

System action: The system attempts a credential loginas a result of the SSO login failure.

User response: Check the dsmerror.log file for detailsabout why the SSO login attempt failed. Then, take anycorrective action, if needed.

FMV2310E The create snapshot task is disabled onthe virtual machine 'VM-name'. As aresult, the virtual machine cannot bebacked up.

Explanation: Virtual machines that are managed orreplicated by another application disable the createsnapshot task. The vSphere client or anotherapplication disabled the create snapshot task on this

virtual machine. As a result, this virtual machinecannot be backed up.

System action: The backup operation skips the virtualmachine with the disabled create snapshot task andcontinues processing the remaining virtual machines.


FMV2311E The create snapshot task is disabled onthe virtual machine. As a result, thevirtual machine cannot be backed up.

Explanation: Virtual machines that are managed orreplicated by another application disable the createsnapshot task. The vSphere client or anotherapplication disabled the create snapshot task on thisvirtual machine. As a result, this virtual machinecannot be backed up.

System action: The backup operation skips the virtualmachine with the disabled create snapshot task andcontinues processing the remaining virtual machines.


FMV2312E -DELTYPE=ALL is not allowed forDELETE BACKUP -OBJTYPE=VM.

Explanation: DELTYPE=ALL is not a valid optionvalue when deleting VM backup objects.

System action: The command is not executed.

User response: If you wish to delete all backups for aVM node, use the DELETE FILESPACE command.

FMV2313E -FILELIST is not allowed for DELETEBACKUP or EXPIRE when-OBJTYPE=VM.

Explanation: -filelist is not a valid option value whendeleting or expiring VM backup objects.


User response: If you wish to delete or expire allbackups for a VM node, use the DELETE FILESPACEcommand.

FMV2314E No VM backup exists for VM-Name.

Explanation: The Tivoli Storage Manager server hasno record of a VM backup for the VM name provided.The backup might have been deleted, or the VM namespelled incorrectly.


User response: If spelling is the problem, correct itand resubmit the command.



FMV2315E -PICK is not allowed for EXPIRE when-OBJTYPE=VM.

Explanation: -pick is not a valid option value whenexpiring VM backup objects.


User response: If you wish to expire all VM nodes,use the DELETE FILESPACE command.

FMV2316E Wildcards are not allowed in the VMname argument.

Explanation: When expiring or deleting a VM backup,the VM name must be specified exactly. The EXPIRE-OBJTYPE=VM command processes only one backupon each invocation. When -INACTIVE is present theDELETE BACKUP -OBJTYPE=VM command displaysall versions of a single VM backup in a list from whichto choose. If -INACTIVE is not present, this commandexpires the current active VM backup.


User response: Specify only one VM name withoutwild cards. It may be in upper or lower case.

FMV2317E Deletion of VM object VMname failed.Reason:

Explanation: The transaction which deletes the namedVM object failed at the server. The reason code ....?????

System action: The deletion is skipped and processingcontinues with the next selection, if any.

User response: Consult the error log for specificreasons for this failure.

FMV2318E Command with -OBJTYPE=VM requiresexactly one non-option argument

Explanation: This command accepts only a single VMname as an argument. Either no arguments wereentered or more than one appeared on the commandline.


User response: Specify only one VM name withoutwild cards. It may be in upper or lower case.

FMV2319W DELETE BACKUP -OBJTYPE=VMfinished with failures.

Explanation: One or more deletions failed.

System action: The VM backups which failed havebeen reported in previous messages. Processingcontinues with the next selection, if any.

User response: Consult the previous error messagesfor the cause of each failure.

FMV2320I DELETE BACKUP -OBJTYPE=VMfinished without failures.

Explanation: All VM backups selected for deletionwere deleted.

System action: Control returns to the command line.

User response: No action is required, this message isinformational.

FMV2321W EXPIRE with -OBJTYPE=VM finishedwith failures.

Explanation: The command did not complete, noobjects were expired.

System action: The VM expire which failed has beenreported in previous messages.

User response: Consult the previous error messagesfor the cause of the failure.

FMV2322I EXPIRE with -OBJTYPE=VM finishedwithout failures.

Explanation: The EXPIRE command executedsuccessfully.

System action: Control returns to the command line.

User response: No action is required, this message isinformational.

FMV2323E The user ID and password for VMwarevCloud Director 'vCD host name' are notset.

Explanation: The user ID and password for VMwarevCloud Director could not be read from encryptedpassword file.


User response: Issue the dsmc SET PASSWORD-type=VCD 'vCloud Director hostname' 'userid''password' command to save an encrypted password.

FMV2324W WARNING: The VMware vCloudDirector user ID <hostuserid> read fromthe password file is different from theVCDUser option value <vmcuserid>.Using stored value.

Explanation: All user IDs that are specified in theTSM.PWD file and in the VCDUSER option must bethe same.


User response: Contact the Tivoli Storage Manageradministrator with the information that is provided inthis message.



FMV2325E Error Accessing Snapshot DifferentialChange Log for filer '' volume '', seeclient error log for more information.

Explanation: The Snapshot Differential Change Logneeded needed to backup the specified filer volumecould not be accessed

System action: The backup of the specified volumefails.

User response: Ensure that the client staging directorywhere change logs are located is accessible.

FMV2326W Corrupt Snapshot Differential ChangeLog detected, change log will be resetand a full progressive incremental willbe performed.

Explanation: A corrupt snapshot differential changelog for the filer volume being backed up was detected.

System action: The change log will be reset and a fullprogressive incremental with a new base snapshot willbe performed.


FMV2327I Creating Snapshot Differential ChangeLog.

Explanation: A new snapshot differential change logwas created.



FMV2328I Using Snapshot Differential ChangeLog.

Explanation: A snapshot differential change log isbeing used for the backup.



FMV2329W Down level Snapshot DifferentialChange Log detected, Change Log willbe reset and a full progressiveincremental will be performed.

Explanation: none.

System action: none.


FMV2330E Failed to unfreeze the VSS writersbecause the snapshot time exceeded the10 second timeout limitation.

Explanation: Microsoft VSS has a 10 second timeoutlimitation between freeze and thaw events for VSSwriters on a VM. When the snapshot time exceeds the10 second timeout limit, the VSS writers return to a'failed' state. This failed state occurs because the VSSprovider did not thaw the VSS writers within theallowed time.


User response: Check the event log. Ensure that thewriters on the guest VM are in 'stable' state beforetrying an application protection VM backup operationagain. A snapshot operation must be completed within10 seconds.

FMV2331W No match found on the server for theHyper-V VM name or VMList 'string'entered

Explanation: No match found on the server for theHyper-V VM name or VMList parameter entered.


User response: Specify another Hyper-V VM name orVMList parameter that exists on the server.

FMV2332E Failed to log on to the vCloud Director.Authentication failed.

Explanation: The vCloud credentials were rejected bythe vCloud Director.


User response: Update username and password forthe vCloud Director.

FMV2333E Failed to establish connection to thevCloud Director.

Explanation: A connection cannot be established tothe vCloud Director on the host that is specified by theVCDHost and VCDPort options.


User response: Verify that the values of the VCDHOstand VCDPort options are valid, network connectivity tothe host exists, and that the vCloud Director service isrunning.

FMV2334E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. Unable to connect to theHyper-V namespace. Confirm thatHyper-V is installed on the backupnode.



Explanation: The Windows ManagementInstrumentation (WMI) namespace"root\virtualization\v2" for Hyper-V could not befound. This namespace is installed with Hyper-V. IfHyper-V is installed, Hyper-V is not in a good state.

System action: Creating a connection to the Hyper-VWMI provider.

User response: Check that Hyper-V is installed. IfHyper-V is not installed, install Hyper-V beforeattempting this operation again.

FMV2335E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. The WMI service is in theshutting down or shutdown state.Restart the service and try again.

Explanation: The Windows ManagementInstrumentation (WMI) service has received a requestto shutdown or has been shutdown due to an externalerror. An internal operation which requires WMI hasbeen attempted and failed. The requested operation isunavailable while WMI is shutdown.

All Hyper-V operations require the WindowsManagement Instrumentation service.

System action: An internal Tivoli Storage Manageroperation involving Windows ManagementInstrumentation has occurred.

User response: Restart the Windows ManagementInstrumentation service.

FMV2336W Tivoli Storage Manager has detectedthat the following Hyper-V virtualmachine "virtual_machines" has aninterrupted incremental backup chain.Performing a full backup on thespecified Hyper-V virtual machine.

Explanation: The last operation of the virtual machinewas a restore; or an unknown party has performedincremental backup operations on the listed virtualmachine. To prevent backup corruption a full backupwill be performed instead.

System action: Tivoli Storage Manager has detectedthat a virtual machine has an interrupted incrementalbackup chains.

User response: A full backup is performed instead ofan incremental.

FMV2337E Tivoli Storage Manager was unable totake cluster resource 'resourcename'offline. The current operation requiresthe resource to be offline. Turning thecluster resource off failed with rc=rc.

Explanation: The cluster resource was not taken

offline within the time limit or an attempt was made totake offline a failed cluster resource.


User response: Check that the cluster resource is notin a failed state. Verify that the cluster resource can betaken offline.

FMV2338W Tivoli Storage Manager has detected arequest to backup a virtual machinereplica. The state of the replica'vmreplicaname', ID='vmid' may differfrom the original virtual machine. If thenames of the original virtual machineand the replica are identical the samefilespace will be used. The data maybecome unrecoverable because the stateof the original virtual machine and thereplica may differ.

Explanation: Backups of an original virtual machineand their replica overwrite each other as their nameand ID are usually identical. Virtual machine replicasare taken in definite time intervals. Between theseintervals the data on the original and the replica maydiffer. In some occasions the difference may cause datacorruption if a backup of the original is followed by abackup of the replica.

System action: A backup request of a virtual machinereplica is being processed.

User response: Configure IBM Tivoli Storage Managerto back up only the original virtual machine or thereplica. Alternatively, one can change the name of thereplica compared to the original virtual machine; andthe replica will back up to a separate filespace.

FMV2339W The Hyper-V VM 'vmname' is in a"branch" state compared to the lastbackup. Incremental Forever -Incremental backup cannot beperformed. An Incremental Forever -Full backup will be performed instead.

Explanation: The VM state is in a "branch" comparedto the last backup. This causes a fallback to IncrementalForever - Full as backup consistency in this state is notguaranteed.

System action: An Incremental Forever - Full backupwill be performed.


FMV2340W The target virtual machine 'VM-name'exists, use the REPLACE option tooverwrite.

Explanation: The specified target VM exists and theuser specified not to allow restore to replace existingmachines.



System action: The virtual machine is not restored.

User response: Specify a different virtual machine as arestore target or specify that existing virtual machinescan be replaced.

FMV2341E The target virtual machine 'VM-name'cannot be restored: The guid differsfrom the backup copy.

Explanation: The specified target VM exists and has adifferent guid than the virtual machine was backed upwith..


User response: Specify a different virtual machine as arestore target or delete the specified target virtualmachine.

FMV2342E The specified restore target 'VM-name' isambiguous: Multiple virtual machineswith the same name exist.

Explanation: The specifed restore target is ambiguous,multiple virtual machine with the same name exist.


User response: Specify a different virtual machine as arestore target.

FMV2343E A snapshot of Virtual machine 'vmname'cannot be taken because a physical diskattached.

Explanation: The Volume Snapshot Service (VSS) isunable to snapshot a virtual machine with a physicaldisk.

System action: The full backup of the the virtualmachine finished with failures. The next virtualmachine in the backup will be processed.

User response: Do not include this virtual machine indomain.vmfull for backup. A snapshot of this virtualmachine cannot be taken.

FMV2344E 'drive-name1' is a disk witness.

Explanation: The indicated volume is a disk witness.Because the CLUSTERNODE option is set to YES, thevolume cannot be backed up or archived.



FMV2345W The virtual machine named '' was foundto have an old snapshot ''. A commandwas sent to the vCenter to remove it.

Explanation: During the snapshot clean-up process thebackup-archive client found old snapshots on thevirtual machine. A remove snapshot command was sentto the VMware vCenter to remove the old snapshots.


User response: Confirm that the the virtual machine isfree of all snapshots before the next scheduled backup.

FMV2346E Expiration of VM object VMname failed.Reason:

Explanation: The transaction which expires the namedVM object failed at the server. The reason code ....?????

System action: The expiration is not completed.

User response: Consult the error log for specificreasons for this failure.

FMV2347E IBM Tivoli Storage Manager applicationprotection cannot be used. The correctJava Runtime Environment version hasnot been detected on machine. A JavaRuntime Environment version or higheris required to run this program. If youhave already installed this level of Javaversion on this machine, please ensurethat the correct Java executable is onyour PATH and start the program again.

Explanation: IBM Tivoli Storage Manager applicationprotection vm backup cannot be started because theJava runtime environment does not meet therequirements.


User response: Verify that the correct java executableis on your PATH or install the required version of Javaruntime environment and run the backup again.

FMV2348E Mount proxy host 'remoteversion' doesnot have a supported operating system.

Explanation: The mount proxy node needs to beconfigured on a supported operating system.


User response: Check the documentation for a list ofsupported operating systems. Configure the mountproxy node on a supported operating system.



FMV2349W The virtual machine named '' was foundto need snapshot consolidation. Acommand was sent to the VMwarevCenter to perform consolidation.

Explanation: During the virtual machine backupprocess the backup-archive client found the virtualmachine needed snapshot consolidation. A commandwas sent to the VMware vCenter to performconsolidation.


User response: Confirm that the virtual machine isclean of all snapshots and snapshot delta files beforethe next scheduled backup.

FMV2350E Virtual machine 'VM name' will not bebacked up because it contains at leastone of the following unsupportedspecial characters \ / : ; , * ? " ' < > |

Explanation: The specified virtual machine containscharacters that are not supported for virtual machinebackup and restore operations.

System action: The backup for the specified virtualmachine fails.

User response: Rename the virtual machine so that itdoes not contain any of the specified special characters.

FMV2351E Duplicate virtual machine name'vmname' was detected in the samebackup operation. Backups of a virtualmachine can not continue without aunique object name.

Explanation: The backup of the virtual machine failedbecause no unique object name is available.

System action: The backup for the specified virtualmachine fails. The next virtual machine to back up willbe processed.

User response: Rename the virtual machine so that itis unique among virtual machines for the node.

FMV2352E Validation of virtual machine 'vmname'configuration returned the followingmessage from Hyper-V: hypervmessageThis message indicated that the virtualmachine could not be restored until themessage from Hyper-V is addressed.

Explanation: When validating the virtual machinewith Hyper-V a message was returned that preventsthe virtual machine restore from continuing.

System action: Cannot continue with restore until theissue is resolved.

User response: Resolve the issue outlined by themessage.

FMV2398I The virtual machine 'VM-name' isconfigured as a VMware Site RecoveryManager placeholder virtual machine onthe recovery site. As a result, the virtualmachine will be skipped.

Explanation: VMware Site Recovery Manager createsplaceholder virtual machines that have no virtual diskdata. As a result, these virtual machines cannot bebacked up.

System action: The backup operation skips theplaceholder virtual machine and continues processingthe remaining virtual machines.

User response: None

FMV2399I The virtual machine is configured as aVMware Site Recovery Managerplaceholder virtual machine on therecovery site. As a result, the virtualmachine will be skipped.

Explanation: VMware Site Recovery Manager createsplaceholder virtual machines that have no virtual diskdata. As a result, these virtual machines cannot bebacked up.

System action: The backup operation skips theplaceholder virtual machine and continues processingthe remaining virtual machines.

User response: None

FMV2408I The virtual machine named 'VMNAME'is ready for Instant Access

Explanation: The Instant Access operation for thespecified virtual machine successfully completed.


User response: None

FMV2409E The Instant Restore type was notidentified.

Explanation: The client encountered a connectionerror when querying the Tivoli Storage Manager serverfor Instant Restore and Access information.


User response: Verify that the client is connected tothe server. Then run the operation again. Check withthe command QUERY SESSION what is the cause forthe connection issue. Also check the dsmerror.log foradditional information



FMV2410E Instant Restore information for thespecified virtual machines was notfound.

Explanation: The Tivoli Storage Manager server doesnot contain Instant Restore information for the specifiedvirtual machines. Or, the virtual machines werespecified incorrectly.


User response: Issue the QUERY VM *-VMRESTORETYPE=ALLTYPE command. Thiscommand queries all active Instant Access, Restore, andDisk sessions available on the Tivoli Storage Managerserver.

FMV2411E Instant Restore/Access of virtualmachine 'vmname' failed with rc =return-code

Explanation: An error happened during processing ofan Instant Restore or Access. See previous output whathappens exactly.


User response: Check the error log for informationabout how to resolve this error.

FMV2412E IBM Tivoli Storage Manager RecoveryAgent is not installed.

Explanation: IBM Tivoli Storage Manager RecoveryAgent is not installed.


User response: Ensure that IBM Tivoli StorageManager Recovery Agent is correctly installed andconfigured.

FMV2413E Cannot find the Recovery Agent shellcommand in the expected installationpath. Ensure that Tivoli StorageManager for VE is correctly installedand configured.

Explanation: The Recovery Agent shell command wasnot found in the expected installation path.


User response: Ensure that Tivoli Storage Manager forVE is correctly installed and configured.

FMV2414E An error occurred when the hostnamefor the local machine was called.

Explanation: The system call gethostname failed.


User response: Verify that the configuration of thenetwork interface is correct.

FMV2415E An error occurred when the machineaddress information was called.

Explanation: The system call getaddrinfo failed.



FMV2416E An error occurred when the machinename information was called.

Explanation: The system call getnameinfo failed.



FMV2417E Unexpected communication method.Only TCP and TCPv6 are accepted.

Explanation: An unexpected communication methodwas detected.


User response: Verify that the communication methodfor Tivoli Storage Manager is correct. Use either TCP orTCPv6.

FMV2418E Unable to read or write to the localinstant restore data. filename File cannotbe accessed or is damaged.

Explanation: Instant access and instant restoreoperations require read/write access on the local datamover to store data.


User response: To store the instant restore restoredata, the data mover application requires read andwrite access to the C:\Documents andSettings\AllUsers\Application Data\Tivoli\TSM\ orC:\ProgramData\Tivoli\TSM folder. Set the accessrights to this directory so that your user has the correctrights. If the file was damaged it can be helpfull toreplace the current version with the .bak file.

FMV2419E The datastore does not have enough freespace for the instant restore operation.

Explanation: The space on the selected datastore is notsufficient for the instant restore operation.


User response: Increase the datastore space or choosea different datastore.



FMV2420E Cannot detect storage deviceinformation.

Explanation: Storage device information cannot beretrieved.


User response: Ensure that the communication withthe ESX host is working. Also, review the log messageson the ESX host.

FMV2421E Cannot detect the iSCSI initiator on theESXi host.

Explanation: The iSCSI initiator name of the ESXi hostcannot be detected.



FMV2422E Cannot detect the iSCSI Host BusAdapter.

Explanation: The iSCSI adapter was not detected.



FMV2424E Cannot find the ESX host 'ESXHOST' inthe vCenter.

Explanation: The specified ESX host cannot be foundin the vCenter.


User response: Ensure that the specified ESX host is inthe vCenter. Ensure that the name of the ESX host iscorrect. Alternatively, specify another ESX host.

FMV2425E Cannot connect to the ESX host'ESXHOST'

Explanation: A connection to the specified ESX hostcannot be made


User response: Ensure that the specified ESX host isconnected to the vCenter and the network.Alternatively, specify another ESX host.

FMV2426E The ESX host 'ESXHOST' is not poweredon.

Explanation: The specified ESX host is not poweredon.


User response: Turn on the power to the ESX host.Alternatively, specify another ESX host.

FMV2427E The ESX host 'ESXHOST' is inmaintenance mode.

Explanation: The specified ESX host is in maintenancemode. A connection cannot be made to this host.


User response: Change the ESX host back to normalmode and try again. Alternatively, specify another ESXhost.

FMV2428E The ESX host 'ESXHOST' is notconnected.

Explanation: The specified ESX host is not connectedin the vCenter.


User response: Connect the ESX host in the vCenterand try again. Alternatively, specify another ESX host.

FMV2430E Cannot find the datacenter'DATACENTER'.

Explanation: The specified Datacenter cannot befound in the vCenter.


User response: Ensure that the specified datacenter isin the vCenter. Alternatively, specify another datacenter.

FMV2431E Cannot find the temporary datastore'TEMPDATASTORE' on the ESX host'ESXHOST'.

Explanation: The specified temporary datastore cannotbe found on the specified ESX host.


User response: Ensure that the specified datastore ison the ESX host. Alternatively, specify anotherdatastore.

FMV2432E The temporary datastore'TEMPDATASTORE' is the same as thetarget datastore 'DATASTORE'.

Explanation: The specified temporary datastore mustbe a different datastore than the one where the machineis restored to. You must specify two different datastoresfor Storage vMotion to work.


User response: Specify another datastore as atemporary datastore.



FMV2433E The '-vmtempdatastore' option must bespecified for an instant restoreoperation.

Explanation: You must specify two differentdatastores for Storage vMotion to work. Use the'-vmtempdatastore' option to specify a temporarydatastore.


User response: Specify a temporary datastore.

FMV2434E The datastore 'DATASTORE' was notfound on the host 'ESXHOST'.

Explanation: The specified datastore cannot be foundon the ESX host.


User response: Ensure that the specified datastore ison the ESX host. Alternatively, specify anotherdatastore.

FMV2444E Cannot find the datacenter for host'ESXHOST'.

Explanation: Unable to determine the datacenterwhere the ESX host is located.


User response: Check that the vCenter of the ESX hostis in a datacenter and that the user has the properauthority to access this information.

FMV2445E Virtual machine 'VM' is running. Youcannot delete this VM.

Explanation: You cannot delete a virtual machine thatis running.


User response: Ensure that you have the properauthority to power off virtual machines, then power offand delete the VM.

FMV2447E Failed to delete VM 'VM' from the ESXhost.

Explanation: You cannot delete the virtual machineform the ESX host.


User response: Ensure that you have the properauthority to delete virtual machines, then delete theVM.

FMV2448E Mount command failed. Command wasCOMMAND Shell command returned:RESULT

Explanation: The TDP mount command was notsuccessful.


User response: Determine the problem from theinformation that was returned for the TDP mountcommand. Resolve the problem, then run the commandagain.

FMV2452E num_discovered iSCSI devices werediscovered on the ESX host, whilenum_mounted were expected.

Explanation: After the ESX host bus adapter wasscanned, the number of devices that were discovered isdifferent from the number of mounted devices.

System action: The Instant Restore or Instant Accessprocess is stopped.

User response: Verify that the Tivoli Storage Managermount is configured to use the correct ESX host IP. Toclean the environment, you must run the cleanupprocess.

FMV2453E An error occurred when the host busadapter was scanned.

Explanation: An error occurred when the ESX hostbus adapter was scanned.

System action: The Instant Restore, Instant Access, orcleanup process is stopped.

User response: Run the cleanup process after you fixany problems with the ESX host bus adapter.

FMV2454E An error occurred when the iSCSI targettarget_name was disconnected from theESX host bus adapter.

Explanation: An error occurred when a specific iSCSItarget was disconnected from the ESX host bus adapter.

System action: The cleanup operation is stopped.

User response: Run the cleanup process after you fixany problems with the ESX host bus adapter.

FMV2455I The virtual machine has been started.You can use the machine after it hasbooted, or you can connect to it andmanage its settings through the vCenterconsole.

Explanation: The virtual machine is being started.


User response: While the boot is in progress, you can



connect to the virtual machine and view or manageBIOS settings, manage the bootloader options, orperform other tasks. After the boot process completes,you can use the virtual machine and its applicationsand resources.

FMV2462E Unable to start the vMotion task forvirtual machine 'vm_name'.

Explanation: An instant restore of the specified virtualmachine was attempted but failed. The client could notstart a vMotion task to migrate the virtual machine.

System action: The Instant Restore operation stops.

User response: Examine the client dsmerror.log file tosee if a log entry indicates why the vMotion task failed.Additional information about the failure might also beavailable in the vCenter server, on the Task and Eventstab for the ESXi host that you were migrating the VMfrom. If possible, use the log and event records todetermine what caused the vMotion task to fail and fixit. Then, clean up the virtual machine (use the RestoreVM command with the -VMRESToretype=VMCLeanupoption) and restart the vMotion task. If you cannotrestart the task, suspend the virtual machine and usethe vSphere web client to start the virtual machinemigration from one host to another.

FMV2463W Instant Restore information cannot besaved on the server.

Explanation: An error occurred when Instant Restoreinformation was being saved on the server. The InstantRestore process is still running.


User response: The client dsmerror.log file mightcontain information to help troubleshoot the reason forthis error. Let the Instant Restore process complete onits own. You might need to run a clean up operation onthe virtual machine. Use the Restore VM command,and specify the -VMRESToretype=VMCLeanup option.

FMV2464E Unable to delete Instant Restoreinformation from the server.

Explanation: An error occurred while attempting todelete Instant Restore information from the server.

System action: The Instant Restore operationcontinues.

User response: The most likely reason for this error isthat an FMV2463W warning previously occurred, andthere is no data to delete. If you have not previouslyseen an FMV2463W message, the client dsmerror.logfile might contain information to help you troubleshootthis error. Clean up the virtual machine to remove oldinformation from the server. Use the Restore VMcommand, and specify the-VMRESToretype=VMCLeanup option.

FMV2465E An error occurred during a storagevMotion operation.

Explanation: A storage vMotion task failed whiletrying to migrate a running virtual machine.

System action: The Instant Restore operation stops.

User response: Examine the client dsmerror.log file tosee if a log entry indicates why the vMotion task failed.Additional information about the failure might also beavailable in the vCenter server, on the Task and Eventstab for the ESXi host that you were migrating the VMfrom. If possible, use the log and event records todetermine what caused the vMotion task to fail and fixit. Then clean up the virtual machine (use the RestoreVM command with the -VMRESToretype=VMCLeanupoption) and restart the vMotion task. If you cannotrestart the task, suspend the virtual machine and usethe vSphere web client to start the VM migration fromone host to another.

FMV2466W If you continue you will lose all datacreated on this virtual machine. Thevirtual machine will also be removedfrom the ESXi host. Are you sure thatyou want to do this? Press Y the virtualmachine data and remove it from theESXi host. Press any other key tocontinue without deleting data or theVM.

Explanation: You are performing an operation that, ifallowed to continue, will delete all data that wascreated after this virtual machine was created.

System action: If Y is pressed, the Instant Restoreoperation is stopped, and a cleanup operation isperformed

User response: Respond to the prompt. Press Y todestroy all data and delete the virtual machine from theserver. Press any other key to continue withoutdeleting.

FMV2467W Unable to delete the snapshot that wascreated for the virtual machine named'vm_name'

Explanation: When a virtual machine is restored by aninstant restore operation, a snapshot is created to storeall data that were written to the virtual machine disks.When the restore is completed, the ESXi host deletesthe snapshot. The snapshot for the specified virtualmachine could not be deleted.


User response: Examine the vSphere log to determinewhy is it not possible to delete the snapshot andresolve the problems that prevent the deletion. Then,delete the snapshot by using the snapshot manager.



FMV2468E The necessary iSCSI targets could notbe found on the ESX host.

Explanation: An instant restore operation wasinitiated and one or more of the required iSCSI targetscould not be found on the ESXi host.


User response: Verify that the IP address that wasspecified with the -VMISCSISERVERADDRESSparameter is correct.

FMV2469E Unable to remove the iSCSI target.

Explanation: An error occurred while trying toremove an iSCSI target.


User response: Check vSphere client log file for thereason this operation failed and remove the iSCSItarget. To remove the failed iSCSI static targets go toyour ESXi host Configuration -> Storage Adapters ->Select the iSCSI Adapter -> right click on it -> ClickProperties -> Static Discovery and select the failediSCSI targets and remove them.

FMV2471E Unable to stop the vMotion Task 'task'.

Explanation: The specified vMotion task could not bestopped.

System action: The instant restore operation isstopped.

User response: Examine the vSphere log to determinewhy the migration cannot be stopped. Resolve theproblem and cancel the vMotion task. Then, use the-VMRESToretype=VMFULLCleanup option on theRestore VM command to remove any files or otherresources that were created by the instant restoreoperation.

FMV2472E Cannot detect the LUN for the attachedRDM devices for virtual machine namedvmname'. The restore operation for thisvirtual machine cannot be completed.

Explanation: The LUNs for the RDM devices use bythe specified virtual machine are either missing, aremapped to an other machine, or the device name andthe LUN do not match.

System action: The restore operation is stopped.

User response: For restore operations wherevmrestoretype=instantrestore orvmrestoretype=instantaccess, verify that the iSCSIserver address and the VMkernel port binding match.Verify this information by checking the followingthings: 1. Check the Data Protection for VMwareconfiguration file TDPVMwareMounter.conf and verifythat the iSCSI server address is bound to the correct

network card and segment. 2. Use the vSphere client toconnect to your ESXi host. In vSphere, selectConfiguration->Storage Adapters to display a list of theiSCSI adapters. Right click the adapter that you areverifying. Then, select Properties ->NetworkConfiguration. In the VMkernel Port Bindings Detailsoutput, verify that the VMkernel Adapter is on thesame subnet that the datamover node is on.

FMV2473E Unable to create a Snapshot of thevirtual machine named 'vm_name'.

Explanation: An instant restore operation wasattempted for the specified virtual machine. Thesnapshot that is used to restore the virtual machinecould not be created.

System action: The instant restore operation stops.

User response: Examine the vCenter logs to determinewhy the snapshot could not be created and try theinstant restore operation again.

FMV2474E Unable to cleanup after an instantrestore operation for the virtual machinenamed 'vm_name', because vMotion taskis still running.

Explanation: An instant restore operation is stillrunning for the specified virtual machine.

System action: The cleanuop operation stops.

User response: Use the query command to check onthe status of the instant restore operation. Examine thevCenter to determine the status of the vMotion task. Ifyou want to stop the instant restore, cancel theoperation in the DP VMware GUI or stop the vMotiontask from the vCenter interface. Then, start the cleanupoperation again.

FMV2476E A restore location must be specified viathe TARGETPATH option whenrestoring to a different virtual machinename.

Explanation: A restore location must be specifed viathe TARGETPATH option when restoring to a differentvirtual machine name specified by the VMNAMEoption.


User response: Specify a restore location with theTARGETPATH option.

FMV2484I Virtual Machine 'vm_name' wassuccessfully restored

Explanation: The Virtual Machine was successfullyrestored.




User response: None

FMV2485E Cannot query the Tivoli StorageManager server to get instant accessinformation

Explanation: The server did not respond to the queryfor instant access information.

System action: The virtual machine cleanup operationis halted.

User response: Examine the dsmerror.log file and theTivoli Storage Manager server activity logs todetermine the cause of this error.

FMV2488E Error mounting the iSCSI device.

Explanation: An error occurred while trying to mountthe iSCSI device. Check the dsmerror.log file todetermine the cause of this error.



FMV2490E Could not turn off the VM that isnamed 'VM' .

Explanation: The specified virtual machine could notbe powered off. This prevents attempts to clean up theresources that were created to restore the virtualmachine.

System action: The restore operation was stopped.

User response: Turn off the virtual machine and thendelete it using the vSphere web client.

FMV2513I The virtual machine has no disksattached

Explanation: The virtual machine exists, but it doesnot have any disks attached. The machine can becleaned up.


User response: None

FMV2514I Disk status cannot be determined

Explanation: It is not possible to determine the statusof this disk.


User response: Examine the vSphere Client log todetermine what is wrong with the machine. If the logentries do not reveal problems with this virtualmachine, inspect the virtual machine in the vSphereClient to determine why the disk status cannot bedetermined. See the vSphere documentation foradditional guidance, if necessary.

FMV2515I No additional information is availablefor this virtual machine. The virtualmachine was deleted or it has beenrenamed

Explanation: Information about the virtual machinecannot be found on the ESXi host. The virtual machinemight have been previously deleted or renamed.


User response: Use the vSphere Client to determinewhat happened to this virtual machine. If the virtualmachine was renamed, make sure that it is runningwithout errors before you clean up the temporaryresources, by using the Restore VM command with the-VMRESToretype=VMCLEANUP option.

FMV2516E VMware storage vMotion operationfailed. Restart the storage vMotionoperation manually, by using thevSphere web client, to finish the restoreoperation. Refer to the documentation toget details about the manual recoveryprocess.

Explanation: Tivoli Storage Manager Changes to therestored VM might not be permanently saved.

System action: Tivoli Storage Manager Automaticcleanup cannot be performed for the failed vMotionoperation.

User response: Examine the event logs to determinethe cause for the failure. Fix any problems and restartthe storage vMotion operation manually, by using thevSphere web clien, to finish the restore operation. Referto the vMotion documentation to get details about themanual recovery process.

FMV2517E Cannot query the Tivoli StorageManager server to get instant restoreinformation

Explanation: The server did not respond to the queryfor instant restore information.

System action: The virtual machine clean upoperation stops.

User response: Examine the dsmerror.log file and theTivoli Storage Manager server activity logs todetermine the cause of this error.



FMV2519E The disk \"diskname\" is an iSCSIdevice with an inactive path. Poweringoff the virtual machine will cause theESXi server to hang. The clean upoperation has been stopped to preventthis. Use the Query VM command withthe -detail option to obtain detailedstatus information about the virtualmachine. Correct the path so that theiSCSI state is active and then tryrunning the VMFULLCleanup operationagain.

Explanation: A running virtual machine that has aninactive iSCSI device cannot be cleaned up.

System action: The virtual machine full clean up(VMRESTORType=VMFULLCLeanup) operation stops.

User response: For information about troubleshootinginactive iSCSI resources, search the VMware supportpages by using a search string like "troubleshootingiSCSI" or "inactive iSCSI".

FMV2520E The disk \"diskname\" is not a physicaldevice. An instant restore clean up wasstopped because vMotion could notrestore all virtual machine data.. Use theQuery VM command with the -detailoption to obtain information about stateof the specified disk. Use vMotion tomanually migrate the virtual machinedevices and then try the clean upoperation again.

Explanation: An instant restore clean up operation(-VMRESToretype=VMCLeanup) cannot completebecause vMotion could not restore all of the virtualmachine resources.

System action: The virtual machine clean upoperation stops.

User response: Use the VMware documentation todetermine how to use vMotion to migrate the virtualmachine. Then, try the clean up operation again byusing the Restore VM command with the-VMRESToretype=VMCLeanup option. If you do notwant to restore this virtual machine, use the RestoreVM command with the-VMRESTORType=VMFULLCLeanup option to removethe virtual machine and all of its resources.

FMV2521E Instant restore operations require validlicenses for both vMotion and storagevMothion.

Explanation: Instant restore works only when theESXi host has a valid license for both vMotion andstorage vMotion

System action: The instant restore operation isstopped.

User response: Obtain the necessary license fromVMware and assign the license to the ESXi host.

FMV2522W A user canceled the 'operationType'operation .

Explanation: A user canceled the restore/backupoperation .


User response: No response is required.

FMV2523E The virtual machine named vm cannotnot be restored to the sameconfiguration it had when it was backedup. IBM Tivoli Storage Manager willreconfigure the virtual machine toinclude only the most essentialconfiguration information and retry therestore operation.

Explanation: The restore operation failed to restore thevirtual machine to its original configuration. This errorcan occur if there is incompatibility between thehardware that the virtual machine was on when it wasbacked up, and the hardware on the physical hostwhere it was restored. IBM Tivoli Storage Manager willreconfigure the virtual machine to eliminate all butmost necessary configuration information (video andvirtual disks) and retry the restore operation.

System action: The restore operation continues, usingthe reconfigured virtual machine information.

User response: When the restore completes,reconfigure the restored virtual machine to yourrequirements.

FMV2524E An attempt to mount a snapshot of VM'disk' from disk 'vm' failed. The volumemight be mounted from anotheroperation and cannot be remounted.

Explanation: An attempt to mount a snapshot of VM'disk' from disk 'vm' failed. The volume might bemounted from another operation and cannot beremounted. .

System action: The mount operation stops.

User response: Dismount the volume by running amount cleanup operation, then run the mountoperation again.

FMV2525E Unable to power on the created virtualMachine.

Explanation: The vSphere Server is unable to poweron the created virtual machine.

System action: The operation will be rolled back andstopped.



User response: Check the dsmerror.log file for moreinformation. Check the vSphere log to check what errorhappened during virtual machine power on.

FMV2526W TheVM_DONT_QUIESCE_ON_SNAPSHOTtestflag is deprecated for full VMbackups. Use theINCLUDE.VMSNAPSHOTATTEMPTSoption to attempt snapshots with"VMware Tools file system quiescingand application (VSS) quiescingdisabled".

Explanation: TheVM_DONT_QUIESCE_ON_SNAPSHOT testflagoverrides the INCLUDE.VMSNAPSHOTATTEMPTSoption. As a result, all snapshot attempts are withVMware Tools file system quiescing and application(VSS) quiescing disabled.

System action: Use theINCLUDE.VMSNAPSHOTATTEMPTS option to specifysnapshot attempts with VMware Tools file systemquiescing and application (VSS) quiescing disabled.

User response: See theINCLUDE.VMSNAPSHOTATTEMPTS documentationfor information about how to set this option.

FMV2600S Browser trying to establish connectionto client; received socket exception:exception-name

Explanation: The browser received the exceptionexception-name trying to connect to the Tivoli StorageManager client computer.


User response: Validate that the LAN is up and thatyou are trying to connect to the correct port number.

Check error logs for any additional information:dsmerror.log, dsmwebcl.log, or dsmj.log. The defaultlocation of these logs is the installation directory of thebackup-archive client.

Ensure that the command line client runs withoutproblems. Test the command line client with acommand like "dsmc q sess".

FMV2601S Browser trying to establish connectionto client; received unknown hostexception: exception-name

Explanation: The browser received the exceptionexception-name trying to connect to the Tivoli StorageManager client machine.


User response: Retry the operation. If it persists,determine what might be causing this kind of aproblem. Determine if your LAN went down.Determine if you are trying to connect to the correctTivoli Storage Manager client machine.

FMV2602S Browser trying to establish connectionto client; received IO exception:exception-name



User response: Determine what might be causing thiskind of an exception. Retry the problem, and check ifthe LAN is down.

FMV2603S Browser trying to establish connectionto client; received exception:exception-name



User response: Determine what might be causing thiskind of an exception. Determine if the LAN may bedown, or if the Tivoli Storage Manager Client AcceptorDaemon on the Tivoli Storage Manager machine is upand running.

FMV2604S The Web client agent was unable toauthenticate with the server.

Explanation: The Tivoli Storage Manager Web clientagent was unable to authenticate with the TivoliStorage Manager server.


User response: One possible solution is to run thecommand line client so that the client password can bere-entered. Another approach is to check the error logon the Tivoli Storage Manager Web client agent for anyrelevant messages.

FMV2605S Browser could not re-establishconnection to client; received protocolerror.

Explanation: The browser received a protocol errortrying to re-connect to the Tivoli Storage Manager clientmachine.




User response: Determine what might be causing thiskind of an error. Determine if the Tivoli StorageManager browser and the Tivoli Storage Manager clientcode might be out of sync.

FMV2606S An invalid password was sent to theserver.

Explanation: The Tivoli Storage Manager passwordthat was sent to the Tivoli Storage Manager server wasinvalid.


User response: Make sure that you have the correctpassword. Also make sure that it is valid, for exampleit is not too short.

FMV2607S Browser could not establish connectionto client.

Explanation: The Tivoli Storage Manager browsercould not connect to the Tivoli Storage Manager clientmachine.


User response: Determine what might be causing thiskind of a problem. Determine if the LAN is down, or ifthe Tivoli Storage Manager Client Acceptor Daemon onthe Tivoli Storage Manager machine is up and running.

FMV2608S Nothing was selected so no operationwas performed.

Explanation: No object was selected in the GUI for theoperation to be performed upon.


User response: Make sure you select one or moreobjects (volume, directory or file) in the GUI beforeclicking on the operation to be performed.

FMV2609S TCP/IP communications failure betweenthe browser and the client machine.

Explanation: This error can occur due to any of thefollowing:

v The LAN connection to the Tivoli Storage Managerclient machine went down.

v You are trying to connect to the Tivoli StorageManager client machine using the wrong portnumber.

v The Client Acceptor Daemon on the Tivoli StorageManager client machine is not up and running andaccepting connections.


User response: Retry the operation and make sure theLAN is up. Also check that the port number is correct,and that the Client Acceptor Daemon is started andrunning on the Tivoli Storage Manager client machine,and that it is listening on the correct port number.

FMV2610S TCP/IP communications failure betweenthe client and the server machine.

Explanation: An attempt to connect to the serverusing TCP/IP communications failed. This can be aresult of incorrect TCP/IP option settings in your clientoptions file. This error can also occur if the LANconnection went down or if your system administratorcanceled a backup operation.

System action: The Tivoli Storage Manager clientends.

User response: Retry the operation and make sure theLAN is up. Make sure that both the Tivoli StorageManager server and the Tivoli Storage Manager clientare up and running.

FMV2611S An unknown error occurred in thebrowser.

Explanation: An unknown error occurred in theapplet running in the browser.


User response: Retry the operation. If the problempersists, turn on tracing and see if the trace to thebrowser console gives the reason for the error.

FMV2612S An unknown error occurred in the clientPlease check the Tivoli Storage ManagerError Log for any additional information

Explanation: An unknown error occurred in the TivoliStorage Manager client.


User response: Retry the operation. If the problempersists, check the Tivoli Storage Manager Error Log forany additional information.

FMV2613S A communications protocol erroroccurred between the web browser andthe client.

Explanation: None.


User response: Try the operation again. If the problemoccurs again, verify that the Tivoli Storage Managerweb client is installed and configured correctly, andmake sure you are using a supported browser. Flushthe browser cache. Then try the operation again. If the

FMV2606S • FMV2613S


problem persists, enable SERVICE traces on the webclient on the target machine and the Tivoli StorageManager Java applet, then reproduce the problem.Collect the traces and contact IBM for furtherassistance.

FMV2614S A protocol error occurred incommunications between the client andthe server.

Explanation: A protocol error happened between theTivoli Storage Manager client and the Tivoli StorageManager server.


User response: Retry the operation. If the problempersists, check the Tivoli Storage Manager Error Log forany additional information. Verify that you are runningthe correct applet with the appropriate level of theclient.

FMV2615S The user ID entered does not match thenode name configured on the clientmachine.

Explanation: The user ID that was entered is not thesame as the node name on this Tivoli Storage Managerclient.


User response: Verify that the node name entered isconfigured correctly on the Tivoli Storage Managerclient.

FMV2616I The machine must be rebooted for thechanges to take effect

Explanation: The machine must be started for therestored registry changes to take effect.

System action: None

User response: Reboot the machine

FMV2617S The destination directory specified isinvalid.

Explanation: The user specified a destination targetdirectory for restore or retrieve which is invalid.


User response: Retry the operation specifying a validdirectory name.

FMV2619S The Client Acceptor Daemon wasunable to start the Remote Client Agent.

Explanation: The Tivoli Storage Manager ClientAcceptor Daemon could not start the Tivoli StorageManager Remote Client Agent.


User response: Check the error log on the TivoliStorage Manager Web client agent for any relevantmessages. Then correct the problem and retry.

FMV2620W The expand entire branch operation maytake a long time, and cannot be canceledonce it has started. Are you willing towait for the operation to complete?

Explanation: The expand entire branch operationcould take a long time and cannot be canceled once itis started.


User response: Answer 'Yes' to start the expand entirebranch operation. If you answer 'No', the currentoperation will be canceled.

FMV2622S An invalid ID or password submitted.

Explanation: Either the ID is not registered on theTivoli Storage Manager server, or the password for theID is incorrect.


User response: Verify that the ID you are using existson the TSM server to which the remote client nodeconnects. The ID must have sufficient privileges toaccess the remote client node's data. Also make surethat you have the correct password for the ID. If the IDdoes not exist or if the password is unknown, contactyour Tivoli Storage Manager administrator. If the IDdoes not exist, then the Tivoli Storage Manageradministrator can use the REGISTER ADMIN andGRANT AUTHORITY commands to register an ID thatcan access the remote client node's data. If thepassword is unknown, the Tivoli Storage Manageradministrator can use the UPDATE ADMIN commandto reset the password.

FMV2623S Web Client applet level is out of syncwith Web Client agent.

Explanation: The Web Client applet and Web Clientagents are at incompatible levels.


User response: Verify that you have the correct level

FMV2614S • FMV2623S


of the applet installed with the client, and that anincorrect level of the applet was not placed in theinstall directory.

FMV2624E This operation requires client ownerauthority.

Explanation: Your user ID has insufficient authority toperform this operation.

System action: Processing continues, but the user isnot allowed to do this operation.

User response: Do not perform this operation, or get ahigher authority level for your user ID in order toperform this operation.

FMV2625E Node does not support this imageoperation.

Explanation: Node does not support or is notconfigured to perform this image operation.

System action: Processing continues, but the user isnot allowed to do this operation.

User response: Verify whether this image relatedoperation is supported or configured on the targetplatform.

FMV2626E The Include-Exclude statement:ieStatement contains invalid characters.

Explanation: The specified Include-Exclude statementhas invalid characters.

System action: Tivoli Storage Manager will not addthe specified Include-Exclude statement to the list.

User response: Retry the operation with anotherstatement that has valid characters.

FMV2627W The NTFS security attributes for object'full-name' could not be set. Windowssystem error code: error; reason:'error-reason'. Default NTFS securityattributes have been set.

Explanation: Tivoli Storage Manager was unable to setthe NTFS security attributes of the file. The errorinformation captured indicates the reason for thefailure. Default NTFS security attributes have been set.


User response: Check the reason field for the codewhich explains why the NTFS security attributes havenot been set. Correct the condition causing the errorand try the operation again. If the problem persists,contact your system administrator or Tivoli StorageManager administrator for further help.

FMV2628W Failed to create named stream of object'filespace namepath-namefile-name'.

Explanation: Tivoli Storage Manager was unable tocreate named stream.

System action: The named stream is notrestored/retrieved.

User response: The object is restored without namedstream, the object should be examined to verify that itis usable. Check the client error log for FMV5250E errormessage that should have been logged when thismessage was written, take the corrective action and trythe operation again. If the problem persists, contactyour system administrator or Tivoli Storage Manageradministrator for further help.

FMV2629I Migration: The filespace will bemigrated to the Incremental Forevermodel.

Explanation: The first time an Incremental ForeverIncremental (IFIncr) backup is performed against avirtual machine that was previously backed up usingthe Periodic Full model, and the latest backup is anincremental backup, then backup chain will bemigrated to the Incremental Forever model.



FMV2666S Source and/or target volumes areduplicated. The same volume ismounted on more volume paths.

Explanation: This error can occur when a sourcevolume 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 pathto keep track of backup information in its internalbackups database, it cannot back up the same volumewith a duplicate volume path. See addition informationin the error log.

System action: Tivoli Storage Manager cannot selectthe volume.

User response: Delete the last snapshots created asthey are not managed by Tivoli Storage Manager.Unmount the duplicate volume path in order to have asingle mount point to the same source volume. RestartTivoli Storage Manager and retry the operation.

FMV2667I Scan operation was successful.

Explanation: The virtual machine was scannedsuccessfully.

System action: The scan process stops for the virtualmachine. The next virtual machine in the data centerwill be processed.



User response: None

FMV2668E Scan operation failed with anunexpected error.

Explanation: An unexpected error occurred duringguest scan operations.


User response: Check the client error log foradditional information.

FMV2669I Guest operating system platform is notsupported.

Explanation: The operating system of the virtualmachine was not supported by the scan operation.


User response: None

FMV2670I Remote directory in guest is being usedby another application.

Explanation: The scan operation was unable to copyfiles to the remote directory because the directory is inuse by another application.


User response: Ensure that the remote directory isunlocked. Then, reschedule the scan operation.

FMV2671I Virtual machine name was not found onthe VMware server.

Explanation: None


User response: None

FMV2672W Hostname could not be found for thespecified virtual machine name.

Explanation: This issue might be caused by the virtualmachine not running and not having a static IPaddress.


User response: Make sure the guest is properlyconfigured. Then, reschedule the scan operation.

FMV2673I Duplicate virtual machine name wasdetected.

Explanation: None


User response: None

FMV2674I The virtual machine is not connected toESX server.

Explanation: None


User response: None

FMV2675E Proxy Rejected: Proxy authority has notbeen granted to the specified datamover node.

Explanation: The scan of the virtual machine failed.



FMV2676W The guest operating system credentialwas not found.

Explanation: The guest scan operation requires a validoperating system credential.


User response: Ensure the guest operating systemcredential is set. Then, reschedule the scan operation.

FMV2677W The guest operating system credential isinvalid.

Explanation: The guest scan operation requires a validoperating system credential.


User response: Ensure a valid guest operating systemcredential is set. Then, reschedule the scan operation.



FMV2678I Guest machine is powered off.

Explanation: None


User response: None

FMV2679I VMware Tools on the guest machine isnot running.

Explanation: None


User response: None

FMV2680I VMware Tools version on the guestmachine is not current.

Explanation: None


User response: None

FMV2681W ESX host or vCenter version is notsupported.

Explanation: The ESX host or vCenter is a down levelversion.


User response: Refer to the product documentationfor supported ESX and vCenter versions.

FMV2682I The guest credential has insufficientpermissions.

Explanation: None


User response: None

FMV2683W Cannot communicate with the remotehost.

Explanation: This communication issue is caused bynetwork errors or by the host not responding.


User response: Ensure that the network and hostconnection are configured correctly. Then, reschedulethe scan operation.

FMV2684I The guest operation agent could not becontacted.

Explanation: None


User response: None

FMV2685I The VM is a template.

Explanation: VM templates are not supported by thescan operation.


User response: None

FMV2686E VM scan initialization error.

Explanation: The vm scan operation encountered anerror during initialization.


User response: Check the client error log and trace foradditional information.

FMV2687W The virtual machine 'VM-name' containsone or more disks that exceed themaximum size limit. Specify the'-VMSKIPMAXVMDKS=yes' option toexclude these disks from the backup.



User response: Specify the'-VMSKIPMAXVMDKS=yes' option to exclude thesedisks from the backup.

FMV2688E The restore of a Hyper-V virtualmachine that was backed up usingincremental forever backup is notallowed on a Windows 2008 or Windows2008 R2 host. The restore operation mustbe completed on a Windows 2012 orlater Hyper-V host

Explanation: A Hyper-V virtual machine that wasbacked up with the incremental forever backup type



can only be restored on a Windows 2012 or laterHyper-V host.

System action: The restore operation does not start.

User response: Try the operation again with aWindows 2012 or later Hyper-V host.

FMV2689E A Hyper-V command subcommandcommand was specified, but theHyper-V role is not enabled on the hostsystem

Explanation: The Hyper-V role must be enabled onthe host system where the Hyper-V operation occurs.The current system does not have the Hyper-V roleenabled.

System action: The operation does not start.

User response: Try the operation again from a hostthat has the Hyper-V role enabled.

FMV2690E A Hyper-V BACKUP VM commandwith mode IFFULL or IFINCR wasspecified but the Data Protection forMicrosoft Hyper-V license file does notexist or is not valid

Explanation: The Data Protection for MicrosoftHyper-V license file is required to issue Hyper-VBACKUP VM commands with mode IFFULL orIFINCR. Make sure the Data Protection for MicrosoftHyper-V file is installed.

System action: The backup does not start.

User response: Try the operation again from a hostthat has the Data Protection for Microsoft Hyper-Vlicense file installed. Or, issue the BACKUP VMcommand and specify mode FULL.

FMV2691E A Hyper-V BACKUP VM commandwith mode FULL was specified but theData Protection for Microsoft Hyper-Vlicense file exists. Mode IFFULL orIFINCR must be specified

Explanation: Hyper-V BACKUP VM commands withmode FULL are not allowed on hosts where the DataProtection for Microsoft Hyper-V license file isinstalled. Instead, issue the BACKUP VM commandusing mode IFFULL or IFINCR.

If you must issue the BACKUP VM command withmode FULL, you must uninstall the Data Protection forMicrosoft Hyper-V license file. However, uninstallingthe license file invalidates the IFINCR backup chain. Asa result, an IFFULL is performed if the Data Protectionfor Microsoft Hyper-V license file is reinstalled.

System action: The backup does not start.

User response: Try the operation again and specifymode IFFULL or IFINCR.

FMV2692E An error occurred while registering thefilespace for virtual machine (VM_name).

Explanation: An error occurred while registering thefilespace for the specified virtual machine.


User response: Check the error log for informationabout how to resolve this issue.

FMV2693E An error occurred while registering thefilespace for virtual machine (VM_name).There is a filespace with the same namethat is currently being deleted.

Explanation: An error occurred while registering thefilespace for the specified virtual machine. A filespacewith the same name is currently being deleted on theTivoli Storage Manager server


User response: Wait for the delete filespace to finishand run the backup command again.

FMV2697E The virtual machine cannot be restoredbecause the datastore named 'datastore'does not exist or is inactive.

Explanation: The datastore referenced by virtualmachine when it was backed up does not exist or isinactive on the ESX/ESXi that you are restoring thevirtual machine to.


User response: Find the missing datastore or specifythe -datastore option on the Restore VM command tospecify an existing datastore to restore the virtualmachine files to.

FMV2698E Snapshot operation failed.

Explanation: If you are performing a VSS or LVSAsnapshot based operation, it is possible that thesnapshot was not large enough to contain all thechanges made to the file system after the snapshot wascreated. This could cause the snapshot to becomeinvalid thereby preventing the Tivoli Storage Managerclient from reading the snapshot.

System action: The requested operation stopped.

User response: Examine the client error log foradditional messages related to this error. Performcorrective actions indicated by the messages, then trythe operation again.



FMV2699W Importing VM 'vm name' failed for vApp'vapp name'.

Explanation: The import VM from vSphere to avCloud vApp operation failed.

System action: Restore processing for the vAppcontinues.

User response: Check the dsmerror.log file forinformation about why the VM was not imported.Then, try the operation again. If the problem persists,visit the IBM Support Portal for additional informationat http://www.ibm.com/support/entry/portal/.

FMV2700E Restoring VM 'vm name' of vApp 'vappname' is not possible. There is no VMbackup data.

Explanation: During the vApp restore, a VM thatexists in the restored vApp version could not berestored, because it was not successfully backed up.

System action: The restore operation will proceed,attempting to restore any available vApp backup data.

User response: Examine the client error log for anymessages that might be indicate on the reason for thespecified VM's backup failure. Contact Tivoli StorageManager technical support if further assistance isrequired.

FMV2701E The attempted database operation wasunsuccessful, check the Tivoli StorageManager error log for any additionalinformation.


System action: Reserved.

User response: Check the Tivoli Storage Managererror log for information regarding failure and takefurther action.

FMV2704E Error: The vCenter server version is at alower level than the ESX host version,or the user ID specified by theVMCUser option does not havesufficient permission to perform theoperation.

Explanation: The vCenter returned an error indicatingthere is a problem with the license. This error can occurwhen the vCenter server version is at a lower levelthan the ESX host version. The vCenter server versionmust be at the same (or later) level as the ESX hostversion. This error can also occur when the user IDspecified by the VMCUser option does not havesufficient permission to perform the operation or thepermissions are not applied at the vCenter server level.


User response: Verify the vCenter server is at thecorrect level, and verify that the user ID specified bythe VMCUser option has sufficient permission toperform the operation.

FMV2705S No DB2 UDB partitions are available forrestore.

Explanation: No DB2 UDB partitions are available onthe Tivoli Storage Manager server for restore. This ismost likely due to a previous backup that was abortedbefore the backup completed. The DB2 UDB databaseand selected partitions cannot be restored.


User response: Issue the Tivoli Storage Manager clientcommand QUERY DB2UDB command with the-DETAIL parameter using the same database, file, anddate criteria to see if any database partitions areavailable for restore. Alternatively restore the DB2 UDBdatabase from a different backup.

FMV2711E The snapshot of virtual machine'VM-name' was removed during thebackup.

Explanation: The virtual machine snapshot wasremoved by another application or process during thebackup. This removal corrupts the backup and itbecomes unusable.


User response: Ensure that another application orprocess does not remove or modify the virtual machineduring the backup.

FMV2712W The virtual machine 'name' has aVMware Tools running, but VMwareTools is out of date.

Explanation: A supported version of VMware Toolsmust be installed, running and current to complete avirtual machine backup.

System action: The backup operation fails.

User response: Verify that a supported version ofVMware Tools is installed, current and running. Then,try the backup operation again.

FMV2713E The virtual machine 'VM-name' is in aninvalid connection state 'state'. As aresult, it cannot be backed up.

Explanation: To back up a virtual machine it must bein the 'connected' state to be accessed.


User response: Return the virtual machine to the'connected' state and try the backup again.



FMV2714W The management class 'mc' specified forthe 'dest' backup destination is invalid.The default management class will beused.

Explanation: None.


User response: Contact the Tivoli Storage Manageradministrator to run the configuration utility for DB2UDB and specify a valid management class.

FMV2715E The virtual machine 'VM-name' isconfigured as a fault tolerant virtualmachine. As a result, it cannot bebacked up.

Explanation: vSphere does not allow for the snapshotor backup of fault tolerant virtual machines withvStorage API for Data Protection.


User response: To back up a fault tolerant virtualmachine with vStorage API for Data Protection, firstdisable fault tolerant. Then, after the backup completes,enable fault tolerant.

FMV2716E A background copy process is stillpending on local hardware. A restoreoperation cannot be initiated until thebackground copy process is completed.

Explanation: None.


User response: Wait until the background copyprocess completes and retry the restore operation.

FMV2717E The multi-node definition does not havepermission to delete its own backupfiles from the server.

Explanation: All DB2 UDB commands require that themulti-node definition has permission to delete its ownbackup files from the server in order to properlyreconcile the local backup repository with the serverbackup repository.


User response: Have the Tivoli Storage Manageradministrator update the multi-node definition so thatit has permission to delete its own backup files fromthe server. For example, on the Tivoli Storage Manageradministrative command-line client: . dsmadmc updatenode <multi-node name> backdelete=yes

FMV2718W The virtual machine 'VM-name' requiressnapshot consolidation.

Explanation: Snapshot consolidation is required whena snapshot is deleted but its associated disk is notcommitted back to the base disk. If consolidation is notcompleted, snapshot disks might grow and eventuallyfill the data store.

System action: The virtual machine backup continues.

User response: Consolidate the virtual machinesnapshots according to instructions provided in theappropriate VMware vSphere documentation.

FMV2719E A previous backup started on 'datetime',is using the resources needed for newbackup is still pending.

Explanation: A new backup can not be done untilprevious backup completes.


User response: Wait until previous backup completesbefore starting another local backup. Alternatively, usedifferent copyType value to perform a local backup.TSM local backup policy only allows one incrementaland one full background copy to be pending at anytime, before local backup resources are reused for anew backup version. A new local backup would resultin a backup with background copy in pending state.

FMV2720W Failed to execute the command'command'.

Explanation: IBM Tivoli Storage Manager Failed toexecute a command. The possible reason - thecommand interpreter cannot be found. Verify theComSpec and PATH environment variables that locatethe command interpreter. Either ComSpec or PATH isnot defined, or it is not correctly defined.

System action: The command does not run. Otherwiseprocessing will attempt to continue.

User response: Correct the ComSpec and PATHenvironment variable that locate the commandinterpreter. Contact your system administrator if youare not sure how to make this correction.

FMV2721E The virtual machine is in an invalidconnection state. As a result, it cannotbe backed up.

Explanation: One or more virtual machine backupsfailed because of an invalid connection state. A virtualmachine must be in the 'connected' state to be accessedfor backup.

System action: Processing stops for this virtualmachine

User response: Check the console output and error



logs for information about why the connection statewas invalid. Correct any issues and try backing up thefailed virtual machines.

FMV2722E There is not enough space in the localrepository to complete this backup.

Explanation: This space available in the localrepository is not enough to perform snapshot for thisbackup operation. It could happen if there is morenumber of local versions kept by the management classthan there is space allocated in the local repository atconfiguration time or application configuration haschanged such that previously allocated space is notenough.


User response: Please validate TSM configuration byrunning the configuration wizard.

FMV2723E A value of UNDEF for theREAdstartsrecall option is not validwhen the HSMBACKENDMODE optionis set to TSM.

Explanation: A value of UNDEF for theREAdstartsrecall option is valid only when theHSMBACKENDMODE option is set to TSMFREE.

System action: The operation stops. The file isskipped.

User response: If the HSMBACKENDMODE option isset to TSM, set the REAdstartsrecall option to YES orNO.

FMV2724E The version of IBM Enterprise StorageServer is not supported.

Explanation: This product only supports IBM ESSmicrocode level 2.3 and 2.4.


User response: Ensure that ESS microcode level 2.3 or2.4 is installed.

FMV2725E IBM Tivoli Storage Manager applicationprotection could not register the TSMVSS provider on the guest VM 'VM'.

Explanation: The guest vm credentials speficied onthe datamover do not have the correct requiredWindows permissions for application protection.

System action: The application protection vm backupprocessing stops.

User response: Make sure that the credentialsspecified for the guest VM have the correct requiredWindows permissions for application protection typevm backups. The user guide outlines the correctpermissions that are required for backuping and

restoring application data for Microsoft Exchange andMicrosoft SQL Servers.

FMV2726E The putenv command failed for path =v1.

Explanation: There was not enough memory in theenvironment to successfully set the environment.


User response: Close all unneeded applications andtry the operation again. For UNIX systems that supportresource limits, check to see if the memory resourcelimit is too low by entering the following command:

ulimit -a


FMV2727E ESS Lun ID v1 is not valid.

Explanation: Length of ESS LUN id must be 8characters.


User response: Make sure the length of ESS Lun id is8.

FMV2728E The ESS jar file v1 cannot be found.

Explanation: The Enterprise Storage Sub-system CopyServices JAR file could not be located.


User response: In order to complete EnterpriseStorage Sub-system Copy Services functions the CopyServices command line functions must be available.Check the Copy Services command line is installed andyour Copy Services option setting is pointing to theinstallation directory of the command line.

FMV2729E Operating system command 'command'failed; rc=rc.

Explanation: None.


User response: Check the return code from theoperating system for more information about thefailure. Issue the failing command manually to see ifthe same failure occurs.

FMV2730E The primary and secondary copy serviceservers are down.

Explanation: None.


User response: Start at least one of the ESS copy



service servers. If copy server is already running, checkthe value of java home specified during configurationto make sure it is a valid path name of the directorywhere JRE is installed on master backup node. Useconfiguration wizard to update java home value for theconfiguration.

FMV2731E Cannot open the ESS command outputfile v1 for writing.

Explanation: Can't open this file for writing.


User response: Make sure you have enough space onyour system and write permission to the file.

FMV2732E The ESS LUN 'Serial number string' arealready in use.

Explanation: One or more LUNs specified in themessage are in use by other flashcopy operation.Therefore this flashcopy operation can not continue.


User response: Release ESS LUN in order to reusethem.

FMV2733E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. Tivoli Storage Manager hasbeen denied access to a WMI systemdue to insufficient privileges.

Explanation: Windows denied access to a WindowsManagement Instrumentation (WMI) resource, object,or operation. This program has insufficient permissionsto perform the requested operation.

System action: Performing an operation requiring theWindows Management Instrumentation service.

User response: Raise the permissions assigned toTivoli Storage Manager and retry the operation.

FMV2734E An operation requiring the WindowsManagement Instrumentation (WMI)service has failed with the error'errorstring'. The application interfacedoes not exist.

Explanation: This error occurred because WindowsManagement Instrumentation (WMI) classes were notregistered or have become unregistered. WMI classesare registered with Windows features.

System action: Initialization of a WindowsManagement Instrumentation object failed.

User response: Register the Windows ManagementInstrumentation classes of the appropriate Windowsfeature.

FMV2736E An unexpected response was receivedfrom a remote Tivoli Storage Managerfile system agent. verb : verb remote host: host return code : rc reason code : rsmsg. string : msg-string

Explanation: None.



FMV2737W No disks from VM are mounted becauseall disks were excluded during thebackup.

Explanation: No disks from VM can be mountedbecause all disks were excluded during backup or theVM did not contain any disks.


User response: If files from the affected file systems orvolumes must be recovered, ensure that at least onedisk is included in the backup.

FMV2740E The vApp restore operation failed.

Explanation: The vApp restore operation failed. Checkthe error log for details on why the operation failed.


User response: Review the console output and errorlogs for the details on the problem. Fix any issues andrestart the operation.

FMV2744I TESTFLAG DB2 enabled with the valueof 'value'.

Explanation: None.

System action: This message is informational.


FMV2745E An assigned virtual disk to Hyper-VVirtual Machine 'virtualmachinename'cannot be found.

Explanation: The IBM Tivoli Storage Manager clientdetected that a Virtual Machine has assigned a diskthat is unreachable. The disk may have been moved ordeleted. A snapshot cannot be taken while the diskcannot be found.

System action: The IBM Tivoli Storage Manager couldnot find a virtual disk at the assigned path.

User response: Check that the virtual disk has notbeen moved or deleted and update the virtual machineconfiguration to match any changes to the file system.



FMV2746E An assigned virtual disk to Hyper-Vvirtual machine 'virtualmachinename' is aVHD or invalid format. Only virtualdisks in VHDX format can be backedup.

Explanation: The IBM Tivoli Storage Manager clientdetected that a virtual machine has assigned a disk thatis in the VHD format or is in an unrecognisable orunsupported format. If the disk is in VHDX format itmay be corrupted.

System action: The IBM Tivoli Storage Manager founda virtual disk in VHD or unrecognisable format whilepreparing for a backup of a virtual machine.

User response: If the virtual disk is in VHD formatthere are several options: Remove the VHD from thevirtual machine, convert the virtual disk from VHDformat to VHDX format, or adjust DOMAIN.VMFULLto skip the virtual machine from backup. If the disk isin VHDX format, check that the disk has not beencorrupted.

FMV2747E An assigned AVHDX virtual disk toHyper-V virtual machine'virtualmachinename' cannot find theparent disk. Snapshots can be takenonly if the parent can be found.

Explanation: The AVHDX format specifies an internalfield that points to a parent AVHDX or VHDX file. Ifthe parent cannot be found the disk is invalid and asnapshot will fail.

System action: Tivoli Storage Manager discovered anAVHDX attached to a virtual machine and attempted tofind the parent AVHDX or VHDX file.

User response: Check that the parent AVHDX orVHDX file still exists and has not been moved ordeleted. Return the parent AVHDX and/or VHDX file.

FMV2748E An assigned virtual disk to Hyper-Vvirtual machine 'virtualmachinename'exceeds the maximum capacity limit.The IBM Tivoli Storage Manager clientcannot backup virtual machines withdisks that exceed the limit of twoterabytes.

Explanation: The IBM Tivoli Storage Manager clientdetected that a Virtual Machine has assigned a diskwhose capacity exceeds two terabytes. Virtual disksthat exceed 2 terabytes are currently not supported byincremental forever backups.

System action: The IBM Tivoli Storage Manager founda virtual disk whose capacity exceeds two terabytes ona virtual machine scheduled for back up.

User response: There are several options available:Remove the disk from the virtual machine, shrink thedisk to under two terabytes, copy the data to virtual

disk with a capacity under two terabytes. Even thoughincremental backup is not available, the always fullbackup type is compatible with disks over twoterabytes.

FMV2749E See Microsoft Technote KB2771882. Anassigned virtual disk to Hyper-V VirtualMachine 'virtualmachinename' containsfiles that are on a Cluster SharedVolume and local volumes. A snapshotof a Virtual Machine in thisconfiguration cannot be taken.

Explanation: The IBM Tivoli Storage Manager clientdetected that a Virtual Machine has files involved inthe snapshot on both local volumes and Cluster SharedVolumes. Attempting to snapshot a virtual machine inthis configuration always results in failure. This error isdocumented in Microsoft Technote KB2771882.

System action: The IBM Tivoli Storage Manager clientdiscovered the virtual machine has files on localvolumes and cluster shared volumes prior to taking asnapshot.

User response: Check that all of the disks and theconfiguration files are all on local volumes or clustershared volumes. If necessary, perform a storagemigration to move the disks and/or configuration files.

FMV2750E The Hyper-V Virtual Machine'virtualmachinename' is currentlyundergoing one of the followingoperations: * Creating Local Snapshot *Applying Local Snapshot * DeletingLocal Snapshot * Exporting VirtualMachine * Migrating Virtual Machine *Volume Snapshot Service (VSS)Snapshot * Restore * MergingDifferencing Disks The aboveoperations prevent a Hyper-V VSSsnapshot from taking place. Wait for theoperation to finish or cancel to performa backup.

Explanation: Some virtual machine management tasksinterfere with a virtual machine VSS snapshot. One ofthese operations was detected during a back uprequest.

System action: The IBM Tivoli Storage Manager clientdiscovered the virtual machine is currently undergoingan operation that will prevent a Volume SnapshotService snapshot from occuring.

User response: Cancel or wait for the current virtualmachine management task to finish and then retry theback up.



FMV2753I Establishing inter-client communicationwith node node(s).

Explanation: None.



FMV2785I Gathering current DB2 configuration for'type' restore.

Explanation: None.



FMV2790E Error Accessing Storage Virtual Machine'svm_name' on NetApp Filer 'filer_name'.

Explanation: The specified Storage Virtual Machinecould not be accessed on the specified filer. Make surethat the storage virtual machine exists and is runningon the specified filer and that the storage virtualmachine has been correctly associated with the filerwith the SET NETAPPSVM command.


User response: Make sure that the storage virtualmachine is running on the specified filer and that theassociation between the filer and the storage virtualmachine has been defined correctly with the dsmc setnetappsvm command.

FMV2798E Unable to start a session from clientnode 'nodename' multi-node 'multi-node'to client at address 'ip-address:ip-port'.The Tivoli Storage Manager return codeis rc.

Explanation: None.



FMV2799E An error was encountered during asession with another client. check theTivoli Storage Manager error log for anyadditional information

Explanation: This message is reserved for DB2 UDB.

System action: Reserved.

User response: This message is reserved for DB2 UDB.

FMV2800W No Tivoli Storage Manager processeswere found.

Explanation: The QUERY PIDS command was unableto identify any known Tivoli Storage Managerprocesses running on the system. If the -FILTER option

was used, no processes matching the filter specificationwere found.


User response: If you need to use dsmtrace to enableor disable tracing for a running client process, makesure that the client is already running. If you used the-FILTER option, try the command again with a differentfilter specification. You can use -FILTER=* to display allprocesses running on the system.

FMV2801E The dsmtrace utility was unable toconnect to the specified process.

Explanation: This message typically occurs when thespecified process ID is not active.


User response: If you need to use dsmtrace to enableor disable tracing for a running client process, makesure that the client is already running. Use thedsmtrace QUERY PIDS command to identify runningclient processes, then try the command again.

FMV2802I Tracing has been disabled.

Explanation: None.



FMV2803E Tracing could not be disabled.

Explanation: A problem occurred while trying todisable tracing for the specified process. This messageis usually accompanied by other, more specificmessages immediately preceding or following thismessage.

System action: No changes are made to the tracestatus of the specified process.

User response: Review the messages that immediatelyprecede or follow this message for further informationabout this error.

FMV2804W Tracing is already enabled.-TRACEFILE, -TRACEMAX, and-TRACESEGSIZE are ignored.

Explanation: When tracing is already enabled for aclient process, only the -TRACEFLAGS option has anyeffect.

System action: The -TRACEFLAGS options are set onthe client process. -TRACEFILE, -TRACEMAX, and-TRACESEGSIZE are ignored.

User response: If you need to modify the-TRACEFILE, -TRACEMAX, or -TRACESEGSIZEsettings, you must first use the dsmtrace DISABLEcommand to disable tracing for the client process. Then



run the dsmtrace ENABLE command to configure thedesired trace settings. If it is not necessary to modifythese settings, then this message may be ignored.

FMV2805I Tracing has been enabled.

Explanation: None.



FMV2806E Tracing could not be enabled.

Explanation: A problem occurred while trying toenable tracing for the specified process. This message isusually accompanied by other, more specific messagesimmediately preceding or following this message.

System action: No changes are made to the tracestatus of the specified process.

User response: Review the messages that immediatelyprecede or follow this message for further informationabout this error.

FMV2807E An incorrect number of parameters wasspecified for the command-namecommand.

Explanation: The specified command was invokedwith too few or too many parameters.


User response: Try the command again with thecorrect number of parameters. Run \"dsmtrace help\"for additional information on dsmtrace commandsyntax.

FMV2808W Incremental by snapshot differencebackup did not locate the registeredbase snapshot 'regbase-name' onNetApp/N-Series filer volume'volume-name'. Snapshot 'olderbase-name' isused as the base snapshot.

Explanation: Incremental by snapshot differencebackup did not locate the specified registered basesnapshot on the specified NetApp/N-Series filervolume. The most recent existing snapshot which isolder than the registered base snapshot is used as thecurrent base snapshot.



FMV2809E The backupid 'backupid:' in the input filedoes not match the vmname 'vmname:'being restored.

Explanation: There is a discrepency between thebackupid and vmname specified in the input file


User response: Confirm that the backupid specifiedmatches the vmname you are attempting to restore byre-running the inquire_detail command and make anynecessary corrections before attempting the restoreagain.

FMV2810E The Tivoli Storage Manager for VirtualEnvironments Input File 'input file:'appears to be empty.

Explanation: While processing the Input File no itemswere found to operate on.

System action: The operation cannot continue with anempty list.

User response: Confirm that the input file is notempty and has valid input. If the file is not empty itmay be that an error occurred while reading the file,please check the error log for any errors found duringthe reading of the file. If errors are found make thenecessary corrections before attempting the operationagain.

FMV2811E The Tivoli Storage Manager for VirtualEnvironments could not find a suitabledatamover agent for the DataCenterNode 'datacenter nodename'.

Explanation: While processing Proxy relationshipswith the DataCenter Node specified, no appropriatedatamover matches detected

System action: The operation cannot continue withouta valid datamover.

User response: Work with your Tivoli StorageManager Administrator to ensure that your DataCenterNodes have granted proxy authority to yourDataMover Nodes.

FMV2812E The Tivoli Storage Manager for VirtualEnvironments could not find Datamovernode named 'datamover nodename' on theTivoli Storage Manager Server.

Explanation: While processing Proxy relationshipswith the DataCenter node and DataMover nodespecified, no appropriate Datamover node namematches detected.

System action: The operation cannot continue withouta valid Datamover Node name.

User response: Make sure the Datamover node namespecified is a valid Tivoli Storage Manager node nameand that the node has the proper proxy relationshipsestablished.



FMV2813E The Tivoli Storage Manager Serverreturned an empty network address orport number for 'datamover nodename'.

Explanation: While querying the Tivoli StorageManager Server for the Datamover network addressand port number, the Server returned zero for one ofthe values.

System action: The operation cannot continue withouta valid Datamover network address and port number.

User response: This is usually the result of aDatamover Node not being started. Log on to theDatamover host and start or restart the DSMCADservice and retry the Tivoli Storage Manager for VirtualEnvironments command again. If the problem persists,work with your Tivoli Storage Manager ServerAdministrator to inspect the Tivoli Storage ManagerServer activity log to identify the issue.

FMV2814E Tivoli Storage Manager for VirtualEnvironments detected an error whileparsing the Input File 'input file'. The'specifier' appears to be empty or invalid.

Explanation: While parsing the Input File an erroroccurred.

System action: The operation cannot continue withoutvalid virtual machine specifications.

User response: This is usually the result of an emptyvirtual machine name or other identifier. Please checkthat the syntax of the Input File is correct for all entriesand that virtual machine names are not empty andretry the operation.

FMV2815E Tivoli Storage Manager for VirtualEnvironments detected an error whileparsing 'read in line' from the Input File'input file'.


System action: The operation cannot continue withoutvalid specifications in the Input File.

User response: This may be the result of an emptyvirtual machine name or other identifier. Please checkthat the syntax of the Input File is correct for all entriesand that virtual machine names are not empty andretry the operation.

FMV2816E Tivoli Storage Manager for VirtualEnvironments detected that the TivoliStorage Manager Server IP address wasnot specified.

Explanation: While parsing the command line options,an empty Server address was detected.

System action: The operation cannot continue without

a valid network address for the Tivoli Storage ManagerServer.

User response: This may be a result of the VMCLIprofile having an empty VE_TSM_SERVER_NAMEentry. Please check that the VMCLI profile is configuredcorrectly specifying the Tivoli Storage Manager Serveraddress.

FMV2817E Tivoli Storage Manager for VirtualEnvironments detected that the vCenterCommand-Line interface node namewas not specified.

Explanation: While parsing the command line options,an empty vCenter Command-Line interface node namewas detected.

System action: The operation cannot continue withouta valid vCenter Command-Line interface node name.

User response: This may be a result of the VMCLIprofile having an empty VE__TSMCLI_NODE_NAMEentry. Please check that the VMCLI profile is configuredcorrectly specifying the vCenter Command-lineinterface node name.

FMV2818E Tivoli Storage Manager for VirtualEnvironments detected that the TivoliStorage Manager Server port was notspecified.

Explanation: While parsing the command line options,an empty Tivoli Storage Manager Server port wasdetected.

System action: The operation cannot continue withouta valid Tivoli Storage Manager Server port.

User response: This may be a result of the VMCLIprofile having an empty VE_TSM_SERVER_PORTentry. Please check that the VMCLI profile is configuredcorrectly specifying the Tivoli Storage Manager Serverport.

FMV2820E An interrupt has occurred. The currentoperation will end and the client willshut down.

Explanation: This message is issued when the processis interrupted by a break signal such as CTRL-BREAKor CTRL-C.

System action: The Tivoli Storage Manager operationand process are ended immediately.

User response: Restart the operation if desired.

FMV2821E The function is not supported on theplatform.

Explanation: The specified function isn't supported onthe specified platform.




User response: Please retry the specified function on asupported platform.

FMV2824E Tivoli Storage Manager for VirtualEnvironments detected that the nodename representing the vCenter is notspecified.

Explanation: While parsing the command line options,an empty vCenter node name was detected.

System action: The operation cannot continue withouta valid vCenter node name.

User response: This may be a result of the VMCLIprofile having an empty VE_VCENTER_NODE_NAMEentry. Please check that the VMCLI profile is configuredcorrectly specifying the vCenter node name.

FMV2825E Tivoli Storage Manager for VirtualEnvironments detected that the nodename representing the Datacenter is notspecified.

Explanation: While parsing the command line options,an empty datacenter node name was detected.

System action: The operation cannot continue withouta valid datacenter node name.

User response: This is a result of the -d DataCenterNode Name not being passed in to the Command-line.Re-try the operation making sure to pass the -dDatacenter Node Name to the command-line call.

FMV2826E Tivoli Storage Manager for VirtualEnvironments detected that the nodename representing the vCenterDatamover is not specified.

Explanation: While parsing the command line options,an empty Datamover node name was detected.

System action: The operation cannot continue withouta valid Datamover node name.

User response: This is a result of the -o DatamoverNode Name not being passed in to the Command-line.Re-try the operation making sure to pass the -oDatamover Node Name to the command-line call.

FMV2827E Tivoli Storage Manager for VirtualEnvironments detected that the inputfile is not specified.

Explanation: While parsing the command line options,an empty or non-existing input file name was detected.

System action: The operation cannot continue withouta valid input file name.

User response: This is a result of the -I Inputfile namenot being passed in to the Command-line. Re-try the

operation making sure to pass the -I input file name tothe command-line call.

FMV2828E Image operations are not supported forthe specified file system.

Explanation: Image backup and restore are notsupported for the specified file system.

System action: The requested image operation is notperformed.


FMV2829E Image operations are not supported forGPFS.

Explanation: Image backup and restore are notsupported for GPFS volumes.

System action: The requested image operation is notperformed.


FMV2830E An incorrect number of parameters wasspecified.

Explanation: The specified command was invokedwith too few or too many parameters.


User response: Try the command again with thecorrect number of parameters.

FMV2831E Incremental by snapshot differencecannot be performed on 'volume-name' asit is of type 'type' and is not aNetApp/N-Series 'fsType' volume.

Explanation: The volume specified cannot be used forperforming NetApp/N-Series snapshot differenceincremental operation. The volume does not correspondto the NFS mount point or the CIFS shared drive for aNetwork Appliance or N-Series NAS volume. Onepossible reason for this failure is that snapshotdifference incremental backups can only be performedagainst NetApp/N-Series NFS volumes on AIX/Linuxplatforms, or CIFS volumes on Windows platforms.

Another possible reason for this failure is that the qtreesecurity style for the volume was incorrectly selected. Ifthe CIFS volume is mapped on Windows, ensure thatthe security style is set to NTFS. If the volume ismounted as NFS, ensure that the security style is set toUNIX.


User response: Try the command again with aNetApp/N-Series NFS or CIFS volume with the correctsecurity style.



FMV2832E Incremental by snapshot differencefailed for filespace name. See the error logfor details.

Explanation: Failed to perform NAS NFS/CIFSIncremental by snapshot difference operation.


User response: Take appropriate action based on theinformation in the error log. If the problem persistsplease contact your IBM Tivoli Storage Manageradministrator.

FMV2834E You have to be a root user in order toperform incremental backup usingsnapshot difference.

Explanation: Failed to perform NAS NFS/CIFSincremental backup operation using snapshot differenceas the user was non root.


User response: Please retry the operation as root user.

FMV2835E Incremental backup using snapshotdifference is not supported on thisplatform.

Explanation: NetApp NFS/CIFS incremental backupoperation using snapshot difference is only supportedon AIX, Linux and Windows platforms.


User response: Retry the incremental operationwithout the snapdiff option.

FMV2836E Incremental backup operation usingsnapshot difference is only available forfull volumes. is a partial volume orqtree.

Explanation: Cannot perform NAS NFS/CIFSincremental backup operation using snapshot differenceon the mounted or mapped volume due to one of thefollowing reasons: 1) The volume is actually a qtree. 2)The volume is not a full volume, it is not mounted ormapped to the root of the volume.


User response: Retry the incremental backupoperation by specifying an entire NAS NFS or CIFSvolume.

FMV2837E Unable to access the required storedNetApp filer credentials (user id andpassword) for filer ''. Make sure the SETPASSWORD -TYPE=FILER commandwas specified correctly to store thecredentials.

Explanation: The user id and password for thespecified NetApp Filer have been either not configuredor have been specified incorrectly.


User response: Use the 'set password -type=filer'command to define the user id and password for thespecified NetApp Filer and retry the snapshotdifferential backup operation.

FMV2838W The file path 'filename' exceeds HSMmaximaum path length.

Explanation: A file that you tried to migrate has apath name that is too long.

System action: File skipped from migration.

User response: Place files into a shorter path to makethem available for migration.

FMV2839E Failed with ONTAPI error 'error_code'while connecting to NetApp Filer'filer_name' using user id 'id_name'. Youmight have provided credentialsincorrectly for this Filer.

Explanation: The user ID and password have beenconfigured incorrectly for the specified Filer.

If you are using the snapdiffhttps option, ensure thatyou are not specifying vFiler volumes as vFiler doesnot support the HTTPS transport type.


User response: Make sure that the credentials youhave specified for the Filer are the correct ones. Use thedsmc set password command to specify the correctcredentials for your Filer and try the command again.

FMV2840E Incremental backup using snapshotdifference is not supported for DataONTAP file server version'version.modification.submodification'.Upgrade the file server 'file-server-name'to Data ONTAP version '7.3' or later inorder to perform incremental backupoperations using snapshot difference.

Explanation: The file server specified is not at theData ONTAP version that supports snapshot differenceAPI.


User response: Upgrade the file server to DataONTAP version 7.3 or later and retry the operation.



FMV2841E Incremental by snapshot difference isonly supported on AIX 64 bit and Linux86 bit clients.

Explanation: Incremental backup using snapshotdifference feature is only available on IBM TivoliStorage Manager AIX 64 bit and Linux 86 clients.


User response: Try the command again with an IBMTivoli Storage Manager AIX 64 bit or Linux 86 client.

FMV2842E Tivoli Storage Manager for VirtualEnvironments detected an error with thecreatesnap: keyword. createsnap:yes isspecified while also specifyingvmsnapname:VMWare Snapshot Name.

Explanation: While parsing the Input File forFlashCopy Manager for VMWare offload backup, anerror condition was detected with VM Ware snapshothandling. Specifying a VMWare Snapshot name whilespecifying createsnap:yes is not allowed.

System action: The operation cannot continue withoutspecifying the correct createsnap: and vmsnapname:combination.

User response: This is a result of the -I Inputfilecontaining conflicting input for createsnap: andvmsnapname: keywords. If you intend to have TivoliStorage Manager for Virtual Environments use aVMWare Snapshot created by FlashCopy Manager thenspecify createsnap:no with a valid VMWare Snapshotfor the vmsnapname: keyword.

FMV2849E Incremental backup operation usingsnapshot difference failed because asnapshot matching 'snapshot name' couldnot be located on volume NAS volume.

Explanation: A snapshot name or pattern specified bythe BASESNAPSHOTNAME orDIFFSNAPSHOTNAME option could not be located onthe volume being backed up.


User response: Rety the operation and specify asnapshot with the BASESNAPSHOTNAME orDIFFSNAPSHOTNAME which exists on the specifiedvolume.

FMV2850E Error Creating Snapshot: Volume NASvolume is a snapmirror destinationvolume.

Explanation: An attempt was made to create asnapshot on a read only snapmirror destinationvolume.


User response: Rety the operation using theUSEEXISTINGBASE and DIFFSNAPSHOT=latestoptions.

FMV2851E Snapshot Processing Error: .

Explanation: An error occurred due to the reasonspecified in the message


User response: Ensure that the specified volume isonline and allows write access.

FMV2852W Registered Base Snapshot '' no longerexists on volume .

Explanation: The specified base snapshot registered bythe previous backup no longer exists on the specifiedvolume.


User response: The client will attempt to use anexisting snapshot older than the missing registeredsnapshot as the base for the current backup.

FMV2853E Unable to establish base snapshot onvolume .

Explanation: A base snapshot could not be created orselected on the specified volume.


User response: See other error messages to determinewhy the base could be established.

FMV2854E Unable to establish diff snapshot onvolume .

Explanation: A diff snapshot could not be created orselected on the specified volume.


User response: See other error messages to determinewhy the diff could be established.

FMV2855W Tivoli Storage Manager for VirtualEnvironments detected an error whileparsing the Input File 'input file'. The'specifier' should not be specified whenusing 'specifier'. Option will be ignored.


System action: The operation will continue ignoringthis parameter.

User response: This is usually the result of anidentifier used with the wrong option. Please check thatthe options in the Input File matches the requestedoperation and retry the operation.



FMV2856E Tivoli Storage Manager for VirtualEnvironments detected that the nodename representing the vCloud is notspecified.

Explanation: A node name that represents the vCloudis not specified in the VMCLI profile.

System action: The operation cannot continue withouta valid vCloud node name.

User response: Specify the vCloud node name in theVE_VCENTER_NODE_NAME parameter in the VMCLIprofile. Then, try the operation again.

FMV2857E Tivoli Storage Manager for VirtualEnvironments detected while parsing'read in line' from the input file 'input file'that option 'specifier' is required for'operation' operation.

Explanation: A required option or identifier is missingfrom the input file.


User response: This may be the result of a missingoption or identifier. Verify that the syntax of thecommand and the syntax of the values in the input fileare correct. Then, try the operation again.

FMV2858E Failed to get the list of available VMsfor backup

Explanation: Failed to get the entire list of VMs inorder to choose ones that needed to be backed up.


User response: Verify that configuration parametersfor connection to vCenter.

FMV2859E Failed to locate the Organization VDCnode that is used to store the backed updata.

Explanation: The Organization VDC node that storesthe backed up vApp data was not located. This nodemust be mapped to the Provider VDC node. This issuemight be caused by invalid mapping between theProvider VDC node and the Organization VDC node.


User response: Go to the Configuration page and click'Run the Configuration Wizard' to verify that mappinginformation for the Provider VDC node is valid.

FMV2860E The PRESNAPSHOTCMD commandfailed. The snapshot differential backupwill not be executed.

Explanation: The command specified by thePRESNAPSHOTCMD option must complete

successfully in order to execute the snapshotdifferential backup. If the command completed with areturn code of 0 (zero), it is considered to havecompleted successfully. If the command completed withany other return code, it is considered to have failed. Ifthe command failed then the snapshot differentialbackup is not executed.

System action: The client does not execute thesnapshot differential backup operation.


FMV2861W The POSTSNAPSHOTCMD commandfailed.

Explanation: If the command specified by thePOSTSNAPSHOTCMD option completed with anon-zero return code, the snapshot differential backupoperation continues. The operation continues with awarning-level result. The result of thePOSTSNAPSHOTCMD command does not supersede ahigher result from the snapshot differential backupcommand. For example, if the snapshot differentialbackup command completed with code 12, a lowerreturn code from the POSTSNAPSHOTCMD commanddoes not alter the return code.

System action: The snapshot differential backupcontinues, but with a warning return code of at least 8.

User response: Identify and repair the problem thatcaused the command to fail. Consider wrapping thecommand in a script that always exits with a returncode of zero.

FMV2862E No entry found for the specified StorageVirtual Machine.

Explanation: The SVM does not exist in the registry orpassword file.

System action: No operation is performed.

User response: The user should register the SVMusing the Set NetAppSVM command.

FMV2863E The backup-archive client failed to loadthe vCloud protection runtime library.

Explanation: vCloud protection runtime library is notloaded by the backup-archive client.


User response: Verify that the vCloud runtime libraryexist in the 'plugins' folder under the client installationfolder.



FMV2864E A Hyper-V operation was attempted, butthe Hyper-V role was not detected onthe host system.

Explanation: The Hyper-V role must be enabled onthe host system where the Hyper-V operation occurs.The current host system either does not have theHyper-V role enabled or does not support Hyper-V.

System action: The operation does not start.

User response: If the host system supports Hyper-Vthen enable the Hyper-V role. Otherwise, try theoperation again from a host system that supportsHyper-V and has the Hyper-V role enabled.

If you want to process VMware virtual machines, go tothe IBM Tivoli Storage Manager window, and click Edit> Client Preferences > VM Backup. Click VMWare FullVM or VMWare File Level. Then, click OK.

FMV2865E An error occurred creating or accessing avirtual disk for virtual machine'VM-name'.

Explanation: An error occurred creating or accessing avirtual disk while restoring a virtual machine.


User response: See the client error log for moredetailed information about the error.

FMV2866E An error occurred creating virtualmachine 'VM-name'.

Explanation: An error occurred creating the virtualmachine during the restore operation.



FMV2867E An error occurred querying virtualmachine 'VM-name'.

Explanation: An error occurred querying the virtualmachine during the restore operation.



FMV2868E An error occurred removing virtualmachine 'VM-name'.

Explanation: An error occurred removing the virtualmachine during the restore operation.



FMV2869E A virtual machine on the hypervisor hasa different name but the same ID asvirtual machine to restore 'VM-name'has. Restore not allowed.

Explanation: A virtual machine with a different nameand the same ID than the virtual machine beingrestored exists on the hypervisor.


User response: Choose a different virtual machine torestore to or delete the existing virtuual machine.

FMV2870W An incremental backup of virtualmachine 'vmname' was requested, but thevirtual machine lacks an existingrecovery snapshot. A full backup will betaken to prevent data loss.

Explanation: Removal of the recovery snapshot of avirtual machine does not reset the last successfulbackup time maintained internally. The lack of a resetcreates an inconsistency between the backup time andthe hard disk configuration of the virtual machine. Afull backup fixes the ambiguity and prevent data loss.

System action: An inconsistency in the virtualmachine configuration was detected.

User response: Avoid deleting the recovery snapshotbetween back up operations.

FMV2872E Tivoli Storage Manager was unable torestore a virtual disk user metadataentry of virtual machine 'vmname' todisk 'diskpath'.

Explanation: An attempt to restore a user metadataentry of a disk failed. The user metadata of the diskmay inaccessible or unreachable.

System action: A restore of a virtual disk.

User response: Check the user privileges includeaccess to virtual disk writes or move the disk to anaccessible location.

FMV2873I Virtual machine 'vmname' wassuccessfully restored. If this virtualmachine was restored to a cluster,ensure that the cluster settings enablethe restored virtual machine to operatein high availability mode. Highavailability settings, and the preferredset of hypervisor nodes that can operatein high availability mode, might not beset automatically.

Explanation: The specified virtual machine has beenrestored, but the restore process does not alterMicrosoft Failover Clustering High Availability settings.If you restored a virtual machine that you previouslydeleted, or if you restored a virtual machine to a new



name and location, the restored virtual machine mightnot be enabled as a high availability resource. Enablehigh availability for this virtual machine by usingMicrosoft Failover Cluster Manager, System CenterVirtual Machine Manager, or by using PowerShellcmdlets.


User response: Use Microsoft Failover ClusterManager, System Center VM manager, or PowerShell toconfigure the cluster to allow this virtual machine toperform in a high availability configuration.

FMV2876E Unable to access the required storedNetApp Management Filer credentials(user id and password) for filer ''associated with storage virtual machine'' . Make sure the SET PASSWORD-TYPE=FILER command was specifiedcorrectly to store the credentials.

Explanation: The user id and password for thespecified NetApp management filer associated with thespecified storage virtual machine have been either notconfigured or have been specified incorrectly.

A storage virtual machine is associated withmanagement filer using the SET NETAPPSVMcommand. Credentials for a management filer arestored with the SET PASSWORD -TYPE=FILERcommand.


User response: Use the 'set password -type=filer'command to define the user id and password for thespecified NetApp Management Filer. Use the 'setnetappsvm' command to associated a storage virtualmachine with a management filer. Ensure that both ofthese commands were specified correctly and retry thesnapshot differential backup operation.

FMV2888E Backup VM Full VM Incremental isunable to run. A valid TSM for VirtualEnvironments license file (license-file)cannot be located.

Explanation: The license file was not found, or cannotbe opened because of permissions, or the file iscorrupted.



FMV2889I The vApp 'vapp name' was successfullyrestored under the name 'new vapp name'

Explanation: The restore operation was succesful inrestoring the vApp into the specified name.



FMV2891W The vApp 'vapp name' was successfullyrestored. However, failed vms num out ofexisting vms num VMs were not restored.

Explanation: Although the vApp restore operation onthe vCloud completed successfully, one or more VMswere not restored.

System action: The operation completed successfully.However, some VMs were not restored.

User response: Check the dsmerror.log file forinformation about why the VMs were not restored.Then, try the operation again. If the problem persists,visit the IBM Support Portal for additional informationat http://www.ibm.com/support/entry/portal/.

FMV2900E Tivoli Storage Manager for VirtualEnvironments detected that the scandomain was not specified.

Explanation: While parsing the command line options,no scan domain was detected. This error occurredbecause the -domain option was not specified.

System action: The operation cannot continue withouta valid scan domain.

User response: Run the operation again and specifythe -domain option.

FMV2901E Tivoli Storage Manager for VirtualEnvironments detected that the domainuser was not specified.

Explanation: While parsing the command line options,no domain user was detected. This error occurredbecause the -user option was not specified.

System action: The operation cannot continue withouta valid domain user.

User response: Run the operation again and specifythe -user option.

FMV2902E Save domain password failed infunction func-name with return codereturn-code.

Explanation: An unexpected write access erroroccurred when the function tried to save the domainpassword. Write access does not exist to either theregistry or to the Tivoli Storage Manager for VirtualEnvironments on Linux installation folder where thepassword file is saved.


User response: Grant write access to either theregistry or to the Tivoli Storage Manager for Virtual



Environments on Linux installation folder and try theoperation again.

FMV2903E Read domain password failed infunction func-name with return codereturn-code.

Explanation: An unexpected error occurred when thefunction tried to read the domain password.


User response: On Windows, verify that the passwordexists in the registry. On Linux, verify that thepassword exists in the password file. Try the operationagain.

FMV2998I The option 'option' that was found in theinclude/exclude file 'file-name' at the linenumber: number is not supported andwill be ignored by the client.

Explanation: The specified option is valid but notsupported on the current platform and will be ignoredby the client.


User response: You can ignore the message or removethe option from the include/exclude file.

FMV3000I communication-type communicationsavailable on port port-number.

Explanation: The specified communications areavailable on the specified port number.



FMV3002I Session started for user userid(communication-method address).

Explanation: A session was started for the specifieduser.



FMV3003I The new password is case sensitive.

Explanation: Your account has been updated to usecase sensitive password.

System action: None

User response: Make sure to remember the newpassword as you enter it, including character casing.For more details, contact your Tivoli Storage Manageradministrator.

FMV3004E Session for user userid terminated -invalid password entered.

Explanation: A session was terminated for thespecified user because an invalid password wasentered.

System action: The session with the specified user isterminated.

User response: Re-start the remote client and enter thecorrect password for the specified user.

FMV3005I Session for user userid terminated - idlefor idle-minutes minutes.

Explanation: A session was terminated for thespecified user because there was no activity on thesession for the specified number of minutes.

System action: The session with the specified user isterminated.

User response: Re-start the remote client to begin anew session.

FMV3006I Processing request for the Tivoli StorageManager Web Client (ip-address).

Explanation: A request for the Web Client is beingprocessed.



FMV3007I Tivoli Storage Manager client-nameterminating - idle for idle-minutesminutes.

Explanation: The specified client is terminatingbecause it has been idle for the specified time. It will beautomatically started when it is needed.

System action: The client program stops.


FMV3008E Too many symbolic links were detectedwhile resolving name 'file_name'




FMV3009E The Logical Volume Snapshot Agentplugin library was not found.

Explanation: The Logical Volume Snapshot Agent(LVSA) plugin library should have been installed whenthe client was installed, but it cannot be found.




User response: Try the operation again. If the problemrecurs, re-install the Tivoli Storage Manager clientsoftware. If the problem persists, contact IBM technicalsupport for further assistance.

FMV3010E The snapshot wizard operation failed.

Explanation: The snapshot wizard operation failedwith a non-zero return code. Check the error log foradditional information.


User response: Review the error log for any errormessages, and then retry the operation after correctingthe cause for failure.

FMV3011E Previous changes have not beencommited. The machine must berebooted before this operation can beperformed

Explanation: A previous operation required themachine to be rebooted for the changes to take effect,but the machine has not been rebooted. The machinemust be rebooted before this selected operation can beperformed.


User response: Reboot the machine and then retry theoperation.

FMV3012E The Logical Volume Snapshot Agent isnot installed. Use the Setup Wizard toconfigure either Online Image or OpenFile support and choose the LogicalVolume Snapshot Agent as the snapshotprovider.

Explanation: The selected operation requires theLogical Volume Snapshot Agent, but it is not installed.Use the Setup Wizard to install the LVSA.


User response: Retry the operation after installing theLogical Volume Snapshot Agent.

FMV3013E The specified snapshot provider is notsupported on this version of theoperating system.

Explanation: The specified snapshot provider is notsupported on the version of the operating system youare currently running. If another snapshot provider isavailable, select it and retry the operation.


User response: If another snapshot provider isavailable, select it and retry the operation.

FMV3014E Expose snapshot failed for backupdocument 'xml-backup-doc-file'.

Explanation: Expose snapshot failed.



FMV3100E Unable to get the iSCSI initiator name.The Windows error is (error)

Explanation: The iSCSI initiator name is notconfigured on the system.


User response: See the appropriate MicrosoftDocumentation about how to configure the iSCSIinitiator name.

FMV3101E The mount operation for virtualmachine 'vmname' failed with rc =return-code

Explanation: An error occurred during the mountoperation. See the output from the previous operationto identify the cause of the error.


User response: Check the error log for informationabout how to resolve this issue.

FMV3102I 'VMNAME' mounted successfully and isready

Explanation: The mount operation for the specifiedvirtual machine completed successfully. As a result, thevirtual machine is ready for a file-level restoreoperation.


User response: None

FMV3103E Unable to load the dynamic link library(iscsidsc.dll). The Windows error is(error)

Explanation: The iSCSI dynamic link library(iscsidsc.dll) cannot be found on the system.


User response: See the appropriate MicrosoftDocumentation about how to install the dynamic linklibrary (iscsidsc.dll).



FMV3104E A target was not found on the iSCSIportal The missing target is 'target'

Explanation: The iSCSI portal is unable to discover allof the targets that were created by the IBM TivoliStorage Manager Recovery Agent command-lineinterface.


User response: See the appropriate MicrosoftDocumentation about how to correct this iSCSI portalissue. Search http://technet.microsoft.com/en-US/windowsserver for iSCSI troubleshooting information.

FMV3105E Unable to connect all targets on theiSCSI Portal The target that is notconnected is 'target'. Windows error is(error)

Explanation: The iSCSI portal is unable to connect alldiscovered targets that were created by the IBM TivoliStorage Manager Recovery Agent command-lineinterface.


User response: See the appropriate MicrosoftDocumentation about how to correct this iSCSI portalissue. Search http://technet.microsoft.com/en-US/windowsserver for iSCSI troubleshooting information.

FMV3106E Windows Configuration Manager isunable to scan for new hardware.Windows error is (error)

Explanation: The new iSCSI disk connection cannot bedetected by the Windows Configuration Manager.


User response: See the appropriate MicrosoftDocumentation about how to correct this hardwarescan issue.

FMV3107E The attempt to retrieve information fordisk 'disk' failed with Windows error(error).

Explanation: A Windows API call failed to retrieve thedisk information.


User response: See the appropriate MicrosoftDocumentation for information about how to resolvethis Windows API call issue.

FMV3108W The disk with label='label' is notmounted because it was excludedduring the backup (Reason: 'reason').

Explanation: The disk cannot be mounted because itwas excluded during backup. It is not possible to

recover files from any of the file systems or volumesthat use this disk.


User response: If files from the affected file systems orvolumes must be recovered, ensure that the disk isincluded in the backup.

FMV3110E Unable to communicate with Windowsdevice 'device'. The Windows error is(error)

Explanation: A Windows API call failed to open aWindows device.



FMV3111E Unable to mount the same dynamicdisks mutliple times. The disk 'disk'signature is the same as the disksignature of another disk that is online.

Explanation: It is not possible to attach a second diskto the system with the same disk signature.


User response: The other disk with the identical disksignature must be dismounted before you can attemptthe operation again.

FMV3112E Windows Virtual Disk Service is notable to detect all new devices.

Explanation: The Virtual Disk Service VDS is unableto access all iSCSI targets. Some targets are missing ornot working.

System action: The operation will be rolled back andstopped.

User response: Determine why the data mover cannotaccess some iSCSI targets. Determine that the TSMserver is working correctly. Determine that the iSCSIservice is running. Search the Windows event log forproblems with the missing devices.

FMV3113E The virtual machine 'name' has at leastone mirror or RAID5 volume. Mirrorand RAID5 support is disabled!

Explanation: During the mount operation it wasdetected that the virtual machine has a mirror orRAID5 volumes. The support for such volumes werediabled by the Administrator.


User response: Contact the Administrator for moreinformation.



FMV3114E The attempt to retrieve information forvolume 'volume' failed with Windowserror (error).

Explanation: A Windows API call failed to retrieve thevolume information.



FMV3115E The attempt to bring disk 'disk' onlinefailed with Windows error (error).

Explanation: A Windows API call failed to bring thedisk online.



FMV3116E The attempt to create directory 'dir'failed with Windows error (error).

Explanation: A Windows API call failed to create thedirectory.



FMV3117E The mount volume attempt at directory'dir' failed with Windows error (error).

Explanation: A Windows API call failed to mount thespecified volume.



FMV3118E Unable to determine the operatingsystem type of the VM to be restored.

Explanation: The operating system type of the VM tobe restored cannot be determined. This issue can occurwhen the restore parameter -VMOSType is notspecified or it specifies an incorrect operating systemtype.


User response: Use the -VMOSType parameter tospecify the correct operating system type of the VM tobe restored.

FMV3119W Operating system type "name1" isdetected but operating system type"name2" is specified.

Explanation: The operating system type of thedetected VM does not match the type specified withthe restore parameter -VMOSType. Inconsistentoperating system types might negatively impact themount operation. The operation will continue using"name2" as the operating system type.


User response: If the mount operation fails, try theoperation again and use automatic detection or specifythe correct operating system.

FMV3122E The Microsoft iSCSI Initiator Serviceencountered an error. The Windowserror is (error).

Explanation: The Microsoft iSCSI Initiator Serviceencountered an error during an iSCSI operation. Thiserror caused the operation to stop.


User response: See the Microsoft iSCSI InitiatorService error message to determine the cause of theerror. If necessary, see the appropriate MicrosoftDocumentation for information about how to resolvethis iSCSI Initiator error.

FMV3123E Unable to read or write the local VMfile-level restore data. filename Filecannot be accessed or is damaged.

Explanation: For VM file-level restore operations, datamust be stored on the local data mover in a directorythat the user running the restore can access. It can alsobe that the data file was damaged!


User response: To store the VM file-level restore data,the data mover application requires read and writeaccess to the C:\Documents and Settings\AllUsers\Application Data\Tivoli\TSM\ or C:\ProgramData\Tivoli\TSM folder. Set the access rights to this directoryso that your user has the correct rights. If the file wasdamaged it can be helpfull to replace the currentversion with the .bak file.

FMV3125E The local data for file-level restoremount with the ID: id and virtualmachine name 'name' cannot be found!

Explanation: The local data set for the specifiedmount ID or virtual machine name cannot be found


User response: Use the query "dsmc q vm <name>-vmrestoretype=mount" command to get the correct



mount ID and virtual machine name for the cleanup

FMV3126E The node name of the Linux mountproxy partner could not be found.

Explanation: An error occurred while querying theIBM Tivoli Storage Manager server for Linux mountproxy partner; the node could not be found.Communications with the Linux mount proxy partneris required to perform Linux VM file-level restoreoperations.


User response: Check the Linux mount proxy partnernode configuration and ensure that the node iscorrectly configured and running.

FMV3127E The IP address or port of the Linuxmount proxy partner could not befound.

Explanation: An error occurred while querying theIBM Tivoli Storage Manager server for the Linux mountproxy partner. The IP address or port of that partnercould not be found; the address and port are requiredto process file-level restores for Linux VMs.


User response: Check the node configuration andensure that the Linux mount proxy partner is correctlyconfigured and running. Verify that the Client AcceptorDaemon on the Linux mount proxy partner is runningand able to connect to the IBM Tivoli Storage Managerserver.

FMV3128E The node name of the Windows mountproxy does not comply with TivoliStorage Manager naming conventions.

Explanation: An error occurred while querying theIBM Tivoli Storage Manager server for Linux mountproxy partner. The name of the Windows mount proxydoes not comply the naming convention. A correctname is required for processing of Linux VMs.


User response: Check the node configuration andensure that the mount proxy name is correct. Use theweb based configuration wizard to set up theconfiguration.

FMV3129I The mount cleanup of VM 'VMNAME'completed.

Explanation: The mount cleanup operation for thespecified virtual machine completed.


User response: None

FMV3130E The mount cleanup operation for virtualmachine 'vmname' failed with rc =return-code

Explanation: An error occurred during the mountcleanup operation. See the output from the previousoperations to identify the cause of the error.


User response: Check the dsmerror.log file forinformation about how to resolve this issue.

FMV3131E The operation to disconnect the iSCSItargets from the Windows data moverfailed.

Explanation: An error occurred during the mountcleanup operation while disconnecting the iSCSItargets. See the output from the previous operations toidentify the cause of the error.


User response: Open the Windows iSCSI Initiator Tooland disconnect the targets and remove the target portal.The tool can be found in "Administrative Tools" ->"iSCSI Initiator"

FMV3132E The Windows iSCSI Service is unable toget a list of all currently runningsessions. The Windows error is (error)

Explanation: The iSCSI Service could not get a list ofall connected targets and the corresponding sessions.


User response: See the Microsoft documentation forinformation to correct this iSCSI issue. Searchhttp://technet.microsoft.com/en-US/windowsserverfor iSCSI troubleshooting information.

FMV3133E The target 'target' could not bedisconnected by the iSCSI portal. TheWindows error is (error)

Explanation: The iSCSI portal is unable to disconnectall the connected targets that were created by therecovery agent command-line interface.


User response: See the Microsoft documentation forinformation to correct this iSCSI portal issue. Searchhttp://technet.microsoft.com/en-US/windowsserverfor iSCSI troubleshooting information.

FMV3134E The Windows iSCSI Service is unable toget list of all currently available portals.The Windows error is (error)

Explanation: The iSCSI Service has a problem gettinga list of all available portals.





FMV3135E The removal of iSCSI Portal 'target'failed with a Windows error of (error)

Explanation: The iSCSI Service cannot remove theiSCSI Portal.



FMV3136E The mount ID was not specified in thecleanup operation.

Explanation: The -MOUNTID parameter must bespecified to perform a 'mountcleanup' operation.


User response: Use the query "dsmc q vm <name>-vmrestoretype=mount" command to get the correctmount ID for the cleanup

FMV3137W 'VMNAME' mount completed witherrors.

Explanation: The mount operation for the specifiedvirtual machine completed with errors. Only a subsetof the virtual machine's disks are ready for a file-levelrestore operation.

System action: The VM disks that failed werereported in previous messages.

User response: Read the previous error messages forthe cause of each failure.

FMV3138E The unmount of the volumes failedduring the cleanup operation of mountID mountid

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes.


User response: See the output from the previousoperations to identify the cause of the error.

FMV3139E The attempt to unmount the disk failedwith Windows error (error).

Explanation: The Windows API call failed to unmountthe disks.


User response: See the Microsoft documentation forinformation to correct this issue; search thedocumentation for this Windows error.

FMV3140E The connection to the following iSCSItargets failed: 'target_list'.

Explanation: The iscsiadm command-line interfacewas not able to connect to the specified iSCSI targets,from the Linux mount proxy machine.


User response: If the target is already connected onthe Linux mount proxy machine, log out from thetarget, for example: iscsiadm -m node -T targetname--logout Also, verify that the iSCSI server address iscorrectly specified.

FMV3141W Mounting the following devices failed:'device_list'.

Explanation: It was not possible to mount thespecified devices on the Linux mount proxy machine.

System action: The operation continues to mount theother devices.

User response: Perform a cleanup, or try to manuallyunmount the devices on the Linux mount proxymachine.

FMV3142E The Windows Virtual Disk Serviceencountered an error. The Windowserror is (error)

Explanation: The Windows Virtual Disk Service is notworking correctly.


User response: See the Microsoft documentation forinformation to correct this issue. Searchhttp://technet.microsoft.com/en-US/windowsserverfor Virtual Disk Service troubleshooting information.

FMV3143W The ISCSI service is not running. Itsstate is 'state'.

Explanation: The ISCSI Service is not running.

System action: The service maybe suspended,however operations cannot continue.

User response: Start the ISCSI service.

FMV3144W The ISCSI service is not running. Filelevel restore mount operations will notwork.

Explanation: The ISCSI Service is not running. Thisservice is required on the Windows and Linux mountproxy for file level restore mount operations. Full VMinstant access and instant restore are not affected.



System action: Mount operations for file level restorecannot continue.

User response: Start the ISCSI service if you want toperform a file level restore operation. For VM instantaccess and instant restore no action is required.

FMV3145E A Windows API call has failed.

Explanation: A Windows API call has failed.

System action: Operations cannot continue.

User response: See the dsmerror.log for moreinformation.

FMV3146E The cleanup operation to unmount thevolume volume failed. The mounted filesystem is busy.

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes onthe Linux mount proxy machine.


User response: Ensure the file system is not in useand then try the cleanup operation again, or manuallyunmount the volume on the host.

FMV3147W The iSCSI Target 'iscsi_target'wasdisconnected successfully, but theattempt to delete the target failed.

Explanation: It was not possible to delete the objectafter the target was disconnected.


User response: Try to manually delete the object onthe Linux machine. For example: iscsiadm -m node -Ttargetname -o delete

FMV3148W The iSCSI Target 'iscsi_target' wasalready connected.

Explanation: The target was already connected on theLinux mount proxy machine. This error can occur if acleanup was not perfomed, or if the cleanup was onlypartially successful.


User response: The Linux mount proxy machine triedto reuse the already connected targets. If the volumesare not correctly mounted, manually disconnect thetargets on the Linux mount proxy machine. Forexample: iscsiadm -m node -T targetname --logout;iscsadm -m node -T targetname -o delete

FMV3149E The iSCSI target 'target' failed todisconnect from the Linux machine. Themessage from the iscsiadmcommand-line interface is:message_output

Explanation: The iscsiadm command-line interfacewas unable to disconnect the specified iSCSI targetfrom the Linux machine.


User response: See if the target is alreadydisconnected on the Linux machine, or try to manuallydisconnect it. For example, iscsadm -m node -Ttargetname --logout Verify that the iSCSI server addressis correctly specified.

FMV3150W The block device 'block_device' of type'device_type' failed to mount. The systemmessage is: 'system_message'

Explanation: It was not possible to mount one ormore devices on the Linux machine.

System action: The operation continues to mount theother devices.

User response: Perform a cleanup, or try to manuallyunmount the devices on the Linux machine.

FMV3151E The initiator.iscsi file does not exist orcannot be opened.

Explanation: The file does not exist or cannot beopened.


User response: The ISCSI service may not be installed.

FMV3152E The initiator.iscsi file does not have avalid initiator id entry.

Explanation: No ISCSI Initiator ID exists.


User response: The ISCSI servoce may not beinstalled.

FMV3153E The mount cleanup completed witherror for mount ID 'mountid' of virtualmachine 'VMNAME'; Error log 'errlog' isavailable on 'machinename'.

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes. Themounted file systems may be busy. See the error log toidentify the cause of the error.


User response: Ensure the file systems are not in use



and the cleanup or manually unmount the volumes onthe host.

FMV3154E The ISCSI service is not installed.

Explanation: The ISCSI Service is not installed.


User response: Install the ISCSI service for yourplatform.

FMV3155I The Windows data mover is 'name' (ip)

Explanation: The DNS name and the IP of theWindows data mover.


User response: This information can be used todetermine if hostname and IP of the Windows datamover are correctly resolved. The information can helpif the iSCSI connection is not working as expected.

FMV3156I The iSCSI server address used is 'ip'

Explanation: This message returns the IP address ofthe iSCSI server.


User response: This information can be used todetermine if the IP address of the iSCSI server addressis correctly resolved. The information might help youtroubleshoot problems if the iSCSI connection is notworking as expected.

FMV3157I The Linux data mover is 'name' (ip)

Explanation: The DNS name and the IP address of theLinux data mover.


User response: This information can be used todetermine if hostname and IP of the Linux data moverare correctly resolved. The information might help youtroubleshoot problems if the iSCSI connection is notworking as expected.

FMV3158W The attempt to create the Windowsshare failed with Windows error (error).The share is not created.

Explanation: The creation of the Windows share failedwith the given user/group name.

System action: The Windows share is not created. Theoperation continues.

User response: One common reason for failures is thatthe specified user/group does not exist. Ensure that theWindows user or group name exists and is accessibleon the Windows data mover. If this is a domain user orgroup, the Windows data mover has to be part of that

domain. If this does not resolve the problem, see theappropriate Microsoft Documentation for informationabout this error code.

FMV3159E The attempt to remove the WindowsShare failed with Windows error (error).

Explanation: A Windows API call failed to remove theWindows Share.



FMV3160W The attempt to export Linux file systemfailed with error: NFS service is notrunning.

Explanation: exportfs command failed to make thedirectory on the Linux mount proxy available for NFSclients to mount.

System action: The operation continues withoutcreating the NFS export.

User response: Resolve the error on the Linux mountproxy. Manually export the directory.

FMV3161E The attempt to unexport Linux filesystem failed with error: NFS service isnot running.

Explanation: exportfs command failed to unexport thedirectory on the Linux mount proxy.


User response: Resolve the error on the Linux mountproxy. Manually unexport the directory.

FMV3162I The Mount cleanup of VM 'VMNAME'with mount id 'Id' and snapshot date'date time' completed.

Explanation: The mount cleanup operation for thespecified virtual machine completed.


User response: None

FMV3163W The Linux Operating System is not atthe minimum level. Mount operationsmay not complete successfully.

Explanation: The Linux Operating System is not at theminimum level.

System action: Mount operations may not completesuccessfully.

User response: Upgrade the Linux operating systemto at least the minimum level.



FMV3164W The minimum level for 'os' is 'level'. Yourcurrent level is 'actual'.

Explanation: The Linux Operating System is not at theminimum level.


User response: Upgrade the Linux operating systemto at least the minimum level.

FMV3165W A Package installed on the LinuxOperating System is not at theminimum level. Mount operations maynot complete successfully.

Explanation: A Package installed on the LinuxOperating System is not at the minimum level.


User response: Upgrade the package to at least theminimum level.

FMV3166W The minimum level for package 'package'is 'level'. Your current level is 'actual'.

Explanation: A Package installed on the LinuxOperating System is not at the minimum level.


User response: Upgrade the package to at least theminimum level.

FMV3167E IBM Tivoli Storage Manager RecoveryAgent service is not installed.

Explanation: IBM Tivoli Storage Manager RecoveryAgent service is not installed.


User response: Ensure that IBM Tivoli StorageManager Recovery Agent is correctly installed andconfigured.

FMV3168E IBM Tivoli Storage Manager RecoveryAgent service is not running.

Explanation: IBM Tivoli Storage Manager RecoveryAgent service is not running.


User response: Start IBM Tivoli Storage ManagerRecovery Agent service. The Recovery Agent can bestarted using "net start RecoveryAgent" or byreferencing TSM Recovery Agent in services.msc.

FMV3169E The mount proxy's operating system isnot Windows 2008, or a newer, operatingsystem.

Explanation: The Windows operating system is not atthe minimum level.


User response: Upgrade the Windows mount proxy toa supported operating system.

FMV3170W The attempt to export Linux file systemfailed with error: exportfs commandfailed.

Explanation: exportfs command failed to make thedirectory on the Linux mount proxy available for NFSclients to mount.

System action: The operation continues withoutcreating the NFS export.

User response: Resolve the error on the Linux mountproxy. Manually export the directory.

FMV3171E The attempt to unexport Linux filesystem failed with error: exportfscommand failed.

Explanation: exportfs command failed to unexport thedirectory on the Linux mount proxy.


User response: Resolve the error on the Linux mountproxy. Manually unexport the directory.

FMV3172T Restoring virtual machine 'source' to newVM with name 'destination'.

Explanation: The specified virtual machine will berestored as a new vm with a new name.

System action: None


FMV3173E The Linux devices failed to mountcorrectly.

Explanation: The Linux devices failed to mountcorrectly.

System action: Mount operations did not notcomplete successfully.

User response: Verify that the Linux mount proxyserver can communicate with the TSM server.



FMV3175E The VM mount cleanup failed.

Explanation: An error occurred during the mountcleanup operation.


User response: Check the command-line output forthe messages that specify what problems wereencountered during the operation.

FMV3176W Unable to locate the Windows user orgroup named 'name'. The share is notcreated.

Explanation: Tivoli Storage Manager was unable tomap the specified user or group name to a Windowssecurity identifier.

System action: The Windows share is not created. Theoperation continues.

User response: One common reason for this messageis that the specified user or group does not exist.Ensure that the Windows user or group name existsand is accessible on the Windows data mover. If this isa domain user or group, the Windows data mover hasto be part of that domain.

This message can also indicate that the Windows datamover is not able to access the active directory domainserver. Ensure that network problems are notpreventing the Windows data mover fromcommunicating with the active directory domain server.

FMV3177E No iSCSI target was connected. Checkyour iSCSI options for backup-archiveclient.

Explanation: No iSCSI target was found or connectedon the Linux mount proxy machine.

System action: The operation is rolled back.

User response: Check that iSCSI is setup correctly onyour Windows as well as your Linux mount proxy. Onecommon reason for a failure is that theVMISCSIServeraddress option is not specified or is setincorrectly in the options file of the Windows datamover.

FMV3178E Volume 'volume' of type 'file_system_type'has not been unmounted. Systemmessage: 'system_message'

Explanation: An error occurred during the mountcleanup operation while unmounting the volumes onthe Linux mount proxy machine.


User response: Ensure the file system is not in useand then try the cleanup operation again, or manuallyunmount the volume on the Linux mount proxy.

FMV3179W Another folder share with the samename 'name' already exists.

Explanation: Tivoli Storage Manager was unable tocreate a folder share with the specified name because ashare with that name already exists

System action: The folder share is not created. Theoperation continues and the VM disks are mounted forfile-level recovery on the mount proxy.

User response: Use operating system commands tocreate the share of the folder with a unique name anddelete it before running the dismount operation.

FMV3180W The parameter 'name' contains charactersthat are not allowed and have beenremoved. Resulting value is 'new'

Explanation: Some characters cannot be used on multiplatform environments. To solve compatibly problemsonly a limited set of characters are allowed on thisspecific parameter.

Parameter "-MOUNTPoint" is restricted at[a-z][A-Z][0-9][:][/][\][_]

Parameter "-MOUNTTag" is restricted at[a-z][A-Z][0-9][_]

Parameter "-EXPORTParameter" is restricted onWindows at [a-z][A-Z][0-9][ ][-][_][\][@]

Parameter "-EXPORTParameter" is restricted on Linuxat [a-z][A-Z][0-9][.][:]

System action: The operation continues with modifiedparameter.

User response: None

FMV3181E The registry keyHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy is set to an othervalue than 3.

Explanation: If the registry keyHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy is set to an other value than 3 it can be thatthe machine hangs during a mount operation. Changethe value to 3 and reboot the machine.


User response: The registry keyHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\partmgr\Parameters\CrPolicy is not documented by Microsoft. Sometimesthis key is set to a value other than 3 what can lead toproblems with the mount operation. Set the value to 3and reboot the machine.



FMV3182E The mount cleanup operation timed outwaiting minutes minutes for responsefrom Linux Mount Proxy.

Explanation: The Windows Mount Proxy didn'treceive any response from Linux Mount Proxy withinthe given timeout. The Linux Mount Proxy is possiblein hanging state.


User response: Check the status of Linux MountProxy machine and mount proxy trace file for moredetails. In the case of a complete system hang onumount, a reboot followed by manual mount cleanupof the Linux mount proxy machine may be required.

FMV3401W The entity name is invalid.

Explanation: A volume with this name could not befound or is not suitable for server-free operations.


User response: Specify the correct name.

FMV3402W name: A system call func failed with coderc.

Explanation: An error occurred while obtaininginformation from the operating system. The volumeinformation could not be obtained.

System action: Processing can continue if theinformation being obtained is not critical for theoperation or if it is expected behaviour in the context ofthe operation being performed.


FMV3403W Volume name cannot be opened forreading. System error code is err.

Explanation: The named volume could not be opened.Examples of why this can occur include, but are notlimited to: the device is not a valid system device, thedevice is locked by another application, or the userdoes not have correct or permissions. The operatingsystem error code shown in the message indicates thespecific reason for the failure.


User response: Use your operating system's tools toobtain the description of the error code. Also check theerror log for any other messages that might indicate areason for the failure. Try to correct any indicatedproblems, then try the operation again. If the problempersists, contact IBM technical support for furtherassistance.

FMV3404W An error occured reading volume name.

Explanation: The named volume could not be read.Examples of why this can occur include, but are notlimited to: the data being read is outside the validrange of the volume, or the device is locked by anotherapplication. The operating system error code shown inthe message indicates the specific reason for the failure.

System action: If server-free data movement is used,processing continues using non-server-free datamovement. Otherwise processing stops.


FMV3405W File system fs on volume name isunknown.

Explanation: The file system on the volume is notsupported for the operation being performed.

System action: If server-free data movement is used,processing continues using non-server-free datamovement. Otherwise processing stops.


FMV3407W name is not local.

Explanation: The drive or filesystem is not local and isnot suitable for image backup.


User response: Specify a volume that is local.

FMV3408E System call 'umount' failed for volume'volume' with errno='error'. Please takesuitable action based on errno and retrythe operation.

Explanation: Umount failed for the specified volumewith the indicated errno. Please take suitable actionbased on errno and retry the operation.


User response: Check errno for umount failure andtake corrective action before retrying the operation.



FMV3409W An error occurred writing to volumename.

Explanation: Tivoli Storage Manager could not writeto the named volume. Examples of why this can occurinclude, but are not limited to: the data being written isoutside the valid range of the volume, or the device islocked by another application. The operating systemerror code shown in the message indicates the specificreason for the failure.



FMV3410E The operating system refused a TivoliStorage Manager request for memoryallocation.

Explanation: Tivoli Storage Manager requires access tomemory in order to store information as processingproceeds. In this case, more memory was requestedthan the operating system would allocate. Possiblereasons include:





User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into serveral smaller units. Forexample, if a file specification contains several highlevel directories, run the Tivoli Storage Manager taskserially for each directory. If the Tivoli Storage Managertask is an incremental backup, use the option"-memoryefficientbackup=yes".



FMV3411E Invalid arguments were passed tofunction name.

Explanation: The named function did not receivecorrect arguments to proceed. Please check error log for

additional errors following this one for furtherexplanation.


User response: Retry the operation. If problem persistscontant your Tivoli Storage Manager administrator.

FMV3412I DiskMapper does not support name forentity name.

Explanation: The requested function is notimplemented in DiskMapper at this time. Please reportthis error to your Tivoli Storage Manager administrator.


User response: Contact your Tivoli Storage Manageradministrator.

FMV3413I DiskMapper object 'name' type 'name' isnot valid.

Explanation: The named object is not valid on theoriginating client system.


User response: Retry the operation. If the problempersists, review the client error log for other messagesthat might be related to this problem. Contact yourTivoli Storage Manager administrator for additionalhelp.

FMV3414I Disk 'name' is not part of any containerdefined on the system.

Explanation: None.

System action: None. This is informational message.


FMV3415W At least one of the disk containing datafor 'name' has bad blocks.

Explanation: One or more physical disks containingdata blocks of the above object has bad blocks and therequested operation can not continue.

System action: The system may find a work-around tocomplete the requested operation, pleasecheck consolelog and error log for additional information oncorrective actions taken or suggested user action.

User response: Depending on the operation TivoliStorage Manager may suggest an alternate way tocomplete the operation. Check your error log, schedlog, or console log for additional information.



FMV3416E The volume 'name' is currently in use byother process.

Explanation: The operation requires exclusive accessto the volume. The most likely cause of this failure isthat other process on the system has the volumeopened.


User response: Check applications running on yoursystem to ensure that volume is not opened by any ifthe process and then retry the operation.

FMV3417W name: A system call func failed with coderc - strerror

Explanation: An error occurred while obtaininginformation from the operating system. The volumeinformation could not be obtained.

System action: Processing can continue if theinformation being obtained is not critical for theoperation or if it is expected behaviour in the context ofthe operation being performed.


FMV3418W Memory allocation request for imagebackup operation was refused by theoperating system.

Explanation: Tivoli Storage Manager requires access tomemory in order to store information about usedblocks of a file system. In this case, more memory wasrequested than the operating system would allocate.

System action: If imagegapsize is too small for adedicated filesystem and Tivoli Storage Manager facesout-of-memory condition then Tivoli Storage Managerautomatically switches to full volume backup.Operation continues with imagegapsize = 0.

User response: Some recommendations to avoid theout-of-memory condition:

v check to see if the memory resource limit is too lowby entering the following command: ulimit -aThen you can ask the UNIX system root user toincrease memory limit.

v increase the value of the imagegapsize option. Thebigger imagegapsize is used, the less memory isneeded for image backup, but more unused data issent to server. And vice versa: the smallerimagegapsize is used, the more memory is neededfor backup, but less unused data is sent to server.The outcome also depends much on how data isspread on the volume.

FMV4000E Error processing 'filespace-name': filespace does not exist.

Explanation: The specified file space (domain) isincorrect or does not exist on the workstation. If themessage results from the BACKUP IMAGE commandwith the -MODE=INCREMENTAL option, it means thatyou have entered the name of a raw logical volume.The MODE=INCREMENTAL option is not valid forraw logical volumes.


User response: Try the operation again, specifying anexisting domain (drive letter or file system name). Ifthe message resulted from improper use of theMODE=INCREMENTAL option, try the commandagain, omitting that option.

FMV4001E The file space for domain 'filespace-name'could not be found on the TivoliStorage Manager server.

Explanation: The specified file space was expected tobe found on the server, but it no longer exists. It ispossible that a command was issued to delete the filespace from the server while the current operation wasin progress.

System action: Tivoli Storage Manager processingstops.

User response: Try the operation again. If the problemrecurs, check the error log for any other messages thatmight indicate a reason for the failure. Try to correctany indicated problems, then try the operation again. Ifthe problem persists, contact IBM technical support forfurther assistance.

FMV4002E Error processing 'filespace-name': volumelabel does not exist

Explanation: The selected drive does not have a label.

System action: Tivoli Storage Manager is unable to dothe requested operation without a drive or labelentered.

User response: If the drive is a floppy drive, place adisk with a volume label in it and retry the operation.If the disk is a hard drive, ensure the drive has avolume label, and retry the operation.

FMV4003E Error processing 'filespace-name':duplicate volume label encountered

Explanation: The selected drive has a duplicatevolume label. Because Tivoli Storage Manager uses thevolume label to keep track of backup/archiveinformation, it cannot back up or archive files from adrive with a duplicate volume label.

System action: Tivoli Storage Manager cannot selectthe drive.



User response: If the volume needs to be available tothe system, exit Tivoli Storage Manager, and assign avolume label to the drive. Restart Tivoli StorageManager and retry the operation.

FMV4004E Error processing 'filespacenamepath-namefile-name': destination fileor directory is write locked

Explanation: The file or directory being restored orretrieved from the server cannot be written to becausethe destination is write locked. Another operationmight have the file open and will not allow it to beupdated.


User response: Either determine which operation hasthe file write locked, or restore the file to another nameor location.

FMV4005E Error processing 'filespacenamepath-namefile-name': file not found

Explanation: The file being processed for backup,archive or migrate no longer exists on the client.Another process deletes the file before it can be backedup, archived or migrated by Tivoli Storage Manager.



FMV4006E Error processing 'filespacenamepath-namefile-name': directory pathnot found

Explanation: The operating system returned a "pathnot found" status when IBM Tivoli Storage Managerattempted to access the directory. You either havespecified a directory that does not exist, as shown inthe message (path-name), or the directory beingprocessed no longer exists on the client because anotherprocess deleted it before it could be backed up orarchived by IBM Tivoli Storage Manager.

System action: The directory is skipped, processingcontinues

User response: Recheck all spelling and punctuation,particularly the placement of directory delimiters (forexample, "\"). Correct the syntax if it is incorrect, thenretry the operation. Ensure that the path is specifiedcorrectly and that the directory actually exists. Retrythe command with the corrected path and directoryname. If you cannot correct the directory name, use theExclude option to exclude the directory from theoperation.

FMV4007E Error processing 'filespacenamepath-namefile-name': access to theobject is denied




FMV4008E Error processing 'filespacenamepath-namefile-name': file istemporarily unavailable

Explanation: File is temporarily unavailable.


User response: Check and see if file is locked by otherprocess. If not, retry the command.

FMV4009E Error processing 'filespacenamepath-namefile-name': disk fullcondition

Explanation: No more files can be restored orretrieved because the destination disk is full.

System action: The client prompts you for action:

v Retry this object

v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Create some free space on the destination diskbefore you retry the operation. Another option is torestore or retrieve the file to another disk.

FMV4010E Error processing 'filespacenamepath-namefile-name': stale NFS handle

Explanation: An NFS file system becomes stale.


User response: Verify that the NFS file system ismounted. If the problem persists, unmount andremount the file system, then try the operation again.

FMV4011E Error processing 'filespacenamepath-namefile-name': no file handlesavailable



User response: Either free some file handles by ending



other processes, or modify your system setup to allowfor more files to be open at the same time.

FMV4012E 'filespace namepath-namefile-name' alreadyexists. It will be skipped.

Explanation: The client tried to restore or retrieve thespecified file, but the file already existed in the targetrestore location and the user chose not to replace theexisting file.

System action: The file is skipped, a message islogged in dsmerror.log, and restore or retrieveprocessing continues with the next object.

User response: The file was skipped because eitherREPLACE NO was in effect, causing all existing filesand directories to be skipped, or REPLACE PROMPTwas in effect, and when prompted, the user chose toskip this file or all existing directories and files. Noadditional action is necessary if the decision to skip thefile was deliberate. Otherwise the operation can beretried using either REPLACE ALL REPLACEPROMPT.

FMV4013E Error processing 'filespacenamepath-namefile-name': invalid filehandle

Explanation: An internal system error occurred. A fileoperation failed because an invalid file handle waspassed.


User response: Report the problem to your systemadministrator, and then retry the operation.

FMV4014E Error processing 'filespacenamepath-namefile-name': unknown systemerror (error-code) encountered. Programending.

Explanation: An unrecognized and unexpectederror-code occurred within the client program. This is aprogramming failure and the client program ends.


User response: Try the operation again. If the problemcontinues, report the error to your Tivoli StorageManager administrator.

FMV4015E Error processing 'filespacenamepath-namefile-name': unexpectedTivoli Storage Manager error (error-code)encountered

Explanation: An unexpected error occurred. Thismight be a low-level system or communication errorthat Tivoli Storage Manager cannot handle or recoverfrom.


User response: Try the operation again. If the problemcontinues, look for other indications of systemproblems to determine where the problem exists. Mostsystems have error or event logs which may containadditional information. See your system administratoror Tivoli Storage Manager administrator for furtherhelp.

FMV4016E Error processing 'filespacenamepath-namefile-name': file is beingexecuted; write permission denied

Explanation: The current file cannot be opened towrite to because it is currently being run by anotheroperation.


User response: Stop the operation that is running thefile and retry the operation, or restore or retrieve thefile to a different name or directory.

FMV4017E Error processing 'filespacenamepath-namefile-name': too manysymbolic links were detected whileresolving name




FMV4018E Error processing 'filespacenamepath-namefile-name': file name toolong

Explanation: The file name specified is too long to behandled by Tivoli Storage Manager.

System action: File is skipped.

User response: See the appropriate Using theBackup-Archive Client book for the particular operatingsystem, for the file names that are handled by TivoliStorage Manager.

FMV4019E Error processing 'filespacenamepath-namefile-name': file system islocked by system

Explanation: File system cannot be accessed because itis locked by the system.

System action: Tivoli Storage Manager cannotcomplete the operation.




FMV4020E The data format for object 'filespacenamepath-namefile-name' is unknown. Theunknown format usually occurs whenthe file was backed up or archived by alater version of IBM Tivoli StorageManager.

Explanation: When a file is backed up or archived,IBM Tivoli Storage Manager includes some additionalinformation about the file. This message is issued ifIBM Tivoli Storage Manager cannot recognize theinformation during a restore or retrieve operation. Themost likely cause is that the file was backed up orarchived with a newer version of IBM Tivoli StorageManager. If the file was backed up from acase-preserving but not case-sensitive file system, thefile name might be displayed with incorrect casing. Theincorrect casing does not otherwise affect processingsince the file is skipped.

System action: The file is not restored or retrieved.Processing continues with the next file.

User response: Try the restore or retrieve operationagain with a current version of the IBM Tivoli StorageManager client software. If the problem persists, contactIBM technical support for further assistance.

FMV4021E Error processing 'filespacenamepath-namefile-name': file system notready

Explanation: The file system/drive was not ready foraccess.


User response: Ensure that the drive is available toTivoli Storage Manager, and then retry the operation.

FMV4022E Error processing 'filespacenamepath-namefile-name': file system isinvalid.

Explanation: The drive was not available for access.


User response: Ensure that the drive is operational,and then try the operation again. If this is unsuccessful,check the error log.

FMV4023E Error processing 'filespacenamepath-namefile-name': file input/outputerror

Explanation: An error was found while reading fromor writing to the file.


User response: Check your system to ensure that it isoperating properly. For OS/2, run CHKDSK /F for thefailing drive which can be found in dsmerror.log.

FMV4024E Error processing 'filespacenamepath-namefile-name': file write error

Explanation: An error was found while writing to thefile.



FMV4025E Error processing 'filespacenamepath-namefile-name': file exceeds useror system file limit

Explanation: A file being backed up/restored orarchived/retrieved exceeds system set limits for thisuser. Shown below are the filesize limits correspondingto various platforms.

AIX 68,589,453,312 (64GB)

HP-UX 1,099,511,627,775 (1TB-1)

Linux 2,147,483,647 (2GB)

Mac pre-OS92,147,482,624 (2GB-1K)

Mac OS918,446,744,073,709,551,616 (16EB)

NetWare4,294,963,200 (4GB -4KB)

NUMA-Q® DYNIX/ptx®

4.5 1,095,216,660,480 (1TB-4GB)

OS/390®

4,294,967,295 (4GB)

SGI 18,446,744,073,709,551,615 (16EB-1)

Solaris 2.6 or higher1,099,511,627,775 (1TB-1)

Tru64 UNIX1,099,511,627,776 (1TB)

UnixWare2,147,483,647 (2GB)

Windows ME (FAT32)4,294,967,295 (4GB)

Windows NT/2000 (NTFS)17,592,185,978,880 (16TB-64K)


User response: Ensure that the system limits are setproperly.

FMV4026W Error processing 'filespacenamepath-namefile-name': size of 'file-size'exceeded the maximum file size limit onyour system

Explanation: You tried to restore or retrieve a file that



has exceeded the maximum file size limitation on yoursystem.


User response: Restore or retrieve this file on a systemthat supports the file size. See your systemadministrator.

FMV4027S Error processing 'filespacenamepath-namefile-name': internal programmessage 'value' encountered

Explanation: An unexpected catastrophic programfailure occurred, indicated by value.


User response: Retry the operation. If the problemcontinues, see your system administrator or servicerepresentative.

FMV4028E Error processing 'filespacenamepath-namefile-name': cannot createfile/directory entry

Explanation: The directory path for files beingrestored or retrieved cannot be created.


User response: Ensure that you have the properauthorization to create the directory for file beingrestored or retrieved.

FMV4029E Error processing 'filespacenamepath-namefile-name': unable to builda directory path; a file exists with thesame name as a directory

Explanation: Tivoli Storage Manager tried to create adirectory path, but is unable to because a file exists thathas the same name as a directory.


User response: Remove the file that has the samename as the directory. Refer to the last restore/retrieveoperation and check all directories along the path.

FMV4030E Error processing 'filespacenamepath-namefile-name': disk space limitfor this process reached

Explanation: The disk space allocated for the clientowner is full.


User response: Free up disk space and retry therestore or retrieve operation.

FMV4031E Error processing'file_space_namepath_namefile_name'. Nameexceeds an internal Tivoli StorageManager limit.

Explanation: During a file operation, Tivoli StorageManager encountered a filename where at least onecomponent of the file name (file_space_name,path_name or directory_name or file_name) exceededan internal Tivoli Storage Manager maximum. Theinternal Tivoli Storage Manager limits should not beconfused with the operating system limits forfile_space_name, path_name or directory_name,file_name.

Shown below are the Tivoli Storage Manager internalfile name limits for various platforms.

AIX HP-UX SolarisFile_space_name 1024Path_name or directory_name 1023File_name 256

LinuxFile_space_name 1024Path_name or directory_name 768File_name 256

Windows XP/2000/2003File_space_name 1024Path_name or directory_name 248File_name 248


User response: Reduce the size of the filename so thatit is smaller that the Tivoli Storage Manager internallimits.

FMV4032E Error processing 'filespacenamepath-namefile-name': file is notcompressed.

Explanation: A file that was flagged as compressedwas not compressed, and the system failed.


User response: See your system administrator toreport this problem. This error is a system failure.

FMV4033E Error processing 'filespacenamepath-namefile-name': file compressedon a different client machine that hasmore memory

Explanation: You are trying to restore a file that wasbacked up and compressed on another clientworkstation that had more memory than your clientworkstation. You cannot restore this file. When the fileis restored, it is expanded and your workstation doesnot have enough memory.




User response: Obtain a machine with more memoryand retry the operation.

FMV4034E Error processing 'filespacenamepath-namefile-name': unknown systemerror

Explanation: An unknown error occurred. This mightbe a low-level system or communication error thatTivoli Storage Manager cannot handle or recover from.


User response: Retry the operation. If the problemcontinues, determine where the problem exists. Seeyour system administrator for further help.

FMV4035W File 'filespace namepath-namefile-name'currently unavailable on server.

Explanation: You tried to restore or retrieve a file thatis currently not available from the Tivoli StorageManager server.

System action: Tivoli Storage Manager Cannot restoreor retrieve the file.

User response: Try to restore or retrieve after the filewas made available on the server. See your systemadministrator.

FMV4036E An error occurred saving the registrykey.

Explanation: The active registry key cannot be copiedto the ADSM.SYS staging directory.

System action: Registry backup operation terminates.

User response: Check the space available on theWindows boot partition to ensure there enough spaceto contain a copy of the Windows registry. This mightrequire several megabytes of free space. Also check theWindows permissions on the ADSM.SYS stagingdirectory and ensure that the Windows user underwhich you are running Tivoli Storage Manager has fullaccess to that directory and its contents.

FMV4037E Object 'file-namefile-namefile-name'changed during processing. Objectskipped.

Explanation: The specified file-name was skippedduring backup, archive, or migrate because it waschanging during the attempt to process it.

System action: Tivoli Storage Manager skipped theobject.

User response: If you want the file backed up,archived, or migrated, retry the operation. If it fails,determine why the object is being changed. For moreinformation on backing up, archiving, or migratingchanging objects, see your system administrator.

FMV4038E An error occurred processing file system'filespace name'.

Explanation: File system 'filespace name' is corrupted orcontains one or more corrupted directories and cannotbe processed.

System action: File system is skipped.

User response: Check your system to ensure that it isoperating properly. For the Windows environment, runCHKDSK utility for the failing drive. More informationabout corrupted directories can be found indsmerror.log.

FMV4039E Error processing 'filespacenamepath-namefile-name': compressed fileis corrupted and cannot be expanded.

Explanation: The compressed file cannot be expandedcorrectly due to one of the following reasons:

v There is a problem on the tape.

v There is a communications problem.

v The compressed file was corrupted on the TSMServer.


User response: 1) The compressed file is corruptedbecause there is a problem on the tape. To know if thisis the problem, please issue the following command onthe TSM Server: audit volume <volume_name> fix=noIf there is any problem reported, you could move thedata from that volume to a new one (see commandMOVE DATA) and try again the restore. 2) There arecommunications problems between the TSM Server andthe TSM Client and the results is that the file iscorrupted during the transmission. If you use a gigabitethernet adapter on the Server please upgrade the carddriver (AIX platform) or add provided by SUNsuggested changes to some system network optionswhich have resolved this problem (SUN platform). 3)Please verify with your network support if during therestore there are no any problems between the TSMClient/Server that is originating the file corruption.

FMV4040E Error processing 'filespacenamepath-namefile-name': file systemfilespace name has exceeded its spacemanagement quota.

Explanation: Tivoli Storage Manager detects that thefile system has exceeded its quota. No more data canbe migrated out of this file system.

System action: Tivoli Storage Manager will notmigrate files from this file system.

User response: Recall some files, or ask the systemadministrator to increase the quota for this file system.



FMV4042E Object name 'filespacenamepath-namefile-name' contains one ormore unrecognized characters and is notvalid.

Explanation: The file name, directory name, orvolume label syntax is incorrect.


User response: Check the disk for errors.

FMV4044E Error processing 'filespace-namepath-namefile-name': Case-sensitive nameconflict exists.

Explanation: While processing the specified file on theworkstation, another file name was encountered with asimilar name which only differed in case. TheBackup-Archive client does not allow names whichdiffer only in case on this platform and cannotguarantee the integrity of the file, so the file is skipped.

System action: This object will be skipped.

User response: Rename the file in question to aunique name.

FMV4045E Error processing 'filespace-namepath-namefile-name': Case-sensitive nameconflict exists. The directory tree will beskipped.

Explanation: While processing the specified file on theworkstation, another object name was encountered witha similar name which only differed in case. TheBackup-Archive client does not allow names whichdiffer only in case on this platform and cannotguarantee the integrity of the file, so the directory andall of the objects contained within it are skipped.


User response: Rename the file in question to aunique name.

FMV4046E There is an error processing'filespace-namepath-namefile-name': theobject is corrupted and unreadable.

Explanation: You tried to read from or write to a fileor directory that is corrupted. The corrupted file isskipped. If this is a directory, the objects contained inthe directory and its subdirectories are skipped.


User response: Check your system to ensure that thefilespace is not corrupted by using system tools likechkdsk (Windows) or fsck (UNIX).

FMV4047E There is a read error on'file-namefile-namefile-name'. The file isskipped.

Explanation: The specified file-name was skippedduring backup archive because the file could not beread.

If you are performing a JFS2 snapshot based operation,it is possible that the snapshot was not large enough tocontain all the changes made to the filesystem after thesnapshot was created. This could cause the snapshot tobecome invalid thereby preventing Tivoli StorageManager client from reading the snapshot.

System action: Tivoli Storage Manager skipped thefile.


If you are performing a JFS2 snapshot based operation,please use the default snapshotcachesize of 100% andensure that the volume group has sufficient disk spaceto allocate snapshots at least as large as the file systemand retry the operation.

FMV4048W LAN-Free connection failed.

Explanation: ENABLELANFREE option is set to YESfor this session, but an attempt to establish LAN-Freeconnection failed.

System action: The Tivoli Storage Manager client willfailover to non LAN-Free support.

User response: Review the Tivoli Storage Managererror.log for LAN-Free failures. Check your LAN-Freesetup and verify that all components are workingproperly.

FMV4049I Established LAN-Free connection.

Explanation: ENABLELANFREE option is set to YESfor this session and the Tivoli Storage Manager clientsuccessfully established LAN-Free connection withserver, after the LAN-Free connection was broken.

System action: The Tivoli Storage Manager client willcommunicate with the server via LAN-Free.

User response: Review the Tivoli Storage Managererror.log for LAN-Free errors. Check your LAN-Freesetup and verify that all components are workingproperly.

FMV4050W Scheduled action 'schedule-action' did notexecute for schedule 'schedule-name' asthe Tivoli Storage Manageradministrator has been disabled fromexecuting the scheduled action on theclient.

Explanation: One or more of the client options -



schedcmddisabled, srvprepostscheddisabled,srvprepostsnapdisabled, restretrscheddisabled, havebeen set to YES on the client thereby preventing theTivoli Storage Manager administrator from executingone of the following scheduled actions on the client -preschedule, postschedule, presnapshot, postsnapshotor scheduled operating system commands, restore orretrieve operations.

System action: The scheduled operation will not beexecuted and a message will be logged to TivoliStorage Manager Server indicating this.

User response: None required.

FMV4051E Error processing 'filespacenamepath-namefile-name': The decryptionoption is in effect, but the user IDunder which back-up or archive is beingrun is not authorized to decrypt thisencrypted-file-system (EFS) file.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The option is specifiedto back-up or archive the file in decrypted form. Theuser ID under which the back-up or archive is beingrun does not have decryption rights for this file.


User response: There are three possible ways to makedecryption work:

v Re-encrypt the file under the encryption key of agroup to which both the owner and theback-up/archive user IDs belong

v Add the back-up/archive user ID to the list of usersauthorized to decrypt this file

v Run the back-up or archive under the owner's userID, if possible

FMV4052E Error processing 'filespacenamepath-namefile-name':Encrypted-file-system (EFS) file cannotbe restored, because file system doesnot support restore from the raw-EFSback-up data, or possibly because therestore function does not have writeaccess to the directory.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The file was backed upin the raw encrypted format. Either the targetfilesystem does not support the encrypted format, orrestore does not have write access to the directory towhich the file is to be restored.

System action: The restore is terminated.

User response:

v The file cannot be restored to this location if the filesystem is not the AIX Enhanced Journaled FileSystem (JFS2)

v If the file is JFS2 but EFS is not enabled, then EFSmust be enabled before the file can be restored

v If the user ID under which restore is being run doesnot have write permission for the directory, thepermissions must be changed or the restore must berun under a different user ID

FMV4053E Error processing 'filespace path filename':The file cannot be restored because thefile system or operating system does notsupport the Encrypting File System(EFS) data.

Explanation: The specified object was backed-up asraw Encrypting File System (EFS) data. The client istrying to restore or retrieve the object to a destinationthat does not support the EFS data. The location mightnot support the EFS data for one of the followingreasons:

v The operating system does not provide the support,or is a release that does not include the support

v EFS support has not been activated on the operatingsystem

v The target file system does not support the EFS data

System action: The object is not restored or retrieved.Processing continues with the next object.

User response: If this file must be restored, restore itto an AIX operating system environment supportingEFS data.

FMV4054E Error processing 'filespacenamepath-namefile-name': The encryptionkey is not loaded.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The option is specifiedto backup or archive the file in decrypted form. Theencryption key, required to decrypt the file, is notloaded in the kernel keyring.


User response: There are three situations in which thisproblem can occur:

v You just performed initial activation of EFS on theAIX system, and have not logged out. AIX does loadthe keys for the session running at the time of initialactivation. Solution: Logout and login again.

v The login password has been changed recently, andyou normally run with the EFS password the sameas the login password. AIX does not automaticallychange the EFS password when you change the loginpassword. Solution: Issue 'efskeymgr -n' to set theEFS password to be the same as the login password.

v You need to run the decrypting backup when theEFS password is different from the login password.Solution: Issue 'efskeymgr -o ksh' to launch a newshell with the keys loaded. AIX will prompt you for



the EFS password as you launch the shell. Run thebackup from the new shell.

FMV4055E Cannot update file space 'filespace-name':the file space version on the TivoliStorage Manager server is notcompatible with this client

Explanation: The file space on the Tivoli StorageManager server is not compatible with this client. Thisis caused by performing a backup or archive operationwith a client and then using a down-level client andattempting a backup or archive operation targeting thesame file space. This problem occurs specifically after aWindows or AIX client V6.1 or higher performs abackup or archive operation and then a subsequentbackup or archive operation is attempted with a clientV5.5 or lower.


User response: Use the correct level of the client.

FMV4056E Object 'object-name' returned by the IBMTivoli Storage Manager server has ahigh-level name that exceeds themaximum length of 6000 characters. Thefile or directory cannot be processed.

Explanation: The IBM Tivoli Storage Manager serverreturned information about a backup or archive versionwith a high level name that exceeds 6000 characters.The high-level name is the directory path that containsthe object (file or directory).

This message is displayed when all of the followingconditions are true:

v The object was backed up or archived by a version6.1 or lower IBM Tivoli Storage Manager client.

v The object was backed up or archived to a version5.5 or lower IBM Tivoli Storage Manager server.

v IBM Tivoli Storage Manager client version 6.2 orhigher is attempting to perform an operation thatcauses the IBM Tivoli Storage Manager server toreturn information about this object to the client.Note: During incremental backup, the server returnsinformation to the client about active backupversions which is used to determine which files havechanged.

Beginning with IBM Tivoli Storage Manager serverversion 6.1, the maximum high level name length wasreduced from 8192 characters to 6000 characters.Objects with high level names that exceed 6000characters are not supported for backup or archive.Beginning with IBM Tivoli Storage Managerbackup-archive client version 6.2, the maximum highlevel name length was similarly reduced.

System action: The file or directory specified in themessage is skipped. Processing will continue with thenext object.

User response: Contact your IBM Tivoli StorageManager server administrator for further assistance.

FMV4058I A write failure occurred whileattempting to save node replicationfailover values to the options file.

Explanation: A write failure is often a result ofinsufficient access permissions to the options file, butcould also be caused by the lack of available diskspace. The replication server connection informationcan not be saved and failover will not be possible.


User response: Check the local disk for possiblecauses of the write error, and check to see thatsufficient access to the options file is configured.

FMV4059I The option USEREPLICATIONFailoveris set to NO. The node will not fail overto the secondary server

Explanation: This option will prevent the node fromconnecting to the replication server in the event of afailure of the primary server.

System action: The configuration set by the TivoliStorage Manager administrator will be saved to theoptions file. The client will not connect to the primaryserver and processing stops.

User response: No response is required.

FMV4061I Connected to secondary server secondaryserver; in fail over mode. Home server is:home server;

Explanation: The node is configured for replicationand has successfully connected to the secondary server.This message is to notify the server administrator that anode has connected to the secondary server in fail overmode.



FMV4063W IBM Tivoli Storage Manager applicationprotection cannot copy the applicationmetafile 'App-Metadata-File-Name' fromthe following VM: 'VM-Name'.Individual database restore from thisbackup is not supported.

Explanation: The application metafile was not foundon the guest machine.

System action: The operation completes. However, theapplication metafile was not copied.

User response: Make sure that the application VSSwriters are running on this guest machine, andapplication database is in the state to allow the backup.



Then try the operation again.

FMV4064I Restoring vCloud Director vApp 'vappname' from Organization VDC 'org vdcname' from organization 'org name' TargetvApp name is 'restored vapp name'Restore VAPP command started. Totalnumber of vApps to process: vapps numto restore

Explanation: The restore vApp operation completed.



FMV4065E Proxy rejected: data mover node 'dmnode' has not been granted proxyauthority for target node 'target_node',associated with Organization vDC'OVDC name' of Organization 'Org Name'.

Explanation: The operation requires that a proxyaccess for the data center node is granted to the datamover node.

System action: Operation is canceled for the specifiedvApp.

User response: Run configuration wizard orconfiguration editor to configure proper nodesrelashionship.

FMV4066W Snapshot operation attempt x of y forthe guest virtual machine 'VM' failedusing "sType" snapshot. Reattemptingsnapshot with "sType2" snapshot.

Explanation: The snapshot operation has failed. Asnapshot retry operation has been scheduled.

System action: Retrying snapshot.

User response: Check the error log for any othermessages that might indicate a reason for the failure.Correct any problems and try the operation again.

FMV4067E Snapshot operation attempt x of y forthe guest virtual machine 'VM' failedusing "sType" snapshot. Backup failed.

Explanation: All snapshot retry attempts of the guestvirtual machine failed.


User response: Check the error log for any messagesthat indicate a reason for the failure. Correct anyproblems and try the operation again. If the problempersists, search the Tivoli Storage Manager Supportweb site (http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html) forknown solutions.

FMV4068I Restored virtual machine 'VM' wasbacked up using a "VMware Tools withfile system quiescing and applicationquiescing disabled" snapshot. This isequivalent to a "crash-consistent"backup.

Explanation: The restored virtual machine was backedup using a "VMware Tools with file system quiescingand application quiescing disabled" snapshot.Application Protection feature is not available.

System action: Restore of the VM continues.

User response: None

FMV4071E 'VM-Name' cannot be restored because itwas backed up with a newer version ofthe client.

Explanation: The client version that attempted torestore the virtual machine is earlier than the clientversion that backed up the virtual machine. The virtualmachine cannot be restored with an earlier clientversion.

System action: The virtual machine is not restored.Processing continues with the next virtual machine.

User response: Upgrade the client to a version that iscompatible with the client version that backed up thevirtual machine.

FMV4077E File 'filespace namepath-namefile-name' isencrypted by Microsoft EFS andcontains at least one sparse data stream.The operating system does not supportrestore for this file so it is not backedup or restored.

Explanation: An error in the Microsoft Windows APIprevents successful restore of files that meet thefollowing conditions:

v The file is encrypted by Microsoft Encrypting FileSystem (EFS) at the time it was backed up

v The file includes at least one data stream (alternate"named" stream or unnamed stream) that is sparse

v The operating system is any edition of Microsoft XP,Microsoft Windows Server 2003, or MicrosoftWindows Server 2003 R2

Because the file cannot be restored, IBM Tivoli StorageManager does not back it up. The problem isdocumented by Microsoft at http://support.microsoft.com/kb/2525290.

System action: The file is not backed up or restored.Processing continues with the next object or ends ifthere are no further objects.

User response: If this message is issued during abackup operation, you can do the following:



v Disable EFS encryption for the file so that it can bebacked up.

v If a backup copy of the file is not necessary, you canexclude it from backup.

FMV4081E Error processing 'filespace-name': filespace type is not supported.

Explanation: The specified file space type is notcurrently supported by Tivoli Storage Manager on thisplatform.

System action: The unsupported file system isskipped. Processing continues with the next file system.

User response: Refer to the documentation forinformation on what file space types are supported.

FMV4083I New node password has beengenerated.

Explanation: The client logged in using administrativeid rather than node name. New random node passwordhas been generated and recorded.



FMV4084E Error processing 'filespace-namepath-namefile-name': cannot get file status.

Explanation: While processing the file, the lstat() callset EOVERFLOW error code.

System action: This file will be skipped.

User response: The file is skipped. Processingcontinues with the next file.

FMV4085I Assigned 'number' objects from previoussystemstate backup to the newsystemstate backup.

Explanation: Objects in the previous System Statebackup have not changed and were assigned to thenew System State backup.



FMV4086W Failed to assign unchanged objects fromprevious systemstate backup to the newsystemstate backup. Objects will bebacked up.

Explanation: Objects in the previous System Statebackup have not changed and should be assigned tothe new systemstate backup. Due to error assignoperation failed and objects will be backed up.


User response: Retry the operation. If the problem

persists, contact Tivoli Storage Manager technicalsupport.

FMV4087E An attempt to load data for the wizardfailed. For more information, please seethe log file.

Explanation: An attempt to load data for the wizardfailed as the remote agent is probably unavailable.


User response: Check the log for reason for thefailure.

FMV4089W File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'.Perform a full incremental backup byspecifying optioncreatenewbase=migrate as soon aspossible.

Explanation: The file server has been upgraded to aversion that supports unicode file names forincremental backup using snapshot difference. Performa full incremental in order to backup any files withunicode names that may have been skipped by theprevious version of the IBM Tivoli Storage Managerclient.


User response: Perform a full incremental byspecifying the command line optioncreatenewbase=migrate with the snapdiff option assoon as possible.

FMV4090I File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'.Perform a full incremental backup byspecifying optioncreatenewbase=migrate as soon aspossible.

Explanation: The file server has been upgraded to aversion that supports unicode file names forincremental backup using snapshot difference. Performa full incremental in order to backup any files withunicode names that may have been skipped by theprevious version of the IBM Tivoli Storage Managerclient.


User response: Perform a full incremental backup byspecifying the command line optioncreatenewbase=migrate with the snapdiff option assoon as possible.



FMV4092E Data mover platform is not supportedfor instant access/restore operations.

Explanation: The instant access/restore operationfailed.

System action: The instant access/restore operationfailed. The reason for the failure is unsupportedplatform.

User response: The instant access/restore operationshould be performed from a supported data moverplatform.

FMV4099E The system volume cannot beidentified. Therefore the system statecannot be backed up.

Explanation: The system volume contains thehardware-specific system state files that are needed tostart Windows, such as Ntldr, Boot.ini, Ntdetect.com orBootmgr. If the system volume cannot be identified,then these files cannot be backed up. Therefore it is notpossible to back up the system state.

System action: Systemstate backup stops.

User response: Try the operation again. If the problempersists, obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your Tivoli Storage Manageradministrator can help you configure the trace.

FMV4137E Error processing 'filespacenamepath-namefile-name': exceededmaximum number of links allowed

Explanation: Link cannot be restored or retrievedbecause the destination file system has exceededmaximum number of links allowed.


v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Restore or retrieve the link to another filesystem.

FMV4148E Full VM backup of Virtual Machine'vmname' failed with RC rc

Explanation: The Full VM backup of virtual machinefailed.

System action: The full backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.

User response: Check the local client error log forreason for the failure.

FMV4150E Incremental backup of Virtual Machine'vmname' failed with RC rc

Explanation: The incremental backup of virtualmachine volumes failed.

System action: The backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.


FMV4151E Failure mounting Virtual Machine'vmname'. RC=rc

Explanation: The VMware failed to mount virtualmachine disk.

System action: The backup of the virtual machine cannot continue. The next virtual machine in the vmlistwill be processed. Refer to dsmerror.log for detailederror message for the reason for the failure.

User response: Refer to dsmerror.log for detailed errormessage.

FMV4152E Failure initializing VMware virtualmachine environment. RC=rc. Refer toIBM Tivoli Storage Manager error logfor detailed error messages.

Explanation: Failure initializing VMware virtualmachine environment. Refer to IBM Tivoli StorageManager error log for detailed error messages.

System action: The backup can not continue.

User response: Refer to IBM Tivoli Storage Managererror log for detailed messages.

FMV4153E Hostname could not be found forVirtual Machine 'vmname'

Explanation: The backup of virtual machine failed.



FMV4154E Possible cause Virtual Machine is notrunning and does not have a static IPaddress.






FMV4155E Virtual Machine 'vmname' could not befound on VMware server.




FMV4156E File level VM backup of virtual machine'vmname' not supported. File level VMbackup not support on non Windowsplatform guest OS. Platform type:'platform'.



User response: Back up the virtual machine using theVMBACKUPType=FULLvm option.

FMV4159E Backup of Virtual Machine 'vmname'failed. rc=rc.




FMV4160E Proxy Rejected: Proxy authority has notbeen granted to Agent Node: 'agent_node'for Target Node: 'target_node'.


System action: The backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure isthe node has not been granted proxy authority toaccess the node named by the backup proxy node. TheTivoli Storage Manager administrator must first grantproxy authority.


FMV4161E Duplicate virtual machine name'vmname' was detected in the samebackup operation. Backup of virtualmachine 'vmfullname' can not continuewithout a unique object name.



User response: Choose a unique name for the virtualmachine.

FMV4162E The virtual machine'virtual-machine-name' has not beenpreviously backed up.

Explanation: The specified virtual machine has notbeen previously backed up, so can not be specified forrestore.

System action: The specified virtual machine isskipped, and the next virtual machine in the restore listis processed.

User response: Verify the virtual machine name to berestored, and re-try the operation.

FMV4163I Encryption is currently enabled, but thevirtual machine backup for'virtual-machine-name' will not beencrypted.

Explanation: Virtual Machine files are not encryptedwhen backed up to the TSM server.

System action: The virtual machine files are notencrypted during the backup processing.

User response: No user action is necessary.

FMV4164W Compression is currently enabled, butthe virtual machine backup for'virtual-machine-name' is not compressedbecause client-side deduplication is notbeing used.

Explanation: Compression can only be used withvirtual machine CTL and Data files when the files arestored in a storage pool that is enabled for client-sidededuplication. This message is issued when the client isconfigured for compression and virtual machine CTL orData files are directed to a storage pool that is notenabled for client-side deduplication.

System action: Backup continues, and data is notcompressed.

User response: If you intend to compress virtualmachine CTL and Data files, then update your TivoliStorage Manager configuration so that both types of



files are directed to storage pools that are enabled forclient-side deduplication. If you intend to compressvirtual machine Data files but not CTL files, thenupdate your Tivoli Storage Manager configuration sothat the Data files are directed to a storage pool that isenabled for client-side deduplication. Set theVMSKIPCTLCOMPRESSION to YES in your clientoptions file. If you do not intend to use compression,then set COMPRESSION NO in your client options file.

FMV4165E Creating a Virtual Machine, but thehostname 'virtual-machine-name' was notfound.

Explanation: The Virtual Machine being creating musthave a valid hostname to be created.

System action: Check the virtual machine hostnamespecified for correctness.

User response: Correct the virtual machine hostnamespecified and retry the restore.

FMV4166E Creating a Virtual Machine, but thedatacenter 'virtual-machine-name' was notfound. The name may be incorrect ormay be located in a VMware folder andrequire the folder name such asvmfolder/dcname.

Explanation: The Virtual Machine being created musthave a valid datacenter to be created.


User response: Check the virtual machine datacenterspecified for correctness. If the datacenter is containedin a folder then the full datacenter name, complete withthe folder path, must be specified, such asvmfolder/dcname.

FMV4167E Creating a Virtual Machine, but thedatastore 'virtual-machine-name' was notfound.

Explanation: The Virtual Machine being creating musthave a valid datastore to be created.

System action: Check the virtual machine datastorespecified for correctness.

User response: Correct the virtual machine datastorespecified and retry the restore.

FMV4168E VMware has reported an error via theirSOAP interface. On the Detailed StatusReport panel, view the last errormessage reported. Also check the errorlog for more information about theproblem that occurred.

Explanation: The command to VMware failed tocomplete. The error returned is displayed on the

Restore or Backup summary panel under the Last ErrorMessage section.

System action: An error occurred, and the operationfailed.

User response: Check the reported error and correctthe problem. Usually the reason for the error is auser-supplied value which is not valid for theoperation.

FMV4169E A write failure occurred on the localdisk proxy used to temporarily store thevirtual machine virtual diskinformation. The write failure can becaused by the lack of available diskspace on the drive used to store thisinformation. The VMBACKDIR optioncan be used to assign a different disklocation for this purpose. Check thedrive being used and ensure that thereis enough space available for thisoperation.

Explanation: There was a write error from the localdisk used to store the virtual machine virtual diskinformation. Usually the write error is due to lack ofdisk space, lack of write permissions, or some similarproblem with the local disk. The VMBACKDIR optioncan be used to assign a different disk location if thelocal drive does not have enough free space for theoperation.

System action: A disk write error occurred, and theoperation failed.

User response: Check the local disk for possiblecauses of the write error, and use the VMBACKDIRoption to assign another disk if needed.

FMV4170E Can not create a Virtual Machine onVMware release 'release-version-target'which was backed up from VMwarerelease 'release-version-source'.

Explanation: The Virtual Machine being created wasbacked up from a version of VMware which is notcompatible with the target VMware release versionbeing used for the restore.


User response: Restore the Virtual Machine to aVMware system which is compatible with the levelfrom which the Virtual Machine was backed up.

FMV4171E Backup of virtual machine 'vmname'failed. VM could not be contactedbecause of 'vmfullname' connection state.


System action: The backup of the virtual machine



finished with failures. The next virtual machine in listwill be processed.

User response: Correct the connection state fromVMware vCenter and assign VM to an ESX Server.

FMV4174E Full VM backup of VMware VirtualMachine 'vmname' failed with RC=rcmode=full_or_incr, target nodename='target_node_name', data movernode name='data_mover_node_name'




FMV4177E Full VM restore of VMware VirtualMachine 'vmname' failed with RC=rctarget node name='target_node_name',data mover nodename='data_mover_node_name'

Explanation: The Full VM restore of the virtualmachine failed.

System action: The full restore of the the virtualmachine finished with failures. The next virtualmachine in the vmlist will be processed. The reason forthe failure is written to the local client error log.


FMV4178W Compression is currently enabled, butthe virtual machine control files for'virtual-machine-name' will not becompressed because client-sidededuplication is not being used for themanagement class default or specifiedby the -vmctlmc option for'vm-ctl-mgmt-class-name'.

Explanation: Virtual machine control files are notcompressed because data is stored in a storage poolthat is not enabled for client-side data deduplication.The virtual machine control files are not compressedduring the backup processing unless data is stored in astorage pool that is enabled for client-datadeduplication.

System action: Backup continues, and control file datais not compressed.

User response: Ensure that the storage pool is enabledfor client-side data deduplication: run "q stg <poolname> f=d" and verify that the value of "DeduplicateData?" is "yes". Ensure that client-side data

deduplication is enabled on the server. To enableclient-side data deduplication, use theDEDUPLICATION parameter on the REGISTER NODEor UPDATE NODE server command. Set the value ofthe parameter to CLIENTORSERVER. The value of theDEDUPLICATION option on the client must be set toYES. You can set the DEDUPLICATION option in theclient options file, in the preference editor of the TivoliStorage Manager client GUI, or in the client option seton the Tivoli Storage Manager server. Use the DEFINECLIENTOPT command to set the DEDUPLICATIONoption in a client option set. To prevent the client fromoverriding the value in the client option set, specifyFORCE=YES. Ensure that the deduplication parameterfor the node is "ClientOrServer": The value of theDEDUPLICATION option on the client must be set toYES.

FMV4179I IBM Tivoli Storage Manager applicationprotection did not truncate the MicrosoftSQL Server logs on VM 'VM'.

Explanation: The SQL server logs were not truncatedbecause the following option was specified for thisvirtual machine: INCLUDE.VMTSMVSS vnameOPTIONS=KEEPSQLLOG

System action: The operation completes.

User response: Remove the OPTIONS=KEEPSQLLOGoption to enable truncation of the SQL logs when abackup completes.

FMV4187W CPU and Memory Resource Allocationconfiguration settings cannot be restoredwhen the IBM Tivoli Storage Managerdata mover node is connected directly toa Virtual Center managed ESX/ESXihost. These settings have been skipped.

Explanation: The VMware vStorage APIs do notsupport the restore of CPU and Memory ResourceAllocation configuration settings when connecteddirectly to an ESX/ESXi host that is managed by aVirtual Center.

System action: CPU and Memory Resource Allocationconfiguration settings are skipped. Processingcontinues.

User response: Virtual machine CPU and MemoryResource Allocation configuration settings will berestored when the IBM Tivoli Storage Manager datamover node connects directly to a vCenter Server.Modify the VMCHOST to connect the TSM data moverto a vCenter Server.

FMV4191E Restore VM operation failed using 'san'transport mode. In some cases switchingfrom SAN to network-based VMrestores can be successful.

Explanation: Restore VM operations that fail using



SAN transport mode can often be successful over aLAN path. If a restore vm operation fails using the'SAN' transport mode, set the client optionVMVSTORTRFMVPORT to "nbd:nbdssl" and try therestore vm operation again.

System action: Restore VM operation failed using 'san'transport mode. Restore may be successful using'nbd:nbdssl' transport modes.

User response: Restore VM operation failed using'san' transport mode. In some cases network-based VMrestores can be successful when using 'nbd' or 'nbdssl'transport modes. The VMVSTORTRFMVPORT optioncan used to restrict the TSM client to use only thespecified transport modes.

FMV4193E vApp 'vApp name' cannot be processedbecause data mover 'dm node' cannotconnect to the target node 'target_node'.

Explanation: The operation requires that a proxyaccess for the data center node is granted to the datamover node.

System action: Operation is canceled for the specifiedvApp.

User response: Look for errors in error log and correctany problems. Run configuration wizard orconfiguration editor to ensure proper nodesconfiguration.

FMV4194E Encryption is currently enabled, but isnot supported for incremental foreverbackups of virtual machines(-MODE=IFFULL or-MODE=IFINCREMENTAL) .

Explanation: Client encryption of virtual machineincremental forever backups (-mode=IFFULL or-mode=IFINCREMENTAL) is not supported. In orderto avoid the unintentional storage of unencrypted dataon the server, the backup operation stops.

System action: The virtual machine backup stops.

User response: Remove the encryption options for thisoperation and run it again. You can use Secure SocketsLayer (SSL) encryption to encrypt the data over thenetwork. If the backup data must be encrypted inTivoli Storage Manager storage pools, use analternative backup method such as full and incrementalbackups (-mode=FULL and -mode=INCREMENTAL),or in-guest backups.

FMV4195E The target node for Organization VDC'OrgVDC name' in Organization 'Orgname' was not found. As a result, vApp'vApp name' cannot be backed up.

Explanation: Either the Tivoli Storage Manager nodefor the specified organization VDC was not found onthe Tivoli Storage Manager server, or information about

the Organization VDC node was not found in theProvider VDC node.

System action: Back up of the specified vApp stops.Processing continues to the next vApp.

User response: Go to the Configuration page and click'Run the Configuration Wizard' to verify that allrequired Tivoli Storage Manager nodes are registeredon the Tivoli Storage Manager server. If required,register a new data mover node. Make sure that theorganization VDC belongs to the provider VDC thatthis data mover node protects.

FMV4199W File 'file name' is not backed up as partof the system state because cluster disk'volume name' is not accessible.

Explanation: The indicated file or directory wasreturned by VSS as part of the backup file list of thewriter. However, the cluster disk where the file islocated is not accessible. The reasons for this problemcan be that the cluster disk is offline or belongs toanother node.

System action: The file is not backed up. Processingcontinues.

User response: This problem is documented inMicrosoft knowledge base topic 980794http://support.microsoft.com/default.aspx?scid=kb;EN-US;980794. The topic includes a hotfix. With the hotfix,you can specify a registry key that contains a list of oneor more files to be excluded from VSS enumeration.IBM Tivoli Storage Manager does not back up files thatare not enumerated by VSS. If the volume is broughtonline to the node performing the system state backup,then it cannot be backed up. You must remove thevolume from the registry key and restart the systembefore you can back up the volume. If you do not wantto implement the hotfix for this problem, IBM TivoliStorage Manager continues to issue this message.

FMV4202E The Deployment Manager failed toinstall language pack: language packname. The Microsoft Installer error codewas error code.

Explanation: The previous language pack has beenuninstalled, and the installation of the new languagepack failed.


User response: For more information about Windowsinstaller error messages, go to the Microsoft DeveloperNetwork (MSDN) technical library athttp://msdn.microsoft.com/en-us/library and searchon "Windows Installer Error Messages".

Check the install log on the client computer.



FMV4251W writername file 'filename': not found.

Explanation: The indicated VSS writer file or directorywas returned by VSS as part of the backup file list ofthe writer. However, the object does not exist on thedisk. .

System action: Processing stops ifSKIPMISSINGSYSWFILES option is set to NO.Processing continues if SKIPMISSINGSYSWFILESoption is set to YES.

User response: Verify that this file can be skippedduring system state backup.

FMV4285E The update restore operation to anexisting virtual machine 'VmName'failed. The virtual machine is not inpower off state.

Explanation: The update restore operation to anexisting virtual machine is not supported for a runningmachine and will be aborted.

System action: Restore aborted.

User response: Turn off the virtual machine andre-run the update restore command.

FMV4290E Only one virtual machine can beselected for restore.

Explanation: Restoring multiple virtual machines isnot allowed. Only one virtual machine can be selectedfor restore.

System action: No processing occurs.

User response: Select only one virtual machine forrestore.

FMV4291E Virtual Machine could not be found onVMware server.




FMV4292E No virtual machine found.

Explanation: No virtual machine found with name orspecified in domain option.


User response: Specify a correct VM name or domainoption.

FMV4293E Backup of VMware vApp 'vApp name' inOrganization VDC 'Org VDC name' oforganization 'Org name' failed.

Explanation: The vApp backup operation failed. Thiserror message is a summary message and does notcontain detailed information.

System action: The configuration information andVMs for the specified vApps are not backed up.Processing continues to the next vApp.

User response: Check the previous messages in thedsmerror.log file for more details about this vApp .

FMV4301I IBM Tivoli Storage Manager detectedMicrosoft Active Directory DomainController on virtual machine 'VM'.

Explanation: The virtual machine contains MicrosoftActive Directory Domain Controller.

System action: IBM Tivoli Storage Manager savedadditional information about this virtual machine.

User response: None

FMV4302W IBM Tivoli Storage Manager failed todetect if Microsoft Active DirectoryDomain Controller on virtual machine'VM'.

Explanation: There was an error while checking if thevirtual machine contains Microsoft Active DirectoryDomain Controller.

System action: IBM Tivoli Storage Manager continuesbacking up this virtual machine.

User response: Check IBM Tivoli Storage Managererror log for additional information.

FMV4303E The vCloud Director vApp 'vapp-name'has not been previously backed up.

Explanation: The specified vCloud Director vApp hasnot been previously backed up, so can not be specifiedfor restore.

System action: The specified vCloud Director vApp isskipped, and the next vApp in the restore list isprocessed.

User response: Verify the vCloud Director vApp nameto be restored, and re-try the operation.

FMV4304I IBM Tivoli Storage Manager could notdetect the TSM for VE license. ActiveDirectory Domain Controller will not beprotected on VM 'VM'.

Explanation: The virtual machine contains MicrosoftActive Directory Domain Controller, but a TSM for VE

FMV4251W • FMV4304I


license is not detected. The Domain Controller will notbe protected.

System action: Install TSM for VE 7.1 or later toprotect Active Directory.

User response: None

FMV4305W Backup of VMware vApp 'vApp name' inOrganization VDC 'Org VDC name' oforganization 'Org name' completed. SomeVMs were not backed up. mode:'Incremental Forever - full_or_incr' targetnode name: 'target_node_name' datamover node name:'data_mover_node_name' VMs backupstatus: number of VM backed up out ofnumber of VMs in vApp VMs backed upsuccessfully.

Explanation: The vApp backup operation completedsuccessfully. However, one or more VMs for thespecified vApp were not backed up. These VMs willnot be created during the restore operation.

System action: Processing continues to the next vApp.

User response: Check the dsmerror.log file for thisvApp for more information about this message. Resolvethe problem, then try the operation again.

FMV4308E Full VM backup of 'hypervisor' VirtualMachine 'vmname' failed with RC=rcmode=full_or_incr, target nodename='target_node_name', data movernode name='data_mover_node_name'




FMV4311E Full VM restore of 'hypervisor' VirtualMachine 'vmname' failed with RC=rctarget node name='target_node_name',data mover nodename='data_mover_node_name'

Explanation: The Full VM restore of the virtualmachine failed.

System action: The full restore of the the virtualmachine finished with failures. The next virtualmachine in the vmlist will be processed. The reason forthe failure is written to the local client error log.


FMV4446E A file-level restore mount operation forhypervisor type Virtual Machine 'vmname'failed. The data center node name is'data center node name', the mount proxynode name is 'mount proxy node name'

Explanation: The file-level restore mount operation ofthe virtual machine failed.

System action: The mount of the virtual machinefinished with failures. The reason for the failure iswritten to the local client error log.


FMV4449E A cleanup of the file-level restore ofhypervisor type Virtual Machine 'vmname'failed. The data center node name is'data center node name', the mount proxynode name is 'mount proxy node name'

Explanation: The cleanup of file-level restore mountoperation of the virtual machine failed.

System action: The cleanup of mount of the virtualmachine finished with failures. The reason for thefailure is written to the local client error log.


FMV4450E Mount proxy platform is not supportedfor file-level restore operations.

Explanation: The file-level restore operation failed.The reason for the failure is an unsupported platformor that the IBM Tivoli Storage Manager Recovery Agentis not correctly installed and configured.

System action: The file-level restore operation failed.

User response: The file-level restore mount operationshould be performed from a supported mount proxyplatform with IBM Tivoli Storage Manager RecoveryAgent installed and configure correctly .

FMV4451E The Windows iSCSI service is notavailable.

Explanation: The Windows iSCSI service is notavailable on the mount proxy machine. It is either notstarted or not installed or configured correctly.

System action: Processing stops, the file-level restoremount operation fails.

User response: Ensure that the iSCSI service is up andrunning on the mount proxy machine.



FMV4900W Schedule 'schedule-name' has opened anew session with the server.

Explanation: A scheduled event endsbecause of aconnection failure. The scheduled event had to berestarted outside its normal startup window tocontinue the operation.

System action: The scheduled event is completedusing more than one session.

User response: None required. If this is a recurrentcondition, you may want to check for networkproblems.

FMV4901E The following object contains one ormore unmatched quotation marks andcannot be processed: 'filespace pathfilename'.

Explanation: The file name in the file list containsunmatched quotes. If a line in the file list begins with asingle or double quotation mark this quotation mark isconsidered to be an opening quotation mark. Thecorresponding closing quotation mark of the same typemust be at the end of the line. If there is no closingquotation mark or the closing quotation mark has beenencountered in the middle of the line, it is an invalidinput.

System action: The object is skipped.

User response: Correct the specification of the object.

FMV4904E Instant access of VMware VirtualMachine 'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The instant access of the virtual machinefailed.

System action: The instant access of the the virtualmachine finished with failures. The reason for thefailure is written to the local client error log.


FMV4907E Instant restore of VMware VirtualMachine 'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The instant restore of the virtual machinefailed.

System action: The instant restore of the the virtualmachine finished with failures. The reason for thefailure is written to the local client error log.


FMV4910E Cleanup of VMware Virtual Machine'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The cleanup of the virtual machinefailed.

System action: The cleanup of the the virtual machinefinished with failures. The reason for the failure iswritten to the local client error log.


FMV4915I Object increased in size duringcompression: filespace pathfilename

Explanation: The file increased in size duringcompression.

System action: Processing contiues.


FMV4942E The file specification 'string' is invalid.

Explanation: The operating system indicated that thefile specification is invalid. One possible reason is thatthe file specification contains unrecognized characters.Another possible cause is incorrect use of quotationmarks in the file specification.


User response: Enter a correct file specification asdescribed in the Using the Backup-Archive Client bookfor the particular operating system. Ensure that the filespecification contains valid characters. Verify correctuse of quotation marks for specifications that containblanks spaces. If multiple file specifications are used,make sure that any use of quotation marks does notcause the file specifications to be treated as a single filespecification.

FMV4946W Warning: virtual machine: 'vm-name'disk: 'disk-name' excluded by user, wasnot found.

Explanation: The specified virtual disk does not existon the virtual machine.


User response: Use the "dsmc backup vm ..."command with the -preview option to display a listingof the disk labels which exist on the virtual machine.Since the disk was specified to be excluded from thebackup, the backup will continue. However it ispossible that a disk will included in the backup whichwas not desired, check the spelling of the disk label,and correct the disk label if an undesired disk is nowincluded in the backup operation.



FMV4947E Error: virtual machine: 'vm-name' disk:'disk-name' included by user, was notfound.

Explanation: The specified virtual disk does not existon the virtual machine.


User response: Use the "dsmc backup vm ..."command with the -preview option to display a listingof the disk labels which exist on the virtual machine.Check the spelling of the disk label and correct the disklabel and then retry the 'backup vm' operation.

FMV4948E A specified virtual disk was not foundon the virtual machine.

Explanation: You must specify a virtual disk labelname which exists on the virtual machine.


User response: For a backup operation, use the "dsmcbackup vm ..." command with the -preview option todisplay a listing of the disk labels which exist on thevirtual machine. For a restore operation, use the "dsmcquery vm ..." command with the -detail option todisplay a listing of the disk labels which exist on thevirtual machine backup. Check the spelling of the disklabel and correct the disk label and then retry theoperation.

FMV4972W File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'. Thisversion does not support unicode filenames for snapshot differenceincremental backup. Upgrade to aversion that supports unicode file namesas soon as possible.

Explanation: The file server has been upgraded from aversion that supports unicode file names forincremental backup using snapshot difference to aversion that does not. If you have upgraded from DataONTAP version 7.3.3 (or later) to 8.0, you lose theability to back up files with unicode file names whenperforming snapshot difference incremental backup.

System action: Processing continues. However, fileswith unicode names are not backed up.

User response: Upgrade to a version that supportsunicode file names as soon as possible. If you haveupgraded from Data ONTAP version 7.3.3 (or later) to8.0, upgrade to 8.1 (or later). If it is not possible toupgrade at this time, you can suppress this warningmessage by renaming the file space on the IBM TivoliStorage Manager server and performing a snapshotdifference incremental backup.

FMV4973E An error occurred accessing NTFSsecurity information for file 'filespacenamepath-namefile-name'

Explanation: An access denied error occurred whileattempting to access NTFS security info rmation.


User response: See your system administrator orbypass the failing check by using SkipNTSecu rityoption.

FMV4974E Error processing 'filespacenamepath-namefile-name': a required NTprivilege is not held.

Explanation: The user account running Tivoli StorageManager does not possess a required NT user right/privilege for performing the current operation.


User response: Your system administrator has theauthority to grant the needed privilege.

FMV4987E Error processing 'filespacenamepath-namefile-name': the object is inuse by another process

Explanation: The specified file is being used byanother process. You tried to read from or write to afile that is currently being used by another process.


User response: Ensure that the file is not locked byanother process. If the file is not locked, retry thecommand.

FMV4988W File 'filespace namepath-namefile-name' iscurrently unavailable on server and hasbeen skipped.

Explanation: You tried to restore or retrieve a file thatis currently not available from the Tivoli StorageManager server. This is most likely a temporarycondition.


User response: Try to restore or retrieve the file againafter the file becomes available on the server. If theproblem persists, see your Tivoli Storage Manageradministrator for assistance.

FMV4989E Error processing 'filespacenamepath-namefile-name': the directory isin use by another process. All objects inthe directory and any of itssubdirectories are skipped.

Explanation: The specified directory is being used by



another process. You tried to read from or write to adirectory that is currently being used by anotherprocess. The objects contained in the directory and itssubdirectories are not backed up.

System action: Processing stopped for that directory.If other files and directories were also specified in thisbackup, they are processed

User response: Ensure that you specified the correctdirectory name, correct the permissions, or specify anew location.If the directory name is correct, retry thebackup when no process has exclusive use of thedirectory.

FMV4991I Application Type Application Message IdApplication Message

Explanation: This is a message sent by the applicationyou are currently running with Tivoli Storage Manager.

System action: Tivoli Storage Manager logs theapplication message.

User response: Refer to the documentation for theapplication that you are using.

FMV4992W Application Type Application Message IdApplication Message




FMV4993E Application Type Application Message IdApplication Message




FMV4994S Application Type Application Message IdApplication Message




FMV4997E Error processing 'filespacenamepath-namefile-name': file system quotareached condition - no space left.

Explanation: No more files can be restored orretrieved because the quota of the destination filesystem has been reached.


v Retry this object

v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Create some free space or increase the quota onthe destination file system before you retry theoperation. Another option is to restore or retrieve thefile to another file system.

FMV4998E Link information for file 'filename' couldnot be obtained: access to the object isdenied.

Explanation: Access to the specified file link is denied.You tried to read information for file link and you donot have access permission for this object.

System action: Processing of System State stops.

User response: Try the operation again. If the problempersists, contact IBM technical support for additionalassistance.

FMV4999I The following message was too long tolog to the server: 'shortened message withmessage number'

Explanation: The message text and inserts are toolarge to send to the server in the available internalbuffer.

System action: The message number message is writtento the local client error log, then shortened and sent tothe server as a part of this message. The message isreduced in length by substituting '...' in the middle ofthe original message.

User response: The message referred to has beenshortened, but describes the error that occurred. See thedocumentation for that message for more information.

FMV5003S The management class assigned todirectories does not exist.

Explanation: The management class named on theDIRMC option does not exist in your assigned policyset on the server. The error log contains an entryshowing the invalid management class name.


User response: Remove the current DIRMC optionfrom the client options file, then run DSMC QUERYMGMTCLASS -DETAIL to view information about

FMV4991I • FMV5003S


available management classes. Make sure themanagement class you select has a backup copy group.If you have more than one Tivoli Storage Managerserver, make sure you are connecting to the correctserver. If you are unable to find a suitable managementclass, contact your Tivoli Storage Manageradministrator for further assistance.

FMV5004S There is no backup copy group in themanagement class used for directories.See the error log.

Explanation: The DIRMC option names amanagement class that contains no backup copy group.


User response: Remove the current DIRMC optionfrom the client options file, then run DSMC QUERYMGMTCLASS -DETAIL to view information aboutavailable management classes. Make sure themanagement class you select has a backup copy group.If you have more than one Tivoli Storage Managerserver, make sure you are connecting to the correctserver. If you are unable to find a suitable managementclass, contact your Tivoli Storage Manageradministrator for further assistance.

FMV5005E Table of contents information is notavailable for the selected images.

Explanation: An error occurred when the server triedto load a table of contents. Requested image or table ofcontents may have expired or been deleted on theserver.


User response: Start a new restore window to getcurrent information.

FMV5006W The policy set does not contain anybackup copy groups. Tivoli StorageManager is unable to continue thebackup.

Explanation: You tried to back up the files using apolicy set that contained no backup managementinformation.

System action: Tivoli Storage Manager did not backup the files.

User response: See your Tivoli Storage Manageradministrator for assistance in associating your nodewith a policy set containing a management class thathas a backup copy group. Then try the operation again.

FMV5007W The policy set does not contain anyarchive copy groups. Tivoli StorageManager is unable to continue thearchive.

Explanation: You tried to archive the files using apolicy set that contains no archive managementinformation.

System action: Tivoli Storage Manager did not archivethe files.

User response: See your Tivoli Storage Manageradministrator for assistance in associating your nodewith a policy set containing a management class thathas an archive copy group. Then try the operationagain.

FMV5008W Incorrect password entered

Explanation: You entered a password that wasincorrect.

System action: Tivoli Storage Manager cannot connectto the server without the correct password.

User response: Reenter the password, or ask yoursystem administrator for the current password.

FMV5009W New password entries are not the same

Explanation: During the change password, updatepassword, or open registration dialog, the two entriesfor the new password were not the same.

System action: The password was not changed on theserver.

User response: Backspace over both of the newpasswords and reenter them, ensuring that they match.

FMV5011I Backup stopped by user

Explanation: You requested to stop the backupoperation.

System action: Backup stopped.


FMV5012E Server out of backup data storage space

Explanation: The server ran out of space in its backupdata storage.

System action: Tivoli Storage Manager cannotcomplete the requested backup operation. Any filesdisplayed on the lower half of the backup activitypanel were successfully backed up.


FMV5013E Not enough memory for backupoperation

Explanation: Tivoli Storage Manager cannot allocatememory for the specified backup operation.




User response: Close all unneeded applications andretry the operation. Reducing the scope of queries andthe amount of data returned might also help, or seeyour system administrator.

FMV5014I Backup completed

Explanation: The backup was completed.

System action: Tivoli Storage Manager backed up thefiles.


FMV5015I Restore stopped by user

Explanation: You requested to stop the restoreoperation.

Attention: If you were restoring files with “overwrite”option specified, the file you restored last can bedamaged (partially overwritten).

System action: Restore stopped.


FMV5016E Not enough memory for restoreoperation

Explanation: Tivoli Storage Manager cannot allocatememory for the requested restore operation.

System action: Tivoli Storage Manager cannotcomplete the requested restore operation.

User response: Close all unneeded applications andretry the operation. Reducing the scope of queries andthe amount of data returned can also help, or see yoursystem administrator.

FMV5017I Restore completed

Explanation: A restore was completed.

System action: Tivoli Storage Manager restored thefiles.


FMV5018E Not enough memory for archiveoperation

Explanation: Tivoli Storage Manager cannot allocatememory for the requested archive operation.

System action: Tivoli Storage Manager cannotcomplete the archive operation.


FMV5019I Archive stopped by user

Explanation: You requested to stop the archiveoperation.

System action: Archive stopped.


FMV5020E The Tivoli Storage Manager server isout of archive data storage space.

Explanation: The server ran out of space in its archivedata storage.

System action: Tivoli Storage Manager cannotcomplete the requested archive operation.

User response: Report the problem to your TivoliStorage Manager system administrator, who canallocate more resources to archive storage.

FMV5021I Archive completed

Explanation: An archive was completed.

System action: Tivoli Storage Manager archived thefiles.


FMV5022I Retrieve stopped by user

Explanation: You requested to stop the retrieveoperation.

Attention: If you were retrieving files with“overwrite” option specified, the file you retrieved lastcan be damaged (partially overwritten).

System action: Retrieve stopped.


FMV5023E Not enough memory for retrieveoperation

Explanation: Tivoli Storage Manager cannot allocatememory for the specified retrieve operation.

System action: Tivoli Storage Manager cannotcomplete the requested retrieve operation.


FMV5024I Retrieve completed

Explanation: A retrieve was completed.

System action: Tivoli Storage Manager retrieved thefiles.




FMV5025E The node name contains invalidcharacters.

Explanation: The specified node name has invalidcharacters.


User response: Retry with another node name thathas valid characters.

FMV5026W MatchAllChar and MatchOneCharoptions MUST precede Include/Excludeoptions

Explanation: The MatchAllChar and MatchOneCharoptions must precede any include-exclude options.

System action: The Tivoli Storage Manager client endsthe current application.

User response: Move the MatchAllChar andMarchOneChar options before any include-excludeoptions.

FMV5027W Objects of different types cannot bebacked up at the same time.

Explanation: Backing up objects of different types atthe same time is not allowed in certain scenarios. Forexample, backing up Hyper-V and VMware virtualmachines at the same time is not possible.


User response: Select objects of the same type toperform backup operation.

FMV5028I Successful completion

Explanation: The operation successfully completed.



FMV5029E This operation cannot continue due toan error on the Tivoli Storage Managerserver. See your Tivoli Storage Managerserver administrator for assistance.

Explanation: The Tivoli Storage Manager serverencountered an error condition that prevents the TivoliStorage Manager client operation from continuing. YourTivoli Storage Manager server administrator can reviewthe Tivoli Storage Manager server activity log for moredetails about the error.

System action: The processing stopped.

User response: Contact your Tivoli Storage Managerserver administrator for assistance. The administratorcan review the Tivoli Storage Manager server activity

log for further information about the conditions thatlead to this error.

FMV5030E No objects on server match query

Explanation: No objects on the server match the queryoperation being performed.


User response: Ensure the names are properlyentered.

FMV5031E Client aborted transaction

Explanation: The client system ended the operationwith the server and ended the current transaction.


User response: Restart the session.

FMV5032W Active object not found

Explanation: An attempt was made to expire anobject, but the server was unable to find an activebackup version of the object. This message is precededby message FMV1228E which specifies the object name.For instance, this message could be issued if twoseparate client processes are backing up the same filesystem at the same time. If one of the processes expiresa file, then the server will make that file inactive. If thesecond process subsequently attempts to expire thatsame file, the server will not find an active version ofthe file, so the second process will issue this messagefor that file.

System action: The object is not expired. Processingcontinues with the next object..

User response: Review the console output, schedulelog, or error log and locate the FMV1228E message thatimmediately precedes this message. FMV1228E willidentify the object that could not be expired. Examinethe conditions under which the problem occurred andassess whether those conditions explain the occurrenceof this message. For example, this message couldappear if multiple instances of the client wereattempting to back up the file system concurrently. Ifthe reason this message occurred can not bedetermined and the message occurs when the operationis tried again, then contact support for furtherassistance. Also try searching for this message numberon http://www.ibm.com for possible solutions.

FMV5033E Server has no data for the object.

Explanation: Server tried to do a restore or retrieve onan object that has no data associated with it. If acorrective action is possible, it is with the server.

System action: Server ends the current operation.

User response: Ask the administrator to check the



activity log for any messages related to this error thatmight help identify the problem.

FMV5034E You entered an incorrect password.

Explanation: You entered an incorrect currentpassword or you entered a new password that does notfulfill the password length requirements set on theserver.

System action: The processing stops.

User response: Retry the session with the correctpassword. If this fails or you have forgotten yourpassword, ask the administrator to assign a newpassword.

FMV5035E Node is in use.

Explanation: The node you are running on is in useby another operation on the server. This might be fromanother client or from some activity on the server.


User response: Retry the operation, or see yoursystem administrator to see what other operations arerunning for your node.

FMV5036E Expiration date must be greater thantoday's date

Explanation: Archive expiration date is too low, thedate must be greater than today's date.

System action: The current operation is canceled.

User response: Retry archiving the file with anexpiration date that is higher than today's date.

FMV5037W The requested data is offline

Explanation: For the restore or retrieve operation, oneor more of the requested files must be recalled fromoffline storage media (generally tape). The wait timedepends on your site's offline storage managementpolicies.

System action: CLient waits for offline storage mediato become available and then continues.


FMV5038E Object too large for server limits.

Explanation: The object is too large. The configurationof the server does not have any data storage space thataccepts the object.


User response: See your system administrator todetermine the maximum file (object) size for whichyour site's server is configured.

FMV5039E Server out of data storage space.

Explanation: The server does not have any spaceavailable to store the object.

System action: Ended the current operation.

User response: You can take any of the followingactions:

v For client, set COMPRESSALWAYS=NO andCOMPRESSIon=YES in the options file (DSM.OPT),then the file will be resent uncompressed if it growsduring compression.

v Request the system administrator to add space to thestorage pool.

v The system administrator can also turn off diskcaching in the disk storage pool, and issue MOVEDATA commands to each disk pool volume to clearout the cached bitfiles.

FMV5040E Server media mount not possible.

Explanation: Server media mount not possible. Theserver timed out waiting for a mount of an offlinevolume.


User response: Retry later when server volumes canbe mounted. Ensure that the MAXNUMMP (maximumnumber of mount points) defined on the server for thisnode is greater than 0.

FMV5041E Size estimate exceeded.

Explanation: The total amount of data for a backup orarchive operation exceeds the estimated size originallysent to the server for allocating data storage space. Thishappens when many files are growing by largeamounts while the backup or archive operation is insession.


User response: Retry the operation. If the problemcontinues, check what other processes are running onthe client machine that are generating large amounts ofdata. Disable those operations while the backup orarchive operation is taking place.

FMV5042E File data is currently unavailable on theTivoli Storage Manager server

Explanation: The Tivoli Storage Manager client wastrying to restore or retrieve data that is currentlyunavailable on the Tivoli Storage Manager server.Possible causes are:

v Data is corrupted at the Tivoli Storage Managerserver

v The Tivoli Storage Manager server encountered aread error



v File is temporarily involved in a reclaim operation atthe server

v The Tivoli Storage Manager requested a tape volumethat is unavailable. Typical reasons for a volume tobe unavailable: a disk volume is offline, the volumeis marked unavailable due to an I/O error, or a tapevolume is checked out of the tape library.


User response: Try the operation again at a later time.If the problem continues, contact your Tivoli StorageManager server administrator for further assistance.The administrator can review the Tivoli StorageManager server activity log for messages related to theproblem.

FMV5043W Unexpected retry request. The serverfound an error while writing the data.

Explanation: None.

System action: The client retries the operation.


FMV5044E Session rejected: All server sessions arecurrently in use.

Explanation: Server has all available sessions in useand cannot accept a new one at this time.

System action: Server canceled the current operation.

User response: Retry the operation.If the problemcontinues, see your system administrator to increase thenumber of concurrently active sessions to the server.

FMV5045E The session is rejected. Your passwordhas expired.

Explanation: Your password has expired.

System action: Server canceled the current operation.You are not allowed to connect to the server until thepassword is updated.

User response: Update your password. You may usethe SET PASSWORD command, or have theadministrator update your node.

FMV5046E Session rejected: Unknown or incorrectnode ID entered

Explanation: The node name you entered is notknown by the server, or you are attempting to access afile migrated to a different node.

System action: The current operation is canceled. Youare not allowed to connect to the server until yournode name is registered with the server. If attemptingto access a migrated file, your node name must be thesame node which migrated the file.

User response: Ensure that you entered your node

name correctly. If yes, see your system administrator.Verify that the server is using closed registration andthat your node name is registered with the server.

FMV5047E Session rejected: Duplicate ID entered.Node already logged onto server

Explanation: Another process using this node name isactive with the server.

System action: Cannot connect to the server. Canceledthe current operation.

User response: Ensure that your node name is uniqueto the server so that it cannot be used by anotherperson. See your system administrator to identify theowner of that node name.

FMV5048E Please choose a filespace.The filespaceto delete/set access cannot be found.

Explanation: The filespace to delete cannot be found.



FMV5049E Session rejected: The server is disabled

Explanation: The server is in a disabled state andcannot be accessed for normal activity.

System action: Canceled the current operation.

User response: Retry the operation after the serverreturns to an enabled state. If the problem continues,see your system administrator.

FMV5050E The server is not configured to allowopen registration.

Explanation: No authorization. Registration isrequired by your system administrator. The server isnot configured to allow open registration.

System action: Session not started.

User response: You must obtain a node and passwordfrom your system administrator.

FMV5051S Session rejected: the client code isdown-level

Explanation: The server version and your clientversion do not match. The client code is downlevel.


User response: See your system administrator to seewhat version to run for your location.



FMV5052E Session rejected: Downlevel server codeversion.

Explanation: The server version and your clientversion do not match. The server code is downlevel.


User response: See your system administrator to seewhat version to run for your location.

FMV5053W The operation was stopped by the user.

Explanation: The operation was stopped at the requestof the user. This usually occurs when the 'Q' key ispressed two times.



FMV5054E The operating system refused a requestfor memory allocation.

Explanation: The client requires access to memory inorder to store information as processing proceeds. Inthis case, more memory was requested than theoperating system would allocate. Possible reasonsinclude:


v The process in which the program runs has exceededthe maximum allocated memory.

v Some other error condition occurred. No memory isavailable.

System action: Client cannot complete the requestedoperation.

User response: Close all unneeded applications andtry the operation again. If the operation still fails, trydividing the task into several smaller units. Forexample, if a file specification contains severalhigh-level directories, run the task serially for eachdirectory. If the task is an incremental backup, use theoption "-memoryefficientbackup=yes".

FMV5055E File not found during Backup, Archiveor Migrate processing. No filespecification entered.

Explanation: The file being processed for backup,archive or migrate no longer exists on the client.Another process deleted the file before it could bebacked up, archived or migrated.



FMV5056E The specified directory path could notbe found.

Explanation: An invalid or unreachable directory pathwas specified.


User response: Try the operation again using a validdirectory path.

FMV5057E Access to the specified file or directoryis denied.




FMV5058E No file handles available



User response: Either free some file handles by endingother processes, or modify your system setup to allowfor more files to be open at the same time.

FMV5059E The file exists and cannot beoverwritten.

Explanation: The file being restored or retrieved existsand cannot be overwritten due to lack of authority oraccess permissions.


User response: Verify that you have sufficient accesspermissions to overwrite the file, then try the operationagain. If the problem persists, contact your systemadministrator or administrator for further assistance.

FMV5060E Invalid parameter passed.

Explanation: The system encountered an internalprogram error due to an invalid parameter.


User response: Ask your service representative tocheck the error log.



FMV5061E An invalid file handle passed. Reporthow you got this system error.

Explanation: An internal system error occurred. A fileoperation failed because of an invalid file handle.


User response: Try the operation again. If the failurepersists, obtain a service trace that captures theproblem and contact technical support for additionalassistance. Your administrator can help you configurethe trace.

FMV5062E Disk full

Explanation: Operation has stopped because thedestination disk is full.


User response: Free up disk space and retry theoperation

FMV5083E Drive specification contains wildcardcharacter.

Explanation: Drive name shouldn't contain wildcardcharacter.

System action: Wildcarded objects skipped.

User response: Use valid drive specification.

FMV5091S The Tivoli Storage Manager server doesnot currently have space in the storagepool for this file. This might be atemporary condition.

Explanation: This message is typically issued whenthe storage pool in which the data is being placed doesnot have sufficient to store the data, but that the spacewill be available soon. For example, a storage poolmigration may free up sufficient space to store the data.


User response: This is possibly a temporary condition.Try the operation again at a later time. If the errorpersists, contact your Tivoli Storage Manageradministrator, who can examine server console anderror logs to locate the cause of the problem.

FMV5092S Server out of data storage space.

Explanation: The server does not have any more spaceavailable to store the object.


User response: Report to your system administratorthat a storage pool on the server is full.

FMV5093S SLM_LICENSE_EXCEEDED: The clientlicenses for Tivoli Storage Manager areexceeded. See your Tivoli StorageManager administrator.

Explanation: Adding a new enrollment will exceed theproduct license count for this Tivoli Storage Managerserver.

System action: The client enrollment or connectionrequest ends.

User response: See your Tivoli Storage Manageradministrator to delete unused enrollments or negotiatean increase in the number of allowed licenses for yourserver.

FMV5094E Session Rejected. Sufficient servermemory is not available.

Explanation: The server does not have enoughmemory to allow your client to establish a connectionwith the server.


User response: Retry later or see your systemadministrator.

FMV5122E The specified filespace does not exist onthe server. The filespace might havebeen deleted by another client or anadministrator.

Explanation: The specified filespace does not exist onthe server. Your administrator might have alreadydeleted the filespace or another client using yourclient's node name might have deleted it.


User response: The filespace you selected does notexist any more. See your Tivoli Storage Manageradministrator for help in finding how the filespace wasdeleted.

FMV5123S Open registration failed because thespecified node name is already definedin the server.

Explanation: Open registration failed because a nodeis defined on the server with the same name.


User response: Retry with another node name.



FMV5124S Open registration failed because there isno default domain.

Explanation: Open registration failed because adefault policy domain does not exist in which to placeyour node. A default policy domain is required to fullysupport open node registration.

System action: Tivoli Storage Manager cancels thecurrent operation.

User response: See your Tivoli Storage Manageradministrator for assistance in registering your node.

FMV5125S Open registration failed because aninvalid node name was specified.

Explanation: Open registration failed because thespecified node name has invalid characters.


User response: Retry with another node name thatdoes not have any invalid characters.

FMV5126S Filespaces with duplicate names are notsupported. Please unmount theduplicate filespace.

Explanation: The selected filespace has a duplicatevolume label. Because Tivoli Storage Manager uses thevolume label to keep track of backup/archiveinformation, it cannot back up or archive files from afilespace with a duplicate volume label.

System action: Tivoli Storage Manager cannot selectthe volume.

User response: If the filespace needs to be available tothe system, exit Tivoli Storage Manager, and assign avolume label to the filespace. Restart Tivoli StorageManager and retry the operation. Otherwise, unmountthe duplicate filespace.

FMV5127I Tivoli Storage Manager has detected anincomplete setup! The system optionsfile 'dsm.sys' was not found, while theclient options file 'file-path' exists! Thewizard will guide you through theconfiguration process of the initial basicTSM client options files replacing yourcurrent option file. Would you like tocontinue?

Explanation: Tivoli Storage Manager has detected anincomplete setup. The system options file, dsm.sys, wasnot found. Additionally, a user options file, dsm.opt,was found. To complete the configuration theconfiguration wizard will create dsm.sys and replacedsm.opt with minimal settings.

System action: Tivoli Storage Manager may stop

User response: If the current version of dsm.opt isneeded, rename the file and restart Tivoli StorageManager. If the current version is not needed, select yesand allow Tivoli Storage Manager to replace the file.

FMV5128E The management class for this file didnot have a backup copy group.

Explanation: For backup operations, a file may onlybe bound to a management class that has a backupcopy group.

System action: Tivoli Storage Manager did not backup the file.

User response: See your Tivoli Storage Managersystem administrator for assistance in finding amanagement class with the required copy group. Theadministrator may also define such a management classfor you.

FMV5129E The management class for this file didnot have an archive copy groupspecified.

Explanation: For archive operations, a file may onlybe bound to a management class that has an archivecopy group.

System action: Tivoli Storage Manager did not archivethe file.

User response: See your Tivoli Storage Managersystem administrator for assistance in finding amanagement class with the required copy group. Theadministrator may also define such a management classfor you.

FMV5130W No filespaces selected for deletion

Explanation: You requested a deletion operationwithout selecting a client domain.

System action: Tivoli Storage Manager cannot performa deletion without a domain selected.

User response: Select the volumes you want to deleteand retry the operation.

FMV5132I Filespace deletion canceled by user

Explanation: You requested to cancel the filespacedeletion operation.

System action: The filespace deletion operationstopped.


FMV5124S • FMV5132I


FMV5133I Filespace 'filespace' was deleted

Explanation: The specified filespace was successfullydeleted.

System action: Tivoli Storage Manager deleted thefilespace.


FMV5134E Unable to delete the filespace becausethis node does not have permission todelete archived data and/or backed updata.

Explanation: You tried to delete a filespace that youdo not have permission to access.


User response: Ensure that you specify the correctfilespace, or specify a filespace you have access to.

FMV5135I Archive delete stopped by user

Explanation: You requested to stop the archive deleteoperation.

System action: Archive delete stopped.


FMV5138I Archive delete completed

Explanation: An archive delete was completed.

System action: Tivoli Storage Manager deleted thearchived files.


FMV5139E Your node does not have permission todelete archived files.

Explanation: Your node is registered at the serverwith the ARCHDELETE option set to 'no'. Thereforeyour node is not allowed by the server to deletearchived files.

System action: Tivoli Storage Manager did not deletethe archived files.

User response: See your Tivoli Storage Managersystem administrator. The administrator has authorityto delete archived files, and can also grant thatauthority to your node.

FMV5145W Server cannot restart the last restorerequest. Do you want to restore withoutrestart?

Explanation: The restart restore token has expired.The server cannot restart the restore from where it lastended.


User response: Retry the request without restart orabort the request.

FMV5146W You cannot perform this operation whileaccessing data for another node. Do youwish to switch back to accessing yourown node?

Explanation: The user cannot perform the selectedoperation while accessing another users data.


User response: Answer "Yes" to switch back toaccessing the server as the original node.

FMV5148W The server needs to do a one-timeconversion of your archive data beforeyou can continue. This operation maytake a long time, and cannot be canceledonce it has started. Are you willing towait for the conversion to complete?

Explanation: The server must do a conversion of thearchive data before continuing. The conversion couldtake a long time, and cannot be canceled once it isstarted.


User response: Answer “Yes” to start the archive dataconversion. If you answer “No”, the current operationwill be canceled.

FMV5150E An active restore for the same sourcefile specification exists. Unable tocontinue with this request.

Explanation: Currently, there is an active restore forthe same source file specification. Another restore of thesame source file specification cannot be started.

System action: The requested restore fails.

User response: Start another restore with a differentsource file specification.

FMV5151S This node currently has a pendingrestartable restore session. Therequested operation cannot completeuntil this session either completes or iscanceled.

Explanation: This operation can not be completedbecause a restartable restore session is pending. Theoperation is not allowed because the restartable sessionand the current operation affect the same file space.

FMV5133I • FMV5151S



User response: Issue the Query Restore command toview a list of your restartable restore sessions in theserver database. Issue the Cancel Restore command tocancel any unneeded restartable restore sessions.

FMV5152S Session Rejected: The server is notlicensed for this platform type. See yourTivoli Storage Manager administrator.

Explanation: The server license governs the types ofclient that can connect to it. The license for this serverdoes not include the requesting client type.

System action: The client enrollment or connectionrequest ends.

User response: See your Tivoli Storage Manageradministrator who must upgrade the server license toaccept your client type.

FMV5153E Session Rejected: The server does notallow a signon as a Unicode enabledclient.

Explanation: The client cannot establish a connectionto the server because of a unicode enabling mismatchbetween server and client.


User response: See your system administratorimmediately.

FMV5154I File is implicitly excluded

Explanation: You tried to back up or migrate a filethat is implicitly excluded.

System action: Tivoli Storage Manager will not backup or migrate an implicitly excluded file.


FMV5155E Valid password not available. The TivoliStorage Manager administrator for yoursystem must run Tivoli Storage Managerand enter the password to store itlocally.

Explanation: The file containing the stored passwordfor the specified server server-name is unavailable.


User response: The Tivoli Storage Manageradministrator for your system must set and store a newpassword.

FMV5158S Filespace deletion is in progress. Tryagain later.

Explanation: The filespace is in the process of beingdeleted.


User response: Try the operation again later. If thefilespace was being deleted, it could take awhile for itto complete. If the problem continues, report theproblem to your system administrator.

FMV5164E Backup or archive of drives withduplicate volume labels is not allowed.

Explanation: You tried to back up or archive a drivethat has a duplicate volume label. Because TivoliStorage Manager uses the volume label to keep track ofbackup or archive information, it cannot back up orarchive files from a drive with a duplicate volumelabel.

System action: Tivoli Storage Manager cannot selectthe drive for backup or archive operations.

User response: If the volume needs to be available tothe system, exit Tivoli Storage Manager and assign aunique volume label to the drive. Restart Tivoli StorageManager and try the operation again.

FMV5165E Drive has no volume label.Backup/Archive not allowed.

Explanation: You tried to backup or archive a drivethat has no volume label.

System action: Tivoli Storage Manager rejected theselected drive.

User response: If the drive is a floppy drive, place adisk with a volume label in it and retry the operation.If the disk is a hard drive, ensure the drive has avolume label, and retry the operation.

FMV5166E An error occurred while removinginclude-exclude statement 'statement'.Please try again.

Explanation: There was a problem with removing theinclude-exclude statement. Make sure that yourinclude-exclude statement is valid.

System action: No include-exclude statement wasremoved. Waiting for user action.

User response: Retry your operation. If you see thiserror message again, contact your system administrator



FMV5176W The requested virtual machine operationcannot be performed because a virtualmachine backup or restore operation isalready in progress. Please retry theoperation after the first operationcompletes.

Explanation: A virtual machine operation is already inprogress, so the requested virtual machine operationcannot be performed until the first operation complets.


User response: Wait for the first virtual machineoperation to complete, and then restart the currentrequest.

FMV5177E Client-side deduplication andserver-initiated sessions are mutuallyexclusive.

Explanation: Conflicting optionsSESSIONINIT=serveronly and DEDUPLICATION=yeswere specified. This combination is not allowed.


User response: Use client-initiated sessions or disableclient-side deduplication

FMV5178E Restart of the RSM service failed.Restart the RSM service manually.

Explanation: RSM database files have been restoredfrom the Tivoli Storage Manager server and imported.Tivoli Storage Manager has tried to restart the RSMservice on the user's behalf but has run into a problem.


User response: Restart the RSM service manually.

FMV5179E Tivoli Storage Manager is unable tocontinue. Exiting program.

Explanation: Tivoli Storage Manager ran into aproblem and is unable to continue. This error messageis usually preceded by other error messages. Resolvethose errors and try again.

System action: Program terminates.

User response: Fix the problem(s) that preceded thismessage and then restart Tivoli Storage Manager.

FMV5181E Invalid selection; A specific backup setmust be selected.

Explanation: A selection was made that might resultin multiple backup sets being restored at the sametime, but restoring multiple backup sets at the sametime is not supported.

System action: The backup set restore was notperformed.

User response: Select a specific backup set to berestored.

FMV5182E Multiple backup sets can not berestored at the same time.

Explanation: Multiple backup sets were selected to berestored, but restoring multiple backup sets at the sametime is not supported.

System action: The backup set restore was notperformed.

User response: Select a specific backup set to berestored.

FMV5183W Objects of different types cannot berestored at the same time.

Explanation: Restoring objects of different types is notallowed. For example, restoring Backup Sets andregular file objects at the same time is not possible.


User response: Select objects of the same type toperform restore operation.

FMV5184E Illegal Operation On Following Object:object

Explanation: Requested operation cannot beperformed on this object.


User response: Try another operation on this object, ortry the same operation on another object.

FMV5186E Server is downlevel, System Servicesand System State backup disabled forthis session.

Explanation: The operation cannot be performedbecause server version is downlevel.

System action: System Service and System Statebackup is disabled for this session.

User response: Must use level 5.2.0 or higher server.

FMV5187E Unable to set SHAREAS extendedattribute for file: 'pathname' Return code:'returncode' 'strerror' Reason code:'reasoncode'

Explanation: You must be the file owner or havesuperuser authority.

System action: File processed without settingattribute.

User response: The attribute must be set manually.



FMV5191E NT Active Directory is not online.Offline backup is not supported.

Explanation: NT Active Directory is not online whenperforming a backup operation. Offline backup is notsupported.


User response: Reboot computer and turn on ActiveDirectory, and try the operation again.

FMV5192E NT Active Directory is online. Onlinerestore is not supported.

Explanation: NT Active Directory is online whenperforming a restore operation. Online restore is notsupported.


User response: Reboot computer and enter ActiveDirectory repair mode, then try the operation again.

FMV5193E Certificate Services is not online.Offline backup is not supported.

Explanation: Certificate Services is not online whenperforming a backup operation. Offline backup is notsupported.


User response: Start Certificate Services and try theoperation again.

FMV5194E Certificate Services is online. Onlinerestore is not supported.

Explanation: Certificate Services is online whenperforming a restore operation. Online restore is notsupported.


User response: Stop Certificate Services and try theoperation again.

FMV5196W Invalid encryption key passwordentered.

Explanation: The encryption key password supplieddoes not meet the Tivoli Storage Manager requirements.This key can be up to 63 bytes in length and includethe following characters: A-Z Any letter, A through Z,uppercase or lowercase 0-9 Any number, 0 through 9 +Plus . Period _ Underscore - Hyphen & Ampersand

System action: Tivoli Storage Manager allows you totry again.


FMV5201E The specified function is notimplemented

Explanation: The specified function is notimplemented.



FMV5202I One or more system objects wereexcluded from processing by entries inthe include-exclude list.

Explanation: One or more system objects wereexcluded from processing by entries in theinclude-exclude list and the client did not process them.

System action: Excluded objects skipped.


FMV5204W Only one backup set may be selectedfor restore.

Explanation: Restoring multiple backup sets is notallowed. Only one backup set may be selected andrestored.


User response: Only one backup set may be selectedfor restore.

FMV5208E An invalid date or time was entered.

Explanation: An invalid date or time value wasentered. Either the syntax of the value was not correct,or an actual value (for example, “45” for month) wasinvalid.


User response: Identify and correct the invalid date ortime value. Refer to the user’s guide of thecorresponding platform for the correct date syntax.

FMV5209E System Volume backup failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while backing up files of the Windows 2000System Volume


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the backup operation



FMV5210E System Volume restore failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while restoring files of the Windows 2000System Volume


User response: Examine the Windows 2000 FileReplication Service Event log to insure the systemvolume was successfully initialized. Restart the serviceand retry the restore operation.

FMV5211E The cluster service is offline. The clusterservice must be online to perform anauthoritative cluster database restoreoperation.

Explanation: The cluster service must be online torestore the cluster database. Tivoli Storage Managertried to start the service and failed. It is possible that anauthoritative restore cannot be done.


User response: Start the cluster service and retry theoperation.

FMV5212E An error occurred while trying torename file space.

Explanation: This operation can not be completedbecause the file space could not be renamed.


User response: Contact system administrator for moreinformation.

FMV5215E function-type is not allowed on object'object'. Object is not sent to the server.

Explanation: The operation could not be performedon this object. For example, if this is an imageoperation, the selected path is a file or a directory andtherefore is not a valid object for image operations.

System action: This object is skipped.

User response: Verify that the object named is of atype supported by the command. For example, if afilespace name is required but a directory name wasgiven, change the name so it includes only the filespacename.

FMV5216E Could not establish a TCP/IP connectionwith address 'tcp-addr:tcp-port'. TheTCP/IP error is 'tcp-err-string' (errno =errno).

Explanation: A TCP/IP connection was attemptedwith a server or agent program and failed.


User response: Ensure that the target TCP/IP addressand port number is correct. Check to ensure that aTivoli Storage Manager server or agent has been startedat the target TCP/IP address and is configured to listenat the port listed in the message.

FMV5217E Your node does not have permission todelete backed up files.

Explanation: You cannot delete backed up files unlessyour Tivoli Storage Manager administrator hasauthorized your node to do so.

System action: Tivoli Storage Manager does not deletethe backed up files.

User response: Use the DSMC QUERY SESSIONcommand to verify your authorization. Ask your TivoliStorage Manager administrator to provide thenecessary authorization.

FMV5219W Objects of different groups cannot berestored at the same time.

Explanation: Restoring objects of different groups isnot allowed.


User response: Select objects of the same group toperform restore operation.

FMV5222E The archive description exceeds 254characters.

Explanation: Tivoli Storage Manager places amaximum length of 254 characters on the archivedescription.


User response: Issue the command again and specifya shorter valid archive description.

FMV5224W Error error code encountered whilereverting to the restored snapshot.

Explanation: After the virtual machine disks arerestored, the virtual machine is reverted to the restoredstate. The specified error was encountered whileperforming this revert operation.


User response: Try powering on the restored virtualmachine. If it fails to start, re-try the restore process.

FMV5225W Error error code encountered whileremoving the restored snapshot.

Explanation: After the virtual machine disks arerestored, the virtual machine is reverted to the restoredstate, and the snapshot is removed. The specified errorwas encountered while removing the snapshot.




User response: Try powering on the restored virtualmachine. If it fails to start, re-try the restore process.

FMV5226E The virtual machine backup operationfailed.

Explanation: The virtual machine backup operationfailed. Check the error log for details on why theoperation failed.



FMV5227E Tivoli Storage Manager detected anerror where both a snapshot name wasspecified, and a request to create asnapshot were specified.

Explanation: Either a snapshot name should bespecified, or a request for Tivoli Storage Manager tocreate the snapshot should be specified, but not both.


User response: This is an internal error and should bereported to your service representative.

FMV5228E A backup VM operation failed becauseVMMAXPARALLEL was reduced to 1and the client still cannot obtain aserver mount point.

Explanation: During a parallel backup operation,concurrent backup sessions required additional servermount points to perform the backups in parallel. Theclient attempted to obtain the additional mount points,but the client requests exceeded the number of mountpoints (MAXNUMMP) defined for the node. In aneffort to make the backup occur, the client reduced theVMMAXPARALLEL option to 1, but was still unable toobtain a mount point. The backup operation wasstopped.

System action: The backup operation was stopped

User response: Check the console or schedule log foradditional information. Retry the operation at a latertime. Ensure VMMAXPARALLEL is set to a value lessthan or equal to MAXNUMMP.

FMV5229E The Snapshot is already mounted forbackup 'backup-name'.

Explanation: The Snapshot is currently mounted onthe local machine or a remote machine. No mountoperation on the snapshot will be allowed until it hasbeen unmounted.



FMV5230E The Snapshot is already imported to thelocal system for backup 'backup-name'.

Explanation: The Snapshot is currently imported onthe local machine. This maybe becasue the Snapshot isin use or it was not created with the Import VSSsnapshots only when needed feature enabled.


User response: Remote Mount operation not allowedon snapshots that are currenlty imported.

FMV5231E VMDK size reported by VMwarevSphere API is different than actual sizeof vmdk file. Reissue the restorecommand with the testflag-VMRESTORE_INCVMDKSIZE.

Explanation: VMDK size reported by VMwarevSphere API for virtual machine configuration isdifferent than actual size of vmdk file. This can be theresult of running a storage alignment tool on vmdkfiles before backup.

System action: Restore processing stops.

User response: Reissue the restore command with thetestflag -VMRESTORE_INCVMDKSIZE.

FMV5232I The virtual machine backup operationwas skipped.

Explanation: The virtual machine backup operationwas skipped. Check the error log for details on why theoperation was skipped.

System action: Processing of the virtual machine isskipped

User response: Review the console output and errorlogs for the details.

FMV5245W TCPWINDOWSIZE optionCur isspecified, but exceeds the maximumvalue allowed by Tivoli StorageManager. TCPWINDOWSIZE optionNewwill be used instead.

Explanation: Refer to product manual for moreinformation about the TCPWINDOWSIZE option.

System action: The operation continues with themaximum value allowed by Tivoli Storage Manager.

User response: Set TCP window size to a value in theallowable range.



FMV5246W TCPWINDOWSIZE optionCur isspecified, but exceeds the maximumvalue allowed by the operating system.TCPWINDOWSIZE optionNew will beused instead.

Explanation: The specified value is within the rangeallowed by Tivoli Storage Manager, but the operatingsystem restricts the value to something less.

System action: The operation continues with themaximum value allowed by the operating system.

User response: Set TCP window size to a valueallowed by the operating system.

FMV5249E The virtual machine restore operationfailed.

Explanation: The virtual machine restore operationfailed. Check the error log for details on why theoperation failed.



FMV5250E An unexpected error was encountered.Tivoli Storage Manager function name :function-name Tivoli Storage Managerfunction : function-desc Tivoli StorageManager return code : TSM-rc TivoliStorage Manager file : file-name(line-number)

Explanation: None.



FMV5251E The snapshot provider is not availablefor this operation.

Explanation: Tivoli Storage Manager was not able totake a snapshot because the snapshot provider is notavailable.


User response: If you are attempting an operationusing the Microsoft Volume Shadow Copy service makesure that Volume Shadow Copy service is installed onthe system and also ensure that the Tivoli StorageManager snapshot plugin "pivss.dll" is present.

FMV5252E Tivoli Storage Manager attempted toexecute a system command which failed.command : command rc : rc

Explanation: Tivoli Storage Manager needed toexecute a system command in conjunction with asnapshot operation.



FMV5253W The system could not create VolumeShadow Copy Services staging directory'dir'.

Explanation: The system was unable to create auser-specified location for the Volume Shadow CopyServices staging area. The default staging area on thesystem drive will be used instead.


User response: Check the option to specify the stagingarea for Volume Shadow Copy Services operations andspecify a valid location.

FMV5254E The Volume Shadow Copy Servicessnapshot plugin 'pivss.dll' was notfound.

Explanation: The system cannot find the VSS snapshotplugin 'pivss.dll' in any of the plugin locations.


User response: Check the Tivoli Storage Managerinstallation to ensure the plugin was installed correctly.

FMV5255E Unable to copy local file 'local-file' toremote location 'remote-file'.

Explanation: An attempt to transfer a file to a remotesystem failed..


User response: Ensure that the directory path on theremote system exists and that the Tivoli StorageManager application has the proper authority to writeto that location.

FMV5257E The volume 'volume' does not supportthe requested VSS operation.

Explanation: The volume does not support therequested VSS operation. Some reasons for this errorinclude the following conditions:

v For off-load backup requests, a hardware providercannot be found

v For off-load backup requests, the provider does notsupport transportable media

v For local backup requests, the provider does notsupport persistent snapshots



v For backup requests of Hyper-V virtual machinesthat are located on the volume with a Cluster SharedVolume File System and theVSSUSESYSTEMPROVIDER option is set to YES


User response: Try the backup again, and use asupported backup destination. If you are backing upHyper-V VMs and the VSSUSESYSTEMPROVIDERoption is set to YES, try the operation again, with theVSSUSESYSTEMPROVIDER option set to NO.

FMV5258E Microsoft volume shadow copysnapshot initialization failed.

Explanation: IBM Tivoli Storage Manager encounteredan error while initializing the Microsoft VolumeShadow Copy Service for backup or restore. The IBMTivoli Storage Manager error log and Windows eventlog can contain additional information about this error.

System action: IBM Tivoli Storage Manager stops theoperation.

User response: Try the operation again. If the errorpersists, review the IBM Tivoli Storage Manager errorlog and Windows event log for information related tothis error. Use the Windows command VSSADMINLIST WRITERS to determine the status of the VolumeShadow Copy service. Reboot the machine to clear thevolume shadow copy error state. If the system is aDomain Controller and the Active Directory service isstopped, restart the Active Directory service.

FMV5259W Failed to update volume 'volume' forread-write access used for 'volume'.

Explanation: Changing the volume to read-writeaccess requires exclusive access to the volume. If thevolume is opened by any application, this operationwill fail.


User response: Close all the applications using thevolumes and use operating system's interface to mountfailed volume for read-write access.

FMV5260W Restore object 'volume' has volume eithersource 'volume' or target 'volume' volumethat has already been selected forrestore from a different snapshotvolumes. It will be restore usingfile-level copy.

Explanation: This error can occur when multipleobjects are selected for snapshot restore and have dataoverlapping on the volumes and were selected forrestore from different backup versions. Snapshot restorecan only be performed from one local backup.

System action: The restore object identified in themessage will be restored using the file-level copy after

snapshot restore is completed.

User response: Retry the restore of identified objectseparately for faster restore using snapshot.

FMV5261W An attempt to create a snapshot hasfailed. Another attempt will be made tocreate the snapshot in number seconds.

Explanation: An attempt to create a snapshot hasfailed with a retryable error. The program will wait fora short time and retry the operation.


User response: Check the IBM Tivoli Storage Managererror logs for additional information.

FMV5262I Snapshot restore will failover tofile-level copy from snapshot volume.

Explanation: Snapshot restore is not possible due toan error at this time. Tivoli Storage Managerwillautomatically fails over to other restore method tocomplete the restore operation.


User response: Check Tivoli Storage Manager errorlog for more information from messages preceding thisone to identify the error condition.

FMV5263E Snapshot module for 'snapshot provider'failed with error 'error msg'.

Explanation: The snapshot module for identifiedsnapshot provider failed to perform the operation andreturned with the identified error.

System action: Restore may automatically failover toalternate restore method 'file-level copy from snapshotvolume' if possible. Otherwise, processing stops.

User response: Check Tivoli Storage Manager errorlog for more information from messages preceding thisone. Use snapshot provider interface to identify andcorrect the problem.

FMV5264W No snapshot plugin found for 'snapshotprovider' snapshot provider.

Explanation: The snapshot restore requires a pluginfor the specified snapshot provider type. The pluginmust be installed under Tivoli Storage Managerdirectory.

System action: Restore will failover to alternaterestore method of 'file-level copy from snapshotvolume'.

User response: Contact your Tivoli Storage Manageradministrator to obtain and install the required pluginmodule.



FMV5265W Snapshot restore has already beeninitialized using 'snapshot provider'provider module. Another module for'snapshot provider' provider can not beloaded at the same time for restore of'object name'.

Explanation: This error occurs when restoringmultiple LOCAL backup objects that were createdusing different snapshot providers. Snapshot restorecan only be done using one snapshot interface.

System action: Restore will failover to file-level copyrestore from snapshot volume.

User response: If snapshot restore is desired for theobject identified in the message, restore it using aseparate command.

FMV5266E File-level copy restore of 'object name'failed.

Explanation: Data files could not be copied from thelocal backup to their destination, causing restore to fail.

System action: Processing continues to another object,if multiple objects are selected for restore.

User response: Check Tivoli Storage Manager errorlog for more information from messages preceding thisone.

FMV5267E Disk Mapper module failed for theoperation.

Explanation: An underlying Tivoli Storage Manageroperation has failed to perform the operation due tosystem error.


User response: Check Tivoli Storage Manager errorlog for more information from messages preceding thisone to identify cause of the failure. Contact TivoliStorage Manager administrator for more information.

FMV5268W The Microsoft Volume Shadow CopyServices writer 'name' current state (state)is not valid for the current operation.

Explanation: None.

System action: The system will retry the operationautomatically after thirty seconds up to three times toallow the writer to return to the proper state. If afterthree attempts the writer is still in the incorrect state,the operation will fail.

User response: Determine if there are other VolumeShadow Copy Services operations that are occurringconcurrently with the current operation.

FMV5269E The Microsoft Volume Shadow CopyServices writer 'name' current state (state)is not valid for the current operation orcannot be determined. The last errorreported is 'error'.

Explanation: None.


User response: Check the Microsoft event log todetermine if there are any problems with the writer.

FMV5270E A VSS restore request with timestamp'time1' conflicts with a restore requestwith timestamp 'time2'

Explanation: A VSS restore request was issued whichrequires restoring multiple components which reside inVSS backup documents with different backuptimestamps. For example, a user backs up Exchangestorage group STG1 on Monday and Exchange storagegroup STG2 on Tuesday. On Wednesday, the user triesto restore STG1 and STG2.


User response: Resubmit the restore request asseparate requests for each component. For example, ifyou receive this error trying to restore Exchangestorage groups STG1 and STG2, resubmit a restorerequest for storage group STG1 and a separate restorerequest for storage group STG2.

FMV5271E A Microsoft Volume Shadow CopyServices writer is in an invalid statebefore snapshot initialization.

Explanation: None.


User response: See the IBM Tivoli Storage Managererror logs for additional information.

One of the VSS writers is in an invalid or unexpectedstate. Try the command "vssadmin list writers" andcheck the state of VSS writers. Writers must be inSTABLE state before IBM Tivoli Storage Manager cancontinue with VSS operations. Some of the writers canrecover automatically from minor errors. In most cases,restarting a writer solves the problem. The easiest wayto restart writers is to restart the operating system. It ispossible to restart the specific service that implements aVSS writer, but it is difficult to determine which serviceto restart.

FMV5272E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter snapshot initialization.

Explanation: None.




User response: See the Tivoli Storage Manager errorlog for additional information.

FMV5273E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter taking a snapshot.

Explanation: None.



FMV5274E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter backup completion.

Explanation: None.



FMV5275E A Microsoft Volume Shadow CopyServices writer is in an invalid statebefore restore initialization.

Explanation: None.



FMV5276E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter preparing for a restore operation.

Explanation: None.



FMV5277E A Microsoft Volume Shadow CopyServices writer is in an invalid stateafter restore termination.

Explanation: None.



FMV5279E Error processing 'filename': file notfound.

Explanation: The file being processed for backup,archive, or migrate, no longer exists on the client.Another process deleted the file before it was backed

up, archived, or migrated by IBM Tivoli StorageManager.



FMV5280E Object enumeration from a file set orfile list failed.

Explanation: For more information, see the IBM TivoliStorage Manager client error log. This message isalways accompanied by error log message FMV5279E ifthe object was not found or by FMV5250E for othercauses, for example, access was denied. These messagesidentify the object in question.


User response: See the user response based on othermessages in the client error log.

FMV5281E A remote backup failure has occurred.remote node name : node remote address: address multi-node name : multi-nodeerror message : msg return code : rc

Explanation: For more information, see the IBM TivoliStorage Manager client error log on the remote system.



FMV5282E A remote backup failure has occurred.

Explanation: For more information, see the IBM TivoliStorage Manager client error log.



FMV5283E The operation was unsuccessful.

Explanation: None.



FMV5284I Tivoli Storage Manager has detected anincomplete setup! The client options file'dsm.opt' was not found, while thesystem options file 'file-path' exists! Thewizard will guide you through theconfiguration process of the initial basicTSM client options files replacing yourcurrent option file. Would you like tocontinue?

Explanation: Tivoli Storage Manager has detected an



incomplete setup. The user options file, dsm.opt, wasnot found. Additionally, a system options file, dsm.sys,was found. To complete the configuration theconfiguration wizard will create dsm.opt and replacedsm.sys with minimal settings.

System action: Tivoli Storage Manager may stop

User response: If the current version of dsm.sys isneeded, rename the file and restart Tivoli StorageManager. If the current version is not needed, select yesand allow Tivoli Storage Manager to replace the file.

FMV5285E The Microsoft Volume Shadow CopyServices (VSS) backup XML documentis not valid for restore. For moreinformation, see the Tivoli StorageManager client error log.

Explanation: Microsoft has released a Volume ShadowCopy Services (VSS) update in the following operatingsystem versions:

v Windows 2003 update rollup package KB940349

v Windows Vista Service Pack 1

This new VSS fix packages causes VSS to generates.xml control files in a format which is not compatiblewith the earlier versions of VSS. This error can occurwhen a system state restore is being performed from abase operating system level which does not have theVSS fixes applied and the system state backup fileswere created by an operating system level that didhave the VSS fixes applied.


User response: The restore procedure for Windowssystem state requires that the operating system versionand service pack level used to initiate the restore be atthe same operating system and service pack level usedto create the system state backup. In addition note thefollowing:

v On Windows 2003 systems you must also apply theVSS rollup package KB940349 prior to performingthe Ssystem state restore.

v On Windows Vista you must apply the same servicepack that was installed at the time of backup prior toperforming the system state restore.

FMV5286I The VSS Instant Restore operation wassuccessful but some existing VSSsnapshots have been deleted by the VSSprovider.

Explanation: A successful VSS Instant Restoreoperation was performed for snapshot volumes thatwere in a dependent relationship. In order for therestore process to succeed, it was necessary to removethe snapshot volumes causing the dependency. Thosesnapshot volumes typically represent newer snapshotbackups. This forced TSM to remove the backups thatincluded the deleted snapshots. This situation is typical

when using SAN Volume Controller (SVC)space-efficient volumes that have multiple snapshots.



FMV5287W VSS restore operation will be performedusing VSS Fast Restore because the XIVVSS Hardware Provider is at level 2.2.2.

Explanation: XIV VSS Hardware Provider 2.2.2 hasissues with VSS Instant Restore. Please update the XIVVSS Hardware Provider to version 2.2.3, or later.


User response: Update XIV VSS Hardware Provider toversion 2.2.3, or later.

FMV5288W Test flag DISCARDZEROFILEDATAenabled. Discarding data for zero lengthobject file-name

Explanation: During the restore of a zero length file ordirectory, data was decompressed. This data could beExtended Attributes, Alternate Streams, or ACL data.By default this data is restored. Because theDISCARDZEROFILEDATA test flag is set the data isdiscarded.

System action: The data is discarded and processingcontinues

User response: Note the file or directory name in thismessage and determine if the discarded data needs tobe reset through some other means.

FMV5296I The virtual machine 'vm-name' containsone or more virtual disks that are oftype Thick Eager Zero. Creating disks ofthis type can take a long time. Thisrestore operation might time out beforethe disks are ready.

Explanation: Restoring a VM that has Thick EagerZero virtual disks can take a long time to completebecause the disks are zero-filled to obscure anyprevious content. The time that is required to provisiona Thick Eager Zero disk depends on processing loadson the VMware resources (vCenter and datastores).

System action: None

User response: Reattempt the restore operation at atime when the processing load is light on thedatacenter and vCenter resources

FMV5298E A Flashcopy background copy is inprogress between source volume: andtarget volume: .

Explanation: A Flashcopy background copy from a



previous operation is not complete for the given sourceand target volumes.


User response: Please wait until the background copyis complete and retry the command.

FMV5299E A Flashcopy association exists betweensource volume: and a different targetvolume: .

Explanation: A Flashcopy association exists betweenthe source volume and a target other than thedesignated target volume.

System action: Restore command will fail.

User response: Please withdraw the Flashcopyassociation between the source volume and the targetvolume and retry the restore command.

FMV5300E Error detected in specified file list 'filelist name' during processing of line linenumber: found an invalid external objectID / inode number / inode generation number/ restore order number / alias entry: 'invalidentry'. Invalid line: 'invalid entry'

Explanation: File list parsing failed because of aninvalid entry.

System action: The operation aborted because of anfile list error.

User response: Correct the invalid file list entry andrestart the operation.

FMV5301E Error detected in specified file list 'filelist name' during processing of line linenumber: found an invalid ordering ofexternal object IDs. ext. object ID ofprevious file: previous external object IDext. object ID of current file: currentexternal object ID

Explanation: File list parsing failed because of aninvalid ordering of the external object IDs.

System action: The operation aborted because of anfile list error.

User response: Correct the invalid file list orderingand restart the operation.

FMV5302E File list stream error to file 'file list name'detected during processing of line linenumber.

Explanation: File list processing failed because of anstream error.

System action: The operation aborted because of anfile list stream error.

User response: Check the specified file list and restartthe operation.

FMV5303I ***** date Processed count Tivoli StorageManager server and count file listobjects *****

Explanation: Tivoli Storage Manager has processedthe specified number of Tivoli Storage Manager serverand file list objects.



FMV5304E program-name: synchronous file deletionfailed for external object ID: externalobject ID.

Explanation: The HSM client could not delete anobject on the Tivoli Storage Manager Server.

System action: The current file is skipped forsynchronous file deletion and the process will continue.

User response: Check the Tivoli Storage Managerserver log file.

FMV5307E The session is rejected. The server doesnot allow a signon of a client that is notenabled for space-managementretention-protection.

Explanation: The client cannot establish a connectionto the server because the server is enabled forspace-management retention-protection and the client isnot.

System action: The session is not started.


FMV5821E Cannot connect to Active Directory.

Explanation: Tivoli Storage Manager could notconnect to Active Directory. The Active Directory iseither not running or you don't have enoughpermissions to use it.


User response: Make sure your system is set up asActive Directory controller and the the service is active.Make sure you are logged in as a user with sufficientrights to administer the Active Directory.

FMV5822E No Active Directory objects matchquery.

Explanation: A search has been performed in ActiveDirectory; however, no objects matching the query werefound.




User response: Make sure you specify a validdistinguished name of Active Directory object or acontainer, or a valid wildcarded name, and that youhave sufficient rights to administer the Active Directory.

FMV5823W Object exists, skipping

Explanation: The client tried to restore the specifiedobject, but the object already existed in the targetrestore location and the user chose not to replace theexisting object.

System action: The object is skipped, a message islogged in dsmerror.log, and restore processingcontinues with the next object.

User response: The object was skipped because eitherREPLACE NO was in effect, causing all existing objectsto be skipped, or REPLACE PROMPT was in effect,and when prompted, the user chose to skip this object.No additional action is necessary if the decision to skipthe object was deliberate. Otherwise the operation canbe retried using either REPLACE ALL (automaticallyreplace existing object) or REPLACE PROMPT (promptthe user whether to replace the object).

FMV5824E Invalid Active Directory searchspecification.

Explanation: The search specification for ActiveDirectory objects is not valid.


User response: Refer to the documentation forsupported Active Directory syntax.

FMV5825E Reanimate 'tombstone-name' to'distinguished-name' failed. See the errorlog for more details.

Explanation: An attempt to reanimate ActiveDirectory tombstone object has been performed, but anerror occurred.

System action: Processing continues to process allother tombstone objects per user's request.


FMV5826E Restoring to a read-only domaincontroller is not allowed.

Explanation: An attempt to restore to a read-onlydomain controller.



FMV5827E A backup copy of the Active Directorydatabase was not found.

Explanation: An attempt to restore Active Directoryobjects from a database that was not backed up.


User response: Verify the Active Directory was backedup with system state.

FMV5828E A system state file space was not foundon the server. Active Directory functionscan not be executed.

Explanation: An attempt to restore the ActiveDirectory database from a system state backup thatdoes not exist.


User response: Verify that system state was backed upor back up the system state then retry the command.

FMV5829E A system state backup on the specifieddate was not found. Active Directoryfunctions can not be executed.

Explanation: An attempt to restore the ActiveDirectory database from a system state backup thatdoes not exist.


User response: Verify that system state was backed upon the specified date or specify a new date.

FMV5830E Restore of object 'tombstone-name' is notallowed by Active Directory.

Explanation: Object of certain types cannot berestored. This is a system limitation.

System action: Processing continues to process allother objects per user's request.


FMV5831E Restore for this object is not allowed byActive Directory.

Explanation: Object of certain types cannot be restord.This is a system limitation.



FMV5832E Reanimate tombstone object failed. Seethe error log for more details.

Explanation: An attempt to reanimate ActiveDirectory tombstone object has been performed, but anerror occurred.





FMV5833E This system is a Domain Controller butthe Active Directory service is stopped.You can not perform the operationunless the Active Directory service isrunning.

Explanation: The Active Directory service must berunning when you back up or restore the system stateor operate on Active Directory objects. When the ActiveDirectory service is running, it can be in online state orin offline state. When you query or restore ActiveDirectory objects, or back up the system state, theActive Directory service must be online. When yourestore the system state, the Active Directory servicemust be offline (but not stopped).


User response: If you are querying or a restoring theActive Directory objects or backing up the system state,put the Active Directory service in online state bystarting the Active Directory service. If you arerestoring the system state, put the Active Directoryservice in offline state by rebooting to the ActiveDirectory Restore Mode. When the Active Directoryservice is in the appropriate state, retry the operation.

FMV5834E Unexpected LDAP error occurred. Seethe error log for more details.

Explanation: An unexpected error occurred duringActive Directory tombstone reanimation.


User response: Check the error log for detailedinformation on the LDAP error.

FMV5835E An LDAP operation returned return code:'error string'

Explanation: An unexpected error occurred duringActive Directory tombstone reanimation.



FMV5836W One or more attributes were notrestored. See the error log.

Explanation: During processing of an Active Directoryobject, one or more object attributes could not berestored.

System action: Processing continues to process allother Active Directory objects per user's request.

User response: Check the error log for detailedinformation on which attribute(s) could not be restored.

FMV5837W 'object name': attribute 'attribute name'could not be restored.

Explanation: The listed attribute could not be restoredduring processing on the Active Directory object.

System action: Processing continues to process allother Active Directory objects per user's request.


FMV5838E The utility dsamain.exe does not existon the system. You cannot perform theoperation unless Tivoli Storage Managercan launch this utility.

Explanation: You attempted to launch dsamain.exe,but the utility does not exist.


User response: Verify that the dsamain.exe utilityexists in the Windows system32 directory. When youcan run the utility independently of Tivoli StorageManager, retry the operation.

FMV5839E The Active Directory object specificationis not allowed.

Explanation: You attempted to restore the domainobject (starting with "DC="), or you attempted torestore all objects ("name=*"), or you did not specifyanything.


User response: Modify the specification then retry theoperation.

FMV5840E The current user is not a member of theAdministrators group, and cannotperform this function.

Explanation: You must be a member of theAdministrators group to perform the Active Directoryobjects function.


User response: Log on with a user who is a memberof the Administrators group or add this user to theAdministrators group then retry the operation.

FMV5841E Active Directory database could not beopened.

Explanation: An error occurred while opening therestored Active Directory database.


User response: Make sure ntdsutil.exe utility is



located in the same directory with Tivoli StorageManager client executables. If it doesn't exist, reinstallthe client. Verify that the dsamain.exe utility exists inthe Windows system32 directory. When you can runthe utility independently of Tivoli Storage Manager,retry the operation. If the problem persists, contact thesupport.

FMV5842E 'tombstone-name': object class violation.

Explanation: Object class error violation occurredduring tombstone reanimation. This can happen if theActive Directory schema was modified and is no longercompatible with the tombstone.


User response: Recreate the failing object manually orrestore it from a backup.

FMV5843E Object class violation.

Explanation: Object class error violation occurredduring tombstone reanimation. This can happen if theActive Directory schema was modified and is no longercompatible with the tombstone.


User response: Recreate the failing object manually orrestore it from a backup.

FMV5844E Unable to update password.

Explanation: An error occurred during the passwordupdate attempt.


User response: Try to update the password again.

FMV5845E Unable to update password because themaximum number of update attemptshas been exceeded.

Explanation: This message is issued after making 3unsuccessful attempts to update the password. Theoriginal password for the node was entered incorrectly;the new password does not meet the length or validcharacter requirements for our passwords; or there wasa mismatch between the first and second times the newpassword was entered.

System action: The password is not updated.

User response:

v Make sure the original password is entered correctly.Contact your Tivoli Storage Manager administratorfor further assistance if you do not know the originalpassword.

v Make sure the new password meets the passwordlength and character requirements.

v You will be prompted to enter the new passwordtwo times, so make sure it is entered correctly bothtimes.

FMV5876I SET EVENT Activate Retentioncompleted

Explanation: The Data Retention ACTIVATEtransaction has completed.

System action: Tivoli Storage Manager activated theobjects that were selected.


FMV5877I SET EVENT Hold completed

Explanation: The Data Retention HOLD transactionhas completed.

System action: Tivoli Storage Manager held theobjects that were selected.


FMV5878I SET EVENT Release completed

Explanation: The Data Retention RELEASE transactionhas completed.

System action: Tivoli Storage Manager released theobjects that were selected.


FMV7421W The archive attribute for file filenamecannot be reset. The return code fromWindows API functionSetFileAttributes() is rc.

Explanation: The client was unable to reset thearchive attribute for the file indicated in the message.This error is due to an error received from theWindows API function SetFileAttributes().


User response: Try the operation again. If the problempersists, it may be indicative of a problem with the file.Contact your system administrator or Tivoli StorageManager administrator for further assistance.

FMV7422E Unsupported action 'action' in schedule'schedule name'.

Explanation: The scheduled action is unknown to thecurrent version of the IBM Tivoli Storage Managerclient and cannot be performed by means of aschedule. The most likely cause is that the scheduledaction requires a later version of the backup-archiveclient. The unsupported action is displayed as anumber because the text description is not available.



Scheduled actions and their corresponding actionnumber can be found by searching for this message onthe IBM Tivoli Storage Manager support site.

System action: The scheduled action is not performedor queried.

User response: Search the IBM Tivoli Storage Managersupport site for this message to find information aboutscheduled actions, their corresponding action numbersand the client version at which the action is supported.Then upgrade your IBM Tivoli Storage Manager clientto a version that supports running this action as ascheduled event. Until the client is upgraded, you canrun the action manually if your version of the clientsupports it.

FMV7423E Use Set Access backup <vmname>-TYPE=VM for VMware backup filespaces. Use of the long form fs-name isnot allowed.

Explanation: You have chosen to set access using thelong-form VM file space name. This name format is notplatform independent and requires special processing.Use the -TYPE=VM option and supply only the VMname.

System action: The set access command is notprocessed.

User response: Enter the set access command usingthe -TYPE=VM option and the short form of the VMfile space name which is simply the VM name.

FMV7500W Object 'object-name' could not be boundto management class 'mgmt-specified'specified in an 'option' statement.

Explanation: The management class specified in aninclude statement was not valid. If the includestatement is an "INCLUDE.SIZE" statement thewarning message will be issued if an appropriatecopygroup is defined for the management class. Forexample, this warning will be issued on a backupoperation if no backup copygroup is defined for themanagement class or this message will be issued on anarchive operation if no archive copygroup is definedfor the management class.

System action: The management class on the includestatement is ignored and processing continues.

User response: Contact the Tivoli Storage Manageradministrator to correct the appropriate copygroupdefinition on the Tivoli Storage Manager Server.

FMV7501E An invalid host address was received.Host address is too long.

Explanation: An invalid host parameter was found inthe HTTP Request. The parameter is too long. Themaximum length for a host address is 64 characters.

System action: Tivoli Storage Manager returns HTTPerror code 400 Bad Request.

User response: Use a host machine with avalid/shorter host address.

FMV7502E An invalid filename was received.Filename is too long.

Explanation: A filename passed to the dsmcad serviceis too long and thus invalid.

System action: Tivoli Storage Manager returns HTTPerror code 400 Bad Request.

User response: Retry connecting to dsmcad but use avalid/shorter filename.

FMV7507W The node name entry is invalid. Pleasetry again.

Explanation: An invalid entry is entered on the NodeName field.

System action: Tivoli Storage Manager prompts youto enter a valid node name.

User response: Enter a valid node name or see yoursystem administrator for the correct syntax.

FMV7510E A NAS node cannot be used for thisoperation.

Explanation: NAS nodes cannot be used foroperations like Access Another Node.

System action: Tivoli Storage Manager prompts youto enter a valid node name.

User response: Enter a valid, non-NAS, Tivoli StorageManager node name.

FMV7524E SSL is required.

Explanation: SSL is required to protect the clientpassword during authentication.


User response: Enable SSL communication or setSSLREQUIRED to NO.

FMV7525E SSL is required by server.

Explanation: SSL is required to protect the clientpassword during authentication.


User response: Enable SSL communication or contactyour Tivoli Storage Manager server administrator.



FMV7526E The SNAPSHOTROOT option is notvalid with either of the followingoptions: -GROUPNAME and-VIRTUALFSNAME.

Explanation: The SNAPSHOTROOT option isincompatible with the -GROUPNAME and-VIRTUALFSNAME options and cannot be used witheither one of those options.


User response: For information about backup-archiveclient processing options, see IBM Tivoli StorageManager Backup-archive Clients Installation and User'sGuide.

FMV7527E The (-SNAPSHOTROOT) option is notvalid in conjunction with num-specs filespecifications.

Explanation: The (-SNAPSHOTROOT) option must beused in conjunction with only one file specification. Itcannot be used with zero file specification (e.g., anINCREMENTAL command with no file specifications)or with more than one file specification.



FMV7529E The specified SNAPSHOTROOT'obj-name' is not valid for the BACKUPIMAGE command.

Explanation: When you use the (-SNAPSHOTROOT)option with the BACKUP IMAGE command,SNAPSHOTROOT must specify the device name of thelogical volume containing the snapshot for the backup.An example is /dev/fslv01 (on Unix) or\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1 (on Windows).

With BACKUP IMAGE, SNAPSHOTROOT cannot beused unless SNAPSHOTPROVIDERIMAGE has one ofthe following values in effect:

v VSS

v JFS2


User response: For the correct use of the(-SNAPSHOTROOT) option, see the appropriateBackup-Archive Client Installation and User's Guide bookfor your operating system.

FMV7531E The (-SNAPSHOTROOT) option isinvalid when processing the NetWareNDS or Server Specific Information.

Explanation: The (-SNAPSHOTROOT) option is only

intended with NetWare file server volumes and is notcompatible with processing the NDS or Server SpecificInformation on NetWare.



FMV7533E The specified file system 'obj-name' doesnot exist or is not local.

Explanation: When you use the (-SNAPSHOTROOT)option, the target and source file systems must be valid,local file systems. The file systems cannot be non-local,such as a remote NetWare drive, a remote Windowsdrive, or an NFS mount. The (-SNAPSHOTROOT)option is valid for local operations only.


User response: For the correct use of the(-SNAPSHOTROOT) option, see the appropriateBackup-Archive Client Installation and User's Guide bookfor your operating system.

FMV7534W Initialization functions cannot open/dev/tty special file. errno = errno-value,error message

Explanation: Special file /dev/tty, required bycommand line internal editor could not be openedduring initialization. The system set the error codeerrno-value.

System action: Processing continues as if EDITORoption was set to NO.

User response: Check your terminal settings.

FMV7535W Command line internal editor can notbe initialized.

Explanation: EDITOR option is set to YES in theoptions file, but command line internal editor can notbe started.

System action: Processing continues as if EDITORoption was set to NO

User response: Check previous messages to determinethe reason why the internal editor could not be started.

FMV7543E Error: Scout is not available for objectquery. Either scout is not running or theinitial file system scan has not finished.

Explanation: The scout daemon must be running forthe reconcile process to do a query for all migratedfiles. If the scout daemon is not running or the initialfile system scan has not finished you cannot run thereconcile tool in orphan check mode.




User response: Ensure that the scout daemon isrunning. If the scout daemon is not running, restart itand retry the command. If the scout daemon isrunning, wait until it finishes the initial file systemscan. You can check the current status of the scoutdaemon by using the dsmscoutd scanplan command.

FMV7544E ICC routine icc-routine failed with thefollowing error: "error-string".

Explanation: There was an error within ICCcryptography library while processing the data. Forexample, this problem can occur when encrypted clientdata is corrupted, so the restore operation cannotcorrectly decrypt it. This message reports an error codeand problem description which can be used by TivoliStorage Manager technical support personnel todetermine the cause of the failure.


User response: Ensure Tivoli Storage Managersoftware is installed correctly. If needed, reinstall thesoftware. Make sure you use the correct encryption keypassword for the data. Make sure there are no TivoliStorage Manager server or network problems that mayaffect the transfer of data. If the problem still exists,contact Tivoli Storage Manager technical support.

FMV7545E Unexpected error while encrypting thedata.

Explanation: There was an error while encrypting thedata. See the error log for more information.

System action: The object is not backed up.

User response: Ensure Tivoli Storage Managersoftware is installed correctly. If needed, reinstall thesoftware. Retry the operation. If the problem still exists,contact Tivoli Storage Manager technical support.

FMV7546E Unexpected error while decrypting thedata.

Explanation: There was an error while decrypting thedata. See the error log for more information. This canhappen if the encrypted data has been corrupted whilein storage, during the network transfer, or both.

System action: The object is not restored.

User response: Ensure Tivoli Storage Managersoftware is installed correctly. If needed, reinstall thesoftware. Make sure there are no Tivoli StorageManager server or network problems that may affectthe transfer of data. Retry the operation. If the problemstill exists, contact Tivoli Storage Manager technicalsupport.

FMV7547E Unexpected error while digesting thedata.

Explanation: There was an error while digesting thedata. See the error log for more information.

System action: The object is not backed up.

User response: Ensure Tivoli Storage Managersoftware is installed correctly. If needed, reinstall thesoftware. Retry the operation. If the problem still exists,contact Tivoli Storage Manager technical support.

FMV7550E The absolute option requires using theCreateNewBase=yes option whenperforming a snapshot differentialbackup.

Explanation: The absolute option specified does nothave any effect when performing a snapshotdifferential backup.


User response: Try to use the CreateNewBase=yesoption when performing a snapshot differential backup.

FMV7552I timestamp ***** Processed count files*****

Explanation: IBM Tivoli Storage Manager hasprocessed the specified number of files.



FMV7553W Disabled demand migration (ENOSPC)on file system file-system-name because ofhigh threshold, low threshold, andpmpercentage settings.

Explanation: The settings of high threshold = 100, lowthreshold = 100, and pmpercentage = 0 are reserved todisable demand migration and automigration. Used forGPFS driven migration.



FMV7554E provider option is required ifHSMBACKENDMODE is set toTSMFREE.

Explanation: You need to specify provider option forevery operation with dsmmigrate.


User response: Specify the provider option value forthe operation.



FMV7557E invalid provider.

Explanation: You need to specify a valid provider forevery operation with dsmmigrate.


User response: Specify a valid provider option valuefor the operation.

FMV7558E target option is required ifHSMBACKENDMODE is set toTSMFREE.

Explanation: You need to specify target option forevery operation with dsmmigrate.


User response: Specify the target option value for theoperation.

FMV7559E The absolute option requires specifyingthe NoJournal option when performinga Journal Based Backup for backing upfs .

Explanation: The absolute option specified does nothave any effect when performing journal basedbackups.

System action: Incremental backup is performed.

User response: Verify that the file spaces specified arenot associated with journal based backup. If the-nojournal option is also specified, then this messagewill not appear.

FMV7566E Unable to load external library: reason

Explanation: There is no valid library in hsm/bindirectory.


User response: Copy a valid external library tohsm/bin directory.

FMV7567E program-name:External recall failed!Reason:

Explanation: There is no valid library in hsm/bindirectory.


User response: Copy a valid external library tohsm/bin directory.

FMV7641I The user does not have administrativecredentials to perform a full systemstate backup.

Explanation: The user account used to perform systemstate backup including ASR Writer data must be a

member of the Administrators group.

System action: System state backup skips ASR Writerdata.

User response: Log on with a user who is a memberof the Administrators group or add this user to theAdministrators group. Then try the system statebackup again.

FMV7642E An error occurred creating the registrydirectory structure.

Explanation: An error occurred while creating thedirectory structure to save or replace a registry key.

System action: Registry function fails.

User response: Ensure that the user account that isrunning the backup of the registry has the properauthority. If the user account has the proper authority,you might need to restart the machine. There might beoperations that are pending which have a file or files inthe registry directory structure locked.

FMV7650E The user does not have sufficientprivileges to execute IBM Tivoli StorageManager.

Explanation: The user account used to execute IBMTivoli Storage Manager must have the "Back up filesand directories" and the "Restore files and directories"security settings assigned.


User response: Assign the "Back up files anddirectories" and the "Restore files and directories"security settings to the account using the WindowsLocal Security Settings tool or use a different user-id toexecute IBM Tivoli Storage Manager.

FMV7660E An error occurred replacing one or moreregistry keys.

Explanation: The registry key or keys being replacedare exclusively held by another process. The registrykeys were previously restored but the system was notrestarted.


User response: Restart the system and try the restoreoperation again.

FMV7709E Restore operation failed. Not all fileswere restored.

Explanation: Restore operation failed due to an error.

System action: Operation completed.

User response: Check the error log for more details.



FMV7899E The client referenced a deduplicatedextent that does not exist on the TivoliStorage Manager server

Explanation: The deduplicated extent has beendeleted from the server during the backup or archiveoperation. If you are using deduplication cache, itmight be out of synch with the Tivoli Storage Managerserver.


User response: Retry the operation. If the problempersists, turn off deduplication and retry the operation.

FMV7900W Deduplication cache has been resetbecause it is not synchronized with theTivoli Storage Manager server

Explanation: The deduplication cache containsdeduplicated extent entries that do not exist on theTivoli Storage Manager server. This occurs when theextents are deleted from the Tivoli Storage Managerserver after they were recorded in the deduplicationcache.

System action: The deduplication cache is reset, andall cache entries are removed. The processing continues.

User response: None

FMV7901W Client deduplication and option-name aremutually exclusive.

Explanation: The following features cannot be usedwith deduplication: lan-free, subfile, NAS,useTsmBuffers.

System action: Client deduplication is disabled.

User response: Review the configuration. Do notconfigure deduplication with the lan-free, subfile, NAS,or useTsmBuffers features.

FMV7902I Client deduplication cache is full. Cacheis reset.

Explanation: The number of entries cached in theclient deduplication cache has exceeded the configuredsize for the cache.

System action: The deduplication feature is designedso that this happens periodically. The cache is reset tono entries.

User response: You can reconfigure the clientdeduplication cache size to a larger value to reduce thefrequency of resets.

FMV7903W Client deduplication cache is locked byanother process.

Explanation: Another process is using the clientdeduplication cache. Only one process may use it at atime.

System action: This process does not use the clientdeduplication cache. The server deduplication is notchanged.

User response: You can serialize processes using theclient deduplication cache. Or you can reconfigure thecurrent process to use a different cache path to avoidcontention.

FMV7904E Client deduplication and lan-free orsubfile backup are mutually exclusive.

Explanation: Client deduplication and lan-free orsubfile are mutually exclusive.

System action: Client deduplication is disabled.

User response: Review the configuration. Do notconfigure deduplication with the lan-free or subfilefeature.

FMV7906W The current storage pool either ran outof space or the current object exceededthe maxsize configuration parameter forthe storage pool, data will be stored intothe next pool - deduplication isdisabled.

Explanation: The current storage pool on the TivoliStorage Manager server is either out of space or thecurrent object exceeded the maxsize configurationparameter for the storage pool . Data will be stored inthe next storage pool. Deduplication is disabled and thetransaction is being resent.

System action: Deduplication is disabled to allow thebackup to complete.

User response: Contact your system administrator toadd volumes to the current storage pool.

FMV7907W Connection to repository repos-namefailed. Retrying with repos2-name.

Explanation: Unable to connect to the Fastback DRHub repository. Retry using Fastback server repository.

System action: Retry operation.

User response: Specify a vaild repository.

FMV7908E Unable to mount FastBack snapshotpolicy 'Policy' client 'Client' volume'Volume'. Reason: reason

Explanation: Tivoli Storage Manager Mount failed.



System action: Tivoli Storage Manager cannotcontinue processing.

User response: Check the Recovery Agent logs forinformation about why the mount operation failed tocomplete.

FMV7912E FastBackMount or FastBackShell is notinstalled.

Explanation: Failure initializing FastBack environment.FastBackShell or FastBackMount are not installed or arenot located in the FastBack install directory.

System action: The FastBack operation cannotcontinue.

User response: Reinstall the software. TheFastBackShell and FastBackMount must be installed onthe dedicated proxy computer.

FMV7913E The given branch was not found in theDR Hub repository.

Explanation: The parameter to the required fbbranchoption is incorrect.

System action: The operation cannot continue.

User response: Correct the parameter given for thefbbranch option.

FMV7914E Incremental backup of FastBack client'vmname' failed with RC rc

Explanation: The archive or incremental backup ofFastBack client volumes failed.

System action: The archive or backup of FastBackclient finished with failures. The next FastBack clientwill be processed. The reason for the failure is writtento the local client error log.


FMV7915E Failure mounting FastBack client'vmname' with FastBack command. RC=rc

Explanation: The FastBackMount command failed tomount a FastBack volume.

System action: The archive or backup of the FastBackvolume can not continue. The next Volume in in linewill be processed. The output of the FastBackMountcommand will show the reason for the failure.

User response: Check the local client error log for thereason for the failure. Issue a FastBack command forthe FastBack volume to determine the reason for thefailure. Refer to the documentation for that message formore information.

FMV7916E Failure initializing FastBackenvironment.RC=rc

Explanation: Failure initializing FastBack environment.Can not find FastBackShell.exe command. TheFastBackShell or FastBackMount is not installed orFastBackShell.exe command is not located in theFastBack install directory.

System action: The backup can not continue. Theoutput of the FastBack command will show the reasonfor the failure.

User response: Issue a FastBack command todetermine the reason for the failure. Refer to thedocumentation for that message for more information.The FastBackShell and FastBackMount must beinstalled on the backup proxy computer.

FMV7917E No FastBack snapshots found for inputpolicy, client and volume combination.

Explanation: Failure processing fbClientName option.

System action: The backup cannot continue.

User response: Check for errors in the FBClientNameoption value. Refer to the documentation for theFBClientName option for more information.

FMV7918E Failure locating mounted volumes forFastBack client 'vmname' volumes. Failedwith RC=rc

Explanation: FastBack client volumes can not befound. Volume mount points are not available on thebackup proxy computer.

System action: The backup of the FastBack client cannot continue. The next FastBack client in the list will beprocessed. The output of the FastBackMount commandwill show the reason for the failure.

User response: Issue a fastbackshell mount addcommand for the FastBack client volume to determinethe reason for the failure. Refer to the documentationfor that message for more information.

FMV7919E Password for Host host could not beread from encrypted password file.

Explanation: Use dsmc SET PASSWORD-type=FastBack 'FastBack hostname' 'userid' 'password'to save encrypted password

System action: The backup cannot continue.

User response: Use dsmc SET PASSWORD-type=FastBack 'FastBack hostname' 'userid' 'password'to save encrypted password



FMV7936E objType objName not found in dump.

Explanation: Tivoli Storage Manager server could notfind the object that is specified in the FastBack Dumpcommand..

System action: Tivoli Storage Manager skips thecurrent object.

User response: Ensure that there is at least onesnapshot for this FastBack volume, client, and policy.Ensure that a correct object is specified as input.

FMV7937E No objType found in dump for inputobjType1 objType2.

Explanation: Tivoli Storage Manager server found noclients for the specified policy. Tivoli Storage Managerserver found no volumes for the specified FastBackclient.

System action: Tivoli Storage Manager skips thecurrent object.

User response: Ensure that there is at least onesnapshot for this FastBack volume, client, and policy.Ensure that a correct object is specified as input.

FMV7938E Unable to dismount FastBack volume'volName'. RC = rc

Explanation: Tivoli Storage Manager Dismount failed.

System action:

User response:

FMV7939E Invalid FastBack volume specification.

Explanation: You must enter at least one FastBackclient with the "-fbclientname=" option before enteringa FastBack volume name.

System action:

User response: When entering a FastBack volumename, enter at least one FastBack client name using the"-fbclientname=" option.

FMV7940W SUBDIR NO is not valid in this context.SUBDIR will be forced to YES forFastBack commands.

Explanation: When using FastBack, SUBDIR is forcedto YES to ensure that the whole volume is processed.

System action: SUBDIR is forced to YES.

User response: To avoid this message, do not useSUBDIR NO with the command.

FMV7941E FastBack invalid repository name ordomain not set in password file entryfor hostname.

Explanation: Tivoli Storage Manager The FastBackrepository name is invalid or the domain has not beenset in the password file when specifying the REP formof the repository.

System action: Tivoli Storage Manager

User response: Issue the command dsmc set passwordserver userid:domain password -type=fastback.

FMV7942E Maximum number of FastBack objNameobjects exceeded.

Explanation: Tivoli Storage Manager The maximumnumber of FastBack objects shown in the message hasbeen exceeded.


User response: Re-run the command with no morethan the maximum number of objects specified.

FMV7943E The combination of objName andobjName is invalid.

Explanation: Tivoli Storage Manager The combinationof options specified is invalid.


User response: Re-run the command with acompatible set of options.

FMV7944W The number of FastBack clientsspecified client is greater than thenumber of FastBack clients found client.

Explanation: Tivoli Storage Manager One or more ofthe FastBack clients specified was not found. Look formessage FMV7936E specifying the client name.


User response: Correct the names of the clientsspecified.

FMV7945W The number of FastBack policiesspecified policy is greater than thenumber of FastBack policies foundpolicy.

Explanation: Tivoli Storage Manager One or more ofthe FastBack policies specified was not found. Look formessage FMV7936E specifying the policy name.


User response: Correct the names of the policiesspecified.



FMV7946E FastBack shell command timeout.SSHKeys may not be configured for nopassword.

Explanation: Tivoli Storage Manager The FastBackshell command timeout. SSH may not be configuredproperly.


User response: Correct SSH configuration.

FMV7947E The root user .ssh directory was notfound. SSH is not configured properly.

Explanation: Tivoli Storage Manager SSH is notconfigured properly for the root user.



FMV7948E The public key for the FastBack serverwas not found. SSH public keys areconfigured properly.

Explanation: Tivoli Storage Manager The SSH publickeys are not configured properly for the root user.



FMV7949E The connection to FastBack serverfailed.

Explanation: Tivoli Storage Manager The connectionto FastBack server failed.


User response: Insure that the FastBack server on thetarget machine is runing properly.

FMV7950E The FastBack server is not installed onthe target machine.

Explanation: Tivoli Storage Manager The FastBackserver is not installed on the target machine.


User response: Install the FastBack server on thetarget machine or specify a different target machiner.

FMV7951E The FastBackShell on the target machinereturned with the message errormsg .

Explanation: Tivoli Storage Manager An erroroccurred with the command issued to the FastBackShellon the target machine.


User response: Correct the options specified on thecommandr.

FMV7952E The package package required forFastBack support is not installed.

Explanation: Tivoli Storage Manager The requiredpackage is not installed.


User response: Install and configure the requiredpackage.

FMV7953E The FastBack shell scripts returned anunexpected error error.

Explanation: Tivoli Storage Manager The FastBackshell scripts returned an unexpected error.


User response: Correct the error.

FMV7954E The SSH connection failed. The SSHdaemon may not be started orconfigured on the target machine

Explanation: Tivoli Storage Manager Ensure that theSSH daemon is configured correctly.



FMV7955E The cygdrive-prefix is set incorrectly.

Explanation: Tivoli Storage Manager Ensure thatcygdrive-prefix is set to / in the ssh cygwinenvironment. The command mount -s--change-cygdrive-prefix / can be use to set the driveprefix correctly.



FMV7956E Unable to execute cygwin shellcommands. The cygwin environmentmay be incorrectly

Explanation: Tivoli Storage Manager Use ssh toconnect to the cygwin shell and ensure that the cygwinenvironment and cygdrive are configured correctly.



FMV7957E Unable discover the FastBackShelllocation in the registry

Explanation: Tivoli Storage Manager Check that theFastBackShell was installed on the Windows FastBackserver machine.





FMV8000I Server command: 'command'.

Explanation: The specified command is being sent tothe server. This message is displayed when thecommand is generated from a macro or when the clientis running in batch mode.

System action: The command is sent to the server forprocessing.


FMV8001I Return code return code value.

Explanation: The error code shown has been returnedfrom the preceding server command. This message ispreceded by a server message explaining the reason forthe error code.



FMV8002I Highest return code was return codevalue.

Explanation: At exit from the client, the highest returncode encountered during the session is displayed.

System action: This value is used as the program exitcode.


FMV8003I Process number process ID started.

Explanation: As a result of the preceding servercommand, the process whose ID is shown starts toexecute the command. The process can be monitoredusing the QUERY PROCESS command.



FMV8004W Your password will expire withindaysRemaining day(s).

Explanation: The password for this id is about toexpire.

System action: Logging on to the TSM Server will notbe prevented, however, the id will be locked out once itexpires.

User response: Change the password or contact yourTivoli Storage Manager administrator to get thepassword updated.

FMV8005E Java Applet failed to load. Please ensurethat the Java Java version Plugin has beeninstalled for this browser.

Explanation: Java Plugin is missing from browser.Since plugin is not present, applet is not able to load.

System action: Applet unable to load and messagedisplayed.

User response: Install appropriate plugin for browserin order to use web client.

FMV8006E Unable to generate an acceptablepassword.

Explanation: An error occurred during a passwordupdate attempt using a generated password.


User response: Contact your Tivoli Storage Manageradministrator.

FMV8007E The user is not authorized to performLDAP authentication.

Explanation: Your node uses LDAP authentication.Your PASSWORDACCESS option is set to GENERATEbut the current user cannot access the stored passwordto perform authentication.

System action: The operation is stopped.

User response: Run Tivoli Storage Manager client asroot user or set PASSWORDACCESS to PROMPT.

FMV8008W Redirection inside macro whose outputis redirected is ignored.

Explanation: An output redirection symbol has beenencountered inside a macro. However, the output of themacro itself (or a higher level macro) is already beingredirected.

System action: The redirection request is ignored.


FMV8010E An attempt to backup or archive a filehas exceed the maximum number ofretries.

Explanation: After five unsuccessful attempts tobackup or archive a file, the client will no longerattempt to send the file to the server.


User response: Check the console or schedule log foradditional information. Retry the operation at a latertime.

FMV8011W Rejected server-initiated session withLDAP authentication from peer name.

Explanation: For security, the client will not acceptserver-initiated sessions from servers that use LDAPauthentication.

System action: The client-server session is not opened,



and the schedule is not executed. The schedulercontinues to wait for contact by a server that usesLOCAL authentication.

User response: If the client system is supposed toaccept scheduled events from the prompting TivoliStorage Manager server, either ask the Tivoli StorageManager server administrator to configure your nodeto use LOCAL authentication, or do not useserver-initiated sessions. If the client system is notsupposed to accept scheduled events from theprompting server, ask the Tivoli Storage Managerserver administrator to remove the client node namefrom the schedule on the prompting server.

FMV8012E Option processing storage exhausted.

Explanation: During processing of the client optionsfile, the client runs out of memory.

System action: The client session is ended.

User response: Make more memory available andrestart the administrative client.

FMV8013I Invalid encryption key password

Explanation: The key you entered does not match thekey that was used to encrypt the file during backup.The file can not be restored unless the matching key isentered.

System action: User is prompted for encryption keypassword.


FMV8014E Insufficient information to connect tohost.

Explanation: The client options file or command line,or both, do not contain enough communicationsinformation to successfully connect to the serversystem. For example, with TCP/IP both the TCPPortnumber and TCPServer address are required to make aconnection.

System action: The administrative client session isended.

User response: Determine what information is neededto establish a connection for your communicationsmethod and then specify all that information in yourclient options file or on the administrative clientcommand line.

FMV8015E File 'file spec', error code error code fromoptions processing.

Explanation: An unknown error code is returned fromthe routine that processes the client options file.


User response: Attempt to determine the error andcorrect it. If the problem persists, contact your servicerepresentative.

FMV8016E Command line parameter parameternumber: 'parameter' is too long.

Explanation: The specified command line parameterexceeds the maximum length for a command lineparameter.


User response: Reissue the command with a shorterparameter.

FMV8017E Command line parameter parameternumber: 'parameter' is not valid.

Explanation: The command line parameter shown isnot a valid administrative client parameter.


User response: Reissue the command with validparameters.

FMV8018E Administrative command not valid inConsole mode.

Explanation: The Console Mode option has beenspecified but the client encounters what appears to be aserver command on the command line.


User response: Reissue the command with no servercommand.

FMV8019E Id and password must be supplied inBatch mode.

Explanation: A server command has been encounteredon the command line, but no administrator ID orpassword, or both, are specified.


User response: Reissue the command and include the-ID and -PASSWORD parameters on the command line.

FMV8020E Unable to open file 'file spec' for output.

Explanation: The file name specified in the -OUTFILEoption cannot be opened.

System action: The -OUTFILE parameter is ignored.

User response: Allow processing to continue or exit



the session and correct the file name.

FMV8021E Exiting Batch mode session due tooutput file error.

Explanation: The file specified in the -OUTFILEparameter cannot be opened for a session running inBatch mode.


User response: Reissue the command with a validoutput file name or make space available for the outputfile.

FMV8022E Output will be written only to stdout.

Explanation: The file specified in the -OUTFILEparameter cannot be opened, so output is written onlyto the standard output stream.

System action: Output that would have been writtento the output file is written to the standard outputstream.

User response: Allow processing to continue or exitthe session and correct the file name.

FMV8023E Unable to establish session with server.

Explanation: The administrative client cannot start asession with the requested server. This message ispreceded by another message that explains the reasonfor the error.


User response: Attempt to correct the error. If theproblem persists, contact your service representative.

FMV8024E End of macro after continued commandline.

Explanation: A macro containing a continuation linehas been executed, but no more lines are found in themacro file.

System action: The continued command is ignored,and an error return code is set for the macro.

User response: Correct the macro in error.

FMV8025E I/O Error reading command input.

Explanation: The client is unable to read an inputcommand from the terminal.


User response: Correct the problem on the terminaland retry the administrative session.

FMV8026E Input line longer than maximum of maxlength characters. Use continuation.

Explanation: An input command line is longer thanthe maximum input line length allowed.

System action: The input command is ignored.

User response: Reissue the command with severallines using continuation characters.

FMV8027E Unterminated comment in command.

Explanation: An input command contains an openingcomment mark but no closing comment mark.


User response: Reissue the command with matchingcomment marks.

FMV8028E Command longer than maximum of maxlength characters.

Explanation: An input command longer than themaximum command length allowed has been entered.


User response: Reissue the command with fewercharacters. This could mean replacing series ofrepeating blanks with a single blank.

FMV8029E Macro processing terminated.

Explanation: An error occurs during processing of amacro because the -ITEMCOMMIT option is notspecified on the command line. Processing of thismacro and any higher level macro is terminated.

System action: All current macro processing ends.

User response: Specify the -ITEMCOMMIT option onthe command line to ensure that the server commitseach command in the macro individually.

FMV8030E Substituted command longer thanmaximum of max length characters.

Explanation: After variable substitution, an inputcommand is longer than the maximum commandlength allowed.


User response: Reissue the command with fewercharacters. This may require replacing a series ofrepeating blanks with a single blank.

FMV8031E Missing name of macro to execute.

Explanation: A macro command is encountered thatdoes not contain a macro name.

System action: The command is ignored.



User response: Reissue the macro command with amacro file name.

FMV8032E Could not allocate storage to processmacro 'file spec'.

Explanation: The client cannot allocate enoughmemory to process the macro shown.


User response: Make more memory available to theclient and retry the macro command.

FMV8033E LDAP authentication is not supportedby Web client.

Explanation: The id you entered uses LDAPauthentication. LDAP authentication is not supportedby Web client.

System action: Login is unsuccessful.

User response: Use an id with LOCAL authentication.

FMV8034E Your administrator ID is not recognizedby this server.

Explanation: The administrator ID entered is notknown to the requested server.

System action: The administrative session terminates.

User response: Ensure that you are using a registeredadministrative ID for the server to which you areconnecting.

FMV8036E Administrative command not valid inMount mode.

Explanation: The Mount Mode option has beenspecified but the client encounters what appears to be aserver command on the command line.


User response: Reissue the command with no servercommand.

FMV8037E Missing name for redirection file.

Explanation: A command is entered that contains anoutput redirection symbol but no output file name.

System action: The command is ignored and an erroris returned.

User response: Reissue the command with an outputfile name.

FMV8038E Unable to open file 'file spec' forredirection.

Explanation: A command has been entered thatspecifies an output redirection file, but the file cannotbe opened.

System action: The command is ignored and an erroris returned.

User response: Reissue the command with a validoutput file name or make space available for the outputfile.

FMV8041E The server connection has been lost andcannot be re-established.

Explanation: During an administrative session, theclient discovers that the connection with the server hasbeen severed; an attempt to reestablish the connectionfails.


User response: Determine the cause of the failure;then try to restart the session at a later time. If theproblem persists, contact your service representative.

FMV8045E Communications error.

Explanation: An unexpected communications erroroccurs during an administrative session.


User response: Verify that communications are activebetween the client and server machines. Server outages,processor outages, and communication controlleroutages can cause this error.

FMV8046E The client connection with the serverhas ended due to an unexpected error.

Explanation: The Tivoli Storage Manager error logmight contain other messages related to this error.

System action: The client session ends.

User response: Check the communication linkbetween the client and server to ensure that it isoperational. Examine the client error log for additionalmessages related to this error.

FMV8047E The client connection with the serverhas ended due to a communicationsbuffer overflow.



User response: Try the operation again. Check thecommunication link between the client and server toensure that it is operational. Examine the client error



log for additional messages related to this error.

FMV8048W Warning! Performing image restore ofthe Linux file system 'src' to an alternatedestination 'dest' is not recommended asthis may result in duplicate UUIDsleading to failed mounts after asuccessful restore.

Explanation: Performing an image restore of a Linuxfile system to an alternate destination may result induplicate UUID leading to failed mounts after asuccessful restore. On Linux, some file systems useUUID to identify themselves. If you took an imagebackup of such volume and restored it to a differentlocation, you will have two volumes with the sameUUID. If you use UUID to define your file systems in/etc/fstab, be aware that TSM may be unable to mountthe restored file system correctly. To avoid suchsituation, restore the image to its original location.


User response: If it is not possible or not desirable toavoid performing an image restore to an alternatedestination, change the UUID of either the original orrestored volume. Refer to your Linux documentationfor instructions on how to do this. You may also needto edit your /etc/fstab manually to allow the original,the restored or both volumes to mount.

FMV8049E A connection with the server cannot beestablished due to a communicationstime-out.



User response: Check the communication linkbetween the client and server to ensure that it isoperational. Examine the client error log for additionalmessages related to this error.

FMV8050E The Tivoli Storage Manager server isnot accepting administrative sessions onthe client port. You must use the portnumber designated for administrativesessions.

Explanation: The Tivoli Storage Manager server isconfigured to not allow administrative sessions on theclient TCP/IP port. A different port number has beendesignated for use by administrative sessions.

System action: The administrative session is notestablished.

User response: Use the TCPADMINPORT clientoption to specify the TCP/IP port number that theTivoli Storage Manager server uses for administrativesessions. See your Tivoli Storage Manager server

administrator if you do not know the correct portnumber.

FMV8052E Unable to decrypt file 'filespacenamepath-namefile-name' ....Please try torestore this file individually

Explanation: File could not be decrypted and restored.

System action: File is not restored.

User response: Restore the file separately.

FMV8053E The network cannot be accessed.



User response: Check the communication linkbetween the client and server to ensure it isoperational. Examine the client error log for additionalmessages related to this error. Try the operation again.

FMV8054E No memory available to service request.

Explanation: Sufficient server memory is not available.


User response: Retry the administrative session. If theproblem persists, contact your service representative.

FMV8055E The server has insufficient resources toperform the operation.

Explanation: The server ran out of resources. A lack ofstorage or other problem condition does not allow anynew activity. The server activity log might containadditional information about this problem.


User response: The Tivoli Storage Manageradministrator should examine the Tivoli StorageManager server activity log to determine the source ofthe resource constraints. Try the operation again whenthe server is under less load.

FMV8056E Your administrator ID is locked.

Explanation: The administrative ID entered has beenlocked by a system administrator and cannot be used.


User response: Contact your system administrator tounlock your ID.



FMV8057E The requested language files are notavailable.

Explanation: The NLS repository for the languagespecified is not available.


User response: Use a different language or obtain acopy of the NLS repository for the language desired.

FMV8058E The specified path is a Linux Btrfssubvolume and is not valid for imagebackup.

Explanation: Linux Btrfs subvolumes are notsupported for image backup.

System action: The image backup operation is notperformed.

User response: Try the operation again using a validLinux Btrfs file system.

FMV8059E The TCP/IP functions have not beenlinked into this module.

Explanation: The ADSM TSO administrative clientcannot find the TCP/IP functions required to supportTCP/IP communications.

System action: The connection to the server fails.

User response: The TCP/IP functions must beincluded in the DSMADMC/FMVADM module. Referto the Program Directory for this product forinstructions on how to include the TCP/IP functions inthe DSMADMC/FMVADM module.

FMV8060E Error validating file 'VHDX file name'

Explanation: Tivoli Storage Manager cannot locate thefile or the file format is not valid.

System action: The backup operation does not start.

User response: Try the operation again. If the problemcontinues, check the error log file for information abouthow to resolve this issue.

FMV8061E Session Rejected: The server does notallow a signon as a Unicode enabledadministrative client

Explanation: The administrative client is unable toestablish a connection to the server because of aunicode enabling mismatch between server and client.


User response: Register a new administrator from adifferent administrative client or the server console, andsignon with the new administrator ID.

FMV8062E Client-to-Client communication is notallowed to take place when TivoliStorage Manager Server authenticationis turned off.

Explanation: Client-to-Client communication requiresTivoli Storage Manager Authentication to be enabled.


User response: Turn Tivoli Storage Manager Serverauthentication on using the Set AUthentication ONcommand.

FMV8063E The remote Tivoli Storage ManagerClient Acceptor associated with Node'name' could not authenticate with theTivoli Storage Manager Server.

Explanation: Some Tivoli Storage Manager Clientoperations require the Backup/Archive Client tocontact Clients on remote machines. The remotemachine in question cannot authenticate with the TivoliStorage Manager Server.


User response: On the remote machine, create a newTivoli Storage Manager password for the ClientAcceptor or verify that the current password is stillvalid before retrying the operation.

FMV8064E Communication timeout. Reissue thecommand.

Explanation: The connection to the server is endedbecause of a communication timeout from the server.

System action: The server does not process thecommand.

User response: Reissue the command. If necessary,increase the values of IDLETIMEOUT andCOMMTIMEOUT options in the server options file.

FMV8103W A command was not successful.command : command Tivoli StorageManager function name : function-nameerror output : error-output return code :return code Tivoli Storage Manager file :file-name (line-number)

Explanation: Tivoli Storage Manager client called anexternal program that failed.

System action: Depending on the circumstances, thefailure may or may not prevent further processing.

User response: See addition information in the errorlog. Use the information provided in this message fortroubleshooting or when talking with Tivoli StorageManager support.



FMV8104W Cannot determine EFS status of the filesystem 'file-system name', errno='errnornumber', processing data normally.

Explanation: IBM Tivoli Storage Manager cannotdetermine EFS status on the specified filesystem. NoEFS specific processing will take place for files on thisfilesystem. If EFS is indeed enabled on the filesystem,all accessaible files will be backedup in cleartext.

System action: The filesystem will be processed as aregular filesystem.

User response: Contact your system administrator todetermine the cause of the error reported in themessage.

FMV8105W Unable to remove snapshot for volume'filespace-name'.

Explanation: Tivoli Storage Manager client was unableto remove the snapshot used for image backup.


User response: See additional information in the errorlog. Use lvdisplay command to view the activesnapshots and lvremove command to remove thesnapshot manually.

FMV8106E Support for multiple IBM Tivoli StorageManager servers is enabled on thisnode. The server name must bespecified for this command.

Explanation: When a node is enabled to supportmultiple IBM Tivoli Storage Manager servers, thecommand must specify a valid IBM Tivoli StorageManager server name.


User response: Specify a valid server name for thiscommand.

FMV8201E Windows Hyper-V incremental backupsrequire Windows 2012 or later.

Explanation: Tivoli Storage Manager can only performincremental backups of Windows Hyper-V on Windowsoperating systems of Windows Server 2012 and later.Incremental backups may not be performed onprevious versions of Windows.

System action: The incremental backup will not occur.

User response: To access incremental backups forWindows Hyper-V upgrade the operating system toWindows Server 2012 or later. Alternatively, PeriodicFull - Full backups are available for previous versionsof Windows.

FMV8503I No matching option found for pattern:'pattern'.

Explanation: You specified a pattern which does notmatch the name of any supported option.

System action: This message is the only response toyour query.

User response: Specify a different pattern or omit thepattern to display all options.

FMV8563E Recall mode has an invalid value:invalidValue.

Explanation: The recall mode you try to enable on thesystem is not existing.


User response: Check the value of the recall option.

FMV8565W ProgramName: list of recall IDs not foundin queue. These recalls are alreadyfinished:

Explanation: The program is not able to find the recallIDs and is not able to delete these processes.


User response: Check that recall IDs exist and arecorrect.

FMV8776E The IBM Tivoli Enterprise SpaceManagement Console cannot be started.Java Runtime Environment versionversion by company has been detected onmachine. A Java Runtime Environmentversion or higher is required to run thisprogram. If you have already installedJava version on this machine, pleaseensure that the correct Java executable ison your PATH, otherwise you candownload it from 'webAddress' and startthe program again.

Explanation: IBM Tivoli Enterprise Space ManagementConsole cannot be started because the Java runtimeenvironment does not meet the requirements.

System action: A confirmation dialog is displayed foryou to close the application, or to open a browser witha link to the Web site where you can download thecorrect version of Java.

User response: Verify that the correct java executableis on your PATH or install the required version of Javaruntime environment and start the program again.



FMV8777E The IBM Tivoli Enterprise SpaceManagement Console cannot be started.An error occurred trying to load Tivolilook and feel. Verify that the product iscorrectly installed.

Explanation: IBM Tivoli Enterprise Space ManagementConsole cannot be started because the library thatdefines the Tivoli look and feel cannot be found.

System action: The IBM Tivoli Enterprise SpaceManagement Console shuts down.

User response: Verify that the product is correctlyinstalled. If IBM Tivoli Enterprise Space ManagementConsole still cannot be started, contact your systemadministrator for further assistance.

FMV8778E A browser program cannot be found orcannot be started. An error occurredexecuting the command. command Verifythat a browser is installed and workscorrectly on your local machine.

Explanation: A browser program cannot be found, soit is not possible to access the IBM Tivoli Web site andonline documentation.

System action: Tivoli Storage Manager continues toprocess user requests.

User response: For the Windows platform, the defaultsystem browser is used. Verify that a browser isinstalled on your machine.

FMV8779E A browser program cannot be found orcannot be started. One of the followingbrowsers is required: browser-list Verifythat one of these browsers is installedand works correctly on your localmachine.

Explanation: A browser program cannot be found, soit is not possible to access the IBM Tivoli Web site andonline documentation.


User response: For UNIX platforms, a list ofsupported browsers is provided in the README.Install the required browser to access the IBM TivoliWeb sites and online documentation.

FMV8780E A browser program cannot be found orcannot be started. Check the 'file-name'file on your local machine for moreinformation.

Explanation: A browser program cannot be found, soit is not possible to access the Web site or onlinedocumentation.


User response: Install a browser to access the Web siteor online documentation.

FMV8781E The system could not log on to TivoliStorage Manager client node node-nameon machine-name. Make sure your dataand password are correct and that capslock key is not on. The SpaceManagement Agent must be running atthe specified port on the machine towhich you are attempting to log on to.

Explanation: The system was not able to connect tothe specified client node.


User response: Verify that:

v the information provided to connect is correct

v the machine is reachable in the network

v HSM is installed on the specified machine and aSpace Management Agent is running at the specifiedport.

FMV8782E An error occurred while loading filesystem information on 'fs-name'. Verifythat the Space Management agent isrunning on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachine and the $DSM_DIR/error-filefile on machine if present. If this doesnot identify the cause of the problem,contact your system administratorand/or Tivoli Storage Manager technicalsupport for further assistance.

Explanation: An error occurred while loading filesystem information on the selected client node

System action: Disconnects the client node.

User response: Verify that the Space Managementagent is running on the client node machine. Checkalso the dsmsm.log file in the installation directory ofyour local machine and the $DSM_DIR/dsmerror.logfile on the client node machine if present. If this doesnot identify the cause of the problem, contact yoursystem administrator and/or Tivoli Storage Managertechnical support for further assistance.



FMV8783E An error occurred loading file systemproperties of fsName required to showspace usage graphical information.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachine and the $DSM_DIR/error-filefile on machine if present. If this doesnot identify the cause of the problem,contact your system administratorand/or Tivoli Storage Manager technicalsupport for further assistance.

Explanation: An error occurred while loading filesystem properties on the selected client node.

System action: Continue to process other file systemproperties.

User response: Verify that the Space Managementagent is running on the client node machine. Checkalso the dsmsm.log file in the installation directory ofyour local machine and the $DSM_DIR/dsmerror.logfile on the client node machine. If this does not identifythe cause of the problem, then see your systemadministrator for further assistance.

FMV8784E An error occurred initializing the clientnodes table. Your local configuration file'config-file' might be corrupted. Removeit from your installation directory andstart the program again. Check also thelog-file file on your local machine formore information.

Explanation: The client nodes table cannot beinitialized.

System action: The IBM Tivoli Enterprise SpaceManagement Console shuts down.

User response: It is possible that your local settingsfile 'dsmsm.cfg' is corrupted. Try to remove it fromyour installation directory and start the program again.Check the dsmsm.log file in the installation directory ofyour local machine and the $DSM_DIR/dsmerror.logfile on the client node machine if present. If this doesnot identify the cause of the problem, contact yoursystem administrator and/or Tivoli Storage Managertechnical support for further assistance.

FMV8785E An error occurred disconnecting thesystem from the client node 'node-name'.The Client node is being disconnectedwithout deleting internal HsmSystemobjects. Verify that the SpaceManagement agent is running on theclient node machine. Check also thelocal-log-file file in the installationdirectory of your local machine and the$DSM_DIR/error-file file on machine ifpresent. If this does not identify thecause of the problem, contact yoursystem administrator and/or TivoliStorage Manager technical support forfurther assistance.

Explanation: An error occurred disconnecting thesystem from the client node. It was not possible todelete internal HsmSystem objects.

System action: The client node disconnected withoutdeleting HsmSystem objects.

User response: Verify that the Space Managementagent is running on the client node machine. Check thedsmsm.log file in the installation directory of your localmachine and the $DSM_DIR/dsmerror.log file on theclient node machine if present. If this does not identifythe cause of the problem, contact your systemadministrator and/or Tivoli Storage Manager technicalsupport for further assistance.

FMV8786E An error occurred loading file systeminformation from the selected clientnode. Verify that the Space Managementagent is running on the client nodemachine. Check also the local-log-file filein the installation directory of your localmachine and the $DSM_DIR/error-filefile in the client node machine ifpresent. If this does not identify thecause of the problem, contact yoursystem administrator and/or TivoliStorage Manager technical support forfurther assistance.

Explanation: An error occurred loading file systeminformation from the selected client node.

System action: File System information is not loaded




FMV8787E An error occurred loading file systeminformation from nodename client node.The client node is being disconnected.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachine and the $DSM_DIR/error-filefile on machine if present. If this doesnot identify the cause of the problem,contact your system administratorand/or Tivoli Storage Manager technicalsupport for further assistance.

Explanation: An error occurred loading file systeminformation from the selected client node.

System action: The client node is disconnected


FMV8788E An error occurred starting manuallythreshold migration on file-system. Verifythat the Space Management agent isrunning on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachine and the $DSM_DIR/error-filefile on machine if present. If this doesnot identify the cause of the problem,contact your system administratorand/or Tivoli Storage Manager technicalsupport for further assistance.

Explanation: An error occurred starting the manuallythreshold migration on the selected client node.

System action: Threshold migration is not startedmanually.

User response: Check the dsmsm.log file in theinstallation directory of your local machine and the$DSM_DIR/dsmerror.log file on the client nodemachine if present. If this does not identify the cause ofthe problem, contact your system administrator and/orTivoli Storage Manager technical support for furtherassistance.

FMV8789E An error occurred trying to deactivate allmanaged file systems of client-node.Check also the local-log-file file in theinstallation directory of your localmachine and the $DSM_DIR/error-filefile on machine if present. If this doesnot identify the cause of the problem,contact your system administratorand/or Tivoli Storage Manager technicalsupport for further assistance.

Explanation: An error occurred trying to deactivate allmanaged file systems of the selected client node.

System action: File systems are not deactivated.


FMV8790E An error occurred trying to reactivate allmanaged file systems of client-node.Check also the local-log-file file in theinstallation directory of your localmachine and the $DSM_DIR/error-filefile on machine if present. If this doesnot identify the cause of the problem,contact your system administratorand/or Tivoli Storage Manager technicalsupport for further assistance.

Explanation: An error occurred trying to reactivate allmanaged file systems of the selected client node.

System action: File systems are not reactivated.


FMV8791E An error occurred trying to add spacemanagement to fs-name file system.Verify that the Space Management agentis running on the client node machine.Check also the local-log-file file in theinstallation directory of your localmachine and the $DSM_DIR/error-filefile on machine if present. If this doesnot identify the cause of the problem,contact your system administratorand/or Tivoli Storage Manager technicalsupport for further assistance.

Explanation: An error occurred trying to add spacemanagement to the selected file system.



System action: Space management is not added to theselected file system.


FMV8792E An error occurred trying to removespace management from file-system filesystem. Verify that the SpaceManagement agent is running on theclient node machine. Check also thelocal-log-file file in the installationdirectory of your local machine and the$DSM_DIR/error-file file on machine ifpresent. If this does not identify thecause of the problem, contact yoursystem administrator and/or TivoliStorage Manager technical support forfurther assistance.

Explanation: An error occurred trying to removespace management from the selected file system.

System action: Space management is not removedfrom the selected file system.


FMV8793E An error occurred trying to deactivatefile-system file system. Verify that theSpace Management agent is running onthe client node machine. Check also thelocal-log-file file in the installationdirectory of your local machine and the$DSM_DIR/error-file file on machine ifpresent. If this does not identify thecause of the problem, contact yoursystem administrator and/or TivoliStorage Manager technical support forfurther assistance.

Explanation: An error occurred trying to deactivatethe selected file system.

System action: The selected file system is notdeactivated.

User response: Check the dsmsm.log file in theinstallation directory of your local machine and the$DSM_DIR/dsmerror.log file on the client nodemachine if present. If this does not identify the cause ofthe problem, contact your system administrator and/or

Tivoli Storage Manager technical support for furtherassistance.

FMV8794E An error occurred trying to reactivatefile-system file system. Verify that theSpace Management agent is running onthe client node machine. Check also thelocal-log-file file in the installationdirectory of your local machine and the$DSM_DIR/error-file file on machine ifpresent. If this does not identify thecause of the problem, contact yoursystem administrator and/or TivoliStorage Manager technical support forfurther assistance.

Explanation: An error occurred trying to reactivate theselected file system.

System action: The selected file system is notreactivated.


FMV8795E An error occurred trying to save yoursettings to config-file configuration fileon your local machine. Check the log-filefile in the installation directory of yourlocal machine for more information.

Explanation: An error occurred trying to save yoursettings to dsmsm.cfg configuration file on your localmachine.

System action: Customized GUI settings are not savedto the local machine


FMV8809E The LD_LIBRARY_PATH is either notset or is set incorrectly. Ensure that theLD_LIBRARY_PATH environmentvariable contains the installationdirectory path name.

Explanation: The LD_LIBRARY_PATH must be setand it must contain the installation directory path.

System action: The VMware backup or restoreoperation fails.

User response: Set the LD_LIBRARY_PATH and



ensure that it contains the Backup/Archive clientinstallation directory.

FMV8810E The LD_LIBRARY_PATH is either notset or is set incorrectly. Ensure that theLD_LIBRARY_PATH environmentvariable contains the installationdirectory.

Explanation: The LD_LIBRARY_PATH must be setand it must contain the installation directory path.


User response: Set the LD_LIBRARY_PATH andensure that it contains the Backup/Archive clientinstallation directory.

FMV8811E VMware operations can not be runwhen the hardware plugin productTIVsm-BAhdw is installed and loaded.Please either uninstall the hardwareproduct TIVsm-BAhdw, or set theoption DONTLOAD PIHDW in theoptions file to prevent the hardwareplugin from being loaded.

Explanation: VMware operations are incompatiblewith the hardware plugin product libraries.


User response: Uninstall the hardware productproduct TIVsm-BAhdw, or set the option DONTLOADPIHDW to prevent the hardware plugin from beingloaded.

FMV8818E An error occurred trying to apply yourchanges. Your changes have not beenapplied to the system. Contact yoursystem administrator.

Explanation: An error occurred trying to apply yourchanges.

System action: User changes are not applied.


FMV8819E The following trace flag(s) are not valid:trace-flag-list. Correct them beforecontinuing.

Explanation: One or more of the trace flags are notvalid.

System action: Prompts the user to correct the traceflags.

User response: Correct the wrong trace flags.

FMV8820E The HSM System Object was not foundon the Space Management agent. Theerror occurred when calling function:function-name. The last operation was notprocessed correctly.

Explanation: The Space Management agent wasunable to process a HSM System function, because theHSM System object was not found.

System action: The last operation is skipped.

User response: Reconnect to the Space Managementagent. If this does not solve the problem restart theSpace Management agent.

FMV8821E Unable to create requested HSM objecton Space Management agent. The lastoperation was not processed correctly.The problem is caused from a memoryproblem. Try to free memory on thesystem where the Space Managementagent is running. Or restart the SpaceManagement agent.

Explanation: Space Management agent was not able tocreate a requested HSM object because not enough freespace was found on the system.

System action: Last operation is skipped.

User response: Try to free more memory on thesystem where the Space Management agent is running,or restart the Space Management agent.

FMV8822E HSM File System Object was not foundon Space Management agent. The erroroccurred when calling function:function-name The last operation was notprocessed correctly.

Explanation: Space Management agent was not able toprocess a HSM File System function, because no HSMFile System object was found.


User response: Reconnect to the Space Managementagent. If this does not solve the problem restart theSpace Management agent.

FMV8823E A Protocol error occurred incommunication with the SpaceManagement agent This error occurswhen a session with the SpaceManagement agent was lost, or networkerror caused synchronization problembetween the Space Management consoleand the agent.

Explanation: Space Management console and SpaceManagement agent has different session andtransaction key in the communication header.




User response: Restart Space Management consoleand Space Management agent.

FMV8824E A internal error occurred in the SpaceManagement agent. The error occurredin function : function-name

Explanation: Not defined exception caused a internalerror in the Space Management agent.


User response: Restart Space Management agent. Ifthis does not solve the problem contact Tivoli StorageManager technical support.

FMV8825E The Space Management API was unableto locate option object The erroroccurred in function : function-name

Explanation: Not defined exception caused thisinternal error in the Space Management API.


User response: Contact Tivoli Storage Managertechnical support.

FMV8826E The Space Management API was unableto query a HSM device. This erroroccurs because the HSM kernelextension was not loaded correctly

Explanation: Because of a wrong configuration HSMwas not able the load the kernel extension. This causesto fail the query for global activation of the HSMsystem.

System action: Query for global HSM activation isskipped.

User response: Check the configuration of the HSMsystem. If you can not find any problem in theconfiguration contact Tivoli Storage Manager technicalsupport.

FMV8827E The Space Management API was unableto locate global control block. The erroroccurred in function : function-name

Explanation: Not defined exception caused thisinternal error in the Space Management API.

System action: Load connection settings function isskipped.

User response: Contact Tivoli Storage Managertechnical support.

FMV8828E The Space Management API lost thesession with the server. This problem iscaused by a connection failure with theserver. Check to see if your SpaceManagement Client machine has anetwork connection to the Tivoli StorageManager server.

Explanation: This error occurs when the SpaceManagement API has connection problems with theTivoli Storage Manager server.

System action: Session with server gets lost andserver operation is skipped.

User response: Check the network connection withTivoli Storage Manager server machine. See the errorlog file for additional information why the session getslost. Restart the Space Management Agent if theconnection re-established automatically.

FMV8829E The Space Management API was unableto initialize the HSM system. The erroris caused from a problem to initialize aDMAPI session.

Explanation: This error is caused from a problem toinitialize a DMAPI session.

System action: The HSM system cannot be initializedand the Space Management Console is ended.

User response: Try to restart Space ManagementAgent. If this does not solve the problem, see the errorlog for additional information and contact TivoliStorage Manager technical support.

FMV8830W Different server name stanzas(HSM-stanza and BA-stanza) forfile-system-name file system for spacemanagement and backup-archive.

Explanation: The server name stanzas you specifiedfor the space management (HSM) client and thebackup-archive (BA) client are different. The inlinebackup and stub restore features will be unavailable forthe file system.


User response: If you want to allow inline backup andstub restore for the file system, the MIGRATESERVERand DEFAULTSERVER options must specify the sameSERVERNAME stanza in dsm.sys. You may also chooseto supply a server stanza name using theSERVERNAME option in dsm.opt or on the commandline. In either case the stanza name must match thestanza specified in the MIGRATESERVER option.



FMV8831E The Space Management API could notfind file system : function-name Anincorrect file system name was passed tothe Space Management API. Ensure thatthe file system that was selected in thefile system list is still valid. Refresh thefile system view in the SpaceManagement Console by pressing F5 onyour keyboard or select 'Refresh` underthe View menu.

Explanation: The Space Management API could notfind the file system that was specified in the SpaceManagement Console. A reason could be that the filesystem was unmounted and is not longer existing onthe system.

System action: Getting file system information for thespecified file system name is skipped.

User response: Update the file system list in the SpaceManagement Console by pressing F5 on your keyboardor selecting 'Refresh' in the View menu.

FMV8832E The Space Management API could notretrieve Tivoli Storage Manager policysettings from the server.

Explanation: The Space Management API tried to getTivoli Storage Manager policy settings from the serverand failed for a unknown reason.

System action: Getting Tivoli Storage Manager policysettings fails and policy information fields are not filledup in the Space Management Console.

User response: See the error log file for additionalinformation.

FMV8833E The Space Management API could notretrieve Tivoli Storage Manager policysettings from the already loaded list.

Explanation: The Space Management API tried to getTivoli Storage Manager policy settings from themanagement list and failed for a unknown reason.

System action: Getting Tivoli Storage Manager policysettings fails and policy information fields are not filledup in the Space Management Console.


FMV8834E The Space Management API was unableto get file system information for filesystem : filesystem-name.

Explanation: The Space Management API could notretrieve the file system information for a selected filesystem.

System action: Getting file system information fails

and information are not displayed in the SpaceManagement Console.


FMV8835E The Space Management API was unableto get file system status for file system :filesystem-name. System call to get filesystem status returned with error.

Explanation: The Space Management API could notretrieve the file system status for a selected file system.The error is caused from a failed system call on the filesystem.

System action: Getting file system status fails andinformation are not displayed in the SpaceManagement Console.


FMV8836E An object creation error occurred in theSpace Management API The erroroccurred in function : function-name. Theproblem is caused from a memoryproblem. Try to free memory on thesystem where the Space Managementagent is running. Or restart the SpaceManagement agent.

Explanation: Caused from a out of memory problemthe Space Management API could not create arequested object.

System action: The requested function fails andcannot retrieve information to the Space ManagementConsole.

User response: Free more memory on the systemwhere the Space Management agent is running, orrestart the Space Management agent.

FMV8837E The Space Management API was unableto get configuration data from managedfile system : filesystem-name. Theproblem is caused from a error whenreading dsmmigfs table entry.

Explanation: The Space Management API readsinformation from dsmmigfs table to get HSM managedfiles system configuration. This error occurs when theAPI is unable to read an entry from this table.

System action: Getting HSM managed file systemconfiguration fails and information is not displayed inthe Space Management Console.

User response: See the error log for additionalinformation on errors occurring when reading entriesfrom the dsmmigfs table.



FMV8838E The Space Management API can not setHSM managed file system configurationfor file system : filesystem-name. Theconfiguration cannot be set because thisfile system is NOT HSM managed.Check to see if the managed file systemthat was selected in the file system listis still HSM managed. Refresh the filesystem view in the Space ManagementConsole by pressing F5 on yourkeyboard or select 'Refresh` under theView menu.

Explanation: The file system that you selected fromthe file system list in the Space Management console isnot longer HSM managed and no configuration can betset for it. A reason could be that the file system wasunmanaged from a other user.

System action: Setting HSM managed file systemconfiguration fails.


FMV8839E A wrong stub file size was passed to theSpace Management API for file system :filesystem-name. The stub file size thatwas entered in the file system propertiesdialog is not supported by this filesystem. Correct the stub file size valuein the file system properties dialog ofthe Space Management Console.

Explanation: The Stub file size that you has specifiedis not supported by this file system.

System action: Wrong stub file size is not applied tothe file system.

User response: Correct the stub file size in the filesystem properties dialog of the Space ManagementConsole.

FMV8840E The maximum number of candidatesthat was specified for file system :filesystem-name is out of range. Themaximum number of candidates valuethat was entered in the file systemproperties dialog is out of range. Correctthe maximum number of candidatesvalue in the file system propertiesdialog of the Space ManagementConsole.

Explanation: The maximum number of candidatesvalue that was specified is out of range for this filesystem.

System action: Wrong maximum number ofcandidates value is not applied to the file system.

User response: Correct the maximum number of

candidates value in the file system properties dialog ofthe Space Management Console.

FMV8841E The server name that was specified forthe file system : optfile-name is not valid.Correct the server name value in theclient node properties dialog of theSpace Management Console.

Explanation: The server name that was specified isnot valid.

System action: Wrong server name value is notapplied to the system options file.

User response: Correct the server name value in theclient node properties dialog of the Space ManagementConsole.

FMV8842E The Space Management API was notable to modify system options file :optfile-name because of insufficientprivilege. Use root user to change HSMmanaged file system configuration.

Explanation: User has no rights to modify systemoptions file.

System action: Changes are not applied to the systemoptions file.

User response: Run as root user to change HSMmanaged file system configuration.

FMV8843E No correct include/exclude settings arefound in system options file :optfile-name. Correct the include/excludelist in the system options file.

Explanation: The include/exclude settings in thesystem options file are not correct.


User response: Correct the include/exclude list in thesystem options file.

FMV8844E A incorrect preferred node or servername was specified in the HSMconfiguration for filesystem-name. Correctthe preferred node and server namevalue in the HSM configuration.

Explanation: The Space Management API could notchange preferred node settings because a wrong valuewas specified


User response: Correct the preferred node and serversettings in Space Management Configuration.



FMV8845E A incorrect owner node or server namewas specified in the HSM configurationfor filesystem-name. Correct the ownernode and server name value in the HSMconfiguration.

Explanation: The Space Management API could notchange owner node settings because a wrong value wasspecified


User response: Correct the owner node and serversettings in Space Management Configuration.

FMV8846E The Space Management API was notable to update the HSM managed filesystem : filesystem-name.

Explanation: The Space Management API could notapply configuration changes to the HSM managed filesystem.

System action: Changes are not applied to HSMmanaged file system.

User response: See error log file for additionalinformation why the update of the file system fails.

FMV8847E The Space Management API was notable to obtain a lock on SDR file for filesystem : filesystem-name.

Explanation: The Space Management API could notlock the SDR file for the file system.

System action: Changes are not applied to HSMmanaged file system.

User response: See the error log file for additionalinformation on why the lock on the SDR file fails.

FMV8848E The Space Management API could notopen file system status file to retrievemanaged file system statistics for :filesystem-name. Reason could beinsufficient permissions or that the filedoes not exist. The managed file systemstatistics are not retrieved from theHSM system.

Explanation: The Space Management API could notretrieve managed file system information from filesystem status file. The error occurred when the APItries to open the file for reading.

System action: Managed file system statistics are notretrieved and information is not displayed in the SpaceManagement Console.

User response: See the error log file for additionalinformation on why opening the file system status filefails.

FMV8849E The Space Management API was notable to load HSM managed file systemstatistics for : filesystem-name. Check tosee if the managed file system that wasselected in the file system list is stillHSM managed. Refresh the file systemview in the Space Management Consoleby pressing F5 on your keyboard orselect 'Refresh` under the View menu.

Explanation: The Space Management API could notload managed file system statistics from selected filesystem. The reason could be that the file system is notlonger HSM managed.

System action: Managed file system statistics are notretrieved and information is not displayed in the SpaceManagement Console.


FMV8850E The Space Management API was notable to add HSM to file system :filesystem-name. This error occurs becauseselected file system is not mounted. Youmust mount the file system before youcan add HSM.

Explanation: The Space Management API could notadd HSM to a file system, because it is not mounted.

System action: The add HSM operation fails and HSMis not added to the selected file system.

User response: Mount the selected file system beforeadding HSM.

FMV8851E The Space Management API was notable to add HSM to file system :filesystem-name. This error occurs becauseselected file system is not supported toadd HSM.

Explanation: The Space Management API could notadd HSM to a unsupported file system.


User response: Select a supported file system to addHSM.

FMV8852E The Space Management API was notable to add HSM to file system :filesystem-name. This error occurs becauseselected file system is already HSMmanaged.

Explanation: The Space Management API attempt tomanage a already HSM managed file system.

System action: The add HSM operation fails and the



selected file system stays HSM managed.

User response: Select a not managed file system toadd HSM.

FMV8853E The Space Management API was notable to add HSM to file system :filesystem-name.

Explanation: The Space Management API attempt tomanage file system and fails for a unknown reason.


User response: Retry the add HSM operation. If thisdoes not solve the problem, see the error log file foradditional information and contact Tivoli StorageManager technical support.

FMV8854E The Space Management API was notable to remove HSM from file system :filesystem-name. The error occurs whenthe Space Management API tries to lockthe SDR file and fails.

Explanation: The Space Management API attempt tounmanage (remove) file system and fails for aunknown reason.

System action: The remove HSM operation fails andHSM is not removed from the selected file system.

User response: Try the remove HSM operation again.If this does not solve the problem, see the error log filefor additional information and contact Tivoli StorageManager technical support.

FMV8855E The Space Management API was notable to start automatic migration on thefile system : filesystem-name.

Explanation: The Space Management API tries to startautomatic migration on a file system and fails for aunknown reason.

System action: The automatic migration is not startedfor the file system.

User response: See the error log file for additionalinformation and contact Tivoli Storage Managertechnical support.

FMV8856E The Space Management API was notable to start reconciliation process onthe file system : filesystem-name.

Explanation: The Space Management API tries to startreconciliation process on a file system and fails for aunknown reason.

System action: The reconciliation process is notstarted for the file system.

User response: See the error log file for additional

information, and contact Tivoli Storage Managertechnical support.

FMV8857E The Space Management API was notable to start scout process on the filesystem : filesystem-name.

Explanation: The Space Management API tries to startscout process on a file system and fails for a unknownreason.

System action: The scout process is not started for thefile system.

User response: See the error log file for additionalinformation, and contact Tivoli Storage Managertechnical support.

FMV8858E The Space Management API was notable to migrate the file : file-name. Theerror occurred in function :function-name.

Explanation: The Space Management API tries tomigrate a file and fails in the displayed API function.

System action: The selected file is not migrated to theserver.


FMV8859E The Space Management API was notable to recall the file : file-name. Theerror occurred in function :function-name.

Explanation: The Space Management API tries torecall a file and fails in the displayed API function.

System action: The selected file is not recalled fromthe server.


FMV8939E An unexpected error occurred trying tofilter the directory tree. rc=return-code

Explanation: The filter was not applied to thedirectory tree.

System action: The directory tree is not filtered.

User response: Contact your system administrator forfurther assistance.

FMV8945E An unexpected error occurred analyzingthe directory tree. The list of filesmatching your search criteria is notcompleted. rc=return-code

Explanation: It was not possible to search all items



matching the search criteria on the directory tree due toan unexpected error.

System action: The search results table shows only theitems found until the error is occurred.

User response: Contact your system administrator forfurther assistance.

FMV8946E RPC call failed.

Explanation: Unable to connect receiver recalldaemon.


User response: System is not operating correctly orrecall daemons are not started.

FMV9005W program name: invalid 'parameter name'value: value (must be in [minimumvalue..maximum value]).

Explanation: The program found an invalid parameterin the space management configuration of a filesystem.

System action: The paramter value was rejected.

User response: In case you tried to set the specifiedvalue manually, choose a value from the specifiedrange instead. If the value is read from a file system'sspace management configuration file (located at[fs]/.SpaceMan/hsmfsconfig.xml), edit the fileaccordingly. The name of the filesystem can bedetermined from a subsequent error message.

FMV9007W program name: invalid 'parameter name'value: value (must be in [minimumvalue..maximum value]).

Explanation: The program found an invalid parameterin the space management configuration of a filesystem.

System action: The paramter value was rejected.

User response: In case you tried to set the specifiedvalue manually, choose a value from the specifiedrange instead. If the value is read from a file system'sspace management configuration file (located at[fs]/.SpaceMan/hsmfsconfig.xml), edit the fileaccordingly. The name of the filesystem can bedetermined from a subsequent error message.

FMV9008W Compression is enabled. Recall modefor file file-name cannot be set to partial.

Explanation: Tivoli Storage Manager can only set fileattributes to a uncompressed migrated file. This file hasbeen migrated with compression enabled.

System action: Tivoli Storage Manager does not setthe file attributes.

User response: Recall the file to state resident disable

compression and migrate the file again. Retry theoperation.

FMV9009E program name: found invalid spacemanagement configuration for'filesystem'.

Explanation: The program found an invalid spacemanagement configuration for the given filesystem.

System action: The space management configurationwas rejected for the given filesystem . When updatingan existing configuration, invalid configurations to setare ignored. When a persistent configuration file isinvalid, the filesystem will appear to not have spacemanagement enabled.

User response: In case you tried to update spacemanagement for this filesystem manually, enter a validconfiguration instead. In case the persistentconfiguration file is invalid, edit the file accordingly;alternatively, you can add space management explicitly(which will remove / overwrite the existingconfiguration). The reason for the configuration can bedetermined from a preceding error message. Thefilesystem's space management configuration file islocated at 'filesystem'/.SpaceMan/hsmfsconfig.xml.

FMV9010E program name: could not parse spacemanagement configuration file'configuration file' for filesystem.

Explanation: The space management configuration filefor the given filesystem is present but its contentappears to have invalid format.

System action: The configuration was rejected. Thefilesystem will appear to not have space managementenabled.

User response: Check the given space managementconfiguration file; it is supposed to contain awell-formed XML document with a root elementnamed 'HsmFsConfig'. To create a new configurationfile, you can simply add space management to thisfilesystem.

FMV9011E program name: could not write spacemanagement configuration file'configuration file' for filesystem.

Explanation: IBM Tivoli Storage Manager could notwrite and save the space management configuration filefor the given filesystem.

System action: IBM Tivoli Storage Manager did notsave the space management configuration information.If you tried to add space management for thisfilesystem, it was not added. If you tried to update thespace managment configuration, it was probably notupdated. If an existing configuration file in old formatwas read successfully, but could not be converted toXML format, space management will be active for this



filesystem with the configuration from the old file.

User response: Determine if there is any reason whythe given file cannot be written.

FMV9012E error-program: Command must be run byroot user.

Explanation: Tivoli Storage Manager requires that aroot user perform this operation.

System action: Tivoli Storage Manager terminates theoperation.

User response: Change to root user, and then retry theoperation.

FMV9016E Cannot get space management migrationstatus for path.

Explanation: An error occurred while trying to get thespace management migration status. Either thepermissions for the status file are not set correctly, orthe status file is damaged.


User response: The root user should check thepermissions of the status file, or contact the servicerepresentative.

FMV9017W error-program: Minimum number ofrecall daemons min-dsmrecalld cannot begreater than maximum number of recalldaemons max-dsmrecalld; defaulting tominimum min-dsmrecalld and maximummax-dsmrecalld.

Explanation: A minimum number of recall daemonshas been entered that is greater than the maximumnumber of recall daemons.

System action: Tivoli Storage Manager uses defaultsinstead of the values specified in the client systemoptions file (dsm.sys).

User response: Correct the MINRECALLDAEMONSand MAXRECALLDAEMONS options in the clientsystem options file and retry the operation.

FMV9020E Could not establish a session with aTivoli Storage Manager server or clientagent. The Tivoli Storage Managerreturn code is tsm-error;.

Explanation: A communication error occured. Thereturn code is provided to help diagnose the problem.


User response: Check the Tivoli Storage Managererror log for communications failures such as TCP/IP,shared memory, or named pipe errors.

FMV9021E error-program Unknown recall daemon(pid process-ID) terminated abnormally,status: status.

Explanation: A recall daemon stops abnormally.


User response: Try the operation again. If the problempersists, send the core file to IBM technical support foranalysis.

FMV9022E error-program Recall daemon (pidprocess-ID) ended abnormally, status:status.

Explanation: A recall daemon stopped abnormally.

System action: The operation does not complete.

User response: Try the operation again. If the problempersists, send the core file to IBM technical support foranalysis.

FMV9024E Starting with this release all candidateprocessing is done internally by theTivoli Storage Manager monitordaemon. Thus -c is no longer a validoption for dsmreconcile.

Explanation: The command line options -c and-Candidates are no longer valid for dsmreconcile as allcandidates processing is now performed bydsmmonitord.

System action: Tivoli Storage Manager detected aninvalid option. dsmreconcile is exiting.

User response: Don't use options -c and -Candidateswith dsmreconcile anymore.

FMV9025E The Data Protection for WebSphereplug-in version and the backup-archiveclient version do not match. Pleaseupgrade your Data Protection forWebSphere plug-in.

Explanation: The release and version of the DataProtection for WebSphere plug-in is downlevel from therelease and version of the Backup-Archive Client.

System action: None

User response: Upgrade Data Protection forWebSphere to the proper release and version.

FMV9028E program name: could not acquire lock forfilesystem.

Explanation: Prior to modifying a space managementconfiguration file, it is required to lock the file in orderto avoid concurrent access. If acquiring the lock fails,there was a concurrent access.



System action: The action was cancelled.

User response: Retry the same request or determinethe process holding the lock.

FMV9029E The WebSphere server is running, butthe server must be shut down for arestore operation. Shut down theWebSphere server and try the restoreoperation again.

Explanation: The WebSphere server must be broughtdown to perform a restore.

System action: The restore operation fails.

User response: Shut down the WebSphere server andtry the restore operation again.

FMV9030W Cannot set conflicting attributes to filefile-name.

Explanation: Tivoli Storage Manager cannot set thefile attributes because the requested attributes are inconflict with one another.


User response: Retry this operation with attributesthat do not conflict with each other.

FMV9031W File file-name is not a migrated file.

Explanation: Tivoli Storage Manager can only set fileattributes to a migrated file. This file has not beenmigrated.


User response: Migrate this file, and then retry theoperation.

FMV9032W File file-name is not in an HSM managedfile system.

Explanation: Tivoli Storage Manager detects that thefile is not in an HSM managed file system, andtherefore, it cannot perform the operation requested.


User response: Add space management to the filesystem, migrate the file, and then retry the operation.

FMV9034E The restore operation did not complete,due to a change in the originalWebSphere environment.

Explanation: The data must be restored to the sameenvironment that it was backed up from. This includesitems such as cell name, node name, and the locationwhere WebSphere is installed.

System action: The restore operation does notcomplete.

User response: Perform the restore procedure in theDP for WebSphere book.

FMV9036W program-name: migrated file(s) aremissing on server for number stub file(s).Look in 'file-spec' for file names.

Explanation: Tivoli Storage Manager cannot find themigrated file(s) on the server.

System action: Tivoli Storage Manager continues.

User response: Look in the path mentioned in themessage for the file name. Also ensure that you areworking with the correct server for this file.

FMV9054E The plug-in was not found.

Explanation: None.

System action: None

User response: Run "dsmc show plugins" at thecommand prompt to see the available plug-ins on thesystem.

FMV9057W error-program: cannot get spaceinformation for file-system: error.

Explanation: Tivoli Storage Manager cannot get thespace information for the file system.


User response: Verify that space management hasbeen added to the file system.

FMV9059E error-program: process cannot detach tobecome a daemon.

Explanation: Tivoli Storage Manager process cannotdetach itself to become a daemon.

System action: Tivoli Storage Manager cannot startthe daemon as requested. Tivoli Storage Manager stops.

User response: Retry the operation.

FMV9060W error-program: cannot get and increaselimit of open files.

Explanation: Tivoli Storage Manager either cannot getthe limit of the number of open files, or cannot increasethe limit of the number of open files.

System action: Tivoli Storage Manager cannot increasethe number of open files, and was not able to completethe operation.

User response: Free some file space by ending someprocesses or removing some files, and retry theoperation.



FMV9062E File 'filename' has changed during thebackup.

Explanation: A file changed during the backup. Checkthe dsmerror.log file for a list of files that havechanged.

System action: The backup fails.

User response: Try the backup again.

FMV9063E error-program: file system file-system is outof inodes.

Explanation: Tivoli Storage Manager cannot get spacefor the file system because the file system is out ofinodes.

System action: Tivoli Storage Manager cannot getspace via migration.

User response: Remove some files to make moreinodes available and retry.

FMV9064E error-program: Cannot fork a newprocess: error.

Explanation: Tivoli Storage Manager cannot fork anew process that is needed. If the operating systemerrno is EAGAIN, then the limit on the total number ofprocesses running on the system or by a single user hasbeen exceeded, or the system does not have theresources necessary to create another process. If theerrno is ENOMEM, then there is not enough memoryto create the process.


User response: Depending on the error code (errno),either allocate additional virtual memory (swap space)or increase the operating system process limit. Thenrestart the HSM daemons or reboot the system.

FMV9065E File 'filename' or file 'filename2' has beenadded or removed during the backup.

Explanation: A file was added or removed during thebackup.



FMV9067W error-program: error updatingdsmmigfstab file for file-system.

Explanation: Tivoli Storage Manager found an error inupdating the dsmmigfstab file for this file system.

System action: Tivoli Storage Manager does notupdate the dsmmigfstab file.

User response: See the preceding error message andcorrect the error if possible. Then, retry the operation. If

problem persists, contact your system administrator.

FMV9068I program-name: dsmmigfstab file updatedfor file system file-system.

Explanation: Tivoli Storage Manager successfullyupdated the dsmmigfstab file for the file system.


User response: Continue with normal operation.

FMV9069I program-name: all file systems arereactivated to previous states.

Explanation: Tivoli Storage Manager has reactivatedall file systems managed by HSM to their previousstates before the global deactivation.



FMV9070I program-name: space management is nowdeactivated for all HSM file systems.

Explanation: Tivoli Storage Manager has deactivatedspace management for all file systems listed in thedsmmigfstab file.



FMV9071W program-name: error reactivating spacemanagement for all HSM file systems.

Explanation: Tivoli Storage Manager found an error intrying to reactivate space management.

System action: Tivoli Storage Manager does notreactivate space management for HSM file systems.

User response: Make sure space management isinstalled correctly and retry the operation.

FMV9072W error-program: error deactivating spacemanagement for all FSM file systems.

Explanation: Tivoli Storage Manager found an error intrying to deactivate space management.

System action: Tivoli Storage Manager does notdeactivate space management for FSM file systems.


FMV9073W program-name: error deactivating spacemanagement for file system file-system.

Explanation: Tivoli Storage Manager found an error intrying to deactivate the file system.

System action: Tivoli Storage Manager does notdeactivate space management for the file system.




FMV9074I program-name: space managementfunctions have been locally deactivatedfor file system file-system.

Explanation: Tivoli Storage Manager has locallydeactivated space management functions likemigration, recall and reconciliation for the file system.



FMV9075W program-name: error reactivating spacemanagement for file system file-system.

Explanation: Tivoli Storage Manager found an error intrying to reactivate space management for the filesystem.

System action: Tivoli Storage Manager does notreactivate space management for the file system.

User response: Verify that the specified file system ismounted 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 theoutput from the mount and dsmdf commands.

FMV9076I program-name: space managementfunctions have been locally reactivatedfor file system file-system.

Explanation: Tivoli Storage Manager has locallyreactivated space management functions like migration,recall and reconciliation for the file system. Please, notehowever that the space management might still beglobally deactivated.



FMV9077I program-name: removed spacemanagement from file system file-system.

Explanation: Tivoli Storage Manager removed spacemanagement. The file system is now a native filesystem.



FMV9078W Space management is not removed fromfile system file-system.

Explanation: Tivoli Storage Manager was not able toremove space management from this file system.Possible causes:

v Kernel extension is downlevel.

v Program is downlevel.

v Insufficient disk space.


User response: Refer to the immediately precedingerror message and retry the operation.

FMV9079W program-name: no migrated filesmatching search criteria found.

Explanation: Tivoli Storage Manager did not find anymigrated files matching the search criteria.


User response: Retry the operation with a differentsearch criteria.

FMV9080E program-name: not enough space in filesystem or storage pool to recall allmigrated files.

Explanation: Tivoli Storage Manager detects there isnot enough space in the file system to hold all themigrated files if all are recalled. If you are using GPFSstorage pools, each pool needs to have enough space torecall it's files.

System action: Tivoli Storage Manager does notattempt to recall all the migrated files.

User response: Make room in the file system byincreasing the file system size or removing some files.Retry the operation.

FMV9081W program-name: orphaned stub file(s)detected in file system file-system.

Explanation: Tivoli Storage Manager detected one ormore orphaned stub files. Either the migration serverwas changed in the client system options file after thefile was migrated, or the migration server database isdamaged.

System action: Tivoli Storage Manager does notattempt to remove space management from the filesystem.

User response: Determine the cause of orphaned stubfiles. Switch to the correct migration server and recallthe migrated files. Retry the operation.

FMV9082W program-name: error encountered whilereconciling file system file-system.

Explanation: Tivoli Storage Manager encountered anerror performing reconciliation on the file system.


User response: Refer to other messages displayed or



messages in the log to correct the problem. Then retrythe operation.

FMV9083W program-name: cannot deactivate spacemanagement on file system file-system.

Explanation: Tivoli Storage Manager cannot deactivatespace management on the file system.


User response: Correct the error if possible and retrythe operation.

FMV9084E program-name: file-system is not managedor not locally managed by spacemanagement.

Explanation: There is no entry for the file system inthe dsmmigfstab file or the file system is managed byanother node.

System action: Tivoli Storage Manager will notperform space management functions on this filesystem.

User response: Add space management to the filesystem, if appropriate, and then retry the operation. Ifthe file system is not locally managed, retry theoperation on the node managing the file system.

FMV9085E program-name: file system file-system isnot managed by space management.

Explanation: There is no entry for the file system inthe dsmmigfstab file.

System action: Tivoli Storage Manager will notperform space management functions on this filesystem.

User response: Add space management to the filesystem, if appropriate, and then retry the operation.

FMV9086E program-name: A DMAPI error occuredadding space management to file systemfile-system, It is possible DMAPI isdisabled on this file system. The systemset the error code: errno = errno-value

Explanation: Tivoli Storage Manager encountered anerror and cannot add space management to the filesystem.

System action: Tivoli Storage Manager Spacemanagement cannot be added to file system.

User response: Verify that DMAPI is enabled for thisfile system and retry the operation.

FMV9087I Space management is successfullyadded to file system file-system.

Explanation: Tivoli Storage Manager has added spacemanagement to the file system, and will now monitorits space usage. You can also perform other spacemanagement operations on this file system.



FMV9088W program-name: space management isalready active for file system filesystem.

Explanation: This message is issued when trying toadd space management to a filesystem with spacemanagement already activated. It is not possible to addspace management for a filesystem that already hasspace management activated.


User response: In case you wanted to update thefilesystem's space management configuration instead,use the appropriate update command.

FMV9089E The group backup validation failed.One or more files were added, removed,or changed during the backup.

Explanation: One or more files have been added,removed, or changed from the time WebSphere wasqueried to the time that all the data was sent to theTivoli Storage Manager server. Check the dsmerror.logfile for a list of files that were added, removed, orchanged.



FMV9090E program-name: file-system is not a validfile system name.

Explanation: Tivoli Storage Manager received aninvalid file system name. The file system is notmounted, or is not mounted correctly.


User response: Correct the file system name, and retrythe operation.

FMV9091E The WebSphere backup validationfailed. One or more files were added,removed, or changed during the backup.

Explanation: One or more files have been added,removed, or changed from the time WebSphere wasqueried to the time that all the data was sent to theTivoli Storage Manager server. Check the dsmerror.logfile for a list of files that were added, removed, orchanged.




User response: Try the backup again. Do not installnew WebSphere applications or change the WebSphereconfiguration while in the backup window.

FMV9092W AES 128-bit Encryption is not beingused.

Explanation: AES 128-bit encryption is not being used.DES 56-bit encryption is being used instead.

System action: DES 56-bit Encryption is used insteadof AES 128-bit encryption.

User response: If the user wants to use AESencryption, then the user must install the IBM JRE inorder to enable AES encryption for the web client.

FMV9093W program-name: cannot update migrationcandidates list file-name.

Explanation: Tivoli Storage Manager cannot updatethe migration candidates list because not enoughmemory is available to create a temporary file.


User response: Make some memory available byending some processes, and then retry the operation.

FMV9094W program-name: no candidates found infile system file-system.

Explanation: Tivoli Storage Manager found no fileseligible for migration in the file system after runningdsmreconcile.



FMV9098E program-name: space management doesnot support file system file-system.

Explanation: Tivoli Storage Manager spacemanagement does not support this type of file system.Space management supports only true local file systems(e.g. JFS on AIX). Space management does not supportother types of file systems (AFS™, NFS, etc).

System action: Processing of the file system stopped.


FMV9099E program-name: space management is notactive for file system file-system.

Explanation: Tivoli Storage Manager found the filesystem did not have space management activated.

System action: Processing of that file system stopped.

User response: Reactivate space management for thefile system.

FMV9100E Unable to open file 'filename' for output.

Explanation: The file name specified cannot beopened.

System action: Make sure that user has access to writeto specified file, or use different file name.

User response: Output will not be saved. Pleasespecify different file or check permissions on chose file.

FMV9101E Migrated files matching 'file-name' couldnot be found.

Explanation: File name for search pattern can not befound in the TSM server database as a migrated file.

System action: No query result.

User response: Verify that the search patter is correct.

FMV9117E Virtual machine 'VM name' will not bebacked up because it contains at leastone of the following unsupportedspecial characters special characters

Explanation: The specified virtual machine containscharacters that are not supported for virtual machinebackup and restore operations.


User response: Rename the virtual machine so that itdoes not contain any of the specified special characters.

FMV9121I Activate completed.

Explanation: A Domino activate databases operationwas completed.

System action: Tivoli Storage Manager activated thedatabases.


FMV9126E program-name: cannot determine whetherspace management is active or inactivefor file-system due to error: error.

Explanation: The program 'program-name' indicatedin the message text was unable to obtain statistics forfile system 'file-system'. Therefore the program cannotdetermine whether space management is activated,deactivated, or globally deactivated on that file system.The message text includes a description of the Unixerrno error that occurred while trying to get the state ofspace management.

System action: Tivoli Storage Manager stops theoperation.

User response: Verify that the file system is mountedand accessible. Using the appropriate tools for that filesystem, check whether there are any I/O or other



integrity errors on that file system. Then try theoperation again. If the operation fails, then a systemreboot might clear the error condition. If, after takingthese actions the problem persists, contact IBMtechnical support for assistance.

FMV9128I Inactivate logs completed.

Explanation: A Domino inactivate log operation wascompleted.

System action: Tivoli Storage Manager inactivated thelog.


FMV9133E program name: space management alreadyactive for filesystem.

Explanation: This message is issued when trying toadd space management to a filesystem with spacemanagement already activated.


User response: Check the filesystem's spacemanagement configuration and consider updating it incase it does not match your needs. It is not possible toadd space management for a filesystem that alreadyhas space management activated.

FMV9134E program name: space management notactive for filesystem.

Explanation: The program requested the spacemanagement configuration for a file system wherespace management is not active.


User response: In case you entered the filesystemspecification, check for correct spelling. It is notpossible to perform space management actions on afilesystem with space management not activated.

FMV9135E program name: space management forfilesystem not controlled by the localnode.

Explanation: The program requested the spacemanagement configuration for a file system wherespace management is active, but not controlled by thelocal node. In cluster environments, some spacemanagement actions are allowed from the owner nodeonly.


User response: Determine the controller node for thisfilesystem and retry.

FMV9136E program name: could not removeconfiguration file for filesystem.

Explanation: During removal of space managementfor the given filesystem, this configuration file couldnot be removed.

System action: Space management could not bedeactivated for this filesystem.

User response: Determine the reason why the filecould not be removed and retry.

FMV9137I File: file-name is not premigrated.

Explanation: File must be premigrated to migrate it.

System action: The file was skipped.

User response: The migration of premigrated filesrequires that the file is in premigration state.

FMV9140E The migration options premigration andstub cannot be combined.

Explanation: The migration option premigration andstub are mutual exclusive. Both options end in differentresults for the same file.

System action: Command ends without changes to thefile.

User response: Use the migration optionspremigration and stub in different instances of thecommand.

FMV9145E Virtual machine will not be backed upbecause it has an empty name.

Explanation: The specified virtual machine name isempty. This is not supported for virtual machinebackup and restore operations.


User response: Rename the virtual machine so that itsname contains supported characters.

FMV9146E An RPC error has happened inprog-name executable! RPC error code:rpcStat-value, reason: rpcStat-explanation

Explanation: Tivoli Storage Manager executable got anRPC error and was unable to continue the currentoperation.

System action: Processing of the current operation isstopped.

User response: Make sure that the appropriate RPCservices are up and running on your system. Forexample: - on Linux, run 'service portmap status' or'service rpcbind status' or 'systemctl status rpcbind'command depending on the Linux distribution in use; -

