DSM_OBJ_FILE or DSM_OBJ_DIRECTORY for Backup, or
DSM_OBJ_FILE for Archive.

User response

For dsmDeleteFS the repository must be one of the following:

DSM_ARCHIVE_REP
DSM_BACKUP_REP
DSM_REPOS_ALL.

stBackup
stArchive
stBackupMountWait
stArchiveMountWait

2022 EFMV0228E DSM_RC_INVALID_SENDTYPE The dsmSendObj sendType is invalid.

Edit online

Explanation

The dsmSendObj sendType is invalid.

System action

The system returns to the calling procedure.

User response

The sendType must be one of the following:

stBackup
stArchive
stBackupMountWait
stArchiveMountWait

2023 EFMV0229E DSM_RC_INVALID_PARAMETER The dsmDeleteObj delType is invalid.

Edit online

Explanation

The dsmDeleteObj delType is invalid.

System action

The system returns to the calling procedure.

User response

The delType must be dtBackup or dtArchive.

2024 EFMV0230E DSM_RC_INVALID_OBJSTATE The query Backup objState is invalid.

Edit online

Explanation

The query Backup objState is invalid.

System action

The system returns to the calling procedure.

User response

The qryBackupData.objState must be one of the following:

DSM_ACTIVE
DSM_INACTIVE
DSM_ANY_MATCH

Consult the documentation for the application and verify that the application is configured correctly. If the problem persists, contact the application vendor for further assistance.

2033 EFMV0237E DSM_RC_NO_NODE_REQD On dsmInit, the node is not allowed when PASSWORDACCESS=generate.

Edit online

Explanation

PASSWORDACCESS=generate establishes a session with the current hostname as the node.

System action

The system returns to the calling procedure.

User response

When using PASSWORDACCESS=generate, set clientNodeNameP to NULL.

2041 EFMV0238E DSM_RC_BAD_CALL_SEQUENCE The sequence of calls is invalid.

Edit online

Explanation

Then API requires function calls to be made in a specific sequence. The function calls were not made in the expected sequence. The error can be triggered by the following issues:

An error in the network.
A bug in the IBM Storage Protect API.
A bug in the IBM Storage Protect server.
A bug in the application (IBM Storage Protect or third party) that uses the IBM Storage Protect API.

System action

The system returns to the calling procedure.

User response

An end user can respond in the following ways:

Check the network for errors.
Look for clues in the IBM Storage Protect server activity log file, client side dsierror.log log file, and log files that are specific to the problem application.
Search the IBM Storage Protect support pages for APARs that match the problem. The support site is at https://www.ibm.com/mysupport/s/topic/0TO50000000IQWvGAO/storage-protect?language=en_US
If the API application is developed by a third party (not IBM Storage Protect), search that third party's support pages for known issues that match the problem.

User response

Verify the following:

The dsmGetList is not NULL.
Each objID is not NULL.
The dsmGetList numObjId is not zero.

Explanation

This transaction must be ended and a new one must be started due to one of the following reasons:

The destination changed.
The byte limit is exceeded
The maximum number of objects is exceeded.

System action

The system returns to the calling procedure.

User response

The accessType must be one of the following:

atBackup
atArchive

Reset the USESNAPOFASNAPTOMOUNT option to No in the Data Protection configuration file and set MOUNTRW=Yes to mount the read/write backup.

FMV0990W Options file '`file-name`' could not be found. Default option values will be used.

Edit online

Explanation

Common reasons for this warning include:

The default options file does not exist, and
You did not specify the -OPTFILE option when starting the IBM Storage Protect client, and
the environment variable DSM_CONFIG was not set.

User response

Run DSMC QUERY MGMTCLASS -DETAIL to view information about available management classes.

If the file is being bound to the default management class, make sure the management class has a backup copy group.
If the file is being bound to a management class specified in an INCLUDE statement, make sure that the management class has a backup copy group.
If you have more than one IBM Storage Protect server, make sure you are connecting to the correct server.
If you are unable to find a suitable management class, contact your IBM Storage Protect administrator for further assistance.

FMV1008E Sending of object '`object-nameobject-nameobject-name`' failed: No Archive Copy Group

Edit online

Explanation

The management class for this file (object-name) did not have an archive copy group specified.

System action

The file could not be backed up.

User response

See your system administrator.

FMV1009W An error occurred processing the operating system include/exclude statements. The error was detected while processing: `subsystemname`.

Edit online

Explanation

The client encountered an error while obtaining the automatic include/exclude statements from the operating system. Possible reasons for this error include:

The specified registry key cannot be opened for reading
The entry under this key has incorrect data

System action

Processing continues without the full list of operating system include/exclude statements.

User response

Ensure that you have access to the specified registry key and that entries are a MULTISZ values that contain:

Individual files
Directories
Wild card entries
Environment variables
/s switch (the /s switch is used on directory and/or wild card entries and signifies that all subdirectories of this directory should be excluded)

If the cause of this message can not be determined or resolved, contact IBM Storage Protect technical support for further assistance.

FMV1010E Error processing '`filespace-name`': Unsupported file system operation.

Edit online

Explanation

The file system does not support an operation 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 supported by the IBM Storage Protect client. If a restore or retrieve failed, retry the operation to another location. If the problem persists, look for other indications of system problems. It may be necessary to run the operating system utility that checks and repairs file system inconsistencies. If the problem still cannot be resolved, contact your IBM Storage Protect administrator for further assistance.

0068 EFMV1015E DSM_RC_CLIENT_NOT_ARCHRETPROT The session is rejected. The server does not allow a signon of a client that is not archive-retention protection enabled.

Edit online

Explanation

The client cannot establish a connection to the server because the server is enabled for archive-retention protection enabled and the client is not.

System action

The session is not started.

User response

See your system administrator.

FMV1016I No eligible files matching '`pathname`' were found.

Edit online

Explanation

The backup or archive operation completed, but no files were processed. Possible reasons for this include:

The directory that was backed up or archived contains no files
The files are excluded from backup or archive

The system is low on memory.
The process in which the program runs has exceeded the maximum memory that it is allowed to allocate.
Some other error condition occurred that caused the program to think it is out of memory.

System action

Requested operation cannot be completed.

User response

Close all unneeded applications and try the operation again. If the operation still fails, try dividing the task into several smaller units. For example, if a file specification contains several high level directories, run the IBM Storage Protect task serially for each directory. If the IBM Storage Protect task is an incremental backup, use the option "-memoryefficientbackup=yes".

For UNIX systems that support resource limits, check to see b if the memory resource limit is too low by entering the following command: ulimit -a

Based on the resulting data, you can ask the UNIX system root user to increase resource limits so that it will override the current default. The UNIX system root user has the authority to increase resource limits.

-051 EFMV1031E DSM_RC_CONN_TIMEDOUT The attempt to establish a TCP/IP connection timed out before the connection was made.

Edit online

Explanation

The Object of the connection attempt failed to respond within the the allotted wait time. In the case of the B/A client, this message is preceded in dsmerror.log by message FMV5216E that gives details of the connection that failed. The condition may be temporary.

System action

processing stops.

User response

Restart the IBM Storage Protect client and retry the operation.
Check the client options file and verify that TCPSERVERADDRESS and TCPPORT specify the correct TCP/IP address and port number for your IBM Storage Protect server.
Verify that network connectivity exists between the IBM Storage Protect client machine and the IBM Storage Protect server machine.
If the problem persists, see your IBM Storage Protect administrator for further assistance.

-052 EFMV1032E DSM_RC_CONN_REFUSED An attempt to establish a TCP/IP connection was rejected by the host

Edit online

Explanation

An attempt to establish a TCP/IP connection was rejected by the server.

System action

Processing stopped.

User response

The server was not fully initialized, is not currently running, was not enabled for TCP/IP communications, or an incorrect TCP/IP port number was specified. If the problem continues, see your system administrator.

-053 EFMV1033E DSM_RC_BAD_HOST_NAME An invalid TCP/IP address was specified.

Edit online

Explanation

The TCP/IP address specified by the IBM Storage Protect client's TCPSERVERADDRESS setting could not be found on the network. Common reasons for this error include:

The TCPSERVERADDRESS client option specifies the wrong TCP/IP address for the IBM Storage Protect server".
The machine that hosts the IBM Storage Protect server is not on the network.
A network problem is preventing the IBM Storage Protect client from reaching the machine that hosts the IBM Storage Protect server.

System action

processing stops.

User response

Verify that the TCPSERVERADDRESS and TCPPORT settings have the correct values for your IBM Storage Protect server. Use your operating system's "ping" (or similar) utility to ensure that your machine can locate the machine that hosts the IBM Storage Protect server across the network. Try the operating again. If the problem persists, ask your IBM Storage Protect administrator for further assistance.

-054 EFMV1034E DSM_RC_NETWORK_UNREACHABLE The specified TCP/IP host name is unreachable

Edit online

Explanation

The TCP/IP host name specified in the TCPSERVERADDRESS statement cannot be reached.

System action

Processing stopped.

User response

Check your options file for the correct TCPSERVERADDRESS statement. See your administrator for the correct name of the server.

0406 SFMV1035S DSM_RC_NO_OPT_FILE Options file '`file-name`' could not be found, or it cannot be read.

Edit online

Explanation

Common reasons for this error include:

The default options file does not exist.
You specified the -OPTFILE option when starting the IBM Storage Protect client, but the options file you provided does not exist.
The DSM_CONFIG (or DSMI_CONFIG if you are using the IBM Storage Protect API) environment variable specifies an options file that does not exist.
You specified the -OPTFILE option when starting the IBM Storage Protect client, but the options file that you provided is not in the standard file encoding of the system. For example, on Windows the expected file encoding is FMVI.
You specified the -OPTFILE option when starting the IBM Storage Protect client, but the options file that you provided does not have appropriate read permissions for the user that is running the operation.

Explanation

IBM Storage Protect requires access to memory in order to store information as processing proceeds. In this case, more memory was requested than the operating system would allocate. Possible reasons include:

The system is low on memory.
The process in which the program runs has exceeded the maximum allocated memory.
Some other error condition occurred. No memory is available.

You specified an incorrect IBM Storage Protect option or option value.

System action

For the command line client: Processing stops.

For the native GUI client: There is a small set of options critical to the initialization of the client. If an error is found in one of these, this message is presented and the client terminates without further processing.

User response

Specify a correct IBM Storage Protect option as defined in the appropriate Using the Backup-Archive Client book for the particular operating system.

FMV1108E Invalid option (`option`) for the `function` command.

Edit online

Explanation

There are two possible reasons for this message:

The option option was specified for a command or subcommand (function) that cannot make use of that option.
The option appears on the initial command line and is not valid there.

System action

Processing stopped.

User response

See the Backup-Archive Client Installation and User's Guide for correct use of the named option.

FMV1110E The client help file `file-name` could not be opened.

Edit online

Explanation

This usually occurs when the help file file-name cannot be found.

System action

Processing stopped.

Perform the following actions to resolve this error:

Run the product in interactive mode.
Ensure your password is set correctly.

FMV1120E Removal of file space '`filespace-name`' failed

Edit online

Explanation

An attempt was made to delete a filespace (either NAS or normal) and it was unsuccessful.

Your client registration may not be authorized to delete filspaces on the server. Look for message FMV1126E.
The named filespace does not exist on the server. Look for message FMV1122W.
Other causes which will be made known in messages following this one

System action

processing stops.

User response

Take action as recommended by other messages that accompanies this one. If so indicated, try to remove the file space again. If the problem continues, your IBM Storage Protect administrator has the authority to delete the file space for you.

FMV1121I A request for removal of file space '`filespace-name`' has been successfully sent to the server.

Edit online

Explanation

Update the authorization, or delete the old rule and define a new one, or use the current authorization.

FMV1133W An expression might contain a wildcard not enclosed in quotes.

Edit online

Explanation

Explanation

An incremental backup was started, but no domain was selected. Possible reasons for this message include:

An attempt was made to back up a file system that is excluded with the EXCLUDE.FS option.
The DOMAIN is empty. That is, a DOMAIN statement excludes one or more file systems, but no DOMAIN statements include any file systems.
DOMAIN ALL-LOCAL is in effect but the system has no local file systems.

System action

processing stops.

User response

Verify that the DOMAIN statements are properly configured and try the backup again. DOMAIN statements can be in client option files (dsm.opt, dsm.sys), client option sets, schedule definitions, and scripted IBM Storage Protect commands. Corrective actions include:

Make sure the DOMAIN option settings specify the file systems you want to back up.
If a file system that should be backed up is excluded by an EXCLUDE.FS statement, remove the EXCLUDE.FS statement.
If a file system that should not be backed up is listed in a DOMAIN statement, remove the file system from the DOMAIN statement.
Make sure the DOMAIN is not empty. That is, if any DOMAIN statements exclude file systems from backup, make sure the DOMAIN statements include the file systems that should be backed up.

Edit online

Explanation

When the CLUSTERNODE option is set to YES, the event logs cannot be backed up or restored.

System action

The event logs are not backed up or restored.

Edit online

Explanation

Creation of the image object failed for one of the following reasons:

The image command was executed by a non-root user
The image plugin library was not found.

Edit online

Explanation

This client is not supported by the IBM Storage Protect express server. This can occur if:

the client is configured as an IBM Storage Protect express client using the CLIENTVIEW option
the client is trying to connect to an IBM Storage Protect express server.

System action

Processing stops.

User response

FMV1205E This is not a supported IBM Storage Protect express platform

Edit online

Explanation

This is not a supported IBM Storage Protect express platform.

System action

Processing stops.

Edit online

Explanation

The password is not updated because of one of the following reasons:

You entered an incorrect current password or
You entered a new password that does not fulfill the password length requirements. The length requirements are set on the server.

There is a problem on the tape.
There is a communications problem.
The compressed file was corrupted on the IBM Storage Protect Server.

Request the system administrator to add space to the storage pool.
For IBM Storage Protect client, set COMPRESSALWAYS=NO and COMPRESSIon=YES in the options file (DSM.OPT), then the file will be resent uncompressed if it grows during compression.
For API Applications, consult the application's documentation for recommendations regarding compression.
Turn off disk caching in the disk storage pool, and issue MOVE DATA commands to each disk pool volume to clear out the cached bitfiles.

Explanation

The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:

Data was corrupted at the server
Server found a read error
File is temporarily involved in a reclaim operation at the server
Server requested a tape volume that was marked unavailable.

System action

Because the file space cannot be renamed, the operation stops.

Edit online

Explanation

An error occurred that prevented the creation of the delta file. Possible reasons for this error include:

The base file cannot be opened for reading
The file being backed up cannot be opened for reading
The delta file cannot be opened for writing
The file being backed up has grown to a size larger than 2 GB
A memory file mapping of the file cannot be created

"IBM Storage Protect Backup for Administrators"
"IBM Storage Protect Scheduler for Administrators"
"IBM Storage Protect Scheduler Daemon for Administrators"

0053 EFMV1353E DSM_RC_REJECT_ID_UNKNOWN Session rejected: User ID is incorrect, does not have admin authority, or is not known by the server

Edit online

Explanation

The user ID, which is either IBM Storage Protect node name or administrative user ID, is not known by the server. Possible reasons for this include:

Your node name is not registered with the IBM Storage Protect server
The node name is correct but does not have a corresponding administrative ID with the same name and client owner authority
you are attempting to access a file that was migrated to a different node.

System action

Current operation has been cancelled.

User response

Do the following checks:

Check that your IBM Storage Protect user ID is entered correctly.
Check the administrative ID associated with your IBM Storage Protect node and verify that the IBM Storage Protect node name has a matching administrative ID with client owner authority for the node. If it does not, your IBM Storage Protect administrator needs to create it.
Check that the server is using closed registration and that your node name is registered with the server.
If attempting to access a migrated file, your node name must be the same node that migrated the file.

IBM Storage Protect client was unable to create a snapshot of the volume due to some reason. Instead of failing the operation, IBM Storage Protect client will perform a non-snapshot based backup.

System action

Snapshot processing stops.

User response

FMV1378E The snapshot operation failed. The SNAPSHOTCACHELocation does not contain enough space for this snapshot operation.

Edit online

Explanation

An unexpected amount of disk activity which is generating more changes than can be contained in the available space at this particular point in time.
The SNAPSHOTCACHELocation is not large enough to handle the usual amount of changes to the volume.
The specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot backup or archive operation.

System action

Processing stopped.

User response

If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation.

FMV1379E The snapshot operation failed. The percent of space to use for the SNAPSHOTCACHELocation, specified via the SNAPSHOTCACHESize, has been exceeded.

Edit online

Explanation

The SNAPSHOTCACHELocation is not large enough to handle the usual amount of changes to the volume.
The specified SNAPSHOTCACHESize is not set to a large enough value to handle the usual amount of changes to the volume during snapshot backup or archive operation.

System action

Processing stopped.

User response

If the problem persists, increase the SNAPSHOTCACHESize or change the value of the SNAPSHOTCACHELocation.

FMV1380W The snapshot operation failed. The filesystem write activity prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options.

Edit online

Explanation

System action

Snapshot processing stops.

User response

If the problem persists, modify the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options to better fit the normal disk write activity of the volume being backed up.

FMV1381W On volumes that are RAW or formatted FAT32 the snapshot cache location cannot be located on the same volume that is being backed up.

Edit online

There are two possible reasons for this message:

The option option was specified for a scheduled command or subcommand (function) that cannot make use of that option.
The option appears on a scheduled command but is valid only on the client scheduler initial command line, not on commands in a schedule from the server.

System action

The option is ignored.

User response

See the Backup-Archive Client Installation and User's Guide for correct use of the named option. The system administrator should remove the invalid option from the schedule definition on the server.

FMV1395E The destination filespace or drive letter is unavailable. The following object was not processed: Filespace:'`filespace-name`'

Edit online

The file "log-name" could not be opened during initialization. The system set the error code errno-value. If the reason given is "access denied," the current user does not have permission to write to the log in the directory specified. It is also possible that no space is available at the given log location.

On Unix systems, the log must not be in the root directory. Attempts to do so will result in an "access denied" error.

System action

Processing terminates.

User response

Set the DSM_LOG (or DSMI_LOG) environment variable to a directory into which the current user can write. You may also use the ERRORLOGNAME option to specify a file to which the current user has write permission.

FMV1399W The logical volume snapshot agent (LVSA) is currently busy performing a snapshot on this same volume.

Edit online

Explanation

IBM Storage Protect was not able to take a snapshot of the specified volume because another process is already performing a snapshot of this volume. The operation continues without snapshot support.

System action

Snapshot processing stops.

User response

Wait until the other IBM Storage Protect process finishes with the volume and then try the operation again.

FMV1400W The snapshot cache location is not valid.

Edit online

The specified image object of type object-type could not be located on the server. The operation cannot complete without this object.

System action

The operation ends.

None.

System action

The registry is not restored.

The registry is not backed up.

User response

FMV1436E An error occurred replacing a registry key.

Edit online

Explanation

None.

System action

The registry key is restored from the server, but cannot be activated in the registry. The current registry key remains active.

User response

FMV1437I Event Log Backup function completed successfully.

Edit online

Explanation

Event Log backup was successful.

System action

None.

User response

Continue with normal operations.

FMV1438E Backup of the event logs failed.

Edit online

Explanation

None.

System action

The event logs are not backed up.

User response

FMV1439I Event Log Restore function completed successfully.

Edit online

Explanation

Event Log Restore was successful.

System action

None.

User response

Continue with normal operations.

FMV1440E Restore of the event logs failed.

Edit online

Explanation

None.

System action

The event logs are not restored.

Creation of the NAS image object failed for one of following reasons:

An unauthorized user invoked the NAS command
NAS operations are not supported on the current platform
Cannot find the NAS plugin library.

System action

The requested NAS operation is not performed.

User response

Retry the operation after correcting the cause for failure.

FMV1446E VSS ASR backup document (ASRBackupDoc.xml) not found.

Edit online

Explanation

An error occurred while performing VSS Automated System Recovery (ASR). Check dsmerror.log for more information. Possible causes for the error are the following:

You are trying to recover a machine running a legacy operating system such as windows XP or windows 2003. VSS ASR Restore is not supported for legacy operating systems.
You are trying to run ASR recovery from a backup created by a client earlier than version 6.2.2. Such backups do not have ASRBackupDoc.xml file.

System action

Processing stops.

User response

Ask your system administrator to check the error log.

FMV1448E The `command` command is not supported by the current server.

Edit online

Explanation

The server to which the client is connected does not support the command.

If the command is "set event," the server does not support event-based policy. This command requires that the server supports event-based policy. That support is available only at IBM Storage Protect Server levels 5.2.2 and above.
If the message displays any other command, the server is configured to support archive retention protection and cannot process operations that are not associated with that facility.

System action

The command is skipped and other processing continues.

The entire volume is backed up.

Ctrl-C - This indicates either the user entered the ctrl-c sequence or that one of the Windows services was stopped.

Explanation

The specified file system is network disk or network share. Because the CLUSTERNODE option is set to YES, the file system cannot be backed up or archived.

System action

Processing stops.

A virtual machine with this name was backed up, and it has a different virtual machine UUID than the virtual machine that is backed up now. This can occur if there are two virtual machines with the same name that are backed up to the same data center node name. In this case, the backup can not continue because the backup-archive client uses the virtual machine name to uniquely reference the virtual machine on the IBM Storage Protect server.

This can also occur if the virtual machine UUID changed after a previous backup operation. This is the case after the following events:

Virtual machine VM_1 backed up.
Virtual machine VM_1 is restored with a new name: VM_2. A new UUID is assigned to VM_2.
Virtual machine VM_1 is deleted.
Virtual machine VM_2 is renamed to VM_1.

System action

The backup of this virtual machine fails. The backup process can continue with other virtual machines.

User response

If there are two or more virtual machines with the same name in the data center inventory, you can complete either of the following actions:

Rename the virtual machines so that all names in the data center inventory are unique.
Backup up virtual machines with the same name to different IBM Storage Protect servers.

System action

The inaccessible file system is ignored.

The server has been halted.
The network connection to the server is down.
The communication program that IBM Storage Protect is interacting with has encountered some problem.

0 - The command completed successfully
4 - One or more files were skipped
8 - One or more warning messages were issued
12 - One or more error messages (except for skipped files) were issued

FMV1901I Highest return code was `return code value`.

Edit online

Explanation

This message indicates the highest return code of all the client commands that were executed. In order of increasing severity, the return code meanings are:

0 - The command completed successfully
4 - One or more files were skipped
8 - One or more warning messages were issued
12 - One or more error messages (except for skipped files) were issued

The scheduled event is failed. The result code for the event is 12.

The client tried to restore or retrieve the specified directory. The directory exists in the target restore location and the user chose not to replace the existing directory.

The directory can be skipped because the option REPLACE=NO is set, which causes all existing files and directories to be skipped. The directory can be skipped because option REPLACE=PROMPT is set, and the user chooses to skip this directory when prompted.

System action

The directory is skipped, a message is logged in the dsmerror.log log file, and restore or retrieve processing continues with the next object.

User response

System action

processing stops.

The client received an invalid option from the IBM Storage Protect server's client option set. Although most syntax checking for client option set options is done by the server, there are still errors that can only be detected by the client. These errors include:

Option value is not correct.
Options that have been retired by newer versions of the IBM Storage Protect client.
Missing brackets or directory delimiters.
Include and exclude patterns that are too complex.

System action

Processing continues.

User response

The requested IBM Storage Protect server was not added to the multi-server environment. There are several causes for this error:

The file system is not managed by HSM.
The HSM management is not active for the file system.
The file system is out of space.
The default IBM Storage Protect server for the file system was not yet added to the multi-server environment.
The IBM Storage Protect server name is not valid.

System action

HSM multi-server processing stops.

User response

Eliminate the possible causes for this issue and retry.

FMV2157E The server '`server-name`' was not removed from the environment.

Edit online

Explanation

The requested IBM Storage Protect server was not added to the multi-server environment. There are several causes for this error:

The file system is not managed by HSM.
The HSM management is not active for the file system.
The IBM Storage Protect server is the default server for the file system and must be removed last.
The IBM Storage Protect server name is not valid.

Database files are located on the dynamic disks, GUID Partition Table (GPT) disks, iSCSI disks or other Network Attached Storage devices.
Microsoft Exchange Server databases are in the dismounted state during virtual machine backup.
Microsoft Exchange Server databases are in the unhealthy state or with unhealthy database copies.
Microsoft Exchange Server databases are being backed up by a different server at the same time.
When vmPreferDagPassive option is set to YES, Microsoft Exchange Server databases are active copies on the current server and have a healthy passive copy on another server.
Microsoft Exchange Server Exchange databases are in the unknown state because IBM Storage Protect is not able to determine the database health status during virtual machine backup.

System action

The backup operation of the full virtual machine continues.

User response

Take one or more of the following actions to resolve the issue:

Move the database files to disks that are supported by in-guest application protection.
Mount the dismounted Microsoft Exchange Server databases before the virtual machine backup.
Repair the Microsoft Exchange Server databases in the unhealthy states.
Use the VMTSMVSS trace flag on the data mover to trace database health status processing during virtual machine backup operations.

If a remote mount proxy node is used, ensure that the default_mp_httpport option is specified in the frConfig.props file with a valid TCP/IP port address.

FMV2269E The maximum number of backups were loaded. If a restore is running, wait for it to complete and load the backup again. If the backup is loaded in another browser window, close that browser.

Edit online

Explanation

To mount another backup, one of the mounted backups must be dismounted.

System action

Processing stops.

User response

Dismount one of the mounted backups and try the operation again.

FMV2309I Single Sign On login to the vSphere Server failed in function `function`. `API message` A credential login is now attempted.

Edit online

Explanation

The Single Sign On (SSO) login to the vSphere Server failed. Possible reasons for this failure include the following situations:

A time difference exists between the vSphere Server clock and the client clock that exceeds 10 minutes.
The SSO server accesses a non-default port. This issue can occur when the SSO server is installed on the same system as the VMware vCenter.

System action

The system attempts a credential login as a result of the SSO login failure.

User response

Check the dsmerror.log file for details about why the SSO login attempt failed. Then, take any corrective action, if needed.

FMV2310E The create snapshot task is disabled on the virtual machine '`VM-name`'. As a result, the virtual machine cannot be backed up.

Edit online

Explanation

Virtual machines that are managed or replicated by another application disable the create snapshot task. The vSphere client or another application disabled the create snapshot task on this virtual machine. As a result, this virtual machine cannot be backed up.

System action

The backup operation skips the virtual machine with the disabled create snapshot task and continues processing the remaining virtual machines.

User response

None.

FMV2311E The create snapshot task is disabled on the virtual machine. As a result, the virtual machine cannot be backed up.

Edit online

Explanation

The indicated volume is a disk witness. Because the CLUSTERNODE option is set to YES, the volume cannot be backed up or archived.

System action

Processing stops.

None.

FMV2378W The single sign-on session to the Platform Services Controller (PSC) failed with the following message: `apimessage`

Edit online

Explanation

The single sign-on session to the Platform Services Controller (PSC) failed. The possible reasons for this failure include the following situations:

This issue might occur when the system clock on the on PSC host, vCenter Server host, and client host are out of sync, or the time zones settings are incorrect.
The PSC single sign-on server accesses a non-default port. This issue might occur when the single sign-on server is installed on the same system as the VMware vCenter.

A completion code of 0 indicates that all items were successfully restored.
A completion code of 8 indicates that the restore operation was completed but some items were not restored.
A completion code of 12 indicates that the restore operation was unsuccessful.

Explanation

This error can occur due to any of the following:

The LAN connection to the IBM Storage Protect client machine went down.
You are trying to connect to the IBM Storage Protect client machine using the wrong port number.
The client acceptor on the IBM Storage Protect client machine is not up and running and accepting connections.

System action

The IBM Storage Protect operation ends.

User response

Retry the operation and make sure the LAN is up. Also check that the port number is correct, and that the client acceptor is started and running on the IBM Storage Protect client machine, and that it is listening on the correct port number.

FMV2610S TCP/IP communications failure between the client and the server machine.

Edit online

The Java runtime library (libjvm), required by the vCloud Suite plug-in library, cannot be loaded, or the initialization of Java runtime environment failed.

System action

Operation is stopped

Edit online

Explanation

Explanation

This error occurred because Windows Management Instrumentation (WMI) classes were not registered or have become unregistered. WMI classes are registered with Windows features.

System action

Initialization of a Windows Management Instrumentation object failed.

FMV2752E The RESTORE VM command failed because the Data Protection for Microsoft Hyper-V license file does not exist or is not valid.

Edit online

Explanation

The Data Protection for Microsoft Hyper-V license file is required for the BACKUP VM command.

System action

The command is not processed.

Explanation

System action

The client does not execute the snapshot differential backup operation.

The operation does not start.

User response

Edit online

Explanation

An error occurred while obtaining information from the operating system. The volume information could not be obtained.

System action

Processing can continue if the information being obtained is not critical for the operation or if it is expected behaviour in the context of the operation being performed.

User response

FMV3403W Volume `name` cannot be opened for reading. System error code is `err`.

Edit online

Explanation

The named volume could not be opened. Examples of why this can occur include, but are not limited to: the device is not a valid system device, the device is locked by another application, or the user does not have correct or permissions. The operating system error code shown in the message indicates the specific reason for the failure.

System action

Processing stops.

User response

Use your operating system's tools to obtain the description of the error code. Also check the error log for any other messages that might indicate a reason for the failure. Try to correct any indicated problems, then try the operation again. If the problem persists, contact IBM Storage Protect technical support for further assistance.

FMV3404W An error occured reading volume `name`.

Edit online

Explanation

The named volume could not be read. Examples of why this can occur include, but are not limited to: the data being read is outside the valid range of the volume, or the device is locked by another application. The operating system error code shown in the message indicates the specific reason for the failure.

System action

If server-free data movement is used, processing continues using non-server-free data movement. Otherwise processing stops.

User response

FMV3405W File system `fs` on volume `name` is unknown.

Edit online

Explanation

The file system on the volume is not supported for the operation being performed.

System action

If server-free data movement is used, processing continues using non-server-free data movement. Otherwise processing stops.

Processing stops.

User response

FMV3410E The operating system refused a request for memory allocation.

Edit online

Explanation

The process requires access to memory in order to store information as processing proceeds. In this case, more memory was requested than the operating system would allocate. Possible reasons include:

The system is low on memory.
The process in which the program runs has exceeded the maximum memory that it is allowed to allocate.
Some other error condition occurred that caused the program to think it is out of memory.

System action

The process cannot complete the requested operation.

User response

User response

FMV3418W Memory allocation request for image backup operation was refused by the operating system.

Edit online

Explanation

IBM Storage Protect requires access to memory in order to store information about used blocks of a file system. In this case, more memory was requested than the operating system would allocate.

System action

If imagegapsize is too small for a dedicated filesystem and the client faces out-of-memory condition then the client automatically switches to full volume backup. Operation continues with imagegapsize = 0.

User response

Some recommendations to avoid the out-of-memory condition:

check to see if the memory resource limit is too low by entering the following command: ulimit -a Then you can ask the UNIX system root user to increase memory limit.
increase the value of the imagegapsize option. The bigger imagegapsize is used, the less memory is needed for image backup, but more unused data is sent to server. And vice versa: the smaller imagegapsize is used, the more memory is needed for backup, but less unused data is sent to server. The outcome also depends much on how data is spread on the volume.

Explanation

System action

IBM Storage Protect processing stops.

Edit online

The client prompts you for action:

Retry this object
Skip this object
Abort the action

A file being backed up/restored or archived/retrieved exceeds system set limits for this user. Shown below are the filesize limits corresponding to 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-OS9: 2,147,482,624 (2GB-1K)
Mac OS9: 18,446,744,073,709,551,616 (16EB)
NetWare: 4,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 higher: 1,099,511,627,775 (1TB-1)
Tru64 UNIX: 1,099,511,627,776 (1TB)
UnixWare: 2,147,483,647 (2GB)
Windows ME (FAT32): 4,294,967,295 (4GB)
Windows NT/2000 (NTFS): 17,592,185,978,880 (16TB-64K)

See your system administrator to report this problem. This error is a system failure.

FMV4033E Error processing '`filespace namepath-namefile-name`': file compressed on a different client machine that has more memory

Edit online

The compressed file cannot be expanded correctly due to one of the following reasons:

There is a problem on the tape.
There is a communications problem.
The compressed file was corrupted on the IBM Storage Protect Server.

User response

There are three possible ways to make decryption work:

Re-encrypt the file under the encryption key of a group to which both the owner and the back-up/archive user IDs belong
Add the back-up/archive user ID to the list of users authorized to decrypt this file
Run the back-up or archive under the owner's user ID, if possible

FMV4052E Error processing '`filespace namepath-namefile-name`': Encrypted-file-system (EFS) file cannot be restored, because file system does not support restore from the raw-EFS back-up data, or possibly because the restore function does not have write access to the directory.

Edit online

Explanation

The file being processed is encrypted by an encrypted file system (EFS). The file was backed up in the raw encrypted format. Either the target filesystem does not support the encrypted format, or restore does not have write access to the directory to which the file is to be restored.

System action

The restore is terminated.

User response

The file cannot be restored to this location if the file system is not the AIX Enhanced Journaled File System (JFS2)
If the file is JFS2 but EFS is not enabled, then EFS must be enabled before the file can be restored
If the user ID under which restore is being run does not have write permission for the directory, the permissions must be changed or the restore must be run under a different user ID

FMV4053E Error processing '`filespace` `path` `filename`': The file cannot be restored because the file system or operating system does not support the Encrypting File System (EFS) data.

Edit online

Explanation

The specified object was backed-up as raw Encrypting File System (EFS) data. The client is trying to restore or retrieve the object to a destination that does not support the EFS data. The location might not support the EFS data for one of the following reasons:

The operating system does not provide the support, or is a release that does not include the support
EFS support has not been activated on the operating system
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 it to an AIX operating system environment supporting EFS data.

FMV4054E Error processing '`filespace namepath-namefile-name`': The encryption key is not loaded.

Edit online

Explanation

The file being processed is encrypted by an encrypted file system (EFS). The option is specified to backup or archive the file in decrypted form. The encryption key, required to decrypt the file, is not loaded in the kernel keyring.

System action

The file is skipped.

User response

There are three situations in which this problem can occur:

You just performed initial activation of EFS on the AIX system, and have not logged out. AIX does load the keys for the session running at the time of initial activation. Solution: Logout and login again.
The login password has been changed recently, and you normally run with the EFS password the same as the login password. AIX does not automatically change the EFS password when you change the login password. Solution: Issue 'efskeymgr -n' to set the EFS password to be the same as the login password.
You need to run the decrypting backup when the EFS password is different from the login password. Solution: Issue 'efskeymgr -o ksh' to launch a new shell with the keys loaded. AIX will prompt you for the EFS password as you launch the shell. Run the backup from the new shell.

FMV4055E Cannot update file space '`filespace-name`': the file space version on the IBM Storage Protect server is not compatible with this client

Edit online

Explanation

The file space on the IBM Storage Protect server is not compatible with this client. This is caused by performing a backup or archive operation with a client and then using a down-level client and attempting a backup or archive operation targeting the same file space. This problem occurs specifically after a Windows or AIX client V6.1 or higher performs a backup or archive operation and then a subsequent backup or archive operation is attempted with a client V5.5 or lower.

System action

Processing stops.

User response

Use the correct level of the client.

FMV4056E Object '`object-name`' returned by the IBM Storage Protect server has a high-level name that exceeds the maximum length of 6000 characters. The file or directory cannot be processed.

Edit online

Explanation

The IBM Storage Protect server returned information about a backup or archive version with a high level name that exceeds 6000 characters. The high-level name is the directory path that contains the object (file or directory).

This message is displayed when all of the following conditions are true:

The object was backed up or archived by a version 6.1 or lower IBM Storage Protect client.
The object was backed up or archived to a version 5.5 or lower IBM Storage Protect server.
IBM Storage Protect client version 6.2 or higher is attempting to perform an operation that causes the IBM Storage Protect server to return information about this object to the client. Note: During incremental backup, the server returns information to the client about active backup versions which is used to determine which files have changed.

Beginning with IBM Storage Protect server version 6.1, the maximum high level name length was reduced from 8192 characters to 6000 characters. Objects with high level names that exceed 6000 characters are not supported for backup or archive. Beginning with IBM Storage Protect backup-archive client version 6.2, the maximum high level name length was similarly reduced.

System action

The file or directory specified in the message is skipped. Processing will continue with the next object.

User response

Contact your IBM Storage Protect server administrator for further assistance.

FMV4058I A write failure occurred while attempting to save node replication failover values to the options file.

Edit online

An error in the Microsoft Windows API prevents successful restore of files that meet the following conditions:

The file is encrypted by Microsoft Encrypting File System (EFS) at the time it was backed up
The file includes at least one data stream (alternate "named" stream or unnamed stream) that is sparse
The operating system is any edition of Microsoft XP, Microsoft Windows Server 2003, or Microsoft Windows Server 2003 R2

Because the file cannot be restored, IBM Storage Protect does not back it up. The problem is documented 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 if there are no further objects.

User response

If this message is issued during a backup operation, you can do the following:

Disable EFS encryption for the file so that it can be backed up.
If a backup copy of the file is not necessary, you can exclude it from backup.

FMV4090I File server `file-server-name` has been upgraded to Data ONTAP version '`version`.`modifcation`.`submodification`'. Perform a full incremental backup by specifying option createnewbase=migrate as soon as possible.

Edit online

Link cannot be restored or retrieved because the destination file system has exceeded maximum number of links allowed.

System action

The client prompts you for action:

Skip this object
Abort the action

User response

For more information about Windows installer error messages, go to the Microsoft Developer Network (MSDN) technical library at http://msdn.microsoft.com/en-us/library and search on "Windows Installer Error Messages".

Check the install log on the client computer.

FMV4206E The Deployment Manager received an error while extracting from installation image: `image name`.

Edit online

Explanation

The installation image might be missing, corrupted, or there might be insufficient disk space on the client computer.

System action

Deployment Manager stops.

User response

Make sure that there is sufficient disk space on the client computer.

Processing stops.

No more files can be restored or retrieved because the quota of the destination file system has been reached.

System action

The client prompts you for action:

Retry this object
Skip this object
Abort the action

User response

FMV5004S There is no backup copy group in the management class used for directories. See the error log.

Edit online

Explanation

The DIRMC option names a management class that contains no backup copy group.

System action

processing stops.

Continue with normal operations.

FMV5015I Restore stopped by user

Edit online

Explanation

Explanation

Explanation

System action

The processing stopped.

User response

You can take any of the following actions:

For client, set COMPRESSALWAYS=NO and COMPRESSIon=YES in the options file (DSM.OPT), then the file will be resent uncompressed if it grows during compression.
Request the system administrator to add space to the storage pool.
The system administrator can also turn off disk caching in the disk storage pool, and issue MOVE DATA commands to each disk pool volume to clear out the cached bitfiles.

FMV5040E Server media mount not possible.

Edit online

Explanation

Server media mount not possible. The server timed out waiting for a mount of an offline volume.

System action

File skipped.

User response

Retry later when server volumes can be mounted. Ensure that the MAXNUMMP (maximum number of mount points) defined on the server for this node is greater than 0.

FMV5041E Size estimate exceeded.

Edit online

Explanation

System action

Processing stopped.

User response

FMV5042E File data is currently unavailable on the IBM Storage Protect server

Edit online

Explanation

The IBM Storage Protect client was trying to restore or retrieve data that is currently unavailable on the IBM Storage Protect server. Possible causes are:

Data is corrupted at the IBM Storage Protect server
The IBM Storage Protect server encountered a read error
File is temporarily involved in a reclaim operation at the server
The IBM Storage Protect requested a tape volume that is unavailable. Typical reasons for a volume to be unavailable: a disk volume is offline, the volume is marked unavailable due to an I/O error, or a tape volume is checked out of the tape library.

The system is low on memory.
The process in which the program runs has exceeded the maximum allocated memory.
Some other error condition occurred. No memory is available.

System action

Processing stops.

User response

The administrator can take the following actions to correct the problem:

Ensure that the Windows domain credentials provided in the configurations notebook has the correct permissions to connect to the virtual machine.
Ensure that the virtual machine is powered on and any firewall has been updated to allow connections from the mount proxy machine.
Ensure that the mount proxy machine is able to connect to the virtual machine manually to ensure there is no networking issue.

For off-load backup requests, a hardware provider cannot be found
For off-load backup requests, the provider does not support transportable media
For local backup requests, the provider does not support persistent snapshots
For backup requests of Hyper-V virtual machines that are located on the volume with a Cluster Shared Volume File System and the VSSUSESYSTEMPROVIDER option is set to YES

System action

Processing stops.

User response

Windows 2003 update rollup package KB940349
Windows Vista Service Pack 1

This new VSS fix packages causes VSS to generates .xml control files in a format which is not compatible with the earlier versions of VSS. This error can occur when a system state restore is being performed from a base operating system level which does not have the VSS fixes applied and the system state backup files were created by an operating system level that did have the VSS fixes applied.

System action

Processing stops.

User response

The restore procedure for Windows system state requires that the operating system version and service pack level used to initiate the restore be at the same operating system and service pack level used to create the system state backup. In addition note the following:

On Windows 2003 systems you must also apply the VSS rollup package KB940349 prior to performing the Ssystem state restore.
On Windows Vista you must apply the same service pack that was installed at the time of backup prior to performing the system state restore.

With BACKUP IMAGE, SNAPSHOTROOT cannot be used unless SNAPSHOTPROVIDERIMAGE has one of the following values in effect:

VSS
JFS2

System action

User response

FMV7939E Invalid FastBack volume specification.

Edit online

Explanation

You must enter at least one FastBack client with the "-fbclientname=" option before entering a FastBack volume name.

IBM Storage Protect was not able to remove space management from this file system. Possible causes:

Kernel extension is downlevel.
Program is downlevel.
Insufficient disk space.

Edit online

Explanation

The IBM Storage Protect Client has detected that HSM is installed on the system. LAN-free is not a valid option when HSM is installed.

This error occurs on AIX when this file is found: /usr/tivoli/tsm/client/hsm/bin/dsmrecalld
This error occurs on Solaris when this file is found: /opt/tivoli/tsm/client/hsm/bin/dsmrecalld

Explanation

The entry for the file system in the dmiFSGlobalState file cannot be removed. Possible reasons:

There is not enough memory to create temporary file name for temporary file system table.
There is not enough free space or inodes to create temporary file system table
The real or temporary file system table files cannot be opened.

FMV messages

FMV0101E Unable to open English message repository file name.

Explanation

System action

User response

FMV0102W Unable to open the message repository file name. The American English repository will be used instead.

Explanation

System action

User response

FMV0103E Error trying to read header record from message repository file name.

Explanation

System action

User response

FMV0105E Error trying to read index for message number from repository file name.

Explanation

System action

User response

FMV0106E Message index not found for message number.

Explanation

System action

User response

FMV0107E Error trying to read header for message number from repository file name.

Explanation

System action

User response

FMV0108E Error trying to read text for message number from repository file name.

Explanation

System action

User response

FMV0109E Insufficient memory for allocation of message structure.

Explanation

System action

User response

FMV0110E Unable to open error log file file name for output.

Explanation

System action

User response

FMV0113E Message repository file name has an invalid control record.

Explanation

System action

User response

FMV0118E Unable to open schedule log file 'file name' for output.

Explanation

System action

User response

FMV0119E Error trying to read response string for message number from repository file name.

Explanation

System action

User response

FMV0120E Message number number contains an invalid multibyte sequence for the current locale.

Explanation

System action

User response

FMV0121W Unable to open the iconv converter for the message repository file name. The American English repository will be used instead.

Explanation

System action

User response

FMV0200E The virtual machine 'VM-name' was backed up with a later version of the backup-archive client.

Explanation

System action

User response

0109 EFMV0201E DSM_RC_INVALID_PARM Invalid parameter was found.

Explanation

System action

User response

0123 EFMV0202E DSM_RC_NO_AUTHORIZATION Not authorized to restore the other node's data.

Explanation

System action

User response

0134 EFMV0203E DSM_RC_NO_LEADING_DIRSEP The objName field has no leading directory separator.

Explanation

System action

User response

0135 EFMV0204E DSM_RC_WILDCARD_DIR Wildcards are not allowed in the objName directory path.

Explanation

System action

User response

0620 EFMV0205E DSM_RC_LOG_CANT_BE_OPENED Unable to open error log file.

Explanation

System action

FMV0101E Unable to open English message repository `file name`.

FMV0102W Unable to open the message repository `file name`. The American English repository will be used instead.

FMV0103E Error trying to read header record from message repository `file name`.

FMV0105E Error trying to read index for message `number` from repository `file name`.

FMV0106E Message index not found for message `number`.

FMV0107E Error trying to read header for message `number` from repository `file name`.

FMV0108E Error trying to read text for message `number` from repository `file name`.

FMV0110E Unable to open error log file `file name` for output.

FMV0113E Message repository `file name` has an invalid control record.

FMV0118E Unable to open schedule log file '`file name`' for output.

FMV0119E Error trying to read response string for message `number` from repository `file name`.

FMV0120E Message number `number` contains an invalid multibyte sequence for the current locale.

FMV0121W Unable to open the iconv converter for the message repository `file name`. The American English repository will be used instead.

FMV0200E The virtual machine '`VM-name`' was backed up with a later version of the backup-archive client.